Page tree
Skip to end of metadata
Go to start of metadata

Publication Request

Publication Request

1. Published Name of the Standard for which request is being made

HL7 FHIR® Implementation Guide: FHIRCast, Release 1, STU2

2. Standards Material/Document


3. Date of Request

Dec 15, 2020

4. Use Period

Two years

5. Reason for extension, timeline, and actions

6. Original Publication Date

7. End date of the current STU period

Dec 15, 2022

8. Length of the requested extension

9. Review Process

10. HL7 Work Group making this request and date

Imaging Integration

10a. Requesting WG Date

Dec 15, 2020

11. URL of approval minutes

12. HL7 Product Management Group


12a. Management Group Date of Approval

Dec 16, 2020

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

HL7 FHIR® Implementation Guide: FHIRCast, Release 1, STU2

19. Requested name for published standard

HL7 FHIR® Implementation Guide: FHIRCast, Release 1, STU2

20. If CMET, list IDs balloted

21. Project Insight Number


22. Document Realm


23. Ballot cycle in which the document was successfully balloted


24. Results of that ballot (following reconciliation activities):

24. Results of that ballot (following reconciliation activities):

(not needed for errata, STU extension, or unballoted STU update)

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

Jan 05, 2021

31. URL of publication material/ SVN repository

32. Publishing Facilitator

Isaac Vetter

33. Special Publication Instructions

1. Retrieve current specification zip from
2. Publish on

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

Imaging Integration

38. Date Product Brief Reviewed

Dec 15, 2020

39. Has the Product Brief changed?

Product Brief

Product Brief

40. Family


41. Section

Implementation Guides

42. Topic

Decision Support CCOW

43. Please Describe the Topic

44. Product Type

Implementation Guide

45. Parent standard


46. Parent Standard Status


47. Update/replace standard

HL7 FHIR® Implementation Guide: FHIRCast, Release 1, STU1

48. Common name/search keyword


49. Description

The FHIRcast specification describes the APIs used to synchronize disparate healthcare applications' user interfaces in real time, allowing them to show the same clinical content to a user (or group of users).



These are categories of potential users, implementers, or other interested parties such as those that are indicated on the Project Scope Statement under “Stakeholders/Vendors/Providers”. Select those that are applicable, or suggest others:

50. Stakeholders

Standards Development Organizations (SDOs)

51. Vendors

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

52. Providers

53. Benefits

• Enables standards-based support for modern, simple application context synchronization
• Supports patient safety in multi-application workflows such as imaging integration with EMR and dictation systems
• Reduces provider burden in multi-application workflows
• Improves security over current application integration mechanisms

54. Implementations/Case Studies

• Epic
• Epic
• Epic
• Epic
• Nuance
• Philips
• Sectra
• Siemens
• Multiple open source projects

55. Development Background

Once the subscribing app knows about the session, the app may subscribe to specific workflow-related events for the given session. The subscription is verified and the app is notified when those workflow-related events occur; for example, by the clinician opening a patient's chart. The subscribing app may initiate context changes by accessing APIs exposed by the Hub; for example, closing the patient's chart. The app deletes its subscription to no longer receive notifications. The notification message describing the workflow event is a simple json wrapper around one or more FHIR resources.

FHIRcast enables a subscriber to receive notifications either through a webhook or over a WebSocket connection. FHIRcast recommends the HL7 SMART on FHIR launch protocol for both session discovery and API authentication.