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

Clarify assumed functions within Knowledge Artifact Repository

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
    • 1.0.0
    • Public Health
    • Knowledge Artifact Repository
    • 3.2.3
    • Hide

      This is addressed in multiple sections in the current IG:
      http://build.fhir.org/ig/HL7/fhir-medmorph/provisioning.html
      • Section 5.1.5
      http://build.fhir.org/ig/HL7/fhir-medmorph/provisioning.html#notifications-of-changes-in-knowledge-artifacts
      o Notifications can be automated or manual and hence there is no expectation that all healthcare organizations automate the KnowledgeArtifact retrieval and operationalization.
      • Section 5.1.6
      http://build.fhir.org/ig/HL7/fhir-medmorph/provisioning.html#operationalization-of-knowledge-artifacts
      o There is explicit mention of testing of KnowledgeArtifacts before they are completely operationalized so that the healthcare organizations can understand the use case expectations.
      • The process of activation/de-activation is also specified in Content IGs (e.g Central Cancer Registry Reporting IG) to avoid automated processing.
      o https://build.fhir.org/ig/HL7/fhir-central-cancer-registry-reporting-ig/spec.html#knowledge-artifact-processing-requirements

       

      Comments from ONC Team:

      Request rephrasing in section 5.1.6

      "

      • Request re-phrasing: “Knowledge Artifacts have to be understood and operationalized by healthcare organizations during implementation. Before operationalizing the Knowledge Artifact and processing by the HDEA/ Backend Services App or by a Data Source, healthcare organizations shall test and validate the processing of the Knowledge Artifact before reporting to Data Receivers.
      • Specific requirements for the HDEA/ healthcare organization for receiving or producing a Knowledge Artifact shall be specified in the Content IG.”
      Show
      This is addressed in multiple sections in the current IG: http://build.fhir.org/ig/HL7/fhir-medmorph/provisioning.html • Section 5.1.5 • http://build.fhir.org/ig/HL7/fhir-medmorph/provisioning.html#notifications-of-changes-in-knowledge-artifacts o Notifications can be automated or manual and hence there is no expectation that all healthcare organizations automate the KnowledgeArtifact retrieval and operationalization. • Section 5.1.6 • http://build.fhir.org/ig/HL7/fhir-medmorph/provisioning.html#operationalization-of-knowledge-artifacts o There is explicit mention of testing of KnowledgeArtifacts before they are completely operationalized so that the healthcare organizations can understand the use case expectations. • The process of activation/de-activation is also specified in Content IGs (e.g Central Cancer Registry Reporting IG) to avoid automated processing. o https://build.fhir.org/ig/HL7/fhir-central-cancer-registry-reporting-ig/spec.html#knowledge-artifact-processing-requirements   Comments from ONC Team: Request rephrasing in section 5.1.6 " Request re-phrasing: “Knowledge Artifacts have to be understood and operationalized by healthcare organizations during implementation. Before operationalizing the Knowledge Artifact and processing by the HDEA/ Backend Services App or by a Data Source, healthcare organizations shall test and validate the processing of the Knowledge Artifact before reporting to Data Receivers. Specific requirements for the HDEA/ healthcare organization for receiving or producing a Knowledge Artifact shall be specified in the Content IG.”
    • Nagesh Bashyam/Bill Lober : 10-0-2
    • Correction
    • Compatible, substantive
    • 1.0.0

    Description

      Is it expected that other actors, like the HDEA, will interact with the Knowledge Artifact Repository and process a PlanDefinition or StructureDefinition on the fly/at run-time and without prior knowledge of the expectations of the use case?  Or will these expectations be fully defined at the time of onboarding so that the HDEA can be designed accordingly?  If the former, this puts a tremendous, and possibly unrealistic, burden on the components on the healthcare organization/EHR side to perform dynamically. We request that the expectations of the actors be more clearly defined, accounting for burden on sending system. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            kathleen.tully@hhs.gov Kathleen Tully
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: