Stream: FHIRcast
Topic: May Connectathon in Cologne
Isaac Vetter (May 03 2018 at 21:03):
Hi everyone,
If you're considering participating in the FHIRcast track during the FHIR Connectathon the weekend after next, don't forget to fill out the Pre-Connectathon Survey.
We're also having a prep call on Tues at 9am Central / 2p GMT / 4p CEST. (Email me if you want the invite).
Webex: https://epic.webex.com/epic-en/j.php?MTID=m39fee89dbb798e065c695b3aa1aa6444
Meeting number (access code): 803 558 190
Meeting password: mP3RJ67p
Isaac
Isaac Vetter (May 07 2018 at 15:56):
Hi everyone,
The FHIRcast Connectathon track prep call was earlier today. We talked through the following topics:
1. General Introduction to HL7 FHIR Connectathons
2. The FHIRcast specification
3. How to run the sandbox locally
4. The testing scenarios that we’re targeting
5. How to give feedback on the specification
If you missed it and are planning on participating in the track in person or remotely, here's your homework:
1. Complete the Pre-connectathon survey, it's quick!
2. Download and install the .Net Core SDK and the sandbox.
3. Read the FHIRcast specification
4. ?
5. Profit!
Brett Esler (May 11 2018 at 11:45):
hi all -trying to get the sequence in my head - here is a diagram we can work on...
Brett Esler (May 11 2018 at 11:45):
https://drive.google.com/file/d/12O91Sxd7pA6VbNZ3l_Dg-XQFD-0O1ggk/view?usp=sharing
Brett Esler (May 11 2018 at 11:45):
can use draw.io to edit...
Isaac Vetter (May 11 2018 at 11:47):
@Brett Esler , nice! You're abstracting a bit of the SMART EHR launch, which totally makes sense.
Brett Esler (May 11 2018 at 11:48):
ty - from this i am wondering whether we should or could allow external notification of context from subscriber; this addition sets up all the difficulty of broken context possibilities - is that a discussion that has happened before?
Isaac Vetter (May 11 2018 at 11:49):
Yes, but hasn't been fully written up / added the spec yet.
Isaac Vetter (May 11 2018 at 11:50):
The basic consensus is the subscribers do need to be able to post context changes to the hub, which would then have the responsibility for accepting/rejecting the change. If accepted the hub would broadcast the change to all subscribers.
Brett Esler (May 11 2018 at 11:50):
ok - will talk with you tomorrow on that one ;)
Isaac Vetter (May 11 2018 at 13:32):
@Brett Esler , just quickly wrote up this pull request to describe a simple technical mechanism, but not the all the possible error cases.
Isaac Vetter (May 12 2018 at 07:41):
Hey @Bas van den Heuvel , I wanted to point you to this PR that addresses a lot of the issues that we talked about this morning: https://github.com/fhircast/docs/pull/21
Brett Esler (May 13 2018 at 08:23):
HI @Isaac Vetter can you resolve https://10.211.55.4:8102/metadata
Isaac Vetter (May 13 2018 at 08:35):
@Martin Bellehumeur, can you navigate to: https://10.211.55.4:8102/metadata on the HL7MAY2018 network?
Brett Esler (May 13 2018 at 14:11):
YouTube of FHIRCast in action https://youtu.be/v3n9MQGES8I
Isaac Vetter (May 13 2018 at 15:05):
Isaac Vetter (May 17 2018 at 23:17):
The HL7 FHIR Connectathon was held this weekend in Cologne, Germany and an intrepid group of developers prototyped FHIRcast. Following implementer feedback at the January connectathon, we'd updated the spec to model a common webhook design pattern (specifically W3C's WebSub). Over the weekend, we implemented this new version of the spec and made heavy use of the excellent, opensource sandbox (recently published by @Leo Bergnéhr and @Niklas Svenzén from Sectra). Connectathon participants developed both hubs and clients. Check out @Brett Esler 's video.
We also continued to refine and enhance the specification; notably, PR #25 begins to define multiple launch and SSO scenarios using Oauth and PR #24 describes bidirectional synchronization -- both critically important.
In addition to the FHIR Dev Days - Boston tutorial on FHIRcast, a SIIM Roundtable is discussing how FHIRcast can solve integration problems lead by our very own @Brad Genereaux .
Interested? After reading the specification, check out our github site and look for progress on the below.
Isaac
### Discovered issues/questions
During the connectathon we identified a number of outstanding issues, both with the sandbox and the specification itself.
#### Specification:
• Issue #29: How can a subscribed app validate that it's subscription is active?
• Issue #28: How can a subscribed app determine session context immediately upon subscribing?
• Issue #27: Does the callback url need to be verified as belonging to the subscriber?
• Issue #26: How are new events defined? Can we create a swagger definition for events?
• Issue #33: Why must a subscriber have a publically accessible url?
#### Sandbox:
• Issue #5: Notification context from sandbox doesn't conform to spec.
• Issues #8: Url verification parameters from sand box doesn't conform to spec.
### What's next?
The future is bright! Next steps include:
1. Resolving the above issues and reviewing and incorporating PRs #24 and #25.
2. Continuing to build the implementer community and respond to feedback.
3. Ballot specification into HL7.
Last updated: Apr 12 2022 at 19:14 UTC
