Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Labels from LOINC codes differ from those in Retam #139

Closed
MiekeNXH opened this issue Sep 5, 2022 · 5 comments
Closed

Labels from LOINC codes differ from those in Retam #139

MiekeNXH opened this issue Sep 5, 2022 · 5 comments

Comments

@MiekeNXH
Copy link

MiekeNXH commented Sep 5, 2022

While testing we notice that the labels in Retam differ from those sent to us from the labs.
In the 2 images you can see the Fhir message with the suggested label from the lab and in the screenshot from NXH you can see the translation from the Retam.

image

image

@bdc-ehealth
Copy link
Collaborator

bdc-ehealth commented Sep 5, 2022

@tomfiers,

Labs sometimes send results in which the label differs from the labels that are defined in Retam. Which labels should be displayed by the GP software: the labels sent by the lab, or the labels as defined in Retam. (see question above by Nexuzhealth.)

@tomfiers
Copy link
Collaborator

tomfiers commented Sep 5, 2022 via email

@filipv-nh
Copy link

Ok, then until we have a crisp answer to this question, we will hold further development of the integration of the Fhir parser in our GP application.

@bdc-ehealth
Copy link
Collaborator

bdc-ehealth commented Oct 19, 2022

If there is a Retam code available, the Retam description must be used/displayed (Keep up to date with the new Retam releases). We propose to provide a mechanism to make the lab provided label retrievable in other cases.

@bdc-ehealth
Copy link
Collaborator

bdc-ehealth commented Oct 25, 2022

WG: the labs should use the same label on paper and electronic communication, it is up to the GP software to decide what label to show in the case of results coming from different labs. I will add this to the FAQ, and to the visualisation guidelines in the IG.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants