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

Difference between revisions of "EpisodeOfCare FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with " <div class="messagebox cleanup metadata"> <div style="float: left;">35px| </div> <div style="background:#F0F0F0"> This page documents a :category...")
 
Line 19: Line 19:
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
−
* "None"
+
* Patient Care
 +
* Financial Management
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
Line 27: Line 28:
  
 
==Scope of coverage==
 
==Scope of coverage==
−
<!-- Appointment resources are used to provide information about a planned meeting that may be in the future or past. The resource only describes a single meeting, a series of repeating visits would require multiple appointment resources be created for each instance. Examples include a scheduled surgery, a follow-up for a clinical visit, a scheduled conference call between clinicians to discuss a case, the reservation of a piece of diagnostic equipment for a particular use, etc. The visit scheduled by an appointment may be in person or remote (by phone, video conference, etc.) All that matters is that the time and usage of one or more individuals, locations and/or pieces of equipment is being fully or partially reserved for a designated period of time.
+
The EpisodeOfCare Resource stores information about an association of a Patient with an Organization for a period of time for a particular reason.
 +
This may include information such as:
 +
* Organization
 +
* Problem/Condition
 +
* Care Team
 +
* Care Manager/Care co-ordinator
 +
* Funding Sources
 +
* Billers
 +
* Contact information
 +
* Period
 +
* Status dates
 +
* Practitioners (and roles)
 +
* Referral source
 +
* Consent?
  
−
This definition takes the concepts of appointments in a clinical setting and also extends them to be relevant in the community healthcare space, and also ease exposure to other appointment / calendar standards widely used outside of healthcare.
+
In many cases, this represents a period of time where the organization has some level of responsibility for the care of the patient, even if not currently participating in an encounter.
  
−
This resource is not expected to handle recurring appointments (at this stage) due to the complexities of recurrences, time-zone transitions, and status changes of variations to the recurrence. If a user of an appointment desires to handle recurrences, they will need to "expand" the recurrences as separate resource instances and use some form of identifier to "join" them together as the one logical collection.
+
Note: The primary difference between the EpisodeOfCare and the Encounter is that the Encounter records the details of an activity directly relating to the patient, however the EpisodeOfCare is the container that can link a series of Enounters together for a specific problem/issue.  
  
−
This resource does not also cover a more extensive definition/description of the actual service that is to take place during this appointment. This is likely to be the content of another new resource "Healthcare Service".
+
These resources are typically known in existing systems as:
−
This new "Healthcare Service" would cover a multi-level category and type structure to assist in the discovery of what services are provided in an organization/location.
+
* EpisodeOfCare: Case, Program, Problem
−
-->
+
* Encounter: Visit, Contact
  
 
==RIM scope==
 
==RIM scope==
Line 41: Line 55:
  
 
==Resource appropriateness==
 
==Resource appropriateness==
−
<!-- Many systems already exchange appointment information using iCal appointments, and some use the HL7v2 schedule messages, or proprietary format messages.
+
Many systems track the progress of a patient’s condition for purposes of ensuring that the care being provided to the patient is maintaining their problem, or improving the issue over time.
−
 
 
−
The existing iCal standard does provide a good basis that is widely accepted by many (mostly non-healthcare related) software packages. However we would like to extend these basic features to better meet the complex needs in the healthcare space where transparency and traceability is critical.
 
−
-->
 
  
 +
Other reasons for creating an EpisodeOfCare could be for tracking the details required for government reporting.
  
 
==Expected implementations==
 
==Expected implementations==
−
<!-- This resource is expected to be implemented by scheduling systems used by community clinics, general practice and specialists to receive and publish their appointments directly to/from users external to the organization providing the information.
+
This resource is likely to be implemented by applications:
−
-->
+
* Community Care Systems
 +
** Tracking progress of a specific condition
 +
** tracking government funding
 +
* Problem based General Practice systems
 +
* Disability Support Systems
 +
* Aged Care Systems (Community and Residential)
  
 
==Content sources==
 
==Content sources==
−
We will be evaluating the HL7 v2 and v3 messages and models which are closely related.
+
We will refer to the HL7 v2 and v3 messages and models.
  
 
==Example Scenarios==
 
==Example Scenarios==
Line 62: Line 79:
  
 
==Resource Relationships==
 
==Resource Relationships==
−
<!-- The Appointment Resource will reference any slots that it is booking to, along with the participants that are involved in the appointment, such as the patient and provider (but not restricted to just these).
+
This resource is expected to have references to Patient, Location, Organization, Practitioner.  
−
It will also reference the Location resource where the appointment is to take place.
 
  
−
The Appointment will be referenced by both the Encounter, and also the AppointmentResponse, where replies to requests are made.
+
Other relationships may include: Appointment, Encounter, Coverage, CarePlan.
−
-->
 
  
 
==Timelines==
 
==Timelines==
−
PA plans to include this resource for inclusion in the next Ballot (expecting September 2014).
+
We are hoping that this resource will be ready for inclusion in the next Ballot (expecting September 2014).  
  
 
==gForge Users==
 
==gForge Users==
 
brian_pos
 
brian_pos

Revision as of 17:16, 8 May 2014

OpenHotTopic.GIF

This page documents a Pending FHIR Resource Proposal



EpisodeOfCare

Owning committee name

Patient Administration

Contributing or Reviewing Work Groups

  • Patient Care
  • Financial Management

FHIR Resource Development Project Insight ID

pending

Scope of coverage

The EpisodeOfCare Resource stores information about an association of a Patient with an Organization for a period of time for a particular reason. This may include information such as:

  • Organization
  • Problem/Condition
  • Care Team
  • Care Manager/Care co-ordinator
  • Funding Sources
  • Billers
  • Contact information
  • Period
  • Status dates
  • Practitioners (and roles)
  • Referral source
  • Consent?

In many cases, this represents a period of time where the organization has some level of responsibility for the care of the patient, even if not currently participating in an encounter.

Note: The primary difference between the EpisodeOfCare and the Encounter is that the Encounter records the details of an activity directly relating to the patient, however the EpisodeOfCare is the container that can link a series of Enounters together for a specific problem/issue.

These resources are typically known in existing systems as:

  • EpisodeOfCare: Case, Program, Problem
  • Encounter: Visit, Contact

RIM scope

Resource appropriateness

Many systems track the progress of a patient’s condition for purposes of ensuring that the care being provided to the patient is maintaining their problem, or improving the issue over time.

Other reasons for creating an EpisodeOfCare could be for tracking the details required for government reporting.

Expected implementations

This resource is likely to be implemented by applications:

  • Community Care Systems
    • Tracking progress of a specific condition
    • tracking government funding
  • Problem based General Practice systems
  • Disability Support Systems
  • Aged Care Systems (Community and Residential)

Content sources

We will refer to the HL7 v2 and v3 messages and models.

Example Scenarios

Resource Relationships

This resource is expected to have references to Patient, Location, Organization, Practitioner.

Other relationships may include: Appointment, Encounter, Coverage, CarePlan.

Timelines

We are hoping that this resource will be ready for inclusion in the next Ballot (expecting September 2014).

gForge Users

brian_pos

Retrieved from "https://wiki.hl7.org/w/index.php?title=EpisodeOfCare_FHIR_Resource_Proposal&oldid=86360"