← Latest papers
🤖 machine learning

From Data Lifting to Continuous Risk Estimation: A Process-Aware Pipeline for Predictive Monitoring of Clinical Pathways

This paper introduces a reproducible, process-aware pipeline that enables continuous predictive monitoring of clinical pathways by progressively refining risk estimates from evolving patient trajectories, demonstrating that predictive performance significantly improves as more clinical events become available.

Original authors: Pasquale Ardimento, Mario Luca Bernardi, Marta Cimitile, Samuele Latorre

Published 2026-05-06
📖 4 min read☕ Coffee break read

Original authors: Pasquale Ardimento, Mario Luca Bernardi, Marta Cimitile, Samuele Latorre

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine a hospital patient's journey as a long, winding road trip. In the past, doctors and computer systems mostly looked at the entire trip after it was over to see what went well or what went wrong. They would say, "Ah, we see now that the patient needed intensive care because of X, Y, and Z." This is like watching a movie only after the credits roll to understand the plot.

This paper proposes a new way of driving: predictive monitoring. Instead of waiting for the trip to end, the system tries to guess the destination (specifically, whether a patient will need to go to the Intensive Care Unit, or ICU) while the patient is still on the road, based only on the miles they have traveled so far.

Here is how the authors built their "navigation system," explained in simple terms:

1. The "Data Lifting" (Cleaning the Messy Map)

Hospitals collect data from many different places: admission forms, lab tests, vital signs, and medication lists. Often, this data is messy. One system might say a patient arrived at 10:00 AM, while another says 10:05 AM, or a vital sign might be missing entirely.

The authors call the process of fixing this "Data Lifting." Think of it like taking a pile of torn, crumpled maps from different drivers and stitching them together into one clean, accurate map. They used rules to fix time errors (like making sure a patient wasn't admitted before they were triaged) and filled in missing gaps so the timeline makes sense. Without this clean map, the computer would get lost.

2. The "Event Log" (The Travel Diary)

Once the map is clean, the system turns the patient's journey into a Travel Diary (called an "event log"). Every time something happens—a blood test, a doctor's visit, a medication change—it gets written down as a specific event with a timestamp.

  • Patient A's Diary: Admitted -> Blood Test -> X-Ray -> Medication -> Discharged.
  • Patient B's Diary: Admitted -> Blood Test -> X-Ray -> Medication -> ICU Transfer.

3. The "Prefix" Strategy (Reading the Story Chapter by Chapter)

This is the clever part. Instead of waiting for the whole diary to be written, the system reads the story one chapter at a time.

  • Chapter 1: Just "Admitted." (The computer guesses: "Maybe they need the ICU? Maybe not. It's too early to tell.")
  • Chapter 10: "Admitted, Blood Test, X-Ray, Medication..." (The computer updates its guess: "Okay, the pattern looks a bit more serious.")
  • Chapter 50: The full story is almost there. (The computer is now very confident.)

The authors call these partial stories "prefixes." They broke down thousands of patient journeys into these smaller, partial chunks to train their computer models.

4. The Prediction (The Weather Forecast)

The computer uses these "chapters" to make a prediction, similar to a weather forecast.

  • Early in the trip (Chapter 1-5): The forecast is shaky. The system isn't sure if the patient will need the ICU. The accuracy is low (about 64%).
  • Middle of the trip (Chapter 20): As more "events" (like lab results) pile up, the forecast gets better. The system starts seeing patterns.
  • Late in the trip (Chapter 50): The forecast is very accurate (over 94%).

The study found that Logistic Regression (a type of statistical math, like a very smart calculator) worked best. It achieved a high score of 90.6% accuracy in predicting ICU needs.

The Big Takeaway

The paper argues that predicting a patient's risk isn't a "one-and-done" calculation. It's a continuous process.

  • Old Way: Wait until the patient is finished, then analyze the data.
  • New Way: constantly update the risk estimate as new events happen.

The authors discovered that predictive signals emerge progressively. You can't know the whole story from the first sentence. You need the middle chapters to see the pattern. However, by the time a patient has gone through about 20 events, the system is already quite good at guessing the outcome, long before the patient leaves the hospital.

Why This Matters (According to the Paper)

The paper emphasizes that the quality of the data cleaning (the "Data Lifting") was just as important as the math used to make the prediction. If the map is messy, even the smartest GPS will give the wrong directions. By building a pipeline that cleans the data, organizes it into a diary, and reads it chapter-by-chapter, they created a system that can watch a patient's journey in real-time and update its risk assessment as the journey unfolds.

In short: They built a system that doesn't just look at the past; it watches the present to guess the future, getting smarter with every new piece of information the patient's journey provides.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →