Back To Index  <<  Back To Terminology

ref Value Set epr_atna_participantObjectTypeCodeRole 2017‑11‑10 09:31:55

Id 2.16.840.1.113883.4.642.3.453 Effective Date valid from 2017‑11‑10 09:31:55
Status draft Draft Version Label 201704.1-stable
Name epr_atna_participantObjectTypeCodeRole Display Name epr_atna_participantObjectTypeCodeRole
Description Codesystem:   https://www.hl7.org/fhir/codesystem-object-role.html#4.2.12.454
Valueset: https://www.hl7.org/fhir/valueset-object-role.html#4.3.1.453

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

Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavors to appear in @nullFlavor attribute instead of @code.
download XML JSON CSV SQL SVS