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: Gaps In Care Server CapabilityStatement

Official URL: http://hl7.org/fhir/us/davinci-deqm/CapabilityStatement/gic-server Version: 4.0.0
Active as of 2021-04-23 Computable Name: GapsInCareServerCapabilityStatement

This profile defines the expected capabilities of a Da Vinci DEQM Gaps In Care Server when conforming to the Da Vinci DEQM Implementation Guide for interactions between Clients and Servers to exchange the Gaps in Care Reports for a measure. Servers are the actors receiving the request for Gaps in Care Reports for quality measure(s). This CapabilityStatement resource includes the complete list of the recommended Da Vinci DEQM profiles and RESTful operations that a Gaps In Care 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

GapsInCareServerCapabilityStatement

This profile defines the expected capabilities of a Da Vinci DEQM Gaps In Care Server when conforming to the Da Vinci DEQM Implementation Guide for interactions between Clients and Servers to exchange the Gaps in Care Reports for a measure. Servers are the actors receiving the request for Gaps in Care Reports for quality measure(s). This CapabilityStatement resource includes the complete list of the recommended Da Vinci DEQM profiles and RESTful operations that a Gaps In Care 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 Gaps In Care Server SHALL

  1. Support the Gaps in Care Reporting transactions defined in the Framework Section of this Implementation Guide.
  2. Declare a CapabilityStatement identifying the list of supported profiles and operations.
  3. Implement the RESTful behavior according to the FHIR specification including returning the appropriate response classes as described in the FHIR specification for FHIR RESTful API.
  4. Support both xml and json resource formats for all interactions.
Transactiony
System Historyy
System Searchy
Resource TypeProfileReadSearchUpdateCreate
Measure y
MeasureReportSupported profiles:
  DEQM Individual MeasureReport Profile		y
BundleSupported profiles:
  DEQM Gaps In Care Bundle		y