This wiki has undergone a migration to Confluence found Here

Difference between revisions of "CommunicationRequest FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(9 intermediate revisions by 3 users not shown)
Line 3: Line 3:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
+
This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
+
[[Category:Approved FHIR Resource Proposal]]
  
  
Line 36: Line 36:
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
 
* [[Clinical Decision Support Workgroup]]
 
* [[Clinical Decision Support Workgroup]]
 +
* [[Patient Care]]
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
Line 41: Line 42:
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
  
Ken to provide
+
1125
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 76: Line 77:
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
  -->
 
  -->
 +
Communications are foundational to the coordination and delivery of care. The Communication resource captures communications between the various stakeholders involved in the provision of care. This may include provider-to-provider exchanges as well as patient-to-provider exchanges. Communications are not limited to human senders and recipients.
 +
 +
At this time, communication requests are the most common type of proposals made by Clinical Decision Support Systems. These generally take the form of notification messages or alerts but may also include patient education communication requests (e.g., a rule executing an infobutton query based on its metadata and patient-specific information)
  
 
==Expected implementations==
 
==Expected implementations==
  
 
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 +
* Unified Communication System (SOA)
  
 
==Content sources==
 
==Content sources==
Line 94: Line 99:
 
* A computer-based decision-support system requesting a reminder or alert be delivered to a responsible provider
 
* A computer-based decision-support system requesting a reminder or alert be delivered to a responsible provider
 
* A physician requesting notification from the nurse if a patient's temperature exceeds a value
 
* A physician requesting notification from the nurse if a patient's temperature exceeds a value
* A monitoring system or a provider requesting a staff member or department to notify a public health agency of a patient presenting with a reportable communicable disease public health agency
+
* A monitoring system or a provider requesting a staff member or department to notify a public health agency of a patient presenting with a communicable disease reportable to the public health agency
 
+
* A computer-based decision-support system proposes to send educational material to a patient
As indicated above the request, may represent an order that entered by a practitioner in a CPOE system as well as a proposal made by a clinical decision support system (CDSS) based on a patient's clinical record and context of care.
 
  
 
==Resource Relationships==
 
==Resource Relationships==
Line 108: Line 112:
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
  -->
 
  -->
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, and devices.
+
A communication request is a request to convey information from one entity, a sender, to another entity, a receiver. The sender and receivers may be patients, practitioners, related persons, organizations, and devices.
  
 
For additional information, please refer to the proposed resource: http://hl7-fhir.github.io/communicationrequest.html
 
For additional information, please refer to the proposed resource: http://hl7-fhir.github.io/communicationrequest.html
Line 115: Line 119:
  
 
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
 
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
 +
May 2015 DSTU
  
 
==gForge Users==
 
==gForge Users==
  
 
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
 
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
 +
cnanjo

Latest revision as of 00:13, 20 March 2015



CommunicationRequest

Owning committee name

Clinical Quality Information Work Group

Contributing or Reviewing Work Groups

FHIR Resource Development Project Insight ID

1125

Scope of coverage

This resource is a record of a request for a communication to be performed. 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, and devices.

RIM scope

Lloyd to provide

Resource appropriateness

Communications are foundational to the coordination and delivery of care. The Communication resource captures communications between the various stakeholders involved in the provision of care. This may include provider-to-provider exchanges as well as patient-to-provider exchanges. Communications are not limited to human senders and recipients.

At this time, communication requests are the most common type of proposals made by Clinical Decision Support Systems. These generally take the form of notification messages or alerts but may also include patient education communication requests (e.g., a rule executing an infobutton query based on its metadata and patient-specific information)

Expected implementations

  • Unified Communication System (SOA)

Content sources

Example Scenarios

Uses of communication request include

  • A computer-based decision-support system requesting a reminder or alert be delivered to a responsible provider
  • A physician requesting notification from the nurse if a patient's temperature exceeds a value
  • A monitoring system or a provider requesting a staff member or department to notify a public health agency of a patient presenting with a communicable disease reportable to the public health agency
  • A computer-based decision-support system proposes to send educational material to a patient

Resource Relationships

A communication request is a request to convey information from one entity, a sender, to another entity, a receiver. The sender and receivers may be patients, practitioners, related persons, organizations, and devices.

For additional information, please refer to the proposed resource: http://hl7-fhir.github.io/communicationrequest.html

Timelines

May 2015 DSTU

gForge Users

cnanjo