Stream: FHIRcast
Topic: May connectathon, 2021
Isaac Vetter (May 18 2021 at 10:09):
Happy Connectathon, all! Let's use this topic to share hub urls!
Herczku Misi (May 18 2021 at 10:16):
Hello EveryOne!
SHS hub url (only websocket is supported):
https://siefhircasthub21.azurewebsites.net/
Samlpe usage requests for postman:
https://www.getpostman.com/collections/45e08d8c260eb25ba23e
Authentication is not needed currently.
Isaac Vetter (May 18 2021 at 10:24):
Also, from Bas, last week:
The Philips server for next weeks connecthaton is up and running. Instructions and url's can be found at: http://212.187.34.124/
Catie Ladd (May 18 2021 at 11:57):
Nuance Hub info:
Nuance Integration Guide:
https://connect2.nuancepowerscribe.com/psonesetup/PO-PowerCastIntegrationGuide.pdf
Hub endpoint:
https://powercast.stage.nuancepowerscribe.com/api/hub
Hub swagger endpoint:
https://powercast.stage.nuancepowerscribe.com/swagger/index.html
Hub will support Subscribe endpoint HTTP GET at base url. Any/all events are allowed. NOTE: Subscribe response does NOT confirm to STU2, but rather returns a json object with two fields: "websocket_endpoint" and "context".
Hub will support Notify at baseurl/topic (HTTP Post) per specification
We can use a topic of your choice, or we can choose one at the time of testing
Nuance clients will use and respond to the following events: DiagnosticReport-open, DiagnosticReport-update, DiagnosticReport-close, userLogoff
subscribe and notify require OAuth2 access token in Authorization header as "Bearer".
I will post bearer tokens each day, they last 24 hrs.
We have implemented content sharing of media, so that will be testable for our Hub as well.
Isaac Vetter (May 18 2021 at 14:02):
FHIRcast stand-up for implementers starting now!
Isaac Vetter (May 19 2021 at 17:31):
FHIRcast track report-out, any feedback?
FHIRcast
Summary
FHIRcast provides modern, simple, application context synchronization. As the number of production-grade releases of FHIRcast increases in 2021 tested interoperability of existing implementations using the STU2 specification.
Additionally, implementers tested prototyped functionality for an STU3 version of the specification.
Implementer Participants
Not including observers, implementers include: Siemens, Nuance, Vital Images, Philips, Epic
Topics of interest
Advanced UI integration beyond simple open and close of coarse context, enabling multiple disparate applications to communicate UI selection of finer-grained clinical concepts.
Improvements to synchronization error scenarios
Exchange of clinical content beyond simple exchange of coarse context information.
Now what?
Throughout 2021, the Infrastructure & Messaging work group has hosted FHIRcast design sessions investigating the above topics.
Design is continuing around these topics, likely to result in an STU2 version of the specification with the goal of preserving backward compatibility for the “simpler” context synchronization use-case well enabled in STU2.
Bas van den Heuvel (May 19 2021 at 17:56):
I've added a summary of the discussion on syncerror to https://github.com/HL7/fhircast-docs/issues/311
Attached the presentation used. SyncError.pptx
Isaac Vetter (May 19 2021 at 18:02):
Bas, updated reportout with the above.
Bas van den Heuvel (May 19 2021 at 18:10):
Created a new issue on github for select and added the event definition we discussed: https://github.com/HL7/fhircast-docs/issues/360
Catie Ladd (May 19 2021 at 20:27):
I wanted to say a big thank you to everyone who participated in our track this week. We had some great discussions! Thank you especially to @Isaac Vetter for organizing and leading the track, to @Herczku Misi for helping me present/demo our content sharing, to @Eric Martin for leading our content sharing discussion, and @Bas van den Heuvel for presenting and leading our syncerror discussion.
Bas van den Heuvel (Sep 08 2021 at 16:18):
The Philips FHIR cast server is up and running. Information on the different endpoints can be found on http://212.187.34.124/.
Last updated: Apr 12 2022 at 19:14 UTC
