Stream: hapi
Topic: why can this ValueSet not be validated against?
Job Schipper (Jun 29 2020 at 15:09):
Hi,
When validating the following test patient against a profile I get the following validation warning:
GET http://hapi.fhir.org/baseDstu3/Patient/2725779/$validate
...
{
"severity": "warning",
"code": "processing",
"diagnostics": "Could not confirm that the codes provided are in the value set http://decor.nictiz.nl/fhir/ValueSet/2.16.840.1.113883.2.4.3.11.60.40.2.20.5.2--20171231000000, and a code should come from this value set unless it has no suitable code",
"location": [
"Patient.address[0].country.extension[0].value.ofType(CodeableConcept).coding[0]",
"Line 1, Col 511"
]
}
...
The valueset itself includes country codes from the codesystem urn:iso:std:iso:3166 which is part of STU3 according to https://www.hl7.org/fhir/stu3/terminologies-systems.html
GET http://hapi.fhir.org/baseDstu3/ValueSet/2.16.840.1.113883.2.4.3.11.60.40.2.20.5.2--20171231000000
"compose": {
"include": [
{
"system": "urn:iso:std:iso:3166"
}
]
}
I have seen ValueSet validation work in HAPI before, so I'm wondering why it is unable to do so in this case. Does the ValueSet validation not support the "include" mechanisms for codesystems?
As always, all help is very much appreciated!
Grahame Grieve (Jun 29 2020 at 19:35):
what is your nominated terminology server?
Job Schipper (Jun 30 2020 at 10:51):
@Grahame Grieve I have no idea to be honest. How can i find out?
Grahame Grieve (Jun 30 2020 at 21:29):
well, it'll be the way you set HAPI up. Unless you are using the CLI directly
Job Schipper (Jul 02 2020 at 14:43):
in my case i am using the public test server @ http://hapi.fhir.org/baseDstu3/ (which happens to be down right now).
Is there a way to retrieve what terminology server it is using from the API?
Also we are in the process of setting up our own HAPI JPA server, so I am interestig to learn more about setting this up. Is there any documentation you can recommend on this subject? I've been looking at https://hapifhir.io/hapi-fhir/docs/server_jpa/introduction.html but i haven't seen anything on configuring a terminology server.
James Agnew (Jul 07 2020 at 15:19):
Hi @Job Schipper - FYI this looks to be a bug in HAPI's term service, I was able to reproduce the results you're seeing locally. We do support ISO3166 validation but it doesn't look like it's working for pre-expanded ValueSets. I'm still investigating why.
Job Schipper (Jul 13 2020 at 08:05):
@James Agnew interesting, did you find out more?
James Agnew (Jul 13 2020 at 09:53):
Yup, this has been fixed on current master. The validation you linked above now works correctly.
Job Schipper (Jul 16 2020 at 10:52):
@James Agnew Great, thanks a lot!
Last updated: Apr 12 2022 at 19:14 UTC