-
Notifications
You must be signed in to change notification settings - Fork 0
Demographic Mapping OSCAR to E2E
irynadavies edited this page Aug 5, 2013
·
9 revisions
The E2E Demographics section contains data pertaining to the specific patient that the record represents. Data such as name, age, gender, HIN, and birth date should be expected.
User Assumptions
- Each demographic in OSCAR represents one unique patient
- Each demographic will be independent of another
Data Assumptions
- Each demographic will map to exactly one E2E record in the export
- There are no other constructs within OSCAR which models or represents a patient
- HINs, or Health Identification Numbers can be entered by the user in OSCAR but a HIN isn't considered a mandatory field. It is possible for a patient to have a record without the HIN documented.
- E2E requires a HIN to be populated - the field cannot be left empty
Decision
- The HIN field in E2E will be populated with "000000000" should the HIN not be defined within OSCAR.
- Birth Date within OSCAR is saved separately as day, month and year fields. E2E specifies birthdate as one field.
Decision
- The year, month and date are manually concatenated to create the expected E2E date output.
Relevant OSCAR DB Tables: demographic
SCOOP is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.
- SCOOP Overall Design
- SCOOP Actors
- User Stories and Use Case Maps
- System Architecture
- Development Process
- Prototypical Questions
- Current Meds vs Med List
- Data Enrichment Design
- Data Visualization
- Deployment Architecture
- EMR-2-EMR (E2E)
- OSCAR Setup
- Gateway & Hub Setup
- OSCAR Development Notes
- OSCAR DB Table Notes
- Coding Standards
- Mongodb Notes
- Server Configuration
- PDC Gateway Server
- Iteration Overview
- Feature List
- Architecture
- Requirements
- Visualization Requirements
- Test Specification