Scheduling, published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 1.0.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

Download and Analysis

You can also download:

• this entire guide,
• the definition resources in json, xml, ttl, or csv format, or
• the example resources in json, xml or ttl format.

The source code for this Implementation Guide can be found on GitHub.

Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (ihe.iti.scheduling.r4) and R4B (ihe.iti.scheduling.r4b) are available.

Dependency Table

Package hl7.fhir.uv.extensions.r4#5.1.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00)

Package hl7.fhir.uv.ipa#1.0.0 This IG describes how an application acting on behalf of a patient can access information about the patient from an clinical records system using a FHIR based API. The clinical records system may be supporting a clinical care provider (e.g. a hospital, or a general practitioner), or a health data exchange, including a national health record system. (built Sun, Mar 26, 2023 20:50+0000+00:00)

Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)

Package ihe.iti.balp#1.1.3 The Basic Audit Log Patterns (BALP) Implementation Guide is a Content Profile that defines some basic and reusable AuditEvent patterns. This includes basic audit log profiles for FHIR RESTful operations to be used when there is not a more specific audit event defined. A focus is enabling Privacy centric AuditEvent logs that hold well formed indication of the Patient when they are the subject of the activity being recorded in the log. Where a more specific audit event can be defined it should be derived off of these basic patterns. (built Wed, Feb 14, 2024 15:23-0600-06:00)

Globals Table

There are no Global profiles defined

IP Statements

This publication includes IP covered under the following statements.

• Copyright HL7. Licensed under creative commons public domain
  Show Usage
  • appointmentReason: Appointment/appt1-1 and Bundle/example-appt-bundle-1
• These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright © 2011 by the National Electrical Manufacturers Association.
  Show Usage
  • DICOM Controlled Terminology Definitions: AuditSchedulingClient and AuditSchedulingServer
  • Audit Event ID: AuditSchedulingClient and AuditSchedulingServer
• This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
  Show Usage
  • SNOMED Clinical Terms® (SNOMED CT®): Appointment/appt1-1, Bundle/example-appt-bundle-1... Show 4 more, Find_Appointments_Operation, IHE_ITI_Appointment_Profile, IHE_ITI_Scheduling_Snomed_CT_Services and IHE_ITI_Scheduling_Specialties
• This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
  Show Usage
  • Audit event entity type: AuditSchedulingClient and AuditSchedulingServer
  • AuditEventEntityRole: AuditSchedulingClient and AuditSchedulingServer
  • identifierType: Patient/pat1
  • ActCode: Encounter/example
  • ActReason: Encounter/example and Patient/ex-patient
  • MaritalStatus: Patient/pat1