Define general rules for the use of display in code, coding and codeable concept in guidance

[bdc-ehealth]

Question from Validation team on 01/02/2024: https://wiki.hl7belgium.org/index.php?title=Minutes_-_FHIR_Validation_Group_2024-02-01#:~:text=11)%20There%20is%20a%20request%20for%20a%20general%20rule%20in%20the%20%E2%80%9Ccore%E2%80%9D%20package%20about%20the%20use%20of%20the%20display%20field%20in%20codes.%20Bart%20will%20open%20an%20issue.

[bdc-ehealth]

WG:
agrees with having a display in the code (SHOULD) and in English. We do not enforce that the display corresponds with the official value in the terminologyserver, but we recommend to use the offical value.

[bdc-ehealth]

text

• orginal value at entry time
• to specify extra information for a generic code

display:

• request by MA Lambot to store the original language of the code (per code)

[bdc-ehealth]

WG: ask the Swiss (Oliver Egger) how they do it.

[costateixeira]

What is the problem? I don't understand the problem statement.

…

On Wed, Jun 12, 2024 at 10:00 AM Bart Decuypere (eHealth) < ***@***.***> wrote: WG: ask the Swiss (Oliver Egger) how they do it. — Reply to this email directly, view it on GitHub <#69 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD3HUUA7B4THOKBRQV56TFLZG753LAVCNFSM6AAAAABDJY3OFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSGM3DAMRZGA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[costateixeira]

Just guessing - Most likely this will be in the area of multilingual content. Once the need is clarified (please do clarify what is the need), we can discuss with people that are working on same topic (myself included). On Wed, Jun 12, 2024 at 10:10 AM Jose Costa Teixeira < ***@***.***> wrote:

…

What is the problem? I don't understand the problem statement. On Wed, Jun 12, 2024 at 10:00 AM Bart Decuypere (eHealth) < ***@***.***> wrote: > WG: ask the Swiss (Oliver Egger) how they do it. > > — > Reply to this email directly, view it on GitHub > <#69 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AD3HUUA7B4THOKBRQV56TFLZG753LAVCNFSM6AAAAABDJY3OFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRSGM3DAMRZGA> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

[bdc-ehealth]

the issue is described here: https://chat.fhir.org/#narrow/stream/179202-terminology/topic/Managing.20multiple.20languages/near/426577638 upto here: https://chat.fhir.org/#narrow/stream/179202-terminology/topic/Managing.20multiple.20languages/near/426763431

It is about the combination of the original UI value that was chosen by the physician (which may be a different language) and any additional information that can be added by the physician. According to the definition in the standard: https://www.hl7.org/fhir/R4/datatypes-definitions.html#CodeableConcept.text (see Definition and Requirements) both go into the same attribute (.text). These are actually semantically two different things. e.g. SNOMED CT code: 836369007 : the value chosen in the interface might be "vaccin tegen virus" which goes in the .text attribute. Additionally, the physician has not found the actual virus vaccine he wants to register, so he adds "vaccine against HIV": this specification is also added to the .text attribute. This results in having to concatenate both values in the .text attribute. We want to avoid this.