This page is part of the FHIR Specification (v5.0.0-draft-final: Final QA Preview for R5 - see ballot notes). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Security Work Group | Maturity Level: 0 | Informative | Use Context: Country: World |
Official URL: http://hl7.org/fhir/ValueSet/security-source-type
|
Version: 5.0.0-draft-final | |||
active as of 2010-08-26 | Computable Name: AuditEventSourceType | |||
Flags: | OID: 2.16.840.1.113883.4.642.3.2981 |
This value set is used in the following places:
The type of process where the audit event originated from. Use of these codes is not required but is encouraged to maintain translation with DICOM AuditMessage schema.
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. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - 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 |