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.
{
{
},
{
}
],
},
"endpoint": "https://uudev-internal.rochedc.accentureanalytics.com/fhirmsg/rdc/v1.0.0/$process-message"
}
}
},
{
},
{
}
],
],
{
}
]
},
}
}
}
]
}