This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Intervention (QDM)"

From HL7Wiki
Jump to navigation Jump to search
 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
[http://wiki.hl7.org/index.php?title=Harmonization_of_Health_Quality_Information_models Back to Harmonization of Health Quality Information Models Page]<br>
 
[http://wiki.hl7.org/index.php?title=Harmonization_of_Health_Quality_Information_models Back to Harmonization of Health Quality Information Models Page]<br>
 
__FORCETOC__
 
__FORCETOC__
−
The CQI Workgroup reviewed this page in April 2018 consistent with QDM version 5.3. There are no updates to the content required based on QDM version 5.4 (reviewed June 7, 2018). Note that while the QDM categories Intervention and Procedure are modeled identically and interoperability standards do not differentiate between them, both are retained in the QDM as they are more clinically expressive for clinicians to understand the measure intent.<br><br>
+
The CQI Workgroup reviewed this page in April 2018 consistent with QDM version 5.3. There are no updates to the content required based on QDM version 5.4 (reviewed June 7, 2018); however, on June 15, 2018, the CQI Workgroup reviewed the QDM FHIR mappings for Intervention and determined there is some ambiguity requiring implementer comment.
 +
* Note that while the QDM categories Intervention and Procedure have been modeled identically in previous versions of QI Core, the [http://hl7.org/fhir/task.html FHIR Task Resource] provides a potentially more effective way to differentiate Interventions from Procedures. Both are retained in the QDM as they are more clinically expressive for clinicians to understand the measure intent.
 +
* The QDM to FHIR mapping provided here show mapping to both Procedure/ProcedureRequest and to Task.
 +
* The FHIR resource definitions for [http://build.fhir.org/procedure.html Procedure] and [http://build.fhir.org/task.html Task] seem to have significant overlap - see [https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=17359&start=50 FHIR Tracker item 17359]
 +
* Both mappings (i.e., Intervention mapped to Procedure/ProcedureRequest and to Task) are shown here. Comments are welcome regarding the most appropriate use.<br><br>
 
QDM defines Intervention as a course of action intended to achieve a result in the care of persons with health problems that does not involve direct physical contact with a patient. Examples include patient education and therapeutic communication. QDM defines three contexts for intervention: Intervention, Order; Intervention, Performed; Intervention, Recommended.
 
QDM defines Intervention as a course of action intended to achieve a result in the care of persons with health problems that does not involve direct physical contact with a patient. Examples include patient education and therapeutic communication. QDM defines three contexts for intervention: Intervention, Order; Intervention, Performed; Intervention, Recommended.
  
  
−
==Intervention, Order==
+
=='''''Intervention, Order [Using ProcedureRequest]'''==
  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
Line 26: Line 30:
 
|-
 
|-
 
| row2cell1 | Author dateTime
 
| row2cell1 | Author dateTime
−
| row2cell2 | ProcedureRequest.AuthoredOn
+
| row2cell2 | ProcedureRequest.authoredOn
−
| row2cell3 | Note - ProcedureRequest.occurrence(x) defines a dateTime when the event should occur - not addressed in QDM
+
| row2cell3 | Note - ProcedureRequest.occurrence[x] defines a dateTime when the event should occur - not addressed in QDM<br>
 +
Note: FHIR Provenance generally addresses the author of the message; the identifier/source of the original resource element is defined by the resource. Individual resource element provenance is summarized in the FHIR W5 Report (http://hl7.org/fhir/w5.html).
 
|-
 
|-
 
| row2cell1 | Code
 
| row2cell1 | Code
Line 41: Line 46:
 
| row2cell3 | Author, orderer - note also, ProcedureRequest.requester.agent for device, practitioner or organization who initiated the request; or ProcedureRequest.requester.onBehalfOf  - the organization the device or practitioner was acting on behalf of
 
| row2cell3 | Author, orderer - note also, ProcedureRequest.requester.agent for device, practitioner or organization who initiated the request; or ProcedureRequest.requester.onBehalfOf  - the organization the device or practitioner was acting on behalf of
 
|}
 
|}
−
==Intervention, Recommended==
+
 
 +
=='''''Intervention, Recommended [Using ProcedureRequest]'''==
  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
Line 62: Line 68:
 
|-
 
|-
 
| row2cell1 | Author dateTime
 
| row2cell1 | Author dateTime
−
| row2cell2 | ProcedureRequest.AuthoredOn
+
| row2cell2 | ProcedureRequest.authoredOn
−
| row2cell3 | Note - ProcedureRequest.occurrence(x) defines a dateTime when the event should occur - not addressed in QDM
+
| row2cell3 | Note - ProcedureRequest.occurrence[x] defines a dateTime when the event should occur - not addressed in QDM<br>
 +
Note: FHIR Provenance generally addresses the author of the message; the identifier/source of the original resource element is defined by the resource. Individual resource element provenance is summarized in the FHIR W5 Report (http://hl7.org/fhir/w5.html).
 
|-
 
|-
 
| row2cell1 | Code
 
| row2cell1 | Code
Line 77: Line 84:
 
| row2cell3 | Author, orderer - note also, ProcedureRequest.requester.agent for device, practitioner or organization who initiated the request; or ProcedureRequest.requester.onBehalfOf  - the organization the device or practitioner was acting on behalf of
 
| row2cell3 | Author, orderer - note also, ProcedureRequest.requester.agent for device, practitioner or organization who initiated the request; or ProcedureRequest.requester.onBehalfOf  - the organization the device or practitioner was acting on behalf of
 
|}
 
|}
−
==Intervention, Performed==
+
 
 +
=='''''Intervention, Performed [Using Procedure]'''==
  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
Line 107: Line 115:
 
| row3cell1 | Author dateTime
 
| row3cell1 | Author dateTime
 
| row3cell2 | FHIR.provenance.recorded
 
| row3cell2 | FHIR.provenance.recorded
−
| row3cell3 | FHIR references authorDatetime as part of the provenance resource for all resources. Is authorDatetime still appropriate for this datatype?
+
| row3cell3 | FHIR references authorDatetime as part of the provenance resource for all resources. Note: FHIR Provenance generally addresses the author of the message; the identifier/source of the original resource element is defined by the resource. Individual resource element provenance is summarized in the FHIR W5 Report (http://hl7.org/fhir/w5.html). Hence, the QDM Procedure author dateTime references FHIR provenance.
 
|-
 
|-
 
| row3cell1 | Status
 
| row3cell1 | Status
 
| row3cell2 | Procedure.status
 
| row3cell2 | Procedure.status
−
| row3cell3 | QDM matched to QI Core / FHIR
+
| row3cell3 | QDM matched to QI Core / FHIR<br>
 +
Note: Procedure.status allows specification of completed but it does not assure the procedure was completed successfully. The FHIR resource Proecedure.outcome does also specification of successful completion, but that element may be ambiguous. The Patient Care Workgroup is evaluating options to more clearly represent a procedure that successfully achieved its objective (objective is not currently available as a metadata element). Moreover, clinical care capture of success with respect to procedure completion is highly variable. See the QDM Known Issues for a description of the issue and a link to the ONC Jira QDM Issues page to join the discussion for QDM [https://github.com/esacinc/CQL-Formatting-and-Usage-Wiki/wiki/eCQM-Known-Issues#qdm-procedure-performed-completion-time].
 
|-
 
|-
 
| row8cell1 | Code
 
| row8cell1 | Code
Line 125: Line 134:
 
| row14cell3 | QDM matched to QI Core / FHIR
 
| row14cell3 | QDM matched to QI Core / FHIR
 
|}
 
|}
 +
 
=='''''Intervention, Order [Using Task]'''''==
 
=='''''Intervention, Order [Using Task]'''''==
  
Line 138: Line 148:
 
|-
 
|-
 
| row2cell1 | Negation Rationale
 
| row2cell1 | Negation Rationale
−
| row2cell2 | .
+
| row2cell2 | Task.statusReason
−
| row2cell3 | FHIR Task Resource does not address notDoneReason
+
| row2cell3 | QDM matched to QI Core/FHIR - Constrained to instances in which Task.status = rejected, cancelled, or failed [http://hl7.org/fhir/task-status Task status value set (required)]
 
|-
 
|-
 
| row2cell1 | Reason
 
| row2cell1 | Reason
Line 146: Line 156:
 
|-
 
|-
 
| row2cell1 | Author dateTime
 
| row2cell1 | Author dateTime
−
| row2cell2 | Task.AuthoredOn
+
| row2cell2 | Task.authoredOn
−
| row2cell3 | QDM matched to QI Core / FHIR
+
| row2cell3 | QDM matched to QI Core / FHIR<br>
 +
Note: FHIR Provenance generally addresses the author of the message; the identifier/source of the original resource element is defined by the resource. Individual resource element provenance is summarized in the FHIR W5 Report (http://hl7.org/fhir/w5.html).
 
|-
 
|-
 
| row2cell1 | Code
 
| row2cell1 | Code
Line 161: Line 172:
 
| row2cell3 | Task also provides the opportunity to request Task.owner (the person responsible for the task) and task.performerType
 
| row2cell3 | Task also provides the opportunity to request Task.owner (the person responsible for the task) and task.performerType
 
|}
 
|}
 +
 
=='''''Intervention, Recommended [Using Task]'''''==
 
=='''''Intervention, Recommended [Using Task]'''''==
  
Line 174: Line 186:
 
|-
 
|-
 
| row2cell1 | Negation Rationale
 
| row2cell1 | Negation Rationale
−
| row2cell2 | .
+
| row2cell2 | | row2cell2 | Task.statusReason
−
| row2cell3 | FHIR Task Resource does not address notDoneReason
+
| row2cell3 | QDM matched to QI Core/FHIR - Constrained to instances in which Task.status = rejected, cancelled, or failed [http://hl7.org/fhir/task-status Task status value set (required)]
 
|-
 
|-
 
| row2cell1 | Reason
 
| row2cell1 | Reason
Line 182: Line 194:
 
|-
 
|-
 
| row2cell1 | Author dateTime
 
| row2cell1 | Author dateTime
−
| row2cell2 | Task.AuthoredOn
+
| row2cell2 | Task.authoredOn
−
| row2cell3 | QDM matched to QI Core / FHIR
+
| row2cell3 | QDM matched to QI Core / FHIR<br>
 +
Note: FHIR Provenance generally addresses the author of the message; the identifier/source of the original resource element is defined by the resource. Individual resource element provenance is summarized in the FHIR W5 Report (http://hl7.org/fhir/w5.html).
 
|-
 
|-
 
| row2cell1 | Code
 
| row2cell1 | Code
Line 197: Line 210:
 
| row2cell3 | Task also provides the opportunity to request Task.owner (the person responsible for the task) and task.performerType
 
| row2cell3 | Task also provides the opportunity to request Task.owner (the person responsible for the task) and task.performerType
 
|}
 
|}
 +
 
=='''''Intervention, Performed [Using Task]'''''==
 
=='''''Intervention, Performed [Using Task]'''''==
  
Line 214: Line 228:
 
|-
 
|-
 
| row3cell1 | Negation Rationale
 
| row3cell1 | Negation Rationale
−
| row3cell2 | .
+
| row3cell2 | Task.statusReason
−
| row3cell3 | FHIR Task Resource does not address notDoneReason
+
| row2cell3 | QDM matched to QI Core/FHIR - Constrained to instances in which Task.status = rejected, cancelled, or failed [http://hl7.org/fhir/task-status Task status value set (required)]
 
|-
 
|-
 
| row3cell1 | Reason
 
| row3cell1 | Reason
Line 222: Line 236:
 
|-
 
|-
 
| row3cell1 | Result
 
| row3cell1 | Result
−
| row3cell2 | Task.businessStatus
+
| row3cell2 | Task.output.value[x]
 
| row3cell3 | QDM matched to QI Core / FHIR
 
| row3cell3 | QDM matched to QI Core / FHIR
 
|-
 
|-
 
| row3cell1 | Author dateTime
 
| row3cell1 | Author dateTime
 
| row3cell2 | Task.authoredOn
 
| row3cell2 | Task.authoredOn
−
| row3cell3 | QDM matched to QI Core / FHIR
+
| row3cell3 | QDM matched to QI Core / FHIR<br>
 +
Note: FHIR Provenance generally addresses the author of the message; the identifier/source of the original resource element is defined by the resource. Individual resource element provenance is summarized in the FHIR W5 Report (http://hl7.org/fhir/w5.html).
 
|-
 
|-
 
| row3cell1 | Status
 
| row3cell1 | Status

Latest revision as of 04:15, 28 November 2018

Back to Harmonization of Health Quality Information Models Page

The CQI Workgroup reviewed this page in April 2018 consistent with QDM version 5.3. There are no updates to the content required based on QDM version 5.4 (reviewed June 7, 2018); however, on June 15, 2018, the CQI Workgroup reviewed the QDM FHIR mappings for Intervention and determined there is some ambiguity requiring implementer comment.

  • Note that while the QDM categories Intervention and Procedure have been modeled identically in previous versions of QI Core, the FHIR Task Resource provides a potentially more effective way to differentiate Interventions from Procedures. Both are retained in the QDM as they are more clinically expressive for clinicians to understand the measure intent.
  • The QDM to FHIR mapping provided here show mapping to both Procedure/ProcedureRequest and to Task.
  • The FHIR resource definitions for Procedure and Task seem to have significant overlap - see FHIR Tracker item 17359
  • Both mappings (i.e., Intervention mapped to Procedure/ProcedureRequest and to Task) are shown here. Comments are welcome regarding the most appropriate use.

QDM defines Intervention as a course of action intended to achieve a result in the care of persons with health problems that does not involve direct physical contact with a patient. Examples include patient education and therapeutic communication. QDM defines three contexts for intervention: Intervention, Order; Intervention, Performed; Intervention, Recommended.


Intervention, Order [Using ProcedureRequest]

QDM Attribute QI Core Metadata Element Comment
Intervention, Order ProcedureRequest.intent Procedure Request intent uses the concepts proposal, plan, order, original-order, reflex-order, filler-order, instance-order, option. Constrain to "order" from the intent value set for QDM datatypes with the order context.
Negation Rationale ProcedureRequest.extension (http://hl7.org/fhir/StructureDefinition/procedurerequest-reasonRefused) QDM matched to QI Core / FHIR
Reason ProcedureRequest.reasonCode QDM matched to QI Core / FHIR
Author dateTime ProcedureRequest.authoredOn Note - ProcedureRequest.occurrence[x] defines a dateTime when the event should occur - not addressed in QDM

Note: FHIR Provenance generally addresses the author of the message; the identifier/source of the original resource element is defined by the resource. Individual resource element provenance is summarized in the FHIR W5 Report (http://hl7.org/fhir/w5.html).

Code ProcedureRequest.code QDM matched to QI Core / FHIR
id ProcedureRequest.id QDM matched to QI Core / FHIR
Source ProcedureRequest.requester Author, orderer - note also, ProcedureRequest.requester.agent for device, practitioner or organization who initiated the request; or ProcedureRequest.requester.onBehalfOf - the organization the device or practitioner was acting on behalf of

Intervention, Recommended [Using ProcedureRequest]

QDM Attribute QI Core Metadata Element Comment
Intervention, Recommended ProcedureRequest.intent Procedure Request intent uses the concepts proposal, plan, order, original-order, reflex-order, filler-order, instance-order, option. "Proposal" is most consistent with the ProcedureRequest when applied to clinical decision support (CDS) in which the CDS proposes an action to a provider or to a patient. The QDM concept Recommended addresses expectations a provider gives to a patient. Such recommendations are most consistent with the ProcedureRequest.intent value of "plan" (an intension to ensure something occurs without providing an authorization to act).
Negation Rationale ProcedureRequest.extension (http://hl7.org/fhir/StructureDefinition/procedurerequest-reasonRefused) QDM matched to QI Core / FHIR
Reason ProcedureRequest.reasonCode QDM matched to QI Core / FHIR
Author dateTime ProcedureRequest.authoredOn Note - ProcedureRequest.occurrence[x] defines a dateTime when the event should occur - not addressed in QDM

Note: FHIR Provenance generally addresses the author of the message; the identifier/source of the original resource element is defined by the resource. Individual resource element provenance is summarized in the FHIR W5 Report (http://hl7.org/fhir/w5.html).

Code ProcedureRequest.code QDM matched to QI Core / FHIR
id ProcedureRequest.id QDM matched to QI Core / FHIR
Source ProcedureRequest.requester Author, orderer - note also, ProcedureRequest.requester.agent for device, practitioner or organization who initiated the request; or ProcedureRequest.requester.onBehalfOf - the organization the device or practitioner was acting on behalf of

Intervention, Performed [Using Procedure]

QDM Attribute QI Core Metadata Element Comment
Intervention, Performed Procedure (the .status metadata allows conformance to the specific QDM datatype context) QDM matched to QI Core / FHIR
Relevant Period Procedure.performed[x] QDM matched to QI Core / FHIR
Negation Rationale Procedure.notDoneReason QDM matched to QI Core / FHIR
Reason Procedure.reasonCode QDM matched to QI Core / FHIR
Result Procedure.outcome QDM matched to QI Core / FHIR
Author dateTime FHIR.provenance.recorded FHIR references authorDatetime as part of the provenance resource for all resources. Note: FHIR Provenance generally addresses the author of the message; the identifier/source of the original resource element is defined by the resource. Individual resource element provenance is summarized in the FHIR W5 Report (http://hl7.org/fhir/w5.html). Hence, the QDM Procedure author dateTime references FHIR provenance.
Status Procedure.status QDM matched to QI Core / FHIR

Note: Procedure.status allows specification of completed but it does not assure the procedure was completed successfully. The FHIR resource Proecedure.outcome does also specification of successful completion, but that element may be ambiguous. The Patient Care Workgroup is evaluating options to more clearly represent a procedure that successfully achieved its objective (objective is not currently available as a metadata element). Moreover, clinical care capture of success with respect to procedure completion is highly variable. See the QDM Known Issues for a description of the issue and a link to the ONC Jira QDM Issues page to join the discussion for QDM [1].

Code Procedure.code QDM matched to QI Core / FHIR
id Procedure.id QDM matched to QI Core / FHIR
Source Procedure.performer QDM matched to QI Core / FHIR

Intervention, Order [Using Task]

QDM Attribute QI Core Metadata Element Comment
Intervention, Order Task.intent Task intent uses the concepts proposal, plan, order, original-order, reflex-order, filler-order, instance-order, option. Constrain to "order" from the intent value set for QDM datatypes with the order context.
Negation Rationale Task.statusReason QDM matched to QI Core/FHIR - Constrained to instances in which Task.status = rejected, cancelled, or failed Task status value set (required)
Reason Task.reason QDM matched to QI Core / FHIR
Author dateTime Task.authoredOn QDM matched to QI Core / FHIR

Note: FHIR Provenance generally addresses the author of the message; the identifier/source of the original resource element is defined by the resource. Individual resource element provenance is summarized in the FHIR W5 Report (http://hl7.org/fhir/w5.html).

Code Task.code QDM matched to QI Core / FHIR
id Task.id QDM matched to QI Core / FHIR
Source Task.requester Task also provides the opportunity to request Task.owner (the person responsible for the task) and task.performerType

Intervention, Recommended [Using Task]

QDM Attribute QI Core Metadata Element Comment
Intervention, Order Task.intent Task intent uses the concepts proposal, plan, order, original-order, reflex-order, filler-order, instance-order, option. Constrain to "plan" from the intent value set for QDM datatypes with the recommended context.
Negation Rationale | row2cell2 | Task.statusReason QDM matched to QI Core/FHIR - Constrained to instances in which Task.status = rejected, cancelled, or failed Task status value set (required)
Reason Task.reason QDM matched to QI Core / FHIR
Author dateTime Task.authoredOn QDM matched to QI Core / FHIR

Note: FHIR Provenance generally addresses the author of the message; the identifier/source of the original resource element is defined by the resource. Individual resource element provenance is summarized in the FHIR W5 Report (http://hl7.org/fhir/w5.html).

Code Task.code QDM matched to QI Core / FHIR
id Task.id QDM matched to QI Core / FHIR
Source Task.requester Task also provides the opportunity to request Task.owner (the person responsible for the task) and task.performerType

Intervention, Performed [Using Task]

QDM Attribute QI Core Metadata Element Comment
Intervention, Performed Task (the .status metadata allows conformance to the specific QDM datatype context) QDM matched to QI Core / FHIR
Relevant Period Task.executionPeriod QDM matched to QI Core / FHIR
Negation Rationale Task.statusReason QDM matched to QI Core/FHIR - Constrained to instances in which Task.status = rejected, cancelled, or failed Task status value set (required)
Reason Task.reason QDM matched to QI Core / FHIR
Result Task.output.value[x] QDM matched to QI Core / FHIR
Author dateTime Task.authoredOn QDM matched to QI Core / FHIR

Note: FHIR Provenance generally addresses the author of the message; the identifier/source of the original resource element is defined by the resource. Individual resource element provenance is summarized in the FHIR W5 Report (http://hl7.org/fhir/w5.html).

Status Task.status QDM matched to QI Core / FHIR
Code Task.code QDM matched to QI Core / FHIR
id Task.id QDM matched to QI Core / FHIR
Source Task.requester Task also provides the opportunity to request Task.owner (the person responsible for the task) and task.performerType
Retrieved from "https://wiki.hl7.org/w/index.php?title=Intervention_(QDM)&oldid=163658"