This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Communication FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 88: Line 88:
  
 
<!--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 systems in a SOA environment.
  
 
==Content sources==
 
==Content sources==

Revision as of 20:08, 8 February 2015



Communication

Owning committee name

Clinical Quality Information Work Group

Contributing or Reviewing Work Groups

FHIR Resource Development Project Insight ID

Ken to provide


Scope of coverage

This resource is a record of a communication that was 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. The communication resource may track the following, for instance:

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

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.

Expected implementations

  • Unified communication systems in a SOA environment.

Content sources

Example Scenarios

Resource Relationships

Please refer to the proposed resource definition: http://hl7-fhir.github.io/communication.html

Timelines

gForge Users