-
Notifications
You must be signed in to change notification settings - Fork 0
Iteration 6
This rapid 4 week iteration is focused on updating OSCAR's E2E exporter to version 1.3, updating hQuery's importer to handle E2E 1.3, and preparing a base set of queries for hQuery.
####AMCARE Queries
Nine queries below are a sub-set taken from the AMCARE list of indicators. They align with the AMCARE 1.0 XML specification so that, once these queries are answerable, they can be used in future iterations where the AMCARE XML output is generated by hQuery (or subcomponent).
- Practice population profile
- BMI or WC documented in last 2 yrs age >19
- Pneumococcal vaccination age 65+
- Fasting blood sugar in last 3 yrs age > 45
- Colon screening in last 2 yrs age 50-74
- Diabetes & BP <= 130/80 in last yr
- Diabetics with HGBA1C in last 6 mo
- Diabetics with HGBA1C in last yr <= 7.0
- Diabetics with LDL in last yr <= 2.5
####Rational Prescribing Queries
The queries below address Rational Prescribing. Some are carried over from the previous iterations and are strengthened in this iteration, while others are new.
- Patients, 65 and older, on 5 or more medications
- Patients, 65 and older, on 10 or more medications
- Most commonly prescribed medication classes
- Patients, 65 and older, with impaired renal function who are on digoxin >125 mcg/day
- Statins for primary prevention
- Statins for secondary prevention
This iteration, we will be defining a set of queries as a single batch or Query Set.
For more details on these queries, see IT6 Queries
One of the elements needed for the overall design is the ability to run (and rerun) sets of queries. These can be related queries in the sense of multiple, related queries (e.g. data quality queries that support interpretation of the main query) or they may be a batch of queries that are run routinely (e.g. in the case of the AMCARE query set).
The main goal of this iteration is to develop the process and tools to manage routine query sets. This would allow for hQuery to run at regular intervals, query sets of commonly asked asked questions that would be needed to be tracked over time such as for AMCARE or for a time series study.
Secondary goals for this iteration includes:
- Map E2E sections / data element to the complete set of AMCARE's current queries data requirements.
- Develop a subset of the AMCARE queries inside of hQuery in preparation for an AMCARE Exporter.
- Develop a query scheduler inside of hQuery.
To contain the scope of the query set, the sub-set of AMCARE queries has been chosen that should cover data elements that are currently included in the OSCAR E2E exporter. Additional mapping will occur in this iteration in preparation for including the full query set, once it has been documented and shared by AMCARE.
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