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

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 4.0.0 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

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

Receiver Server CapabilityStatement

  • Implementation Guide Version: 4.0.0
  • FHIR Version: 4.0.1
  • Supported Formats: xml, json
  • Supported Patch Formats: application/json-patch+json
  • Published on: Sun Jul 05 00:00:00 UTC 2020
  • Published by: HL7 International / Clinical Quality Information

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.

SHALL Support the Following Implementation Guides

FHIR RESTful Capabilities

Mode: server

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.

Security

For general security consideration refer to the Security and Privacy Considerations.

Summary of System-wide Interactions
  • SHOULD support the transaction interaction.
  • MAY support the batch interaction.
  • MAY support the search-system interaction.
  • MAY support the history-system interaction.

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Resource TypeProfileRSUCDSearches_include_revincludeOperations
MeasureReportSupported profiles:
  DEQM Summary MeasureReport Profile
  DEQM Individual MeasureReport Profile		yyy

Resource Conformance: SHALLMeasureReport

Core FHIR Resource
MeasureReport
Reference Policy
Interaction summary
  • SHALL support create, update.
  • SHOULD support delete.

Supported Profiles

http://hl7.org/fhir/us/davinci-deqm/StructureDefinition/summary-measurereport-deqm
http://hl7.org/fhir/us/davinci-deqm/StructureDefinition/indv-measurereport-deqm

Documentation

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.