Make version of schema used for knowledge representation independent of version/profiles of patient data used by the knowledge - CPG #68

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • Clinical Guidelines (FHIR)
    • STU3
    • Clinical Decision Support
    • (NA)
    • Hide

      Agreed, provide guidance on using different models and provide:

      1) An extension in the knowledge resources to indicate the target model of the knowledge artifact (for libraries, you could infer this by peeking in the CQL).

      2) An extension in the Library to allow identification of data types of the target model in the data requirements.

      3) Extensions on any resource-specific touchpoints within the knowledge artifact (ActivityDefinitions, PlanDefinitions, Measures) to allow reference to data types of the target model.

       

      Show
      Agreed, provide guidance on using different models and provide: 1) An extension in the knowledge resources to indicate the target model of the knowledge artifact (for libraries, you could infer this by peeking in the CQL). 2) An extension in the Library to allow identification of data types of the target model in the data requirements. 3) Extensions on any resource-specific touchpoints within the knowledge artifact (ActivityDefinitions, PlanDefinitions, Measures) to allow reference to data types of the target model.  
    • Chris Moesel/Rob Samples: 18-0-2
    • Enhancement
    • Compatible, substantive

      Comment:

      Recommend making the knowledge representation FHIR version independent of the underlying data version. I.e., that an R4-based representation of a clinical guideline could be used to execute on data from R4, STU3, DSTU2, etc., and also with QICore FHIR profiles, or EHR vendor A's profiles, or USCore FHIR profiles, etc., in each version of FHIR. Otherwise, copies of the knowledge resource would need to be created for each version of FHIR, and/or each flavor/profile of FHIR within that version. Perhaps a given knowledge resource could work against multiple FHIR versions, or a logical model that can span multiple versions of FHIR.

      Summary:

      Make version of schema used for knowledge representation independent of version/profiles of patient data used by the knowledge

            Assignee:
            Unassigned
            Reporter:
            Kensaku Kawamoto
            Kensaku Kawamoto
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: