This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Encounter FHIR Resource Proposal"
Jump to navigation
Jump to search
Ewoutkramer (talk | contribs) (Created page with "{{subst::Template:FHIR Resource Proposal}}") |
|||
| (3 intermediate revisions by one other user 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 13: | Line 12: | ||
| − | = | + | =Encounter= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 28: | Line 27: | ||
==Owning committee name== | ==Owning committee name== | ||
| + | [[Patient_Administration]] | ||
<!-- 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. --> | ||
| − | |||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
| − | + | None | |
<!-- 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) --> | ||
| − | |||
| − | |||
| − | |||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| + | 925 | ||
<!-- 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 --> | ||
==Scope of coverage== | ==Scope of coverage== | ||
| + | Covers the data about an interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient. | ||
| + | |||
| + | It covers encounters in ambulatory, emergency, home health, inpatient and virtual visits. An Encounter encompasses the lifecycle from pre-admission and preparation, the actual visit (for ambulatory visits), and admission, stay and discharge (for inpatient visits). | ||
<!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | <!-- Define the full scope of coverage for the resource. The scope must be clearly delineated such that it does not overlap with any other existing or expected resource. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | ||
| Line 57: | Line 57: | ||
==RIM scope== | ==RIM scope== | ||
| + | PatientEncounter | ||
<!-- 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== | ||
| + | Hospital systems track information about the admission and discharge of patients and meetings between the patient and a care professional (mostly for billing purposes). The systems we've looked at include data about the patient's location as well. Although data around encounters is certainly tracked during a period of time, there seems to be no clear identifier for an encounter. Many systems seem to keep separate records for in- and outpatients but we combined these into one resource after broad consultation: | ||
| + | * There's considerable overlap in attributes (although that would not be enough reason on its own to combine them) | ||
| + | * We prefer having a single concept to use for tracking the administrative context of the clinical events, it's less relevent whether this is for an in- or outpatient | ||
| + | * Recently, PA and PC have merged the different v3 models that existed for separate kinds of Encounters into one, based on community input | ||
| + | * Gut feeling and experience with teaching shows its problematic to keep them separate | ||
<!-- Does the resource meet the following characteristics? | <!-- Does the resource meet the following characteristics? | ||
| Line 76: | Line 82: | ||
==Expected implementations== | ==Expected implementations== | ||
| + | Encounter data is tracked by most, if not all, hospital information systems. | ||
<!--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== | ||
| + | * CIMI | ||
| + | * Actual implementations: ChipSoft, Epic, Cerner | ||
<!-- 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 86: | Line 95: | ||
==Example Scenarios== | ==Example Scenarios== | ||
| + | * A patient present at the hospital for an outpatient encounter with his cardiologist | ||
| + | * A person brought in at the emergency department | ||
| + | * An older couple staying at a nursery home | ||
| + | * A GP visiting a patient at home | ||
<!-- 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== | ||
| + | Refers to Location, Patient, Appointment, Practitioner, Organization | ||
| + | Will be refered to by all (possibly PC-related resources) that want to track the context of recording (i.e. measurement taken during which encounter) | ||
<!-- 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 101: | Line 116: | ||
==Timelines== | ==Timelines== | ||
| + | Expected to be ready for september 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:41, 22 May 2014
This page documents an Approved FHIR Resource Proposal
Contents
- 1 Encounter
- 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
Encounter
Owning committee name
Contributing or Reviewing Work Groups
None
FHIR Resource Development Project Insight ID
925
Scope of coverage
Covers the data about an interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.
It covers encounters in ambulatory, emergency, home health, inpatient and virtual visits. An Encounter encompasses the lifecycle from pre-admission and preparation, the actual visit (for ambulatory visits), and admission, stay and discharge (for inpatient visits).
RIM scope
PatientEncounter
Resource appropriateness
Hospital systems track information about the admission and discharge of patients and meetings between the patient and a care professional (mostly for billing purposes). The systems we've looked at include data about the patient's location as well. Although data around encounters is certainly tracked during a period of time, there seems to be no clear identifier for an encounter. Many systems seem to keep separate records for in- and outpatients but we combined these into one resource after broad consultation:
- There's considerable overlap in attributes (although that would not be enough reason on its own to combine them)
- We prefer having a single concept to use for tracking the administrative context of the clinical events, it's less relevent whether this is for an in- or outpatient
- Recently, PA and PC have merged the different v3 models that existed for separate kinds of Encounters into one, based on community input
- Gut feeling and experience with teaching shows its problematic to keep them separate
Expected implementations
Encounter data is tracked by most, if not all, hospital information systems.
Content sources
- CIMI
- Actual implementations: ChipSoft, Epic, Cerner
Example Scenarios
- A patient present at the hospital for an outpatient encounter with his cardiologist
- A person brought in at the emergency department
- An older couple staying at a nursery home
- A GP visiting a patient at home
Resource Relationships
Refers to Location, Patient, Appointment, Practitioner, Organization Will be refered to by all (possibly PC-related resources) that want to track the context of recording (i.e. measurement taken during which encounter)
Timelines
Expected to be ready for september 2013 DSTU ballot
gForge Users
ewoutkramer
