This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Communication FHIR Resource Proposal"
Jump to navigation
Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}") |
|||
| (17 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: | + | 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: | + | [[Category:Approved FHIR Resource Proposal]] |
| Line 13: | Line 13: | ||
| − | = | + | =Communication= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 30: | Line 30: | ||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | ||
| − | [[ | + | [[Clinical Quality Information Work Group]] |
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
<!-- 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]] |
| − | * | + | * [[Patient Care]] |
| − | |||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
<!-- 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 --> | ||
| + | |||
| + | 1125 | ||
==Scope of coverage== | ==Scope of coverage== | ||
| Line 55: | Line 56: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| + | |||
| + | 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, and 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 | ||
==RIM scope== | ==RIM scope== | ||
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
| + | Lloyd to provide | ||
==Resource appropriateness== | ==Resource appropriateness== | ||
| Line 74: | Line 82: | ||
* 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. | ||
==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 systems in a SOA environment. | ||
| + | * FHIR Profiles for Quality | ||
==Content sources== | ==Content sources== | ||
| Line 88: | Line 101: | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
| + | |||
| + | Refer to 'Scope of Coverage' for some examples. | ||
==Resource Relationships== | ==Resource Relationships== | ||
| Line 99: | Line 114: | ||
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) | ||
--> | --> | ||
| + | |||
| + | 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. | ||
| + | |||
| + | Please refer to the proposed resource definition: http://hl7-fhir.github.io/communication.html | ||
==Timelines== | ==Timelines== | ||
<!-- 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 23:54, 19 March 2015
This page documents a Approved FHIR Resource Proposal
Contents
- 1 Communication
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
Communication
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 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, and 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
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.
- FHIR Profiles for Quality
Content sources
Example Scenarios
Refer to 'Scope of Coverage' for some examples.
Resource Relationships
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.
Please refer to the proposed resource definition: http://hl7-fhir.github.io/communication.html
Timelines
May 2015 DSTU
gForge Users
cnanjo
