Stream: FHIRcast
Topic: Sept FHIRcast Connectathon
Isaac Vetter (Jul 23 2019 at 14:40):
The Sept FHIRcast Connectathon (in Atlanta, Georgia, USA) will focus on three areas:
1) Basic connectivity & testing of the STU1 spec
2) Websocket support using the draft spec, here: FHIRcast websocket support
3) How the heck should we exchange draft, discrete measurements?
Check out the Connectathon track description & orientation call details.
Isaac Vetter (Sep 03 2019 at 14:51):
Hey Guys - we'll be having a breakout session bright and early Saturday morning at 9a. Be there or be sqaure! @Paul Curcio @Bas van den Heuvel
Isaac Vetter (Sep 03 2019 at 14:52):
If you're planning on attending the connectathon track and weren't able to attend our orientation call this morning, mind replying here? @George Kustas @Ashish Singh @Wouter Devriendt
Bas van den Heuvel (Sep 04 2019 at 08:57):
Ouch that is early :grinning: - will there be coffee?
I'll be there.
George Kustas (Sep 04 2019 at 16:56):
Hey guys... Sorry I've been out of the loop these last few weeks. If it's OK, I'd like to call in to the meeting. We have our hub available for testing (including websockets). I'd also like the opportunity to present some other things we're doing with the Observation resource and "prior studies" in the imagingStudy resource. I'll get something out here on Zulip within the next couple of days in case you are interested.
Isaac Vetter (Sep 04 2019 at 17:32):
@George Kustas that sounds great.
Isaac Vetter (Sep 04 2019 at 18:19):
Don't forget to fill out the pre-connectathon survey if you're planning on participating!
George Kustas (Sep 06 2019 at 15:46):
I welcome anyone to connect and test with our FHIRCast Hub in the cloud. The hub conforms to the STU1 specifications and also supports WebSockets as documented here: https://github.com/HL7/fhircast-docs/wiki/Websocket-proposal.
The hub base URL is https:/connect.nuancepowerscribe.com/fhirhub/api/hub/
I plan on remotely attending the 9 AM breakout session from 9-11. I will have a test application that I can use to join in a FHIRCast session over our hub or other hub implementations.
@Isaac Vetter what number can I call in on, or better yet, is there a gotomeeting available?
Isaac Vetter (Sep 14 2019 at 03:09):
@George Kustas , as requested!
Meeting number (access code): 801 514 263
Meeting password: yHZ6wHSP
_Join by phone_
Tap to call in from a mobile device (attendees only)
404-397-1525 US Toll
877-309-8689 US Toll Free
Global call-in numbers | Toll-free calling restrictions
Isaac Vetter (Sep 14 2019 at 12:39):
The FHIRcast breakout is in Room M 103 a bit after 9a.
Isaac Vetter (Sep 14 2019 at 16:01):
Hey @George Kustas , @Will Maethner is successfully exchanging websocket notifications with your hub running locally!
Isaac Vetter (Sep 14 2019 at 16:01):
I'm trying to connect to your hosted hub, here: https://connect.nuancepowerscribe.com/fhirhub/api/hub/; however, a simple subscription request fails:
Isaac Vetter (Sep 14 2019 at 16:01):
HTTP POST https://connect.nuancepowerscribe.com/fhirhub/api/hub/ Content-Type: application/x-www-form-urlencoded hub.mode=subscribe&hub.topic=fba7b1e2-53e9-40aa-883a-2af57ab4e2c&hub.secret=shhh-this-is-a-secret&hub.events=patient-open,patient-close&hub.channel.type=websocket
Isaac Vetter (Sep 14 2019 at 16:02):
My impression is that your hub will accept any topic and doesn't require authentication. If you have a chance today, are you able to easily identify what I'm doing wrong?
Paul Curcio (Sep 14 2019 at 16:19):
This POST body seems to work though:
hub.mode=subscribe&hub.events=open-imaging-study&hub.topic=DrXRay&hub.channel.type=websocket
Paul Curcio (Sep 14 2019 at 16:31):
However, if I try this via a simple React app I'm cooking up (using fetch), I get a 202 response but no body (blank string, no "wss://" url in there)
George Kustas (Sep 14 2019 at 21:12):
I will look at the logs right now @Isaac Vetter to see what happened to your subscription request. @Paul Curcio the posting of notification events over websockets is actually not supported anymore in the specifications. We agreed that only hub->client event notifications will be sent over websockets, because that is the only situation where a client would need to "host" a secure web site otherwise. The clients should use the REST POST for event notifications. Finally, @Isaac Vetter I agree the the intent verification is unnecessary.
George Kustas (Sep 14 2019 at 21:27):
@Paul Curcio - while what I said about sending events over websocket events is true, I just re-read your post and realize you were not trying to do so :-|
The question is why your Subscribe worked and Isaac's did not. I'll get back to you both.
George Kustas (Sep 14 2019 at 21:30):
@Isaac Vetter Looking at my log files, my hub isn't seeing any of the querystring after the topic, which makes me suspicious of the hyphens in your topic string. Paul's subscribe did work using a topic of DrXRay. I think a GUID without the hyphens might work. I'll verify, but you can try giving that a shot.
Isaac Vetter (Sep 14 2019 at 21:37):
George, Fyi, Will's got your hub working locally over websockets with his own client.
Paul Curcio (Sep 14 2019 at 21:53):
@George Kustas I don't think I ever had a hyphen in my topic name from the React app I put together ... my subscribes work from Postman but not from the React app running in Chrome. (For what it's worth, I also tried subscribing via Node directly to sidestep any potential CORS-type issues, and still got the same blank response.) If there's anything I can do to help you find my requests in your logs, please let me know.
George Kustas (Sep 14 2019 at 21:59):
Thnks @Paul Curcio . So, this is a React-native app or react in a web browser? Try sending another request and use a differnt topic name or something so that I can easily spot it in the logs. I'll let you know what I see. THANKS!
Paul Curcio (Sep 14 2019 at 22:15):
See if you can find a request with the payload below, sent just now... this is a React app in a browser, to answer your question.
hub.channel.type: "websocket" hub.events: "open-imaging-study" hub.mode: "subscribe" hub.topic: "HiGeorgeImDebugging"
George Kustas (Sep 14 2019 at 22:25):
I'm seeing the following error in the logs. Are you sending form data?
2019-09-14 17:57:40.0626|13|ERROR|Microsoft.AspNetCore.Server.Kestrel|Connection id "0HLPP4MDQ2H4H", Request id "0HLPP4MDQ2H4H:00000003": An unhandled exception was thrown by the application. System.InvalidOperationException: Incorrect Content-Type
George Kustas (Sep 14 2019 at 22:45):
OK, nothing wrong with hyphens in the topic name. I added some additional logging to identify the client host name/ip and to display raw form data. I hope to be able to speak with you guys live tomorrow at some point. I left my calendar open!
Paul Curcio (Sep 14 2019 at 23:17):
What content type are you expecting? Was using x-form-url-encoded (or whatever the proper version of that is). It doesn’t like it if I omit the content-type header entirely (I get a 500 in that case)
George Kustas (Sep 15 2019 at 13:10):
Hey @Paul Curcio , if you are using Chrome, open the web inspector and go to the "Network" tab. You will be able to examine your HTTP request from there, and make sure the headers and everything looks right.
Bas van den Heuvel (Sep 15 2019 at 13:32):
I've uploaded to demo I showed yesterday to https://github.com/PhilipsOnFhir/fhir-cast/tree/develop.
It contains a SmartOnFhir based implementation of FHIRCast, using websockets to send events (rest is also supported but currently not used).
George Kustas (Sep 15 2019 at 14:09):
Hey @Bas van den Heuvel , looking at your code now. Is there anything there that will help us figure out a way to launch our client executables using Smart on Fhir? There are a lot of projects (angular and java) in this code. I'm familiar with typescript but not angular. I can understand Java, but more familiar with C++ and C#.
Paul Curcio (Sep 15 2019 at 14:28):
An update on where I am - I'm able to subscribe via POST to the hub, and establish the WebSockets connection (and I'm getting the initial "subscribe" event coming through). However, if I try sending events via the application at https://hub-fhircast.azurewebsites.net/websocket (using https://connect.nuancepowerscribe.com/fhirhub/api/hub as the hub), I don't seem to be getting events sent to my socket on the client side.
Isaac Vetter (Sep 15 2019 at 15:45):
Great update, @Paul Curcio . @George Kustas - do you have any thoughts?
Isaac Vetter (Sep 15 2019 at 16:16):
Hey @Bas van den Heuvel , @Will Maethner , @Paul Curcio , @George Kustas. Great work this weekend! Any feedback on this proposed report-out?
Paul Curcio (Sep 15 2019 at 16:20):
Looks good to me!
George Kustas (Sep 15 2019 at 18:02):
Looks great Isaac. I posted two proposals in fhircast-docs: New "get current context", and DiagnosticReport events). Both are very rough and need more discussion and refinement before we can actually create true specifications. I am currently working on a third which is a proposal to support the DiagnosticReport resource for specifying one or more results (Observation resources). This would most likely be a DiagnosticReport-update event. The Observation could be a measurement or some other clinical finding.
George Kustas (Sep 15 2019 at 18:15):
@Paul Curcio - Let's work offline soon and see if we can figure out what happened in your latest tests. I can't tell by looking at the logs.
George Kustas (Sep 15 2019 at 21:23):
Hey @Will Maethner . @Isaac Vetter , @Paul Curcio , @Bas van den Heuvel
I just updated our Nuance sandbox to remove intent verification for websockets.
Isaac Vetter (Sep 15 2019 at 22:12):
George, as soon as we feel reasonably confident that the stu1 version is right. I'll snapshot it and begin integrating the websockets spec in.
Catie Ladd (Sep 08 2021 at 18:46):
I'm not seeing anything on the Whova agenda for our FHIRCast track. Am I searching incorrectly or is nothing posted yet?
Isaac Vetter (Sep 08 2021 at 20:37):
Hey Catie, it's not posted yet.
Isaac Vetter (Sep 09 2021 at 16:16):
Hey @Catie Ladd , @Eric Martin , @Bas van den Heuvel -- does this schedule look okay to you? (Note that I'm aggressively listing you as a potential "speaker" in a few sessions).
image.png
https://confluence.hl7.org/display/FHIR/Connectathon+Session+Capture+28
Eric Martin (Sep 09 2021 at 16:34):
Surprisingly the times you have me listed both work for me. Yay!
Regards…
Eric
Isaac Vetter (Sep 09 2021 at 17:00):
HL7 HQ is loading them into whova now. (giant shoutout to Mary Ann and Sandy :heart: ).
Catie Ladd (Sep 09 2021 at 17:09):
Looks good to me too.
Isaac Vetter (Sep 09 2021 at 17:42):
Fyi - I added a 1/2 hr session on Tues late morning about home-open, image.png
Alexander Z Liu (Sep 09 2021 at 18:53):
Hello All!
Ahead of the upcoming FHIRcast Connectathon track, we are hoping to get those who are interested up and running to test with Epic's FHIRcast hub implementation. In that effort, there are a few things that would be useful to review and set up before we come together next week.
We have published documentation available for the list of supported events and more in-depth documentation of the communication framework.
To get access to Epic's FHIRcast hub implemention, there are a few important steps that require some advanced notice and approval so it is recommended to try to complete the setup described here before Monday, September 13th. Please don't hesitate to reach out with any questions and I look forward to seeing you next week!
Bas van den Heuvel (Sep 10 2021 at 09:02):
Most of it looks good. I have to join some of the other tracks as well. I would appreciate it if the content and subscription meeting can be moved up one hour.
Catie Ladd (Sep 14 2021 at 12:19):
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 conform 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.
There is a test client that can be used to jump start your integration, or to use as an example for your coding located here:
https://github.com/fhircast/.net/tree/master/TestPowerCast
Access Token 1: eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6Ik1qTkVRa014TkVVd1F6UXdRVFJFUVRBNU9UWTNRalUzT1RoQk16QXdPRUpCTXpNeVJqWkJRZyJ9.eyJodHRwczovL251YW5jZWhkcC5jb20vYWxpYXMiOiJBcHBsaWNhdGlvbnxOdWFuY2VQb3dlckNhc3RUZXN0MSIsImlzcyI6Imh0dHBzOi8vbnVhbmNlaGRwLmF1dGgwLmNvbS8iLCJzdWIiOiJERTJKdFZmVFZjb2lVeGplc2E0bW5seEZSMjhGVGFVTEBjbGllbnRzIiwiYXVkIjoiaHR0cHM6Ly9udWFuY2VoZHAuY29tL1Bvd2VyQ2FzdC9IdWIiLCJpYXQiOjE2MzE2Mjk2MzQsImV4cCI6MTYzMTcxNjAzNCwiYXpwIjoiREUySnRWZlRWY29pVXhqZXNhNG1ubHhGUjI4RlRhVUwiLCJzY29wZSI6IkFkbWluIiwiZ3R5IjoiY2xpZW50LWNyZWRlbnRpYWxzIiwicGVybWlzc2lvbnMiOlsiQWRtaW4iXX0.aLu_42OCoHEenOhnicR6fqfDhqOP3YM8nYfOK4p2cCHzrcB0gV2aDM5TGEVL4R9rqRp5rYdN-7Xpglvmjew-h6lQkapLVw0irzkSFeJNze1gQnciDYYVZJBsSSNeKVPuQ_nFh8oj7VYPegkpTCKwedkUenjoj5tCdSiUnzl54XU3qwj45eIfZy9yD8un3-Kwz_bY7CRsADn4clCG62-C4wLS6B4OgRG1RBHUgfRKL8Ho-9UCz_v8FaF9KPgJfwRdEl91i9m9XoKAl8PUjqaSo6DrIVSpPp4xG4vCa6YbBmRCfC5kbVmYdtyIORFZAR7quCUDzoMEepUqbqfuyo72xg
Access Token 2:
eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6Ik1qTkVRa014TkVVd1F6UXdRVFJFUVRBNU9UWTNRalUzT1RoQk16QXdPRUpCTXpNeVJqWkJRZyJ9.eyJodHRwczovL251YW5jZWhkcC5jb20vYWxpYXMiOiJBcHBsaWNhdGlvbnxOdWFuY2VQb3dlckNhc3RUZXN0MiIsImlzcyI6Imh0dHBzOi8vbnVhbmNlaGRwLmF1dGgwLmNvbS8iLCJzdWIiOiJKSWtORDFxSlhjT0w0d0ZtcEppUUhmMmlYVWs3UzRSbUBjbGllbnRzIiwiYXVkIjoiaHR0cHM6Ly9udWFuY2VoZHAuY29tL1Bvd2VyQ2FzdC9IdWIiLCJpYXQiOjE2MzE2Mjk2OTQsImV4cCI6MTYzMTcxNjA5NCwiYXpwIjoiSklrTkQxcUpYY09MNHdGbXBKaVFIZjJpWFVrN1M0Um0iLCJzY29wZSI6IkFkbWluIiwiZ3R5IjoiY2xpZW50LWNyZWRlbnRpYWxzIiwicGVybWlzc2lvbnMiOlsiQWRtaW4iXX0.pf5v6k__zh9OJQsygXHIIskeOS_Ul8Mq-V0tS364k6i_TsPGrvqataDruY1zNAXpn16c20OD9kTzMQ7dCjCORNuNPetVwrWhSH2YM2fKSMw13tb7CTq_WbQap_HwLNHmS7I6m2kI_o52Gyum6I40iPG0IetM_T5mJN0-kqNsgzQMoFUIqVRI9tn8dkCQJnZYU1uZMbKlSPjTQJXnaYd0pY6XmblT3Qiy9sdhZxJzdLpo_dPImcK-vX7clDb7hhjEzlLwccKoAfeC34ZjCvEjSTYUVnaX8yoCy1V5PdkgH5FdsNYSe5uiMpHHAOeKfrjTQ1OK3HWQBxRr3qI2ZfFxGw
Stanislav Melnikov (Sep 14 2021 at 12:52):
Smart Reporting Hub info:
STU-2 conformed:
Hub IP address: http://3.67.90.180
Authentication:
Header: Authorization APIKEY testApiKey
Supported events:
Patient-open
Patient-close
ImagingStudy-open
ImagingStudy-close
userLogout
userHibernate
syncerror
The hub accepts subscriptions on new and existing topics, context change events and broadcasts events to subscribers.
Not STU-2 conformed:
Hub IP address: http://35.157.93.103
Authentication:
Header: Authorization APIKEY testApiKey
Supported events:
Patient-open
Patient-close
ImagingStudy-open
ImagingStudy-close
DiagnosticReport-open
DiagnosticReport-update
DiagnosticReport-close
DiagnosticReport-select
userLogout
userHibernate
syncerror
The hub accepts subscriptions on new and existing topics, context change events and broadcasts events to subscribers.
Differences from STU-2:
Response for a subscription returns a json object with two fields: "websocket_endpoint" and "context".
Herczku Misi (Sep 14 2021 at 14:29):
Hello EveryOne!
Siemens Healthineers 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.
Stanislav Melnikov (Sep 14 2021 at 14:48):
Successfully connected to the Nuance hub. Sent Imaging-Study-open response: 200. After a few seconds WebSocket connection was terminated: Web socket endpoint terminated connection abnormally: 1006, reason: Unexpected Status of SSLEngineResult after an unwrap() operation
Stanislav Melnikov (Sep 14 2021 at 14:52):
Successfully connected to the Siemens hub. Subscription is successful. Websocket endpoint is received. My json parser (standard net.sf.json) could not parse response to subscription. It was formatted as a string, not as a JSON (with extra " characters).
Catie Ladd (Sep 14 2021 at 14:53):
I'm getting into our logs now, I'll see what comes up @Stanislav Melnikov
Catie Ladd (Sep 14 2021 at 15:05):
Everyone, I just updated our URLS in my message above to point to our staging environment instead of our dev environment. Please update your URLs accordingly. The same auth tokens will still work.
Stanislav Melnikov (Sep 14 2021 at 15:25):
Successfully connected to Philips hub. Subscribed for a topic. Event "imaging-study-open" returned code 404
Stanislav Melnikov (Sep 14 2021 at 15:28):
Is there any possibility to connect to the Epic hub with own client?
Herczku Misi (Sep 14 2021 at 15:40):
Successfully connected to Smart hub, both, but mostly tested the"Not STU-2 conformed".
Subscription was successful. ImagingStudy-open was successful. Event notification through websocket arrived. After another subscription request, the response contained the ImagingStudy context. Then I tried to send another context change, but I got "There is an unconfirmed subscription in this event notification broadcast","code":2" What does that mean "unconfirmed" subscription? Is there a way to get the context from the hub?
Stanislav Melnikov (Sep 14 2021 at 15:46):
Herczku Misi said:
Successfully connected to Smart hub, both, but mostly tested the"Not STU-2 conformed".
Subscription was successful. ImagingStudy-open was successful. Event notification through websocket arrived. After another subscription request, the response contained the ImagingStudy context. Then I tried to send another context change, but I got "There is an unconfirmed subscription in this event notification broadcast","code":2" What does that mean "unconfirmed" subscription? Is there a way to get the context from the hub?
Well, unconfirmed subscription means that your client did not confirm the subscription. You subscribed twice for the same topic. You should confirm it twice. It can be that the hub is confused. I have to check how it can happen. Thanks for the testing!
Alexander Z Liu (Sep 14 2021 at 16:35):
Stanislav Melnikov said:
Is there any possibility to connect to the Epic hub with own client?
There are a few steps to get access to the client test harness we have available. Those steps are documented here: https://open.epic.com/Prototype/HyperdriveDownload
Specifically step 3 describes the process to request a Client ID to get access use the Subspace/FHIRcast APIs.
Herczku Misi (Sep 14 2021 at 17:49):
@Stanislav Melnikov
Thanks, then I think the error message came because the second subscription request was sent by postman, which is not establishing websocket connection, therefore it is not confirmed.
Álvaro Sánchez (Sep 14 2021 at 17:53):
Hey @Alexander Z Liu , I could not find an endpoint to the Epic Hub in the thread above, could you point me to it? Or is it necessary to log in through https://open.epic.com/Account/LogOn to get an endpoint?
Ryan Becker (Sep 14 2021 at 18:16):
I was successfully subscribing to the dev hub instance but failing thesame subscribe with the same access tokens to the stage instance. Any idea what I could have misconfigured? @Catie Ladd
Ryan Becker (Sep 14 2021 at 18:16):
Could anyone point me to the documentation for the Philips hub? Thanks!
Álvaro Sánchez (Sep 14 2021 at 18:19):
Catie Ladd said:
I'm getting into our logs now, I'll see what comes up Stanislav Melnikov
I could also reproduce the issue @Catie Ladd , it happened after < 2 min idling without messages:
2021-09-14 20:15:19.739 [WebSocketClient-SecureIO-1] INFO c.s.f.HubWebsocketClient - Received a message
Enter a command ('quit' for quiting).
2021-09-14 20:16:42.998 [WebSocketClient-SecureIO-1] INFO c.s.f.HubWebsocketClient - Web socket endpoint terminated connection abnormally: 1006, reason: Unexpected Status of SSLEngineResult after an unwrap() operation
Catie Ladd (Sep 14 2021 at 18:36):
Álvaro Sánchez said:
Catie Ladd said:
I'm getting into our logs now, I'll see what comes up Stanislav Melnikov
I could also reproduce the issue Catie Ladd , it happened after < 2 min idling without messages:
2021-09-14 20:15:19.739 [WebSocketClient-SecureIO-1] INFO c.s.f.HubWebsocketClient - Received a message Enter a command ('quit' for quiting). 2021-09-14 20:16:42.998 [WebSocketClient-SecureIO-1] INFO c.s.f.HubWebsocketClient - Web socket endpoint terminated connection abnormally: 1006, reason: Unexpected Status of SSLEngineResult after an unwrap() operation
@Álvaro Sánchez which environment are you going against? I first posted URLs for our DEV environment, but have updated them to our STAGING which is preferred.
Catie Ladd (Sep 14 2021 at 18:39):
Ryan Becker said:
I was successfully subscribing to the dev hub instance but failing thesame subscribe with the same access tokens to the stage instance. Any idea what I could have misconfigured? Catie Ladd
@Ryan Becker - I just tested against our STAGING urls with both tokens and was successful on subscribe and unsubscribe requests. Possibly just a copy/paste error?
Álvaro Sánchez (Sep 14 2021 at 18:40):
Catie Ladd said:
Álvaro Sánchez which environment are you going against? I first posted URLs for our DEV environment, but have updated them to our STAGING which is preferred.
Using stage: https://powercast.stage.nuancepowerscribe.com/api/hub . Connects/subscribes perfectly, posting is-open/close without problems. Only after some idle time get this disconnection issue. We had a similar problem when deploying the hub on Kubernetes, we suspected some config on the nginx-ingress-controller messing with our websocket.
Catie Ladd (Sep 14 2021 at 18:41):
Álvaro Sánchez said:
Catie Ladd said:
Álvaro Sánchez which environment are you going against? I first posted URLs for our DEV environment, but have updated them to our STAGING which is preferred.
Using stage:
https://powercast.stage.nuancepowerscribe.com/api/hub
Hmm... we use this environment all the time and don't typically have socket connection errors. I'll look at our logs in staging (our logs in dev are not currently working, hence the environment switch).
Ryan Becker (Sep 14 2021 at 18:47):
Catie Ladd said:
Ryan Becker said:
I was successfully subscribing to the dev hub instance but failing thesame subscribe with the same access tokens to the stage instance. Any idea what I could have misconfigured? Catie Ladd
Ryan Becker - I just tested against our STAGING urls with both tokens and was successful on subscribe and unsubscribe requests. Possibly just a copy/paste error?
Was using a different auth header key per another hub. Working fine now, thanks!
Isaac Vetter (Sep 14 2021 at 19:11):
Hey @Bas van den Heuvel , should this server work as a FHIRcast hub? http://212.187.34.124/ ?
Bas van den Heuvel (Sep 14 2021 at 19:22):
That is the root -- the FHIRcast server is hosted at http://212.187.34.124:9450/api/sync/fhircast/
Alexander Z Liu (Sep 14 2021 at 19:23):
Álvaro Sánchez said:
Hey Alexander Z Liu , I could not find an endpoint to the Epic Hub in the thread above, could you point me to it? Or is it necessary to log in through https://open.epic.com/Account/LogOn to get an endpoint?
The URL will be different between sessions of Hyperdrive and can be discovered. This process is explained in greater detail in the Initialization Sequence section of the Subspace Framework Documentation here: https://open.epic.com/Content/specs/staged/Subspace%20Communication%20Framework%20Overview.pdf
Stanislav Melnikov (Sep 14 2021 at 19:41):
To get topic state from the not STU2 conformed Smart Reporting hub you can use the following endpoint:
http://35.157.93.103/topicState/{topic-id}
Stanislav Melnikov (Sep 14 2021 at 19:46):
here is a respond received from the Siemens hub after a subscription request:
"{\"websocket_endpoint\":\"wss://siefhircasthub21.azurewebsites.net/ebc11228-a570-4f6f-90e2-b861dbf05d00\",\"contexts\":[{\"contextType\":\"ImagingStudy\",\"context\":[{\"key\":\"patient\",\"resource\":{\r\n \"resourceType\": \"Patient\",\r\n \"id\": \"ewUbXT9RWEbSj5wPEdgRaBw3\",\r\n \"identifier\": [\r\n {\r\n \"system\": \"urn:oid:1.2.840.114350\",\r\n \"value\": \"185444\"\r\n },\r\n {\r\n \"system\": \"urn:oid:1.2.840.114350.1.13.861.1.7.5.737384.27000\",\r\n \"value\": \"2667\"\r\n }\r\n ]\r\n}},{\"key\":\"study\",\"resource\":{\r\n \"resourceType\": \"ImagingStudy\",\r\n \"id\": \"8i7tbu6fby5ftfbku6fniuf\",\r\n \"status\": \"available\",\r\n \"subject\": {\r\n \"reference\": \"http://fhirserver.org/Patient/ewUbXT9RWEbSj5wPEdgRaBw3\"\r\n },\r\n \"started\": \"2018-07-07T08:01:20+00:00\",\r\n \"numberOfSeries\": 1,\r\n \"numberOfInstances\": 1,\r\n \"series\": [\r\n {\r\n \"uid\": \"2.16.124.113543.6003.2588828330.45298.17418.2723805630\",\r\n \"number\": 3,\r\n \"modality\": {\r\n \"system\": \"http://dicom.nema.org/resources/ontology/DCM\",\r\n \"code\": \"CT\"\r\n },\r\n \"description\": \"CT Surview 180\",\r\n \"numberOfInstances\": 1,\r\n \"bodySite\": {\r\n \"system\": \"http://snomed.info/sct\",\r\n \"code\": \"67734004\",\r\n \"display\": \"Upper Trunk Structure\"\r\n }\r\n }\r\n ],\r\n \"meta\": {\r\n \"versionId\": \"0\"\r\n }\r\n}}]}]}"
Ryan Becker (Sep 14 2021 at 20:02):
@Catie Ladd dr-open.json
Álvaro Sánchez (Sep 15 2021 at 13:51):
Alexander Z Liu said:
The URL will be different between sessions of Hyperdrive and can be discovered. This process is explained in greater detail in the Initialization Sequence section of the Subspace Framework Documentation here: https://open.epic.com/Content/specs/staged/Subspace%20Communication%20Framework%20Overview.pdf
Thanks for the heads-up @Alexander Z Liu . @Stanislav Melnikov applied for the account but did not receive any response yet
Ryan Becker (Sep 15 2021 at 14:20):
@Bas van den Heuvel is there an existing topic on the Philips hub that should be used to connect? I am getting a "topic not found" when specifying my own
Bas van den Heuvel (Sep 15 2021 at 14:20):
Topic1 to Topic9
Isaac Vetter (Sep 15 2021 at 14:26):
Hey @Bas van den Heuvel - want to do an FHIRcast implementer demo in 35 minutes? It's okay if not.
Bas van den Heuvel (Sep 15 2021 at 14:34):
Isaac, I've been given the same demo for last X tracks. I think it is better if the others show what they have.
Catie Ladd (Sep 15 2021 at 14:52):
@Bas van den Heuvel - our demo is very similar to last time's as well. I would say a demo of your system would be valuable as an example of multi-tab, which we cannot show.
Bas van den Heuvel (Sep 15 2021 at 14:58):
Too bad that part is not working very well right now :(
Bas van den Heuvel (Sep 15 2021 at 15:02):
Somehow I broke something and I'm not sure where. Sorry
Isaac Vetter (Sep 15 2021 at 21:07):
Friends, great work yesterday and today! Report-out for our track is here: https://docs.google.com/document/d/1YwlWckE69LXUvSAtgJyzz5OmCvE-NqwE/edit#heading=h.fyk0mqsomft6
Look okay to you?
Catie Ladd (Sep 15 2021 at 21:14):
Looks good to me, thanks @Isaac Vetter !
Ryan Becker (Sep 16 2021 at 13:14):
Looks good, Thank you @Isaac Vetter !
Bas van den Heuvel (Sep 16 2021 at 13:32):
@Isaac Vetter good summary
Herczku Misi (Sep 23 2021 at 16:09):
Hi @Álvaro Sánchez @Stanislav Melnikov , Sorry for the late answer, but I thought better later then never. I updated our hub (https://siefhircasthub21.azurewebsites.net/), now I hope you can parse the response for the subscription request. I would appreciate your feedback. (and also Let's direct this conversation to outlook.)
Last updated: Apr 12 2022 at 19:14 UTC
