Where does data come from? - DTR #57

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • US Da Vinci DTR (FHIR)
    • STU3
    • Clinical Decision Support
    • (profiles) [deprecated]
    • CQL
    • Hide

      Will update the description and diagrams to clarify that CQL execution uses the FHIR APIs to access data in the EHR.

      Show
      Will update the description and diagrams to clarify that CQL execution uses the FHIR APIs to access data in the EHR.
    • Bob Dieterle / Floyd Eisenberg: 9-0-3
    • Clarification
    • Non-substantive

      Existing Wording: The DTR application will examine the payer supplied Questionnaire resource. This resource SHALL conform to the CQF Questionnaire Profile when using FHIR R4 or CQIF Questionnaire Profile when using FHIR STU3. The DTR application will examine each Questionnaire.item to find a valueExpression (FHIR R4) or cqif-calculatedValue. The DTR application will then use the statement identifier to retrieve a value from CQL execution. The resulting value is used to satisfy documentation requirements. If the value is null, the user will be prompted to supply a value.

      Comment:

      I'm definitely not a CQL expert. It seems like this explanation of how the DTR app should behave should also mention how the app actually gets the data used to automatically satisfy each CQL valueExpression. This sentence in particular: "The DTR application will then use the statement identifier to retrieve a value from CQL execution." seems like it should mention that the app is actually making RESTful FHIR queries against the EHR's FHIR server. Is that implied within the term "CQL execution"? If so, it's not apparent to a non-expert and should be explicitly called out.

      Summary:

      Where does data come from?

            Assignee:
            Unassigned
            Reporter:
            Michael Clifton
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: