Observation Calibration
Sample scenario
| Name of the field | Value | FHIR element | Detail |
|---|---|---|---|
| data → calibration → timestamp | 2019-02-13T10:12:00+02:00 | Observation.effectiveDateTime | observation.code = C69187; observation.category = C105585 (code for Glucose Measurement) |
| data → calibration → bg value | 192 mg/dL | Observation.valueQuantity | observation.code = C69187; observation.category = C105585 (code for Glucose Measurement) |
| data → calibration → source device | 0 - Manual Entry via smartphone app | DeviceComponent resource for the SmartPhone + DeviceMetric resource that references the DeviceComponent |
- DeviceComponent is linked to the observation resource through the DeviceMetric resource - DeviceComponent will hold the input source which is "SinovoApp" in this case. - The part-number and serial-number should be sent if available. These help identifying a device uniquely - DeviceMetricn defines the measurement unit (mg/dL) of the Device and is necesasry for the link between the Observation and DeviceComponent resource |
| data → calibration → runtime | 102 min | Observation.extension:time-offset | observation.code = C0006751; observation.category = C105585 (code for Glucose Measurement) |
| data → calibration → action | accepted | Observation.extension:calibration-action | observation.code = C0006751; observation.category = C105585 (code for Glucose Measurement) |
Important Note for Implementers:
please consider the source for mapping the device component, for more details refer the Roche JSON schema (https://confluence.rochedc.accentureanalytics.com/x/WglsBQ)
Sample Bundle
Command 'json' could not render: File not found for 'subject=example-sinovo-calibration'