ArticleJAMIA open2026
Evaluating large language models for automated REDCap support ticket triage and response.
Article in JAMIA open, 2026. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Not yet cited in PubMed.
What it found
Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.
The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.
The trial behind it
Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.
Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.
Who cites it
0 citing papers in PubMed.
No citing paper in PubMed yet.
Corrections and comments
PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.
Authors and funding
5 authors.
Funding
No grant is acknowledged in the PubMed record.
Abstract
Objectives: To evaluate the utility of large language models (LLMs) without and with retrieval-augmented generation (RAG) resources for automating Research Electronic Data Capture (REDCap) support at a large academic medical center, focusing on ticket complexity, categorization, and response drafting. Materials and Methods: We randomly selected 90 REDCap support tickets from 6316 received in 2023, stratified by estimated complexity (low, moderate, high) using ticket metadata. Four LLM configurations (GPT-4o Default; GPT-4o + Vanderbilt REDCap documentation; GPT-4o + University of Michigan [UM] REDCap documentation; GPT-4o + combined documentation) were evaluated on 3 tasks per ticket: complexity assessment, category assignment, and email response drafting. Human REDCap experts provided gold-standard ratings and assessed email drafts. Results: Compared to the gold standard, the GPT-4o Default environment most closely matched human complexity ratings, while specialized RAG environments tended to overestimate complexity. For ticket support categorization, all LLM configurations achieved high agreement with human judgments (Cohen's kappa ≈0.85), correctly categorizing 81%-89% of tickets. In generating ticket responses, the GPT-4o + REDCap + UM environment provided the most correct answers, particularly for low and moderate complexity tickets, where about two-thirds of responses were substantially or fully correct. Discussion: Large language models have potential to automate ticket triage and response drafting for routine REDCap support, with context augmentation improving response accuracy for lower complexity tickets. Conclusion: Large language model-based support tools hold promise for reducing human workload for REDCap support tickets. Continued human oversight, iterative prompt engineering, and expanded local documentation are needed for reliable, effective deployment.
Indexed as
Identifiers
What OpenQuestion holds
Registered trials
Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.