refactor retraction section in imaging report

Author: oijauregui

ig-src/input/pagecontent/imaging-report.md

@@ -156,7 +156,7 @@ This IG adopts the HL7 [FHIR Clinical Document — Succession Management](https:
 
 * **Replacement** — the previously reported content is changed. A *complete* new document (the full report, not only the changes) supersedes the previous one, which is not meant to be read anymore except for audit purposes.
 In this case the new report references the previous one through `Composition.relatesTo` with {%if isR4%}`code = replaces` and the prior `Bundle.identifier` in `targetIdentifier`{%endif%}{%if isR5%}`type = replaces` and the prior `Bundle.identifier` in `resourceReference.identifier`{%endif%}. `DiagnosticReport.status` and `Composition.status` SHALL be aligned for both the new and previous reports as shown below.
-* **Retraction** — the report was issued in error and is withdrawn, for example because it was assigned to the wrong patient or study. y. Following the FHIR Clinical Documents IG, the original report is replaced by an empty `Composition` and empty `DiagnosticReport` (no clinical content, preserving/updating the references) with the value of `Composition.status` and `DiagnosticReport.status` set to `entered-in-error`.
+* **Retraction** — the report was issued in error and is withdrawn, for example because it was assigned to the wrong patient or study. y. Following the FHIR Clinical Documents IG, the original report is replaced by an empty `Composition` and empty `DiagnosticReport` (no clinical content, and a minimal explanatory narrative) with the value of `Composition.status` and `DiagnosticReport.status` set to `entered-in-error`.
 
 Note: The `DiagnosticReport.status` version management model is specific to this specification and is not part of the FHIR Clinical Documents IG.