This fragment is available on en/downloads.html
This publication includes IP covered under the following statements.
| Type | Reference | Content |
|---|---|---|
| web | example.org | Information Source: http://example.org/fhir/server |
| web | example.org | module : http://example.org/radiology-appropriateness-guidelines.html |
| web | example.org | module : http://example.org/medication-adherence-guidelines.html |
| web | github.com | 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 1.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 |
| web | github.com | The bulk-submit-data operation sends a bulk import request based on the data requirements of a FHIR Measure. This operation is modeled off the existing draft of the Bulk Data Import Ping and Pull Approach . |
| web | github.com |
The request body for this operation is a FHIR Parameters Resource
. The body SHALL include a FHIR MeasureReport Resource of type data-collection
that references a measure by canonical URL. Additionally, the FHIR Parameters resource SHALL include the URL of a Data Provider, as defined in the Bulk Data Import Ping and Pull Approach
. The Data Provider SHALL support $export
. It is assumed that the data-of-interest for the measure referenced in the MeasureReport lives on the Data Provider server.
|
| web | en.wikipedia.org | Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS ). |
| web | wiki.ihe.net | This is a metadata field from XDS/MHD . |
| web | icf.atlassian.net | DEQM STU5 Final Publication: Build QA #1 (individual measure report errors)( CQF-2428 ) |
| web | icf.atlassian.net | DEQM STU5 Final Publication: Build QA #1 (individual measure report errors)( CQF-2428 )( Applied here ) |
| web | icf.atlassian.net | DEQM STU5 Final Publication: Address deqm-6 issue on SubjectList ( CQF-2611 ) Applied ( here ) |
| web | www.openinfobutton.org | Infobutton event listing |
| web | cds-hooks.org | CDS Hooks Hook definitions |
| web | hackmd.io | The Bulk Data Access IG provides workflows for Bulk Export and Bulk Submit (the latter expected to ballot in September 2026, currently in draft here ). DEQM endorses the Bulk Data Access IG as the method for bulk data exchange and it can be integrated into DEQM workflows. |
| web | ucum.org |
The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
Show Usage
|
| web | www.postman.com | The request below asks for Group id of 123 to be run asynchronously with FHIR+ndjson as the output format. The header portions should be entered in the API client header section. For example, in the Postman tool, enter “Prefer” in Key and “respond-async” in Value as an entry in the Headers tab. |
| web | hackmd.io | In each of the scenarios described in DEQM, the FHIR API can be used directly to access the data of interest for the measure being reported. However, to support large volumes of data, Bulk Data may be used to transfer the data of interest between the clinical data repository and the reporting system. As of the time of this publication, the Bulk Data specification is being updated to include important capabilities that will improve the performance of bulk data for the quality reporting use case, in particular the ability to organize bulk data feeds by subject. A future version of this publication will provide more detail on how this capability can be used directly once the updated Bulk Data specification is published (expected to ballot in September 2026, currently in draft here . |
| web | www.flaticon.com | Hospital icons created by Freepik - Flaticon |
|
../assets/images/001.svg |
COL Worklow Diagram - Data Exchange Indiv collect-data.jpg
|
COL Worklow Diagram - Data Exchange Indiv submit-data.jpg
|
DEQM Resource Diagram - VTE1.jpg
|
DEQM Resource Diagram - VTE2.jpg
|
DEQM Resource Diagram - VTE3.jpg
|
DEQM Resource Diagram - VTE4.jpg
|
DEQM Resource Diagram - VTE5.jpg
|
DEQM Resource Diagram - VTE6.jpg
|
DEQM Resource Diagram - VTE7.jpg
|
MRP_Technical_Workflow.jpg
|
clinicalreasoning-measure-report-patient-list.png
|
clinicalreasoning-qi-ecosystem.png
|
col-option1-using-observation.png
|
col-option2-using-diagnostic-report.png
|
col-option3-using-procedure.png
|
col-option4-using-condition.png
|
col_indv_report.jpg
|
col_summ_report.jpg
|
collect-data-steps.jpg
|
collect-data.jpg
|
data-model-standards-landscape.png
|
data-requirement.jpg
|
gaps-reporting-scenario.png
|
gaps-swimlane-caregap-report.png
|
gic-bundle-structure-edit.png
|
gic-care-gaps-operation-group.png
|
gic-care-gaps-operation-single-patient.png
|
gic-colonoscopy-example-pt1-step1-open-gap.png
|
gic-colonoscopy-example-pt1-step3-gap-closed.png
|
gic-colonoscopy-example-pt2-step1-no-gap.png
|
gic-colonoscopy-example-pt3-step1-prospective-gap.png
|
gic-colonoscopy-example-pt3-step3-prospective-gap-closed.png
|
gic-ecosystem_new.png
|
gic-prospective-retrospective.png
|
gic-reporting-flow.png
|
gic-resources.png
|
indv_report_post.jpg
|
measure-resource-graph.jpg
|
mrp-observation.png
|
mrp-task.png
|
mrp_indv_report.jpg
|
mrp_summ_report.jpg
|
quality-measurement-standards-landscape.png
|
quality-reporting-exchange-scenarios.png
|
quality-reporting-exchange-scope.png
|
quality-reporting-overview.png
|
quality-reporting-reporting-scenarios.png
|
submit-data-step.jpg
|
submit-data.jpg
|
summ_report_post.jpg
|
tree-filter.png
|
vte_indv_report.jpg
|