FHIR specify set of Resources with dataelements with specific datatype as informational model - StructureDefinition resource. So we have to convert StructureDefinition into JSON schema.
Also FHIR has specification of REST API by convention - http://hl7.org/fhir/http.html, and ability to extend API by custom Operations - http://hl7.org/fhir/operationslist.html
| MyController = ($scope, $resource)-> | |
| $scope.items = $resource.query() |
| 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
