Stream: hapi
Topic: Validating differences. Hapi CLI vs. library
Robin Bosman (Nov 10 2020 at 16:04):
Hello, some of our users stumbled on some behavior that creates some ambiguity in implementation and documentation.
It seems when validating using the Hapi libraries, we seem to be missing <details> and <expression> in the OperationOutcome as opposed to validating using the CLI.
Is this normal behavior or is there something we need to do to also get <details> and <expression> when using the libraries?
Any feedback how we should approach this is highly appreciated.
Just as an example what we mean:
When using the ValidationResult using the Hapi libraries we always get an OperationOutcome e.g. in this style
[...]
<diagnostics value="Unknown code[...]'"></diagnostics>
<location value="Bundle.entry[0].resource.ofType(MessageHeader).event.ofType(Coding)"></location>
<location value="Line 1, Col 670"></location>
[...]
...as opposed to when we use the CLI, the OperationOutcome is quite different:
and something in this style:
[...]
<severity value="warning"/>
<code value="code-invalid"/>
<details>
<text value="The Coding provided [...] is not in the value set [...] (error message = Not in value set http://www.mycarenet.be/fhir/ValueSet/eagreementadjudicationreason)"/>
</details>
<expression value="Bundle.entry[4].resource.ofType(Bundle).entry[5].resource.ofType(ClaimResponse).addItem[0].adjudication[0].reason.coding[0]"/>
</issue>
Robin Bosman (Nov 23 2020 at 07:46):
Hello everyone, is there no input on this? (Or is there maybe an easy way to deal with this?)
Grahame Grieve (Nov 23 2020 at 12:04):
@Mark Iantorno can you add this to your list please
Mark Iantorno (Nov 24 2020 at 13:55):
I will give this another go. The two validators need to be aligned.
Patrick Werner (Nov 24 2020 at 19:30):
thanks! @Mark Iantorno & @Grahame Grieve
Last updated: Apr 12 2022 at 19:14 UTC
