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

## Requirements: RI.1.1.16.1 Evidence of Record Entry Destruction Event (Function)

Page standards status: Informative

Statement N:

Maintain Evidence of Record Entry Destruction Event

Description I:

Evidence of Record Entry Destruction Event includes key metadata, ensures health record integrity (and trust) and enables record audit.

Actors:
ehr Criteria N:

RI.1.1.16.1#01 | dependent SHALL | The system SHALL audit each occurrence when Record Entry content is destroyed according to scope of practice, organizational policy, and/or jurisdictional law.
RI.1.1.16.1#02 | SHALL | The system SHALL capture identity of the organization where Record Entry content is destroyed.
RI.1.1.16.1#03 | SHALL | The system SHALL capture identity of the patient who is subject of destroyed Record Entry content.
RI.1.1.16.1#04 | SHALL | The system SHALL capture a destruction identifier for destroyed Record Entry content (e.g., nursing home inpatient stay from 3/15/2000 thru 6/10/2000).
RI.1.1.16.1#05 | SHALL | The system SHALL capture identity of the user destroying Record Entry content.
RI.1.1.16.1#06 | SHALL | The system SHALL capture identity of the system application which destroyed Record Entry content.
RI.1.1.16.1#07 | SHALL | The system SHALL capture the type of Record Event trigger (i.e., destroy).
RI.1.1.16.1#08 | SHALL | The system SHALL capture the date and time Record Entry content is destroyed.
RI.1.1.16.1#09 | SHOULD | The system SHOULD capture identity of the location (i.e., network address) where Record Entry content is destroyed.
RI.1.1.16.1#10 | MAY | The system MAY capture the rationale for destroying Record Entry content.
RI.1.1.16.1#11 | MAY | The system MAY capture the data, document or other identifier for destroyed Record Entry content.
RI.1.1.16.1#12 | MAY | The system MAY capture data elements for Record Entry content de-identified.