Skip to content

zib-Encounter: .class ConceptMap #303

@jd-nictiz

Description

@jd-nictiz

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions