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

Why do we mandate the use of library?

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • 1.0.0 [deprecated]
    • Clinical Decision Support
    • Retrieval of Payer Resources [deprecated]
    • Hide

      Change the following:
      "The DTR process SHALL use the URL provided in the cqf-library extension to retrieve the CQL necessary to execute the payer rules"

      To:
      "CQL can either be embedded inline as part of an expression or referenced in a library.  All libraries needed by a questionnaire SHALL be referenced by the cqf-library extension which SHALL be resolvable by the SMART app"

      Show
      Change the following: "The DTR process SHALL use the URL provided in the cqf-library extension to retrieve the CQL necessary to execute the payer rules" To: "CQL can either be embedded inline as part of an expression or referenced in a library.  All libraries needed by a questionnaire SHALL be referenced by the cqf-library extension which SHALL be resolvable by the SMART app"
    • Bob Dieterle / Ben Hamlin : 9-0-0
    • Clarification
    • Compatible, substantive

    Description

      Given that the questionnaire and logic will be tightly intertwined, what's the benefit of having the CQL in a separate library as opposed to embedded directly in the Expression elements?  At minimum, it should be possible for payers to embed the CQL directly in the Questionnaire if they wish.  It's architecturally simpler and cleaner for maintenance.

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: