CR 14300:2002

SLOVENSKI STANDARD
01-oktober-2003
=GUDYVWYHQDLQIRUPDWLND±0HGREUDWRYDOQRVWYHþSUHGVWDYQLKSRURþHYDOQLK
VLVWHPRY]GUDYVWYHQHJDYDUVWYD
Health Informatics - Interoperability of healthcare multimedia report systems
Ta slovenski standard je istoveten z: CR 14300:2002
ICS:
35.240.80 Uporabniške rešitve IT v IT applications in health care
zdravstveni tehniki technology
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

CEN REPORT
CR 14300
RAPPORT CEN
CEN BERICHT
January 2002
ICS
English version
Health Informatics - Interoperability of healthcare multimedia
report systems
This CEN Report was approved by CEN on 14 December 2001. It has been drawn up by the Technical Committee CEN/TC 251.
CEN members are the national standards bodies of Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece,
Iceland, Ireland, Italy, Luxembourg, Malta, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: rue de Stassart, 36  B-1050 Brussels
© 2002 CEN All rights of exploitation in any form and by any means reserved Ref. No. CR 14300:2002 E
worldwide for CEN national Members.

Contents
Foreword 7
1 INTRODUCTION 8
1.1 Executive Summary 8
1.2 Digital healthcare multimedia reports 9
1.3 Motivation 10
1.4 Aims and Objectives 10
1.4.1 Aims 10
1.4.2 Objectives 11
1.5 Method of Work 11
1.5.1 Traditional Healthcare Service Report Scenarios 11
1.5.2 Scenarios of healthcare multimedia reports 11
1.5.3 Multimedia report use cases 11
1.5.4 Conceptual Modelling 11
1.5.5 Logical data structures 12
1.5.6 Assessment of the applicability of relevant existing and emerging Standards and Specifications 12
1.5.7 Recommendations for use and/or extension of standards and Publicly Available Specifications 12
2SCOPE 13
3 REFERENCES AND BIBLIOGRAPHY 14
3.1 References 14
3.2 Bibliography 15
4 ABBREVIATIONS AND DEFINITIONS 16
4.1 Abbreviations 16
4.2 Definitions 17
5 REPORT SCENARIOS 22
5.1 Introduction 22
5.2 Healthcare Service Requests and Reports 22
5.3 Performing the Healthcare Procedure - production of results 23
5.3.1 Introduction 23
5.3.2 The Healthcare Procedure details 23
5.3.3 Healthcare Service Request approval 23
5.3.4 Appointment Scheduling 23
5.3.5 Acquisition Scheduling and Preparation 23
5.3.6 Acquisition and Processing of Healthcare Data 24
5.3.7 Data Processing 24
5.3.8 Preparation of material for reporting 24
5.4 The nature and content of Reports. 25
5.4.1 Free Reporting 25
5.4.2 Structured Reporting 25
5.4.3 Assistance for the Reporting Clinician 26
5.4.4 Selection of supplied Healthcare Procedure Products 26
5.4.5 Healthcare Service Report sections 26
5.4.6 Recording the Report Words 27
5.4.7 Supplementary Healthcare Service Report 27
5.4.8 Other supplied Healthcare Procedure Products 28
5.4.9 Report Approval 28
5.4.10 Joint reporting of a Healthcare Procedure 28
5.4.11 One to one Conference 28
5.4.12 Peer to peer Consultation 28
5.4.13 Report Distribution 28
5.4.14 Case Conference of the Patient 29
5.5 Utilisation of the Healthcare Service Report and Healthcare Procedure Products 29
5.5.1 Utilisation by the Requester for diagnosis or follow up 29
5.5.2 General Practitioner 29
5.5.3 Hospital Clinician Consultation 29
5.5.4 Ward, Dentistry and Casualty staff 29
5.6 Utilisation of medical data for therapy 30
5.6.1 Surgeon in Theatre 30
5.6.2 Planning 30
5.6.3 Interventional imaging 30
5.6.4 Per operative imaging 30
5.6.5 Endoscopy 30
5.7 Audit 30
5.8 Epidemiology 30
5.9 Administration 30
5.10 Teaching and Research 31
5.11 Presentation of Healthcare Service Reports to recipients 31
6 MULTIMEDIA SCENARIOS 32
6.1 Healthcare Multimedia Reports 32
6.1.1 Presentation Requirements - Computer Interaction 32
6.1.2 General Requirements 33
6.1.3 HCMR links to Healthcare Procedure Products 34
6.2 Examples of multimedia reports 34
6.2.1 Report on endoscopy. 34
6.2.2 Report on coronary angiography. 34
6.2.3 Report on a CT scan of a pituitary tumour. 34
6.2.4 Report on a gated Tc-99m Tetrofosmin cardiac single photon emission Tomography, SPET,
procedure. 35
6.2.5 Further Healthcare Procedure scenarios 35
6.2.6 Summary and Conclusions 36
6.2.7 Additional Requirements 37
6.3 Healthcare multimedia report data 37
6.3.1 Multimedia report contents 38
6.3.2 Healthcare Procedure Product logical data structures 38
6.4 Interoperability of multimedia report systems 40
7 USE CASE MODELLING 42
7.1 Introduction 42
7.2 Use Case Models of processes 42
7.2.1 Introduction 42
7.2.2 Sequence diagrams 44
8 CONCEPTUAL MODELS 57
8.1 Rationale 57
8.2 Level 0: Healthcare Service Request / Healthcare Service Report generic model 57
8.3 Level 1: Healthcare Multimedia Report (HCMR) 59
8.3.1 Healthcare Multimedia Report - Structuring, Content and HCMR links 59
8.3.2 Healthcare Multimedia Report - Multimedia Performance 62
8.4 Level 2: Diagnostic Imaging and Vital Signs Studies Reports 64
8.4.1 “Rendered procedure product” Entities 65
8.4.2 Life Cycle Entities Model 66
8.5 Level 3: Application of the model to Diagnostic Imaging 67
9 APPLICABILITY OF EXISTING STANDARDS AND SPECIFICATIONS 69
9.1 Introduction 69
9.2 Nature of HCMR 69
9.3 Nature of Standards to support HCMR 69
9.4 Generic report standards and specifications for Report Words 70
9.4.1 Relation to ENV 13606 - Part 1 and Part 2 70
9.4.2 Supplement 23 Structured Reporting 71
9.4.3 ENV12539-diagnostic services messages 74
9.4.4 HL7 74
9.5 Composite rendered procedure products 75
9.5.1 Imaging Modifiable rendering format 75
9.5.2 Waveform and other non-imaging data 76
9.6 Creation and modification of HCMR
9.7 Presentation of HCMR to report recipient in Navigation mode
9.7.1 Navigation mode Presentation in modifiable form
9.7.2 Navigation mode Presentation in non-modifiable form
9.8 Presentation of HCMR to report recipient in Performance mode
9.8.1 Performance mode Presentation in modifiable form
9.8.2 P 79
erformance mode Presentation in non-modifiable form
9.9 Mapping tables 80
10 CONCLUSIONS 88
10.1 Nature of HCMR 88
10.2 Generic report standards and specifications 88
10.3 Composite rendered Healthcare Procedure Products 88
10.3.1 Modifiable rendering format 88
10.3.2 Non- modifiable rendering format 88
10.4 Creation and modification of H522CMR 89
10.5 Presentation to report recipient 89
10.5.1 Presentation in modifiable form 89
10.5.2 Presentation in non-modifiable form 89
11 RECOMMENDATIONS 89
11.1 Recommendation 1 89
11.2 Recommendation 2 89
11.3 Recommendation 3 90
11.4 Recommendation 4 90
11.5 Recommendation 5 90
11.6 Recommendation 6 90
11.7 Recommendation 7 90
ANNEX TO THE CEN REPORT 91
1. MULTIMEDIA REPORTS OVERVIEW 94
1.1 Healthcare Service Reports 94
1.1.1 The Traditional Healthcare Service Report 94
1.1.2 The traditional Healthcare Service Report in electronic form 94
1.1.3 The Healthcare Multimedia Report 95
1.1.4 The record of a Healthcare Multimedia presentation 95
1.2 Interoperability 96
1.3 Interoperability of networked co-operating applications 98
1.4 Images and Medical images 98
1.4.1 Digital Image Data and Digital Images 99
1.4.2 Greyscale images - thresholding. 99
1.4.3 True and Pseudo Colour Images 99
1.4.4 Image descriptive data 99
1.5 Non-image Medical Device data 100
2. PATIENT DATA ACQUISITION 100
2.1 Introduction 100
2.2 Patient Data Acquisition, processing and reporting 100
2.2.1 Introduction -Healthcare Service Requests and Healthcare Service Reports. 100
2.2.2 Requesting a diagnostic service 101
3. PATIENT AND HEALTHCARE SERVICE REPORT DATA 102
3.1 Patient Measurement and Information item Data structures 102
3.1.1 Example of Patient data acquisition processing and display 102
3.1.2 Information Item Procedure Product Data Structure 104
3.1.3 Presentation of Information items - Labels and Annotation 104
3.1.4 Information item data structures 105
3.1.5 Vector and image descriptive data 106
3.2 Healthcare Service Report data records 107
3.2.1 Report Text 107
3.2.2 Rendered Healthcare Procedure Products 108
3.2.3 Multimedia Performance 108
3.3 Vital signs acquisition and reporting 108
3.3.1 EEG measurement scenario 108
3.3.2 Epilepsy intensive monitoring scenario 109
3.3.3 ENMG measurement scenario 110
3.3.4 Intensive care monitoring scenario 111
4. MULTIMEDIA REPORT DEMONSTRATION 112
4.1 Navigation presentation recorded as HTML file 112
4.2 Performance Presentation recorded as SMIL file 114
5. UNIFIED MODELLING LANGUAGE NOTES 115
5.1 Introduction 115
5.2 Use Cases 115
5.3 Sequence Diagrams 117
5.4 Class Diagrams 117
5.5 Relationships 118
Foreword
This CEN REPORT has been prepared by Technical Committee CEN/TC 251 "Health informatics", the
secretariat of which is held by SIS under mandate BC/CEN/03/255/97/23.6 by the European Commission and the
European Free Trade Association. This work item was originally entitled Medical Multimedia and Related
Interoperability Data Format but CEN/TC 251 decided to change the title to Interoperability of healthcare
multimedia report systems in order to reflect more accurately the main focus.
This report has been produced by members of the Project Team 34 MULTIMED under the supervision of
CEN/TC 251/WGIV: Technology for Interoperability.
This CEN Report is not a standard and does not contain the definition of a new data file format.
Defined terms are shown with the first letter of each word in capitals.
1 INTRODUCTION
1.1 Executive Summary
This CEN Report is concerned with the interoperability of systems for the creation, modification and presentation
of digital healthcare multimedia report records. In addressing these issues the purpose of this CEN Report is:

to examine the nature of healthcare reports as delivered and viewed using traditional methods

to recommend methods for the presentation of electronic healthcare service reports using multimedia
facilities

to assess the suitability of existing and emerging standards and specifications

to make recommendations for future work to enable the implementation of multimedia reports within the
clinical process.
Reports presented using electronic multimedia facilities should, by comparison with commonly used existing
methods, enable improved communication of the information obtained by service departments to those who
request their services, thus leading to improved quality of Healthcare.
This report is intended to inform standards makers, systems designers and healthcare professionals about the
nature of healthcare multimedia report records and show the way for the development of clinically viable
implementations.
The domain of Healthcare Procedure Reporting is reviewed by means of scenarios which take account of
previous CEN/TC 251 work and the views of clinicians and medical informaticians obtained by consultation. The
two most common means by which Healthcare Service Reports are traditionally presented to clinicians are
identified as a) report text on paper accompanied by optional supporting results in hardcopy form (e.g., X-Ray
films) and b) live presentation, for example, as part of a case conference.
Multimedia Scenarios explain the application of multimedia facilities in the domain of Healthcare Service Reports
and their subsequent use. Use cases illustrate the creation, amendment and subsequent use of healthcare
multimedia reports. Conceptual models are derived from the use cases and illustrate the generic logical data
structures required to record healthcare multimedia reports and the data presented. This CEN Report concludes
that the clinical needs for healthcare multimedia reports may be served by presentation in two modes:
a) Navigation mode: The report text is presented in a form such as that supported by a Web Browser. A clinician
can select as much or as little of the available material for presentation as is needed in the current clinical
situation in the same way as is currently done when a written report on paper is accompanied by selected
Healthcare Procedure Products such as images in hardcopy form. He/she also decides the order in which to
view the available material.
b) Performance mode: The report is presented in a form similar to a lecture type presentation, for example, as
part of a case conference and would appear to the recipient in the form of a video performance. The items and
their order of presentation cannot be altered from that chosen by that report author (apart from changes
implemented by the use of video like controls such as pause rewind, etc.), i.e. the material must be viewed in the
way the author believes to be most appropriate.
In short, a Navigation Mode record specifies the layout and rendering for a set of procedure products in space. A
Performance Mode record specifies how different Procedure Products are to be presented during a specified
period of time.
This CEN Report uses the analogy of the performance of a piece of orchestral music as represented in the
conductor's music score. In the case of a healthcare multimedia report Performance mode score there will be
one line for each presentation channel, such as a defined region of a display window or sound channel. The
score specifies the sequence and duration for the presentation of sets of healthcare information items, such as
images and annotations, in a number of display regions, perhaps with synchronised sound such as a 'voice over'
and annotation by fixed regions of interest and/or a pointer.
This CEN report explains the nature of the data to be presented as well as the presentation record data (score)
for performance mode and Navigable record data for Navigation mode. It is noted that the report text may be
required as the legally binding result of a healthcare service procedure. The availability of relevant existing
standards to support the identified needs is reviewed and recommendations for enhancement of existing
standards and creation of new standards are made.
This CEN Report concludes that Web-based and other standards/specifications, which support most of the
identified requirements for the exchange of healthcare multimedia report (HCMR) records already exist. These
standards/specifications also provide support of the identified presentation modes when interaction by the
recipient is not required (e.g., no windowing of images, etc.). One of the deliverables of this CEN Project is a
demonstration package that includes digital records of both Navigation mode and Performance mode HCMR
presentation.
Standards do not, however, exist for the creation and amendment of the record of Multimedia Presentations in
interactive form (record of the layout and rendering parameters of the presented procedure products). It is
recommended that authoring tools be developed to enable the production of healthcare multimedia report
records using the identified Navigation and Performance modes of presentation. These need to support both
interactive and non-interactive forms to enable co-operation between medically qualified and non-medically
qualified Healthcare Professionals in the task of producing multimedia reports. This should be implemented in
collaboration with relevant groups, including CEN/TC 251, ISO/TC 215, HL7 and DICOM.
1.2 Digital healthcare multimedia reports
A digital multimedia document may be defined as a document that includes numerical representations of
information that has been presented using different media. Such a document constitutes a digital record of a
multimedia presentation. The monomedia items presented may include for example: text (structured or free), a
static image (picture), a time series of images, a graphics entity (such as might delineate a Region of Interest), a
voice sound clip. One such monomedia entity may be related to another. For example, a Region of Interest may
need to be aligned in space upon the image to which it applies. A sound clip may need to be aligned in time with
a time series of images (synchronised). Multimedia presentation systems are, of course, also capable handling a
monomedia document (a document requiring presentation using one medium only e.g., text) and multimedia
documents which do not invoke synchronisation.
Interoperability of systems for the creation, modification and presentation of digital healthcare multimedia report
records depends on understanding and consistency in the representation of data. The key requirements for
healthcare multimedia report presentation are:
a) that appropriate use is made of multimedia facilities to enhance the communication of information from
reporting clinician to recipient and;
b) that the recipient sees and hears effectively the same things when he/she observes a presentation of the
multimedia report as the clinician saw and heard when the report was recorded.
The understanding of the requirements for interoperability of healthcare multimedia report systems requires an
understanding of the nature of the Healthcare Procedure Product data which is presented and the methods of
presentation. This CEN report includes discussion of the nature of the logical data structures required to carry
Healthcare Procedure Product data and healthcare multimedia report record data.
One of the main reasons for the need for specific Healthcare Standards is that medical images are of a different
nature from images generally used by multimedia applications. A medical image, such as the image rendered
from a regular array of X-Ray attenuation values acquired by a Computed Tomography (CT) modality, is a Digital
Image. A Digital Image is a visual representation of a Digital Image Data matrix. In order for an application to
present such an image on a screen two sets of data are required a) the Digital Image Data matrix and b) the
rendering data. In the case of a CT image presentation to the reporting clinician on the display screen of a
multimedia reporting system, facilities will be provided for him/her to adjust the rendering parameters. These are
generally controlled by means of controls, called window controls, which select the range of X-Ray attenuation
values to be displayed. By adjustment of these controls, the reporting clinician can select the most appropriate
settings to demonstrate the image features referred to in the Report Words.
A number of stages in the life history of a Healthcare service report may be identified. First a report instance is
created and associated with the request. Usually some or all of the report content is immediately recorded
following the report instance creation. The report content is then built up by assembling and adjusting the
presentation of a number of components (Report Words, images, Curves, etc.). This process may be
accomplished during one or more editing sessions during which there are no restrictions on the modifications
which may be made to the report content (addition or removal of sections of Report Words, addition or removal
of presented Healthcare Procedure Products, adjustment of presentation parameters). There may be a number
of approval stages for the various components. Finally the whole report is approved (signed off) and is ready for
dispatch. Usually the data will be sent out in a form that does not allow the recipient to alter the presentation
parameters such as image windowing.
Subsequently it may be found that errors exist in the approved (signed off report). There are two commonly used
methods for dealing with this situation:
a) No changes are made to the original approved report content but a section is added
b) The faulty report is withdrawn and is superseded by a new report instance without those errors which in turn
is approved (Signed off).
From the above it is clear that applications for the creation, modification and presentation of multimedia report
records must support constrained and unconstrained modification of the healthcare multimedia report record. In
particular, applications for the presentation to report recipients will not allow any modification of the presentation.
1.3 Motivation
Significant developments in computer hardware, software and data communications used in Healthcare have
taken place in the last few years. In particular, it is now possible to incorporate the results of Healthcare
Procedures such as images and Curves within electronic reports, possibly using multimedia facilities. Systems
can be implemented at reasonable cost using World Wide Web Technology and there is considerable interest in
this area, which will impact on the Electronic Patient Record as well as the diagnostic imaging department.
It is believed that a review of the specific medical needs for multimedia reports and evaluation of existing and
draft standards for use in this area will assist the healthcare informatics standards community in further
standards development. A review will, in particular, help TC 251 in enabling the healthcare community to gain
maximum benefit from the emerging technology.
From the standards development point of view, it is important to exploit the use of appropriate standards and to
identify areas where more work is required to enable interoperability of systems.
In assessing the clinical requirements for healthcare multimedia reports and how these could be met, major
problems exist. These are:
• There is no clear agreement about what a healthcare multimedia report is
•
Implementations are rare
• Technologies develop rapidly
•
Inadequate standards and specifications lead to interoperability problems.
1.4 Aims and Objectives
1.4.1 Aims
In addressing the problems listed above, this CEN Report aims to facilitate Interoperability of Healthcare
Informatics Systems that support the use of Multimedia information. The report focuses on Healthcare
(Procedure) multimedia reports such as Radiological procedure reports within the clinical process by:
a) identifying the needs for their implementation, and
b) reviewing existing and emerging standards and specifications in the light of the identified clinical needs, and
c) considering the requirements for further standardisation activities
1.4.2 Objectives
The overall objective is to make recommendations to CEN/TC 251 regarding future standards work required to
enable the interoperability of Healthcare Multimedia systems for the creation, modification and presentation of
healthcare multimedia report records, taking account of existing standards and existing and emerging
technologies.
This CEN report has the following specific objectives:
Healthcare Multimedia Report: To define and explain the term Healthcare Multimedia Report (HCMR) in the
context of this CEN Report.
Interoperability: To define and explain the term Interoperability in the context of this report
Healthcare Procedure Scenarios: To inform healthcare informaticians by documenting Scenarios of Healthcare
Procedures such as diagnostic imaging procedures and intensive monitoring, illustrating the use of Imaging and
other Medical Devices in the acquisition and processing of acquired patient data.
Healthcare Procedure Data: To describe the nature of the acquired and processed data produced by
Healthcare Procedures. This will allow precise specification of the processes necessary for multimedia
presentation of these data.
Healthcare Service Reports: To document scenarios of the production, recording and subsequent presentation
of Healthcare Service Reports, with and without the use of multimedia facilities.
Healthcare Procedure Report Data: To discuss the nature of the data required to specify the presentation of a
Healthcare Multimedia Report. Note that it is not intended to prescribe the method of presentation.
Unified Modeling Language Modelling: To develop Unified Modeling Language (UML) conceptual models
based on the above scenarios.
Review of existing standards: To examine current relevant standards and determine to what extent they
support the needs identified in this CEN Report.
Recommendations: To make recommendations regarding work required to improve interoperability of
multimedia report systems, including recommendations for the extension of existing standards/specifications and
the development of new standards/specifications.
1.5 Method of Work
1.5.1 Traditional Healthcare Service Report Scenarios
Scenarios of the creation and use of Healthcare Service Reports such as Radiological Reports were produced.
These take into account the existing scenarios documents of CEN/TC 251/WG4 and CEN/TC 251/WG5 and the
knowledge and experience of the medically qualified healthcare professional member of this CEN Report Project
Team and views of various workers in the field. A scenario describes the processes that take place in the
relevant domain and identifies the human actors, real world entities and logical data structures involved.
1.5.2 Scenarios of healthcare multimedia reports
Viable means for the clinical use of Multimedia Reports were identified:
1.5.3 Multimedia report use cases
Use cases of the creation, amendment and use of multimedia reports were produced based on the two related
scenarios sections. These utilise both a textual format and diagrams to illustrate the sequence of events in a
process showing how human actors, system facilities and logical data structures relate to each other.
1.5.4 Conceptual Modelling
Formal Unified Modeling Language (UML) conceptual models were derived from the use cases.
These high-level abstractions are also represented using UML system sequence diagrams. A system sequence
diagram provides a model of a particular course of events within a use case where it is demonstrated how
human actors interact with physical entities and multimedia entities and the events that are generated from this
interaction. Use case and sequence diagrams are used to further derive a formal UML conceptual model (that is
a representation of concepts of entities in the problem domain) using UML class diagram notation.
1.5.5 Logical data structures
The characteristics of a Healthcare Procedure Product logical data structure to support the forms of acquired and
processed data covered by the scope of CEN/TC 251 WGIV are described at the end of section 8.
The characteristics of logical data structures for describing the Multimedia presentation of a specific set of
Healthcare Procedure Product logical data structures are discussed in section 9.
1.5.6 Assessment of the applicability of relevant existing and emerging Standards and Specifications

The applicability of multimedia and other existing and emerging standards/specifications to support the identified
requirements was assessed as a guide to the needs for further work.
1.5.7 Recommendations for use and/or extension of standards and Publicly Available Specifications

Recommendations are made for the use of (and possible extensions to) multimedia standards to serve the
identified clinical needs. Areas where standards are lacking are identified, and need for further work items
highlighted.
2 SCOPE
The scope includes issues concerning the interoperability of systems for the creation, modification and
presentation of digital healthcare multimedia report records as described in the Introduction.
This CEN report concentrates on a limited set of multimedia documents, namely reports such as those of
Diagnostic Imaging and Vital Signs studies. This set of documents constitutes a representative sample of
complex healthcare multimedia reports within the scope of CEN/TC 251/WGIV. It is expected that the
recommendations, which take into account this complexity, will support the management of less complex reports.
This CEN report has three main parts:
• Identification and modelling of the needs for interoperability of multimedia systems for the creation,
modification and presentation of Healthcare Service Reports.
• Assessment of the applicability of appropriate existing and emerging standards and Publicly Available
Specifications as at November 1998.
• Recommendations for the use and/or extension of Standards and Publicly Available Specifications.
The scope does not include the creation of implementable specifications or complete requirement specifications.
3 REFERENCES AND BIBLIOGRAPHY
3.1 References
ENV 13734:2000 Health informatics - Vital Signs Information Representation. (VITAL)
Extensible Biosignal Format, University of Erlangen, Germany,. http://www.ipb.uni-
erlangen.de/biokybernetik/biokybernetik.html. EBS
European Data Format. Kemp B., Värri A., Rosa A.C., Nielsen K.D., Gade J.,
A simple format for exchange of digitised polygraphic recordings, Electroencephalogr. Clin. Neurophysiol.,
Vol. 82, 1992, 391-393. EDF
ENV 1064 Medical Informatics - Standard Communications Protocol - Computer-Assisted Electrocardiography.
(SCP-ECG)
ENV 12265:1995 The Electronic Healthcare Record Architecture. EHCR
ENV 13606-1:2000 Health informatics - Electronic healthcare record communication – Part 1: Extended
architecture
ENV 13606-2:2000 Health informatics - Electronic healthcare record communication – Part 2: Domain termlist
ISO/JTC1/SC29/WG10 IS10918- 1,2,3 Joint photographic Export Group. JPEG
ISO/JTCI/SC29/WG11 IS 11172-1,2 Moving pictures expert group. MPEG
ISO 8879: 1986 Standard Generalised mark-up Language. SGML
IETF HTML: DTD of SGML HyperText Mark-up Language. HTML
Digital Imaging COmmunication in Medicine PS 3 1998. Details available via
ftp://ftp.nema.org/medical/dicom/final. DICOM
DICOM Structured Reporting Frozen Draft Supplement 23.
DICOM Waveform Supplement. Draft Supplement 30.
DICOM Greyscale Presentation State Draft Supplement 33.
WWW Consortium Recommendation: Synchronised Multimedia Integration Language, Version 1.0,
http://www.w3.org/AudioVideo/. SMIL
WWW Consortium, Extensible Markup Language, Version 1.0, February 1998, http://www.w3.org/XML/. XML
WWW Consortium, Extensible Style Language, Version 1.0, Working Draft 16-December-1998,
http://www.w3.org/Style/XSL/. XSL
WWW Consortium, Cascading Style Sheets, Version 2.0, May 1998, http://www.w3.org/Style/CSS/. CSS
An Examination of Multi-media interchange profiles with respect to their application in the healthcare sector
EWOS/EG MED/MED.5 (00251026)
3.2 Bibliography
ENV 12052:1995: Item 4.3 Medical Image and related data interchange format. MEDICOM
ISO/JTCI/SC29/WG12 IS13522 Multimedia and hypermedia information coding expert group. MHEG
ISO/JTCI/SC29/WG11 IS 11172-3. MPEG Audio
ISO/JTCI/SC29/WG9 IS 11544 Joint bi level image compression. JBIG
ISO 9069: 1988 SGML Interchange format. SDIF
ISO/IEC 14772-1:1997, the Virtual Reality Modeling Language (VRML)
WWW Consortium, Digital Signature Working Group, Recommendation, Version 1.0, May 1998,
http://www.w3.org/DSig/Overview.html.
ISO/IEC/JTCI/SC24 IS12087-3 Image Processing and Interchange Facility. IPI
ISO/IEC/DIS 1074 4 Hypermedia/Time based Structuring Language. HyTime
Fowler, Martin UML Distilled: Applying the Standard Object Modeling Language, Addison-Wesley, Reading,
Mass. 1997
4 ABBREVIATIONS AND DEFINITIONS
4.1 Abbreviations
CEN European Committee for Standardisation
CSS Cascading Style Sheets
CT Computed Tomography
DICOM Digital Image COmmunication in Medicine
DTD Document Type Definition
ECG Electrocardiogram
EEG Electroencephalogram
EHCR Electronic Health Care Record
ENMG Electroneuromyogram
EPR Electronic Patient Record
FEF File Exchange Format
HCMR Healthcare Multimedia Report
HCP Health Care Professional
HL7 Health Level Seven
HTML HyperText Markup Language
HTTP HyperText Transport Protocol
ICU Intensive Care Unit
ID Identification
IOD Information Object Definition in DICOM
ISO International Standards Organisation
LUT Look-Up Table
MRI Magnetic Resonance Imaging
NEMA National Electrical Manufacturers Association
PT Project Team
ROI Region of Interest
RTSP Real Time Streaming Protocol
SMIL Synchronised Multimedia Integration Language
SOP Service Object Pair in DICOM
SPET Single Photon Emission Tomography
TC Technical Committee
UID Unique Identifier
UML Unified Modeling Language
WG Working Group
W3C World Wide Web Consortium
XML Extensible Markup Language
XSL Extensible Style Language
4.2 Definitions
4.2.1
Cine Loop
A mode of display for a Medical Image Series which simulates the display produced by a continuous loop of
cine film by a cine projector by displaying the images in their proper order starting again with the first after display
of the last.
Note: the duration of the display of each image is the same but should be selectable by the operator over a
suitable range.
4.2.2
Composite Rendered Healthcare Procedure Product
A Logical Data Structure which specifies two or more Rendered Healthcare Procedure Products and the
alignment between them in time or space, such as a Medical Image and a graphic entity to be superimposed on
it or two or more Medical Image Series which are to be displayed synchronised in Cine Loop mode.
4.2.3
Curve
A Healthcare Procedure Product which may be presented in the form of a rectilinear graph as might be plotted
on graph paper.
4.2.4
Digital Image
A visual representation of Digital Image Data.
4.2.5
Digital Image Data
A set of numerical values which may be meaningfully rendered as a visible image.
4.2.6
Digital Image Rendering Data
Data required to enable Digital Image Data values to be rendered.
Note: It includes image size and position (Zoom and Pan) within the display area and LUT data and window
(threshold) information.
4.2.7
HCMR Container
A Logical Data Structure for the presentation of specified composite rendered Healthcare Procedure
Products.
4.2.8
HCMR Navigation Mode
An HCMR presentation mode in which the operator can navigate the presented report.
4.2.9
HCMR Performance Mode
An HCMR presentation mode in which a report is presented non-interactively to an observer by means of an
HCMR Score.
4.2.10
HCMR Score
Record of an HCMR Performance Mode which includes the specification of the way in which one or more
Composite Rendered Healthcare Procedure Products are presented.
4.2.11
Healthcare Multimedia Report
A Healthcare Service Report which might be presented using more than one medium.
Note: An application which can present multimedia data is required to present a Healthcare Multimedia Report.
Such an application is also able to present mono-media data. This CEN Report is concerned with the nature of
such applications and the data needed to record such Healthcare Service Reports.
4.2.12
Healthcare Procedure
A systematic activity directed at, or performed on, an individual with the object of disease screening, monitoring,
prevention, diagnosis, treatment or rehabilitation.
4.2.13
Healthcare Procedure Product
An entity produced when a Healthcare Procedure is performed.
Note: It may be a Information Item Procedure Product such as a measured value, Curve, Image or section of
text or a physical sample or specimen taken from a patient.
4.2.14
Healthcare Procedure Product Rendering Data
A Logical Data Structure which specifies a set of rendering parameters for a Healthcare Procedure Product.
4.2.15
Healthcare Procedure Step
An identified part of a Healthcare Procedure.
Note 1: It may be performed during a single department visit by the patient (or visit to the patient in the case of
the use of a mobile data acquisition unit). For compatibility with DICOM study component, it should be
performed using not more than one piece of Medical Image data creating equipment for data acquisition or
processing).
Note 2: In general a Healthcare Procedure will be performed in a number of steps some of which will yield
Healthcare Procedure Products.
4.2.16
Healthcare Procedure Type
The name of a Healthcare Procedure which may be performed on a patient (e.g., in-vivo healthcare diagnostic
procedure such as a diagnostic imaging procedure).
Note: A directory of Healthcare Procedure Types is maintained by a Healthcare Service department to show
Healthcare Procedures for which Healthcare Service Requests can be accepted.
4.2.17
Healthcare Service
Service provided with the intention of directly or indirectly improving the health of the people, populations or
animals to whom it is provided.
4.2.18
Healthcare Service Report
A set of one or more Information Item Procedure Products.
4.2.19
Healthcare Service Request
A request, made by an identifiable person, for one or more Healthcare Procedures to be performed for a
specified patient.
Note 1: The Healthcare Procedure type(s) may or may not be specified depending on the local rules of the
Institution.
Note 2: A Healthcare Service Report is usually a deliverable arising from a Healthcare Service Request.
4.2.20
Healthcare Service Requester
A medically qualified healthcare professional who submits a Healthcare Service Request.
4.2.21
Imaging Modality
Technique or apparatus for the acquisition of Digital Images for example: X-Ray imaging, computed
tomography, echosonography and magnetic resonance imaging.
4.2.22
Information Item Procedure Product
A Healthcare Procedure Product which is not a sample, e.g., text, a numerical value, a Curve, a Digital
Image, a piece of Sound (including spoken words) or a video.
4.2.23
Intensive Care Unit
Unit within a hospital in which critically ill patients are managed using multiple modes of monitoring and vital
system support.
4.2.24
Interoperability
A state which exists between two application entities, with regard to a specific task, when one application entity can
accept data from the other and perform that task in an appropriate and satisfactory manner without the need for
extra operator intervention.
4.2.25
Logical Data Structure
Conceptual aspect of data type expressing the nature of values that are composite, i.e. not atoms (an atom being a
value that cannot be further decomposed). The non atomic values have constituent parts (which need not
themselves be atoms), and the data structure expresses how constituents may be combined to form a compound
value or selected from a compound value.
4.2.26
Look-Up Table (LUT)
A table of values used to select the luminance and colour of a pixel in a Digital Image.
4.2.27
Medical Device
Device, apparatus, or system used to prevent, measure, diagnose, or treat disease in humans, and which does
not normally enter metabolic pathways.
Note: For the purposes of this CEN report the scope of Medical Device is further limited to those medical
devices which provide support for electronic communications.
4.2.28
Medical Image
A Healthcare Procedure Information Item which is a visual representation of an entity.
Note: the entity may be a matrix of measured values such as X-Ray attenuation coefficient values or a
photograph, for example.
4.2.29
Medical Image Series
A ordered set of two or more Medical Images such as a set of axial slices or a set of frames obtained during
consecutive time periods.
4.2.30
Pixel
An area of defined shape, size and position within an area occupied by a two dimensional Digital Image with which
a measured value or values are associated.
Note: short for ‘picture element’.
4.2.31
Problem Domain
The field of activity under consideration in a modelling process.
4.2.32
Region Of Interest (ROI)
Identified part(s) of a Digital Image Data matrix or Vector data matrix.
4.2.33
Region Of Interest data
Data which can be used to identify the elements of a Digital Image Data matrix or Vector data matrix which are
part of a Region of Interest.
4.2.34
Rendered Healthcare Procedure Product
A Healthcare Procedure Product which is presented to an observer by an application which applies
Healthcare Procedure Product Rendering data to a Information Item Healthcare Procedure Product.
4.2.35
Report words
Words chosen or approved by a medically qualified healthcare professional and which form part of a Report.
4.2.36
Note: They may be spoken or written.
4.2.37
Scenario
Formal description of a class of business activities including the semantics of business agreements, conventions,
and information content.
4.2.38
Vector
A one-dimensional array of integer or floating-point numbers, for example obtained by calculation from a time
series of Digital Image and Region of Interest data, or by direct measurement.
Note: It can be used for storing Waveform, Curve or histogram data, for example.
4.2.39
Vital Sign
Clinical information relating to one or more patients which can be measured by, or derived from, apparatus
connected to the patient, or otherwise gathered from the patient.
4.2.40
Voxel
A volume of defined shape, size and position within a three dimensional space with which a measured value or
values are associated.
4.2.41
Waveform
A Curve of repetitive form such as an electrocardiogram.
5 REPORT SCENARIOS
5.1 Introduction
The development of scenarios is an important part of the process of identifying user requirements. The following
scenarios have been derived from consultations with users and creators of Healthcare Service Reports and
medically qualified users, in order to help define the requirements for multimedia reports. This chapter gives an
overview of generic reporting scenarios. Chapter 6 considers the particular requirements of multimedia
scenarios, illustrated by examples that the project team consider are representative. These are followed by a
summary and conclusions, and an outline of some technical presentation requirements. Further details of
generic and specific scenarios are given in Annex Parts 2 and 3.
Healthcare Service Reports are, in general, produced in response to Healthcare Service Requests. They are
clinically approved by a medically qualified healthcare professional. When a Healthcare Service Report which
may be presented using multimedia facilities is presented, more than one medium can be used. Such a report is
referred to in this CEN Report as a Healthcare Multimedia Report (HCMR). The text part of the HCMR will be
regarded as the legally binding entity in many circumstances. (In the future, other aspects of the Healthcare
Multimedia Report, such as the positioning of Regions of Interest referred to in the text, may be considered as
legally binding.). HCMRs also provide a resource for clinical research and teaching so anonymisation may be
required. They may be subject to clinical audit. Structured HCMR containing clinical codes may be subject to
automatic computer search techniques.
This section is intended to give a general overview of the reporting in the context of healthcare and is not
specifically concerned with multimedia issues.
5.2 Healthcare Service Requests and Reports
This section provides an over
...