L CCI Component table: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 30: | Line 30: | ||
* [[CCI_2_Code]] - second component, <2 numbers><optionally more letters> | * [[CCI_2_Code]] - second component, <2 numbers><optionally more letters> | ||
To understand all [[CCI Procedure]]s for a patient, consider [[ | To understand all [[CCI Procedure]]s for a patient, consider [[L_CCI_Component table]] and [[L_CCI_Picklist table]] together, eg. by using the [[Query L CCI Resolver]]. | ||
== Related Articles == | == Related Articles == | ||
Revision as of 20:47, 16 January 2019
The L_CCI_Component table in CCMDB.mdb contains the CCI data collected as per CCI Collection. It's the counterpart of the L CCI Picklist table.
Data Structure
| field | type | description |
|---|---|---|
| L_CCI_ID | Long Integer(AutoNumber) | unique ID |
| Patient_ID/D_ID | text | link to L_Log table |
| CCI_1_ID | long integer | link to s_CCI_1 table, defaults to No procedure entered |
| CCI_2_ID | long integer | link to s_CCI_2 table, defaults to No procedure entered |
| Px_Date | Date/Time | Px_Date |
| Px_Date_missing | yes/no | originally intended for cross check if no Px_Date and Px_Type = acquired; not currently used or accessible in CCMDB.mdb front end |
| Px_Type | text(8) | Acquired, Admit, Comorbid |
| Px_Count | number (integer) | number of times procedure was performed on a given day |
How it works
Two fields together make a single CCI Procedure:
- CCI_1_Code - first component, <number between 1-8>.<2 letters>
- CCI_2_Code - second component, <2 numbers><optionally more letters>
To understand all CCI Procedures for a patient, consider L_CCI_Component table and L_CCI_Picklist table together, eg. by using the Query L CCI Resolver.