1. Published Name of the Standard for which request is being made (if previously published)

2. Standards Material/Document


3. Date of Request

May 09, 2019

4. Use Period

5. Reason for extension, timeline, and actions

6. Original Publication Date

7. End date of the current STU period

8. Length of the requested extension

9. Review Process

10. HL7 Work Group making this request and date

SOA 8/May/2019

10a. Requesting WG Date

11. URL of approval minutes


12. HL7 Product Management Group

12a. Management Group Date of Approval

13. URL of approval minutes

14. Is the artifact ready for final publication?


15. If not ready, please describe remaining steps.

16. Tool name used to produce the machine processable artifacts in the IG

17. The name of the “IG artifact” within the context of the above mentioned tool.

18. Balloted Name of the standard for which request is being made

Unified Communication Service Interface, Release 1

19. Requested name for published standard. See Naming Examples

HL7 Service Functional Model - Unified Communication Service

19a. Specification Feedback Name (For Search in Jira)

20. If CMET, list IDs balloted

21. Project Insight Number


22. Document Realm

US Realm

23. Ballot cycle in which the document was successfully balloted


25. Affirmative


26. Negative


27. Abstentions


28. Not Returned


29. Total in ballot pool


30. Date on which final document/standards material was supplied to HQ

May 09, 2019

31. URL of publication material/ SVN repository

See Balloted document - no changes

32. Publishing Facilitator

33. Special Publication Instructions

34. URL of ballot reconciliation document


35. Has the Work Group posted its consideration of all comments received in its reconciliation document on the ballot desktop?


36. Substantive Changes Since Last Ballot?


37. Product Brief Reviewed By


38. Date Product Brief Reviewed

May 08, 2019

39. Has the Product Brief changed?

40. Family


41. Section

Clinical and Administrative Domains

42. Topic

43. Please Describe the Topic

44. Product Type

45. Parent standard


46. Parent Standard Status

47. Update/replace standard


48. Common name/search keyword

Universal Communication Service UCS

49. Description

The Unified Communication Service complements existing SOA services by providing a Service Functional Model (SFM) for delivering alerts, recommendations, and other notifications using a variety of transport mechanisms including email, SMS, VOIP or other communication channels. The service provides for message routing and/or escalation to ensure that when the intended recipients are not available, appropriate surrogates can be notified in a timely manner.

50. Stakeholders

Clinical and Public Health Laboratories, Immunization Registries

51. Vendors

Pharmaceutical, EHR, PHR, Clinical Decision Support Systems, Lab, HIS

52. Providers

Clinical and Public Health Laboratories Emergency Services Local and State Departments of Health Healthcare Institutions (hospitals, long term care, home care, mental health)

53. Benefits

Unified communications allows services, systems, and applications to be used 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 using standardized, ubiquitous communication modalities. The integration of voice, email, video, instant messaging and any additional compliant communication medium, removes communication barriers and reduces latencies. Automatic escalations to address communication channel or receiver non-availability and improves the ability to ensure that communications are delivered promptly to an appropriate end-point

54. Implementations/Case Studies

Cognitive Computer Systems
Veteran's Administration

55. Development Background

This SFM was developed as part of the Health Services Specification Project (HSSP). As part of that process an implementation of the SFM was developed as an OMG specification and will be available on the OMG Healthcare web site. Whilst formally a US Realm specification due to lack of non-USA input into its development, this SFM does not contain any USA specific content or requirements

1 Comment

  1. New confluence form is excellent

    Minor - Services is duplicated in the category list