Personal Health Record System Functional Model, Release 2
0.1.0 - CI Build

Personal Health Record System Functional Model, Release 2 - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## : RI.1.1.4 Attest Record Lifecycle Event (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-RI.1.1.4"/>
      <meta>
        <profile value="http://hl7.org/ehrs/StructureDefinition/FMFunction"/>
      </meta>
      <text>
        <status value="extensions"/>
        <div xmlns="http://www.w3.org/1999/xhtml">
        <table id="statements" class="grid dict">

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

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

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL conform to function [[TI.1.1]] (Entity Authentication).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#02</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL conform to function [[TI.1.2]] (Entity Authorization).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#03</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL provide the ability to attest (approve and apply signature to) Record Entry content by the author.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#04</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL capture the signature event (e.g., digital signature) of the Attesting Author, binding signature to Record Entry content.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#05</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL provide the ability to maintain any attestable Record Entry content added or changed with the content's author</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#06</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL present the status of attestable Record Entry content which has not been attested, conforming to function [[RI.1.3.1]] (Record Pending State).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#07</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>IF the attester is different than the author(s), THEN the system SHALL provide the ability to maintain Record Entry content by properly authenticated and authorized users different from the author (e.g., counter-signature) according to scope of practice, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#08</span>

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

                    <span>SHOULD</span>

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

                    <span><div><p>The system SHOULD provide the ability to manage digital signatures as the means for attestation.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#09</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>IF more than one author contributed to the Record Entry content, THEN the system SHALL provide the ability to maintain all authors/contributors associated with their content.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#10</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>IF Record Entry content is attested by someone other than the author, THEN the system SHALL maintain and display the author(s) and attester.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#11</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL provide the ability to present a minimum set of information that identifies the author of Record Entry content according to scope of practice, organizational policy, and/or jurisdictional law (e.g., name, credential, and/or role (such as Karen Smith, RN)).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#12</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL capture the signature type of the entity (individual, PHR or other system, or organization) sending Record Entry content.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#13</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL capture the signature type of the entity (individual, PHR or other system, or organization) receiving Record Entry content.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>RI.1.1.4#14</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL capture all signature types of the entities through which Record Entry content has passed.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-RI.1.1.4"/>
      <version value="0.1.0"/>
      <name value="RI_1_1_4_Attest_Record_Lifecycle_Event"/>
      <title value="RI.1.1.4 Attest Record Lifecycle Event (Function)"/>
      <status value="active"/>
      <date value="2024-01-31T14:45:34+00:00"/>
      <publisher value="EHR WG"/>
      <contact>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org/Special/committees/ehr"/>
        </telecom>
      </contact>
      <description
                   value="Occurs when an agent causes the system to capture the agent's digital signature (or equivalent indication) during formal validation of record entry content.

    Reference: ISO 21089-2018, Section 15.4."/>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-01"/>
        <label value="RI.1.1.4#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL conform to function [[TI.1.1]] (Entity Authentication)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-02"/>
        <label value="RI.1.1.4#02"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL conform to function [[TI.1.2]] (Entity Authorization)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-03"/>
        <label value="RI.1.1.4#03"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to attest (approve and apply signature to) Record Entry content by the author."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-04"/>
        <label value="RI.1.1.4#04"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL capture the signature event (e.g., digital signature) of the Attesting Author, binding signature to Record Entry content."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-05"/>
        <label value="RI.1.1.4#05"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to maintain any attestable Record Entry content added or changed with the content's author"/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-06"/>
        <label value="RI.1.1.4#06"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL present the status of attestable Record Entry content which has not been attested, conforming to function [[RI.1.3.1]] (Record Pending State)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-07"/>
        <label value="RI.1.1.4#07"/>
        <conformance value="SHALL"/>
        <conditionality value="true"/>
        <requirement
                     value="IF the attester is different than the author(s), THEN the system SHALL provide the ability to maintain Record Entry content by properly authenticated and authorized users different from the author (e.g., counter-signature) according to scope of practice, organizational policy, and/or jurisdictional law."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-08"/>
        <label value="RI.1.1.4#08"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage digital signatures as the means for attestation."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-09"/>
        <label value="RI.1.1.4#09"/>
        <conformance value="SHALL"/>
        <conditionality value="true"/>
        <requirement
                     value="IF more than one author contributed to the Record Entry content, THEN the system SHALL provide the ability to maintain all authors/contributors associated with their content."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-10"/>
        <label value="RI.1.1.4#10"/>
        <conformance value="SHALL"/>
        <conditionality value="true"/>
        <requirement
                     value="IF Record Entry content is attested by someone other than the author, THEN the system SHALL maintain and display the author(s) and attester."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-11"/>
        <label value="RI.1.1.4#11"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to present a minimum set of information that identifies the author of Record Entry content according to scope of practice, organizational policy, and/or jurisdictional law (e.g., name, credential, and/or role (such as Karen Smith, RN))."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-12"/>
        <label value="RI.1.1.4#12"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL capture the signature type of the entity (individual, PHR or other system, or organization) sending Record Entry content."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-13"/>
        <label value="RI.1.1.4#13"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL capture the signature type of the entity (individual, PHR or other system, or organization) receiving Record Entry content."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-RI.1.1.4-14"/>
        <label value="RI.1.1.4#14"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL capture all signature types of the entities through which Record Entry content has passed."/>
      </statement>
    </Requirements>