Stream: fhirpath
Topic: narrow the scope of fhirpath
nicola (RIO/SS) (Aug 06 2018 at 18:39):
My opinion, that functions:
- resolve()
- elementDefinition()
- conformsTo()
expand fhirpath scope too much and bring ref impl client into engine :(.
resolve can be implemented after getting result of fhirpath and walking in your runtime thro resulting collection
elementsDefinition means fhirpath knows and contains FHIR metadata
conformsTo means fhirpath includes profile validator
We already discussed to split fhirpath into two parts - so this 3 possibly belong to second one.
As well time algebra :)
nicola (RIO/SS) (Aug 06 2018 at 18:41):
@Bryn Rhodes @Grahame Grieve @Josh Mandel @Ewout Kramer what do you think?
Bryn Rhodes (Aug 06 2018 at 18:47):
Hi @nicola (RIO/SS) , these aspects are all already part of the FHIR-specific extensions for FHIRPath, not the core FHiRPath spec. I don’t know the extent to which these features are used in invariants in FHIR, though, that would definitely be a good thing to clarify.
nicola (RIO/SS) (Aug 06 2018 at 18:48):
:+1:
Grahame Grieve (Aug 06 2018 at 19:05):
we use resolve() heaps.Not so much the others
Last updated: Apr 12 2022 at 19:14 UTC
