-
Notifications
You must be signed in to change notification settings - Fork 0
Core Data Model
Jeremy Ho edited this page Jun 5, 2013
·
2 revisions
The data model for SCOOP is, of course, central to answering questions. This will be the common extract from EMRs that can be queried at the end points. The scope of SCOOP data (sorry, couldn't resist) gives us the range of data we can query against.
We considered several options including
- C32 - already in HQuery. Well defined. Not implemented in Canadian EMRs
- Ontario MD export - XML, already in OSCAR. Not in all EMRs
- EMR2EMR DTC - CDA based, supported in BC, broad scope, would be implemented in all EMRs being considered by the PDC.
We chose to align on the EMR2EMR model as that is also what the PDC is developing against.
Based on the E2E, here is a high level model.
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