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.
Bundle – HDDT CGM Summary Report
This profile defines the exchange of aggregated measurement data for the Mandatory Interoperable Value (MIV) "Continuous Glucose Measurement". By this it provides a patient's glucose profile for a defined period. The MIV "Continuous Glucose Measurement" 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 aggregated glucose profile data with DiGA, too.
This profile constrains the FHIR Bundle resource for use as the result container of the $hddt-cgm-summary operation.
The operation requests a patient's glucose profile. The glucose profile is calculated form continuous glucose measurement data
and consists of the machine-readable parts of the HL7 CGM summary profile.
The Bundle is of type collection and MUST contain only resources of the following types:
Observations conforming to HL7 CGM profiles:
Device resources conforming to
HddtPersonalHealthDeviceto provide context about the actual Personal Health Device device used.
The purpose of this Bundle profile is to provide a consistent structure for server responses when clients query for CGM data with aggregation logic.
It ensures interoperability across different implementations by defining a predictable response format.
This supports use cases such as:
- Retrieval of CGM summary metrics over a given time interval in support for the upcoming digital disease management program (dDMP) on Diabetes, e.g. for
- continuous therapy monitoring and adjustment
- forwarding key data to treating physicians, e.g. for clinical decision support
- supporting asynchonous telemonitoring by ad hoc provisioning of condensed status information
- Combining aggregated measurement data and device metadata for downstream applications such as visualization or compliance monitoring
Constraints applied:
Bundle.typeis fixed tocollection.Bundle.entry.resourceis restricted to CGM Observation profiles andHddtPersonalHealthDevice. No other resource types are allowed in the Bundle.Bundle.entryis set as mandatory. A requests for a CGM summary that would result in an empty bundle, MUST give an OperationOutcome with an error or warning message as its response. Therefore there is no scenario where an empty bundle would be shared with a DiGA.
- type Profile on Bundle
- FHIR R4
- status Draft
-
version...
This resource matches a canonical claim from this project.
Claim: https://gematik.de/fhir/hddt/