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
(Created page with "{{subst::Template:FHIR Resource Proposal}}")
 
m (Appointment)
Line 13: Line 13:
  
  
=PutProposedResourceNameHere=
+
=Appointment=
 
 
<!-- Resource names should meet the following characteristics:
 
* Lower camel case
 
* U.S. English
 
* Domain-friendly
 
* Short
 
* Clear
 
* Unique
 
* Avoid non-universal abbreviations (e.g. URL would be ok)
 
* Be expressed as a noun
 
* Be consistent with other similar resources
 
-->
 
  
 
==Owning committee name==
 
==Owning committee name==
 
+
[[Patient Administration]]
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
 
[[YourCommitteeName]]
 
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
 
+
* "None"
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
 
* Work Group Name
 
* or link
 
* or "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.
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 
  
 
==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.
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult
 
 
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
  
 
==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.
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
 
  
 
==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.
  
<!-- What are the resources do you expect will reference this resource and in what context?
+
The Appointment will be referenced by both the Encounter, and also the AppointmentResponse, where replies to requests are made.
 
 
What resources do you expect this resource reference and in what context?
 
 
 
Note: These may be existing resources or "expected" resource
 
 
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
-->
 
  
 
==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.
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
 
  
 
==gForge Users==
 
==gForge Users==
 
+
brian_pos
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
+
ewoutkramer
 +
grahameg

Revision as of 14:17, 14 April 2014



Appointment

Owning committee name

Patient Administration

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