Closed pdi-uk closed 3 years ago
@pdi-uk: Can you perhaps provide us with the input ODM that provokes this error? From the provided error message it looks like you might tried to send the output of a single ODM2FHIR run several times to your FHIR server (as we currently generate a new, unique UUID for each resource during each run of ODM2FHIR).
The ODM2FHIR
app already has a built-in HAPI FHIR validator, which ensures that invalid FHIR resources are not added to the bundle.
When testing the method you described above with our dummy data output, the online validator only delivers errors/warnings of the following types:
I cannot reproduce the error you described. So it would be good to get a copy of your input-ODM, as @holger-stenzhorn already said.
this is our input ODM:
Thanks! I will check the problem and come back to you tomorrow.
@pdi-uk Admittedly, this does not really concern your reported issue but still... :-) Which version of the data dictionary did you actually import into REDCap to create the instruments in there? It looks like you used the quite outdated one from 23.10.2020 which sadly does not work correctly with the recent ODM2FHIR. ...or did you just accidentally provide here an ancient export from 10.12.2020 and you have a more recent one based on the data dictionary from 13.11.2020 or (even better) 11.12.2020?
The version information of the data dictionary is lost in RedCap after uploading, but I think we used the data dictionary from 13.11.2020. However, we will try again with the newest version of the data dictionary.
You have to remember that if you update the data dictionary, the already filled in forms WILL NOT BE UPDATED!
Changes can therefore only be determined in the forms edited afterwards.
We updated the data dictionary and created a new sample patient. The error mentionted above does not appear any more when trying to validate the bundle.
Okay, thats good! I will close the issue as it's solved.
Describe the bug Error messages on HAPI test server when trying to validate json-bundle gererated by ODMtoFHIR
To Reproduce Steps to reproduce the behavior:
Expected behavior Status 201 created
Screenshots Status 412
Error Messages:
{ "severity": "error", "code": "processing", "diagnostics": "bdl-7: FullUrl must be unique in a bundle, or else entries with the same fullUrl must have different meta.versionId (except in history bundles) [(type = 'history') or entry.where(fullUrl.exists()).select(fullUrl & resource.meta.versionId).isDistinct()]", "location": [ "Bundle", "Line 1, Col 2" ] }
Desktop (please complete the following information):