Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

HL7 Updates

HL7 Ballots

  • CQF-on-FHIR IG is being published as the Clinical Reasoning Module as part of FHIR STU3
  • FHIR Quality Profiles (QI-Core) is being published as a US-Realm IG based on the US-Core profiles and targeting FHIR STU3
  • FluentPath has been renamed to FHIRPath for legal reasons and will be published as an STU
  • CDS WG is preparing an InfoButton IG based on the Clinical Reasoning Module for ballot in January
  • HQMF - Pending ANSI approval for normative status
  • CQL-Based HQMF IG - Finalizing examples and content based on additional feedback from review and terminology discussions
  • CQL - Currently applying ballot reconciliation changes to STU comments

...

CQF ONC Tech Lab projects will run as scenarios under the Clinical Reasoning Track at the upcoming HL7 FHIR Connectathon 14 in San Anotonio, TX

FHIR Connectathon 13 Results from HL7 WGM September, Baltimore, MD

CQF-on-FHIR

  • Affirmative- 38, Negative- 34, Abstain- 68, No Return- 44
  • Total- 184, Affirmatives Needed- 44
    • Committees agreed on the approach to service definition to simplify expression of decision support services
    • Committees agreed to a pilot implementation project based on a CDS Hooks use case (Zika is the current candidate) as an approach to explore CDS Hooks alignment
    • Committees (including Pharmacy) agreed to define DosageInstruction and potentially DispenseRequest types to support description of medication order templates using ActivityDefinition
    • Committees agreed to the use of Metadata data types to ensure consistency between metadata expressed on conformance resources and knowledge artifact resources
    • Committees agreed on the approach to RequestGroup to enable expression of optional request resources within a CarePlan

QI-Core

  • Affirmative- 58, Negative- 5, Abstain- 59, No Return- 36
  • Total- 158, Affirmatives Needed-38
    • Agreed to derive QI-Core from DAF directly, even if it means selecting bindings that are more restrictive than is desired in the long term. We will focus on supporting implementation initiatives, and revisit the binding issues if and when they are encountered at a later time.

FluentPath

  • Affirmative- 23, Negative- 19, Abstain- 50, No Return- 25
  • Total- 117, Affirmatives Needed-26
    • Clarified that the upcoming ballot of CQL will be backwards compatible with 1.1, and that it will not remove any CQL operators, only introduce the ability to use FluentPath expressions within CQL.
    • The name FluentPath has IP issues significant to prevent us from pursuing it as a trademark. The committee recommended returning to FHIRPath as the name now that the language has been published as a separate specification with the ability to operate on any data model.

...