HL7 Personal Health Record System Functional Model, Release 2
2.0.1-ballot - Normative Ballot

Publication Build: This will be filled in by the publication tooling

## : RI.1.1.18 Re-activate Record Lifecycle Event (Function) - XML Representation

Page standards status: Informative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-RI.1.1.18"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"/>
      </meta>
      <text>
        <status value="extensions"/>
        <div xmlns="http://www.w3.org/1999/xhtml">
        <span id="description"><b>Statement <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b> <div><p>Re-activate Record Entries (1 or more instances)</p>
    </div></span>

        <span id="purpose"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>Occurs when an agent causes the system to recreate or restore full status to record entries previously deleted or deprecated.</p>
    <p>Reference: ISO 21089-2018, Section 15.18.</p>
    </div></span>

        <span id="actors"><b>Actors:</b><br/> ehr</span>

        <span id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></span>

        <table id="statements" class="grid dict">

            <tr>
                <td style="padding-left: 4px;">

                    <span>RI.1.1.18#01</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>SHALL</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHALL provide the ability to untag Record Entries that were previously tagged as being deleted or deprecated (or tag Record Entries as no longer being deleted that were previously deleted, or as no longer being deprecated that were previously deprecated) and thus reactivate those Record Entries according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url
           value="http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-RI.1.1.18"/>
      <version value="2.0.1-ballot"/>
      <name value="RI_1_1_18_Re_activate_Record_Lifecycle_Event"/>
      <title value="RI.1.1.18 Re-activate Record Lifecycle Event (Function)"/>
      <status value="active"/>
      <date value="2025-04-04T11:42:51+11:00"/>
      <publisher value="EHR WG"/>
      <contact>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org/Special/committees/ehr"/>
        </telecom>
      </contact>
      <description value="Re-activate Record Entries (1 or more instances)"/>
      <purpose
               value="Occurs when an agent causes the system to recreate or restore full status to record entries previously deleted or deprecated.

    Reference: ISO 21089-2018, Section 15.18."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="PHRSFMR2-RI.1.1.18-01"/>
        <label value="RI.1.1.18#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to untag Record Entries that were previously tagged as being deleted or deprecated (or tag Record Entries as no longer being deleted that were previously deleted, or as no longer being deprecated that were previously deprecated) and thus reactivate those Record Entries according to scope of practice, organizational policy, and/or jurisdictional law."/>
      </statement>
    </Requirements>