Difference between revisions of "Product SC"
(New page: ==Product Brief - HL7 V3: Scheduling, R1== back to Main_Page<br/>back to Product_List ===Product Name=== HL7 V3: Scheduling, R1 ===Topics=== *Appointment *Slot ===Standard Catego...) |
|||
| Line 1: | Line 1: | ||
| − | + | =Product Brief - HL7 V3: Scheduling, R1= | |
| + | __TOC__ | ||
back to [[Main_Page]]<br/>back to [[Product_List]] | back to [[Main_Page]]<br/>back to [[Product_List]] | ||
| − | + | ==Product Name== | |
HL7 V3: Scheduling, R1 | HL7 V3: Scheduling, R1 | ||
| Line 19: | Line 20: | ||
===Summary=== | ===Summary=== | ||
| − | This document describes a messaging architecture for the notification of scheduling information from a scheduling system to auxiliary systems. 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 where the details of the activity are published in messages under the section of this ballot responsible for the specialized domain. The intent is to establish a standard for the minimum functionaity that is useful and comprehensive enough to explore the important concepts. This minimum functionality is: notifications of new appointments, revised appontments, cancelled appointments, and rescheduled appointments. Later releases will build upon this basic set of interactins to include requests and queries. In addition to appointments, Scheduling also includes the concepts of resource time slots. Slots will also be supported in later releases. | + | This document describes a messaging architecture for the notification of scheduling information from a scheduling system to auxiliary systems. 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 where the details of the activity are published in messages under the section of this ballot responsible for the specialized domain. The intent is to establish a standard for the minimum functionaity that is useful and comprehensive enough to explore the important concepts. This minimum functionality is: notifications of new appointments, revised appontments, cancelled appointments, and rescheduled appointments. Later releases will build upon this basic set of interactins to include requests and queries. In addition to appointments, Scheduling also includes the concepts of resource time slots. Slots will also be supported in later releases. |
===Description=== | ===Description=== | ||
| Line 38: | Line 39: | ||
*Vendor: Health Care IT | *Vendor: Health Care IT | ||
*Payers | *Payers | ||
| − | + | <!-- | |
===Benefits=== | ===Benefits=== | ||
===Implementations/ Case Studies (Actual Users)=== | ===Implementations/ Case Studies (Actual Users)=== | ||
| − | + | --> | |
===Resources=== | ===Resources=== | ||
| Line 51: | Line 52: | ||
*Tutorial: V3 Overview | *Tutorial: V3 Overview | ||
* See more at http://www.hl7.org/implement/training.cfm | * See more at http://www.hl7.org/implement/training.cfm | ||
| + | <!-- | ||
=====Certification Available===== | =====Certification Available===== | ||
*none | *none | ||
====Presentations==== | ====Presentations==== | ||
| − | * | + | * |
===Relationship to/ Dependencies on, other standards=== | ===Relationship to/ Dependencies on, other standards=== | ||
| − | * | + | * --> |
===Links to current projects in development=== | ===Links to current projects in development=== | ||
| − | *[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=292 Project Insight # 292], | + | *[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=292 Project Insight # 292], Scheduling Release 2 |
| − | *[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=459 Project Insight # 459], | + | *[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=459 Project Insight # 459], Scheduling CMETs |
Revision as of 17:34, 10 November 2009
Product Brief - HL7 V3: Scheduling, R1
back to Main_Page
back to Product_List
Product Name
HL7 V3: Scheduling, R1
Topics
- Appointment
- Slot
Standard Category
- Health Information Exchange Standards
Integration Paradigm
- Messaging
Type
Normative, ANSI standard
Releases
- ANSI/HL7 V3 SC, R1-2003 - HL7 Version 3 Standard: Scheduling, Release 1 (12/1/03)
Summary
This document describes a messaging architecture for the notification of scheduling information from a scheduling system to auxiliary systems. 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 where the details of the activity are published in messages under the section of this ballot responsible for the specialized domain. The intent is to establish a standard for the minimum functionaity that is useful and comprehensive enough to explore the important concepts. This minimum functionality is: notifications of new appointments, revised appontments, cancelled appointments, and rescheduled appointments. Later releases will build upon this basic set of interactins to include requests and queries. In addition to appointments, Scheduling also includes the concepts of resource time slots. Slots will also be supported in later releases.
Description
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. This release of V3 contains generic scheduling messages that can be implemented by themselves or they can be used as a pattern for domain-specific messages.
The scheduling messages in this section are designed to communicate various events related to the scheduling of generic appointments for healthcare services. There are three basic types of interactions defined in the scheduling domain:
- Request messages and their responses
- Query messages and their responses, and
- Unsolicited notifications
Request transactions communicate requests for the scheduling of appointments for healthcare services or for the booking of resource slots. These transactions occur between placer (requesting) applications and fulfiller (scheduling) applications. The query transactions allow any application to query the current schedule of booked and available slots or booked appointments. Unsolicited transactions provide for the notification of scheduling information between systems.
For this publication of the HL7 Scheduling standard, we are limiting the scope 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.
Business Case (Intended Use, Customers)
- Provider: Healthcare Institutions (hospitals, long term care, home care, mental health)
- Vendor: Health Care IT
- Payers
Resources
Work Groups
Education
- Tutorial: V3 Overview
- See more at http://www.hl7.org/implement/training.cfm
Links to current projects in development
- Project Insight # 292, Scheduling Release 2
- Project Insight # 459, Scheduling CMETs
