Stream: FHIRcast
Topic: Sept Connectathon - Use Cases
Jeremy Richardson (Sep 29 2018 at 14:13):
At the roundtable for FHIRCast, we started talking about problems. These are my developing thoughts...
fhircast.usecases.jsr.2018-09-29_1005.md
Jeremy Richardson (Sep 29 2018 at 14:26):
@Will Maethner @Isaac Vetter @David La Hei @Sagy Pundak Mintz @Glenn Potter ^^
Isaac Vetter (Sep 30 2018 at 12:48):
Hey @Jeremy Richardson !
Thank you for working on this. I think that we've got a good start on some user stories, here: https://github.com/fhircast/docs/wiki/FHIRcast-High-Level-Use-Cases
Jeremy, I wasn't sure how to massage the IT considerations, I saved them off and removed them from the wiki. Interested in improving these:.
Jeremy Richardson (Oct 01 2018 at 23:23):
Any thoughts on how we can collaborate on these remotely @Isaac Vetter ? I'm a big fan of starting with an outline and filling it in. I think the etiquette on commenting we talked about would come in super handy here, even if you and I are making asynchronous changes.
Isaac Vetter (Oct 03 2018 at 00:18):
Hey @Jeremy Richardson - how about just a google doc? Would that work alright?
Jeremy Richardson (Oct 05 2018 at 01:57):
@Isaac Vetter , that sounds like a third place for content, versus the primary website is fhircast.org and the Wiki... Is it beneficial to have something that natively works with Markdown? I haven't successfully used Word Online or Google Docs for editing Markdown. Maybe you have had success with this. Google Docs is great for live collaboration.
What about just working in the docs repo?
I think Confluence would be superior to the Git Wiki.
I would love to have a single place to go for content. My sense is the docs repo is the right place, if we're committed to the way fhircast.org is currently setup.
Last updated: Apr 12 2022 at 19:14 UTC
