Data Exchange For Quality Measures Implementation Guide
4.0.0 - STU4 United States of America

This page is part of the Da Vinci Data Exchange for Quality Measures (DEQM) FHIR IG (v4.0.0: STU4 (v4.0.0)) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

CapabilityStatement: Receiver Server CapabilityStatement

Official URL: http://hl7.org/fhir/us/davinci-deqm/CapabilityStatement/receiver-server Version: 4.0.0
Active as of 2020-07-05 Computable Name: ReceiverServerCapabilityStatement

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.

Raw OpenAPI-Swagger Definition file | Download

ReceiverServerCapabilityStatement

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.

ModeSERVER
Description

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.

Transactiony
System Historyy
System Searchy
Resource TypeProfileReadSearchUpdateCreateDelete
MeasureReportSupported profiles:
  DEQM Summary MeasureReport Profile
  DEQM Individual MeasureReport Profile		yyy