Strange data structures in CCMDB: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 8: | Line 8: | ||
* version table - only contain one value, the current version of the Access program they are in | * version table - only contain one value, the current version of the Access program they are in | ||
* [[Postal Code Master table]] | * [[Postal Code Master table]] | ||
* [[s_level_of_care table]] - deals with assigning [[Level of care hierarchy]] to [[Boarding Loc]]s | |||
* [[dates table]] | |||
* [[s_Priorities table]] | |||
* [[S_Standard_emails table]] | |||
== Related articles == | == Related articles == | ||
Revision as of 12:22, 9 May 2023
Some portions of CCMDB don't really fit into the
- Entity–attribute–value model of the L Tmp V2 table
- Charlson Comorbidity scoring in ICD10 codes
- APACHE Acute Diagnoses
- APACHE Comorbid Diagnoses
- Linking pairs table, Created_<name> tables - these are tables created as needed by queries; this is done because SAS could not read those access queries/views
- settings table - Settings
- version table - only contain one value, the current version of the Access program they are in
- Postal Code Master table
- s_level_of_care table - deals with assigning Level of care hierarchy to Boarding Locs
- dates table
- s_Priorities table
- S_Standard_emails table
Related articles
| Related articles: |