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

2. Standards Material/Document

 Normative

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

 https://confluence.hl7.org/display/SOA/SOA+May+2019+WGM+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?

 No

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

 Event Publish & Subscribe Service Interface, Release 1

19. Requested name for published standard. See Naming Examples

 HL7 Service Functional Model: Event Publish & Subscribe Service Interface, Release 1

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

20. If CMET, list IDs balloted

21. Project Insight Number

 1051

22. Document Realm

 Universal

23. Ballot cycle in which the document was successfully balloted

 2018-May

25. Affirmative

 11

26. Negative

 0

27. Abstentions

 73

28. Not Returned

 13

29. Total in ballot pool

 97

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

31. URL of publication material/ SVN repository

32. Publishing Facilitator

33. Special Publication Instructions

34. URL of ballot reconciliation document

 http://www.hl7.org/documentcenter/public/ballots/2018MAY/reconciliation/recon_v3_soa_epssrvint_r1_n1_2018may.xls

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

 Yes

36. Substantive Changes Since Last Ballot?

 No

37. Product Brief Reviewed By

 SOA WG

38. Date Product Brief Reviewed

 May 08, 2019

39. Has the Product Brief changed?

40. Family

 Cross-Paradigm

41. Section

 Clinical and Administrative Domains, Rules and References

42. Topic

43. Please Describe the Topic

44. Product Type

45. Parent standard

 N/A

46. Parent Standard Status

47. Update/replace standard

 N/A

48. Common name/search keyword

 HL7 Pub/Sub service

49. Description

 The Event Publish and Subscribe Service complements existing HL7 SOA services by providing a Service Functional Model (SFM) for services,
components and systems to subscribe to clinical events of interest and receive notice when new data is available.
The service supports two common forms of filtering: topic-based and content-based.

50. Stakeholders

 Clinical and Public Health Laboratories, Immunization Registries, Standards Development Organizations (SDOs)

51. Vendors

 Pharmaceutical, EHR, PHR, Health Care IT, Clinical Decision Support Systems, Lab

52. Providers

 Healthcare Institutions (hospitals, long term care, home care, mental health)

53. Benefits

 A generalized Event Publish & Subscribe Service is needed as a foundation for a wide variety of applications, including new result feeds, content syndication, rich presence and clinical workflow systems. In general, Pub/Sub offers:
(a) event subscribers to be easily added, managed, and notified
(b) Consumer empowerment, allowing stakeholders to manage their own data requirement.
(c) Efficient resource utilization via forward messages only to interested parties.
(d) Enhanced performance and scalability

54. Implementations/Case Studies

 Cognitive Computer Systems
Veteran's Administration
Tesltra Health

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.