Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-30268

Need to define use of PlanDefinition for each of the given use case types, currently unclear in the IG how they differ

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Triaged (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive with Modification
    • Specification:
      US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
    • Raised in Version:
      0.1.0
    • Work Group:
      Public Health
    • Related Artifact(s):
      USPublicHealthPlanDefinition
    • Related Page(s):
      Provisioning Workflow Specification
      Report Submission
      Research Data Extraction
      Research Data Query
    • Resolution Description:
      Hide

      We will propose to implement the following:

      1. Creating a separate PHA Reporting PlanDefinition profile with applicable constraints. Add specific examples for each of the use cases using the PHA PlanDefinition profile.
      2. Create a separate Research Data Extraction PlanDefinition profile with applicable constraints. Add specific example for the use cases using the Research Data Extraction PlanDefinition profile.
      3. Create a separate Research Data Query PlanDefinition profile with applicable constraints. Add specific example for the use cases using the Research Data Query PlanDefinition profile.
      Show
      We will propose to implement the following: Creating a separate PHA Reporting PlanDefinition profile with applicable constraints. Add specific examples for each of the use cases using the PHA PlanDefinition profile. Create a separate Research Data Extraction PlanDefinition profile with applicable constraints. Add specific example for the use cases using the Research Data Extraction PlanDefinition profile. Create a separate Research Data Query PlanDefinition profile with applicable constraints. Add specific example for the use cases using the Research Data Query PlanDefinition profile.
    • Change Category:
      Correction
    • Change Impact:
      Compatible, substantive

      Description

      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.  

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              rdingwell Rob Dingwell
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: