search

hl7-be / lab

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

Manual available for visualization tool? #181

Closed KristiaanJaques closed 1 year ago

KristiaanJaques commented 1 year ago

Is there an instruction manual for the upload section of the FHIR Visualization tool (https://vizapp.icure.dev/)?

We attempt to submit files to the visualization tool, but keep getting the following error: "Filename.xml" file upload failed.

Is there a limitation to the extension of the file or other formatting requirements that prevent upload of a file to the test environment?

bdc-ehealth commented 1 year ago

@KristiaanJaques ,

There seems to be a problem with the testing of xml files. JSON files work fine. We will try to fix this.

In the mean time you can use: https://fhir-formats.github.io/ or the Visual Studio plugin vscode-fhir-tools to convert your xml file to json.

We will notify you if the bug is fixed.

KristiaanJaques commented 1 year ago

What can we expect as feedback from the visualisation tool? Is it only a success/fail message When we get a fail message, do we also get a description of the reason of the fail?

bdc-ehealth commented 1 year ago

@KristiaanJaques

As feedback from the visualization tool, you get a "readable" rendering of the message, i.e. a message that can be read by people who have no computer science background, such as a clinical biologist.

Secondly, you also get a validation against the standard. The compliancy problems are pointed out line by line.

KristiaanJaques commented 1 year ago

"We will notify you if the bug is fixed." Is there any indication when the fix for the .XML bug will be available?

bdc-ehealth commented 1 year ago

@KristiaanJaques , we will keep you up to date, but I won't be in 2022 anymore.

KristiaanJaques commented 1 year ago

Thank you for the suggestion to convert XML files to JSON. We successfully converted an XML file to JSON format. We were able to upload the converted JSON file to the vizualisation tool (https://vizapp.icure.dev/) and obtained a favorable analysis report. However, we noticed that the JSON converter has a number of conversion problems. I.e. that some XML items are converted to a JSON array, when no array is expected and some XML elements are converted to a single JSON value where an array is expected. We refer in particular to the XML observation.hasmember element. This has to be converted to a JSON array, but this is not the case when there is only one member in the observation. When there are more members in the observation, the first observation.hasmember is not present in the JSON file. We believe that this is the consequence of the same error. This behavior seems to be consistent and independent of the number of members when the number of members is greater than one. example of issues.txt Can you please check this?

sttav commented 1 year ago

@bdc-ehealth, we also would like to use XML. Any updates on when the bug can be fixed? Thanks

FlorianBonte-Moonchase commented 1 year ago

As an alternative to the online visualiser/validator, try the one in this repository: https://github.com/ehealthplatformstandards/laboResultVisualization

When something goes wrong in the online validator, it can be helpful to get a second opinion. For example, the online validator fails without a proper error message if the Organization resource referenced as the performer of the DiagnosticReport does not have a name. This tool also fails on that, but at least gives a stack trace and an indication of what went wrong.

I suppose it can work with XML as well, but I haven't tried.

bdc-ehealth commented 1 year ago

@sttav , @KristiaanJaques The Visualization Tool now works for XML, except for the validation. This will be fixed soon, we will keep you up to date. Check: https://fhir-testserver.be/index.php/visualization_webapp

bdc-ehealth commented 1 year ago

@sttav , @KristiaanJaques XML Validation is now available as well in the Visualization tool!

sttav commented 1 year ago

@bdc-ehealth , Dear, we now use the Visualization Tool at https://fhir-testserver.be/index.php/visualization_webapp. It used to validate our files nicely, but now we get errors again for our files. In the feedback I see the build is quite old, is this the latest version? visualiser

bdc-ehealth commented 1 year ago

@sttav, could be that this is the cause, although I doubt it... you can send me the file you tested with at support@be-ehealthstandards.atlassian.net, or if the information is not GDPR sensitive, you can just attach it here. I will check it for you.

sttav commented 1 year ago

In bijlage de file.

Bij voorbaat dank

Van: Bart Decuypere (eHealth) @.> Verzonden: donderdag 23 maart 2023 16:11 Aan: hl7-be/lab @.> CC: Stefaan Tavernier @.>; Mention @.> Onderwerp: Re: [hl7-be/lab] Manual available for visualization tool? (Issue #181)

@sttavhttps://github.com/sttav, could be... you can send me the file at @.**@.>, or if the information is not GDPR sensitive, you can just attach it here. I will check it for you.

— Reply to this email directly, view it on GitHubhttps://github.com/hl7-be/lab/issues/181#issuecomment-1481371506, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACDAJOJVG6Z6NR2SWKWNRO3W5RRYLANCNFSM6AAAAAAS6O6QKA. You are receiving this because you were mentioned.Message ID: @.***>

bdc-ehealth commented 1 year ago

@sttav , the file did not make it to GitHub. Could you add it using the browser in stead of using a mail. Or just email it to support@be-ehealthstandards.atlassian.net if you prefer email.

sttav commented 1 year ago

14221022-Copy.txt

Hi, this is the XML renamed tot TXT. It seems that an order constraint has been added for the XML?

KR

sttav commented 1 year ago

@bdc-ehealth btw, I received an email bounce when i tried to mail to the support@be-ehealth... , the mail alias was not recognised.

bdc-ehealth commented 1 year ago

@sttav , sorry I made a typo: 'support@be-ehealth-standards.atlassian.net'. I am looking at your file.

bdc-ehealth commented 1 year ago

@sttav , here is the result from a very recent version of the validator. There are some order issues, but not only with the id.

java -jar c:\Users\eh089\.vscode\extensions\yannick-lagger.vscode-fhir-tools-1.5.0\validator_cli.jar "c:\Temp\empty\lab\input\examples\14221022-Copy.xml" -ig hl7.fhir.be.lab
FHIR Validation tool Version 5.6.107 (Git# 1e43fe43f05e). Built 2023-03-10T13:10:13.315Z (13 days old)
  Java:   18 from C:\openjdk-18\jdk-18 on amd64 (64bit). 4050MB available
  Paths:  Current = C:\Temp\empty\lab, Package Cache = C:\Users\eh089\.fhir\packages
  Params: c:\Temp\empty\lab\input\examples\14221022-Copy.xml -ig hl7.fhir.be.lab
Scanning for versions (no -version parameter):
Installing hl7.fhir.be.lab#1.0.0 to the package cache
  Fetching:
.
  Installing: . done.
  Package hl7.fhir.be.lab: 4.0
-> use version 4.0
  Jurisdiction: United States of America
Loading
  Load FHIR v4.0 from hl7.fhir.r4.core#4.0.1.Can't find BackboneElement profile http://hl7.org/fhir/StructureDefinition/document-section-library but trying to go on
Can't find BackboneElement profile http://hl7.org/fhir/StructureDefinition/document-section-library but trying to go on
Can't find BackboneElement profile http://hl7.org/fhir/StructureDefinition/document-section-library but trying to go on
: - 4576 resources (00:05.459)
  Load hl7.terminology#5.1.0 - 4180 resources (00:01.995)
  Load R5 Extensions - 151 resources (00:03.229)
  Terminology server http://tx.fhir.org - Version 2.0.14 (00:01.219)
  Load hl7.terminology.r4#3.1.0 - 4117 resources (00:01.232)
  Load hl7.fhir.be.core#2.0.0 - 23 resources (00:00.034)
Installing hl7.fhir.be.core-clinical#1.0.0 to the package cache
  Fetching:

  Installing:  done.
  Load hl7.fhir.be.core-clinical#1.0.0 - 19 resources (00:00.314)
  Load hl7.fhir.be.lab#1.0.0 - 15 resources (00:00.005)
  Package Summary: [hl7.fhir.r4.core#4.0.1, hl7.fhir.xver-extensions#0.0.12, hl7.terminology#5.1.0, hl7.terminology.r4#3.1.0, hl7.fhir.be.core#2.0.0, hl7.fhir.be.core-clinical#1.0.0, hl7.fhir.be.lab#1.0.0]
  Get set...  go (00:00.213)
Validating
  Validate c:\Temp\empty\lab\input\examples\14221022-Copy.xml
Validate Bundle against http://hl7.org/fhir/StructureDefinition/Bundle|4.0.1..........20..........40..........60..........80.........|
 00:17.600
Done. Times: Loading: 00:14.822, validation: 00:17.601. Memory = 317Mb

*FAILURE*: 58 errors, 1 warnings, 72 notes
  Error @ Bundle.id (line 7, col33): As specified by profile http://hl7.org/fhir/StructureDefinition/Bundle|4.0.1, Element 'id' is out of order (found after identifier)
  Error @ Bundle.entry[0].resource/*Composition/Report-2301168790*/.date (line 31, col47): As specified by profile http://hl7.org/fhir/StructureDefinition/Composition|4.0.1, Element 'date' is out of order (found after title)
  Error @ Bundle.entry[1].resource/*Observation/Test-00333*/.issued (line 68, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[2].resource/*Observation/Test-00185*/.issued (line 124, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[3].resource/*Observation/Test-00002*/.issued (line 180, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[4].resource/*Observation/Test-00298*/.issued (line 236, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[5].resource/*Observation/Test-00299*/.issued (line 292, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[6].resource/*Observation/Test-00300*/.issued (line 348, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[7].resource/*Observation/Test-00003*/.issued (line 404, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[8].resource/*Observation/Test-00093*/.issued (line 460, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[9].resource/*Observation/Test-00095*/.issued (line 516, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[10].resource/*Observation/Test-00096*/.issued (line 572, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[11].resource/*Observation/Test-00004*/.issued (line 628, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[12].resource/*Observation/Test-00070*/.issued (line 684, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[14].resource/*Observation/Test-00749*/.issued (line 775, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[15].resource/*Observation/Test-00007*/.issued (line 831, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[16].resource/*Observation/Test-01731*/.issued (line 887, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[17].resource/*Observation/Test-00550*/.issued (line 943, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[18].resource/*Observation/Test-01730*/.issued (line 999, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[20].resource/*Observation/Test-00551*/.issued (line 1090, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[21].resource/*Observation/Test-00552*/.issued (line 1146, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[22].resource/*Observation/Test-00008*/.issued (line 1202, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[23].resource/*Observation/Test-00056*/.issued (line 1258, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[25].resource/*Observation/Test-01118*/.issued (line 1373, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[27].resource/*Observation/Test-00045*/.issued (line 1453, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[29].resource/*Observation/Test-00182*/.issued (line 1532, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[30].resource/*Observation/Test-00035*/.issued (line 1588, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[31].resource/*Observation/Test-00034*/.issued (line 1644, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[32].resource/*Observation/Test-00037*/.issued (line 1700, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[33].resource/*Observation/Test-00135*/.issued (line 1756, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[34].resource/*Observation/Test-00038*/.issued (line 1812, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[36].resource/*Observation/Test-01070*/.issued (line 1907, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[37].resource/*Observation/Test-01078*/.issued (line 1963, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[37].resource/*Observation/Test-01078*/.interpretation[0] (line 1968, col17): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'interpretation' is out of order (found after note)
  Error @ Bundle.entry[39].resource/*Observation/Test-00051*/.issued (line 2029, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[40].resource/*Observation/Test-00553*/.issued (line 2085, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[41].resource/*Observation/Test-00169*/.issued (line 2141, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[43].resource/*Observation/Test-00030*/.issued (line 2227, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[45].resource/*Observation/Test-03213*/.issued (line 2307, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[46].resource/*Observation/Test-00442*/.issued (line 2363, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[47].resource/*Observation/Test-00146*/.issued (line 2419, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[48].resource/*Observation/Test-02541*/.issued (line 2456, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[48].resource/*Observation/Test-02541*/.interpretation[0] (line 2468, col17): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'interpretation' is out of order (found after note)
  Error @ Bundle.entry[49].resource/*Observation/Test-00330*/.issued (line 2503, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[49].resource/*Observation/Test-00330*/.interpretation[0] (line 2514, col17): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'interpretation' is out of order (found after note)
  Error @ Bundle.entry[50].resource/*Observation/Test-00571*/.issued (line 2563, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[50].resource/*Observation/Test-00571*/.interpretation[0] (line 2573, col17): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'interpretation' is out of order (found after note)
  Error @ Bundle.entry[51].resource/*Observation/Test-00569*/.issued (line 2608, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[51].resource/*Observation/Test-00569*/.interpretation[0] (line 2619, col17): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'interpretation' is out of order (found after note)
  Error @ Bundle.entry[52].resource/*Observation/Test-00156*/.issued (line 2654, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[54].resource/*Observation/Test-04508*/.issued (line 2755, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[54].resource/*Observation/Test-04508*/.interpretation[0] (line 2762, col17): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'interpretation' is out of order (found after note)
  Error @ Bundle.entry[56].resource/*Observation/Test-00494*/.issued (line 2821, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[58].resource/*Observation/Test-01081*/.issued (line 2901, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[59].resource/*Observation/Test-01082*/.issued (line 2957, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[60].resource/*Observation/Test-01083*/.issued (line 3013, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[61].resource/*Observation/Test-01085*/.issued (line 3043, col49): As specified by profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1, Element 'issued' is out of order (found after performer)
  Error @ Bundle.entry[63].resource/*DiagnosticReport/Report-2301168790*/.language (line 3090, col24): As specified by profile http://hl7.org/fhir/StructureDefinition/DiagnosticReport|4.0.1, Element 'language' is out of order (found after identifier)
  Information @ Bundle.entry[13].resource/*Observation/Title-T02554*/.hasMember[0] (line 732, col12): Details for Observation/Test-00093 
matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[13].resource/*Observation/Title-T02554*/.hasMember[1] (line 735, col12): Details for Observation/Test-00095 
matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[13].resource/*Observation/Title-T02554*/.hasMember[2] (line 738, col12): Details for Observation/Test-00096 
matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[13].resource/*Observation/Title-T02554*/.hasMember[3] (line 741, col12): Details for Observation/Test-00004 
matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[13].resource/*Observation/Title-T02554*/.hasMember[4] (line 744, col12): Details for Observation/Test-00070 
matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[19].resource/*Observation/Title-T02555*/.hasMember[0] (line 1047, col12): Details for Observation/Test-00749 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[19].resource/*Observation/Title-T02555*/.hasMember[1] (line 1050, col12): Details for Observation/Test-00007 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[19].resource/*Observation/Title-T02555*/.hasMember[2] (line 1053, col12): Details for Observation/Test-01731 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[19].resource/*Observation/Title-T02555*/.hasMember[3] (line 1056, col12): Details for Observation/Test-00550 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[19].resource/*Observation/Title-T02555*/.hasMember[4] (line 1059, col12): Details for Observation/Test-01730 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[24].resource/*Observation/Header-102*/.hasMember[0] (line 1306, col12): Details for Observation/Test-00333 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[24].resource/*Observation/Header-102*/.hasMember[1] (line 1309, col12): Details for Observation/Test-00185 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[24].resource/*Observation/Header-102*/.hasMember[2] (line 1312, col12): Details for Observation/Test-00002 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[24].resource/*Observation/Header-102*/.hasMember[3] (line 1315, col12): Details for Observation/Test-00298 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[24].resource/*Observation/Header-102*/.hasMember[4] (line 1318, col12): Details for Observation/Test-00299 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[24].resource/*Observation/Header-102*/.hasMember[5] (line 1321, col12): Details for Observation/Test-00300 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[24].resource/*Observation/Header-102*/.hasMember[6] (line 1324, col12): Details for Observation/Test-00003 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[24].resource/*Observation/Header-102*/.hasMember[9] (line 1333, col12): Details for Observation/Test-00551 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[24].resource/*Observation/Header-102*/.hasMember[10] (line 1336, col12): Details for Observation/Test-00552 
matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[24].resource/*Observation/Header-102*/.hasMember[11] (line 1339, col12): Details for Observation/Test-00008 
matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[24].resource/*Observation/Header-102*/.hasMember[12] (line 1342, col12): Details for Observation/Test-00056 
matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[26].resource/*Observation/Header-104*/.hasMember[0] (line 1422, col12): Details for Observation/Test-01118 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[28].resource/*Observation/Header-105*/.hasMember[0] (line 1501, col12): Details for Observation/Test-00045 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[35].resource/*Observation/Header-106*/.hasMember[0] (line 1861, col12): Details for Observation/Test-00182 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[35].resource/*Observation/Header-106*/.hasMember[1] (line 1864, col12): Details for Observation/Test-00035 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[35].resource/*Observation/Header-106*/.hasMember[2] (line 1867, col12): Details for Observation/Test-00034 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[35].resource/*Observation/Header-106*/.hasMember[3] (line 1870, col12): Details for Observation/Test-00037 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[35].resource/*Observation/Header-106*/.hasMember[4] (line 1873, col12): Details for Observation/Test-00135 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[35].resource/*Observation/Header-106*/.hasMember[5] (line 1876, col12): Details for Observation/Test-00038 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[38].resource/*Observation/Header-107*/.hasMember[0] (line 1995, col12): Details for Observation/Test-01070 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[38].resource/*Observation/Header-107*/.hasMember[1] (line 1998, col12): Details for Observation/Test-01078 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[42].resource/*Observation/Header-108*/.hasMember[0] (line 2190, col12): Details for Observation/Test-00051 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[42].resource/*Observation/Header-108*/.hasMember[1] (line 2193, col12): Details for Observation/Test-00553 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[42].resource/*Observation/Header-108*/.hasMember[2] (line 2196, col12): Details for Observation/Test-00169 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[44].resource/*Observation/Header-109*/.hasMember[0] (line 2276, col12): Details for Observation/Test-00030 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[53].resource/*Observation/Header-112*/.hasMember[0] (line 2703, col12): Details for Observation/Test-03213 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[53].resource/*Observation/Header-112*/.hasMember[1] (line 2706, col12): Details for Observation/Test-00442 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[53].resource/*Observation/Header-112*/.hasMember[2] (line 2709, col12): Details for Observation/Test-00146 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[53].resource/*Observation/Header-112*/.hasMember[3] (line 2712, col12): Details for Observation/Test-02541 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[53].resource/*Observation/Header-112*/.hasMember[4] (line 2715, col12): Details for Observation/Test-00330 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[53].resource/*Observation/Header-112*/.hasMember[5] (line 2718, col12): Details for Observation/Test-00571 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[53].resource/*Observation/Header-112*/.hasMember[6] (line 2721, col12): Details for Observation/Test-00569 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[53].resource/*Observation/Header-112*/.hasMember[7] (line 2724, col12): Details for Observation/Test-00156 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[55].resource/*Observation/Header-111*/.hasMember[0] (line 2790, col12): Details for Observation/Test-04508 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[57].resource/*Observation/Header-114*/.hasMember[0] (line 2870, col12): Details for Observation/Test-00494 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[62].resource/*Observation/Header-224*/.hasMember[0] (line 3066, col12): Details for Observation/Test-01081 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[62].resource/*Observation/Header-224*/.hasMember[1] (line 3069, col12): Details for Observation/Test-01082 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[62].resource/*Observation/Header-224*/.hasMember[2] (line 3072, col12): Details for Observation/Test-01083 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[62].resource/*Observation/Header-224*/.hasMember[3] (line 3075, col12): Details for Observation/Test-01085 matching against profile http://hl7.org/fhir/StructureDefinition/Observation|4.0.1
  Information @ Bundle.entry[1].resource/*Observation/Test-00333*/.code.coding[0] (line 53, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[13].resource/*Observation/Title-T02554*/.code.coding[0] (line 722, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[17].resource/*Observation/Test-00550*/.value.ofType(Quantity) (line 944, col16): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[17].resource/*Observation/Test-00550*/.referenceRange[0].low (line 958, col6): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[17].resource/*Observation/Test-00550*/.referenceRange[0].high (line 964, col7): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[19].resource/*Observation/Title-T02555*/.code.coding[0] (line 1037, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[20].resource/*Observation/Test-00551*/.code.coding[0] (line 1075, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[21].resource/*Observation/Test-00552*/.code.coding[0] (line 1131, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[26].resource/*Observation/Header-104*/.code.coding[0] (line 1411, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[35].resource/*Observation/Header-106*/.code.coding[0] (line 1850, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[42].resource/*Observation/Header-108*/.code.coding[0] (line 2179, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[44].resource/*Observation/Header-109*/.code.coding[0] (line 2265, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[45].resource/*Observation/Test-03213*/.value.ofType(Quantity) (line 2308, col16): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[45].resource/*Observation/Test-03213*/.referenceRange[0].low (line 2322, col6): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[45].resource/*Observation/Test-03213*/.referenceRange[0].high (line 2328, col7): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[53].resource/*Observation/Header-112*/.code.coding[0] (line 2692, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[54].resource/*Observation/Test-04508*/.code.coding[0] (line 2740, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[55].resource/*Observation/Header-111*/.code.coding[0] (line 2779, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[57].resource/*Observation/Header-114*/.code.coding[0] (line 2859, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[58].resource/*Observation/Test-01081*/.code.coding[0] (line 2886, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[60].resource/*Observation/Test-01083*/.code.coding[0] (line 2998, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[61].resource/*Observation/Test-01085*/.code.coding[0] (line 3028, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Information @ Bundle.entry[62].resource/*Observation/Header-224*/.code.coding[0] (line 3055, col9): Code System URI 'https://www.nuytinck.be' is unknown so the code cannot be validated
  Warning @ Bundle.entry[65].resource/*Patient/Patient-2301168790*/.birthDate (line 3220, col33): The value '0001-01-01' is outside the range of reasonable years - check for data entry error
sttav commented 1 year ago

@bdc-ehealth FYI yes, we get multiple errors but mainly because the ordering does not follow the XML schema (out of order errors). This is a bit annoying, because there seems to be no prescribed ordering for the json structure.

bdc-ehealth commented 1 year ago

@sttav @KristiaanJaques ,

For your attempts on the test server, I saw that you are not sending the de profile information in the meta.profile section. That is the reason most of your tests fail.

KristiaanJaques commented 1 year ago

Dear bdc-ehealth,

A genuine concern is developling concerning the stability of validation criteria during the homologation procedure.

A number of our test files was classified as "passed" in the homologation procedure until yesterday.

All of a sudden, none of these files had the status "passed" anymore.

The concern is that when we solve this situation and modify the files to pass, later the criteria will change again and we can start all over with development.

In this specific case, the meta.profile element is not a required element in the international FHIR standard.

https://github.com/hl7-be/lab/issues/181#issuecomment-1680541207

Resource.meta Cardinality 0..1

https://www.hl7.org/fhir/resource.html#Meta

... profile S 0..* canonical(StructureDefinition) Profiles this resource claims to conform to

Did we miss a specific national requirement? Can you point us to the specific national requirement documentation?

With kind regards.

bdc-ehealth commented 1 year ago

@KristiaanJaques ,

As you say, the indication of the profile is not mandatory for the international profile. However, you are developing for the Belgian profile. If you do not indicate that you are creating a file for the Belgian profile, there is no way for the tools to guess that you are doing so. Files that comply with the Belgian standard are a subset of the files that comply with the international standard.

As for the changing of the test conditions, the test conditions are made together with clinical biologists, who in case of doubt, judge the clinical risk associated with variations in files that claim to conform with the testcase. If they judge that the risk for clinical mistakes is too high, we make the rules for a particular testcase more strict to avoid the clinical risk (all labs and softwares that already passed the test are re-evaluated so that everybody is evaluated according to the same criteria). This is an advantage, because the informal, intuitive, textual description of a testcase (which is often not very clear at the beginning) is replaced by a objective way of evaluation that is more precise, checkable by a computer and the same for everyone. If you do not agree with the interpretation of the testcase, you can always use the "yellow" button, and we will discuss your input with the clinical biologists. So also your input may cause a change in the testrules, which is a very healthy thing from a collaborative point of view.

In your particular case, the files that do not contain the information about the Belgian profile, are not displayed by the visualizer, because they are not recognized as Belgian files. Since the clinical biologists use the visualizer tool as the means for their evaluation, they were not able to evaluate the files you were providing.