Data Exchange For Quality Measures STU3 for FHIR R4
2.1.0 - Ballot

This page is part of the Da Vinci Data Exchange for Quality Measures (DEQM) FHIR IG (v2.1.0: STU 3) based on FHIR R4. The current version which supercedes this version is 3.1.0. For a full list of available versions, see the Directory of published versions

CapabilityStatement: Gaps In Care Server CapabilityStatement

Raw OpenAPI-Swagger Definition file | Download

Gaps In Care Server CapabilityStatement

  • Implementation Guide Version: 2.1.0
  • FHIR Version: 4.0.1
  • Supported formats: xml, json
  • Published: 2020-07-05
  • Published by: HL7 International - Clinical Quality Information Work Group

This profile defines the expected capabilities of a Da Vinci DEQM Gaps In Care Server when conforming to the Da Vinci DEQM Implementation Guide for interactions between Clients and Servers to exchange the gaps in care reports for a measure. Servers are the actors receiving the gaps in care results of quality measure(s). This CapabilityStatement resource includes the complete list of the recommended Da Vinci DEQM profiles and RESTful operations that a Da Vinci DEQM Reporter Client 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 Gaps In Care Server SHALL

  1. Support the Gaps in Care Reporting transactions 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
    Measure care-gaps

    Measure

    Conformance Expectation: SHALL

    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]