wondering if we should add some of the documents that are shared in the threads.
Possibly add the ability to create documentation, I’ve used something called a fhir implementation guide which allows documentation to be created using markdown and plantuml. It’s quite easy to setup.
Sounds like a great idea @mayfield.g.kev - I think many moons ago I did have a GH org for OHH, but it ended up not really having anything terribly useful in it. I don’t think I was able to get openhealthhub because it’s already taken Open HealthHub · GitHub.
We could certainly start with a docs site in one of our own orgs/personal account? The FHIR Docs/Implementation guide sounds like a plan.
[Maybe in view of Open Health Hub being a different thing (Dutch company) we shoudl consider changing the name of this site?]
is the Docs plugin an option? Doc Categories | Discourse - Civilized Discussion
avoid the need to rename the forum
edit: I thought you were worried github/open health hub was too close - I didn’t realise there is now a dutch company with the same name.
Very happy to enable the Discourse Docs Categories plugin - I use it on several other Discourse instances. However for what Kev’s suggesting I think docs within Discourse aren’t the best solution. He wants a Git-tracked static site repo I think, and I agree this is probably the right way if there is a FHIR Implementation Guide static site generator.
I haven’t used Codeberg, but they seem good! As long as the artifacts we’re storing are just files in a Git repo without dependencies to GitHub features, then it’s relatively simple to move a repo from one Git hosting site to another.
p.s. volume 1 is missing on purpose…… I’ve not found a good source linking pathways → process → tech
Some of the newer international IHE profiles and HL7 implementation guides are quite good around this but the core/foundation domains/frameworks I’ve used here are a bit verbose.