STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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: R5 R4B R4 R3 R2

4.3.1.957 Value Set http://hl7.org/fhir/ValueSet/object-role

This is a value set defined by the FHIR project.

Summary

Defining URL:

http://hl7.org/fhir/ValueSet/object-role

Name:

AuditEventEntityRole

Definition:

Code representing the role the entity played in the event.

Committee:

Security

Work Group

OID:

2.16.840.1.113883.4.642.2.957 (for OID based terminology systems)

Copyright:

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.

Source Resource

XML / JSON

This value set is used in the following places:

This value set is the designated 'entire code system' value set for AuditEventEntityRole
AuditEvent.entity.role (Extensible)

4.3.1.957.1 Content Logical Definition

This value set includes codes from the following code systems:

Include all codes defined in http://hl7.org/fhir/object-role

4.3.1.957.2 Expansion

This expansion generated 06 Dec 2016

This value set contains 24 concepts

Expansion based on http://hl7.org/fhir/object-role version 1.8.0

All codes from system http://hl7.org/fhir/object-role

Code	Display	Definition
1	Patient	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.
2	Location	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.
3	Report	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.
4	Domain Resource	A logical object related to a health record event. This is any healthcare specific resource (object) not restricted to FHIR defined Resources.
5	Master 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.
6	User	A human participant not otherwise identified by some other category.
7	List	(deprecated)
8	Doctor	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.
9	Subscriber	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.
10	Guarantor	Insurance company, or any other organization who accepts responsibility for paying for the healthcare event.
11	Security User Entity	A person or active system object involved in the event with a security role.
12	Security User Group	A person or system object involved in the event with the authority to modify security roles of other objects.
13	Security Resource	A 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	Practitioner	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 practitioners and the doctor that actually provided the care to the patient.
16	Data Destination	The source or destination for data transfer, when it does not match some other role.
17	Data Repository	A source or destination for data transfer that acts as an archive, database, or similar role.
18	Schedule	An object that holds schedule information. This could be an appointment book, availability information, etc.
19	Customer	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.
20	Job	An order, task, work item, procedure step, or other description of work to be performed; e.g. a particular instance of an MPPS.
21	Job Stream	A list of jobs or a system that provides lists of jobs; e.g. an MWL SCP.
22	Table	(Deprecated)
23	Routing 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.
24	Query	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.

See the full registry of value sets defined as part of FHIR.

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

Source

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