BGM data

BGM data - Automatic - mg/dL

Sample scenario

Name of the field Value FHIR element Detail
Entry mechanism (datasource) 3 - Automatic - Accu-Chek Guide DeviceComponent resource for the Glucometer + DeviceMetric resource that references the DeviceComponent
- DeviceComponent is linked to the observation resource through the DeviceMetric resource
- DeviceComponent.productionSpecification for specType = "unspecified" will hold the name/model of the Glucometer
- The field is set based on the source
       - 2 - Automatic - Unspecified Glucose Meter --> "Unspecfied"
      - 3 - Automatic - Accu-Chek Guide --> "Guide"
      - 4 - Automatic - Accu-Chek Mobile --> "Mobile"
      - 5 - Automatic - Accu-Chek Instant --> "Instant"
- The part-number and serial-number should be sent if available. These help identifying a device uniquely
- DeviceMetric defines the measurement unit (mg/dL) of the Device and is necesasry for the link between the Observation and DeviceComponent resource
Timestamp 2020-10-14T02:00:00.000+00:00 Observation.effectiveDateTime observation.code = clinical-observation; observation.category = 41653-7 (code for entry from Glucometer)
bg Value 102 mg/dL Observation.valueQuantity observation.code = clinical-observation; observation.category = 41653-7 (code for entry from Glucometer)

Command 'json' could not render: File not found for 'subject=example-smartlife-BG-glucometer'

BGM data - Manual - mg/dL

Sample scenario

Name of the field Value FHIR element Detail
Entry mechanism (datasource) 1 - Manual Entry DeviceComponent resource for the SmartPhone + DeviceMetric resource that references the DeviceComponent
- DeviceComponent is linked to the observation resource through the DeviceMetric resource
- DeviceComponent.productionSpecification for specType = "unspecified" will hold the input source which is "SmartLifeApp" in this case.
- The part-number and serial-number should be sent if available. These help identifying a device uniquely
- DeviceMetric defines the measurement unit (mg/dL) of the Device and is necesasry for the link between the Observation and DeviceComponent resource
Timestamp 2020-10-14T01:00:00.000+00:00 Observation.effectiveDateTime observation.code = clinical-observation; observation.category = 362943005 (code for manual entry)
bg Value 149 mg/dL Observation.valueQuantity observation.code = clinical-observation; observation.category = 362943005 (code for manual entry)

Command 'json' could not render: File not found for 'subject=example-smartlife-BG-manual-mgdl'

BGM data - out of range

Sample scenario 1

Name of the field Value FHIR element Detail
Entry mechanism (datasource) 3 - Automatic - Accu-Chek Guide DeviceComponent resource for the Glucometer + DeviceMetric resource that references the DeviceComponent
Timestamp 2020-10-14T02:00:00.000+00:00 Observation.effectiveDateTime observation.code = clinical-observation; observation.category = 41653-7 (code for entry from Glucometer)
bg Value 2 mg/dL Result is not filled in the Observation as it is invalid
Out of measurement range indicator 1 - LO value Observation.dataAbsentReason = "NINF"

Sample scenario 2

Name of the field Value FHIR element Detail
Entry mechanism (datasource) 3 - Automatic - Accu-Chek Guide DeviceComponent resource for the Glucometer + DeviceMetric resource that references the DeviceComponent
Timestamp 2020-10-14T01:00:00.000+00:00 Observation.effectiveDateTime observation.code = clinical-observation; observation.category = 41653-7 (code for entry from Glucometer)
bg Value 999 mg/dL Result is not filled in the Observation as it is invalid
Out of measurement range indicator 2 - HI value Observation.dataAbsentReason = "PINF"

Command 'json' could not render: File not found for 'subject=example-smartlife-BG-out-of-range'