DOI 10.1080/09286586.2025.2528675
Comparing the Use of Administrative Claims with the Electronic Health Record Data for Identifying Diabetic Retinopathy Examinations.
Аннотация
PURPOSE: To characterize differences in identification of diabetic retinopathy examinations using administrative claims and electronic health record data.
METHODS
Adult patients ≥18 years with diabetes seen in the ophthalmology department at Johns Hopkins Hospital were included. Two methodologies were used to identify diabetic retinopathy examinations across the hospital system. First, a pre-specified set of Current Procedural Terminology (CPT) codes from administrative claims data were used. Second, natural language processing (NLP) was used to parse ophthalmology provider notes for mention of diabetic retinopathy screening or follow-up. The percentage of visits meeting each set of criteria was determined. Cohen's kappa of agreement between the two methodologies was calculated.
RESULTS
A total of 59,538 patients and 1,926,828 office visits, of which 485,228 (25%) were in the ophthalmology department, were included. Most patients (86%) had at least one diabetic retinopathy examination identified using administrative codes, and 84% using the NLP-based methodology. Of all ophthalmology visits, administrative codes identified more diabetic retinopathy examinations compared to the NLP-based methodology (60%, versus 48%). Cohen's kappa for agreement was 0.57 (standard error 0.001, p < 0.001).
CONCLUSION
This study found only moderate agreement between the two methodologies for identifying diabetic retinopathy examinations. Given the imprecision of administrative codes, this suggests that prior studies reporting eye care utilization using only administrative claims may be over-estimating receipt of diabetic retinopathy examinations.
Предметные рубрики MeSH
Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Ошибки и ограничения
История · было → стало
Состояние обновляется каждые 5 секунд, пока блок открыт. Процент показывается только там, где известен объём работы. Пауза останавливает продолжение этапа; текущий запрос к источнику может завершиться.
Тип публикации указан по данным источника. Уровень доказательности автоматически не присваивается.