Stream: implementers
Topic: Validation - Reject resource if no meta.profile
Andreas (Jun 11 2020 at 10:07):
Hi, we are implementing validation on our FHIR-server with HAPI, and are using the RequestValidatingInterceptor with a ValidationSupportChain consisting of DefaultProfileValidationSupport, PrePopulatedValidationSupport, InMemoryTerminologyServerValidationSupport. We have loaded our own StructureDefinitions into the PrePopulatedValidationSupport and want to only validate against these. This works if the resource contains a profile-url in meta.profile. But if the client does not provide a meta.profile-url, they can get around validating against our provided StructureDefinitions.
Is it possible with HAPI (or the validator) to reject any resource that does not conform to our provided StructureDefinitions?
Michele Mottini (Jun 11 2020 at 13:38):
Try the #hapi stream
Jose Costa Teixeira (Jun 11 2020 at 13:40):
yes, I also want to know how, and will ask this in the HAPI stream
Michele Mottini (Jun 11 2020 at 13:42):
(I am trying to push HAPI-specific stuff to #hapi to make #implementers less noisy)
Last updated: Apr 12 2022 at 19:14 UTC
