This page is part of the Da Vinci Data Exchange for Quality Measures (DEQM) FHIR IG (v1.0.0: STU 1) based on FHIR R3. The current version which supercedes this version is 3.1.0. For a full list of available versions, see the Directory of published versions
Downloads: CapabilityStatement: (XML, JSON),OpenAPI-Swagger Definition file
DaVinci DEQM Producer Client CapabilityStatement
This profile defines the expected capabilities of a Da Vinci DEQM Producer Client 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 Client could support. Clients have the option of choosing from this list based on their local use cases and other contextual requirements.
- FHIR Version: 3.0.2
- Supported formats: xml, json
- Published: 2019-03-14
- Published by: The DaVinci Project
Implementation guides that SHOULD be supported:
FHIR RESTful Capabilities
Da Vinci DEQM Producer Client SHALL
- Support at least one transaction defined in the Framework Section of this Implementation Guide.
Security:
For general security consideration refer to the Security and Privacy Considerations.
RESTful Capabilities by Resource/Profile:
Summary of Operations
$submit-data
operation.$data-requirements
operation.Summary of Search Criteria
Resource Type | Supported Profiles | Supported Searches | Supported Includes |
---|---|---|---|
MeasureReport | DEQM Summary MeasureReport Profile, DEQM Data Exchange MeasureReport Profile, DEQM Individual MeasureReport Profile | ||
Library |
MeasureReport
Supported Profiles:
DEQM Summary MeasureReport Profile, DEQM Data Exchange MeasureReport Profile, DEQM Individual MeasureReport Profile
The DaVinci DEQM Producer Client SHOULD be capable of supporting the DEQM MeasureReport Profiles and all the DEQM and QI Core Profiles they reference.
Profile Interaction Summary:
- SHOULD support
create
.
Library
Profile Interaction Summary:
- SHOULD support
read
.
Fetch and Search Criteria:
-
A Client SHOULD be capable of fetching a Library resource using:
GET [base]/Library/[id]