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. For a full list of available versions, see the Directory of published versions

CapabilityStatement: Consumer Server CapabilityStatement

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

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.

Raw OpenAPI-Swagger Definition file | Download

ConsumerServerCapabilityStatement

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.

ModeSERVER
Description

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.
Transactiony
System Historyy
System Searchy
Resource TypeProfileReadSearchUpdateCreate
MeasureSupported profiles:
  CQFM Measure		y