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
| Active as of 2024-01-31 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="PHRSFMR2-TI.2.1.3"/>
<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>TI.2.1.3#01</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 log system maintenance events for loading new versions of, or changes to, the clinical system.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>TI.2.1.3#02</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 store system maintenance events for loading new versions of codes and knowledge bases.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>TI.2.1.3#03</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 log system maintenance events for creating and restoring of backup.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>TI.2.1.3#04</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 audit events in the case of detection of corrupt or dirty data.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>TI.2.1.3#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 audit the access and usage of systems, data, and organizational resources.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>TI.2.1.3#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 provide the ability to log system events at the hardware and software architecture level.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>TI.2.1.3#07</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 log system maintenance events for entry to, and exit from, the PHR system.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>TI.2.1.3#08</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 log system maintenance events for remote access connections including those for system support and maintenance activities for security and access purposes.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-TI.2.1.3"/>
<version value="0.1.0"/>
<name value="TI_2_1_3_System_Audit_Triggers"/>
<title value="TI.2.1.3 System Audit Triggers (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="System Audit Triggers are designed to capture system related events, both routine and exceptional, including key metadata (who, what, when, where, why)."/>
<statement>
<key value="PHRSFMR2-TI.2.1.3-01"/>
<label value="TI.2.1.3#01"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to log system maintenance events for loading new versions of, or changes to, the clinical system."/>
</statement>
<statement>
<key value="PHRSFMR2-TI.2.1.3-02"/>
<label value="TI.2.1.3#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to store system maintenance events for loading new versions of codes and knowledge bases."/>
</statement>
<statement>
<key value="PHRSFMR2-TI.2.1.3-03"/>
<label value="TI.2.1.3#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to log system maintenance events for creating and restoring of backup."/>
</statement>
<statement>
<key value="PHRSFMR2-TI.2.1.3-04"/>
<label value="TI.2.1.3#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to audit events in the case of detection of corrupt or dirty data."/>
</statement>
<statement>
<key value="PHRSFMR2-TI.2.1.3-05"/>
<label value="TI.2.1.3#05"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to audit the access and usage of systems, data, and organizational resources."/>
</statement>
<statement>
<key value="PHRSFMR2-TI.2.1.3-06"/>
<label value="TI.2.1.3#06"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to log system events at the hardware and software architecture level."/>
</statement>
<statement>
<key value="PHRSFMR2-TI.2.1.3-07"/>
<label value="TI.2.1.3#07"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to log system maintenance events for entry to, and exit from, the PHR system."/>
</statement>
<statement>
<key value="PHRSFMR2-TI.2.1.3-08"/>
<label value="TI.2.1.3#08"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to log system maintenance events for remote access connections including those for system support and maintenance activities for security and access purposes."/>
</statement>
</Requirements>