Health informatics - Quality of service requirements for health information interchange

This document is concerned with QoS as it applies to interactions between components of distributed healthcare IT systems.  The scope is not limited to network infrastructures; it includes the QoS requirements of information storage and processing IT systems.  The related areas of security and financial cost considerations are not within the primary scope of the document, although they are considered briefly.  
Of course, an informatics system with a high QoS does not guarantee a high standard of healthcare in terms of clinical outcomes or patient care.  The quality of healthcare delivered to patients (the ultimate "users") depends upon a number of external factors such as the experience and competence of the healthcare professional(s) or institution(s) involved.  Potential QoS characteristics for the total healthcare delivery process such as mortality rate, clinical outcome, etc. are therefore not within the scope of this report.
The report contains no provisions to avoid the incorporation of bad or dangerous practice into healthcare IT systems.  It is possible to circumvent good clinical practice with technical solutions which may cause bad practice.  This vital issue is not covered by this report.  To take an example scenario:
A patient consults a doctor, who takes a blood sample and arranges to see the patient again in two weeks.
a)   A "good" practice doctor sees and reviews the blood test result as soon as it comes back from the laboratory and then files it if no action is required.
b)   A "bad" practice doctor sees and reviews the blood test results only when he reviews the patient's case on the patient's next visit.  This case is not defensible if the patient has a preventable adverse event and takes legal action (source: MPS Casebook Summer 1997).  
The healthcare information system put into the medical practice in electronic form could build-in either practice (a) or practice (b).  This report does not consider the clinical quality assurance mechanism fo

Medizinische Informatik - Anforderungen an die Service-Qualität für den Austausch von medizinischen Informationen

Informatique de santé - Exigences de qualité de service pour les échanges d'information de santé

Zdravstvena informatika – Zahteve za kakovost storitev pri izmenjavi zdravstvenih informacij

General Information

Status
Published
Publication Date
06-Dec-2005
Current Stage
6060 - Definitive text made available (DAV) - Publishing
Start Date
07-Dec-2005
Completion Date
07-Dec-2005

Buy Standard

Technical report
TP CEN/TR 15253:2006
English language
32 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST-TP CEN/TR 15253:2006
01-april-2006
Zdravstvena informatika – Zahteve za kakovost storitev pri izmenjavi zdravstvenih
informacij
Health informatics - Quality of service requirements for health information interchange
Medizinische Informatik - Anforderungen an die Service-Qualität für den Austausch von
medizinischen Informationen
Informatique de santé - Exigences de qualité de service pour les échanges d'information
de santé
Ta slovenski standard je istoveten z: CEN/TR 15253:2005
ICS:
03.120.99 Drugi standardi v zvezi s Other standards related to
kakovostjo quality
35.240.80 Uporabniške rešitve IT v IT applications in health care
zdravstveni tehniki technology
SIST-TP CEN/TR 15253:2006 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST-TP CEN/TR 15253:2006

---------------------- Page: 2 ----------------------

SIST-TP CEN/TR 15253:2006
TECHNICAL REPORT
CEN/TR 15253
RAPPORT TECHNIQUE
TECHNISCHER BERICHT
December 2005
ICS 35.240.80

English Version
Health informatics - Quality of service requirements for health
information interchange
Informatique de santé - Exigences de qualité de service Medizinische Informatik - Anforderungen an die Service-
pour les échanges d'information de santé Qualität für den Austausch von medizinischen
Informationen
This Technical Report was approved by CEN on 13 November 2005. It has been drawn up by the Technical Committee CEN/TC 251.
CEN members are the national standards bodies of Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France,
Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia,
Slovenia, 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
© 2005 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TR 15253:2005: E
worldwide for CEN national Members.

---------------------- Page: 3 ----------------------

SIST-TP CEN/TR 15253:2006
CEN/TR 15253:2005 (E)
Contents page
Foreword .3
Introduction.4
0 Scope .5
1 Structure of this document .5
2 References.6
3 Abbreviation .7
4 Terms and definitions.8
5 Quality of service concepts.9
6 Current relevant work in healthcare informatics standardisation.13
7 Typical healthcare QoS scenarios.14
8 Healthcare QoS categories.16
9 Development of ETG 021 Method .23
10 Summary and conclusions.25

Annex A Application of QoS concepts.29

2

---------------------- Page: 4 ----------------------

SIST-TP CEN/TR 15253:2006
CEN/TR 15253:2005 (E)
Foreword
This Technical Report (CEN/TR 15253:2005) has been prepared by Technical Committee CEN /TC 251,
"Health informatics" the secretariat of which is held by NEN.
This document has been developed by the Expert Group for Healthcare within the European Workshop for
Open Systems (EWOS/EG MED). The editor of the document is Dr A J Kerr of Level-7 Ltd, a member of
EWOS/EG MED. Thanks are due to all who have contributed ideas, text and scenarios to assist in the
production of this report. Special appreciation is expressed to Jerem
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.