Flag | Table | Field | Best guess as to meaning / questions about fields | | | | | |
? | OBSERVATION_FACT | MODIFIER_CD | | | | | | see document |
? | OBSERVATION_FACT | VALTYPE_CD | What is the type of data? Text, numerical? | | | | | see document |
? | OBSERVATION_FACT | VALUEFLAG_CD | | | | | | see document |
? | OBSERVATION_FACT | QUANTITY_NUM | | | | | | see document |
? | OBSERVATION_FACT | CONFIDENCE_NUM | Some estimate of confidence in the accuracy of the data? | | | | | Yes |
? | PATIENT_DIMENSION | VITAL_STATUS_CD | | | | | | see document |
? | PROVIDER_DIMENSION | PROVIDER_BLOB | Free text entry about provider, but what would go here? | | | | | |
? | PROVIDER_DIMENSION | DOWNLOAD_DATE | dt was downloaded into etl area | | | | | YES |
? | PROVIDER_DIMENSION | IMPORT_DATE | dt was imported into star schema | | | | | YES |
? | VISIT_DIMENSION | INOUT_CD | Admission status: Inpatient, Outpatient? | | | | | YES |
? | VISIT_DIMENSION | LOCATION_CD | Ward, outpatient clinic, location of service | | | | | YES |
? | VISIT_DIMENSION | LOCATION_PATH | How does this differ from Location_CD? | | | | | Clinics\BWH\TSI\Arthritis Center (18)\ is an example of a path, it defines the hierarchical path to the code and describes how the hierarchy will look in the workbench |
? | VISIT_DIMENSION | UPLOAD_ID | | | | | | see document |
v | PATIENT_DIMENSION | STATECITYZIP_PATH | What would valid values look like for this? | | | | | Zip codes\Massachusetts\Everett\02149\ |
| | | | | | | | |
Other questions: | | | | | | | | |
| Why no provider in VISIT_DIMENSION? | | Our strategy leaves this in the fact table. A local implementation could put this in the visit table | | | | | |
| Where would procedures go in the i2b2 schema? | | Our strategy places this in the fact table. | | | | | |