There may occur times when a content creator wishes to obsolete all data in a previously sent clinical document and replace the content with new data or may wish to append an existing document with new data. When this occurs the content consumer is expected to create a replacement relationship between the two documents.
Figure 4 illustrates an example of how a replacement should be performed. The example instructs OpenSHR to replace the contents of document 1.2.3.1.2.3.4.3.234 with the contents in the current document instance.
Figure 4 - Replacing a document
<ClinicalDocument classCode="DOCCLIN" moodCode="EVN" xmlns="urn:hl7-org:v3">
...
<relatedDocument typeCode="RPLC">
<parentDocument classCode="DOCCLIN" moodCode="EVN">
<id root="1.2.3.1.2.3.4.3" extension="234" />
</parentDocument>
</relatedDocument>
...
</ClinicalDocument>
If a document were submitted to OpenSHR with this element, the SHR would attempt to load the specified document identifier, obsolete all data related to that document, and would then store the new data.
Note: This reference can only be used to reference a stable CDA document that was submitted to the OpenSHR instance. The OpenSHR cannot replace or amend an on-demand document or non-CDA document.
Overview
Content Tools