FHIR Profiling FAQ
From Health Level 7 Belgium Wiki
Revision as of 20:43, 12 January 2020 by Jose Costa Teixeira (talk | contribs) (First draft created)
Contents
Tools
Profiling Tools
The profiling can be done via
- Profiles: Forge
- CodeSystem editing: FHIR Toolkit
- ValueSet Editing: FHIR Toolkit
- Implementation Guides: Trifolia, Simplifier, FHIR Toolkit
Repositories and publications
Questions
Making version support mandatory
In a profile, to make version support mandatory, i.e. to define that the implementation SHALL support versions of resource instances, 2 constructs are needed:
- CapabilityStatement.rest.resource.interaction.code must include history (history-xxx)
- The Conformance extension must be used
Link to example:
Asserting backwards compatibility between profiles
To ensure (and test) that the versions are backwards compatible or any incompatibility is noted, we can use the profile comparator. Currently the output of such comparison is html text, and the comparison must be made manually. This is OK because a new release requires manual work anyway, so manually checking compatibility does not impose an unjustified burden. Link to detailed instructions:
