-
Notifications
You must be signed in to change notification settings - Fork 0
Family History Mapping OSCAR to E2E
Jeremy Ho edited this page Apr 25, 2013
·
3 revisions
The E2E Family History section contains data pertaining to the conditions that the patient's family members have or have had in the past that may affect the patient's treatment.
User Assumptions
- The provider shall enter all family history entries into OSCAR under the Family History section of the Encounter page
- All relevant fields presented will be filled with data if applicable
Data Assumptions
- We expect family history data to be a freetext field which will make sense to a human reader
- Family History data will not be entered in other parts of OSCAR
- OSCAR records relationship as freetext while E2E expects codified data
Options
- Create a freetext parser to map freetext data to codes
- Ignore the code and default to other and saving the relationship freetext as a field
Decision
- We decided to default the code to other for the interim because parsing freetext to a code may cause more harm than good
- Freetext parsing is inherently not safe - you may be able to translate most cases without issue, but there will exist edge cases that can cause data loss
- Flag this to OSCAR and GPI to discuss
Relevant OSCAR DB Tables: casemgmt_note, casemgmt_note_ext
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