Encounter.class has an extensible binding but has a ConceptMap defined. According to the Profiling Guidelines, we only need a ConceptMap with a required binding.
Should the ConceptMap be removed? And if so, is it sufficiently clear to implementer that the OTH code (in this case) can also be added to be zib compliant?
You could argue that the ConceptMap is a good way to communicate that fact that 'the zib allows this and this extra codes' with an extensible binding. In that case the guidelines should be edited.
This is actually a strange beast, as the codes in the zib ValueSet are part of the FHIR ValueSet, with the addition of OTH. Binding the zib ValueSet here seems the proper thing to do.
https://simplifier.net/nictiz-r4-zib2020/zibencounter
Encounter.class has an extensible binding but has a ConceptMap defined. According to the Profiling Guidelines, we only need a ConceptMap with a required binding.
Should the ConceptMap be removed? And if so, is it sufficiently clear to implementer that the OTH code (in this case) can also be added to be zib compliant?
You could argue that the ConceptMap is a good way to communicate that fact that 'the zib allows this and this extra codes' with an extensible binding. In that case the guidelines should be edited.