IHE ITI Scheduling
0.8.0-current - ci-build International flag

IHE ITI Scheduling, published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 0.8.0-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.Scheduling/ and changes regularly. See the Directory of published versions

2:3.117 Book Appointment [ITI-117]

This section corresponds to transaction [ITI-117] of the IHE Technical Framework. Transaction [ITI-117] is used by the Scheduling Client and Scheduling Server Actors. The Find Appointments [ITI-115] transaction is used to provide a set of parameters to the server, and based on them to get back a list of possible appointments.

Scope

The Client [ITI-Y] transaction passes a go Request from a Client to a Server.

Actors Roles

Table: Actor Roles

Actor Role
Client Sends query to Server
Server Receives the query and responds

Referenced Standards

FHIR-R4 HL7 FHIR Release 4.0

Interactions

Scheduling ClientScheduling Server1. Book Appointment Request [ITI-117]2. Book Appointment Response [ITI-117]


Figure: Go Interactions

go Query Message

This message uses the HTTP GET method on the target Server endpoint to convey the query parameters FHIR query.

Trigger Events

'’TODO: define the triggers’’

Message Semantics

'’TODO: define the message – usually with a StructureDefinition’’

Expected Actions

'’TODO: define expected actions’’

Go Response Message

Trigger Events

'’TODO: define the triggers’’

Message Semantics

'’TODO: define the message – usually with a StructureDefinition’’

Expected Actions

'’TODO: define expected actions’’

CapabilityStatement Resource

Server implementing this transaction shall provide a CapabilityStatement Resource as described in ITI TF-2x: Appendix Z.3 indicating the transaction has been implemented.

  • Requirements CapabilityStatement for Client
  • Requirements CapabilityStatement for Server

Security Considerations

See MHD Security Considerations

Security Audit Considerations

'’TODO: The security audit criteria ‘’

Client Audit

'’TODO: the specifics’’

Server Audit

'’TODO: the specifics’’