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: Receiver Server CapabilityStatement

Raw OpenAPI-Swagger Definition file | Download

Receiver 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 Receiver Server when conforming to the Da Vinci DEQM Implementation Guide. Receivers include systems that are primary receivers of Measure data such as payers as well as public health and other healthcare-related agencies. This CapabilityStatement resource includes the complete list of the recommended Da Vinci DEQM profiles and RESTful operations that a Da Vinci DEQM Receiver 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 the following transactions defined in the Framework Section of this Implementation Guide:

    • Individual Reporting
    • Summary Reporting

  2. Declare a CapabilityStatement identifying the list of supported profiles and operations.

  3. Implement the FHIR RESTful API for operations including returning the appropriate response classes as described in the FHIR specification for Extended Operations on the 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

  • SHOULD 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
    MeasureReportDEQM Summary MeasureReport Profile, DEQM Individual MeasureReport Profile

    MeasureReport

    Conformance Expectation: SHALL

    Supported Profiles: DEQM Summary MeasureReport Profile, DEQM Individual MeasureReport Profile

    Resource Specific Documentation:

    The DaVinci DEQM Receiver Server SHALL be capable of supporting the DEQM Summary MeasureReport Profile and DEQM Individual MeasureReport Profile and all the DEQM and QI Core Profiles they reference.

    Profile Interaction Summary:

    • SHALL support create, update.
    • SHOULD support delete.

    Fetch and Search Criteria: