Stream: FHIRcast
Topic: Jan Connectathon track
Isaac Vetter (Jan 03 2019 at 14:51):
Hi FHIRcasters!
With the HL7 FHIR Connectathon a little over a week away, our track coordination call is starting in 10 minutes. Call details here: http://wiki.hl7.org/index.php?title=201901_FHIRcast
Isaac Vetter (Jan 03 2019 at 14:51):
If you're not able to make it, no worries, just reply with any questions.
Isaac Vetter (Jan 12 2019 at 14:06):
Hey FHIRcast people! We're at table 13 in the connectathon room.
Isaac Vetter (Jan 12 2019 at 14:57):
FHIRcast breakout session at noon-1p Central time (local San Antonio time). We're going to try to have a call-in as well for remote people.
Isaac Vetter (Jan 12 2019 at 14:58):
Here's the details:
Join Webex meeting
Meeting number (access code): 807 010 915
Meeting password: vY6MnAHc
Join from a video system or application
Dial 807010915@epic.webex.com
You can also dial 173.243.2.68 and enter your meeting number.
Join by phone
404-397-1525 US Toll
877-309-8689 US Toll Free
Global call-in numbers | Toll-free calling restrictions
Will Maethner (Jan 12 2019 at 18:07):
We are starting the webex and meeting in Llano for anyone interested.
Isaac Vetter (Jan 13 2019 at 21:36):
FHIRcast synchronizes healthcare applications in real time to show the same clinical content to a common user, by extending SMART on FHIR to achieve tight integration between disparate, full-featured applications. The FHIRcast specification models the common webhook design pattern and specifically the W3C WebSub RFC.
An intrepid group developers participated in our FHIRcast track during the HL7 FHIR Connectathon in San Antonio this weekend. @George Kustas from Nuance continued his work implementing the websockets for FHIRcast with @Martin Bellehumeur's opensource client and continues to provide his valuable real-world implementation perspective. @Bas van den Heuvel from Philips wrote both a hub and client in java, which he intends to make available on https://github.com/philipsonfhir. Bas also provided constructive feedback on the specification ahead of our ballot. @Will Maethner from Epic worked on his Hub implementation and successfully accepted subscriptions and communicated event notifications, and even began work on a client!
Since the September connectathon, we've strengthened the specification by specifying the ability for the client to query for current context as needed, but also by designing and testing a websockets implementation. @Martin Bellehumeur has made tremendous contributions this fall and winter in the form of his opensource javascript sandbox, Swift client, .Net client and youtube video(https://www.youtube.com/watch?v=iHNSBg0Kn3M&feature=youtu.be).
Here's some of our in-flight or recent changes:
- Optional support for websockets instead of web hooks
- Informative description of synchronization failure considerations
- Informative description of security considerations for FHIRcast implementers
- Add capability for the client to query for current context
We've also made a few smaller updates that clarify the specification, such as:
- Clarifying that the subscriber should respond with an HTTP 200 upon an event notification.
- Fixes some typos in the specification around the event names (https://github.com/fhircast/docs/pull/39)
Next Steps:
- Look forward to our continued work on the experimental websockets specification.
We're tentatively planning on balloting FHIRcast into HL7 this spring!
Last updated: Apr 12 2022 at 19:14 UTC
