Stream: implementers
Topic: STU3 validation messages doesn’t contain resource name
Mritunjay Dubey (Apr 21 2017 at 03:22):
Hello guys,
After upgrading our servers to hapi-fhir stu3 we saw a change in the way validation messages are given.
For example /f:Bundle/f:entry/f:resource/f:Condition/f:code/f:coding[1] is changed to Bundle.entry[3].resource.code.coding[1]. Any specific reason why the resourcename i.e. Condition is not present?
There are times when we are doing some task when Condition.category gives a validation-error, but we don't want same for ProcedureRequest.Category. The exisiting message was easy to distinguish but now it's not possible.
Lloyd McKenzie (Apr 21 2017 at 06:28):
The old mechanism was an xpath, the new mechanism is a FHIRPath. And in FHIRPath, the entry is just known as "resource" because that's what the model knows it as. XPath introduced an extra layer to manage the choice.
Lloyd McKenzie (Apr 21 2017 at 06:28):
Given that you should know what you sent, figuring out what resource it was shouldn't be that hard . . .
Last updated: Apr 12 2022 at 19:14 UTC
