Stream: cds hooks
Topic: May 2020 Connectathon
Dennis Patterson (Apr 16 2020 at 16:18):
Hi everyone!
The HL7 FHIR Connectathon 24 is coming up quickly on May 13-15! The CDS Hooks Track contains scenarios around 1.0 specification integrations, as well as opportunities to implement 1.1 candidate functionality. Head over to HL7's registration page to formally sign up for the event.
While all of our prior track instances have greatly benefited from pre-coordination between CDS Clients and Services, you can imagine how much more important that will be this time. Sign up on our Google Spreadsheet if you plan to participate, indicating who you are, what time zone you're in, and information about your CDS Client/Server + what you're wanting to test. Coordination across time zones will bring a new dynamic to the event, and having yourself in this spreadsheet will help immensely.
Reach out if you have questions, or feel free to start chiming in here if you want to start setting up your integrations!
Isaac Vetter (Apr 21 2020 at 16:52):
Hey Dennis, is there a track orientation call scheduled for this track yet?
Dennis Patterson (Apr 21 2020 at 19:31):
Not yet. Coming soon. I was hoping to get some sign-ups on the tracking spreadsheet so I'd know what time zones to account for. :)
Dennis Patterson (Apr 27 2020 at 19:23):
I updated the track page with an Orientation call next week on Tuesday, May 5th at 10 AM Central time.
If you're unable to make the call, please sync up with me and/or make sure you're registered for the event using the links above. I want to make sure your questions get answered and that we can start integrating before the event to ensure a profitable time. Thanks!
Dennis Patterson (May 04 2020 at 22:58):
Friendly reminder to fill out the Pre-Connectathon Survey, as well as the tracking spreadsheet! The survey gives the event organizers insight into your track participation, and the tracking spreadsheet specifically helps our track with expressing your track focus, urls, and (new this year!) coordination across time zones. :)
I will re-iterate this in the track orientation scheduled tomorrow (Tuesday, May 5th) at 10am Central time. I look forward to chatting then!
Dennis Patterson (May 05 2020 at 16:59):
Thanks to everybody who made it to the orientation call and signed up on the tracking spreadsheet! If you weren't able to make the call, no worries. The track page has now been updated with a recording. :)
Dennis Patterson (May 07 2020 at 16:36):
For any CDS Services wanting to start testing calls to their feedback endpoint, the public sandbox has been updated to call it when a suggestion is accepted. Let me know if you run into any issues
Dennis Patterson (May 07 2020 at 16:38):
Note that you must be returning card.uuid and suggestion.uuid for it to work :)
Dennis Patterson (May 12 2020 at 15:30):
Hi everybody! We're drawing near the event kick-off soon, so I encourage you to register your endpoint information in in the tracking spreadsheet and to start reaching out to other participants to get connections wired up! Below I'm going to create some polls to establish some virtual touch points for the event.
Dennis Patterson (May 12 2020 at 15:31):
Beyond the large group GoTo Webinar kick-off on Wednesday at 4PM ET, we should have a track kick-off using our Zoom channel
Dennis Patterson (May 12 2020 at 15:31):
/poll Track Kick-off: Immediately Following 4PM ET Wednesday Connectathon Kick-off
I can make a track kick-off afterward (~4:30PM or 5PM ET (UTC-4))
I'd prefer a track kickoff Thursday at 10am ET
Dennis Patterson (May 12 2020 at 15:31):
Our Zoom channel will remain open, but we'll have a daily touch point for everybody to join to sync on how things are going / raise any issues
Dennis Patterson (May 12 2020 at 15:31):
/poll Daily Syncs: 10AM and 3PM ET (UTC-4)
Both times work for me
I can make one of those times
I can't make either time
Dennis Patterson (May 12 2020 at 15:32):
The breakout will be a deeper discussion of reviewing progress, gauging maturity of 1.1 proposed features, and talking through next steps. (My proposal is to re-use one of the daily sync times)
Dennis Patterson (May 12 2020 at 15:32):
/poll Breakout Session
Friday at 10AM ET
Friday at 3pm ET
Douglas DeShazo (May 12 2020 at 16:02):
Will there be any language provided for suggestions, override reasons, etc.? Or should we be creating our own or using the spec examples?
Dennis Patterson (May 12 2020 at 16:23):
Hi Douglas! Can you clarify? For suggestions, you'd be proposing FHIR resource changes. For override reasons, the spec doesn't currently prescribe a standard set so one focus I anticipate is seeing what reasons services are interested in communicating and then we can further discuss if there are a subset that could be eventually made into an extendable ValueSet
Douglas DeShazo (May 13 2020 at 12:20):
Hi Dennis, we were just wondering if any override reasons had been decided upon for communication back in the returned card. We can use generic language for testing if needed. You do bring up a good point about suggestions and the action.resource parameter. Are we looking to have action taken on a resource as part of the suggestion returned? We can look at create or update for that if that's the scenario. Thanks.
Dennis Patterson (May 13 2020 at 14:09):
What you put in your suggestions will depend on the type of situation you're looking to detect. :) The suggestion may involve removing an order, replacing it with a different one, altering an order's dose, ...
Dennis Patterson (May 13 2020 at 17:26):
Sandbox update: The sandbox now renders override reasons, as well as allowing you to dismiss a card. The PR has screenshots for reference - https://github.com/cds-hooks/sandbox/pull/134. Any CDS Services working with override reasons are welcome to try.
Dennis Patterson (May 13 2020 at 17:26):
Dismissing cards isn't yet wired up to calling feedback, but I'll see what I can get done today :)
Dennis Patterson (May 13 2020 at 18:50):
Scheduling Update: I've placed a schedule out on the Track Page to help keep track of the overall schedule vs track schedule, which room for what
Dennis Patterson (May 13 2020 at 18:52):
Short version: we'll have a track kick-off in Zoom after the event GoToWebinar kick-off.. Then, current plan is to have daily syncs at 10AM and 3PM ET and a breakout session on Friday morning. We'll discuss this in the track kick-off, and touch on it again at the first daily sync tomorrow to ensure scheduling works
Dennis Patterson (May 13 2020 at 20:35):
If you're on the kickoff and trying to track down where the page is with all the zoom rooms, just go to our track page... i've posted that there along with a full schedule of relevant syncs
Dennis Patterson (May 13 2020 at 20:35):
I'm waiting until the Q&A is over in the event kickoff before starting the track kickoff
Isaac Vetter (May 13 2020 at 20:54):
but, it turns out that James is mostly talking about CDS Hooks in the primary GoToWebinar ...
Dennis Patterson (May 13 2020 at 21:14):
What do folks think about kicking off the track kickoff at 5:30PM ET, regardless of whether the main kick-off is done with Q&A?
Dennis Patterson (May 13 2020 at 21:19):
Thanks for the +1s. We'll start then, which will give people a little break. I'm about to drop from the main kickoff and will open the room so people can start trickling in
Dennis Patterson (May 13 2020 at 21:21):
room is open
Isaac Vetter (May 13 2020 at 21:47):
Main GoToWebinar schedule: https://docs.google.com/spreadsheets/d/1P4EPT2Hi3PI9eB-TYPj5xYHzInZS4ixd/edit#gid=1512697744
Isaac Vetter (May 13 2020 at 21:47):
CDS Hooks track schedule: https://confluence.hl7.org/display/FHIR/2020-05+CDS+Hooks+Track
Isaac Vetter (May 13 2020 at 21:47):
CDS Hooks track details/sign-up: https://docs.google.com/spreadsheets/d/10NMbAA0I4HRDcIkh6LPwTa0bcklfQJlBPcPjkIB1bWY/edit#gid=1720900059
Dennis Patterson (May 13 2020 at 23:08):
Thanks to everybody who joined the track kickoff! We got right into the weeds on some good topics, and even had some folks stick around for additional discussion. Looking forward to seeing what we can accomplish tomorrow!
Dennis Patterson (May 13 2020 at 23:53):
Sandbox update: the sandbox now calls your feedback endpoint when a card is dismissed and includes an auth header. Earlier enhancements were made to display override reasons and send feedback on acceptance of a suggestion. So, this should help with testing some of the 1.1 scenarios. I can do a demo and talk through it tomorrow during our first daily sync
Dennis Patterson (May 14 2020 at 13:56):
Good morning! Reminder that we'll be having our first daily sync in just under 5 minutes in Zoom!
Kevin Price (May 14 2020 at 14:55):
Hey Everyone! Primary Objective for Appriss Health today is to implement all the security recommendations and best practices defined with the specification. Currently I am leveraging the Cerner FHIR Sandbox with the CDS Hook Sandbox for some initial development. I also plan on diving into the Scenarios for 1.1 and can support and clients that want to test those features this afternoon and tomorrow.
I have also created specific cds services for the clients I see on the participation list - That way if there are any specific/custom scenarios you want to jump into we can dive in with you.
Cerner:
https://cds-cerner.hc.appriss.com/cerner/cds-services
Epic:
https://cds-epic.hc.appriss.com/epic/cds-services
T-System
https://cds-tsystems.hc.appriss.com/tsystems/cds-services
Dennis Patterson (May 14 2020 at 15:08):
I'm curious what you'd flex per client? We were just talking about this kind of thing yesterday.
Side note...each client authenticates their calls to you and provides an iss value that can be used to know which client it is
Dennis Patterson (May 14 2020 at 15:13):
Side note for participants. I neglected to highlight this earlier, but if you're newer to the spec and want a simple one-sheet representation of the 1.0 spec to aid you in development, check out our "Cheat Sheet" PDF! https://cds-hooks.org/cheat-sheet/Cheat%20Sheet%20-%20Sept%202019.pdf
Dennis Patterson (May 14 2020 at 18:44):
Reminder that we'll have having our second daily sync in Zoom in about 15 minutes!
Dennis Patterson (May 15 2020 at 13:56):
We'll be having our sync / breakout session in about 5 minutes in Zoom!
Isaac Vetter (May 15 2020 at 14:07):
fyi - https://cds-hooks.org/specification/current/#feedback :tada:
Dennis Patterson (May 15 2020 at 16:16):
Reminder: would you mind reaching out to me privately over Zulip or e-mail and sharing your connectathon experiences by sending me a few sentences including:
- Who you integrated with
- What you tested/accomplished/uncovered
- Any CDS Service screenshots (from the public sandbox or another CDS Client / EHR)
- Anything else you’d like to share
It would be helpful to have this info for the track report! Please send by 1PM ET if you can!
Dennis Patterson (May 15 2020 at 18:45):
Thanks to everybody who has responded with comments and screenshots! I have built out most of the track report and am trying to pull in some screenshots now. Please double-checkout to ensure your accomplishments and the issues we've discussed are represented accurately.
Dennis Patterson (May 15 2020 at 18:46):
We have our final track sync in 15 min and you can also bring up any changes you'd like there
Vijay Thirumalai (May 15 2020 at 20:08):
Please advise where i could find list of CDS client available for testing. I am currently using cds-hooks.org sandbox and interested to test with others.
Phillip Warner (May 15 2020 at 20:10):
@Vijay Thirumalai https://docs.google.com/spreadsheets/d/10NMbAA0I4HRDcIkh6LPwTa0bcklfQJlBPcPjkIB1bWY/edit#gid=1720900059
Vijay Thirumalai (May 15 2020 at 20:12):
Phillip Warner said:
Vijay Thirumalai https://docs.google.com/spreadsheets/d/10NMbAA0I4HRDcIkh6LPwTa0bcklfQJlBPcPjkIB1bWY/edit#gid=1720900059
Thanks
Dennis Patterson (May 15 2020 at 21:37):
Thanks again to everybody who participated in the track! It’s always exciting to see what people can accomplish and how many integrations occur in such a short time. A lot of good topics/questions got raised and even generated some new GitHub issues, so thanks again!
Last updated: Apr 12 2022 at 19:14 UTC
