IHE ITI Scheduling
0.8.0-current - ci-build
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
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.
The Client [ITI-Y] transaction passes a go Request from a Client to a Server.
Table: Actor Roles
Actor | Role |
---|---|
Client | Sends query to Server |
Server | Receives the query and responds |
FHIR-R4 HL7 FHIR Release 4.0
Figure: Book Appointment Interactions
This transaction uses the $book
operation as defined in the Operation Definition.
This transaction can be triggered by:
$find
operationThe Book Appointment request is defined as a FHIR Operation. Please see the corresponding Operation Definition.
'’TODO: define expected actions’’
'’TODO: define the triggers’’
'’TODO: define the message – usually with a StructureDefinition’’
'’TODO: define expected actions’’
Server implementing this transaction shall provide a CapabilityStatement Resource as described in ITI TF-2x: Appendix Z.3 indicating the transaction has been implemented.
See MHD Security Considerations
'’TODO: The security audit criteria ‘’
'’TODO: the specifics’’
'’TODO: the specifics’’