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 – Continuous Glucose Measurement
Profile for capturing continuous glucose measurements from real-time monitoring devices (esp. rtCGM).
This profile defines the exchange of raw measurement data for the Mandatory Interoperable Value (MIV) "Continuous Glucose Measurement" which is technically defined by the ValueSet hddt-miv-continuous-glucose-measurement. This MIV is e.g. implemented by real-time Continuous Glocose Monitoring devices (rtCGM) and Automated Insulin Delivery systems (AID) that control an insulin pump from rtCGM data. Future non-invasive measuring methods will expectedly be linked with this MIV and therefore use this profile for sharing data with DiGA, too.
Obligations and Conventions:
Devices for continuously measuring glucose values may produce data with a sample rate of more than 1000 values per day (e.g. current
rtCGM provide measures for glucose in interstitial fluid with up to one value per minute). For sharing such data efficently, this profile
makes use of the FHIR sampledData data type. Sampled data is portioned into
chunks of a fixed size (for an exception see below), with the chunk size being set by the resource server (e.g. such that 24 h of measurements fit into a single chunk). If a DiGA
requests data for a period where the end time is earlier that the expected end time of the current chunk, the resource server only fills up the chunk
up to the requested end time and sets the Observation.status to incomplete while Observation.effectivePeriod captures the
full period of the chunk (see section "Retrieving Data" in the HDDT specification for details on chunks and missing data).
Each Continuous Glucose Measurement MUST either hold a reference to a Sensor Type And Calibration Status DeviceMetric resource or to a
Personal Health Device Device resource (eXclusive OR). A reference to Sensor Type And Calibration Status MUST be provided
from the Observation resource if the sensor for continuous measuring needs to be calibrated (either automatically or by the user)
or if the sensor may change its calibration status over time. A change in DeviceMetric.calibration.state or a change of Device.status to inactive finalizes the
current chunk and therefore is the only reason why a chunk may be smaller than the defined fixed size.
Constraints applied:
codeis constrained to the ValueSet that represents the MIV Continuous Glucose Measurementeffective[x]is restricted toeffectivePeriodand constrained as mandatory. Both a starting time and an end tme MUST be given.value[x]is restricted to valueSampledData. The elementsvalueSampledData.origin.unit,valueSampledData.origin.system, andvalueSampledData.origin.codeare mandatory.valueSampledData.origin.systemis restricted to UCUM.Observation.valueSampledDataMAY only be omitted in case of an error that accured with the measurement. In this case,Observation.dataAbsentReasonMUST be provided.deviceis set to be mandatory in order to provide the DiGA with information about the sensor's calibration status and with information about the static and dynamic attributes of the Personal Health Device.
- type Profile on Observation
- FHIR R4
- status Draft
-
version...
This resource matches a canonical claim from this project.
Claim: https://gematik.de/fhir/hddt/