Data Exchange For Quality Measures Implementation Guide
3.1.0 - STU 3.1.0 US

This page is part of the Da Vinci Data Exchange for Quality Measures (DEQM) FHIR IG (v3.1.0: STU 3) 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: Producer Server CapabilityStatement

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

This profile defines the expected capabilities of a Da Vinci DEQM Producer Server when conforming to the Da Vinci DEQM Implementation Guide. Producers include systems that are primary producers of patient healthcare information. This CapabilityStatement resource includes the complete list of the recommended Da Vinci DEQM profiles and RESTful operations that a Da Vinci DEQM Producer 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

ProducerServerCapabilityStatement

This profile defines the expected capabilities of a Da Vinci DEQM Producer Server when conforming to the Da Vinci DEQM Implementation Guide. Producers include systems that are primary producers of patient healthcare information. This CapabilityStatement resource includes the complete list of the recommended Da Vinci DEQM profiles and RESTful operations that a Da Vinci DEQM Producer 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 Collect 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:
  http://hl7.org/fhir/us/cqfmeasures/StructureDefinition/measure-cqfm		y