-
Notifications
You must be signed in to change notification settings - Fork 0
Encounter Mapping OSCAR to E2E
Jeremy Ho edited this page Dec 16, 2013
·
2 revisions
The E2E Encounter section contains data pertaining to the patient's visits or encounters with the provider or care practicioner. This data includes notes and annotations that the doctor would have saved regarding the visit.
User Assumptions
- The provider shall enter all encounter entries into OSCAR under the Encounter section of the Encounter page
- All relevant fields presented will be filled with data if applicable
Data Assumptions
- We expect encounter data to be a freetext field which will make sense to a human reader
- Encounter data will not be entered in other parts of OSCAR
- OSCAR records encounters as freetext while E2E expects codified data
Options
- Create a freetext parser to map freetext data to codes
- Ignore the code and populate with freetext, adding codes if available
Decision
- We decided to ignore the code requirement and populate the section with freetext on a best-effort basis
- If a code exists within the entry, it will be included
- Flag this to OSCAR and GPI to discuss
Relevant OSCAR DB Tables: casemgmt_note
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