This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Appointment FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 32: Line 32:
  
 
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.
 
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.
 
  
 
==RIM scope==
 
==RIM scope==

Revision as of 19:38, 28 April 2014



Appointment

Owning committee name

Patient Administration

Contributing or Reviewing Work Groups

  • "None"

FHIR Resource Development Project Insight ID

pending

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.

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.

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.

RIM scope

Act (ActMood = ActMoodAppointment or ActMoodAppointmentRequest)

Resource appropriateness

Many systems already exchange appointment information using iCal appointments, and some use the HL7v2 schedule messages, or proprietary format messages.

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.


Expected implementations

This resource is expected to be implemented by community clinics, general practice and specialist software solutions to receive and publish their appointments directly to/from users external to the organization providing the information.

Content sources

The appointment resource has a lot of similarities and has been inspired by the iCal standard, and as such there will be a mapping provided to this standard.

Example Scenarios

A Physio-Therapy clinic that has its available times published via Availability and Slot resources wants to be able to accept appointment requests from users outside the organization. This resource provides users with a way of making the request, and viewing the outcomes from any invited parties as to the status of the appointment.

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). 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.

Timelines

Given the progress to date, we expect that this resource will be ready for inclusion in the next Ballot (expecting September 2014) the resource has already undergone a great deal of review in PA over the last 6 months.

gForge Users

brian_pos ewoutkramer grahameg