FQL is a query language that allows you to retrieve, filter and project data from any data source containing FHIR Resources. It brings the power of three existing languages together: SQL, JSON and FhirPath. It allows you to create tables and is useful for gaining insight and perform quality control.
-
Default
What is FQL?
-
FQL Query resources
FQL Playground
Try Firely Query Language in our playground by using this scope as data source.
- FQL Documentation
-
FQL Language
Syntax specification
To learn more about FQL syntax choose this menu item.
-
YamlGen Generate resources
YamlGen Playground
Try YamlGen in our playground by using this scope as data source.
-
YamlGen Language
YamlGen Syntax specification
To learn more about YamlGen syntax choose this.
-
FHIRPath Inspect resource
FHIRPath Playground
Try out the FHIRPath playground and navigate inside this resource.
-
FHIRPath Documentation
FHIRPath Documentation
Find out what FHIRPath is or learn how to write FHIRPath scripts.
-
FHIR
Get this resource using a FHIR client.
-
Embed
Embed this resource in your own website. How?
-
Custom Example generation
Custom Example generation beta
Experiment with resource instance generation using YamlGen and based on this profile.
This feature is in beta. You can help us improve it by giving feedback with the feedback button at the top of the screen.
Observation – Complete Lung Function Testing
Profile for capturing the relative lung function testings (i.e. an individual measurement divided by the corresponding reference value) as FHIR Observation resources.
This profile defines the exchange of a single relative value for the Mandatory Interoperable Value (MIV) "Lung Function Testing" which is technically defined by the ValueSet hddt-miv-lung-function-testing. This MIV is e.g. implemented by peak flow meter that can connect to a Personal Health Gateway (e.g. a mobile app for tracking lung function values) through wireless or wired communication.
Obligations and Conventions:
Each Lung Function Testing MAY either hold a reference to a Sensor Type And Calibration Status DeviceMetric resource or to a Personal Health Device Device resource (eXclusive OR). Typically the reference will be to a Device resource, but the option to reference a DeviceMetric resource is provided for compatibility with the overarching HDDT specification.
Each instance of this Observation MUST reference the Observations holding the corresponding raw measurement and reference value via the derivedFrom element.
Constraints applied:
statusis restricted to finalcodeis constrained to a subset of the MIV Lung Function Relative Values ValueSet, defined by the HddtLungFunctionRelativeValues ValueSet.effective[x]is restricted toeffectiveDateTimeand constrained as mandatory.value[x]is restricted tovalueQuantity. The elementsvalueQuantity.value,valueQuantity.system, andvalueQuantity.codeare constrained in a way that a value MUST be provided and that UCUM MUST be used for encoding the unit of measurement.Observation.valueQuantityMAY only be omitted in case of an error that accured with the measurement. In this case,Observation.dataAbsentReasonMUST be provided.derivedFromis constrained to require exactly two references: one to the raw lung function testing Observation and one to the lung function reference value Observation.
- type Profile on Observation
- FHIR R4
- status Active
-
version1.0.0-rc
This resource matches a canonical claim from this project.
Claim: https://gematik.de/fhir/hddt/