FHIR Chat · dom-3 and fhirpath trace function · implementers

Stream: implementers

Topic: dom-3 and fhirpath trace function


view this post on Zulip Jim Steel (Oct 31 2018 at 01:00):

I'm getting an error in some validation code that is trying to evaluate the dom-3 constraint on DomainResource, saying that the trace function should only have one parameter. This seems to agree with the FHIRPath spec at http://hl7.org/fhirpath/.

It seems like dom-3 might be broken, which seems like its fairly significant. Question: am I looking in the right places for these things?

view this post on Zulip Grahame Grieve (Oct 31 2018 at 01:05):

see build.fhir.org/fhirpath.html#functions

view this post on Zulip Jim Steel (Oct 31 2018 at 04:05):

Ah, cool. In that case the problem might be in the HAPI fhirpath implementation I'm using rather than in the constraint

view this post on Zulip Grahame Grieve (Oct 31 2018 at 04:06):

what version are you using? I updated the R4 one a long time ago....

view this post on Zulip Jim Steel (Oct 31 2018 at 04:06):

Using 3.5.0

view this post on Zulip Jim Steel (Oct 31 2018 at 04:07):

And yes, R4

view this post on Zulip Grahame Grieve (Oct 31 2018 at 04:13):

well, the current one accepts 2 parameters. I would think I made this change several months ago at least

view this post on Zulip Grahame Grieve (Oct 31 2018 at 04:14):

@James Agnew when would this be updated in HAPI? I thought you did a release a few weeks back?

view this post on Zulip James Agnew (Oct 31 2018 at 20:40):

@Jim Steel could you try this on the current 3.6.0 snapshot builds? This will be released within the next 2 weeks.


Last updated: Apr 12 2022 at 19:14 UTC