Release 5 Preview #1

This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3

4.3.14.198 Code System http://terminology.hl7.org/CodeSystem/object-role

Security Work Group Maturity Level: 3Trial Use Use Context: Any

This is a code system defined by the FHIR project.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/object-role
Version:4.2.0
Name:AuditEventEntityRole
Title:AuditEventEntityRole
Definition:

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

Committee:Security Work Group
OID:2.16.840.1.113883.4.642.1.1135 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

4.3.14.198.1 Content

4.3.14.198.2 AuditEventEntityRole

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

This code system http://terminology.hl7.org/CodeSystem/object-role defines the following codes:

CodeDisplayDefinition
1 PatientThis 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.
2 LocationThis 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.
3 ReportThis 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.
4 Domain ResourceA logical object related to a health record event. This is any healthcare specific resource (object) not restricted to FHIR defined Resources.
5 Master fileThis is any configurable file used to control creation of documents. Examples include the objects maintained by the HL7 Master File transactions, Value Sets, etc.
6 UserA human participant not otherwise identified by some other category.
7 List(deprecated).
8 DoctorTypically, 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.
9 SubscriberA 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.
10 GuarantorInsurance company, or any other organization who accepts responsibility for paying for the healthcare event.
11 Security User EntityA person or active system object involved in the event with a security role.
12 Security User GroupA person or system object involved in the event with the authority to modify security roles of other objects.
13 Security ResourceA passive object, such as a role table, that is relevant to the event.
14 Security Granularity Definition(deprecated) Relevant to certain RBAC security methodologies.
15 PractitionerAny 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.
16 Data DestinationThe source or destination for data transfer, when it does not match some other role.
17 Data RepositoryA source or destination for data transfer that acts as an archive, database, or similar role.
18 ScheduleAn object that holds schedule information. This could be an appointment book, availability information, etc.
19 CustomerAn 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.
20 JobAn order, task, work item, procedure step, or other description of work to be performed; e.g. a particular instance of an MPPS.
21 Job StreamA list of jobs or a system that provides lists of jobs; e.g. an MWL SCP.
22 Table(Deprecated).
23 Routing CriteriaAn 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.
24 QueryThe 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.

 

See the full registry of code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code