Are non-FHIR data models allowed?

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • Clinical Guidelines (FHIR)
    • STU3
    • Clinical Decision Support
    • Profile Definitions and Documentation
    • Hide

      You are correct, we do not currently limit usage to FHIR models, and we probably should, but we do have experience actually packaging these types of artifacts in FHIR but referencing other models (QDM, specifically), and we didn't want to preclude the ability to do that necessarily. We do need to define some additional extensions to support it fully, and we will add some documentation around supporting different versions of FHIR, as well as non-FHIR models using these patterns.

      Show
      You are correct, we do not currently limit usage to FHIR models, and we probably should, but we do have experience actually packaging these types of artifacts in FHIR but referencing other models (QDM, specifically), and we didn't want to preclude the ability to do that necessarily. We do need to define some additional extensions to support it fully, and we will add some documentation around supporting different versions of FHIR, as well as non-FHIR models using these patterns.
    • Bob Dieterle/Floyd Eisenberg: 9-0-2
    • Enhancement
    • Compatible, substantive

      In the Data Model section of the "Using Libraries" documentation, it says:

      "CQL can be used with any data model. In the context of a given computable artifact, any referenced CQL library SHALL identify the data model with a using declaration that includes a version specifier."

      There is nothing restricting data model to FHIR or something based on FHIR. Is this intentional? It seems that if data requirements must be specified as FHIR profiles, then maybe the CQL model should be FHIR-based? Or are you intentionally allowing for authors to use a different model that implementors must translate to/from FHIR?

            Assignee:
            Unassigned
            Reporter:
            cmoesel
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: