Is there a plan to support the function mentioned there ? https://build.fhir.org/ig/HL7/FHIRPath/en/changes.html
thanks in advance
I asked an LLM to describe what it means:
Description
Background
The official FHIRPath 3.0.0 STU 3 has been released with a significant number of new functions, improved semantics, and clarifications.
Goals
- Achieve high conformance with FHIRPath 3.0.0 STU 3
- Pass (or clearly document) the updated official
fhir-test-cases
- Maintain backward compatibility with existing 2.x behavior where possible
- Update documentation and conformance table
Key Changes to Implement (from official changelog)
New Functions
coalesce()
sort()
repeatAll()
defineVariable()
matchesFull()
indexOf(), lastIndexOf()
comparable()
pathname()
- Aggregate:
sum(), min(), max(), avg()
- Date/time extractors:
yearOf(), monthOf(), dayOf(), hourOf(), minuteOf(), secondOf(), millisecondOf(), timezoneOffsetOf(), dateOf(), timeOf()
- Boundary/precision:
lowBoundary(), highBoundary(), precision()
Language / Type System
Long (integer64) literal with required L suffix
- Constructor syntax support (
System.String(...), etc.)
combine(preserveOrder) overload
- Case-sensitivity options for regex functions (
matches, replaceMatches, etc.)
- Date/time subtraction improvements
Clarifications & Behavior Changes
- Singleton evaluation rules
iif() lazy evaluation
- Equality & comparison semantics
- Quantity / UCUM handling
- Many example corrections
Proposed Implementation Plan
- Grammar & Parser – Update
FHIRPath.g4 and regenerate ANTLR artifacts (Long literal + constructor syntax).
- Core Functions – Implement by priority (see below).
- Type System – Add full
Long support.
- Testing – Integrate latest
fhir-test-cases and update conformance table.
- Documentation & Release – Update README, changelog, and bump version.
Priority Order
- Grammar + Long literal + constructor syntax
coalesce, sort, aggregates (sum/min/max/avg)
- Date extractors +
lowBoundary/highBoundary/precision
- String/index functions +
repeatAll/combine
defineVariable, comparable, pathname
- All clarifications and test fixes
Acceptance Criteria
Is there a plan to support the function mentioned there ? https://build.fhir.org/ig/HL7/FHIRPath/en/changes.html
thanks in advance
I asked an LLM to describe what it means:
Description
Background
The official FHIRPath 3.0.0 STU 3 has been released with a significant number of new functions, improved semantics, and clarifications.
Goals
fhir-test-casesKey Changes to Implement (from official changelog)
New Functions
coalesce()sort()repeatAll()defineVariable()matchesFull()indexOf(),lastIndexOf()comparable()pathname()sum(),min(),max(),avg()yearOf(),monthOf(),dayOf(),hourOf(),minuteOf(),secondOf(),millisecondOf(),timezoneOffsetOf(),dateOf(),timeOf()lowBoundary(),highBoundary(),precision()Language / Type System
Long(integer64) literal with requiredLsuffixSystem.String(...), etc.)combine(preserveOrder)overloadmatches,replaceMatches, etc.)Clarifications & Behavior Changes
iif()lazy evaluationProposed Implementation Plan
FHIRPath.g4and regenerate ANTLR artifacts (Long literal + constructor syntax).Longsupport.fhir-test-casesand update conformance table.Priority Order
coalesce,sort, aggregates (sum/min/max/avg)lowBoundary/highBoundary/precisionrepeatAll/combinedefineVariable,comparable,pathnameAcceptance Criteria