Data Exchange For Quality Measures Implementation Guide
5.0.0-ballot - STU5 Ballot United States of America flag

This page is part of the Da Vinci Data Exchange for Quality Measures (DEQM) FHIR IG (v5.0.0-ballot: STU5 (v5.0.0) Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 4.0.0. For a full list of available versions, see the Directory of published versions

CapabilityStatement: Reporter Client CapabilityStatement

Official URL: http://hl7.org/fhir/us/davinci-deqm/CapabilityStatement/reporter-client Version: 5.0.0-ballot
Active as of 2020-07-05 Computable Name: ReporterClientCapabilityStatement
Other Identifiers: OID:2.16.840.1.113883.4.642.40.2.13.8

This profile defines the expected capabilities of a Da Vinci DEQM Reporter Client when conforming to the Da Vinci DEQM Implementation Guide. Reporters include systems that are primary reporters 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 Reporter Client could support. Clients 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 reporter-client

Reporter Client CapabilityStatement

  • Implementation Guide Version: 5.0.0-ballot
  • FHIR Version: 4.0.1
  • Supported Formats: xml, json
  • Supported Patch Formats: application/json-patch+json
  • Published on: 2020-07-05
  • 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: client

Da Vinci DEQM Producer Client SHALL support at least one of the following transactions defined in the Framework Section of this Implementation Guide:

  • Individual Reporting
  • Summary Reporting
Security

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

Summary of System-wide Interactions
  • SHALLSupports the transactioninteraction.
  • MAYSupports the batchinteraction.
  • MAYSupports the search-systeminteraction.
  • MAYSupports the history-systeminteraction.

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: SHALL MeasureReport

Core FHIR Resource
MeasureReport
Reference Policy
Interaction summary
  • SHALLsupport create.
  • SHOULDsupport update, 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 Reporter Client SHALL be capable of supporting at least one of the DEQM MeasureReport Profiles listed above and all the DEQM, CQFM and QI Core Profiles they reference.