Digital Imaging and Communications in Medicine (DICOM)

304
Chapter 14 Standards and System Integration in Digital Medicine
Table 51 EVN (event) segment format, used for HL7 events
Field # Name Data type Required Default
1 Event Type Code ID No –
2 Recorded Date/Time TS Yes –
3 Date/Time Planned Event TS No –
4 Event Reason Code IS No –
5 Operator ID XCN No –
6 Event Occurred TS No –
7 Event Facility HD No –
The most popular versions of HL7 (2.3, 2.4, 2.5), have been around for a
while. In 2001, a completely new HL7 version 3.0 was released, changing both
the format and underlying organization of HL7 data. Just like DICOM 3.0, HL7
3.0 adopted object-oriented design (see 5.7.5) to represent the entire information
flow as an interaction between data objects. This paradigm shift led to the
shift in the HL7 format: the clumsy pipes were abandoned and the much more
appropriate and powerful XML was used:
A08
200601080823
200601080823
01
3175875
Sample
Joe
Albeit long-awaited, HL7 3.0 was perceived as a dramatic change from the
previous HL7 versions, which is why the majority of the clinical practices and
large, hard-to-evolve healthcare vendors still remain with HL7 2.x format. Nev-