-
Notifications
You must be signed in to change notification settings - Fork 0
Iteration 11
This iteration is focused on implementing support for another EMR to join the SCOOP network.
This iteration will continue using a set of queries as a single batch or Query Set. These queries will be based on what was defined in IT6 and may expand on it as well as a set of Data Quality probes.
For more details on these queries, see IT11 Queries
Thusfar, the SCOOP network has only had intercompatibility with OSCAR EMR. Since SCOOP is designed to be EMR agnostic, bring in support from another EMR vendor for the SCOOP network would not only expand SCOOP's capabilities, but also expose places for improvement within the network's software.
The main goal this iteration is to achieve the capability of exporting E2E documents from a non-OSCAR EMR and be able to push the records into the query gateway via HTTP REST POST. Since the gateway supports E2E document imports, the gateway should be capable of at least importing some of the content without modification. With another source of data coming in to the SCOOP network, we would be able to identify what sections of data are not being properly handled and improve the resilience of the network.
Secondary goals for this iteration includes:
- Investigating Data Quality from both the source and the processed outputs
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