Enforce the registration of display labels and translation

[HanneVuegen]

For the next release

As a HCA or patient I always want to know the readable/understandable information about the vaccinecode - not only the code, also the label/translation. Can we enforce the use of the display labels (and translation) for the Vaccinecodes? Now it is possible to only registrate the snomed code. Can we expect all applications to add the applicable display labels and translations when visualizing? Or should we enforce the registration of the display labels and translations?

Kr,
Hanne

[bdc-ehealth]

@HanneVuegen ,

there are two aspects to this:

1. Showing a synonym (or translation, which is a synonym in another language), is the responsibility of the terminology server (locally, fed by the central terminology server managed by FPS Health). Translations/synonyms are usually not a mandatory part of a FHIR message.

2. There is also a medico-legal issue, as mentioned by @mlambot and technically explained in this issue (in combination with a technical issue on the part of HL7 Int'l): Define general rules for the use of display in code, coding and codeable concept in guidance core#69 . The medico-legal issue amounts to the fact that the "display" value that was chosen by the physician should be present in the exchanged message, for legal responsability reasons.

Summary: the receiving application should be able to show the description it wants (so not mandatory) (provided it is one of the descriptions/translations that match with the code), for legal reasons, the transferred message should contain the description (display) that was originally chosen by the physician.

[HanneVuegen]

This isn't blocking for publication. Let's discuss with the workgroup for the next version.