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
identifierwith which it was previously ingested - the
registeredTimestampholding the timestamp of the update
- the same
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 alreadystatus- 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.
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 alreadystatus- 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.
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 alreadystatus- 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.
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 alreadystatus- 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.
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 alreadystatus- 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.
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 |