Stream: connectathon mgmt
Topic: Ad Hoc Connectahons?
Abbie Watson (May 16 2018 at 18:25):
Hi,
Not to distract from the work going on in Koln, but I have a question about ad-hoc connectathons. It turns out that some of the medical school and business school students at UChicago decided to organize a health tech hackathon this week. We have a new Trauma Center opening up at the University, and the hackathon theme is 'Trauma', which is ostensibly the same as 'Acute Care' use case from the Clinicians on FHIR group. I've talked with the organizer, and they're anticipating about 40 people to attend (including 3 to 6 from the Biomedical Informatics program); which seems like it's enough to qualify for an ad-hoc connectathon or Clinicians on FHIR session.
So, where do we begin with something like this? Are there any introductory materials or on-ramping materials for groups holding local connectahons? Are there any considerations we need to keep in mind regarding the HL7 brands and trademarks?
We're tentatively planning on doing a presentation on FHIR and the Clinician on FHIR usecases, and to try to rally the ~40 folks around using interoperability standards. We've also been working on making the Meteor on FHIR platform available through the University tech-transfer program; so the teams who are starting from scratch can build directly on a FHIR platform.
Any thoughts much appreciated.
Abigail
Lloyd McKenzie (May 16 2018 at 18:36):
Well, there are these: http://wiki.hl7.org/index.php?title=FHIR_Connectathon_Track_Process
http://wiki.hl7.org/index.php?title=Connectathon_Track_Lead_Responsibilities
The various tracks from the last 3-6 connectathons to mine for topics/track definitions
The various training materials from things like DevDays, some of which explain a little bit about what a connectathon is
Something else to consider is picking a primary server or two and making arrangements with the maintainer of that server to ensure they won't take it down for maintenance in the middle of your Connectathon and ideally that they'll be around to help if something goes wrong.
Abbie Watson (May 16 2018 at 19:29):
Perfect! Thank you! Exactly what I was looking for. :)
We'll do this ad-hoc and try to keep in spirit with the HL7 process, take notes, and do a short write up afterwards.
Thank you!
Lloyd McKenzie (May 16 2018 at 19:36):
Have fun. Sounds like an awesome idea
Lloyd McKenzie (May 16 2018 at 19:37):
Also, be sure to introduce the particpants to chat.fhir.org and encourage them to engage with the broader community when they have questions - may as well start them early :)
Abbie Watson (May 16 2018 at 19:42):
Absolutely! :D
Michael Donnelly (May 16 2018 at 20:58):
When’s that going on, Abigail?
Abbie Watson (May 16 2018 at 21:07):
Friday noon through end of day Saturday.
David Hay (May 17 2018 at 07:00):
BTW - the conman app (part of clinFHIR) was developed to help support events like this. Just reach out if you want more info...
Michael Donnelly (May 21 2018 at 20:23):
How'd this end up going?
Abbie Watson (May 22 2018 at 15:59):
BTW - the conman app (part of clinFHIR) was developed to help support events like this. Just reach out if you want more info...
Thank you! Yes, we're definitely interested in flow-charting and diagraming these usecases as a next step. Are you going to be at FHIR DevDays in Boston this year? I want to discuss in more detail (but am still gathering information).
Abbie Watson (May 22 2018 at 16:30):
How'd this end up going?
It went well! About 40 to 50 people showed; of which maybe a half-dozen were organizers, and another dozen were mentors. Probably a 3:1 ratio of students : professionals; divided into 5 teams. A lot of greenfield projects, where folks were just wireframing ideas. There were maybe a half-dozen of us who were experienced enough to be standing up actual systems. We wound up getting 3 or 4 FHIR Servers up and running during the connectathon, and were mostly focused on non-clinical resources such as Location, Organization, and RelatedPerson. Our team implemented a $near geospatial operator for proximity detection, with an eye towards first-responder applications. We had a lot of learnings about how to run Meteor on FHIR framework within a hackathon environment; including what we need in a custom settings.json file, and how we might use IPFS to autosynchronize datasets. All in all, it went really well!
David Hay (May 23 2018 at 13:32):
Hi @Abigail Watson - sorry won't be at the Boston event (still haven't made it home form Cologne yet!). The tooling is more about tracking outcomes (for a technical CT) though, not intending to move into the flowcharting / diagramming space (ATM :) ). Are you likely to be in Baltimore?
Last updated: Apr 12 2022 at 19:14 UTC
