Page History
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
i2b2 Design Document
Data Repository (CRC) Cell
Document Version: | 1.7.1 |
i2b2 Software Version: | 1.7.00 |
Table of Contents
Document Management
1. Introduction
2. i2b2 Data Mart
3. i2b2 Data Mart Tables
3.1. General Information
3.2. OBSERVATION_FACT Table
3.2.1. Value Columns
3.2.1.1. VALTYPE_CD Column
3.2.1.2. TVAL_CHAR Column
3.2.1.3. NVAL_NUM Column
3.2.1.4. VALUEFLAG_CD Column
3.2.1.5. UNITS_CD Column
3.2.1.6. OBSERVATION_BLOB Column
3.2.2. Example of Value Constraints Used in Queries
3.2.2.1. Value Constraint by Number
3.2.2.2. Value Constraint by Text
3.2.2.3. Value Constraint by Flag
3.3. PATIENT_DIMENSION Table
3.4. VISIT_DIMENSION Table
3.5. CONCEPT_DIMENSION Table
3.6. PROVIDER_DIMENSION Table
3.7. MODIFIER_DIMENSION Table
3.8. CODE_LOOKUP Table
3.9. PATIENT_MAPPING Table
3.10. ENCOUNTER_MAPPING Table
3.11. Joining Columns
4. Patient Data Object
5. Patient and Event Mapping Scenarios
5.1. Self-Mapping
5.2. New Mappings – Adding New Values
5.2.1. Use Case 1: Create new entry if PID not found
5.2.2. Use Case 2: Create new entry if patient does not exist
5.2.3. Use Case 3: Create new entry if hive entry does not exist for a patient
5.3. Handling Existing Values
5.3.1. Use Case 1: Hive id found but <patient_map_id> is not mapped
5.3.2. Use Case 2: Patient id, num and map_ids are not mapped
5.3.3. Use Case 3: PATIENT_NUM in mapping table but with a different date
5.3.4. Use Case 4: <patient> without a HIVE number
5.4. Invalid XML
5.4.1. Use Case 1: <pid> without a PATIENT_ID)
6. Observation Fact Scenarios
6.1. Use Case 1: Replace old facts with new facts
6.2. Use Case 2: Add new facts
7. Data Permission
8. Definition of Terms
