ArticleCureus2025
Use of a Novel Natural Language Processing Utility to Extract Structured Data From Free-Text Medical Notes.
Article in Cureus, 2025. 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
1 author.
Funding
No grant is acknowledged in the PubMed record.
Abstract
Introduction Electronic medical records (EMRs) contain a large amount of clinical data potentially useful for research. A barrier to the use of this data is that much of it is unstructured, mainly in the form of free-text clinical notes. Software utilities can help with extraction and conversion of this information into a usable form. Traditionally, this was performed with rule-based natural language processing (NLP) software, but, recently, large language models based on machine learning have been applied to this task. Methods A set of software utilities called Note Language Processing (NoteLP) were developed to extract information from free-text notes and convert it to datasets in standard format. A manual data search was performed in the Epic EMR to serve as the reference standard for the time required to conduct a search manually. Twenty-two sample research projects were designed. The time required to extract the required data using NoteLP was recorded and compared to the time that would be required per patient to retrieve the same data via manual search. Eleven of the search criteria for our sample projects that had corresponding ICD-9 codes were selected. A gold standard for accuracy was established via manual review. Sensitivity and specificity of ICD-9 and note extracted data were calculated versus the gold standard. Results The reference standard was established at 63.4 seconds per patient to manually classify one condition per patient via a manual Epic search. NoteLP required a mean of 37.5 seconds per patient to retrieve data for the sample projects involving ICD-9 comparisons. A further set of more extensive searches required a mean of 16.6 seconds per patient (p<0.001 for all time comparisons of NoteLP versus manual search). The mean ICD-9 sensitivity was 0.65 versus the mean note sensitivity of 0.98 (p<0.001). The mean ICD-9 specificity was 0.93 versus the mean note specificity of 0.94 (p=0.65). Conclusion The use of NoteLP is more efficient than a manual search. Its accuracy compares favorably with manual coding, achieving greater sensitivity and equal specificity. Rule-based NLP utilities such as NoteLP remain a valuable tool for the extraction of research information from unstructured medical text.
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.