-
Notifications
You must be signed in to change notification settings - Fork 0
Allergy Mapping OSCAR to E2E
Jeremy Ho edited this page Mar 18, 2013
·
3 revisions
The E2E Allergies section contains data pertaining to the specific patient's allergy history. It aims to give detailed information about when their allergies started, their intensity, and onset.
User Assumptions
- The provider will search for the allergen and select the closest matching result if available
- Given two of the same results, the provider will select the one that is more specific
Data Assumptions
- The data will be assumed to be "complete" in the sense that no information is not recorded in the EMR
- Codified data will be available whenever possible, but is not guaranteed
- Codified data will represent a drug allergy, while any freetext allergy is of an unknown type.
- Allergies may contain codified data, but not all entries will be codified.
Decision
Discussion: 14-Nov-2012
- After some clinical insight and investigation, any codified allergy entry is classified as a drug allergy. Any free-text based entry is of an unknown type.
- Export will include codified data if available and return a nullFlavor when not available.
Relevant OSCAR DB Tables: allergy
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