This specification defines how FHIR canonical resources and packages are:
- Authored (i.e., created and maintained in Implementation Guides (IGs))
- Assembled (Configured) into final systems by users
- Executed (Runtime) to provide functionality
| time ollama run glm-4.7-flash "implement promise funciton in js from scratch" > result.md | |
| ollama run glm-4.7-flash "implement promise funciton in js from scratch" > 0.23s user 0.38s system 1% cpu 49.968 total |
This specification defines how FHIR canonical resources and packages are:
Suggest an algorithm to turn linear structures like this
[ {path: 'a', value: 'k'}, {path: 'b', value: 'l'}, {path: 'b.c', value: 'm'}, {path: 'd', value: 'n')]list of path and value objects into a nested data-structure like this:
{ elements: { a: {value: 'k'}, b: {value: 'l', elements: {c: {value: 'm'}}, d: {value: 'n'}}| grammar fhirpathmini; | |
| path : expr EOF ; | |
| expr : expr AMPERSAND expr # concatexpr | |
| | chain # chainexpr | |
| ; | |
| chain : ( variable | element ) (DOT ( element | funcall | where ) | index)*; | |
| variable : VARIABLE ; |
| grammar fhirpathmin; | |
| expression | |
| : expression '.' expression #chain | |
| | expression '[' int ']' #index | |
| | FIRST #first | |
| | WHERE predicate ')' #where | |
| | element #term | |
| ; |
zd meta model is harmonized with https://www.w3.org/2000/01/rdf-schema zd can work with rdf schema and owl ontologies and export data as rdf
.zd file parsed into a resource - map with :zd.id zd.id is calculated from file path '[paths]/a/b/c.zd' => :zd.id = a.b.c
hardware & os