Difference between revisions of "EpisodeOfCare FHIR Resource Proposal"
| Line 54: | Line 54: | ||
==RIM scope== | ==RIM scope== | ||
<!-- Act (ActMood = ActMoodAppointment or ActMoodAppointmentRequest) --> | <!-- Act (ActMood = ActMoodAppointment or ActMoodAppointmentRequest) --> | ||
| + | TBD. | ||
==Resource appropriateness== | ==Resource appropriateness== | ||
Revision as of 17:17, 8 May 2014
This page documents a Pending FHIR Resource Proposal
Contents
- 1 EpisodeOfCare
- 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
EpisodeOfCare
Owning committee name
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
TBD.
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
