FHIR Chat · Error null validating Coding · clinFHIR

Stream: clinFHIR

Topic: Error null validating Coding


view this post on Zulip Lauri Karppinen (Jul 11 2018 at 08:13):

Hi! @David Hay Did'n notice this stream. Know that I know i'll reply here. Here is the JSON screenshot. Gives error but still uploads to server. Error-null-validating-Coding.PNG

view this post on Zulip David Hay (Jul 11 2018 at 17:57):

hmm. seems OK and I can retrieve from the server (https://fhirtest.uhn.ca/baseDstu3/Observation/cf-1531225812689) - what error are you getting?

view this post on Zulip Lauri Karppinen (Jul 12 2018 at 11:57):

I have made many different observations and every one them is giving error: "Error null validating Coding". Maybe i'm missing something obvious since I'm new to FHIR. Patient is only resource not giving any errors. I can still upload and read all the resources with no problem. That seems pretty weird. Since scenario builder also shows red cross in valid column for observations: "Resource is not valid".

JSON from error code:
{
"severity": "error",
"code": "processing",
"diagnostics": "Error null validating Coding",
"location": [
"Parameters.parameter.resource.code.coding"
]
},

view this post on Zulip Lloyd McKenzie (Jul 12 2018 at 14:30):

The terminology server pointed to by the validator by default is down. For now, you can override what server the validator is pointing to or you can specify a server of n/a. FOr the IGPublisher, you can only do the latter.

view this post on Zulip David Hay (Jul 12 2018 at 18:23):

I suspect this is a HAPI issue - when I try the validate operation directly (https://fhirtest.uhn.ca/baseDstu3/Observation/cf-1531225812689/$validate - which is similar to what CF does) I do get this error (as well as a complaint about lacking a performer and date). I'll post to the HAPI group and see what comments I get. In the mean time, just carry on!

view this post on Zulip Lauri Karppinen (Aug 06 2018 at 05:22):

Thanks a lot for the information David and Lloyd!


Last updated: Apr 12 2022 at 19:14 UTC