Stream: cds hooks
Topic: Sept 2018 Connectathon
Kevin Shekleton (Aug 23 2018 at 04:36):
Hi everyone!
The next HL7 FHIR Connectathon is coming up at the end of next month and I hope to see you all there! The Connectathon is Sept 29-30 (Saturday & Sunday) and will be held in Baltimore, MD at the Hyatt Regency Baltimore Inner Harbor.
They are expecting a very large turnout for this Connectathon and space is limited. If you are planning on attending but have not registered yet, I would do so before they sell out. Registration is $450 and can be done at http://www.hl7.org/events/working_group_meeting/2018/09/
Already registered? Make sure you add yourself to our participant tracking sheet AND fill out the Connectathon survey to indicate that you will be participating in the CDS Hooks track.
So far we have two use cases with confirmed participants:
- Implement the final 1.0 spec (this includes changes from the recent May 2018 HL7 ballot)
- Check for drug-drug interactions with the medication-prescribe hook
We are soliciting additional scenarios and documenting them on our track Wiki page. If you are interested in a particular scenario, please reply here and let's find CDS Clients (ex: EHRs) and CDS Service Providers who are interested in participating in the scenario with you.
Let me know if you have any questions and I'm looking forward to seeing you all in Baltimore!
Kevin Shekleton (Aug 24 2018 at 14:09):
For those planning to attend the upcoming Connectathon, we will have a GoToMeeting call next Friday, Aug 31 (details follow). Each track hosts their own pre-Connectathon call to go over the basics of the Connectathon, logistics, and specifics for the track. If you can't make it, don't worry as we'll record the call and post it here for everyone to view later.
~~~~~~~~~
CDS Hooks Pre Connectathon 19 Call
When: Fri, Aug 31, 2018 12:00 PM - 1:00 PM EDT
Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/535831877
You can also dial in using your phone.
United States: +1 (646) 749-3122
Access Code: 535-831-877
Shalinee Batri (Aug 28 2018 at 08:48):
Hi Kevin- Can anyone who is interested in the new developments in the said topic can join these calls or is there a specific criteria.
Kevin Shekleton (Aug 28 2018 at 11:37):
Anyone can join this Connectathon prep call!
Isaac Vetter (Aug 31 2018 at 16:25):
Hey @Lloyd McKenzie - have you interest from Da Vinci / CRD to as a scenario to test at the HL7 Connectathon?
Lloyd McKenzie (Aug 31 2018 at 16:30):
We're doing our initial connectathon planning next Wed so not sure exactly how much of the CRD we'll bite off. The reference implementation will bite off all of it, but not sure where the payers and EHR vendors plan to be.
Isaac Vetter (Aug 31 2018 at 16:31):
@Richard Ettema pointed out that we've got a [CRD track|http://wiki.hl7.org/index.php?title=201809_Coverage_Requirements_Discovery] in Sept.
Lloyd McKenzie (Aug 31 2018 at 16:34):
Yes. I thought you were asking more specifically about what participants had committed to (as opposed to what we've crossed our fingers and are hoping for) :)
David Teirney (Sep 10 2018 at 02:30):
@Kevin Shekleton when is the next call to discuss the CDS Hook connectathon. We're literally about to register and we've got some questions about what the EMRs are likely to support around the patient-view hook, prefetch for various resources, demo practitioner and patient information so we can start some prep on our end to line up data so we can hit the ground running on the Saturday. I'll draft some specific questions this evening (NZ time). Is this the right topic to post those questions?
Kevin Shekleton (Sep 11 2018 at 15:46):
We don't have another call planned for the upcoming Connectathon. I think you would best find what you're looking for by reaching out to the various CDS Client (aka, EHR) vendors attending.
Also, can you share here exactly what it is you are looking to do? Eg, what hook(s) are you using and what FHIR resources you must need as required?
Kevin Shekleton (Sep 11 2018 at 15:47):
Here's our participant tracking spreadsheet: https://bit.ly/cds-hooks-connectathon-tracking
David Teirney (Sep 18 2018 at 04:16):
@Kevin Shekleton I'm new to connectathon's and following Working Group meetings. Is there going to be any conversation about CDS Hooks in any of the working group meetings in the days following the connectathon?
David Teirney (Sep 19 2018 at 00:45):
@Kevin Shekleton re reaching out to the other EMR vendors, is that typically done via email based on the email addresses in the participant tracking sheet? Here are a list of the questions we've got so far:
- Will the Practitioner's that are passed through as the user have a "system" defined for the identifier. The default CDS Hooks sandbox FHIR server only returns "use" and "value" for the identifier (and sometimes not even that). We need to identify the user appropriately for future downstream authorization and patient privacy related aspects.
- Will the EMRs attending support changing the user for the testing? E.g. so different users are presented in the CDS hooks that are published? We've got a PR up for changing the CDS Hooks sandbox to support this.
- What resources will the vendors have data for? We're currently looking to use Allergies, Conditions, Procedures, MedicationOrder, MedicationStatement. Which of those resource would support prefetch vs post fetch.
- What JWK signing certs will be used. We ran into an issue with our JWKS library not supporting ES key types which we're still to resolve.
Chuck Feltner (Sep 19 2018 at 12:29):
Welcome to the connectathon @David Teirney . Here is the info for the T-System EMR. The servers are listed on the spreadsheet.
1. There will be an identifier with a system in the Practitioner resource when you retrieve it using the practitioner id included in the CDS Service request.
2. Yes, we can use different users in the testing.
3. There should be data for all the resources we support. If not I can add the data you need.
4. Currently support RS256.
Isaac Vetter (Sep 19 2018 at 14:47):
Hey @Bryn Rhodes -- will there be time on the CDS wg's schedule during the HL7 meeting (following the connectathon) to talk through CDS Hooks issues/updates?
It would be good to have this issue specifically addressed.
Bryn Rhodes (Sep 19 2018 at 15:08):
@Isaac Vetter , yes, we currently have it on the agenda for Tuesday Q3: http://wiki.hl7.org/index.php?title=CDS_WG_Agenda_2018-09
Bryn Rhodes (Sep 19 2018 at 15:08):
I'll add that issue to the agenda
Bryn Rhodes (Sep 19 2018 at 15:10):
Well, as soon as I can update the wiki, currently getting some sort of CGI error :)
Kevin Shekleton (Sep 21 2018 at 18:01):
@David Teirney - Most of the EHR folks on the spreadsheet can be reached here in Zulip but the reason why we ask for emails too is so you can contact them directly if need be.
Regarding your questions, here are the answers for Cerner:
- Practitioner - just like what Chuck mentioned, you take the identifier and lookup the Practitioner resource to get the data you're looking for here.
- Change user - yes, we can do this
- Resources - you can see everything we support at fhir.cerner.com. We only support prefetching Patient
- JWK - We use ES256. See also this ballot issue. Side note - the open source Sandbox also uses ES256
Kevin Shekleton (Sep 29 2018 at 12:45):
Hi everyone and welcome to Baltimore! The CDS Hooks track is in the satellite room on the 15th floor (the view is fantastic up here!). Grab your breakfast down on the 2nd floor and then head up to the 15th. See you soon!
Kevin Shekleton (Sep 29 2018 at 12:54):
Take a look at our participant tracking spreadsheet here: https://bit.ly/cds-hooks-connectathon-tracking
We have 41 (!!!) registered participants for the CDS Hooks track this time. Use that to see who is here and what they are bringing to the Connectathon. If you're not on the list but here participating in the track, please add yourself to the list.
Kevin Shekleton (Sep 29 2018 at 13:03):
FYI - the kickoff will be happening soon (as soon as James gets back with his coffee). After that we'll do our own CDS Hooks kickoff :-)
David Teirney (Sep 29 2018 at 13:41):
Any EMR vendor available for some initial integration testing? I'll need to review the Practitioner identifier content in the patient-view hook to align some configuration on our side.
Chris Courville (Sep 29 2018 at 13:42):
I'm working on some initial set up for Epic, so we can be ready shortly
Paul Curcio (Sep 29 2018 at 13:48):
We had a discussion at our table about dealing with uncertainty in the course of execution of a hook - for example, if a CDS service needs a certain set of clinical data to make a decision as to whether show or not, but that data is not available to the service for whatever reason (e.g. transient error, insufficient scope to access, unsupported code system, etc.). How should this be handled? Since one of the features of CDS Hooks is that they don't "bother" the user with a card if the situation the hook is meant to handle doesn't apply, failing silently would imply that there's "nothing to worry about" with the situation.
(I guess there was some discussion of an "error" card before; see https://chat.fhir.org/#narrow/stream/17-cds-hooks/subject/error.20card)
David Teirney (Sep 29 2018 at 13:50):
@Chris Courville , great! Our DSTU2 endpoint is up at https://demo.portals.odl.io/cds-services
Brad Engels (Sep 29 2018 at 13:53):
Thanks for posting, @Paul Curcio , a real-world example I experienced outside of CDS Hooks is very relevant. With Epic's older implementation to FDB's drug dosing content, if FDB drug data did not contain dose-range information about a prescribed med, the user received a "No dosing data available" alert in the workflow. That non-value "alert" understandably drove users nuts
Kevin Shekleton (Sep 29 2018 at 13:56):
For anyone who wants to integrate with Cerner - please let myself or @Kol Kheang know and we will help you out. We will have @Andrew Torres from Cerner here later this morning as well to help.
Kevin Shekleton (Sep 29 2018 at 13:59):
@Paul Curcio - We never decided to add an error card in CDS Hooks (though as an aside, I still think that is a good idea).
In lieu of that, CDS Service developers should return an appropriate HTTP status code (eg, 5xx) if the EHR needs to know about the error. The EHR can then decide if the error should be displayed to the user or if it should be silently logged
Paul Curcio (Sep 29 2018 at 14:07):
Thanks @Kevin Shekleton - it's an interesting philosophical question, and I wonder if the answer is to limit the suggested use cases of CDS Hooks to situations where lack of expected information would not result in potential patient harm
Chuck Feltner (Sep 29 2018 at 14:15):
@David Teirney We have an STU3 server. Do you support STU3 as well as DSTU2?
STU3 Secure server: https://fhirsandbox2.tsysinteropsvcs.net:8100/sites/123/
Tom Wilson (Sep 29 2018 at 14:19):
@Chris Courville would love for you to try our cds hook - https://cds-hooks-cerner.staging.medwiseadvisor.com/cds-services
Kevin Shekleton (Sep 29 2018 at 14:36):
We have two breakouts scheduled for tomorrow around CDS Hooks for anyone interested.
9a - 10a: Discussion around CDS Hooks and the Decisions workflow. Decision was a feature we have discussed previously, ultimately pulling it from the 1.0 release due to lack of implementation feedback and we thought it would be changing directions. We'll discuss Decisions and a proposal for a future release.
10a - 11a: CDS Hooks open Connectathon & 1.0+ plans.
Both of these breakouts are tomorrow (Sunday) in the Constellation F room.
Kevin Shekleton (Sep 29 2018 at 14:37):
You can view all breakouts for the weekend in this spreadsheet: https://docs.google.com/spreadsheets/d/1fKoRbsD750R6hKcptCoCX4eufnwkBKkbTDBHQbpgVQ4/edit?usp=sharing
Chris Courville (Sep 29 2018 at 14:41):
Hey @David Teirney , I've everything set up on our side and just tried hitting you but got a rejection. Seems like a security issue. When you have a second can you come over and talk to me?
David Teirney (Sep 29 2018 at 14:51):
@Chris Courville sure thing. I've got one Authorization header come through without a "jku" entry in the JWT header. issuer was "https://igneous-cds-hooks.herokuapp.com"
Chris Courville (Sep 29 2018 at 14:52):
@Chris Courville would love for you to try our cds hook - https://cds-hooks-cerner.staging.medwiseadvisor.com/cds-services
No problem. I'll get our side setup and will let you know when I try it
Guilherme Del Fiol (Sep 29 2018 at 15:10):
For anyone who wants to integrate with Cerner - please let myself or @Kol Kheang know and we will help you out. We will have @Andrew Torres from Cerner here later this morning as well to help.
@Kevin Shekleton , I have a CDS service to test if you guys are ready - https://dev-service.oib.utah.edu:443/cds-services
It should retrieve patient education content from a couple of online resources - works both with patient-view and medication-prescribe.
Jeremy Audino (Sep 29 2018 at 15:10):
The CoverMyMeds team is ready to try connecting to an EHR, anyone game? https://master-cdshooks.integration.covermymeds.com/cds-services
Thomas Reese (Sep 29 2018 at 15:12):
Using the CDS Hooks Sandbox to send a request, we get a missing element error for expires_in. The CDS Hooks 1.0 specifies expires_in as REQUIRED for fhirAuthorization parameter. Our CQF Ruler is validating the request and seems to be correctly responding with an error. Is there a quick fix to add this to the Sandbox? Or, has anyone else run into this issue and has a fix?
Jeremy Audino (Sep 29 2018 at 15:13):
@Kevin Shekleton @Kol Kheang let us know when you have avail to try and connect to CDS Service let the CoverMyMeds team know
Guilherme Del Fiol (Sep 29 2018 at 15:19):
@Chris Courville , we have a cds service to test if you are ready. Works on patient-view and medication-prescribe. https://dev-service.oib.utah.edu:443/cds-services
Raj M (Sep 29 2018 at 15:21):
For anyone who wants to integrate with Cerner - please let myself or @Kol Kheang know and we will help you out. We will have @Andrew Torres from Cerner here later this morning as well to help.
@Andrew Gordon @Raj M @Kol Kheang @Kevin Shekleton
We have two CDS services which we would like you guys to try. WK Health Endpoints
https://prototypes.utdlab.com/argonaut/cds-services (use case #1)
https://wkcdshooks.azurewebsites.net/cds-services (use case 2)
Joseph Athman (Sep 29 2018 at 15:32):
@Kevin Shekleton @Kol Kheang The Surescripts CDS hook endpoint is available at https://surescripts-hooks.azurewebsites.net/cds-services. You should get a card back for medication-prescribe. I'm having a problem with the SMART app that launches from the link returned, but if you are able to get the card that is great.
Daryl Chertcoff (Sep 29 2018 at 15:51):
@Kevin Shekleton @Kol Kheang We (HLN) have a CDS Service we'd like to test with Cerner's system when you get a chance. https://cds.hln.com/cds-services. At the bottom of the card is a link to a SMART on FHIR app. (Link name is "ICE SMART App"
Daryl Chertcoff (Sep 29 2018 at 15:54):
@Chris Courville We (HLN) have a CDS Service we'd like to test with Epic's system when you get a chance. https://cds.hln.com/cds-services. At the bottom of the card is a link to a SMART on FHIR app. (Link name is "ICE SMART App"
Robert Sax (Sep 29 2018 at 16:20):
@Chris Courville When you get the chance, can you ping the stanson service (https://staging1-api.stansonhealth.com/07A83F99-BD4A-4DD0-B77C-E59E422F18CB/cds-services)
Kevin Shekleton (Sep 29 2018 at 16:29):
In case you haven't heard -- we will still be upstairs here on the 15th floor working. Apparently there was not room downstairs for us
Mike Gabrin (Sep 29 2018 at 17:45):
@Chris Courville I have a CDS Service I'd like to try whenever you have a chance. It's at https://cds-hooks-forwarder-dev.mmodal.com/rsna/cds-services. Thank you!!
Joseph Athman (Sep 29 2018 at 18:31):
If anyone from Epic is available to test the Surescripts endpoint I'm ready whenever you are. https://surescripts-hooks.azurewebsites.net/cds-services. I'd also love to see what it looks like within Epic to get a better feel for how providers will see it. Thanks!
Chris Courville (Sep 29 2018 at 19:04):
If anyone from Epic is available to test the Surescripts endpoint I'm ready whenever you are. https://surescripts-hooks.azurewebsites.net/cds-services. I'd also love to see what it looks like within Epic to get a better feel for how providers will see it. Thanks!
@Joseph Athman We tried to hit your patient-view service and ran into an issue. I sent you a direct message, but feel free to come by where we are (near the middle) to talk through it
Jeremy Audino (Sep 29 2018 at 19:09):
@Chris Courville @Isaac Vetter @Matt Varghese - can we set up a time to hit our medication-prescribe service? https://master-cdshooks.integration.covermymeds.com/cds-services
David Teirney (Sep 29 2018 at 19:22):
For the EMR Vendors here, which will support the "jku" field in the JWT header to provide the URL of a JWKS for production environments and which will expect the public key to be provided in some out of band process?
Rich Boyce (Sep 29 2018 at 19:27):
Using the CDS Hooks Sandbox to send a request, we get a missing element error for expires_in. The CDS Hooks 1.0 specifies expires_in as REQUIRED for fhirAuthorization parameter. Our CQF Ruler is validating the request and seems to be correctly responding with an error. Is there a quick fix to add this to the Sandbox? Or, has anyone else run into this issue and has a fix?
For now we have set expires_in as not required in our version of cqf ruler by changing line 33 in src/main/java/org/opencds/cqf/cdshooks/request/FhirAuthorization.java from expiresIn = JsonFieldResolution.getIntegerField(fhirAuthorization, "expires_in", true) to expiresIn = JsonFieldResolution.getIntegerField(fhirAuthorization, "expires_in", false)
Isaac Vetter (Sep 29 2018 at 19:30):
Hey @David Teirney - we're still trying to figure that out. A jku seems really nice, but we haven't done this dev for our CDS Hooks implementation.
Which would you prefer?
Chuck Feltner (Sep 29 2018 at 19:31):
@David Teirney T-System supports jku in JWKS. https://fhirsandbox2.tsysinteropsvcs.net:8100/sites/123/.well-known/jwks.json
David Teirney (Sep 29 2018 at 19:32):
jku is really straight forward for us. No needing to manage keys, and makes rotation pretty much transparent. If the JWKS URL returns the appropriate Cache-Control header then we'll refresh as often as necessary to get the updated public keys.
David Teirney (Sep 29 2018 at 19:37):
Wondering if it makes sense to add some notes to the spec around a recommendation for using the standard HTTP Cache-Control header with the JWKS endpoint to provide information to the client about how long they can cache the key set for.
David Teirney (Sep 29 2018 at 19:38):
We'd prefer to not hit the URL for the JWKS for every CDS hook invocation.
David Teirney (Sep 29 2018 at 19:42):
Following on from some earlier discussion, what's the appropriate HTTP response code to send back to the EMR vendor if for some reason we weren't able to get all the information we needed to return a valid card(s). In our case for the testing done today the data we need wasn't in the prefetch content and there was then a problem fetching the content from the FHIR server. We had a bug that I'm just about to fix whereby we were just returning 200 with an empty cards array for that case, which seems wrong.
Raj M (Sep 29 2018 at 19:51):
@Kevin Shekleton @Kol Kheang is below is right issuer and jku to use for this connectathon for whitelisting on our end? Sorry if this was posted already
"issuer": "https://igneous-cds-hooks.herokuapp.com",
"jku": "https://igneous-cds-hooks.herokuapp.com/jwks.json",
David Teirney (Sep 29 2018 at 20:18):
Does anyone know why there's a limitation on transparency for the PNG referenced in the icon field? Just trying to convert our PNG with transparency to one without. What background color are people antialiasing to? White?
David Teirney (Sep 29 2018 at 20:27):
Also, a more standard image size like 128x128 would be nice (then people could just clip that out of their favicon). In fact, was their any discussion on using an ico, which can support a number of image sizes depending on where the image needs to be used?
Tejay Cardon (Sep 29 2018 at 20:48):
I agree an ico would be a nice change or addition to the standard
Isaac Vetter (Sep 29 2018 at 21:20):
When we put this into the spec, we looked to how Apple did it. I think that .ico contains multiple distinct images bundled into one file.
David Teirney (Sep 29 2018 at 21:27):
Apple has different image formats and rules based on where the image ends up being used, e.g. launch screen, home screen, tab bar etc. Apple also trims images directly in some places, e.g. the home screen icons.
Brad Engels (Sep 29 2018 at 21:28):
FYI we have a few people planning to walk to Max's Taphouse for drinks (it's about a 25 minute walk depending on how fast we walk). We're meeting in the Hyatt lobby at 7:30 to head over there, so meet us at that time if you're interested.
David Teirney (Sep 29 2018 at 21:29):
http://ogp.me/ has some similar concepts to the meta-data exposed in the CDS Hook response.
Kensaku Kawamoto (Sep 29 2018 at 22:51):
* Request for EHR vendor testing of CDC-sponsored opioid CDS content * (thanks to Epic for already trying)
Endpoint: https://fhir.cygni.cc/opencds/hooks/cds-services
For medication-prescribe:
1. https://fhir.cygni.cc/opencds/hooks/cds-services/opioid-mme (provides information on opioid morphine milligram equivalence, requires draft opioid order such as oxycodone)
2. https://fhir.cygni.cc/opencds/hooks/cds-services/opioid-benzodiazepine (warns for opioid and benzodiazepine co-prescription, e.g., oxycodone and diazepam)
For patient-view:
1. https://fhir.cygni.cc/opencds/hooks/cds-services/opioid-mme-sof (provides information on opioid morphine milligram equivalence of any active or draft opioid orders)
Open FHIR server endpoint with relevant data (active methadone and diazepam):
https://api.hspconsortium.org/uofu/open
Patient with ID of SMART-1288992
Kevin Shekleton (Sep 30 2018 at 12:03):
@Raj M - That is the correct jku for the Connectathon for Cerner, yes
Kevin Shekleton (Sep 30 2018 at 12:05):
Reminder - we have two breakouts today for anyone interested, both in the Constellation F room.
9a - 10a: Decisions workflow and inter-app communication
10a - 11a: CDS Hooks 1.0 and future plans
Paul Curcio (Sep 30 2018 at 12:57):
@Kensaku Kawamoto, the SVG chart in the card is a really nice touch! Did it display properly in your EHR vendor testing?
Kensaku Kawamoto (Sep 30 2018 at 13:25):
@Paul Curcio , it's been verified in -- CDS Hooks Sandbox, Epic EHR with a custom CDS Hooks middleware we implemented leveraging Epic BPA Web services (in production enterprise use). In the Epic upcoming CDS Hooks implementation, the image heights are much taller than we would have expected. Are you seeing anything similar? Would love to see.
Paul Curcio (Sep 30 2018 at 13:28):
@Kensaku Kawamoto, I was partly asking because the CDS Hooks 1.0 spec says that the "detail" of the card "... MUST be represented in (GitHub Flavored) Markdown". But it looks like vendors are piping HTML in there straight from the card. Is this potentially a security concern?
Thomas Reese (Sep 30 2018 at 13:39):
@Chris Courville @Isaac Vetter @Matt Varghese , Would you have an open time slot we could test the PDDI-CDS scenario? We are ready with one case and finalizing the second.
Kensaku Kawamoto (Sep 30 2018 at 14:15):
Re: Opioid CDS. Please note a presecription start date is required for draft med orders.
Kensaku Kawamoto (Sep 30 2018 at 15:50):
@Paul Curcio My understanding is that GitHub Flavored Markdown allows piping in HTML with new line breaks to indicate the start of HTML tags. There's no scripting allowed still, however. So all dynamic content has to be handled via CSS.
Kensaku Kawamoto (Sep 30 2018 at 15:52):
@Chris Courville Could you try again? Phil was just reloading the service to fix the HTML style issue. It was right around when you sent the message.
Chris Courville (Sep 30 2018 at 15:53):
its returning the card now
Chris Courville (Sep 30 2018 at 15:53):
thanks
Kevin Shekleton (Sep 30 2018 at 16:02):
@Paul Curcio - GitHub Flavored Markdown allows for a subset of HTML (it excludes some tags which pose security concerns). See https://github.github.com/gfm/#disallowed-raw-html-extension-
Kensaku Kawamoto (Sep 30 2018 at 16:03):
Re: Opioid CDS. The service at https://fhir.cygni.cc/opencds/hooks/cds-services has been updated to return dynamic content for the MME/OME calculator (below each opioid med should be a chevron, which can be clicked to expand details). The original service without dynamic content is now at https://fhir.cygni.cc/opencds-2/hooks/cds-services. Would appreciate input on whether the service works or does not work in an EHR. P.S. these services are CDC-sponsored, there is ongoing funding for further development, and are available free and open-source. They also support average MME (vs. only the max MME typically supported), as well as natural language processing of free-text Sigs (affects ~20% of opioids at our institution). Thanks! Ken
Kensaku Kawamoto (Sep 30 2018 at 17:44):
@Kol Kheang The Opioid CDS service is at https://fhir.cygni.cc/opencds/hooks/cds-services. Hooks for patient-view and medication-prescribe.
Tom Wilson (Sep 30 2018 at 20:31):
@Kevin Shekleton Thank you for leading the CDS Hooks track in this connectathon, it was a lot of fun and I learned a lot. I am looking forward to the next one. It was very nice to meet everyone, I hope everyone has a great conference!
Last updated: Apr 12 2022 at 19:14 UTC
