Transcript Data Partner

MDPHnet & ESP Data Partner
Participation Overview
The following slides describe the necessary steps for a data partner to
participate in the MDPHnet Network as a queryable data partner
How a site participates as a queryable data partner for MDPHnet
• Install and configure the ESP server and software
• Populate the ESP database
• Develop EHR extract(s) to populate ESP data model and MDPHnet reporting
schemas
• Run processing scripts to load data
• Set up routine (daily or weekly) data feeds
• Email monitoring options available
• Install and configure the Query Tool DataMart Client software
• Go live!
• Create, receive, and respond to queries
• Participate in the MDPHnet community
• Consider next steps!
• ESP notifiable disease case reporting, RiskScape, TrimTracker
General MDPHNet / ESP Wiki Page with additional resources:
https://popmednet.atlassian.net/wiki/display/DOC/MDPHnet
Step 1: Install ESP Server and Software Application
• Identify a LINUX server for the ESP application and database
• Install and configure a Postgres database, the open source ESP software,
and associated infrastructure
• Implement the UNIX shell scripts to be used for the “care and feeding” of
ESP’s processes
• ESP Website:
http://esphealth.org/ESPnet/images/ESP%20Deployment.html
• Wiki:
https://popmednet.atlassian.net/wiki/display/DOC/ESP%3A+MDPHnet
Step 2: Populate ESP Database
• Determine data to include in the ETL (extract, transform, load) process
from the EHR to ESP
• Complete data mappings*
• Run processing scripts to load data
• Implement the extracts for to populate the MDPHnet reporting schema
• Set up routine (daily or weekly) data feeds
*Note that the level of effort for data mapping will vary depending on the level of MDPHnet participation. For
example, a site participating as a queryable data partner requires fewer resources than a site participating in
notifiable disease case reporting where lab mapping are much more extensive. There are several validated case
detection algorithms available for electronic automated reporting.
Step 3: Validate the EHR to ESP Data Feeds*
• Activities include:
• Data mapping & validation
• Troubleshooting
• Loading historical data
*Note that the level of effort for these activities vary depending on the level of MDPHnet
participation. For example, a site participating as a queryable data partner requires fewer resources
than a site participating in notifiable disease case reporting. There are several validated case detection
algorithms available for electronic automated reporting.
Step 4: Install MDPHnet Query Tool (PopMedNet) DataMart Client
• In order to receive and respond to MDPHnet queries, the open source DataMart
Client software must be installed with the ability to connect to the local ESP data
• User training and technical support for configuration and query response processes
available
• PopMedNet DataMart Client Overview
Wiki:
https://popmednet.atlassian.net/wiki/display/DOC/The+DataMart+Client+Appli
cation YouTube Video: https://www.youtube.com/watch?v=7eO9Nm7iqxE
• DataMart Client installation and setup
Wiki:
https://popmednet.atlassian.net/wiki/display/DOC/Configuring+the+DataMart
+Client
https://popmednet.atlassian.net/wiki/display/DOC/Configuring+your+DataMar
ts#ConfiguringyourDataMarts-ESPRequestsandSQLDistributionModelProcessors
YouTube Video: https://www.youtube.com/watch?v=HUcAwrU7LLk
Step 5: Go Live as a Queryable Data Partner!*
• After ESP is installed and the data are populated from the EHR, the Data
Partner can receive and respond to MDPHnet queries
• Query Overviews:
• https://popmednet.atlassian.net/wiki/display/DOC/Query+Composer+Request
• https://popmednet.atlassian.net/wiki/display/DOC/ESP+Query+Composer+Projections
• Review MDPHnet governance document
• Participate in the MDPHnet community working group
• Consider next steps!
• ESP notifiable disease case reporting https://popmednet.atlassian.net/wiki/display/DOC/ESPnet+Algorithms
http://esphealth.org/ESPnet/images/notifiable%20diseases.html
• RiskScape http://esphealth.org/ESPnet/images/RiskScape.html
• TrimTracker
*Test environments are available for sites to create, run and respond to queries on synthetic ESP data. Please
contact [email protected] if interested.
Example Query**: MDPH staff or Data Partner* (i.e. requestor) Composes a Menu-Driven
Query
Query Metadata
*Data partners currently only have access to query their own data
**Note that the system also allows arbitrarily complex customized analyses using user‐developed programs (i.e. SQL
8
distribution)
Requestor Composes the Query
Criteria Group:
Patients with Diabetes
9
Requestor Composes the Query
Criteria Group: And Hypertension
10
Requestor Composes the Query
Criteria Group: Without Stroke
11
DataMart Administrator Receives the Query
DataMart Administrator Inbox
12
DataMart Administrator Reviews Query Details
Administrator
can review
query input
13
DataMart Administrator Executes the Query and Reviews Results
…and output
14
DataMart Administrator Uploads Results
…and send results
back to the
requestor
15
Requestor Views Results
Requestor can view aggregate views (across all data partners queried), or by individual sites. Projected*
and adjusted results are also available.
*For more information about the projections functionality, see
https://popmednet.atlassian.net/wiki/display/DOC/ESP+Query+Composer+Projections
Requestor Views State-Wide Projections
Requestor Selects a Location
Requestor* Views Projections for a Town
*The requestor may be a data partner who uses this tool to project the query results of their patient
population to nearby towns in their catchment area or other towns of interest.
MDPHnet & ESP
Data Flow Diagrams
The following slides illustrate data flow processes for the different activities
that Data Partners can participate in:
•
•
•
•
MDPH aggregate querying & reporting: MDPH users querying multiple
data partners
MDPH aggregate querying & reporting: Data Partners querying their
local data
MDPHnet aggregate querying & reporting + ESP notifiable disease case
reporting
MDPHnet aggregate querying & reporting + ESP notifiable disease case
reporting + RiskScape + TrimTracker reporting
MDPHnet Query Tool Request Cycle
Optional
email
notification
to requestor
about
responses
MDPH
1
6
MDPHnet Query Tool Portal
Optional email
notification to
Data Partner
about new
requests
2
Data Partner1
3
PMN
DataMart
Client
4
Data Partner 2
3
PMN
DataMart
Client
4
PMN
DataMart
PMN
DataMart
ESP Application Server
ESP Application Server
MDPHnet Schema
MDPHnet Schema
EHR
5
EHR
*Workflow includes aggregate querying & reporting ; does NOT include ESP notifiable disease reporting
1. MDPHnet user creates
and submits query to
selected sites
2. Individual sites retrieve
query
3. Sites review and run
query against the ESP
database
via the PMN DataMart
Client
4. Sites review and
approve results
5. Individual site returns
results via secure
network
6. MDPHnet user views
results in PMN Portal
-Users at Data Partners
and MDPH have options
to receive query
notifications throughout
21
cycle
MDPHnet Query Tool Request Cycle: Data Partners
querying data for their site(s)
1. Data Partner user creates and
submits query for local data
analysis
Data Partner 1
1
6
MDPHnet Query Tool Portal
2
3. Sites review and run query
against their local ESP database
via the PMN DataMart Client
Data Partner1
3
PMN
DataMart
Client
5
2. The DataMart Administrator
or Analyst at the site retrieves
query
4
PMN
DataMart
4. DataMart Administrator or
Analyst reviews results
5. DataMart Administrator or
Analyst returns results via secure
network
ESP Application Server
MDPHnet Schema
6. Requestor from this Data
Partner views results in PMN
Portal
EHR
-Users at Data Partners have
options to receive query
notifications throughout cycle
*Workflow includes local aggregate querying & reporting ; does NOT include ESP notifiable disease reporting
MDPHnet Data Flow*
PopMedNet Query Tool (PMN) + ESP Notifiable Disease Reporting
Data Partner
PMN queries: include custom
queries for summary data as well as
routine aggregate reporting queries
(e.g. ILI)
Data Partner
Staff: Query
Requestor
MDPH
MDPHnet
Query Tool
(PMN Portal)
Data Partner
PMN DataMart
Client
PMN
DataMart
MDPH Staff:
Query
Requestor
ESP Application Server
MDPHnet Schema
ESP Data Model
MDPH BID
Notifiable
Disease
Case
Reports
*Workflow includes aggregate querying & reporting as well as ESP notifiable disease reporting
EHR
MDPHnet Data Flow*
PopMedNet Query Tool (PMN) +ESP Case Reporting + TrimTracker (TT) + RiskScape (RS)
FISMA Compliant Data
Center
MDPHnet
Query Tool
(PMN Portal)
MDPH
MDPH
Staff
ESP.org Server
Only
summary
counts and
averages are
sent to the
TT/RS
application
interface.
The
applications
generate
queries
based on
user
selections
TT/RS
applications
PMN queries are separate from RS/TT queries
and user activity. Include custom queries as
well as routine aggregate reporting queries
(e.g. ILI)
Data Partner
PMN DataMart
Client
PMN
DataMart
Data updated weekly, patient level
data with 1 row per patient with
numbers to represent the values and
variables. The site is also included. The
data are anonymized, categorized and
not identifiable. Data are sent from the
sites to the ESPHealth.org server
ESP Application Server
ESP Common Data Model
TT/RS database
MA Virtual Gateway
MDPH BID
Notifiable
Disease Case
Reports
RS/TT
anonymized
categorized
patient level
data
ESP
Common
Data
Model
EHR
*Workflow includes aggregate querying & reporting, notifiable disease reporting, TrimTracker, and RiskScape
MDPHnet
Schema