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

Difference between revisions of "Communication (QDM)"

From HL7Wiki
Jump to navigation Jump to search
 
(6 intermediate revisions by the same user 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><br>
 
[http://wiki.hl7.org/index.php?title=Harmonization_of_Health_Quality_Information_models Back to Harmonization of Health Quality Information Models Page]<br><br>
Entered onto CQI WG Wiki on 18 April 2018<br><br>
+
The CQI Workgroup reviewed this content in April 2018 based on QDM version 5.3. The content has been updated to reflect a change in QDM version 5.4. QDM version 5.4 removes the previous QDM datatypes "Communication, Patient to Provider", "Communication, Provider to Patient", and "Communication, Provider to Provider". QDM version 5.4 creates a new QDM datatype, "Communication, Performed".  The previous QDM datatype mapping are retained for historical review. <br><br>
QDM defines Communication as the transmission, receipt, or acknowledgement of information sent from a source to a recipient, such as from one clinician to another regarding findings, assessments, plans of care, consultative advice, instructions, educational resources, etc. It also may include the receipt of response from a patient with respect to any aspect of the care provided. Furthermore, it may include the conveying of information from provider to patient (e.g., results, findings, plans for care, medical advice, instructions, educational resources, appointments). A time and date stamp is required. QDM defines three contexts for communication: Communication, Patient to Provider; Communication, Provider to Patient; Communication, Provider to Provider. For the CQI Work Group, please consider what is intended by the concept of communication as it is identified in FHIR / QI Core, and whether that matches to the intent in QDM.<br><br>
+
QDM defines Communication as the transmission, receipt, or acknowledgement of information sent from a source to a recipient, such as from one clinician to another regarding findings, assessments, plans of care, consultative advice, instructions, educational resources, etc. It also may include the receipt of response from a patient with respect to any aspect of the care provided. Furthermore, it may include the conveying of information from provider to patient (e.g., results, findings, plans for care, medical advice, instructions, educational resources, appointments). A time and date stamp is required. QDM defines on QDM datatype, Communication, Performed.<br><br>
 
'''''[http://hl7.org/fhir/communication.html FHIR Communication Resource]'''''<br>
 
'''''[http://hl7.org/fhir/communication.html FHIR Communication Resource]'''''<br>
 
This resource is a record of a communication. A communication is a conveyance of information from one entity, a sender, to another entity, a receiver. The sender and receivers may be patients, practitioners, related persons, organizations, or devices. Communication use cases include:
 
This resource is a record of a communication. A communication is a conveyance of information from one entity, a sender, to another entity, a receiver. The sender and receivers may be patients, practitioners, related persons, organizations, or devices. Communication use cases include:
Line 15: Line 15:
  
 
__FORCETOC__
 
__FORCETOC__
 +
=='''''QDM 5.4 ONLY''''' Communication, Performed==
  
==Communication, Patient to Provider==
+
{|border="1" cellpadding="2" cellspacing="0"
 +
| align="center" style="background:#f0f0f0;"|'''QDM Attribute'''
 +
| align="center" style="background:#f0f0f0;"|'''QI Core Metadata Element'''
 +
| align="center" style="background:#f0f0f0;"|'''Comment'''
 +
|-valign="top"
 +
| row1cell1 | Communication, Performed
 +
| row1cell2 | Communication.status
 +
| row1cell3 | QDM matched to FHIR / QI Core  (the .status metadata allows conformance to the specific QDM datatype context)
 +
|-
 +
| row2cell1 | Code
 +
| row2cell2 | Communication.reasonCode
 +
| row2cell3 | Note - CommunicationRequest in QI Core could be considered but QDM does not differentiate a Communication recommended or ordered, only communication so the mapping assumes the communication has occurred, with or without a response.
 +
|-
 +
| row2cell1 | Category
 +
| row2cell2 | Communication.category
 +
| row2cell3 | QDM matched to FHIR / QI Core
 +
|-
 +
| row2cell1 | Sender
 +
| row2cell2 | Communication.sender
 +
| row2cell3 | QDM matched to FHIR / QI Core
 +
|-
 +
| row2cell1 | Recipient
 +
| row2cell2 | Communication.recipient
 +
| row2cell3 | QDM matched to FHIR / QI Core
 +
|-
 +
| row2cell1 | Negation Rationale
 +
| row2cell2 | Communication.notDoneReason
 +
| row2cell3 | QDM matched to FHIR / QI Core
 +
|-
 +
| row2cell1 | Medium
 +
| row2cell2 | Communication.medium
 +
| row2cell3 | QDM matched to FHIR / QI Core
 +
|-
 +
| row2cell1 | Relevant Period
 +
| row2cell2 | Communication.sent<br> Communication.received
 +
| row2cell3 | QDM matched to FHIR / QI Core; Note - if interoperability is not present, the sending system may not have acknowledgement that the communication was received. In such situation, the QDM relevant period will have no end dateTime.
 +
|-
 +
| row2cell1 | Author dateTime
 +
| row2cell2 | Communication.sent
 +
| row2cell3 | QDM addresses authorDatetime as the time the communication is sent.
 +
|-
 +
| row2cell1 | Related to
 +
| row2cell2 | Communication.basedOn
 +
| row2cell3 | An order, proposal or plan fulfilled in whole or in part by this Communication.
 +
|-
 +
| row2cell1 | id
 +
| row2cell2 | Communication.id
 +
| row2cell3 | QDM matched to FHIR / QI Core
 +
|-
 +
| row2cell1 | Source
 +
| row2cell2 | Communication.sender
 +
| row2cell3 | The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.
 +
|}
 +
 
 +
=='''''QDM 5.3 ONLY''''' Communication, Patient to Provider==
  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
Line 51: Line 106:
 
| row2cell3 | The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.
 
| row2cell3 | The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.
 
|}
 
|}
==Communication, Provider to Patient==
+
=='''''QDM 5.3 ONLY''''' Communication, Provider to Patient==
  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  
Line 86: Line 141:
 
| row2cell3 | The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.
 
| row2cell3 | The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.
 
|}
 
|}
==Communication, Provider to Provider==
+
=='''''QDM 5.3 ONLY''''' Communication, Provider to Provider==
  
 
{|border="1" cellpadding="2" cellspacing="0"  
 
{|border="1" cellpadding="2" cellspacing="0"  

Latest revision as of 12:35, 15 June 2018

Back to Harmonization of Health Quality Information Models Page

The CQI Workgroup reviewed this content in April 2018 based on QDM version 5.3. The content has been updated to reflect a change in QDM version 5.4. QDM version 5.4 removes the previous QDM datatypes "Communication, Patient to Provider", "Communication, Provider to Patient", and "Communication, Provider to Provider". QDM version 5.4 creates a new QDM datatype, "Communication, Performed". The previous QDM datatype mapping are retained for historical review.

QDM defines Communication as the transmission, receipt, or acknowledgement of information sent from a source to a recipient, such as from one clinician to another regarding findings, assessments, plans of care, consultative advice, instructions, educational resources, etc. It also may include the receipt of response from a patient with respect to any aspect of the care provided. Furthermore, it may include the conveying of information from provider to patient (e.g., results, findings, plans for care, medical advice, instructions, educational resources, appointments). A time and date stamp is required. QDM defines on QDM datatype, Communication, Performed.

FHIR Communication Resource
This resource is a record of a communication. A communication is a conveyance of information from one entity, a sender, to another entity, a receiver. The sender and receivers may be patients, practitioners, related persons, organizations, or devices. Communication use cases include:

  • A reminder or alert delivered to a responsible provider
  • A recorded notification from the nurse that a patient's temperature exceeds a value
  • A notification to a public health agency of a patient presenting with a communicable disease reportable to the public health agency
  • Patient educational material sent by a provider to a patient
  • Non-patient specific communication use cases may include:
  • A nurse call from a hall bathroom
  • Advisory for battery service from a pump

HL7 FHIR Procedure Resource
The boundary between determining whether an action is a Procedure (training or counseling) as opposed to a Communication is based on whether there's a specific intent to change the mind-set of the patient. Mere disclosure of information would be considered a Communication. A process that involves verification of the patient's comprehension or to change the patient's mental state would be a Procedure.


QDM 5.4 ONLY Communication, Performed

QDM Attribute QI Core Metadata Element Comment
Communication, Performed Communication.status QDM matched to FHIR / QI Core (the .status metadata allows conformance to the specific QDM datatype context)
Code Communication.reasonCode Note - CommunicationRequest in QI Core could be considered but QDM does not differentiate a Communication recommended or ordered, only communication so the mapping assumes the communication has occurred, with or without a response.
Category Communication.category QDM matched to FHIR / QI Core
Sender Communication.sender QDM matched to FHIR / QI Core
Recipient Communication.recipient QDM matched to FHIR / QI Core
Negation Rationale Communication.notDoneReason QDM matched to FHIR / QI Core
Medium Communication.medium QDM matched to FHIR / QI Core
Relevant Period Communication.sent
Communication.received
QDM matched to FHIR / QI Core; Note - if interoperability is not present, the sending system may not have acknowledgement that the communication was received. In such situation, the QDM relevant period will have no end dateTime.
Author dateTime Communication.sent QDM addresses authorDatetime as the time the communication is sent.
Related to Communication.basedOn An order, proposal or plan fulfilled in whole or in part by this Communication.
id Communication.id QDM matched to FHIR / QI Core
Source Communication.sender The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.

QDM 5.3 ONLY Communication, Patient to Provider

QDM Attribute QI Core Metadata Element Comment
Communication, Patient to Provider Communication.status QDM matched to FHIR / QI Core (the .status metadata allows conformance to the specific QDM datatype context)
Code Communication.reasonCode Note - CommunicationRequest in QI Core could be considered but QDM does not differentiate a Communication recommended or ordered, only communication so the mapping assumes the communication has occurred, with or without a response.
Negation Rationale Communication.notDoneReason QDM matched to FHIR / QI Core
Author dateTime Communication.sent QDM addresses authorDatetime as the time the communication is sent.
Related to Communication.basedOn An order, proposal or plan fulfilled in whole or in part by this Communication.
id Communication.id QDM matched to FHIR / QI Core
Source Communication.sender The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.

QDM 5.3 ONLY Communication, Provider to Patient

QDM Attribute QI Core Metadata Element Comment
Communication, Provider to Patient Communication.status QDM matched to FHIR / QI Core (the .status metadata allows conformance to the specific QDM datatype context)
Code Communication.reasonCode Note - CommunicationRequest in QI Core could be considered but QDM does not differentiate a Communication recommended or ordered, only communication so the mapping assumes the communication has occurred, with or without a response.
Negation Rationale Communication.notDoneReason QDM matched to FHIR / QI Core
Author dateTime Communication.sent QDM addresses authorDatetime as the time the communication is sent.
Related to Communication.basedOn An order, proposal or plan fulfilled in whole or in part by this Communication.
id Communication.id QDM matched to FHIR / QI Core
Source Communication.sender The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.

QDM 5.3 ONLY Communication, Provider to Provider

QDM Attribute QI Core Metadata Element Comment
Communication, Provider to Provider Communication.status QDM matched to FHIR / QI Core (the .status metadata allows conformance to the specific QDM datatype context)
Code Communication.reasonCode Note - CommunicationRequest in QI Core could be considered but QDM does not differentiate a Communication recommended or ordered, only communication so the mapping assumes the communication has occurred, with or without a response.
Negation Rationale Communication.notDoneReason QDM matched to FHIR / QI Core
Author dateTime Communication.sent QDM addresses authorDatetime as the time the communication is sent.
Related to Communication.basedOn An order, proposal or plan fulfilled in whole or in part by this Communication.
id Communication.id QDM matched to FHIR / QI Core
Source Communication.sender The entity (e.g. person, organization, clinical information system, or device) which was the source of the communication.