Cargando…

Analysis of Clinical Record Data for Anticoagulation Management within an EHR System

OBJECTIVES: This paper reports an evaluation of the properties of a generic electronic health record information model that were actually required and used when importing an existing clinical application into a generic EHR repository. METHOD: A generic EHR repository and system were developed as par...

Descripción completa

Detalles Bibliográficos
Autores principales: Austin, T, Kalra, D, Lea, N.C, Patterson, D.L.H, Ingram, D
Formato: Texto
Lenguaje:English
Publicado: Bentham Open 2009
Materias:
Acceso en línea:https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2737130/
https://www.ncbi.nlm.nih.gov/pubmed/19738915
http://dx.doi.org/10.2174/1874431100903010054
_version_ 1782171410033016832
author Austin, T
Kalra, D
Lea, N.C
Patterson, D.L.H
Ingram, D
author_facet Austin, T
Kalra, D
Lea, N.C
Patterson, D.L.H
Ingram, D
author_sort Austin, T
collection PubMed
description OBJECTIVES: This paper reports an evaluation of the properties of a generic electronic health record information model that were actually required and used when importing an existing clinical application into a generic EHR repository. METHOD: A generic EHR repository and system were developed as part of the EU Projects Synapses and SynEx. A Web application to support the management of anticoagulation therapy was developed to interface to the EHR system, and deployed within a north London hospital with five years of cumulative clinical data from the previous existing anticoagulation management application. This offered the opportunity to critique those parts of the generic EHR that were actually needed to represent the legacy data. RESULTS: The anticoagulation records from 3,226 patients were imported and represented using over 900,000 Record Components (i.e. each patient’s record contained on average 289 nodes), of which around two thirds were Element Items (i.e. value-containing leaf nodes), the remainder being container nodes (i.e. headings and sub-headings). Each node is capable of incorporating a rich set of context properties, but in reality it was found that many properties were not used at all, and some infrequently (e.g. only around 0.5% of Record Components had ever been revised). CONCLUSIONS: The process of developing generic EHR information models, arising from research and embodied within new-generation interoperability standards and specifications, has been strongly driven by requirements. These requirements have been gathered primarily by collecting use cases and examples from clinical communities, and been added to successive generations of these models. A priority setting approach has not to date been pursued - all requirements have been received and almost invariably met. This work has shown how little of the resulting model is actually needed to represent useful and usable clinical data. A wider range of such evaluations, looking at different kinds of existing clinical system, is needed to balance the theoretical requirements gathering processes, in order to result in EHR information models of an ideal level of complexity.
format Text
id pubmed-2737130
institution National Center for Biotechnology Information
language English
publishDate 2009
publisher Bentham Open
record_format MEDLINE/PubMed
spelling pubmed-27371302009-09-04 Analysis of Clinical Record Data for Anticoagulation Management within an EHR System Austin, T Kalra, D Lea, N.C Patterson, D.L.H Ingram, D Open Med Inform J Article OBJECTIVES: This paper reports an evaluation of the properties of a generic electronic health record information model that were actually required and used when importing an existing clinical application into a generic EHR repository. METHOD: A generic EHR repository and system were developed as part of the EU Projects Synapses and SynEx. A Web application to support the management of anticoagulation therapy was developed to interface to the EHR system, and deployed within a north London hospital with five years of cumulative clinical data from the previous existing anticoagulation management application. This offered the opportunity to critique those parts of the generic EHR that were actually needed to represent the legacy data. RESULTS: The anticoagulation records from 3,226 patients were imported and represented using over 900,000 Record Components (i.e. each patient’s record contained on average 289 nodes), of which around two thirds were Element Items (i.e. value-containing leaf nodes), the remainder being container nodes (i.e. headings and sub-headings). Each node is capable of incorporating a rich set of context properties, but in reality it was found that many properties were not used at all, and some infrequently (e.g. only around 0.5% of Record Components had ever been revised). CONCLUSIONS: The process of developing generic EHR information models, arising from research and embodied within new-generation interoperability standards and specifications, has been strongly driven by requirements. These requirements have been gathered primarily by collecting use cases and examples from clinical communities, and been added to successive generations of these models. A priority setting approach has not to date been pursued - all requirements have been received and almost invariably met. This work has shown how little of the resulting model is actually needed to represent useful and usable clinical data. A wider range of such evaluations, looking at different kinds of existing clinical system, is needed to balance the theoretical requirements gathering processes, in order to result in EHR information models of an ideal level of complexity. Bentham Open 2009-08-19 /pmc/articles/PMC2737130/ /pubmed/19738915 http://dx.doi.org/10.2174/1874431100903010054 Text en © Austin et al.; Licensee Bentham Open. http://creativecommons.org/licenses/by-nc/3.0/ This is an open access article licensed under the terms of the Creative Commons Attribution Non-Commercial License (http://creativecommons.org/licenses/by-nc/3.0/) which permits unrestricted, non-commercial use, distribution and reproduction in any medium, provided the work is properly cited.
spellingShingle Article
Austin, T
Kalra, D
Lea, N.C
Patterson, D.L.H
Ingram, D
Analysis of Clinical Record Data for Anticoagulation Management within an EHR System
title Analysis of Clinical Record Data for Anticoagulation Management within an EHR System
title_full Analysis of Clinical Record Data for Anticoagulation Management within an EHR System
title_fullStr Analysis of Clinical Record Data for Anticoagulation Management within an EHR System
title_full_unstemmed Analysis of Clinical Record Data for Anticoagulation Management within an EHR System
title_short Analysis of Clinical Record Data for Anticoagulation Management within an EHR System
title_sort analysis of clinical record data for anticoagulation management within an ehr system
topic Article
url https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2737130/
https://www.ncbi.nlm.nih.gov/pubmed/19738915
http://dx.doi.org/10.2174/1874431100903010054
work_keys_str_mv AT austint analysisofclinicalrecorddataforanticoagulationmanagementwithinanehrsystem
AT kalrad analysisofclinicalrecorddataforanticoagulationmanagementwithinanehrsystem
AT leanc analysisofclinicalrecorddataforanticoagulationmanagementwithinanehrsystem
AT pattersondlh analysisofclinicalrecorddataforanticoagulationmanagementwithinanehrsystem
AT ingramd analysisofclinicalrecorddataforanticoagulationmanagementwithinanehrsystem