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

Replace CQL Library profile with SDC Library profile

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Clinical Decision Support
    • Library
    • (profiles)
    • Hide

      To align this with the SDC and CPG efforts, we will:

      1. Pull in the cpg-knowledgeCapability and cpg-knowledgeRepresentationLevel extensions and add them as 0..* elements on the ShareableLibrary
      2. Pull in the CPGComputableLibrary, CPGPublishableLibrary, and CPGExecutableLibrary profiles, deriving them from ShareableLibrary and dropping the CPG prefix
      3. Add the fhirpath and x-fhir-query content slices to the resulting ComputableLibrary profile, but expand their cardinality to 0..*
      4. Add language to the profile to say that if it includes CQL and FHIRPath/xFHIRQuery content, they SHALL represent the same expressions
      5. In the R5 CPG/SDC, they would be able to use these profiles directly, rather than defining Library profiles
      6. Update the CQLComputableLibrary profile to derive from Computable and only allow the CQLContent slice (and require it)

      Note explicitly we are leaving the problem of referencing multiple FHIRPath/xFHIRQuery expressions out of scope for this, needs another tracker to resolve.

      Show
      To align this with the SDC and CPG efforts, we will: Pull in the cpg-knowledgeCapability and cpg-knowledgeRepresentationLevel extensions and add them as 0..* elements on the ShareableLibrary Pull in the CPGComputableLibrary, CPGPublishableLibrary, and CPGExecutableLibrary profiles, deriving them from ShareableLibrary and dropping the CPG prefix Add the fhirpath and x-fhir-query content slices to the resulting ComputableLibrary profile, but expand their cardinality to 0..* Add language to the profile to say that if it includes CQL and FHIRPath/xFHIRQuery content, they SHALL represent the same expressions In the R5 CPG/SDC, they would be able to use these profiles directly, rather than defining Library profiles Update the CQLComputableLibrary profile to derive from Computable and only allow the CQLContent slice (and require it) Note explicitly we are leaving the problem of referencing multiple FHIRPath/xFHIRQuery expressions out of scope for this, needs another tracker to resolve.
    • Rob Hausam/Matthew Burton: 18-0-0
    • Enhancement
    • Non-compatible
    • R5

    Description

      As suggested in FHIR-21340, replace the existing CQL Library profile with the new SDC Library profile that also supports FHIRPath and FHIR query.

      Attachments

        Activity

          People

            bryn.rhodes Bryn Rhodes
            joeegarcia Josephine Garcia (Inactive)
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: