Stream: implementers
Topic: HAPI FHIR validating R3 upgraded to R4 FHIR msg
Maria Hu (Sep 11 2020 at 18:58):
When feeding a FHIR R4 msg with deprecated elements from R3, it appears that HAPI FHIR just ignore it without returning any errors/warnings/information, the assumption is that HAPI FHIR is being backward compatible and accepts the deprecated elements from R3.
e.g. resourceImmunization.notGiven is an R3 element which has been deprecated in R4, but if send in a R4 msg HAPI FHIR did not reject it.
However if the same R4 msg is feed through a generic FHIR validator, ( e.g. the validator posted on Simplifier.net), the R4 msg is rejected as non-conformant.
Question: Is this the expected behaviour of HAPI FHIR accepting R4 msg with deprecated R3 elements without any errors/warnings/information? Has anyone encountered this issue and how to resolve it? Please advise, thanks.
Lloyd McKenzie (Sep 11 2020 at 19:21):
@James Agnew
Grahame Grieve (Sep 14 2020 at 00:10):
yes. this is the difference between an operational server and a validator. The validator will always be strict, where as actual operational systems are allowed to (though not required to) ignore unknown elements
Maria Hu (Sep 14 2020 at 20:54):
Thanks Grahame.
Wonder if the operational systems can return a WARNING or INFORMATION regarding the deprecated elements? Can it be configured somewhere? Pls advise, thanks.
Last updated: Apr 12 2022 at 19:14 UTC
