This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Location FHIR Resource Proposal"
Jump to navigation
Jump to search
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
<div class="messagebox cleanup metadata"> | <div class="messagebox cleanup metadata"> | ||
<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 | + | This page documents an [[: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 35: | Line 34: | ||
<!-- 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) --> | ||
| − | + | None | |
==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 --> | ||
| − | + | 925 | |
==Scope of coverage== | ==Scope of coverage== | ||
| Line 54: | Line 53: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| + | Resource covers contact details and position information for a physical place that may be visited and where healthcare resources and participants may be found or contained, accomodated, or stored. A Location includes both incidental locations (a place at which is used without prior designation or authorization) and dedicated, formally appointed locations. | ||
| + | |||
| + | The Location resource is *not* used to indicate the location of something on or in a person - for example the location of a lesion. this is the responsibility of that resource or the terminology used. | ||
==RIM scope== | ==RIM scope== | ||
| + | Place | ||
<!-- 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. --> | ||
| + | |||
==Resource appropriateness== | ==Resource appropriateness== | ||
| − | + | Almost all organizations of any size need to keep track of the locations used for healthcare, to keep track of where patients, devices and materials are located. This information goes beyond a simple name, to include contact details and spatial containment. | |
<!-- Does the resource meet the following characteristics? | <!-- Does the resource meet the following characteristics? | ||
| Line 75: | Line 79: | ||
==Expected implementations== | ==Expected implementations== | ||
| + | Present in CCDA. | ||
| + | Likely to be used in Encounter summaries | ||
| + | Needed for Hospital and other in-patient EMR systems (and some ambulatory care EMR's as well) | ||
<!--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. --> | ||
==Content sources== | ==Content sources== | ||
| + | None beyond the standard list | ||
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult | <!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult | ||
| Line 85: | Line 93: | ||
==Example Scenarios== | ==Example Scenarios== | ||
| + | Examples of use for Location are: | ||
| + | |||
| + | *A hospital building, clinic or GP's office, a home | ||
| + | *A ward, corridor, bedroom, emergency room or operation room | ||
| + | *A freezer or cabinet | ||
| + | *An ambulance, personal car or roadside location | ||
| + | |||
<!-- 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.) --> | ||
==Resource Relationships== | ==Resource Relationships== | ||
| + | Resources references Organization. Encounter will reference Location as will any resource that needs to indicate where an event or action took place. | ||
<!-- What are the resources do you expect will reference this resource and in what context? | <!-- What are the resources do you expect will reference this resource and in what context? | ||
| Line 100: | Line 116: | ||
==Timelines== | ==Timelines== | ||
| − | + | Expected to be ready for the sept 2013 DSTU ballot | |
<!-- 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 --> | ||
==gForge Users== | ==gForge Users== | ||
| − | + | ewoutkramer | |
<!-- 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.) --> | ||
Latest revision as of 05:44, 22 May 2014
This page documents an Approved FHIR Resource Proposal
Contents
- 1 Location
- 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
Location
Owning committee name
Contributing or Reviewing Work Groups
None
FHIR Resource Development Project Insight ID
925
Scope of coverage
Resource covers contact details and position information for a physical place that may be visited and where healthcare resources and participants may be found or contained, accomodated, or stored. A Location includes both incidental locations (a place at which is used without prior designation or authorization) and dedicated, formally appointed locations.
The Location resource is *not* used to indicate the location of something on or in a person - for example the location of a lesion. this is the responsibility of that resource or the terminology used.
RIM scope
Place
Resource appropriateness
Almost all organizations of any size need to keep track of the locations used for healthcare, to keep track of where patients, devices and materials are located. This information goes beyond a simple name, to include contact details and spatial containment.
Expected implementations
Present in CCDA. Likely to be used in Encounter summaries Needed for Hospital and other in-patient EMR systems (and some ambulatory care EMR's as well)
Content sources
None beyond the standard list
Example Scenarios
Examples of use for Location are:
- A hospital building, clinic or GP's office, a home
- A ward, corridor, bedroom, emergency room or operation room
- A freezer or cabinet
- An ambulance, personal car or roadside location
Resource Relationships
Resources references Organization. Encounter will reference Location as will any resource that needs to indicate where an event or action took place.
Timelines
Expected to be ready for the sept 2013 DSTU ballot
gForge Users
ewoutkramer
