search

hl7-be / lab

Creative Commons Zero v1.0 Universal
6 stars 9 forks source link

What to do with errors in errolog on testserver? #253

Open JanVanElslande opened 8 months ago

JanVanElslande commented 8 months ago

Hello all,

I am new to this and I have some basic questions.

I managed to generate a .json file in FHIR standard from the laboratory information system (GLIMS) (I edited this a bit with a text editor to make it anonymous)

bundle_23111715092.json

When I dragged and dropped this into the vizualisation app (link: https://fhir-testserver.be/index.php/visualization_webapp) I got

1) An output: Output_testserver_JSON_FHIR_parsing_order_2311-030031.docx

2) An errorlog: Errorlog_testserver_JSON_FHIR_parsing_order_2311-030031.docx

My question now is: what do the different errorcodes mean exactly? What do I have to do to "solve" them?

bdc-ehealth commented 8 months ago

@JanVanElslande

Happy New Year!

Jan, first of all, are you aware of the 11 steps to do the test program? The steps are briefly explained here by a non-informatician working in an actual lab (AZ Zeno - Knokke). 20231025 Digitalisation Labresults - Testserver QA Session - BDC.pptx

This will solve your first point, making the files anonymous (you have to create testpatients in your system). The visualisation tool is an aid for you, as a non-informatician to look at the generated files. You do not have to do anything with the output, apart from reading and verifying it. The error output of the visualization tool is the best indicator to check the validity of your file. Check the red lines (errors), the yellow lines (warning/information) are not always pertinent. Try to fix the issues you see there by modifying your GLIMS configuration (two important issues I saw in your logs was a missing results interpreter (GLIMS setting), and a wrong UCUM unit, which is also a GLIMS configuration.)

If you don't feel secure enough modifying your GLIMS configuration, you will have to contact GLIMS.

The best thing is to follow the 11 steps in the slides, and see how AZ Zeno solved some of the problems (which are likely to be similar to yours). If you have other problems, do not hesitate to publish them here, or if you do not want them to be public, send a mail to support@be-ehealth-standards.atlassian.net