Cargando…

An administrative data merging solution for dealing with missing data in a clinical registry: adaptation from ICD-9 to ICD-10

BACKGROUND: We have previously described a method for dealing with missing data in a prospective cardiac registry initiative. The method involves merging registry data to corresponding ICD-9-CM administrative data to fill in missing data 'holes'. Here, we describe the process of translatin...

Descripción completa

Detalles Bibliográficos
Autores principales: Southern, Danielle A, Norris, Colleen M, Quan, Hude, Shrive, Fiona M, Galbraith, P Diane, Humphries, Karin, Gao, Min, Knudtson, Merril L, Ghali, William A
Formato: Texto
Lenguaje:English
Publicado: BioMed Central 2008
Materias:
Acceso en línea:https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2244639/
https://www.ncbi.nlm.nih.gov/pubmed/18215293
http://dx.doi.org/10.1186/1471-2288-8-1
_version_ 1782150649761234944
author Southern, Danielle A
Norris, Colleen M
Quan, Hude
Shrive, Fiona M
Galbraith, P Diane
Humphries, Karin
Gao, Min
Knudtson, Merril L
Ghali, William A
author_facet Southern, Danielle A
Norris, Colleen M
Quan, Hude
Shrive, Fiona M
Galbraith, P Diane
Humphries, Karin
Gao, Min
Knudtson, Merril L
Ghali, William A
author_sort Southern, Danielle A
collection PubMed
description BACKGROUND: We have previously described a method for dealing with missing data in a prospective cardiac registry initiative. The method involves merging registry data to corresponding ICD-9-CM administrative data to fill in missing data 'holes'. Here, we describe the process of translating our data merging solution to ICD-10, and then validating its performance. METHODS: A multi-step translation process was undertaken to produce an ICD-10 algorithm, and merging was then implemented to produce complete datasets for 1995–2001 based on the ICD-9-CM coding algorithm, and for 2002–2005 based on the ICD-10 algorithm. We used cardiac registry data for patients undergoing cardiac catheterization in fiscal years 1995–2005. The corresponding administrative data records were coded in ICD-9-CM for 1995–2001 and in ICD-10 for 2002–2005. The resulting datasets were then evaluated for their ability to predict death at one year. RESULTS: The prevalence of the individual clinical risk factors increased gradually across years. There was, however, no evidence of either an abrupt drop or rise in prevalence of any of the risk factors. The performance of the new data merging model was comparable to that of our previously reported methodology: c-statistic = 0.788 (95% CI 0.775, 0.802) for the ICD-10 model versus c-statistic = 0.784 (95% CI 0.780, 0.790) for the ICD-9-CM model. The two models also exhibited similar goodness-of-fit. CONCLUSION: The ICD-10 implementation of our data merging method performs as well as the previously-validated ICD-9-CM method. Such methodological research is an essential prerequisite for research with administrative data now that most health systems are transitioning to ICD-10.
format Text
id pubmed-2244639
institution National Center for Biotechnology Information
language English
publishDate 2008
publisher BioMed Central
record_format MEDLINE/PubMed
spelling pubmed-22446392008-02-15 An administrative data merging solution for dealing with missing data in a clinical registry: adaptation from ICD-9 to ICD-10 Southern, Danielle A Norris, Colleen M Quan, Hude Shrive, Fiona M Galbraith, P Diane Humphries, Karin Gao, Min Knudtson, Merril L Ghali, William A BMC Med Res Methodol Research Article BACKGROUND: We have previously described a method for dealing with missing data in a prospective cardiac registry initiative. The method involves merging registry data to corresponding ICD-9-CM administrative data to fill in missing data 'holes'. Here, we describe the process of translating our data merging solution to ICD-10, and then validating its performance. METHODS: A multi-step translation process was undertaken to produce an ICD-10 algorithm, and merging was then implemented to produce complete datasets for 1995–2001 based on the ICD-9-CM coding algorithm, and for 2002–2005 based on the ICD-10 algorithm. We used cardiac registry data for patients undergoing cardiac catheterization in fiscal years 1995–2005. The corresponding administrative data records were coded in ICD-9-CM for 1995–2001 and in ICD-10 for 2002–2005. The resulting datasets were then evaluated for their ability to predict death at one year. RESULTS: The prevalence of the individual clinical risk factors increased gradually across years. There was, however, no evidence of either an abrupt drop or rise in prevalence of any of the risk factors. The performance of the new data merging model was comparable to that of our previously reported methodology: c-statistic = 0.788 (95% CI 0.775, 0.802) for the ICD-10 model versus c-statistic = 0.784 (95% CI 0.780, 0.790) for the ICD-9-CM model. The two models also exhibited similar goodness-of-fit. CONCLUSION: The ICD-10 implementation of our data merging method performs as well as the previously-validated ICD-9-CM method. Such methodological research is an essential prerequisite for research with administrative data now that most health systems are transitioning to ICD-10. BioMed Central 2008-01-23 /pmc/articles/PMC2244639/ /pubmed/18215293 http://dx.doi.org/10.1186/1471-2288-8-1 Text en Copyright © 2008 Southern et al; licensee BioMed Central Ltd. http://creativecommons.org/licenses/by/2.0 This is an Open Access article distributed under the terms of the Creative Commons Attribution License ( (http://creativecommons.org/licenses/by/2.0) ), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.
spellingShingle Research Article
Southern, Danielle A
Norris, Colleen M
Quan, Hude
Shrive, Fiona M
Galbraith, P Diane
Humphries, Karin
Gao, Min
Knudtson, Merril L
Ghali, William A
An administrative data merging solution for dealing with missing data in a clinical registry: adaptation from ICD-9 to ICD-10
title An administrative data merging solution for dealing with missing data in a clinical registry: adaptation from ICD-9 to ICD-10
title_full An administrative data merging solution for dealing with missing data in a clinical registry: adaptation from ICD-9 to ICD-10
title_fullStr An administrative data merging solution for dealing with missing data in a clinical registry: adaptation from ICD-9 to ICD-10
title_full_unstemmed An administrative data merging solution for dealing with missing data in a clinical registry: adaptation from ICD-9 to ICD-10
title_short An administrative data merging solution for dealing with missing data in a clinical registry: adaptation from ICD-9 to ICD-10
title_sort administrative data merging solution for dealing with missing data in a clinical registry: adaptation from icd-9 to icd-10
topic Research Article
url https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2244639/
https://www.ncbi.nlm.nih.gov/pubmed/18215293
http://dx.doi.org/10.1186/1471-2288-8-1
work_keys_str_mv AT southerndaniellea anadministrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT norriscolleenm anadministrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT quanhude anadministrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT shrivefionam anadministrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT galbraithpdiane anadministrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT humphrieskarin anadministrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT gaomin anadministrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT knudtsonmerrill anadministrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT ghaliwilliama anadministrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT anadministrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT southerndaniellea administrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT norriscolleenm administrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT quanhude administrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT shrivefionam administrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT galbraithpdiane administrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT humphrieskarin administrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT gaomin administrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT knudtsonmerrill administrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT ghaliwilliama administrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10
AT administrativedatamergingsolutionfordealingwithmissingdatainaclinicalregistryadaptationfromicd9toicd10