Health & Research Data Platforms

Interactive reporting for clinicians, patients and policymakers

The analysis is rarely the gap. The gap is between that analysis and the person making a decision with it.

Registries, annual data reports and outcomes studies produce large, dense datasets. They are often published as PDFs and static tables. That format works for the research team and works less well for a patient choosing a transplant center or a policymaker evaluating a program.

I build the application layer that closes that gap. R, SAS and Python output goes in. A fast, filterable, linkable web application comes out.

Where This Has Been Built

SRTR Interactive Reports

Transplant program outcomes from R datasets, rendered as interactive charts and maps. A significant performance and usability improvement over the prior static reports.

View the live tool
USRDS Annual Data Report

Interactive visualization platform for the national kidney disease data report, used by healthcare professionals and researchers to explore trends nationwide.

View the live tool
Transplant Center Search

Patient and provider search comparing transplant center outcomes, with real-time filtering built to support real clinical decisions.

View the live tool
Liver Waiting List Calculator

Two years of actual patient outcomes visualized so patients and providers can understand what waitlist trends mean for them specifically.

View the live tool

What I Build

  • Interactive report builds. Replacing static PDF reports with filterable, linkable, fast web applications.
  • Analysis pipeline integration. Taking R, SAS or Python output and turning it into a queryable data layer that a web application can hit.
  • Data visualization. Charting and mapping validated against the published results.
  • Public and patient-facing tools. Search, comparison and calculator interfaces for audiences with no statistical training.
  • Annual cycle support. Rebuilding and republishing when the next data cycle lands.
  • Accessibility and compliance. Section 508 and WCAG conformance, which is not optional for federally funded work.

Who This Is For

Academic medical centers, disease and outcomes registries, research nonprofits, public health departments and federally funded programs. If you publish an annual data report, run a registry, or have a dataset that currently reaches its audience as a spreadsheet, this is the work.

I am based in Minneapolis and work with organizations across the country. The Twin Cities happens to be a dense health data cluster, so a fair amount of this work is local.

Have data to publish?

Tell me what you publish today and who it is for.

Start a Conversation