Release 4B Snapshot #1

This page is part of the FHIR Specification v4.3.0-snapshot1: R4B Snapshot to support the Jan 2022 Connectathon. About the R4B version of FHIR. The current officially released version is 4.3.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3

4.3.14.216 Code System http://terminology.hl7.org/CodeSystem/audit-event-type

Security Work Group Maturity Level: 0Informative Use Context: Any

This is a code system defined by the FHIR project.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/audit-event-type
Version:4.3.0-snapshot1
Name:AuditEventID
Title:Audit Event ID
Definition:

Event Types for Audit Events - defined by DICOM with some FHIR specific additions.

Committee:Security Work Group
OID:2.16.840.1.113883.4.642.1.1136 (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 ResourceXML / JSON

This Code system is used in the following value sets:

  • ValueSet: Audit Event ID (Event Types for Audit Events - defined by DICOM with some FHIR specific additions.)

This code system http://terminology.hl7.org/CodeSystem/audit-event-type defines the following codes:

CodeDisplayDefinition
rest RESTful OperationAudit Event: Execution of a RESTful operation as defined by FHIR.

 

See the full registry of code systems defined as part of FHIR.


Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. See Code System for further information.
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code