Stream: hapi
Topic: Error with ValueSets
Kevin Power (Sep 29 2018 at 19:44):
When POST'ing a new StructureDefinition, I am seeing the following error:
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "Invalid resource reference found at path[StructureDefinition.snapshot.element.binding.valueSet] - Resource type is unknown or not supported on this server - http://loinc.org/vs/LL4033-8"
}
]
For a different ValueSet, I tried uploading the ValueSet as its own resource, but I got the same error when later trying to POST the StructureDefinition. However, if we add ValueSet to the name (as in http://loinc.org/vs/ValueSet/LL4033-8), the validation error goes away. Is there a requirement to have ValueSet in the name?
Any recommendations?
Kevin Power (Sep 29 2018 at 19:57):
According to this https://www.hl7.org/fhir/loinc.html#alist, how we have it (http://loinc.org/vs/LL4033-8) looks OK?
Patrick Werner (Sep 29 2018 at 20:06):
@James Agnew
i don't get the error in the current snapshot deployed locally. Could you please update fhirtest.uhn.ca/baseR4 ?
Patrick Werner (Sep 29 2018 at 20:10):
nvm we now run in the next issue:
Caused by: org.hl7.fhir.exceptions.FHIRException: Unable to find type canonical for element valueCanonical with path Extension.value[x]
This will take some time to fix as you mentioned in the latest release notes.
Grahame Grieve (Sep 29 2018 at 20:37):
the loinc issue... sounds like a bug. Sometimes I forgot to check for implicit value sets
Patrick Werner (Sep 29 2018 at 21:12):
the loinc issue seems to be fixed in the latest hapi snapshot.
Now VS bindings with urls without "ValueSet" as part of the url are working
Grahame Grieve (Sep 30 2018 at 14:29):
great
Last updated: Apr 12 2022 at 19:14 UTC
