FHIR Release 3 (STU) 5 Ballot

This page is part of the FHIR Specification (v3.0.2: STU (v5.0.0-ballot: R5 Ballot - see ballot notes 3). ). 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 R2

Using Codes Code Systems Value Sets Concept Maps Identifier Systems

4.2.13.326 4.3.2.211 HL7 Version 2 Table 0326 CodeSystem http://terminology.hl7.org/CodeSystem/object-role

Vocabulary Security icon Work Group   Maturity Level : N/A 3 External Trial Use Use Context : Any

This is a table code system defined as part of HL7 v2 . Related by the FHIR content: v2 Visit Indicator . project.

Summary

http://hl7.org/fhir/v2/0326 http://hl7.org/fhir/ValueSet/v2-0326 XML / JSON
Name: Defining URL: v2 Visit Indicator http://terminology.hl7.org/CodeSystem/object-role
Definition: Version: FHIR Value set/code system definition for HL7 v2 table 0326 ( Visit Indicator) 5.0.0-ballot
Code System URL: Name: AuditEventEntityRole
Title: AuditEventEntityRole
Value Set URL: Status: draft
Definition:

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

OID: Committee: ?? Security icon Work Group
CodeSystem Resource OID: 2.16.840.1.113883.4.642.4.1135 (for OID based terminology systems)
Flags: CaseSensitive, Complete
ValueSet Resource All codes ValueSet: XML / JSON AuditEventEntityRole

This value set Code system is used in the following places: value sets:

  • This value set is ValueSet: AuditEventEntityRole icon (Code representing the designated 'entire code system' value set for v2 Visit Indicator role the entity played in the audit event.)
  • ValueSet: AuditEventEntityRole (Code representing the role the entity played in the audit event.)

4.2.13.326.1 4.3.2.211.1 Code System Content

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

Comment Version
Code Description Display Deutsch (German) Definition Nederlands (Dutch) Copy
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. btn   btn
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. btn   btn
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. btn   btn
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. btn   btn
5 Account level (default) Master file Fallanlage bei ambulanten Fällen ohne Erfassung eines Besuchstages 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. Accountniveau (standaard) btn   btn
6 added v2.3 User A human participant not otherwise identified by some other category. btn   btn
7 V List (deprecated). btn   btn
8 Visit level Doctor Aufnahme (ambulanter Besuch, stationäre Episode) 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. Bezoekniveau btn   btn
9 added v2.3 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. btn   btn
10 Guarantor Insurance company, or any other organization who accepts responsibility for paying for the healthcare event. btn   btn
11 Security User Entity A person or active system object involved in the event with a security role. btn   btn
12 Security User Group A person or system object involved in the event with the authority to modify security roles of other objects. btn   btn
13 Security Resource A passive object, such as a role table, that is relevant to the event. btn   btn
14 Security Granularity Definition (deprecated) Relevant to certain RBAC security methodologies. btn   btn
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 practitioner and the doctor that actually provided the care to the patient. btn   btn
16 Data Destination The source or destination for data transfer, when it does not match some other role. btn   btn
17 Data Repository A source or destination for data transfer that acts as an archive, database, or similar role. btn   btn
18 Schedule An object that holds schedule information. This could be an appointment book, availability information, etc. btn   btn
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. btn   btn
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. btn   btn
21 Job Stream A list of jobs or a system that provides lists of jobs; e.g. an MWL SCP. btn   btn
22 Table (Deprecated). btn   btn
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. btn   btn
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. btn   btn

 

See the full registry of code systems 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. See Code System for further information.
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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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