FHIR Chat · FHIRPath tester questions · implementers

Stream: implementers

Topic: FHIRPath tester questions


view this post on Zulip Marten Smits (Mar 03 2017 at 09:39):

We are using the FHIRPath tester from: https://github.com/brianpos/FhirPathTester @Brian Postlethwaite
Using exists with a criteria is an unrecognized functions signature, same for allTrue() and allFalse() and a few others. Is the tester or the spec wrong?

view this post on Zulip Grahame Grieve (Mar 03 2017 at 10:53):

tester is wrong here

view this post on Zulip Brian Postlethwaite (Mar 03 2017 at 11:19):

Yes, the dotnet fhirpath lib needs an update to support it.

view this post on Zulip Marten Smits (Mar 03 2017 at 12:24):

Ok, thanks!

view this post on Zulip Mario Hyland (Mar 04 2017 at 00:50):

Touchstone 3.3.0 Enhancements: Add support for FHIRPath evaluation when used in TestScript “variable.expression”,
“assertion.expression”, and “assertion.compareToSourceExpression” elements.

The Advanced-FHIR1-8-0, Basic-FHIR1-8-0, and Connectathon14 test scripts use FHIRPath expressions for some assertion evaluations.

Details can be found at http://hl7.org/fhirpath/index.html

Touchstone continues to support “variable.path”, “assertion. path”, and “assertion. path” elements where built-in to XPath/JSONPath is executed.

Is there something specific you are looking to test? I will let @Richard Ettema answer anything more detailed or technical.


Last updated: Apr 12 2022 at 19:14 UTC