I’ve known about FHIRPath for some time, though I must admit I haven’t paid a lot of attention to it.
Put briefly, FHIRPath is a specification that describes how to identify (and potentially extract) data from a resource using a path based syntax. From the spec:
Of particular importance is the ability to easily and precisely express conditions of basic logic, such as those found in requirements constraints (e.g. Patients must have a name), decision support (e.g. if the patient has diabetes and has not had a recent comprehensive foot exam), cohort definitions (e.g. All male patients aged 60-75), protocol descriptions (e.g. if the specimen has tested positive for the presence of sodium), and numerous other environments.
with these features:
- Graph-traversal: FHIRPath is a graph-traversal language; authors can clearly and concisely express graph traversal on hierarchical information models (e.g. HL7 V3, FHIR, vMR, CIMI, and QDM).
- Fluent: FHIRPath has a syntax based on the Fluent Interface pattern
- Collection-centric: FHIRPath deals with all values as collections, allowing it to easily deal with information models with repeating elements.
- Platform-independent: FHIRPath is a conceptual and logical specification that can be implemented in any platform.
- Model-independent: FHIRPath deals with data as an abstract model, allowing it to be used with any information model.
Read more of this post
Recent Comments