×

HL7's new AMS is live!   We are working with Fonteva to resolve log in issues. My Account

Section 1e: Version 3 (V3)
Section 2: Clinical and Administrative Domains

HL7 Version 3 Standard: Scheduling, Release 2

DESCRIPTION

Scheduling is both a domain and a process. As a domain, Scheduling requires a generic set of messages and behavior to implement any number of Scheduling scenarios. As a process, Scheduling can offer an abstract data model and a set of operations to any domain within HL7 that utilizes scheduling concepts.

The scheduling messages are designed to meet the need to communicate various events related to the scheduling of generic appointments for healthcare services and/or for the use of resource slots

The HL7 Version 3 Normative Edition’s Scheduling document describes a messaging architecture for the notification of scheduling information from a scheduling system to auxiliary systems. This includes notifications of new, revised, cancelled, and rescheduled appointments. The messages in this document can be utilized "as is" for generic appointments where minimal detail is required. This section can also be used as a pattern for scheduling specialized activities.

ALTERNATIVE NAMES

HL7 Version 3 Standard: Scheduling, Release 2 may also go by the following names or acronyms:

"HL7 Version 3 Standard: Scheduling, R2", "V3: Scheduling, R1", Patient Administration, Scheduling, SCHED

TARGETS

  • Healthcare Institutions (hospitals, long term care, home care, mental health)
  • Clinical and Public Health Laboratories
  • Medical Imaging Service providers

BENEFITS

  • Provides interactions for scheduling general services
  • Provides a pattern for scheduling specialized activities

DEVELOPMENT BACKGROUND

In Version 3, Scheduling is both a domain and a process. As a domain, Scheduling offers a generic set of messages and behavior to implement any number of Scheduling scenarios. As a process, Scheduling offers an abstract data model and a set of operations to any domain within HL7 that utilizes scheduling concepts. We can consider Scheduling as a service and the use of that service as an interface.

 

Request transactions are unsolicited requests for scheduling (booking) an appointment for healthcare services or resource slots. These transactions occur between a placer (requesting) application and fulfiller (scheduling) applications. The query transactions allow any application to  discover the current schedule of available slots or appointments. Unsolicited transactions provide for the notification of scheduling information between systems. The scope is currently limited to four basic appointment notification interactions: New Appointment, Revise Appointment, Cancel Appointment, and Reschedule Appointment. Future releases will expand the scope to include additional scenarios, including requests, queries and slot management.

RELATED DOCUMENTS

HL7 Version 3 Standard: Scheduling, Release 2

(Download) (161.02 MB)

ADDITIONAL DETAILS

For specifications and information about workgroups, training, projects and more, visit the
HL7 Wiki page for this product at: http://wiki.hl7.org/index.php?title=Patient_Administration

TOPICS

  • Patient Administration
  • Scheduling

BALLOT TYPE

  • Normative

STATUS DATE

2014-12-12

RESPONSIBLE WORK GROUP

Patient Administration

PRODUCT TYPE

  • ANSI-approved

STAKEHOLDERS

  • Clinical and Public Health Laboratories
  • Healthcare Institutions
  • Medical Imaging Service Providers

FAMILY

  • V3

CURRENT STATE

  • Stable

REALM

  • Universal