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'