Data Exchange For Quality Measures Implementation Guide, published by HL7 International / Clinical Quality Information. This guide is not an authorized publication; it is the continuous build for version 5.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-deqm/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/us/davinci-deqm/CapabilityStatement/receiver-server | Version: 5.0.0-ballot | |||
Active as of 2020-07-05 | Computable Name: ReceiverServerCapabilityStatement | |||
Other Identifiers: OID:2.16.840.1.113883.4.642.40.2.13.7 |
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
Generated Narrative: CapabilityStatement receiver-server
xml
, json
application/json-patch+json
Note to Implementers: FHIR Capabilities
Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.
server
Da Vinci DEQM Producer Server SHALL
Support the following transactions defined in the Framework Section of this Implementation Guide:
Declare a CapabilityStatement identifying the list of supported profiles and operations.
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 .
Support both xml and json resource formats for all interactions.
For general security consideration refer to the Security and Privacy Considerations.
transaction
interaction.batch
interaction.search-system
interaction.history-system
interaction.The summary table lists the resources that are part of this configuration, and for each resource it lists:
_include
_revinclude
Resource Type | Profile | R | S | U | C | D | Searches | _include | _revinclude | Operations |
---|---|---|---|---|---|---|---|---|---|---|
MeasureReport | Supported Profiles DEQM Summary MeasureReport Profile DEQM Individual MeasureReport Profile | y | y | y |
create
, update
.delete
.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.