First milestone STU release of FHIRPath since normative publication, containing implementer feedback and additional functions and capabilities, as well as clarifications and corrections throughout. Additions have been clearly marked as STU.
descmd
First milestone STU release of FHIRPath since normative publication, containing implementer feedback and additional functions and capabilities, as well as clarifications and corrections throughout. Additions have been clearly marked as STU.
The resource CodeSystem/calendar-units must have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
ImplementationGuide/hl7.fhirpath: ImplementationGuide: Validated against fhir.ImplementationGuide
Path
Severity
Message
Validating
Resource
information
The resource ImplementationGuide/hl7.fhirpath could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource ValueSet/calendar-units must have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The TSMG has approved this code system as an exemption from moving to THO on 7th May 2026. This code system is appropriately defined in the FHIRPath specification as it is similar to a required code binding in FHIR. https://confluence.hl7.org/spaces/TSMG/pages/453915259/2026-05-07+TSMG+Agenda+and+Minutes
INFORMATION: CodeSystem/calendar-units: CodeSystem: Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG) (1 uses)
This specification pre-dates the conformance clause marking functionality, it may be added in a future publication
INFORMATION: en/index.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'This specification uses the conformance verbs SHALL, MUST, SHOULD, and MAY as defined in RFC 2119. Unlike RFC 2119, however, this specification allows that different applications might not be able to interoperate because of how they use optional features. In particular:' (1 uses)