Difference between revisions of "Slot FHIR Resource Proposal"
Ewoutkramer (talk | contribs) (Created page with "{{subst::Template:FHIR Resource Proposal}}") |
m (Slot) |
||
Line 13: | Line 13: | ||
− | = | + | =Slot= |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==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== | ||
+ | The slot is used to cover: | ||
+ | * an interval of time whereby the referenced availability resource's may be booked | ||
+ | * what type of appointment can be booked in the interval of time (may over-rule the availabilities restrictions) | ||
+ | * The status of the slot (booked/available/overbooked) | ||
− | + | The slot does not cover: | |
− | + | * Recurrences | |
− | + | * the total window of time in the "planning horizon" (This is covered by the Availability resource) | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==RIM scope== | ==RIM scope== | ||
− | |||
<!-- 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. --> | ||
Line 76: | Line 54: | ||
==Expected implementations== | ==Expected implementations== | ||
− | + | This resource is expected to be implemented by community clinics, general practice and specialist software solutions to publish their availability information to take appointments directly from users external to the organization providing the information. | |
− | |||
==Content sources== | ==Content sources== | ||
− | + | The slot resource has some overlap with the iCal standard, the mapping to this standard will also be in scope of the resource. | |
− | |||
− | |||
− | |||
==Example Scenarios== | ==Example Scenarios== | ||
− | + | A Physio-Therapy clinic wants to publish a 2 month planning horizon for where appointments can be booked. Each available period of time will have a slot resource created describing that time slot; what it can be used for, and the availability status of the slot. | |
− | + | If the clinic had repeating intervals, these must be expanded into each slot and created on the fhir server. This removes the need for the slot's recurrence information to be concerned with handling time zones across time intervals. | |
==Resource Relationships== | ==Resource Relationships== | ||
− | + | This Slot Resource will reference the Availability that it "belongs" to, and will be referenced by any Appointment Resources that have been booked into this Slot. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==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:07, 14 April 2014
Contents
- 1 Slot
- 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
Slot
Owning committee name
Contributing or Reviewing Work Groups
- "None"
FHIR Resource Development Project Insight ID
pending
Scope of coverage
The slot is used to cover:
- an interval of time whereby the referenced availability resource's may be booked
- what type of appointment can be booked in the interval of time (may over-rule the availabilities restrictions)
- The status of the slot (booked/available/overbooked)
The slot does not cover:
- Recurrences
- the total window of time in the "planning horizon" (This is covered by the Availability resource)
RIM scope
Resource appropriateness
Expected implementations
This resource is expected to be implemented by community clinics, general practice and specialist software solutions to publish their availability information to take appointments directly from users external to the organization providing the information.
Content sources
The slot resource has some overlap with the iCal standard, the mapping to this standard will also be in scope of the resource.
Example Scenarios
A Physio-Therapy clinic wants to publish a 2 month planning horizon for where appointments can be booked. Each available period of time will have a slot resource created describing that time slot; what it can be used for, and the availability status of the slot. If the clinic had repeating intervals, these must be expanded into each slot and created on the fhir server. This removes the need for the slot's recurrence information to be concerned with handling time zones across time intervals.
Resource Relationships
This Slot Resource will reference the Availability that it "belongs" to, and will be referenced by any Appointment Resources that have been booked into this Slot.
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