HL7 Terminology (THO)
5.1.0 - Publication International flag

This page is part of the HL7 Terminology (v5.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

ValueSet: AuditEventEntityRole

Official URL: http://terminology.hl7.org/ValueSet/object-role Version: 0.5.0
Draft as of 2020-02-24 Maturity Level: 3 Responsible: HL7 (FHIR Project) Computable Name: AuditEventEntityRole
Other Identifiers: id: urn:oid:2.16.840.1.113883.4.642.3.460

Copyright/Legal: These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright © 2011 by the National Electrical Manufacturers Association.

Code representing the role the entity played in the audit event.


This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)



This value set contains 24 concepts

Expansion based on AuditEventEntityRole v0.5.0 (CodeSystem)


This object is the patient that is the subject of care related to this event. It is identifiable by patient ID or equivalent. The patient may be either human or animal.


This is a location identified as related to the event. This is usually the location where the event took place. Note that for shipping, the usual events are arrival at a location or departure from a location.


This object is any kind of persistent document created as a result of the event. This could be a paper report, film, electronic report, DICOM Study, etc. Issues related to medical records life cycle management are conveyed elsewhere.

  4http://terminology.hl7.org/CodeSystem/object-roleDomain Resource

A logical object related to a health record event. This is any healthcare specific resource (object) not restricted to FHIR defined Resources.

  5http://terminology.hl7.org/CodeSystem/object-roleMaster file

This is any configurable file used to control creation of documents. Examples include the objects maintained by the HL7 Master File transactions, Value Sets, etc.


A human participant not otherwise identified by some other category.




Typically, a licensed person who is providing or performing care related to the event, generally a physician. The key distinction between doctor and practitioner is with regards to their role, not the licensing. The doctor is the human who actually performed the work. The practitioner is the human or organization that is responsible for the work.


A person or system that is being notified as part of the event. This is relevant in situations where automated systems provide notifications to other parties when an event took place.


Insurance company, or any other organization who accepts responsibility for paying for the healthcare event.

  11http://terminology.hl7.org/CodeSystem/object-roleSecurity User Entity

A person or active system object involved in the event with a security role.

  12http://terminology.hl7.org/CodeSystem/object-roleSecurity User Group

A person or system object involved in the event with the authority to modify security roles of other objects.

  13http://terminology.hl7.org/CodeSystem/object-roleSecurity Resource

A passive object, such as a role table, that is relevant to the event.

  14http://terminology.hl7.org/CodeSystem/object-roleSecurity Granularity Definition

(deprecated) Relevant to certain RBAC security methodologies.


Any person or organization responsible for providing care. This encompasses all forms of care, licensed or otherwise, and all sorts of teams and care groups. Note the distinction between practitioner and the doctor that actually provided the care to the patient.

  16http://terminology.hl7.org/CodeSystem/object-roleData Destination

The source or destination for data transfer, when it does not match some other role.

  17http://terminology.hl7.org/CodeSystem/object-roleData Repository

A source or destination for data transfer that acts as an archive, database, or similar role.


An object that holds schedule information. This could be an appointment book, availability information, etc.


An organization or person that is the recipient of services. This could be an organization that is buying services for a patient, or a person that is buying services for an animal.


An order, task, work item, procedure step, or other description of work to be performed; e.g. a particular instance of an MPPS.

  21http://terminology.hl7.org/CodeSystem/object-roleJob Stream

A list of jobs or a system that provides lists of jobs; e.g. an MWL SCP.



  23http://terminology.hl7.org/CodeSystem/object-roleRouting Criteria

An object that specifies or controls the routing or delivery of items. For example, a distribution list is the routing criteria for mail. The items delivered may be documents, jobs, or other objects.


The contents of a query. This is used to capture the contents of any kind of query. For security surveillance purposes knowing the queries being made is very important.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code


2020-10-14reviseVocabulary WGGrahame GrieveReset Version after migration to UTG
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.