Project Summary for Unified Communication Service Interface Specification Project
Visit Project Insight to see the full project details. *
Project Details
Number | 1052 View Ballot Items List (with NIBs) |
---|---|
Name | Unified Communication Service Interface Specification Project |
Sponsor(s) | Services Oriented Architecture Work Group |
Co-Sponsor(s) | Clinical Decision Support Work Group |
Steering Division | Infrastructure |
Description | The proposed Unified Communication Service is intended to complement existing SOA services and the SAIF Behavioural Framework (BF) for HL7. It will provide a Service Functional Model (SFM) for delivering alerts, recommendations, and other notifications using a variety of transport mechanisms to include email, SMS, VOIP or other communication channels. The service will provide for message routing and/or escalation to ensure that when the intended recipients are not available, appropriate surrogates can be notified and priority messages can be responded to in a timely manner. The interface specification will be developed according to the conventions described at http://hssp.wikispaces.com/HSSPApproach, and will be documented in a corresponding HSSP wiki. Pre-existing conceptual and standards-development work in the Communications domain (Extensible Messaging and Presence Protocol-XMPP, Short Message Service-SMS, Session Initiation Protocol-SIP, OASIS WS-Human Task, OASIS Web Services Notification-WSN) will be leveraged to help document the necessary definitions, descriptions, graphics, and artifacts that are relevant. In keeping with the approach used by other HL7 specifications, the Communication Service will distinguish between the communication modality itself and the payload being communicated. The Service Interface Specification will provide functional, semantic, and conformance profiles. Some usage scenarios: a) A CDS system sends a priority alert to a provider's EMR account informing them of a potentially dangerous drug-drug interaction. The alert is sent with read recipient enabled. When the original recipient doesn't respond within pre-determined 45mins time window, the system escalates the reminder to a dedicated surrogate and modifies the payload to explain the reason for the escalation. b) The Labor and Delivery team utilizes a specialized paging service to call for a NICU resuscitation team when a crash C-Section is underway. The system takes a basic text description of the clinical scenario, the Operating Room number, etc. and broadcasts the information by priority page to all the NICU Response Team members simultaneously. c) An automated patient notification system sends a PPD converter their annual health screening reminder by email, requesting that they either log in to their secure PHR to complete the online survey, or call an automated VOIP line to submit their survey responses verbally. |
Project Facilitator | Emory Fry, MD |
Status | Archived |
SD Approval Date | Oct 22, 2013 |
TSC Approval Date | Nov 4, 2013 |
Type | Ballot - STU to Normative |
Objectives / Deliverables | Project Initiation - Target: 2013 May Service Requirements Specification - Target: 2013 July Initial Specification of Service Functional Model - Target: 2013 November Ballot for Comment - Target: 2014 January DSTU Ballot - Target: 2014 May DSTU Reconciled and Published - Target: 2014 Sept |
Next Milestone Date | 2019 September WGM |
Project End Date | 2019 September WGM |
Project Intent | Create New Standard |
Project Need | A generalized Communication Service is needed that other services, systems, and applications can use to facilitate the coordinated delivery of clinical care, to request human tasks to be completed, and to provide a set of APIs to deliver alerts/recommendations using standardized and ubiquitous communication modalities. The field of Communication is undergoing one of the most significant revolutions in its history. Voice communications have evolved from analog to digital to voice over IP (VoIP). New systems for email, video conferencing, and instant messaging (IM) are being introduced everyday. Integration of these separate systems into a unified, communications strategy is a priority for effectively communicating with patients in the near future. A Service that automates and unifies human and device communications in a common context promises to help optimize business processes, reduce latency, manage workflows, and eliminating device and media dependencies that create barriers to effective communication. |
Implementers | Cognitive Medical Systems Intermountain Healthcare |
Security Risks | |
External Drivers | |
Common Names / Keywords/ Aliases | |
Lineage | |
Dependancies | This project is intended to interface closely with the SOA/CDS modeling efforts, SAIF and consumer standards such as SMTP, VOIP and SMS. |
Project Document Repository | http://hssp.wikispaces.com/comms |
Backwards Compatibility | N/A |
External Vocabularies | |
Products | Functional Profile |
Joint Copyright? | No |
External Pjt Collaborators | Although no direct coordination is required, final outcome needs to be clearly communicated to other profilers basing their work on V3 messages/services. |
Realm | Universal |
HL7 Affiliate | |
Stakeholders | Clinical and Public Health Laboratories, Immunization Registries, Quality Reporting Agencies, Standards Development Organizations (SDOs) |
Vendors | Pharmaceutical; EHR, PHR; Equipment; Health Care IT; Clinical Decision Support Systems; Lab; HIS |
Providers | Clinical and Public Health Laboratories; Local and State Departments of Health; Healthcare Institutions (hospitals, long term care, home care, mental health) |
Ballot Cycle Info | 2018 May Ballot Cycle Info: NORMATIVE Ballot results: Met basic vote requirements. 0 Negatives to reconcile Document Name: HL7 Version 3 Specification: Unified Communication Service Interface, Release 1 - US Realm 2014 Sept Ballot Cycle Info: DSTU Ballot results: Met basic vote requirements. 0 Negatives to reconcile Document Name: HL7 Version 3 Specification: Unified Communication Service Interface, Release 1 Submitted By: Lorraine Constable 2014 Jan Ballot Cycle Info: COMMENT ONLY Ballot results: Met basic vote requirements. 0 Negatives to reconcile Document Name: HL7 Version 3 Specification: Unified Communication Service Interface, Release 1 - US Realm |
Misc Notes | 20-19 October: Received ANSI approval forHL7 Version 3 Standard: Event Publish & Subscribe Service Interface, Release 1 - US Realm. PMO archived. 2019 June: TSC approved Normative Publication Request for Unified Communication Service Interface, Release 1 Feb 2017: TSC approved STU Extension Request for HL7 Version 3 Specification: Unified Communication Service Interface, Release 1 (US Realm) at TSC Tracker 12745 was approved for 12 months through 2018-02-18. Feb 2015: TSC approved DSTU Publication Request of HL7 Version 3 Specification: Unified Communication Service Interface - Release 1 - US Realm for 24 months at TSC Tracker 5598 through February 18, 2017 |
U.S. Govt Interest? | Yes |
USRSC Approval | |
FMG Approval | Not Needed |
ARB Approval | |
Start Date | Oct 22, 2013 |
* A Project Insight User ID and password is required to access Project Insight. Contact the HL7 PMO at for more information.
Visit the Projects, Ballots and Standards Metrics Excel Report to view projects that are behind 120+ days along with other ballots and standards requiring a Work Group's attention.
Visit the Projects, Ballots and Standards Metrics Excel Report to view projects that are behind 120+ days along with other ballots and standards requiring a Work Group's attention.