Database
Revision as of 22:47, 8 February 2023 by Aesetholephews (talk | contribs)
Database Basic
- Relational databases (e.g. MySQL) are probably the most common. Essentially they store data in a set of 2D tables (relations) that follow certain rules of normalization and can be linked to each other via relational algebra (mostly set theory type functions).
- To address problems encountered when trying to interface a RDBMS with an object-oriented programming language, alternative non-relational database structures (e.g. XML, NoSQL, Hierarchical, Network) are available and may have advantages in certain situations.
- Tables (Relations/Relvars) are made up of Rows (Tuples/Records) and Columns (Attributes/Fields) where the intersection at a certain cell is called a value.
- Each Tuple should have a primary key (normally an arbitrary integer) that identifies a unique tuple. Natural keys (those based on attributes) are possible as well but less optimized.
Working Prototype
Disease | Risk Factors | Associated Conditions | Complications | Symptoms | Vitals | Signs | Labs | Imaging | Studies |
---|---|---|---|---|---|---|---|---|---|
Primary Key | LIST of epidemiologic risk factors (age, sex, race, family history) | problem LIST at time of presentation | LIST of possible complications (screening and anticipatory guidance) | LIST of symptoms (keep it broad: chest pain rather than substernal acute pressure-like chest pain with radiation) | LIST of vital abnormalities | LIST of pertinent positive/negative physical exam findings | LIST relevant lab abnormalities | LIST of useful imaging findings | LIST relevant echo/ECG/PFT/sleep/etc studies |