Argo-Scheduling Implementation Guide Release 1.0.0

This page is part of the Argonaut Scheduling Implementation Guide (v1.0.0: Release) based on FHIR R3. This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Profiles defined as part of this Guide

Profiles

The following Profiles have been defined for this implementation guide.

  • Argonaut_Appointment_Bundle_Profile The Argonaut Appointment Bundle Profile is returned as a result of the '$find' operation and Appointment search.
  • Argonaut_Appointment_Profile The Argonaut Appointment Profile is used with the '$find', '$hold', and '$book' operations and when fetching appointments.
  • Argonaut_Coverage_Profile The Argonaut Coverage Profile profile is used to provide insurance information for scheduling an appointment and or registering a patient.
  • Argonaut_Prefetch_Slot_Profile The Argonaut Prefetch Slot Profile defines the Slots that are returned when prefetching slots.
  • Argonaut_Schedule_Notification_Profile The Argonaut Scheduling Schedule Notification Profile is defined for use as the payload when sending notifications to a subscriber as described in the updating slots step in [Use Case 3 Prefetching Open Slots](patient-scheduling.html#use-case-3-prefetching-open-slots).
  • Argonaut_Scheduling_Subscription_Profile The Argonaut Scheduling Subscription Profile is defined for sending notifications to a subscriber as described in the updating slots step in [Use Case 3 Prefetching Open Slots](patient-scheduling.html#use-case-3-prefetching-open-slots).
  • Argonaut_Slot_Bundle_Profile The Argonaut Slot Bundle Profile is returned as a result of the '$find' operation and Appointment search.

  • Extensions:

    These extensions have been defined for this implementation guide.

  • Subscription_Trigger_Event_Extension A brief, natural language description of a particular event identified by the implementation environment. When this event is evaluated as true, it triggers a notification to the subscriber.
  • Subscription_Payload_Profile_Extension The profile of the required data to be sent in the payload.
  • Subscription_Event_Focus_Extension The type of the required data, specified as the type name of a resource. For profiles, this value is set to the type of the base resource of the profile.
  • Reason_For_Current_Status Captures the reason for the current state of the Appointment.