This page is part of the HL7 Terminology (v1.0.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
Summary
Defining URL: | http://terminology.hl7.org/ValueSet/audit-source-type |
Version: | 4.1.0 |
Name: | AuditEventSourceType |
Status: | Active |
Title: | Audit Event Source Type |
Definition: | The type of process where the audit event originated from. |
Publisher: | NEMA/DICOM |
Committee: | Security |
OID: | 2.16.840.1.113883.4.642.3.466 (for OID based terminology systems) |
Maturity: | 3 |
Source Resource: | XML / JSON / Turtle |
References
This value set is not used
http://terminology.hl7.org/CodeSystem/security-source-type
This value set contains 9 concepts
Expansion based on Audit Event Source Type v4.2.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/security-source-type
Code | Display | Definition |
1 | User Device | End-user display device, diagnostic device. |
2 | Data Interface | Data acquisition device or instrument. |
3 | Web Server | Web Server process or thread. |
4 | Application Server | Application Server process or thread. |
5 | Database Server | Database Server process or thread. |
6 | Security Server | Security server, e.g. a domain controller. |
7 | Network Device | ISO level 1-3 network component. |
8 | Network Router | ISO level 4-6 operating software. |
9 | Other | Other kind of device (defined by DICOM, but some other code/system can be used). |
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 |
History
Date | Action | Custodian | Author | Comment |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |