New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relatedperson-relationshiptype value set validation fails #370

volodymyr-vynnytskyi opened this Issue May 24, 2016 · 3 comments


None yet
2 participants

volodymyr-vynnytskyi commented May 24, 2016


I'm using RequestValidationInterceptor with FhirInstanceValidator and during validation of "myRelationship" field of custom resource extended from RelatedPerson I am able to see error below:

UnprocessableEntityException: HTTP 422 Unprocessable Entity: None of codes provided are in the value set

Other resources with CodeableConceptDt field passed validation without any errors.
Looks like it is related with fact that above value set also includes another one ("")`.
I tried to set such system as "", "" and "" but there was the same error.
Also, I debugged HapiWorkerContext.validateCode() method and notice that "expansion" and "concept" fields in ValueSet have null values.

Have you any idea what is cause of this issue?


This comment has been minimized.


jamesagnew commented Jun 8, 2016

Hi @Xoude,

Thanks for reporting!

This turned out to be an issue with the actual codesystem as distributed by HL7. It turns out it was missing a code that was preventing successful validation.

I'm checking in a fix shortly, so the next 1.6-SNAPSHOT should be able to validate this successfully.

@jamesagnew jamesagnew closed this in 0a2b429 Jun 8, 2016


This comment has been minimized.

volodymyr-vynnytskyi commented Jun 17, 2016

Hi @jamesagnew ,

Thanks a lot!


This comment has been minimized.

volodymyr-vynnytskyi commented Sep 27, 2016

If i'm not wrong u fixed it in 'hapi-fhir-structures-dstu3' module, but in 'hapi-fhir-structures-hl7org-dstu2' i'm able to reproduce above issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment