fhirpath.dialects package¶
Submodules¶
fhirpath.dialects.base module¶
fhirpath.dialects.elasticsearch module¶
ElasticSearch Dialect
- class fhirpath.dialects.elasticsearch.ElasticSearchDialect(connection=None)[source]¶
Bases:
fhirpath.dialects.base.DialectBase
- static apply_from_constraint(query, body_structure, resource_type, root_replacer=None)[source]¶
We force apply resource type boundary
- static apply_source_filter(query, body_structure, root_replacer=None)[source]¶
https://www.elastic.co/guide/en/elasticsearch/reference/ current/search-request-body.html#request-body-search-source-filtering
- 1.) we are using FHIR field data from ES server directly, unlike collective.
elasticsearch, where only path is retrieve, then using that set zcatalog brain, this patternt might good for general puporse but here we exclusively need fhir resource only which is already stored in ES. Our approach will be definately performance optimized!
- 2.) We might loose minor security (only zope specific),
because here permission is not checking while getting full object.
- compile_for_single_resource_type(query, resource_type, mapping=None, root_replacer=None)[source]¶
- Param
query
- Param
mapping: Elasticsearch mapping for FHIR resources.
- Root_replacer
Path´s root replacer: Could be mapping name or index name in zope´s ZCatalog context
fhirpath.dialects.postgres module¶
RAW PostgresSQL Dialect for FHIRPath Engine