MDTIG - Local Development build (v0.8.1). See the Directory of published versions

Reporting

Reporting

This is a DRAFT FHIR Implementation Guide. This version is not final yet. DO NOT USE, except for trial and test.

Measurements are commonly exchanged in a few patterns:

1. directly querying or retrieving individual measurements;
2. getting statistical values, such as an average, over base measurements;
3. grouping related measurements in a ‘panel’;
4. retrieving a report of related measurements.

The first one is basic FHIR search and create. The other 3 are described on this page.

Statistics

One aspect of reporting are statistical values, such as a Patient’s average glucose level over a certain period.

For statistical values, we follow the approach in LOINC, where specific codes for average values are used.

97507-8 (Average glucose [Mass/volume] in Interstitial fluid during Reporting Period)

The code directly denotes a statistical observation, over a flexible period. The period is specified in Observation.effectivePeriod.

A fragment showing this in pseudocode (in this case an average sensor glucose for 2 weeks):

Observation:
* code.coding: http://example.medtronic.com#200001 "Average SG"
* code.coding: http://loinc.org#97507-8 (Average glucose [Mass/volume] in Interstitial fluid during Reporting Period)
* effectivePeriod.start: "2021-11-12T00:00:00+01:00"
* effectivePeriod.end: "2021-11-26T00:00:00+01:00"

The Medtronic code is always provided. In cases where there is no appropriate LOINC code, only the Medtronic code is provided.

(Also see the entire example in the Artifacts section.)

Panels

Common sets of Observations belonging together are collected in Panels. This is a common approach in LOINC, where combinations such as Insulin delivery device panel are coded with a code for the entire panel, as well as codes for the members of the panel.

Medtronic also combines Observations commonly requested together in Panels. A Panel is itself an Observation, and the member Observation are listed as ‘hasMember’ children within that Observation. A shortened example:

Observation:
* code.coding: MED#200015 "Diabetes MVP Panel"
* effectivePeriod.start: "2021-11-17T00:00:00+01:00"
* effectivePeriod.end: "2021-11-17T23:59:00+01:00"
* hasMember = Reference(urn:uuid:7965af3d-8b9c-489a-ac13-61920b6d5665) //sensor-glucose-component2wk
* hasMember = Reference(urn:uuid:b1b50b8c-018a-4b32-b991-947630084d8c) // sensor-glucose-std-dev2wk
* hasMember = Reference(urn:uuid:95ecf853-637d-4339-8b51-884713d2d50c) // a1c-level-value2wk
* hasMember = Reference(urn:uuid:ca240415-98af-4052-9817-dac6854b8574) // time-in-range-observation2wks
etc.

The ‘hasMember’ Observations are referenced. When retrieving the panel, the referenced member Observations are included in the response with the FHIR Bundle.

(Also see the entire example in the Artifacts section.)