Difference between revisions of "Restricted Metadata Update (RMU)"
(→Specification: removed the "c" after reference to Volume 2) |
|||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
== Summary == | == Summary == | ||
| − | The Restricted Metadata Update (RMU) Profile provides | + | The Restricted Metadata Update (RMU) Profile provides a mechanism for changing Document Sharing metadata both within and across community boundaries in a controlled manner. |
| − | |||
| − | |||
| + | == Benefits == | ||
| + | RMU enables modification of a restricted set of Document Sharing metadata attributes to allow for predictable and safe use in a wide range of operating environments. Communities can use this Profile as part of meeting legislative requirements for patient control of their distributed medical information | ||
== Details == | == Details == | ||
| − | + | The Restricted Metadata Update (RMU) Profile provides a mechanism for updating Document Sharing metadata both within and across community boundaries in a controlled manner. By restricting which structural metadata attributes can be changed, this Profile can be applied in situations where legislation grants patients control of their medical information. | |
| − | + | ||
| + | This Profile can be combined with other IHE profiles, such as XCA and XDS, to build patient longitudinal records that can be maintained both within and across medical communities and national borders. | ||
| + | |||
| + | The Profile maintains the stewardship of the patient record in the community where patient record was stored. When patient records are shared across communities, it is expected that the record will contain the patient identifier and coding system values from the community where the record originated. | ||
| + | |||
| + | The Profile expects that the latest version of the stored DocumentEntry metadata object(s) will be used as the basis for the update submission. | ||
| + | |||
| + | In order to maintain interoperability among participating communities, certain metadata attributes are restricted from modification as they describe the current state of DocumentEntry object, or the stored physical document. | ||
==Actors & Transactions== | ==Actors & Transactions== | ||
| Line 24: | Line 31: | ||
'''Documents:''' | '''Documents:''' | ||
| − | [ | + | [https://www.ihe.net/uploadedFiles/Documents/ITI/IHE_ITI_Suppl_RMU.pdf RMU supplement] |
'''Affected Sections''' | '''Affected Sections''' | ||
:* Vol. 1 - Section 48 | :* Vol. 1 - Section 48 | ||
| − | :* Vol. | + | :* Vol. 2 - Sections 3.92 |
:* Vol. 3 - Section 4.2 | :* Vol. 3 - Section 4.2 | ||
| Line 37: | Line 44: | ||
==Implementation Material== | ==Implementation Material== | ||
| − | :*[ | + | :*[https://drive.google.com/drive/folders/1jJAlsQOxkhnwRffOdYNYegwF4ubKghCC?usp=sharing/ WSDL] |
| − | + | ||
Revision as of 17:56, 22 June 2021
Summary
The Restricted Metadata Update (RMU) Profile provides a mechanism for changing Document Sharing metadata both within and across community boundaries in a controlled manner.
Benefits
RMU enables modification of a restricted set of Document Sharing metadata attributes to allow for predictable and safe use in a wide range of operating environments. Communities can use this Profile as part of meeting legislative requirements for patient control of their distributed medical information
Details
The Restricted Metadata Update (RMU) Profile provides a mechanism for updating Document Sharing metadata both within and across community boundaries in a controlled manner. By restricting which structural metadata attributes can be changed, this Profile can be applied in situations where legislation grants patients control of their medical information.
This Profile can be combined with other IHE profiles, such as XCA and XDS, to build patient longitudinal records that can be maintained both within and across medical communities and national borders.
The Profile maintains the stewardship of the patient record in the community where patient record was stored. When patient records are shared across communities, it is expected that the record will contain the patient identifier and coding system values from the community where the record originated.
The Profile expects that the latest version of the stored DocumentEntry metadata object(s) will be used as the basis for the update submission.
In order to maintain interoperability among participating communities, certain metadata attributes are restricted from modification as they describe the current state of DocumentEntry object, or the stored physical document.
Actors & Transactions
Actors involved in this profile are:
- Update Initiator
- Update Responder
Specification
Profile Status: Trial Implementation
Documents: RMU supplement
Affected Sections
- Vol. 1 - Section 48
- Vol. 2 - Sections 3.92
- Vol. 3 - Section 4.2
Underlying Standards: