The Mobile access to Health Documents (MHD) Profile defines one standardized interface to health documents for use by mobile devices so that deployment of mobile applications is more consistent and reusable. The transactions defined here leverage the document content- and format-.agnostic metadata
In the Improvements 2022, (version 4.2.0) there is added functionality "replace" support added to be used by a Document Source to better support FHIR backends like MHDS.
in section 2:3.65.4.1.2.3 Replace, Transform, Signs, and Append Associations
...
If a DocumentReference will be replaced, the to be replaced DocumentReference needs to be added and updated to status superseded within the transaction bundle.
When a Document Source is submitting a new DocumentReference that is replacing a previous DocumentReference, this "replace" functionality is used only to modify the previous DocumentReference.status to the superseded state. In this way the Document Source simply provides minimal details on the previous DocumentReference using PATCH to change the .status to superseded. The new DocumentReference would continue to need to properly populate the .relatesTo element.
see example: Bundle-ex-comprehensiveProvideDocumentBundleReplace.html
Note that this "replace" feature has always worked with XDS and XDR; as those solutions did support the server side functionality to mark previous as superseded.
This replace fix is important for MHDS based persistence, as use of this new PATCH mechanism is the normal FHIR RESTful method. Prior to this new replace feature a MHDS Document Registry would have had to had special handling of replace to mark the old DocumentReference as superseded.
Comments are welcome. Both for and against this new support. Any concerns should be brought forward.
In the Improvements 2022, (version 4.2.0) there is added functionality "replace" support added to be used by a Document Source to better support FHIR backends like MHDS.
When a Document Source is submitting a new DocumentReference that is replacing a previous DocumentReference, this "replace" functionality is used only to modify the previous DocumentReference.status to the superseded state. In this way the Document Source simply provides minimal details on the previous DocumentReference using PATCH to change the
.statustosuperseded. The new DocumentReference would continue to need to properly populate the.relatesToelement.see example: Bundle-ex-comprehensiveProvideDocumentBundleReplace.html
Note that this "replace" feature has always worked with XDS and XDR; as those solutions did support the server side functionality to mark previous as superseded.
This replace fix is important for MHDS based persistence, as use of this new PATCH mechanism is the normal FHIR RESTful method. Prior to this new replace feature a MHDS Document Registry would have had to had special handling of replace to mark the old DocumentReference as superseded.
Comments are welcome. Both for and against this new support. Any concerns should be brought forward.