BMJ  2003;326:1101-1102 (24 May), doi:10.1136/bmj.326.7399.1101

Editorial

Why clinical information standards matter

Because they constrain what can be described

Most clinicians probably know clinical information standards as the coding systems used for representing clinical concepts. They include longstanding systems such as the International Classification of Diseases and the Diagnostic and Statistical Manual of Mental Disorders as well as more recent systems such as the Read Clinical Classification and Snomed, though coded vocabularies themselves are only the visible tip of the standards iceberg. Work on clinical information standards is not glamorous, but such standards are fundamental for progress in health care. They are essential resources for future clinical decision support, audit, governance, research, education, and training. In a very real sense, these standards define what can be said about patient care.

In this issue Brown et al describe a crossover trial comparing the accuracy and usability of two clinical terminology standards in a setting designed to reflect tasks and circumstances commonly encountered in contemporary British general practice (p 1127).¹ The paper may seem of limited relevance, in that it is focused on Britain, on primary care, and on two specific clinical standards, both of which are probably obsolescent. Also in this issue is a report describing the practical use of clinical information coding for managing diabetes in south London primary care (p 1130). ² Again, this is a paper whose main focus is on British primary care.

However, these papers do have wider relevance, as much for the general questions they raise as for the particular questions they answer. For example they raise questions about what clinical information standards doctors need, who should develop them, and how they should be evaluated.

What standards do we need?

The answer to the first general question—what standards do we need—is easy (though hard to execute). We need three types of clinical information standards: document structuring standards; term lexicons; and ontologies.

Document structuring standards specify what information items a particular clinical document must, may, or cannot contain; how the items are represented; and where in the document the items are to be found.^3–5. For example, a structuring standard for an operating theatre list might specify that for each patient there must be precisely one field called "date of birth," containing a value of the form "1970-02-17" and appearing immediately after a field called "sex."

Term lexicons are sets of coded terms. Their primary purpose is to resolve synonymy. Thus a term lexicon may say whether "myocardial infarction" should be taken to mean the same as "coronary thrombosis."

Ontologies represent domain knowledge in a form that can be exploited by computers. For example, an ontology covering surgical procedures might allow a computer program to deduce that a "flexible bronchoscopy" is a type of investigation of the lungs that can be done as a day case.

The answer to the second general question—on who should develop standards—is difficult. Organisations that might develop clinical information standards include national or international standards organisations^6–8 (as with the International Classification of Diseases, for example); health related government agencies (as with Read codes); academic research groups⁸; professional colleges and societies; commercial companies or consortia⁹; charities; health trusts; or combinations of these, as with Snomed Clinical Terms.¹⁰

Large organisations have large resources but may be slow, bureaucratic, and unfocused, whereas small organisations are often dynamic and focused but may not have the resources to distribute and maintain standards. Commercial companies have extensive experience of implementing standards in clinical information systems—for example, by incorporating facilities within their systems for browsing and selecting clinical terms from large coded vocabularies—but they cannot be expected to fund efforts which are not commercially beneficial. Clinicians understand the domain, but may have limited theoretical or practical knowledge of information representation technologies, whereas computer scientists cannot be expected to have insight into clinical working practices.

The answer to the third general question, about evaluation, is also difficult. Standards can be judged only if there is a precise statement of their intended purposes, and such purposes may be inherently imprecise and evolutionary. Different types of standards are interdependent in practice, though standards are usually developed and evaluated in isolation. Evaluation in realistic clinical circumstances is the ideal, as in this week's comparison by Brown et al, but by this stage the cost of development will already have been incurred.

Since the three types of clinical information standard are highly interdependent, there should be greater coordination in their development. Although the number of individuals active in clinical standards work is small, it is important that those who evaluate and assess standards should be independent of those who develop standards.

Building ontologies is complex and challenging, but they are crucial for next generation clinical information systems. Lexicons such as Read Codes version 5, Clinical Terms version 3, and Snomed Clinical Terms incorporate some ontological content, but their primary purpose is to enumerate terms, and their ontological content is simply not sufficient to support sophisticated reasoning in future computerised clinical information systems, which must provide much greater clinical decision support than is found in current systems. More work is required on rich ontologies.

It is tempting for policymakers to believe that clinical information standards (and clinical information technologies in general) are now nearing maturity, and therefore that an appropriate strategy is to identify the best current systems and promote their adoption.¹¹ However, there is little evidence to suggest that we are approaching a plateau of maturity in health information standards or health information technologies generally. On the contrary, the next decade will be characterised by accelerating and unpredictable innovation. In such circumstances we should accept the need for large scale experimentation in health information systems. Brown et al have shown that even small scale studies can show significant benefits of one standard versus another. In itself, their study perhaps does not justify wholesale abandonment of Read Codes version 5 in favour of Clinical Terms version 3, but clearly there is a need for more widespread independent clinical evaluation of standards.

Department of Computing Science, University of Glasgow, Glasgow G12 8RZ (martin{at}dcs.gla.ac.uk)

---

Papers pp 1127, 1130

Competing interests: As well as his academic appointment MG is a director of a company specialising in the design of hand held clinical information systems.

References

1. Brown PJB, Warmington V, Laurence M, Prevost AT. Randomised crossover trial comparing the performance of Clinical Terms Version 3 and Read Codes 5 byte set coding schemes in general practice. BMJ 2003;326: 1127-30.[Abstract/Free Full Text]
2. Gray J, Orr D, Majeed A. Use of Read codes in diabetes management in a south London primary care group: implications for establishing disease registers. BMJ 2003;326: 1130-2.[Abstract/Free Full Text]
3. Dolin RH, Alschuler L, Beebe C, Biron PV, Boyer SL, Essin D, et al. The HL7 Clinical Document Architecture. J Am Med Inform Assoc 2001;8: 552-69.[Abstract/Free Full Text]
4. Gardner M, Peachey T. A standard XML schema for computerised anaesthetic records. Anaesthesia 2002;57: 1174-82.[CrossRef][ISI][Medline]
5. Woolman PS. XML for electronic clinical communications in Scotland. Int J Med Inf 2001;64: 379-83.[CrossRef][ISI][Medline]
6. World Health Organization, www.who.int/whosis/icd10/
7. Cen/TC 251, www.centc251.org/
8. OpenGALEN, www.opengalen.org/
9. Health Level Seven, www.hl7.org/
10. SNOMED Clinical Terms, www.nhsia.nhs.uk/snomed/pages/default.asp
11. Department of Health. Delivering 21st century IT support for the NHS. London: DoH, 2002.

CiteULike    Complore    Connotea    Del.icio.us    Digg    Reddit    Technorati    What's this?

Related Articles

How computers help make efficient use of consultations

Frank Sullivan and Jeremy C Wyatt
BMJ 2005 331: 1010-1012. [Extract] [Full Text] [PDF]

Use of Read codes in diabetes management in a south London primary care group: implications for establishing disease registers

Jeremy Gray, Douglas Orr, and Azeem Majeed
BMJ 2003 326: 1130. [Abstract] [Full Text] [PDF]

Randomised crossover trial comparing the performance of Clinical Terms Version 3 and Read Codes 5 byte set coding schemes in general practice

Philip J B Brown, Victoria Warmington, Michael Laurence, and A Toby Prevost
BMJ 2003 326: 1127. [Abstract] [Full Text] [PDF]

This article has been cited by other articles:

• Richesson, R. L., Andrews, J. E., Krischer, J. P. (2006). Use of SNOMED CT to Represent Clinical Research Data: A Semantic Characterization of Data Items on Case Report Forms in Vasculitis Research. J. Am. Med. Inform. Assoc. 13: 536-546 [Abstract] [Full text]  
• Sullivan, F., Wyatt, J. C (2005). How computers help make efficient use of consultations. BMJ 331: 1010-1012 [Full text]  
• Sanderson, H., Adams, T., Budden, M., Hoare, C. (2004). Lessons from the central Hampshire electronic health record pilot project: evaluation of the electronic health record for supporting patient care and secondary analysis. BMJ 328: 875-878 [Full text]  

Rapid Responses:

Read all Rapid Responses

Biophysical Semeiotics, Clinical Information Standards and “human” Medicine.

Sergio Stagnaro
bmj.com, 23 May 2003 [Full text]

Clinical coding: when to standardise ?

Jeremy E Rogers
bmj.com, 27 May 2003 [Full text]

Why clinical information standards matter

Robin Y Mann, et al.
bmj.com, 30 May 2003 [Full text]

Clinical Terminology numbering

Charles A West
bmj.com, 30 May 2003 [Full text]