Stream: implementers
Topic: FHIR Connectathon for Startups
Samm Anderegg (Dec 18 2018 at 15:00):
Hi everyone!
I'm a clinician and long-time standards nerd from the pharmacy space. I fully transitioned to tech 2 years ago working on an (not quite certified) EHR for pharmacists with community practices. We're really excited about the C-CDA IAT and Da Vinci Project tracks at the upcoming Connectathon in San Antonio. This would be our first Connectathon--it would help a ton if we understood how the event is set up and what type of learning comes out of the experience. Could you help us understand:
How are these events facilitated?
Who would we be interacting with?
Which team members/how many should be present (CTO, product manager, engineers, etc)?
What type of learning/benefits would we take home?
Sorry for the dumb questions--we're an early stage start up running lean, but want to engage with HL7 in the best way possible.
Thank you!
Samm Anderegg, Pharm.D., MS, BCPS
CEO, DocStation
Lloyd McKenzie (Dec 18 2018 at 15:22):
There are a multitude of tracks running (list for January is here: http://wiki.hl7.org/index.php?title=FHIR_Connectathon_20). Each one has a coordinator that will reach out to participants who have self-identified in a survey sent out prior to the event. Degree of pre-work expected varies by track from "none" to "fully working system that's been tested with peers in advance". Participants in a given track gather at the same table or set of tables and work through some of the scenarios, testing with each other. They may also have break-outs to discuss issues (either in one of the bookable breakout rooms or just in the hall). People arrive between 8-9 on Saturday and leave between 6 and 9 that evening. On Sunday we start at the same time with a stop at 4:30, then a summary of highlights and a hard stop at 5. Attendees include those who build the spec, those who maintain the reference implementations, a range of EHR and other vendors, large companies like Google and Microsoft and small startups. Some folks will have attended 15+ connectathons previously, others will be there for the first time.
There's often a range of attendee types, but the event is focused on those who write code. Learnings include building relationships with others in the same space (and with the organizations you'll need to interoperate with), increased understanding of using FHIR to solve real-world problems, better familiarity with reference implementations, a chance to take the theory of FHIR and apply it in practice, help getting over the humps those sitting beside you have already hit their heads on and learned how to solve, understanding of how to use FHIR in a consistent way to solve track-specific use-cases, ability to influence the FHIR spec to better meet your requirements, sense of who the people are in the community who might be best able to help answer particular questions.
Samm Anderegg (Dec 18 2018 at 16:10):
Extremely helpful, thank you so much @Lloyd McKenzie!
David Hay (Dec 24 2018 at 02:09):
BTW - note the specific stream for connectathon: https://chat.fhir.org/#narrow/stream/58-connectathon-mgmt
Last updated: Apr 12 2022 at 19:14 UTC
