-
Notifications
You must be signed in to change notification settings - Fork 0
Problems Mapping OSCAR to E2E
irynadavies edited this page Aug 5, 2013
·
4 revisions
The E2E Labs section contains data pertaining to the specific patient's problem list. It covers chronic diseases and ailments as well as other noteable medical problems a patient may have.
User Assumptions
- The provider will search for the disease and perform a code search for data entry
- When no direct match is available, the provider will select the closest matching ICD9 code
- Diseases which no longer apply to a patient will be deleted from the UI
Data Assumptions
- Although Disease Registry supports ichppccode, we will assume that all diagnoses will be encoded in only icd9
- Ongoing concerns are outside exporter scope
- User has the ability to enter diseases either through disease registry or ongoing concerns
- Both methods of entry enter the database through different means - one is ICD9 while the other is freetext
Options
- Support both disease registry and ongoing concerns in the export
- Bound support of problem list to just disease registry
Decision
- We decided to bound the export to just the disease registry
- Disease registry supports codified ICD9 diseases - this is more impactful than freetext entries and is easier to interpret
Relevant OSCAR DB Tables: dxResearch
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