Scheduling
1.0.1-current - ci-build

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

## Significant Changes and Issues

## Significant Changes

### Significant Changes from Previous Revision

None, this is the first published revision.

## Issues

### Submit an Issue

IHE welcomes New Issues from the GitHub community. For those without GitHub access, issues can be submitted to the ITI Public Comment form.

As issues are submitted they will be managed on the ITI.Scheduling GitHub Issues, where discussion and workarounds can be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later).

### Open Issues

- ITI-Scheduling-001: `$book` only, or `$book` and `$modify`? The current approach is to provide three distinct uses for the `$book` operation. See the `$book` operation for details. (Issue 31)
- ITI-Scheduling-002: Should there be a named option for supporting the Appointment Hold [ITI-16] transaction? (Issue 32)
- ITI-Scheduling-003: Should there be a named option for supporting the Find Existing Appointments [ITI-18] transaction? (Issue 33)
- ITI-Scheduling-004: Need to add Resource Examples (Issue 26)
- ITI-Scheduling-005: Need a Test Plan (Issue 20)
- ITI-Scheduling-006: Need Audit Events for [ITI-115], [ITI-116], and [ITI-118] (Issue 30)

### Closed Issues

No closed issues.