This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). 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
Vocabulary Work Group | Maturity Level: 0 | Informative | Use Context: Any |
This is a code system defined by the FHIR project.
Summary
Defining URL: | http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle |
Version: | 20100826 |
Name: | DICOM Audit Message Record Lifecycle Events |
Title: | |
Definition: | Attached is vocabulary for the record lifecycle events, as per DICOM Audit Message, |
Committee: | ?? |
OID: | (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 Resource | XML / JSON |
This Code system is not currently used
Attached is vocabulary for the record lifecycle events, as per DICOM Audit Message,
Copyright Statement:
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.
This code system http://terminology.hl7.org/CodeSystem/dicom-audit-lifecycle defines the following codes:
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 |