EDITED values

  • MySugr maintains a unique identifier for ALL the editable resources. NOTE: This identifier is unique for the resource. If a log entry has more than one data point resulting in more than 1 resource, each resource should be identified uniquely.

  • If there is any update on any entry, mySugr shall send the updated resource alone (no history) carrying

    • the same identifier with which it was previously ingested
    • the registeredTimestamp holding the timestamp of the update
  • RDCP shall maintain the history so there will be no need to send the history through ACSPIX

More details at - https://confluence.rochedc.accentureanalytics.com/x/wwb4Aw

This section contains a generalized approach for each resource type. If a particular data point is editable in mySugr, one needs to follow the approach based on the FHIR resource type used for that data point. For instance: meal-carbohydrates, exercise-duration, blood-glucose etc are observation resources and therefore follow the approach given under "Observation resource" category.

Observation resource

The "edit" approach for any observation resource will be the same. So this approach applies for "updation" of any data point that is modelled as an observation resource.

  • effectiveDateTime - will have the timestamp of the measurement/observation made. This will remain the same unless the user updates also the measurement timestamp
  • extension registered-timestamp - will have the timestamp of the update made on the entry
  • device - will be a reference always to the device metric which basically points to the smartphone (assuming editing is only possible on the app)
  • identifier - will have the same unique identifier with which it has been ingested already
  • status - will always be "final" for the updated resource

   

Below is a sample for updating a BG observation with identifier "AAAAA-AAAAA-AAAAA":

   

Step Description BG Value BG Measurement TimeStamp Registered TimeStamp Type Identifier
1 A new blood glucose entry is made 88 2020-04-06T10:00:00Z 2020-04-06T12:00:00Z manual entry AAAAA-AAAAA-AAAAA
2 The entry is updated 90 2020-04-06T10:00:00Z 2020-04-06T13:00:00Z manual entry AAAAA-AAAAA-AAAAA
3 The entry is updated 92 2020-04-06T10:00:00Z 2020-04-06T14:00:00Z manual entry AAAAA-AAAAA-AAAAA

The following bundle is generated on Step 3.

Command 'json' could not render: File not found for 'subject=example-mysugr-edited-values-observation'

MedicationAdministration resource

The "edit" approach for any MedicationAdministration resource will be the same. So this approach applies for "updation" of any data point that is modelled as MedicationAdministration resource.

  • effectiveDateTime - will have the timestamp of the medication administration. This will remain the same unless the user updates also the administration timestamp
  • extension registered-timestamp - will have the timestamp of the update made on the entry
  • extension parent-device-metric - will be a reference always to the device metric which basically points to the smartphone (assuming editing is only possible on the app)
  • identifier - will have the same unique identifier with which it has been ingested already
  • status - will always be "completed" for the updated resource

   

Below is a sample for updating a pen_basal_injection_unit with identifier "BBBBB-BBBBB-BBBBB":

   

Step Description Insulin Units Injected TimeStamp Registered TimeStamp Type Identifier
1 A pen_basal_injection_unit is entered 2 2020-04-06T10:00:00Z 2020-04-06T11:00:00Z manual entry BBBBB-BBBBB-BBBBB
2 The entry is updated 3 2020-04-06T10:00:00Z 2020-04-06T12:00:00Z manual entry BBBBB-BBBBB-BBBBB

The following bundle is generated on Step 2.

Command 'json' could not render: File not found for 'subject=example-mysugr-edited-values-medicationadministration'

Goal resource

The "edit" approach for any goal resource will be the same. So this approach applies for "updation" of any data point that is modelled as goal resource.

  • extension registered-timestamp - will have the timestamp of the update made on the entry
  • identifier - will have the same unique identifier with which it has been ingested already
  • status - will always be "planned" for the updated resource

   

Below is a sample for updating a body weight goal range with identifier "BBBBB-BBBBB-BBBBB":

   

Step Description Weight lower range Weight higher range Registered TimeStamp Type Identifier
1 Target lower and higher range goal values are entered 55 75 2020-06-24T13:00:00Z manual entry BBBBB-BBBBB-BBBBB
2 The entry is updated 50 80 2020-06-24T13:16:00Z manual entry BBBBB-BBBBB-BBBBB

The following bundle is generated on Step 2.

{
"resourceType": "Bundle",
"id": "1318898c-3553-4643-95cd-4f9884ce0b52",
"type": "message",
"entry": [
{
"resourceType": "MessageHeader",
"id": "id-messageHeader",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/message-header"
]
},
{
"url": "http://roche.com/fhir/rdc/StructureDefinition/gdpr-controller",
"valueString": "<GDPR controller>"
}
],
"event": {
"system": "http://roche.com/fhir/rdc/message-type",
"code": "new-bundle",
"display": "New bundle generated"
},
"timestamp": "2020-06-24T13:00:16+00:00",
"source": {
"name": "mySugrApp",
"software": "mySugrBackend",
"version": "x.x",
"endpoint": "https://uudev-internal.rochedc.accentureanalytics.com/fhirmsg/rdc/v1.0.0/$process-message"
}
}
},
{
"resourceType": "Device",
"id": "id-device",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/phg-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"
}
},
{
"resourceType": "DeviceComponent",
"id": "id-deviceComponent-smartPhone",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/phd-devicecomponent"
]
},
"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"
}
]
},
"lastSystemChange": "2020-06-24T13:16:00+00:00",
"source": {
"reference": "Device/id-device"
},
{
"coding": [
{
"system": "http://hl7.org/fhir/specification-type",
"code": "serial-number",
"display": "Serial Number"
}
]
},
"productionSpec": "450274815"
},
{
"coding": [
{
"system": "http://hl7.org/fhir/specification-type",
"code": "unspecified",
"display": "Unspecified Production Specification"
}
]
},
"productionSpec": "mySugrApp"
},
{
"coding": [
{
"system": "http://hl7.org/fhir/specification-type",
"code": "part-number",
"display": "Part Number"
}
]
},
}
]
}
},
{
"resourceType": "Goal",
"id": "id-goal-body-weight",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/goal"
]
},
{
"url": "http://roche.com/fhir/rdc/StructureDefinition/registered-timestamp",
"valueDateTime": "2020-06-24T13:16:00Z"
}
],
{
"system": "http://roche.com/fhir/rdc/sid/goal/mysugr",
"value": "BBBBB-BBBBB-BBBBB"
}
],
"status": "planned",
"coding": [
{
"system": "http://roche.com/fhir/rdc/cs",
"code": "patientTargetRange",
"display": "Patient Target Range"
}
]
},
"subject": {
"reference": "Patient/eec0ef84-a64f-4ad1-bae0-e8f17e57f639"
},
"target": {
"measure": {
"coding": [
{
"system": "http://loinc.org",
"code": "29463-7",
"display": "Body weight"
}
]
},
"low": {
"value": 50,
"unit": "kg",
"system": "http://unitsofmeasure.org",
"code": "kg"
},
"high": {
"value": 80,
"unit": "kg",
"system": "http://unitsofmeasure.org",
"code": "kg"
}
}
}
}
}
]
}

Condition resource

The "edit" approach for any condition resource will be the same. So this approach applies for "updation" of any data point that is modelled as condition resource.

  • extension registered-timestamp - will have the timestamp of the update made on the entry
  • identifier - will have the same unique identifier with which it has been ingested already
  • status - will always be "active" for the updated resource

   

Below is a sample for updating bg diabetes type with identifier "BBBBB-BBBBB-BBBBB":

   

Step Description BG diabetes type Registered TimeStamp Type Identifier
1 Bg diabetes type value is entered Diabetes mellitus type 1 2020-06-24T13:00:00Z manual entry BBBBB-BBBBB-BBBBB
2 The entry is updated Diabetes mellitus type 2 2020-06-24T13:16:00Z manual entry BBBBB-BBBBB-BBBBB

The following bundle is generated on Step 2.

{
"resourceType": "Bundle",
"id": "1318898c-3553-4643-95cd-4f9884ce0b52",
"type": "message",
"entry": [
{
"resourceType": "MessageHeader",
"id": "id-messageHeader",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/message-header"
]
},
{
"url": "http://roche.com/fhir/rdc/StructureDefinition/gdpr-controller",
"valueString": "<GDPR controller>"
}
],
"event": {
"system": "http://roche.com/fhir/rdc/message-type",
"code": "new-bundle",
"display": "New bundle generated"
},
"timestamp": "2020-06-24T13:00:16+00:00",
"source": {
"name": "mySugrApp",
"software": "mySugrBackend",
"version": "x.x",
"endpoint": "https://uudev-internal.rochedc.accentureanalytics.com/fhirmsg/rdc/v1.0.0/$process-message"
}
}
},
{
"resourceType": "Condition",
"id": "id-bg-diabetes-type",
"meta": {
"profile": [
"http://roche.com/fhir/rdc/StructureDefinition/condition"
]
},
{
"url": "http://roche.com/fhir/rdc/StructureDefinition/registered-timestamp",
"valueDateTime": "2020-06-24T13:16:00Z"
}
],
{
"system": "http://roche.com/fhir/rdc/sid/condition/mysugr",
"value": "BBBBB-BBBBB-BBBBB"
}
],
"clinicalStatus": "active",
"code": {
"coding": [
{
"system": "http://snomed.info/sct",
"code": "44054006",
"display": "Diabetes mellitus type 2 (disorder)"
}
]
},
"subject": {
"reference": "Patient/14435e70-25d8-4db4-8941-9a191735b31e"
}
}
}
]
}

CarePlan resource

The "edit" approach for any CarePlan resource will be the same. So this approach applies for "updation" of any data point that is modelled as a CarePlan resource.

  • extension registered-timestamp - will have the timestamp of the update made on the entry
  • identifier - will have the same unique identifier with which it has been ingested already
  • status - will always be "active" for the updated resource

   

Below is a sample for updating the careplan-therapy-insulin-type in the careplan with identifier "BBBBB-BBBBB-BBBBB":

   

Step Description careplan-therapy-insulin-type Registered TimeStamp Identifier
1 CarePlan for a user is ingested holding his/her therapy settings Novolog 2020-04-24T10:00:00Z BBBBB-BBBBB-BBBBB
2 The setting careplan-therapy-insulin-type is updated to add another insulin to the list Novolog; Abasaglar 2020-06-24T13:00:00Z BBBBB-BBBBB-BBBBB

The following bundle is generated on Step 2.

Command 'json' could not render: File not found for 'subject=example-mysugr-DG3-careplan-edited'

MedicationRequest resource

The "edit" approach for any MedicationRequest resource will be the same. So this approach applies for "updation" of any data point that is modelled as MedicationRequest resource.

  • authoredOn - will have the timestamp of the medication request.
  • extension registered-timestamp - will have the timestamp of the update made on the entry
  • extension parent-device-metric - will be a reference always to the device metric which basically points to the smartphone (assuming editing is only possible on the app)
  • identifier - will have the same unique identifier with which it has been ingested already
  • Important - In RDCP ACSPIX format, the ADVISED_BOLUS object that holds the information from the MedicationRequest resource is a child of the BG tag. So if there is any change to the MedicationRequest resource, even the associated BG and/or CARB observations have to be sent with their respective identifiers.

   

Below is a sample for updating a medication request resource with identifier BBBB

   

Step Time Bolus ID Bolus delivery type Bolus Activation type Selected total bolus Recommended bolus Confirmed bolus BG/Carb used for Bolus calculation
1 At 2020-12-28T09:20:00Z BBBB PUMP_STANDARD Recommended bolus 5 IU
meal - 2IU
correction - 3 IU
5 IU
meal - 2IU
correction - 3 IU
5 IU
meal - 2IU
correction - 3 IU
BG - 170 mg/dL
Carb - 10g
2 At 2020-12-28T10:20:00Z BBBB PUMP_STANDARD Manual bolus 5 IU
meal - 2.5 IU
correction - 2.5 IU
5 IU
meal - 2IU
correction - 3 IU
5 IU
meal - 2IU
correction - 3 IU
BG - 170 mg/dL
Carb - 10g

The following bundle is generated on Step 2.

Command 'json' could not render: File not found for 'subject=example-mySugr-edited-values-medicationrequest-resource'