meal-carbohydrates
Sample scenario:
- Carb 5g associated with a Blood Glucose entry 149 mg/dL (from a glucometer)
- Carb 10g not associated with any Blood Glucose value (manual entry on the smart phone)
FHIR bundle:
Carbs - updated
Note : ("carb-observation" is modelled as "nutritional-value-observation") - Needs update in mySugr.
Sample scenario:
- Carb 5g associated with a Blood Glucose entry 149 mg/dL (from a glucometer)
- Carb 10g not associated with any Blood Glucose value (manual entry on the smart phone)
FHIR bundle:
{
"id": "1318898c-3553-4643-95cd-4f9884ce0b52",
"resourceType": "Bundle",
"type": "message",
"entry": [
{
"resource": {
"id": "id-messageHeader",
"resourceType": "MessageHeader",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/message-header"
]
},
"event": {
"system": "http://roche.com/fhir/rdc/message-type",
"code": "new-bundle",
"display": "New bundle generated"
},
"timestamp": "2020-04-28T11:28:57.962Z",
"source": {
"name": "mySugrApp",
"software": "mySugrBackend",
"version": "x.x",
"endpoint": "https://uudev-internal.rochedc.accentureanalytics.com/fhirmsg/rdc/v1.0.0/$process-message"
},
"extension": [
{
"url": "http://roche.com/fhir/rdc/StructureDefinition/gdpr-controller",
"valueString": "<GDPR controller>"
}
]
}
},
{
"resource": {
"id": "id-device",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/phg-device"
]
},
"resourceType": "Device",
"status": "active",
"type": {
"coding": [
{
"system": "http://roche.com/fhir/rdc/cdf",
"code": "cdf.dev.im",
"display": "Manual interface"
}
]
},
"manufacturer": "mySugr",
"model": "mySugrApp",
"version": "x.x"
}
},
{
"resource": {
"id": "id-deviceComponent-smartPhone",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/phd-devicecomponent"
]
},
"resourceType": "DeviceComponent",
"identifier": {
"system": "http://roche.com/fhir/rdc/sid/device-identifier",
"value": "mySugrApp/712/450274815"
},
"type": {
"coding": [
{
"system": "http://roche.com/fhir/rdc/cs",
"code": "smartPhone",
"display": "Smart Phone"
}
]
},
"source": {
"reference": "Device/id-device"
},
"measurementPrinciple": "manual",
"productionSpecification": [
{
"specType": {
"coding": [
{
"system": "http://hl7.org/fhir/specification-type",
"code": "serial-number",
"display": "Serial Number"
}
]
},
"productionSpec": "450274815"
},
{
"specType": {
"coding": [
{
"system": "http://hl7.org/fhir/specification-type",
"code": "unspecified",
"display": "Unspecified Production Specification"
}
]
},
"productionSpec": "mySugrApp"
},
{
"specType": {
"coding": [
{
"system": "http://hl7.org/fhir/specification-type",
"code": "part-number",
"display": "Part Number"
}
]
},
"productionSpec": "712"
}
],
"lastSystemChange": "2020-04-28T12:00:00.000Z"
}
},
{
"resource": {
"id": "id-deviceMetric-smartPhone-blood-glucose",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/dm-device-metric"
]
},
"resourceType": "DeviceMetric",
"identifier": {
"system": "http://roche.com/fhir/rdc/sid/devicemetric-identifier",
"value": "2339-0"
},
"type": {
"coding": [
{
"system": "http://loinc.org",
"code": "2339-0",
"display": "Glucose [Mass/volume] in Blood"
}
]
},
"unit": {
"coding": [
{
"system": "http://unitsofmeasure.org",
"code": "mg/dL",
"display": "milligram per deciliter"
}
]
},
"source": {
"reference": "Device/id-device"
},
"parent": {
"reference": "DeviceComponent/id-deviceComponent-smartPhone"
},
"operationalStatus": "on",
"category": "measurement"
}
},
{
"resource": {
"id": "id-deviceComponent-glucometer",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/phd-devicecomponent"
]
},
"resourceType": "DeviceComponent",
"identifier": {
"system": "http://roche.com/fhir/rdc/sid/device-identifier",
"value": "mySugrApp/705/450182936"
},
"type": {
"coding": [
{
"system": "http://roche.com/fhir/rdc/cdf",
"code": "cdf.dev.bgmeter",
"display": "Glucometer"
}
]
},
"source": {
"reference": "Device/id-device"
},
"measurementPrinciple": "impedance",
"productionSpecification": [
{
"specType": {
"coding": [
{
"system": "http://hl7.org/fhir/specification-type",
"code": "serial-number",
"display": "Serial Number"
}
]
},
"productionSpec": "450182936"
},
{
"specType": {
"coding": [
{
"system": "http://hl7.org/fhir/specification-type",
"code": "unspecified",
"display": "Unspecified Production Specification"
}
]
},
"productionSpec": "Guide"
},
{
"specType": {
"coding": [
{
"system": "http://hl7.org/fhir/specification-type",
"code": "part-number",
"display": "Part Number"
}
]
},
"productionSpec": "705"
}
],
"lastSystemChange": "2020-04-26T11:00:00Z"
}
},
{
"resource": {
"id": "id-deviceMetric-glucometer-blood-glucose",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/dm-device-metric"
]
},
"resourceType": "DeviceMetric",
"identifier": {
"system": "http://roche.com/fhir/rdc/sid/devicemetric-identifier",
"value": "41653-7"
},
"type": {
"coding": [
{
"system": "http://loinc.org",
"code": "41653-7",
"display": "Glucose [Mass/volume] in Capillary blood by Glucometer"
}
]
},
"unit": {
"coding": [
{
"system": "http://unitsofmeasure.org",
"code": "mg/dL",
"display": "milligram per deciliter"
}
]
},
"source": {
"reference": "Device/id-device"
},
"parent": {
"reference": "DeviceComponent/id-deviceComponent-glucometer"
},
"operationalStatus": "on",
"category": "measurement"
}
},
{
"resource": {
"id": "id-deviceMetric-smartPhone-carb",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/dm-device-metric"
]
},
"resourceType": "DeviceMetric",
"identifier": {
"system": "http://roche.com/fhir/rdc/sid/devicemetric-identifier",
"value": "2331003"
},
"type": {
"coding": [
{
"system": "http://snomed.info/sct",
"code": "2331003",
"display": "Carbohydrate (substance)"
}
]
},
"unit": {
"coding": [
{
"system": "http://unitsofmeasure.org",
"code": "g",
"display": "gram"
}
]
},
"source": {
"reference": "Device/id-device"
},
"parent": {
"reference": "DeviceComponent/id-deviceComponent-smartphone"
},
"operationalStatus": "on",
"category": "measurement"
}
},
{
"resource": {
"resourceType": "Observation",
"id": "id-observation-bg-withcarb",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/bg-observation"
]
},
"identifier": [
{
"system": "http://roche.com/fhir/rdc/sid/observation/mySugr",
"value": "unique-obs-id"
}
],
"status": "final",
"category": [
{
"coding": [
{
"system": "http://roche.com/fhir/rdc/cs",
"code": "clinical-observation",
"display": "Clinical Observation"
}
]
}
],
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "41653-7",
"display": "Glucose [Mass/volume] in Capillary blood by Glucometer"
}
]
},
"subject": {
"reference": "Patient/abcdefghijklmnopqrstuvxyz0123456789ABCDEFGHIJKLMNOPQRSTUVXYZ"
},
"effectiveDateTime": "2020-04-26T10:11:00Z",
"performer": [
{
"reference": "Patient/abcdefghijklmnopqrstuvxyz0123456789ABCDEFGHIJKLMNOPQRSTUVXYZ"
}
],
"valueQuantity": {
"value": 149,
"unit": "mg/dL",
"system": "http://unitsofmeasure.org",
"code": "mg/dL"
},
"device": {
"reference": "DeviceMetric/id-deviceMetric-glucometer-blood-glucose"
},
"related": [
{
"type": "has-member",
"target": {
"reference": "Observation/id-observation-carb-associated-to-bg"
}
}
],
"extension": [
{
"url": "http://roche.com/fhir/rdc/StructureDefinition/registered-timestamp",
"valueDateTime": "2020-04-26T11:00:00Z"
}
]
}
},
{
"resource": {
"resourceType": "Observation",
"id": "id-observation-carb-associated-to-bg",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/nutritional-value-observation"
]
},
"identifier": [
{
"system": "http://roche.com/fhir/rdc/sid/observation/mySugr",
"value": "unique-obs-id"
}
],
"status": "final",
"category": [
{
"coding": [
{
"system": "http://snomed.info/sct",
"code": "84626001",
"display": "Nutritional value, function (observable entity)"
}
]
}
],
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "9060-5",
"display": "Carbohydrate intake Measured"
}
]
},
"subject": {
"reference": "Patient/abcdefghijklmnopqrstuvxyz0123456789ABCDEFGHIJKLMNOPQRSTUVXYZ"
},
"effectiveDateTime": "2020-04-26T10:11:00Z",
"performer": [
{
"reference": "Patient/abcdefghijklmnopqrstuvxyz0123456789ABCDEFGHIJKLMNOPQRSTUVXYZ"
}
],
"valueQuantity": {
"value": 5,
"unit": "g",
"system": "http://unitsofmeasure.org",
"code": "g"
},
"device": {
"reference": "DeviceMetric/id-deviceMetric-smartPhone-carb"
},
"extension": [
{
"url": "http://roche.com/fhir/rdc/StructureDefinition/registered-timestamp",
"valueDateTime": "2020-04-26T11:00:00Z"
}
]
}
},
{
"resource": {
"resourceType": "Observation",
"id": "id-observation-nobg-withcarb",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/bg-observation"
]
},
"identifier": [
{
"system": "http://roche.com/fhir/rdc/sid/observation/mySugr",
"value": "unique-obs-id"
}
],
"status": "final",
"category": [
{
"coding": [
{
"system": "http://roche.com/fhir/rdc/cs",
"code": "clinical-observation",
"display": "Clinical Observation"
}
]
}
],
"code": {
"coding": [
{
"system": "http://snomed.info/sct",
"code": "362943005",
"display": "Manual method (qualifier value)"
}
]
},
"subject": {
"reference": "Patient/abcdefghijklmnopqrstuvxyz0123456789ABCDEFGHIJKLMNOPQRSTUVXYZ"
},
"effectiveDateTime": "2020-04-26T11:11:00Z",
"performer": [
{
"reference": "Patient/abcdefghijklmnopqrstuvxyz0123456789ABCDEFGHIJKLMNOPQRSTUVXYZ"
}
],
"dataAbsentReason": {
"coding": [
{
"system": "http://hl7.org/fhir/data-absent-reason",
"code": "unknown",
"display": "Unknown"
}
]
},
"device": {
"reference": "DeviceMetric/id-deviceMetric-smartPhone-blood-glucose"
},
"related": [
{
"type": "has-member",
"target": {
"reference": "Observation/id-observation-carb-standalone"
}
}
],
"extension": [
{
"url": "http://roche.com/fhir/rdc/StructureDefinition/registered-timestamp",
"valueDateTime": "2020-04-26T12:00:00Z"
}
]
}
},
{
"resource": {
"resourceType": "Observation",
"id": "id-observation-carb-standalone",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/nutritional-value-observation"
]
},
"identifier": [
{
"system": "http://roche.com/fhir/rdc/sid/observation/mySugr",
"value": "unique-obs-id"
}
],
"status": "final",
"category": [
{
"coding": [
{
"system": "http://snomed.info/sct",
"code": "84626001",
"display": "Nutritional value, function (observable entity)"
}
]
}
],
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "9060-5",
"display": "Carbohydrate intake Measured"
}
]
},
"subject": {
"reference": "Patient/abcdefghijklmnopqrstuvxyz0123456789ABCDEFGHIJKLMNOPQRSTUVXYZ"
},
"effectiveDateTime": "2020-04-26T11:11:00Z",
"performer": [
{
"reference": "Patient/abcdefghijklmnopqrstuvxyz0123456789ABCDEFGHIJKLMNOPQRSTUVXYZ"
}
],
"valueQuantity": {
"value": 10,
"unit": "g",
"system": "http://unitsofmeasure.org",
"code": "g"
},
"device": {
"reference": "DeviceMetric/id-deviceMetric-smartPhone-carb"
},
"extension": [
{
"url": "http://roche.com/fhir/rdc/StructureDefinition/registered-timestamp",
"valueDateTime": "2020-04-26T12:00:00Z"
}
]
}
}
]
}
pen_basal_injection_units/pen_bolus_injection_units/drug_type/Insulin pen device properties
Sample scenario:
- Basal (long-acting) Novolin insulin 5 (iU) (manual entry on the smart phone)
- Bolus (short-acting) Novolog insulin 2 (iU) (manual entry on the smart phone)
- Basal (long-acting) Novolin insulin 3 (iU) (entry from Insulin Pen)
NOTE:
- It is assumed that the drugType (name of insulin) will fall under any one of the category basal (long-acting) or bolus (short-acting)
- mySugr shall send the part number if available. If not, they should send the unique number 9000018 for NovoPen. If there are any more devices, they shall let us know so that we can assign the unique number.
FHIR bundle:
tags
The approach to model tags has been revised. Please see Tags - Revised approach
Sample scenario:
- All the following tags associated to one Blood Glucose observation 149 mg/dL (not a realistic case, but covers all use-cases)
| Tag | Code | detail |
|---|---|---|
| AFTER_MEAL | PC | extension - observation-event-timing |
| AFTER_SPORTS | PEXERCISE | extension - observation-event-timing |
| BEDTIME | HS | extension - observation-event-timing |
| BEFORE_MEAL | AC | extension - observation-event-timing |
| BEFORE_SPORTS | AEXERCISE | extension - observation-event-timing |
| BREAKFAST | CM | extension - observation-event-timing |
| DINNER | CV | extension - observation-event-timing |
| HYPER_FEELING | feel-hyper | health-event-observation |
| HYPO_FEELING | feel-hypo | health-event-observation |
| LUNCH | CD | extension - observation-event-timing |
| SICK | Illness | health-event-observation |
| SNACK | snack | extension - observation-event-timing |
| STRESS | stress | health-event-observation |
| FASTING | fasting | health-event-observation Previously the approach was to use Observation.code=41604-0 |
FHIR bundle:
Tags
This approach to handle TAGS is focused on capturing the concept in a generic and de-coupled way. Also, not changing the approach entirely for BG tags since that will impact the current integration with RDCP.
The mySugr TAGs are basically catogorized as follows.
- event-timing (like after-meal, bedtime etc). They basically define the timing of the measurement wrt meals, sports etc.
- diet-intake (like breakfast, lunch etc). These are tags that indicate a meal intake
- health-event (stress, nervous etc..). These are tags that indicate a feeling/health status of the user
- activity (like sports, driving etc.). These are tags that indicate an activity a user performed
- event related to device (like catheter change, needle change). These are events related to a device.
Each TAG can fall under one or more than one category depending on the scenario. For instance, the tag "breakfast" could be a diet-intake when standalone and when accompanied with any measurement it also means an event-timing.
TAGs Data Group 1:
| mySugr Tag | Category | FHIR Modelling when STANDALONE | FHIR Modelling when associated with BG | FHIR Modelling when associated with any other measurement |
|---|---|---|---|---|
| AFTER_MEAL | event-timing | n/a* | extension event-timing on bg-observation | extension event-timing on the relevant resource** |
| AFTER_SPORTS | event-timing | n/a* | extension event-timing on bg-observation | extension event-timing on the relevant resource |
| BEFORE_MEAL | event-timing | n/a* | extension event-timing on bg-observation | extension event-timing on the relevant resource |
| BEFORE_SPORTS | event-timing | n/a* | extension event-timing on bg-observation | extension event-timing on the relevant resource |
| FASTING | health-event | health-event-observation (standalone) | health-event-observation (referenced in the BG Observation) | health-event-observation (standalone) |
| HYPER_FEELING | health-event | health-event-observation (standalone) | health-event-observation (referenced in the BG Observation) | health-event-observation (standalone) |
| HYPO_FEELING | health-event | health-event-observation (standalone) | health-event-observation (referenced in the BG Observation) | health-event-observation (standalone) |
| SICK | health-event | health-event-observation (standalone) | health-event-observation (referenced in the BG Observation) | health-event-observation (standalone) |
| STRESS | health-event | health-event-observation (standalone) | health-event-observation (referenced in the BG Observation) | health-event-observation (standalone) |
| BREAKFAST | diet-intake + event-timing (when accompanied with a measurement) | diet-intake-observation (standalone) | extension event-timing on bg-observation + diet-intake-observation (referenced in the BG Observation) | extension event-timing on the relevant resource + diet-intake-observation (standalone) |
| DINNER | diet-intake + event-timing (when accompanied with a measurement) | diet-intake-observation (standalone) | extension event-timing on bg-observation + diet-intake-observation (referenced in the BG Observation) | extension event-timing on the relevant resource + diet-intake-observation (standalone) |
| LUNCH | diet-intake + event-timing (when accompanied with a measurement) | diet-intake-observation (standalone) | extension event-timing on bg-observation + diet-intake-observation (referenced in the BG Observation) | extension event-timing on the relevant resource + diet-intake-observation (standalone) |
| SNACK | diet-intake + event-timing (when accompanied with a measurement) | diet-intake-observation (standalone) | extension event-timing on bg-observation + diet-intake-observation (referenced in the BG Observation) | extension event-timing on the relevant resource + diet-intake-observation (standalone) |
| BEDTIME | activity + event-timing (when accompanied with a measurement) | activity-observation (standalone) | extension event-timing on bg-observation + activity-observation (referenced in the BG Observation) | extension event-timing on the relevant resource + activity-observation (standalone) |
*MySugr shall not share these tags when standalone as they do not have any meaning when selected without an accompanying measurement. However, if a user edits such a tag and adds a measurement, then that data has to be shared.
**Relevant resources with which TAGs can be associated in data group 0/1 (apart from BG) are
- meal-carbohydrates - carbs-observation
- pen basal and bolus insuling units - medicationAdminitration
Editing and Deleting of tags
- If a tag is unmarked/unselected for a log entry then:
- tags with event-timing category - then the parent resource that holds the extension will be updated. The updated resource will no more have the event-timing extension for that tag. (see the chapter Edited values - Final approach)
- tags with health-event/diet-intake/activity category - since these are modelled as separate resources, in this case the tag resource needs to be cancelled. (see the chapter Deleted values - Final approach)
- If a measurement is added to the log entry which already has tags
- If BG measurement is added:
- tags with event-timing category - Send the BG Observation with the respective event-timing extension
- tags with health-event/diet-intake/activity category - Send the BG observation with references to the respective tag resources
- If any other measurement is added:
- tags with event-timing category - Send the relevant measurement resource with the respective event-timing extension
- tags with health-event/diet-intake/activity category - Send the relevant resource. (No need to reference the related tag observations. The effectiveDateTime will be the same across all the resources in the log entry)
- If BG measurement is added:
- If a measurement is removed from a log entry which already has tags
- Only the relevant measurement resource will be cancelled. (see the chapter Deleted values - Final approach)
NOTE: More details are available in the spike documentation on Confluence- https://confluence.rochedc.accentureanalytics.com/x/X4B-B
Sample Bundles:
airshot
The elements that differentiate a basal/bolus administration from an airshot are as follows:
| Element | pen basal/bolus administration | airshot |
|---|---|---|
| MedicationAdministration.Status | completed | entered-in-error |
| MedicationAdministration.notGiven | (null) | true |
| MedicationAdministration.reasonNotGiven | (null) | prime-insulin-pen |
Therefore, if a user marks/unmarks an insulin entry as "airshot", the above elements have to be updated accordingly for that MedicationAdministration resource (see the chapter Edited values - Final approach for the approach followed to edit resources)
Sample scenario:
The following entries are imported from an insulin pen
- Airshot - Bolus (short-acting) Novolog insulin 1 (iU)
- Actual administration - Bolus (short-acting) Novolog insulin 5 (iU)