Back to Feed
Reasoning / Safety & Alignment

Automated Evidence Based Heart Failure Feature Engineering

Original: Tracing the Heart: An Evidence-Linked Pipeline for Heart-Failure Feature Engineering

Listen to the summary

Uses a voice available on your device

Audio options
On this page

Key Takeaways

  • Implemented a clinical reasoning layer to generate 70 composite features from EHR data.
  • Used a restricted language model to audit feature structural integrity and rubric compliance.
  • Improved HFrEF model AUROC from 0.895 to 0.963 and HFpEF from 0.870 to 0.910.
  • Achieved 81.5 percent of maximum points in independent LLM rubric assessments.

Summary & Methodology Analysis

The pipeline standardizes raw EHR tables via ISO datetime formatting and deduplication based on clinical event keys. After temporal aggregation, the system merges data into patient rows, preserving null values. A clinical reasoning layer then processes these records into interpretable flags, which serve as inputs for a versioned, cardiologist-reviewed scoring rubric. This produces 70 composite features, which are then audited by a restricted language model to ensure they align with the rubric and maintain structural integrity.

Interactive System Flowchart

Click diagram to expand and zoom

Cross-Examination & FAQs

A deeper dive clarifying mechanics, constraints, and baseline evaluations.

Q1. What is the primary challenge this pipeline addresses?

It solves the difficulty of integrating fragmented EHR data with evidence-based clinical reasoning, which is typically a manual and non-maintainable process.

Q2. How does the pipeline handle clinical data?

It standardizes, deduplicates, and aggregates EHR tables into patient-level summaries, followed by an automated clinical reasoning layer.

Q3. What is the main result of this approach?

The pipeline significantly improved predictive performance for both HFrEF and HFpEF heart failure subtypes.

Q4. What role does the language model play in the pipeline?

A restricted language model performs local audits on each candidate feature to ensure the output meets the requirements of the clinical scoring rubric.

Q5. Which specific tools and models were utilized?

The project used the Nimblemind Multi-Agent System, FIDDLE, MIMIC-Extract, the OHDSI patient-level prediction framework, Qwen 2.5-1.5B-Instruct, XGBoost, and Claude Opus 4.8.

Q6. How many features does the final pipeline produce?

The pipeline produces 132 structured features and 70 rubric-scored aggregated features.

Q7. What are the limitations regarding the dataset?

The system was evaluated on a dummy, single-institution cohort, which limits its generalizability.

Q8. Does this approach measure long term clinical outcomes?

No, the paper does not measure prospective clinical impact or patient outcomes.

Q9. Are there any known weaknesses in the data processing?

Yes, the use of regular-expression matching for comorbid conditions may fail to capture specific medical terminology.