Data Exchange For Quality Measures STU2 for FHIR R4 Implementation Guide CI Build

Data Exchange For Quality Measures STU2 for FHIR R4, published by HL7 International - Clinical Quality Information Work Group. This is not an authorized publication; it is the continuous build for version 1.1.1). This version is based on the current content of https://github.com/HL7/davinci-deqm/ and changes regularly. See the Directory of published versions

Downloads: CapabilityStatement: (XML, JSON),OpenAPI-Swagger Definition file

Producer Server CapabilityStatement

  • Implementation Guide Version: 1.1.0
  • FHIR Version: 4.0.1
  • Supported formats: xml, json
  • Published: 2019-10-22
  • Published by: HL7 International - Clinical Decision Support Work Group

This profile defines the expected capabilities of a Da Vinci DEQM Producer Server when conforming to the Da Vinci DEQM Implementation Guide. Producers include systems that are primary producers of patient healthcare information. This CapabilityStatement resource includes the complete list of the recommended Da Vinci DEQM profiles and RESTful operations that a Da Vinci DEQM Producer Server could support. Servers have the option of choosing from this list based on their local use cases and other contextual requirements.

SHALL Support the Following Implementation Guides:

FHIR RESTful Capabilities

Da Vinci DEQM Producer Server SHALL

  1. Support at least one transaction defined in the Framework Section of this Implementation Guide.
  2. Declare a CapabilityStatement identifying the list of supported profiles and operations.
  3. Implement the RESTful behavior according to the FHIR specification including returning the appropriate response classes as described in the FHIR specification for FHIR RESTful API.
  4. Support both xml and json resource formats for all interactions.

Security:

For general security consideration refer to the Security and Privacy Considerations.

Summary of System Wide Interactions

  • MAY support the transaction interaction.
  • MAY support the batch interaction.
  • MAY support the search-system interaction.
  • MAY support the history-system interaction.
  • RESTful Capabilities by Resource/Profile:

    Summary of Search Criteria

    Resource TypeSupported ProfilesSupported SearchesSupported _includesSupported _revincludesSupported Operations
    MeasureCQFM Measure $collect-data

    Measure

    Supported Profiles: CQFM Measure

    Profile Interaction Summary:

    • SHOULD support read.

    Operation Summary:

    Fetch and Search Criteria:

    • A Server SHOULD be capable of returning a Measure resource using:
      GET [base]/Measure/[id]