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.
Command 'json' could not render: File not found for 'subject=example-mysugr-edited-values-observation'