-
Type:
Change Request
-
Resolution: Persuasive with Modification
-
Priority:
Medium
-
US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
-
0.1.0
-
Public Health
-
US Public Health PlanDefinition
-
Provisioning Workflow Specification
Report Submission
Research Data Extraction
Research Data Query [deprecated] -
-
Correction
-
Compatible, substantive
The IG currently uses PlanDefinition for public health reporting , research data extraction and research data query. However it does not define the differences in how to use the plan definition to support each of these activities. For instance, Research Data Extraction contains the following:
The Backend Service App SHALL process a Knowledge Artifact PlanDefinition resource to determine the following
- Which Group to use to export the data for patients?
- How frequently the data has to be exported?
- What translations are required for the data post extraction?
What is not included in the IG is how to identify the group to extract the data for. It may be intending to leverage the subject[x] field of plan definition but it is not specified anywhere. If the plan is to leverage subject[x] then there needs to be some sort of coordination for the Group reference as plan definitions are applicable to more than a single site.
The IG also contains this
Step Q4: The Backend Service App receives the query via the Knowledge Artifact and runs submits the query for execution to the Data Mart.
Again however it isn't defined what that type of Knowledge artifact would look like compared to either a PHA reporting plan def or a research extraction plan def.
Theses items need to be defined so backend service apps can differentiate between the requirements needed for each type of situation.
- is voted on by
-
BALLOT-15053 Affirmative - Marc Hadley : 2021-Jan-FHIR IG MEDMORPH R1 STU
- Balloted