Data Exchange For Quality Measures STU2 for FHIR R4
2.0.0 - STU2 Release

This page is part of the Da Vinci Data Exchange for Quality Measures (DEQM) FHIR IG (v2.0.0: STU 2) 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: Consumer Server CapabilityStatement

Raw OpenAPI-Swagger Definition file | Download

Consumer Server CapabilityStatement

  • Implementation Guide Version: 2.0.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 Consumer Server when conforming to the Da Vinci DEQM Implementation Guide. Consumers include systems that are primary consumers of patient healthcare information and systems that consume data from Producers. This CapabilityStatement resource includes the complete list of the recommended Da Vinci DEQM profiles and RESTful operations that a Da Vinci DEQM Consumer 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 Consumer Server SHALL

  1. Support the Submit Data 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 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

  • 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 data-requirements, submit-data

    Measure

    Conformance Expectation: SHALL

    Supported Profiles: CQFM Measure

    Profile Interaction Summary:

    • SHOULD support read.

    Operation Summary:

    • SHALL support the $data-requirements operation , $submit-data operation

      SHALL Use the DEQM Submit Data Update Type Extension to indicate whether it whether it supports snapshot or incremental data exchange. SHALL reject the submit data payload if there is mismatch between the Consumer’s stated capabilities and the required modifier extension by returning a 400 Bad Request http error code. An OperationOutcome SHOULD be returned stating that the [snapshot/incremental] update is not supported .

    Fetch and Search Criteria:

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