ISO/PRF 27789
(Main)Health informatics — Audit trails for electronic health records
- Abstract
This document specifies a common framework for audit trails for electronic health records (EHR), in terms of audit trigger events and audit data, to keep the complete set of personal health information auditable across information systems and domains. It is applicable to systems processing personal health information that create a secure audit record each time a user reads, creates, updates, or archives personal health information via the system. NOTE Such audit records at a minimum uniquely identify the user, uniquely identify the subject of care, identify the function performed by the user (record creation, read, update, etc.), and record the date and time at which the function was performed. This document covers only actions performed on the EHR, which are governed by the access policy for the domain where the electronic health record resides. It does not deal with any personal health information from the electronic health record, other than identifiers, the audit record only containing links to EHR segments as defined by the governing access policy. It does not cover the specification and use of audit logs for system management and system security purposes, such as the detection of performance problems, application flaw, or support for a reconstruction of data, which are dealt with by general computer security standards such as ISO/IEC 15408 (all parts)[9]. Annex A gives examples of audit scenarios. Annex B gives an overview of audit log services.
- Status
- Not Published
- Technical Committee
- ISO/TC 215 - Health informatics
- Drafting Committee
- ISO/TC 215/WG 4 - Security, Safety and Privacy
- Current Stage
- 5020 - FDIS ballot initiated: 2 months. Proof sent to secretariat
- Start Date
- 18-Nov-2026
- Completion Date
- 21-Nov-2026
Buy Documents
ISO/PRF 27789 - Health informatics — Audit trails for electronic health records
REDLINE ISO/PRF 27789 - Health informatics — Audit trails for electronic health records
Relations
- Consolidates
prEN ISO 27789 - Health informatics - Audit trails for electronic health records (ISO/DIS 27789:2026) - Effective Date
- 12-Feb-2026
- Effective Date
- 19-Jul-2025
- Effective Date
- 05-Jul-2025
Buy Documents
ISO/PRF 27789 - Health informatics — Audit trails for electronic health records
REDLINE ISO/PRF 27789 - Health informatics — Audit trails for electronic health records
Get Certified
Connect with accredited certification bodies for this standard

BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.

NYCE
Mexican standards and certification body.
Sponsored listings
Frequently Asked Questions
ISO/PRF 27789 is a draft published by the International Organization for Standardization (ISO). Its full title is "Health informatics — Audit trails for electronic health records". This standard covers: This document specifies a common framework for audit trails for electronic health records (EHR), in terms of audit trigger events and audit data, to keep the complete set of personal health information auditable across information systems and domains. It is applicable to systems processing personal health information that create a secure audit record each time a user reads, creates, updates, or archives personal health information via the system. NOTE Such audit records at a minimum uniquely identify the user, uniquely identify the subject of care, identify the function performed by the user (record creation, read, update, etc.), and record the date and time at which the function was performed. This document covers only actions performed on the EHR, which are governed by the access policy for the domain where the electronic health record resides. It does not deal with any personal health information from the electronic health record, other than identifiers, the audit record only containing links to EHR segments as defined by the governing access policy. It does not cover the specification and use of audit logs for system management and system security purposes, such as the detection of performance problems, application flaw, or support for a reconstruction of data, which are dealt with by general computer security standards such as ISO/IEC 15408 (all parts)[9]. Annex A gives examples of audit scenarios. Annex B gives an overview of audit log services.
This document specifies a common framework for audit trails for electronic health records (EHR), in terms of audit trigger events and audit data, to keep the complete set of personal health information auditable across information systems and domains. It is applicable to systems processing personal health information that create a secure audit record each time a user reads, creates, updates, or archives personal health information via the system. NOTE Such audit records at a minimum uniquely identify the user, uniquely identify the subject of care, identify the function performed by the user (record creation, read, update, etc.), and record the date and time at which the function was performed. This document covers only actions performed on the EHR, which are governed by the access policy for the domain where the electronic health record resides. It does not deal with any personal health information from the electronic health record, other than identifiers, the audit record only containing links to EHR segments as defined by the governing access policy. It does not cover the specification and use of audit logs for system management and system security purposes, such as the detection of performance problems, application flaw, or support for a reconstruction of data, which are dealt with by general computer security standards such as ISO/IEC 15408 (all parts)[9]. Annex A gives examples of audit scenarios. Annex B gives an overview of audit log services.
ISO/PRF 27789 is classified under the following ICS (International Classification for Standards) categories: 35.240.80 - IT applications in health care technology. The ICS classification helps identify the subject area and facilitates finding related standards.
ISO/PRF 27789 has the following relationships with other standards: It is inter standard links to prEN ISO 27789, ISO 17294-2:2023, ISO 27789:2021. Understanding these relationships helps ensure you are using the most current and applicable version of the standard.
ISO/PRF 27789 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
International
Standard
ISO 27789
Third edition
Health informatics — Audit trails
for electronic health records
Informatique de santé — Historique d'expertise des dossiers de
santé informatisés
PROOF/ÉPREUVE
Reference number
ISO 27789:2026(en) © ISO 2026
ISO 27789:2026(en)
© ISO 2026
All rights reserved.
This ISO publication is protected by copyright and is owned by ISO and/or its licensors.
The content of this ISO publication is provided under licence, not sold. Use is subject to the applicable licence terms issued by ISO,
an ISO member body, or an authorized third-party distributor.
Except as required for implementation or expressly permitted by a separate licence, no part of this ISO publication may be
reproduced, distributed, modified, used, or made available in any form or by any means – electronic or mechanical, including
photocopying, scanning, recording, or posting on internal or external digital platforms.
Any use beyond the scope of the granted rights is prohibited and may result in legal action.
ISO copyright office
CP 401 • CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
PROOF/ÉPREUVE
ii
ISO 27789:2026(en)
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 4
5 Requirements and uses of audit data. 4
5.1 Ethical and formal requirements .4
5.1.1 General .4
5.1.2 Access policy .4
5.1.3 Unambiguous identification of information system users.5
5.1.4 User roles .5
5.1.5 Secure audit records .5
5.2 Uses of audit data .5
5.2.1 Governance and supervision .5
5.2.2 Subjects of care exercising their rights .6
5.2.3 Evidence and retention requirements .6
6 Trigger events . 6
6.1 General .6
6.2 Details of the event types and their contents .7
6.2.1 Access events to the personal health information .7
6.2.2 Query events to the personal health information .7
7 Audit record details . 7
7.1 The general record format .7
7.2 Trigger event identification . . .9
7.2.1 Event ID .9
7.2.2 Event action code .10
7.2.3 Event date and time .10
7.2.4 Event outcome indicator .11
7.2.5 Event type code .11
7.3 User identification .11
7.3.1 User ID .11
7.3.2 Alternative user ID . 12
7.3.3 User name . 12
7.3.4 User is requestor . 12
7.3.5 Role ID code . 12
7.3.6 Purpose of use . 13
7.4 Access point identification .14
7.4.1 Network access point type code .14
7.4.2 Network access point ID . 15
7.5 Audit source identification . 15
7.5.1 Overview . 15
7.5.2 Audit enterprise site ID .16
7.5.3 Audit source ID . . .16
7.5.4 Audit source type code .16
7.6 Participant object identification .17
7.6.1 Overview .17
7.6.2 Participant object type code .17
7.6.3 Participant object type code role .18
7.6.4 Participant object data life cycle and record entry lifecycle events .19
7.6.5 Participant object ID type code .21
7.6.6 Participant object Permission PolicySet . 22
PROOF/ÉPREUVE
iii
ISO 27789:2026(en)
7.6.7 Participant object sensitivity . 22
7.6.8 Participant object ID . 22
7.6.9 Participant object name . 22
7.6.10 Participant object query . 22
7.6.11 Participant object detail, Participant object description . 23
8 Audit records for individual events .23
8.1 Access events . 23
8.2 Query events . 25
9 Secure management of audit data .28
9.1 Security considerations . 28
9.2 Securing the availability of the audit system . 28
9.3 Retention requirements . 28
9.4 Securing the confidentiality and integrity of audit trails . 28
9.5 Access to audit data . 28
Annex A (informative) Audit scenarios .30
Annex B (informative) Audit log services .36
Bibliography .45
PROOF/ÉPREUVE
iv
ISO 27789:2026(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 215, Health informatics, in collaboration with
the European Committee for Standardization (CEN) Technical Committee CEN/TC 251, Health informatics, in
accordance with the Agreement on technical cooperation between ISO and CEN (Vienna Agreement).
This third edition cancels and replaces the second edition (ISO 27789:2021), which has been technically
revised.
The main changes are as follows:
— harmonization between ISO 27789 audit record format and DICOM format;
— bibliography update.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
PROOF/ÉPREUVE
v
ISO 27789:2026(en)
Introduction
0.1 General
Personal health information is regarded by many as among the most confidential of all types of personal
information and protecting its confidentiality is essential to maintain the privacy of subjects of care. In
order to protect the consistency of health information, it is also important that its entire life cycle be fully
auditable. Health records should be created, processed and managed in ways that guarantee the integrity
and confidentiality of their contents and that support legitimate control by subjects of care in how the
records are created, used and maintained.
Trust in electronic health records requires physical and technical security elements along with data integrity
elements. Among the most important of all security requirements to protect personal health information
and the integrity of records are those relating to audit and logging. These help to ensure accountability
for subjects of care who entrust their information to electronic health record (EHR) systems. They also
help to protect record integrity, as they provide a strong incentive to users of such systems to adopt to
organizational policies on the use of these systems.
Effective audit and logging can help to uncover misuse of EHR systems or EHR data and can help organisations
and subjects of care obtain redress against users abusing their access privileges. For auditing to be effective,
it is necessary that audit trails contain sufficient information to address a wide variety of circumstances
(see Annex A).
Audit logs are complementary to access controls. The audit logs provide a means to assess conformity with
organizational access policy and can contribute to improving and refining the policy itself. But as such a
policy needs to anticipate the occurrence of unforeseen or emergency cases, analysis of the audit logs
becomes the primary means of ensuring access control for those cases.
This document is strictly limited in scope to logging of events. Changes to data values in fields of an EHR
are presumed to be recorded in the EHR database system itself and not in the audit log. It is presumed that
the EHR system itself contains both the previous and updated values of every field. This is consistent with
contemporary point-in-time database architectures. The audit log itself is presumed to contain no personal
health information other than identifiers and links to the record.
Electronic health records on an individual person can reside in many different information systems within
and across organisational or even jurisdictional boundaries. To keep track of all actions that involve records
on a particular subject of care, a common framework is a prerequisite. This document provides such a
framework. To support audit trails across distinct domains, it is essential to include references in this
framework to the policies that specify the requirements within the domain, such as access control rules and
retention periods. Domain policies may be referenced implicitly by identification of the audit log source.
0.2 Benefits of using this document
Standardization of audit trails on access to electronic health records aims at two goals:
— ensuring that information captured in an audit log is sufficient to clearly reconstruct a detailed chronology
of the events that have shaped the content of an electronic health record;
— ensuring that an audit trail of actions relating to a subject of care’s record can be reliably followed, even
across organizational domains.
This document is intended for those responsible for overseeing health information security or privacy and
for healthcare organizations and other custodians of health information seeking guidance on audit trails,
together with their security advisors, consultants, auditors, vendors and third-party service providers.
0.3 Related standards on electronic health record audit trails
[1]
This document builds upon, and is consistent with, the work begun in IETF RFC 3881 with respect to
[2]
access to the EHR. This document also builds upon and is consistent with the content in ISO/DIS 21089 .
PROOF/ÉPREUVE
vi
International Standard ISO 27789:2026(en)
Health informatics — Audit trails for electronic health
records
1 Scope
This document specifies a common framework for audit trails for electronic health records (EHR), in terms
of audit trigger events and audit data, to keep the complete set of personal health information auditable
across information systems and domains.
It is applicable to systems processing personal health information that create a secure audit record each
time a user reads, creates, updates or archives personal health information via the system.
NOTE Such audit records at a minimum uniquely identify the user, uniquely identify the subject of care, identify
the function performed by the user (record creation, read, update, etc.), and record the date and time at which the
function was performed.
This document covers only actions performed on the EHR, which are governed by the access policy for the
domain where the EHR resides. It does not deal with any personal health information from the EHR, other
than identifiers, the audit record only containing links to EHR segments as defined by the governing access
policy.
It does not cover the specification and use of audit logs for system management and system security
purposes, such as the detection of performance problems, application flaw, or support for a reconstruction
[3]
of data, which are dealt with by general computer security standards such as ISO/IEC 15408 (all parts) .
Annex A gives examples of audit scenarios. Annex B gives an overview of audit log services.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/DIS 21089, Health informatics — Trusted end-to-end information flows
ISO 27799:2025, Health informatics — Information security controls in health based on ISO/IEC 27002
ISO 8601-1, Date and time — Representations for information interchange — Part 1: Basic rules
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/DIS 21089 and the following apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
PROOF/ÉPREUVE
ISO 27789:2026(en)
3.1
access control, noun
means to ensure that access to assets is authorized and restricted based on business and security
requirements
[4]
[SOURCE: ISO/IEC 27000:2018 , 3.1]
3.2
access policy, noun
definition of the obligations for authorizing access to a resource
3.3
alert, noun
what is sent when the monitor service notices that a series of events matches a pattern
3.4
audit archive, noun
archival collection of one or more audit logs (3.6)
3.5
audit data, noun
data obtained from one or more audit records (3.7)
3.6
audit log, noun
chronological sequence of audit records (3.7), each of which contains data about a specific event
3.7
audit record, noun
record of a single specific event in the life cycle of an electronic health record (3.13)
3.8
audit system, noun
information processing system that maintains one or more audit logs (3.6)
3.9
authentication, noun
provision of assurance that a claimed characteristic of an entity is correct
[4]
[SOURCE: ISO/IEC 27000:2018 , 3.5]
3.10
authorization, noun
granting of rights, which includes the granting of access based on access rights
[5]
[SOURCE: ISO/IEC 2382:2015 , 2126256, modified — Notes to entry were deleted.]
3.11
availability, noun
property of being accessible and useable upon demand by an authorized entity
[4]
[SOURCE: ISO/IEC 27000:2018 , 3.7]
3.12
confidentiality, noun
property that information is not made available or disclosed to unauthorized individuals, entities, or
processes
[4]
[SOURCE: ISO/IEC 27000:2018 , 3.10]
PROOF/ÉPREUVE
ISO 27789:2026(en)
3.13
electronic health record, noun
EHR, noun
repository of (organized sets of) information regarding the health status of a subject of care (3.24), in
computer processable form
[6]
[SOURCE: ISO/TR 20514:2005 , 2.11, modified — “organized sets of” was added in parentheses; Note 1 to
entry was removed.]
3.14
electronic health record segment, noun
EHR segment, noun
part of an electronic health record (3.13) that constitutes a distinct resource for the access policy (3.2)
3.15
identification, noun
process of recognizing the attributes that identify the object
[7]
[SOURCE: ISO 16678:2014 , 2.1.7]
3.16
identifier, noun
one or more characters used to identify or name a data element and possibly to indicate certain properties
of that data element
[5]
[SOURCE: ISO/IEC 2382:2015 , 2121623, modified — Notes to entry were deleted.]
3.17
integrity, noun
property of accuracy and completeness
[4]
[SOURCE: ISO/IEC 27000:2018 , 3.36]
3.18
object identifier, noun
OID, noun
globally unique identifier (3.16) for an information object
Note 1 to entry: The object identifiers used in this document refer to code systems. These code systems can be defined
in a standard or locally defined per implementation. The object identifier is specified using the Abstract Syntax
[8] [9]
Notation One (ASN.1) defined in ISO/IEC 8824-1 and ISO/IEC 8824-2 .
3.19
policy, noun
set of rules related to a particular purpose
Note 1 to entry: A rule can be expressed as an obligation, an authorization (3.10), a permission or a prohibition.
[10]
[SOURCE: ISO 19101-2:2018 , 3.29, modified — Note 1 to entry added]
3.20
privilege, noun
capacity assigned to an entity by an authority
3.21
records management, noun
field of management responsible for control of creation, receipt, maintenance, use and disposition of records,
including processes for capturing and maintaining evidence of and information about business activities
and transactions in the form of records
[11]
[SOURCE: ISO 15489-1:2016 , 3.15, modified — “efficient and systematic” was removed before “control”.]
PROOF/ÉPREUVE
ISO 27789:2026(en)
3.22
role, noun
set of competences and/or performances associated with a task
3.23
sensitivity, noun
measure of the potential or perceived potential to abuse or misuse data about subjects or to harm them
3.24
subject of care, noun
healthcare actor with a person role (3.22), who seeks to receive, is receiving, or has received healthcare
EXAMPLE Patient, client, customer, or health plan member.
[12]
[SOURCE: ISO/TS 17975:2022 , 3.27, modified — The note to entry and example were removed, and a new
example was added.]
3.25
user, noun
person or other entity authorized by a provider to use some or all of the services provided by the provider
Note 1 to entry: A user can use the system to issue requests to objects in order to get them to perform functions in the
system on their behalf.
4 Abbreviated terms
1)
HL7 ® Health Level Seven
EV enumerated value
5 Requirements and uses of audit data
5.1 Ethical and formal requirements
5.1.1 General
Healthcare providers have their professional ethical responsibilities to meet. Among these are protecting
the privacy of subjects of care and documenting the findings and activities of care. Restricting access to
health records and ensuring their appropriate use are both essential requirements in healthcare and in
many jurisdictions. These requirements are set by law.
Secure audit trails of access to electronic health records can support conformity with professional ethics,
organizational policies and legislation, but they are not sufficient in themselves to assess completeness of an
electronic health record.
5.1.2 Access policy
Access to the audit trail shall be governed by an access policy. This policy should be determined by the
organization responsible for maintaining the audit log.
The access policy shall be in accordance with ISO 27799:2025, 5.1.
NOTE 1 The access policy is presumed to define an EHR segment structure.
NOTE 2 In the audit record the access policy is identified by the audit log source.
1) HL7® is the registered trademark of Health Level Seven International. This information is given for the convenience
of users of this document and does not constitute an endorsement by ISO of the product named.
PROOF/ÉPREUVE
ISO 27789:2026(en)
[13]
Guidance on specifying and implementing access policies can be found in ISO 22600 (all parts) . A field
“Participant object Permission Policy Set” is defined in 7.6.6 to support referencing the actual policies in the
audit record.
5.1.3 Unambiguous identification of information system users
The audit trails shall provide sufficient data to unambiguously identify all authorized health information
system users. Users of the information system can be persons, but also other entities.
The audit trails shall provide sufficient data to determine which authorized users and external systems have
accessed or been sent health record data from the system.
5.1.4 User roles
The audit trail shall show the role of the user while performing the recorded action on personal health
information.
Information systems processing personal health information should support role-based access control
capable of mapping each user to one or more roles, and each role to one or more system functions, as
[14]
recommended in ISO 27799:2025 , 8.2.
[15]
Functional and structural roles are documented in ISO 21298 . Additional guidance on privilege
[13]
management in health is given by ISO 22600 (all parts) .
5.1.5 Secure audit records
Secure audit records, in accordance with ISO 27799:2025, 8.15, shall be created each time personal health
information is read, created, updated, or archived. The audit records shall be maintained by secure records
management.
5.2 Uses of audit data
5.2.1 Governance and supervision
The audit trails shall provide data to enable responsible authorities to assess conformity with the
organization’s policy and to evaluate its effectiveness.
This implies:
— detecting unauthorized access to health records;
— evaluating emergency access;
— detecting abuse of privileges;
— support for:
— documenting access across domains;
— evaluation of access policies.
NOTE Full assessment of conformity with the organization’s policy can require additional data that is not
contained in the audit record, such as user information, permission tables or records on physical entry to secured
rooms. See Annex B for audit log services.
The audit trails shall provide sufficient data to determine all access within a defined time period to the
records of subjects of care, by a specified user.
The audit trails shall provide sufficient data to determine all access within a defined time period to the
records of subjects of care, that are marked to be at elevated risk of privacy breaches.
PROOF/ÉPREUVE
ISO 27789:2026(en)
5.2.2 Subjects of care exercising their rights
The audit trails shall provide sufficient data to subjects of care to enable:
— assessing which authorized user(s) have accessed their health record and when;
— assessing accountability for the content of the record;
— determination of conformity with the subject of care’s consent directives on access to or disclosure of the
subject of care’s data;
— determination of emergency access (if any) granted by a user to the subject of care’s record, including the
identification of the user, time of access and location where it was accessed from.
5.2.3 Evidence and retention requirements
The audit trails shall hold data (that care providers can use as documentary evidence) to determine which
actions were taken (create, look-up, read, correct, update, extract, output, archive, etc.) in relation to the
information as well as when and by whom.
Audit records shall be retained in accordance with the retention policy as specified in 9.3.
The following documents provides guidance and further information:
[2]
— ISO/DIS 21089 ;
[16]
— ISO 10781 .
6 Trigger events
6.1 General
The audit events (trigger events) that cause the audit system to generate audit records are defined according
to each health information system’s scale, purpose, and the contents of privacy and security policies. As the
scope of this document is limited to personal health information, only trigger events relating to access and
query of such information are specified here.
In order to generate the audit records that satisfy the requirement derived from Clause 5, i.e. “when”, “who”,
“whose”, audit records shall be generated for the following two events:
— access events to personal health information;
— query events about personal health information.
Examples of out-of-scope events are:
a) start and stop events of the application program;
b) authentication events involving authentication of users;
c) input and output events from/to the external environment;
d) access events to information other than personal health information;
e) security alert events related to the application programs;
f) access events to the audit log preserved in the application programs;
g) events generated by the operating system, middleware and so on;
h) access events generated by using system utilities;
i) physical connection/disconnection events of equipment to the network;
PROOF/ÉPREUVE
ISO 27789:2026(en)
j) start/stop events of the protection systems such as anti-virus protection systems;
k) software update events involving software modification or patch programs.
6.2 Details of the event types and their contents
6.2.1 Access events to the personal health information
In this document, the access to the personal health information is regarded as an audit event. Here “Access”
means the creation, reading, update, deletion of data. The contents of the audit log provide the information
about the access “when”, “who” and “access to whose” data to be protected. Table 1 describes the contents in
access events.
Table 1 — Access events
Event Contents
When
Access events to the personal health information Who
Access to whose
6.2.2 Query events to the personal health information
Querying an EHR database in order to obtain personal health information is regarded as an auditable event.
The query event is the query action itself, the reference to the personal health information resulting from
the query is regarded as the access event. The contents of the audit record provide the information about the
query “when”, “who” and “what condition for querying”. Table 2 describes the contents in query events.
Table 2 — Query events
Event Contents
When
Query events to the personal health information Who
What condition for querying
7 Audit record details
7.1 The general record format
Table 3 describes the general format of the audit records. Regarding to the record contents of each event,
[1] [17]
see Clause 8. The record format is defined after IETF RFC 3881 and ISO 12052 (DICOM PS3.15) with
addition of the optional fields PurposeOfUse and ParticipantObjectPolicySet.
PROOF/ÉPREUVE
ISO 27789:2026(en)
Table 3 — General format of the audit records
Type Field name Optionality Description Additional information
Event related EventID M ID for the audited event
(1)
Type of action performed
EventActionCode M
during the audited event
Date/time of the audited
EventDateTime M See 7.2
event occurrence
Success or failure of the
EventOutcomeIndicator U
event
EventTypeCode U The category of the event
user related ID for the person or pro-
UserID M
cess
(1.2)
Alternative ID for
AlternateUserID U
user or process
UserName U Name of user or process
Indicator that the user is
See 7.3
UserIsRequestor U
or is not the requestor
Specification of the role
RoleIDCode U the user plays when per-
forming the event
Code for the purpose of
PurposeOfUse U
use of the data accessed
Type of
NetworkAccessPointTypeCode U
network access point
See 7.4
ID for network
NetworkAccessPointID U
access point
audit system Site ID of
AuditEnterpriseSiteID U
related
audit enterprise
(1)
Unique ID See 7.5
AuditSourceID M
of audit source
AuditSourceTypeCode U Type code of audit source
Participant Code for the participant
object object type
ParticipantObjectTypeCode M
related
(0.N)
ParticipantObjectTypeCodeRole M Object type code of role
identifier for the data
ParticipantObjectDataLifeCycle U life-cycle stage for the
participant object
Type code of Participant
ParticipantObjectIDTypeCode M
Object ID
Permission PolicySet for
ParticipantObjectPolicySet U
ParticipantObjectID
Multiplicity:
(1): Only 1 exists
(1.2): 1 or 2 exist(s)
(0.N): 0 to N exist(s)
Optionality:
M: Mandatory
MC: Conditional Mandatory
U: Optional
PROOF/ÉPREUVE
ISO 27789:2026(en)
TTabablele 3 3 ((ccoonnttiinnueuedd))
Type Field name Optionality Description Additional information
sensitivity defined by the
ParticipantObjectSensitivity U policy for ParticipantOb-
jectID
Identifies a specific in-
ParticipantObjectID M stance of the participant See 7.6
object
Object name
of participant, such as a
ParticipantObjectName MC person’s name
Required if ParticipantO-
bjectQuery is not present.
Contents of query for
the participant object
ParticipantObjectQuery MC
Required if ParticipantO-
bjectName is not present.
Detail of
ParticipantObjectDetail U
participant object
Description of
ParticipantObjectDescription U
participant object
Multiplicity:
(1): Only 1 exists
(1.2): 1 or 2 exist(s)
(0.N): 0 to N exist(s)
Optionality:
M: Mandatory
MC: Conditional Mandatory
U: Optional
7.2 Trigger event identification
7.2.1 Event ID
a) Description: Unique identifier for a specific audited event, e.g. a menu item, program, rule, policy,
function code, application name, URL. It identifies the performed function.
b) Optionality: Mandatory.
c) Format/Values: Coded value, either defined by the system implementers or as a reference to a standard
vocabulary. The “code” attribute shall be unambiguous and unique, at least within audit Source ID (see
7.5). Examples of Event IDs are program name, method name, function name.
[18] [17]
NOTE The coding is modelled after IHE ITI TF-1 and TF-2 and ISO 12052 (DICOM PS3.15).
[1]
For implementation-defined coded values or references to standards, the XML schema in IETF RFC 3881
defines the optional attributes as shown in Table 4.
PROOF/ÉPREUVE
ISO 27789:2026(en)
Table 4 — Event ID reference attributes
Attribute Value
CodeSystem OID reference
CodeSystemName Name of the coding system; strongly recommended to be valued for locally-defined
code-sets.
CodeValue The specific code within the coding system
DisplayName The value to be used in displays and reports
OriginalText Input value that was translated to the code
To support the requirement for unambiguous event identification, multiple values shall not be specified.
d) Rationale: This identifies the audited function. For “Execute” Event Action Code audit records, this
identifies the application function performed.
At least one of CodeSystem (OID) or CodeSystemName is mandatory.
7.2.2 Event action code
a) Description: Indicator for type of action performed in the audit event.
b) Optionality: Mandatory.
c) Format/Values: Enumeration as shown in Table 5.
Table 5 — Event action codes
Value Meaning Examples
C Create Create a new database object, such as Placing an Order
R Read/Query Read or query data, such as a diagnosis
U Update Update data, such as Revise Personal Health Information
D Delete Make items inaccessible
E Execute Perform a system or application function such as search, extract,
or use of an object’s method
d) Rationale: This broadly indicates what kind of action was done on the Participant Object.
NOTE 1 Actions that are not enumerated above are considered an Execute of a specific function or object interface
method or treated two or more distinct events. An application action, such as an authorization or digital signing, is a
function Execute, and the Event ID would identify the function.
NOTE 2 For some applications, such as radiological imaging, a Query action can only determine the presence of data
but not access the data itself. Auditing need not always make as fine a distinction.
NOTE 3 Compound actions, such as “Move”, “Archive” or “Copy”, would be logged by creating audit data for each
operation – read, create, delete – or as an Execute of a function or method.
7.2.3 Event date and time
a) Description: A date/time specification that is unambiguous as to local time zones.
b) Optionality: Mandatory.
c) Format/Values: A date/time representation that is unambiguous in conveying universal coordinated
time (UTC). The time shall be in a UTC format as per ISO 8601-1 and shall be within a tolerance of no
more than 250 ms of UTC.
d) Rationale: This ties an event to a specific date and time. Security audits typically require a consistent
time base to eliminate time-zone issues arising from geographical distribution.
PROOF/ÉPREUVE
ISO 27789:2026(en)
[19]
NOTE In a distributed system, some sort of common time base, e.g. an NTP IETF RFC 1305 server, is a good
implementation tactic.
7.2.4 Event outcome indicator
a) Description: Indicates whether the event succeeded or failed.
b) Optionality: Optional.
c) Format/Values: Coded value. A code zero (0) indicates success. Values for failure of an event are not
meaningful within the scope of this document.
d) Rationale: This field is specified to conserve compatibility with audit trails as defined in IETF RFC 3881
[1]
.
7.2.5 Event type code
a) Description: Identifier for the category of event.
b) Optionality: Optional.
c) Format/Values: Coded value enumeration, either defined by the sy
...
ISO/DISPRF 27789
ISO/TC 215
Secretariat: ANSI
Date: 2026-09-0311-17
Health informatics — Audit trails for electronic health records
Informatique de santé — Historique d'expertise des dossiers de santé informatisés
DIS stage
TTTThhhhiiiis drs drs drs draaaaftfffttt i i i is s s s susususubbbbmmmmiiiitttttttteeeedd d d ttttoooo a aaa pppparaaarrraaaallellellellel l l l vvvvooootttteeee i i i innnn IIIISSSSOOOO,,,, CCCCEEEEN.N.N.N.
VVoottiing bng beegiginsns o on:n: 202 20266--0303--1313
VoVotintingg t tererminminatateses o onn:: 22002266--0066--0505
© PROOF
ISO/DISPRF 27789:2026(en)
All rights reserved. Unless otherwise specified,
This ISO publication is protected by copyright and is owned by ISO and/or its licensors.
The content of this ISO publication is provided under licence, not sold. Use is subject to the applicable licence terms issued
by ISO, an ISO member body, or an authorized third-party distributor.
Except as required in the context of its for implementation or expressly permitted by a separate licence, no part of this
ISO publication may be reproduced or utilized otherwise, distributed, modified, used, or made available in any form or
by any means, – electronic or mechanical, including photocopying, scanning, recording, or posting on internal or external
digital platforms.
Any use beyond the internet or an intranet, without prior written permission. Permission can be requested from either
ISO at the address below or ISO’s member body in the countryscope of the requestergranted rights is prohibited and may
result in legal action.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: + 41 22 749 01 11
E-mailEmail: copyright@iso.org
Website: www.iso.org
Published in Switzerland
iii
ISO/DISPRF 27789:2026(en)
Contents
Foreword . v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 4
5 Requirements and uses of audit data . 4
5.1 Ethical and formal requirements . 4
5.2 Uses of audit data . 5
6 Trigger events . 6
6.1 General . 6
6.2 Details of the event types and their contents . 7
7 Audit record details . 8
7.1 The general record format . 8
7.2 Trigger event identification . 10
7.3 User identification . 12
7.4 Access point identification . 16
7.5 Audit source identification . 17
7.6 Participant object identification . 18
8 Audit records for individual events . 25
8.1 Access events . 25
8.2 Query events . 27
9 Secure management of audit data . 30
9.1 Security considerations . 30
9.2 Securing the availability of the audit system . 30
9.3 Retention requirements . 30
9.4 Securing the confidentiality and integrity of audit trails . 30
9.5 Access to audit data . 31
Annex A (informative) Audit scenarios . 32
Annex B (informative) Audit log services . 38
Bibliography . 50
iv
ISO/DISPRF 27789:2026(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of
ISO documents should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawnISO draws attention to the possibility that some of the elementsimplementation of this
document may beinvolve the subjectuse of (a) patent(s). ISO takes no position concerning the evidence,
validity or applicability of any claimed patent rights in respect thereof. As of the date of publication of this
document, ISO had not received notice of (a) patent(s) which may be required to implement this document.
However, implementers are cautioned that this may not represent the latest information, which may be
obtained from the patent database available at www.iso.org/patents. ISO shall not be held responsible for
identifying any or all such patent rights. Details of any patent rights identified during the development of the
document will be in the Introduction and/or on the ISO list of patent declarations received (see ).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 215, Health informatics, in collaboration with
the European Committee for Standardization (CEN) Technical Committee CEN/TC 251, Health informatics, in
accordance with the Agreement on technical cooperation between ISO and CEN (Vienna Agreement).
This third edition cancels and replaces the second edition (ISO 27789:2021), which has been technically
revised.
The main changes are as follows:
— harmonization between ISO 27789 audit record format and DICOM format;
— bibliography update.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
v
ISO/DISPRF 27789:2026(en)
Introduction
0.1 General
Personal health information is regarded by many as among the most confidential of all types of personal
information and protecting its confidentiality is essential to maintain the privacy of subjects of care. In order
to protect the consistency of health information, it is also important that its entire life cycle be fully auditable.
Health records should be created, processed and managed in ways that guarantee the integrity and
confidentiality of their contents and that support legitimate control by subjects of care in how the records are
created, used and maintained.
Trust in electronic health records requires physical and technical security elements along with data integrity
elements. Among the most important of all security requirements to protect personal health information and
the integrity of records are those relating to audit and logging. These help to ensure accountability for subjects
of care who entrust their information to electronic health record (EHR) systems. They also help to protect
record integrity, as they provide a strong incentive to users of such systems to adopt to organizational policies
on the use of these systems.
Effective audit and logging can help to uncover misuse of EHR systems or EHR data and can help organisations
and subjects of care obtain redress against users abusing their access privileges. For auditing to be effective,
it is necessary that audit trails contain sufficient information to address a wide variety of circumstances (see
Annex A).
Audit logs are complementary to access controls. The audit logs provide a means to assess conformity with
organizational access policy and can contribute to improving and refining the policy itself. But as such a policy
needs to anticipate the occurrence of unforeseen or emergency cases, analysis of the audit logs becomes the
primary means of ensuring access control for those cases.
This document is strictly limited in scope to logging of events. Changes to data values in fields of an EHR are
presumed to be recorded in the EHR database system itself and not in the audit log. It is presumed that the
EHR system itself contains both the previous and updated values of every field. This is consistent with
contemporary point-in-time database architectures. The audit log itself is presumed to contain no personal
health information other than identifiers and links to the record.
Electronic health records on an individual person can reside in many different information systems within
and across organisational or even jurisdictional boundaries. To keep track of all actions that involve records
on a particular subject of care, a common framework is a prerequisite. This document provides such a
framework. To support audit trails across distinct domains, it is essential to include references in this
framework to the policies that specify the requirements within the domain, such as access control rules and
retention periods. Domain policies may be referenced implicitly by identification of the audit log source.
0.2 Benefits of using this document
Standardization of audit trails on access to electronic health records aims at two goals:
— ensuring that information captured in an audit log is sufficient to clearly reconstruct a detailed chronology
of the events that have shaped the content of an electronic health record;
— ensuring that an audit trail of actions relating to a subject of care ’scare’s record can be reliably followed,
even across organizational domains.
This document is intended for those responsible for overseeing health information security or privacy and for
healthcare organizations and other custodians of health information seeking guidance on audit trails, together
with their security advisors, consultants, auditors, vendors and third-party service providers.
vi
ISO/DISPRF 27789:2026(en)
0.3 Related standards on electronic health record audit trails
[1]
This document builds upon, and is consistent with, the work begun in IETF RFC 3881 with respect to access
[2]
to the EHR. This document also builds upon and is consistent with the content in ISO/CDDIS 21089 .
vii
ISO/DISPRF 27789:2026(en)
Health informatics — Audit trails for electronic health records
1 Scope
This document specifies a common framework for audit trails for electronic health records (EHR), in terms of
audit trigger events and audit data, to keep the complete set of personal health information auditable across
information systems and domains.
It is applicable to systems processing personal health information that create a secure audit record each time
a user reads, creates, updates, or archives personal health information via the system.
NOTE Such audit records at a minimum uniquely identify the user, uniquely identify the subject of care, identify the
function performed by the user (record creation, read, update, etc.), and record the date and time at which the function
was performed.
This document covers only actions performed on the EHR, which are governed by the access policy for the
domain where the electronic health recordEHR resides. It does not deal with any personal health information
from the electronic health recordEHR, other than identifiers, the audit record only containing links to EHR
segments as defined by the governing access policy.
It does not cover the specification and use of audit logs for system management and system security purposes,
such as the detection of performance problems, application flaw, or support for a reconstruction of data, which
are dealt with by general computer security standards such as ISO/IEC 15408 (all parts) all parts.
Annex A gives examples of audit scenarios. Annex B gives an overview of audit log services.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content constitutes
requirements of this document. For dated references, only the edition cited applies. For undated references,
the latest edition of the referenced document (including any amendments) applies.
ISO/DIS 21089, Health informatics — Trusted end-to-end information flows
ISO 27799:2025, Health informatics — Information security controls in health based on ISO/IEC 27002
ISO 8601-1, Date and time — Representations for information interchange — Part 1: Basic rules
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/DIS 21089 and the following terms
and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obp
— IEC Electropedia: available at https://www.electropedia.org/https://www.electropedia.org/
3.1
access control, noun
means to ensure that access to assets is authorized and restricted based on business and security
requirements
ISO/DISPRF 27789:2026(en)
[4]
[SOURCE: ISO/IEC 27000:2018 , 3.1]
3.2
access policy, noun
definition of the obligations for authorizing access to a resource
3.3
alert, noun
what is sent when the monitor service notices that a series of events matches a pattern
3.4
audit archive, noun
archival collection of one or more audit logs (3.6)
3.5
audit data, noun
data obtained from one or more audit records (3.7)
3.6
audit log, noun
chronological sequence of audit records (3.7,), each of which contains data about a specific event
3.7
audit record, noun
record of a single specific event in the life cycle of an electronic health record (3.13)
3.8
audit system, noun
information processing system that maintains one or more audit logs (3.6)
3.9
authentication, noun
provision of assurance that a claimed characteristic of an entity is correct
[4]
[SOURCE: ISO/IEC 27000:2018 , 3.5]
3.10
authorization, noun
granting of rights, which includes the granting of access based on access rights
[5]
[SOURCE: ISO/IEC 2382:2015 , 2126256, modified — Notes to entry were deleted.]
3.11
availability, noun
property of being accessible and useable upon demand by an authorized entity
[4]
[SOURCE: ISO/IEC 27000:2018 , 3.7]
3.12
confidentiality, noun
property that information is not made available or disclosed to unauthorized individuals, entities, or processes
[4]
[SOURCE: ISO/IEC 27000:2018 , 3.10]
ISO/DISPRF 27789:2026(en)
3.13
electronic health record, noun
EHR, noun
repository of (organized sets of) information regarding the health status of a subject of care (3.24), in computer
processable form
[6]
[SOURCE: ISO/TR 20514:2005 , 2.11, modified — Text in parenthesis added“organized sets of” was added
in parentheses; Note 1 to entry was removed.]
3.14
electronic health record segment, noun
EHR segment, noun
part of an electronic health record (3.13) that constitutes a distinct resource for the access policy (3.2)
3.15
identification, noun
process of recognizing the attributes that identify the object
[7]
[SOURCE: ISO 16678:2014 , 2.1.7]
3.16
identifier, noun
one or more characters used to identify or name a data element and possibly to indicate certain properties of
that data element
[5]
[SOURCE: ISO/IEC 2382:2015 , 2121623, modified — Notes to entry were deleted.]
3.17
integrity, noun
property of accuracy and completeness
[4]
[SOURCE: ISO/IEC 27000:2018 , 3.36]
3.18
object identifier, noun
OID, noun
globally unique identifier (3.16) for an information object
Note 1 to entry: The object identifiers used in this document refer to code systems. These code systems can be defined in
a standard or locally defined per implementation. The object identifier () is specified using the Abstract Syntax Notation
[8] [9]
One (ASN.1) defined in ISO/IEC 8824-1 and ISO/IEC 8824-2 .
3.19
policy, noun
set of rules related to a particular purpose
Note 1 to entry: A rule can be expressed as an obligation, an authorization (3.10), a permission or a prohibition.
[10]
[SOURCE: ISO 19101-2:2018 , 3.29, modified — Note 1 to entry added]
3.20
privilege, noun
capacity assigned to an entity by an authority
ISO/DISPRF 27789:2026(en)
3.21
records management, noun
field of management responsible for control of creation, receipt, maintenance, use and disposition of records,
including processes for capturing and maintaining evidence of and information about business activities and
transactions in the form of records
[11]
[SOURCE: ISO 15489-1:2016 , 3.15, modified — Some adjectives“efficient and systematic” was removed]
before “control”.]
3.22
role, noun
set of competences and/or performances associated with a task
3.23
sensitivity, noun
measure of the potential or perceived potential to abuse or misuse data about subjects or to harm them
3.24
subject of care, noun
healthcare actor with a person role (3.22;), who seeks to receive, is receiving, or has received healthcare
EXAMPLE Patient, client, customer, or health plan member.
[12]
[SOURCE: ISO/TS 17975:2022 , 3.27, modified — ExamplesThe note to entry and example were removed,
and a new example was added.]
3.25
user, noun
person or other entity authorized by a provider to use some or all of the services provided by the provider
Note 1 to entry: Also, human being usingA user can use the system to issue requests to objects in order to get them to
perform functions in the system on their behalf.
4 Abbreviated terms
HL7 ® Health Level Seven
EV Enumerated Valueenumerated value
5 Requirements and uses of audit data
5.1 Ethical and formal requirements
5.1.1 General
Healthcare providers have their professional ethical responsibilities to meet. Among these are protecting the
privacy of subjects of care and documenting the findings and activities of care. Restricting access to health
records and ensuring their appropriate use are both essential requirements in healthcare and in many
jurisdictions, these. These requirements are set down inby law.
1)
HL7® is the registered trademark of Health Level Seven International. This information is given for the convenience of
users of this document and does not constitute an endorsement by ISO of the product named.
ISO/DISPRF 27789:2026(en)
Secure audit trails of access to electronic health records can support conformity with professional ethics,
organizational policies and legislation, but they are not sufficient in themselves to assess completeness of an
electronic health record.
5.1.2 Access policy
Access to the audit trail shall be governed by an access policy. This policy should be determined by the
organization responsible for maintaining the audit log.
The access policy shall be in accordance with ISO 27799:2025, 5.1.
NOTE 1 The access policy is presumed to define an EHR segment structure.
NOTE 2 In the audit record the access policy is identified by the audit log source.
Guidance on specifying and implementing access policies can be found in ISO 22600 (all parts) all parts. A
field “Participant object Permission Policy Set” is defined in 7.6.6 to support referencing the actual policies in
the audit record.
5.1.3 Unambiguous identification of information system users
The audit trails shall provide sufficient data to unambiguously identify all authorized health information
system users. Users of the information system can be persons, but also other entities.
The audit trails shall provide sufficient data to determine which authorized users and external systems have
accessed or been sent health record data from the system.
5.1.4 User roles
The audit trail shall show the role of the user while performing the recorded action on personal health
information.
Information systems processing personal health information should support role-based access control
capable of mapping each user to one or more roles, and each role to one or more system functions, as
[14]
recommended in ISO 27799:2025 , 8.2.
[15]
Functional and structural roles are documented in ISO 21298 . Additional guidance on privilege
management in health is given by ISO 22600 (all parts) (all parts).
5.1.5 Secure audit records
Secure audit records, in accordance with ISO 27799:2025, 8.15, shall be created each time personal health
information is read, created, updated, or archived. The audit records shall be maintained by secure records
management.
5.2 Uses of audit data
5.2.1 Governance and supervision
The audit trails shall provide data to enable responsible authorities to assess conformity with the
organization’s policy and to evaluate its effectiveness.
This implies:
— detecting unauthorized access to health records,;
ISO/DISPRF 27789:2026(en)
— evaluating emergency access, and;
— detecting abuse of privileges.;
— and support for:
— documenting access across domains, and;
— evaluation of access policies.
NOTE Full assessment of conformity with the organization’s policy can require additional data that is not contained
in the audit record, such as user information, permission tables or records on physical entry to secured rooms. See Annex
B for audit log services.
The audit trails shall provide sufficient data to determine all access within a defined time period to the records
of subjects of care, by a specified user.
The audit trails shall provide sufficient data to determine all access within a defined time period to the records
of subjects of care, that are marked to be at elevated risk of privacy breaches.
5.2.2 Subjects of care exercising their rights
The audit trails shall provide sufficient data to subjects of care to enable:
— assessing which authorized user(s) have accessed his/hertheir health record and when,;
— assessing accountability for the content of the record,;
— determination of conformity with the subject of care'scare’s consent directives on access to or disclosure
of the subject of care'scare’s data, and;
— determination of emergency access (if any) granted by a user to the subject of care'scare’s record,
including the identification of the user, time of access and location where it was accessed from.
5.2.3 Evidence and retention requirements
The audit trails shall hold data [((that care providers can use as documentary evidence)]) to determine which
actions were taken (create, look-up, read, correct, update, extract, output, archive, etc.) in relation to the
information as well as when and by whom.
Audit records shall be retained in accordance with the retention policy as specified in 9.3.
The following documents provides guidance and further information:
[2]
— ISO/DIS 21089 ;
[16]
— ISO 10781 .
6 Trigger events
6.1 General
The audit events (trigger events) that cause the audit system to generate audit records are defined according
to each health information system’s scale, purpose, and the contents of privacy and security policies. As the
scope of this document is limited to personal health information, only trigger events relating to access and
query of such information are specified here.
ISO/DISPRF 27789:2026(en)
In order to generate the audit records that satisfy the requirement derived from Clause 5, i.e. “when”, “who”,
“whose”, audit records shall be generated for the following two events:
— Accessaccess events to personal health information;
— Queryquery events about personal health information.
Examples of out-of-scope events are:
a) Startstart and stop events of the application program;
b) Authentication authentication events involving authentication of users;
c) Inputinput and output events from/to the external environment;
d) Accessaccess events to information other than personal health information;
e) Securitysecurity alert events related to the application programs;
f) Accessaccess events to the audit log preserved in the application programs;
g) Eventsevents generated by the operating system, middleware and so on;
h) Accessaccess events generated by using system utilities;
i) Physicalphysical connection/disconnection events of equipment to the network;
j) Startstart/stop events of the protection systems such as anti-virus protection systems;
k) Softwaresoftware update events involving software modification or patch programs.
6.2 Details of the event types and their contents
6.2.1 Access events to the personal health information
In this document, the access to the personal health information is regarded as an audit event. Here “Access”
means the creation, reading, update, deletion of data. The contents of the audit log provide the information
about the access “when”, “who” and “access to whose” data to be protected. Table 1 describes the contents in
access events.
Table 1 — Access events
Event Contents
When,
Access events to the personal health information Who,
Access to whose
6.2.2 Query events to the personal health information
Querying an EHR database in order to obtain personal health information is regarded as an auditable event.
The query event is the query action itself, the reference to the personal health information resulting from the
query is regarded as the access event. The contents of the audit record provide the information about the
query “when”, “who” and “what condition for querying”. Table 2 describes the contents in query events.
ISO/DISPRF 27789:2026(en)
Table 2 — Query events
Event Contents
When,
Query events to the personal health information Who,
What condition for querying
7 Audit record details
7.1 The general record format
Table 3 describes the general format of the audit records. Regarding to the record contents of each event, see
[1] [17]
Clause 8. The record format is defined after RFC 3881 IETF RFC 3881 and ISO 12052 (DICOM PS3.15)
with addition of the optional fields PurposeOfUse and ParticipantObjectPolicySet.
Table 3 — General format of the audit records
Type Field name OptionO Description Additional
ptionalit info.information
y
Event EventID M ID for the audited event
related
Type of action
(1)
EventActionCode M performed during the
audited event
Date/time of the audited See 7.2
EventDateTime M
event occurrence
Success or failure of the
EventOutcomeIndicator U
event
EventTypeCode U The category of the event
user related ID for the person or
UserID M
process
(1.2)
Alternative ID for
AlternateUserID U
user or process
UserName U Name of user or process
Indicator that the user is
See 7.3
UserIsRequestor U
or is not the requestor
Specification of the role
RoleIDCode U the user plays when
performing the event
Code for the purpose of
PurposeOfUse U
use of the data accessed
Type of
NetworkAccessPointTypeCode U
network access point
See 7.4
ID for network
NetworkAccessPointID U
access point
Site ID of
AuditEnterpriseSiteID U See 7.5
audit enterprise
ISO/DISPRF 27789:2026(en)
Type Field name OptionO Description Additional
ptionalit info.information
y
audit Unique ID
AuditSourceID M
system
of audit source
related
Type code of audit
(1)
AuditSourceTypeCode U
source
Participant Code for the participant
object object type
ParticipantObjectTypeCode M
related
(0.N)
ParticipantObjectTypeCodeRole M Object type code of role
identifier for the data
ParticipantObjectDataLifeCycle U life-cycle stage for the
participant object
Type code of Participant
ParticipantObjectIDTypeCode M
Object ID
Permission PolicySet for
ParticipantObjectPolicySet U
ParticipantObjectID
sensitivity defined by the
ParticipantObjectSensitivity U policy for
ParticipantObjectID
Identifies a specific
ParticipantObjectID M instance of the See 7.6
participant object
Object name
of participant, such as a
person’s name
ParticipantObjectName MC
Required if
ParticipantObjectQuery
is not present.
Contents of query for
the participant object
ParticipantObjectQuery MC
Required if
ParticipantObjectName
is not present.
Detail of
ParticipantObjectDetail U
participant object
Description of
ParticipantObjectDescription U
participant object
Multiplicity:
a
:(1): Only 1 exists
(0.1): 0 or 1 exists
(1.2): 1 or 2 exist(s)
(0.N): 0 to N exist(s)
Optionality:
M: Mandatory
MC: Conditional Mandatory
ISO/DISPRF 27789:2026(en)
Type Field name OptionO Description Additional
ptionalit info.information
y
U: Optional
M/U: Mandatory or Optional related to events
7.2 Trigger event identification
7.2.1 Event ID
a) Description: Unique identifier for a specific audited event, e.g. a menu item, program, rule, policy, function
code, application name, or URL. It identifies the performed function.
b) Optionality: Mandatory.
c) Format/Values: Coded value, either defined by the system implementers or as a reference to a standard
vocabulary. The “code” attribute shall be unambiguous and unique, at least within audit Source ID (see
7.5). Examples of Event IDs are program name, method name, or function name.
[18] [17]
NOTE The coding is modelled after IHE ITI TF-1 and TF-2 and ISO 12052 (DICOM PS3.15).
[1]
For implementation-defined coded values or references to standards, the XML schema in IETF RFC 3881 RFC
3881 defines the optional attributes as shown in Table 4.
Table 4 — Event ID reference attributes
Attribute Value
CodeSystem OID reference
CodeSystemName Name of the coding system; strongly recommended to be valued for locally-defined
code-sets.
CodeValue The specific code within the coding system
DisplayName The value to be used in displays and reports
OriginalText Input value that was translated to the code
To support the requirement for unambiguous event identification, multiple values mayshall not be specified.
d) Rationale: This identifies the audited function. For “Execute” Event Action Code audit records, this
identifies the application function performed.
At least one of CodeSystem (OID) or CodeSystemName is mandatory.
7.2.2 Event action code
a) Description: Indicator for type of action performed in the audit event.
b) Optionality: Mandatory.
c) Format/Values: Enumeration as shown in Table 5.
ISO/DISPRF 27789:2026(en)
Table 5 — Event action codes
Value Meaning Examples
C Create Create a new database object, such as Placing an Order
R Read/Query Read or query data, such as a diagnosis
U Update Update data, such as Revise Personal Health Information
D Delete Make items inaccessible
E Execute Perform a system or application function such as search,
extract, or use of an object'sobject’s method
d) Rationale: This broadly indicates what kind of action was done on the Participant Object.
NOTE 1 Actions that are not enumerated above are considered an Execute of a specific function or object interface
method or treated two or more distinct events. An application action, such as an authorization or digital signing, is a
function Execute, and the Event ID would identify the function.
NOTE 2 For some applications, such as radiological imaging, a Query action can only determine the presence of data
but not access the data itself. Auditing need not always make as fine a distinction.
NOTE 3 Compound actions, such as “Move”, “Archive” or “Copy”, would be logged by creating audit data for each
operation -– read, create, delete -– or as an Execute of a function or method.
7.2.3 Event date and time
a) Description: A date/time specification that is unambiguous as to local time zones.
b) Optionality: Mandatory.
c) Format/Values: A date/time representation that is unambiguous in conveying universal coordinated time
(UTC). The time shall be in a UTC format as per ISO 8601-1 and shall be within a tolerance of no more than
250 ms of UTC.
d) Rationale: This ties an event to a specific date and time. Security audits typically require a consistent time
base to eliminate time-zone issues arising from geographical distribution.
[19]
NOTE In a distributed system, some sort of common time base, e.g. an NTP IETF RFC 1305 server, is a good
implementation tactic.
7.2.4 Event outcome indicator
a) Description: Indicates whether the event succeeded or failed.
b) Optionality: Optional.
c) Format/Values: Coded value. A code zero (0) indicates success. Values for failure of an event are not
meaningful within the scope of this document.
[1]
d) Rationale: This field is specified to conserve compatibility with audit trails as defined in IETF RFC 3881 .
7.2.5 Event type code
a) Description: Identifier for the category of event.
b) Optionality: Optional.
ISO/DISPRF 27789:2026(en)
c) Format/Values: Coded value enumeration, either defined by the system implementers or as a reference
to a standard vocabulary. For implementation defined codes or references to standards, the XML schema
[1]
in IETF RFC 3881 defines the optional attributes as shown in Table 6.
Table 6 — Event type code reference attributes
Attribute Value
CodeSystem OID reference
CodeSystemName Name of the coding system; strongly recommended to be valued for locally-
defined code-sets
DisplayName The value to be used in displays and reports
OriginalText Input value that was translated to the code
Since events can be categorized in more than one way, there can be multiple values specified.
d) Rationale: This field enables queries of audit records by implementation-defined event categories.
7.3 User identification
7.3.1 User ID
a) Description: Unique identifier for the user actively participating in the event.
b) Optionality: Mandatory.
c) Format/Values:User identifier text string from the authentication system. It is a unique value within the
Audit Source ID (see 7.4).
d) Rationale: This field ties an audit event to a specific user. In this context, a user can be a person, group,
team, server, process, or task thread.
NOTE 1 For cross-system audits, especially with long retention, this user identifier is meant to permanently tie an
audit event to a specific user via a unique key that retains its uniqueness over the entire lifetime of the archiving of the
audit trail.
NOTE 2 For node-based authentication – where only the system hardware or process, but not a human user, is
identified – User ID would be the node name.
NOTE 3 If the audit trail is used for clinical audit, or to provide evidence, where needed, of misuse, the audit trail can
record sufficient information to unambiguously associate a unique identifier with an actual user.
7.3.2 Alternative user ID
a) Description: Alternative unique identifier for the user.
b) Optionality: Optional.
c) Format/Values: User identifier text string from authentication system. This identifier would be one
known to a common authentication system, if available.
d) Rationale: In some situations, a user may authenticate with one identity but, to access a specific
application system, may use a synonymous identify. The alternative identifier would then be the original
identify used for authentication, and the user ID is the one known to and used by the application.
ISO/DISPRF 27789:2026(en)
7.3.3 User name
a) Description: The human-meaningful name for the user.
b) Optionality: Optional.
c) Format/Values: Text string.
d) Rationale: The user ID and alternative user ID may be internal or otherwise obscure values. This field
assists the auditor in identifying the actual user.
7.3.4 User is requestor
a) Description: Indicator that the user is or is not the requestor, or initiator, for the event being audited.
b) Optionality: Optional.
c) Format/Values: Boolean, default/assumed value is “true”.
d) Rationale: This value is used to distinguish between requestor-users and recipient-users. For example, a
report can be retrieved by a user (the requestor). Or a user (the requestor) maycan initiate a report to be
sent to another user (who is the recipient of the report but not the requestor).
7.3.5 Role ID code
a) Description: Specification of the role(s) the user exercises when performing the event, as assigned in role-
based access control security. Such role-based access control systems map each user to one or more roles,
and each role to one or more system functions.
b) Optionality: Optional; multi-valued.
c) Format/Values: Coded value, with attribute “code” valued with the role code or text from authorization
system. More than one value may be specified, because more than one role-based access control system
[14]
or taxonomy or both may be in use. Note that both ISO 27799:2025 , 8.2 and ISO 22600 (all parts) (all
parts)specify that user of a health information system containing personal health information accesses its
services in a single role (i.e. users who have been registered with more than one role then designates a
single role during each health information system access session).
[20]
It is recommended to use a coding system compatible with the functional roles defined in ISO 21298 and
listed in Table 7.
The vocabulary identification for this list of coded values can be referenced by the following OID, specified
[8] [9]
using the Abstract Syntax Notation One (ASN.1) defined in ISO/IEC 8824-1 and ISO/IEC 8824-2 :
[20]
Vocabulary identification: iso (1) standard (0) functional and structural roles (ISO 21298 ) functional role
vocabulary (4).
Table 7 — Functional role ID codes
role_identifie role_name description
r
01 Subject of care principal data subject of the electronic health record
02 subject of care agent e.g. parent, guardian, carer, or other legal representative
ISO/DISPRF 27789:2026(en)
role_identifie role_name description
r
03 Personal healthcare healthcare professional or professionals with the closest relationship
professional to the patient, often the patient’s family doctor
04 Privileged healthcare nominated by the subject of care
professional
OR
nominated by the healthcare facility of care (if there is a nomination by
regulation, practice, etc. such as an emergency over-ride)
05 Healthcare professional party involved in providing direct healthcare to the patient
06 Health-related party indirectly involved in patient care, teaching, research, etc.
professional
07 Administrator any other parties supporting service provision to the patient
This identifies a high-level list of functional roles to enable interoperable exchanges across jurisdictional or
domain boundaries. This can be applied to manage the creation, access, processing, and communication of
health information. More granular functional roles may be asserted within a domain or jurisdiction or may be
agreed upon for communications between such domains or jurisdictions.
The codes may be implementation-defined or reference a standard vocabulary enumeration. For
[1]
implementation defined codes or references to standards, the XML schema in RFC 3881IETF RFC 3881
defines the optional attributes as shown in Table 8.
Table 8 — Role ID code reference attributes
Attribute Value description
CodeSystem OID reference
CodeSystemName Name of the coding system; strongly recommended to be valued for locally-defined
code-sets
Display Name The value to be used in displ
...







