-
Notifications
You must be signed in to change notification settings - Fork 0
Immunization Mapping OSCAR to E2E
Jeremy Ho edited this page Mar 19, 2013
·
4 revisions
The E2E Immunization section contains data pertaining to the specific patient's immunization history.
User Assumptions
- The provider will select one of the provided preventions in the UI
- The old immunizations option will not be used
- All form fields will be filled in if the data is available
Data Assumptions
- Preventions listed will be in a bounded list. We expect that all types of possible preventions are listed are the only ones that can appear.
- There may exist immunizations that aren't included in oscar's list. There is no direct way of modelling them from the UI.
- New entries have to be added in via a flatfile change.
Decision
- Export will be bound to whatever OSCAR supports. Anything outside of that list is outside of export scope.
- OSCAR contains an immunization table as well as the prevention table
- Immunization is directly tied to the "old immunization" dialogue
Decision
- Export will not be suppoting the old immunizations table
- May be a good side project to develop a translator/updater from immunizations to prevention table
Relevant OSCAR DB Tables: prevention
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