Difference between revisions of "Database"
Jump to navigation
Jump to search
Line 12: | Line 12: | ||
|- | |- | ||
| 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 | | 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 | ||
+ | |} | ||
+ | {| class="wikitable" | ||
+ | |+ Base Table | ||
+ | |- | ||
+ | ! Header text | ||
+ | |- | ||
+ | | Disease (PK) || text | ||
+ | |- | ||
+ | | Risk factors || text | ||
+ | |- | ||
+ | | Associated Conditions || text | ||
+ | |- | ||
+ | | Complications || text | ||
+ | |- | ||
+ | | Symptoms || text | ||
+ | |- | ||
+ | | Vitals || text | ||
+ | |- | ||
+ | | Signs || text | ||
+ | |- | ||
+ | | Labs || text | ||
+ | |- | ||
+ | | Imaging || text | ||
+ | |- | ||
+ | | Studies || text | ||
|} | |} |
Revision as of 17:22, 9 February 2023
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.
- Attributes contain values of the same data type (domain), e.g. integer, string, boolean.
- 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.
- Databases can be indexed to streamline queries.
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 |
Header text | |
---|---|
Disease (PK) | text |
Risk factors | text |
Associated Conditions | text |
Complications | text |
Symptoms | text |
Vitals | text |
Signs | text |
Labs | text |
Imaging | text |
Studies | text |