This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "AppointmentResponse FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
Line 3: Line 3:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
+
This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
+
[[Category:Approved FHIR Resource Proposal]]
  
  

Latest revision as of 17:53, 19 February 2015



AppointmentResponse

Owning committee name

Patient Administration

Contributing or Reviewing Work Groups

  • "None"

FHIR Resource Development Project Insight ID

pending

Scope of coverage

As the AppointmentResponse resource is directly related to the Appointment Resource it provides the accountability and transparency of the overall appointment.

The scope of the appointment response includes:

  • The acceptance status of the response
  • the reference to the appointment
  • which entity that is responding to the appointment request
  • the details that the participant accepts (or wants to accept)
  • any additional notes that the participant wants to provide with respect to the response


RIM scope

Act(ActMood = actMoodAppointmentRequest or actMoodAppointment) Note: This relationship is through the interaction rather than the RIM.

Resource appropriateness

This resource is required to be able to communicate the distinct responses to appointment requests.

Note: The existing iCal Standard also has this concept covered in it's basic structure.

Expected implementations

This resource is expected to be implemented by community clinics, general practice and specialist's appointment scheduling systems to reply to appointment requests.

Content sources

The appointment response resource has a lot of similarities with the iCal standard and a mapping to this standard will be expected.


Example Scenarios

An appointment has been requested for a physician, room (location) and the patient to meet. A response will be created for each of these participants indicating their acceptance status. Once all participants have responded the overall status of the appointment can be processed and updated.


Resource Relationships

The AppointmentResponse Resource references the Appointment Resource (related to a specified participant), where the Appointment is in a pending state.

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