Skip to content
PIMAP

About

What PIMAP is

PIMAP is a research effort exploring pressure injury monitoring and prevention. This site is a public showcase of that work — a place to understand the problem, the research, and the directions we are investigating.

A plain-language look at pressure injury

A pressure injury is damage to the skin and underlying tissue that can develop when sustained pressure reduces blood flow to an area, often over a bony part of the body. People with limited mobility are more susceptible. Care teams routinely assess risk and take preventive steps as part of everyday care.

This is a general explanation for context only. It is not medical advice, and it is not a guide to assessment or treatment. Clinical decisions belong with qualified care teams.

Focus

Our research focus

We work across three connected areas and keep them deliberately distinct.

  • Data & infrastructure

    Preparing clinical research data into structured, reviewable features, and sketching the research platform that could support reproducible work.

  • Predictive modeling

    Experimenting with established models to ask whether prepared features carry a usable signal, with honest evaluation.

  • Clinical workflows & integration

    Designing monitoring interface concepts and mapping the questions that any clinical integration would raise.

Audiences

Who this is for

  • Clinical collaborators
  • Researchers
  • Engineers and integration partners
  • Institutional stakeholders and potential sponsors

We write accessible summaries first, with technical depth available on the detail pages.

Foundational research

Data-drive framework

The foundational PIMAP dissertation frames patient monitoring as a repeating, data-driven cycle of storing data, analyzing it, and visualizing results, built on top of the data environment that supports those activities.

Our current projects map onto this framework. Clinical feature preparation and the proposed research platform sit in the data layer; the prediction experiments are analysis; the monitoring interface concepts are visualization; and Epic integration is an exploration of how such a cycle might one day connect to clinical systems. We are careful to separate what the framework envisions from what today's supplied artifacts actually demonstrate.

The PIMAP framework describes a repeating cycle: first, store patient data in a controlled research environment; second, analyze it by preparing features and running experiments; third, visualize the results through interfaces that support review. The cycle then repeats.

Principles

How we approach the work

  • Evidence transparency

    We distinguish what has been demonstrated from what is proposed or exploratory, and we avoid overstating results.

  • Usable workflows

    Information is only helpful if it fits how clinicians actually work. We design with that fit in mind.

  • Clinician involvement

    Clinical input shapes what we build. Prototypes exist to prompt feedback, not to replace judgment.

  • Responsible data handling

    Research data stays in controlled research contexts, separate from this public site.