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

Difference between revisions of "CommunicationRequest FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
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]]
  
  

Revision as of 22:30, 25 February 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 reportable communicable disease public health agency

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

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.

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

Timelines

May 2015 DSTU

gForge Users

cnanjo