Later this month I hope to initiate a number of community “work packages” to assist the community in building interoperable FHIR based assets. We are still working out the details but current thoughts include:
Guidance for FHIR Naming schemes
Guidance for naming FHIR Profiles, ValueSets, Identifiers etc - how to avoid unintended collision between projects.
Guidance for versioning of FHIR assets (and identifying a version)
Community FHIR Profiles
To test the water in creating community FHIR assets then potentially we could start with the core building blocks of a system PATIENT, PRACTITIONER, ORGANIZATION, LOCATION etc
How do we profile these for community use? Too loose and they will inhibit innovation and supplier flexibility, too tight and they will inhibit adoption and innovation - discuss !
Ensure we have properly defined valueSets with cross-mappings if required
Where to the assets go - GitHub?
Whereas I will throw these out into the community as there is a benefit to “the centre” in the community working together to deliver these assets, there does need to be people who stand up and join the team to develop these.
I’m confident that more communication will follow via the Code4Health community but in the meantime if you think this is an area where you can provide input register your interest here and I’ll make sure you are “in the loop” when we initiate this work.