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

END-to-End testing: opmerkingen #316

Open
RDEVIDTS opened this issue Jul 11, 2024 · 1 comment
Open

END-to-End testing: opmerkingen #316

RDEVIDTS opened this issue Jul 11, 2024 · 1 comment

Comments

@RDEVIDTS
Copy link

Hallo,
Labo AZ Alma is bezig met CGM (Daktari) de end-to-end testing aan het uitvoeren. We hebben enkele (belangrijke) opmerkingen.

  • Wie bepaald de volgorde van rapporteren van de verschillende hoofdingen? Moet de volgorde overgenomen worden van het labo of bepaald de softwareleverancier zelf de volgorde?
  • De labo's (Glims gebruikers) sturen in het FHIR rapport zowel de LOINC-code als de eigen omschrijving van de test mee. Moet de eigen omschrijving van het labo of de omschrijving van de LOINC-code getoond worden bij de visualisatie in het artsenpakket. Wat dan met anderstalige artsen? Eventueel mee te nemen naar een volgende werkgroep?

Alvast bedankt
mvg Rinaldo De Vidts

@bdc-ehealth
Copy link
Collaborator

bdc-ehealth commented Jul 22, 2024

Hello @RDEVIDTS ,

Nobody determines the report order in a structured context. The report itself is a tree, and the only thing you should care about is that each item has the correct parent. There is no order in the siblings.

The receiving end is responsible for the display of any textual information related to a LOINC-code. There is a preference to show the (short) labels available in the ReTaM table, and possibly add a reference to the long description to avoid ambiguity. For codes that are not part of ReTaM/LOINC, the software will use the display value in the FHIR file, or if it has its own translation table for other code systems, it will use its own table, as it was in the past. The same question was already asked in this issue: #276

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

2 participants