Expand description
The shared foundation of the FerroBRIDGE mapping languages.
FHIRconnect and OMOCL are two languages over one header. The FHIRconnect
header page states that the header “is standardized for both FHIRconnect
and OMOCL”
(docs/specs/fhirconnect/modules/ROOT/pages/basics/main.adoc, §Header), so
this crate models the header once, loads either language’s YAML into a
positioned value tree, indexes the loaded set by mapping name and by
archetype id, and carries one diagnostic type for every refusal. It also
carries the openEHR path model the two languages share, including the
../ parent step they add to the openEHR path grammar.
Nothing here interprets a mapping. The FHIRconnect and OMOCL crates read the positioned tree this crate returns and apply their own grammar to it.
openEHR is a registered trademark of the openEHR Foundation.
Modules§
- composition
- Composition build and read, behind one path and value seam.
- diagnostic
- The one diagnostic every refusal renders into.
- header
- The header both mapping languages share.
- index
- The
aqlPathindex over a built Web Template. - loader
- The YAML loader: one file in, a header and a positioned value tree out.
- party
- The build of a canonical demographic
PARTYfrom node values. - path
- The openEHR path model the two mapping languages share.
- position
- Source positions, and values paired with the position they were read from.
- registry
- The registry of loaded mapping files.
- schema
- The bridge between a positioned value tree and a JSON Schema validator.
- template
- The template a path resolves against, in either generation.
- value
- The positioned YAML value tree a mapping file loads into.