This fragment is available on index.html
This publication includes IP covered under the following statements.
Type | Reference | Content |
---|---|---|
web | github.com |
![]() |
web | github.com | Common CQL Artifacts for FHIR (US-Based), published by HL7 International / Clinical Decision Support. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/us-cql-ig/ and changes regularly. See the Directory of published versions |
web | github.com | To address this, static analysis of the CQL can be used to determine the set of data requirements for an expression (or set of expressions), as described in the Artifact Data Requirements section of the CQL specification. The DataRequirementsProcessor provides an implementation of this capability. This component can accept a list of the expressions that should be analyzed to determine data requirements. |
web | github.com | Well-known Documentation Tags |
web | github.com | In particular, the publisher supports processing and validation of CQL libraries through Binary Adjunct Files . The source for these libraries can be edited alongside the other source for the rest of the IG, using tools such as the CQFramework CQL Plugin for Visual Studio Code . |
web | github.com | For a walkthrough of how to build and maintain a content implementation guide, refer to the Colorectal Cancer Screening Walkthrough . This walkthrough covers the creation of a content implementation guide that has a simple decision support and quality measure related to colorectal cancer screening. |
web | github.com |
Manually translate the PDF content into a FHIR Questionnaire (this can optionally be done first in FSH
format but ultimately must be present as an XML or JSON FHIR resource located at the path input/resources/questionnaire
). An example for the form in #1 can be found here
.
|
web | github.com |
Create a CQL file located at input/cql
and remember to name it the same as the end of the canonical URL defined in step #3. An example for the MNAC form can be found here
.
|
web | marketplace.visualstudio.com |
The CQL VS Code extension
allows for right-clicking Execute CQL
. To successfully investigate if a certain definition results in the desired output, some test resources need to be provided and located in a folder at the following path: input/tests/library/YOUR-CQL-LIBRARY-NAME
. Sub-folders can define multiple patients filled with multiple resource files. The MNAC test folder with resources of a Patient called example
can be found here
.
|
web | github.com |
The CQL VS Code extension
allows for right-clicking Execute CQL
. To successfully investigate if a certain definition results in the desired output, some test resources need to be provided and located in a folder at the following path: input/tests/library/YOUR-CQL-LIBRARY-NAME
. Sub-folders can define multiple patients filled with multiple resource files. The MNAC test folder with resources of a Patient called example
can be found here
.
|
web | github.com |
Start a local instance of the Clinical Reasoning enabled HAPI JPA Server Starter
(e.g. by using Docker) or use a publicly available FHIR server that supports CQL processing and the
SDC $populate operation
.
|
web | github.com |
Test and see if the operation $populate
for your questionnaire results in the expected initial values for each item. A complete sample Postman collection for a different Questionnaire can be found here
. This collection also contains automated tests to highlight what to look for.
|
web | github.com | In addition, testing artifacts are available in the form of test bundles, one for each questionnaire in the IG repository: Test Bundles |
web | www.iso.org |
ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
Show Usage
|
web | ucum.org |
The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
Show Usage
|
web | github.com | NOTE: Content for this page was adapted from the QICore Authoring Patterns - Allergies topic. |
web | github.com | NOTE: Content for this page was adapted from the QICore Authoring Patterns - Laboratory Result topic. |
web | github.com | NOTE: Content for this page was adapted from the QICore Authoring Patterns - Medications topic. |
web | docushare-web.apps.external.pioneer.humana.com | Almost all prior authorization forms contain a question about the urgency of the request. Different forms have different ways of expressing the same logic. E.g., the Humana Uniform Pharmacy Prior Authorization Request Form uses check boxes with the strings "Urgent" and "Non-Urgent". The form Geisinger Medical Benefit Outpatient Drug Authorization Form contains a categorization as "Urgent" more in a boolean logic with a required rationale if the request is labelled as "Urgent". |
web | www.geisinger.org | Almost all prior authorization forms contain a question about the urgency of the request. Different forms have different ways of expressing the same logic. E.g., the Humana Uniform Pharmacy Prior Authorization Request Form uses check boxes with the strings "Urgent" and "Non-Urgent". The form Geisinger Medical Benefit Outpatient Drug Authorization Form contains a categorization as "Urgent" more in a boolean logic with a required rationale if the request is labelled as "Urgent". |
web | github.com | NOTE: Content for this page was adapted from the QICore Authoring Patterns - Patient topic. |
web | github.com | NOTE: Content for this page was adapted from the QICore Authoring Patterns - Procedures topic. |
web | github.com | Compare those patterns with QI Core Authoring Patterns to see if we can align. |
web | github.com | User's Guide - Adding Test Data |
web | github.com | The DTR SMART on FHIR App has facilities for end-to-end testing of the DaVinci DTR questionnaire use case, including questionnaire population and EHR FHIR queries. |
web | github.com | (NOTE: These collections were tested against a HAPI JPA Server Starter instance using version 3.27.0 of the Clinical Reasoning module. They also include missing US Core 7.0.0 dependencies due to some technical limitations in the CQF Tooling used to construct the questionnaire bundles. Once those limitations have been removed that collection will no longer be required.) |
web | github.com | (NOTE: These collections were tested against a HAPI JPA Server Starter instance using version 3.27.0 of the Clinical Reasoning module. They also include missing US Core 7.0.0 dependencies due to some technical limitations in the CQF Tooling used to construct the questionnaire bundles. Once those limitations have been removed that collection will no longer be required.) |
web | github.com | Postman Collections |
web | github.com | Running the Quality Measure |
web | github.com | Measure Reporting Client |
web | github.com | Running the Decision Support |
web | provider.humana.com | Preauthorization and Notification Lists for Healthcare Providers - Humana |
Integration-Test-Scenarios.png ![]() |
dtr-data-flow.svg |