Difference between revisions of "Appointment FHIR Resource Proposal"
Ewoutkramer (talk | contribs) (Created page with "{{subst::Template:FHIR Resource Proposal}}") |
m (Appointment) |
||
Line 13: | Line 13: | ||
− | = | + | =Appointment= |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Owning committee name== | ==Owning committee name== | ||
− | + | [[Patient Administration]] | |
− | |||
− | [[ | ||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
− | + | * "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 --> | ||
+ | pending | ||
==Scope of coverage== | ==Scope of coverage== | ||
Line 76: | Line 59: | ||
==Expected implementations== | ==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== | ==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== | ==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== | ==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== | ==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== | ==gForge Users== | ||
− | + | brian_pos | |
− | + | ewoutkramer | |
+ | grahameg |
Revision as of 14:17, 14 April 2014
Contents
- 1 Appointment
- 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
Appointment
Owning committee name
Contributing or Reviewing Work Groups
- "None"
FHIR Resource Development Project Insight ID
pending
Scope of coverage
RIM scope
Resource appropriateness
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