← All case studies

Case study

Package and freight operations, applied toOrgan and team transport

Organ transport logistics: from carrier invoices to a control-center plan

How my cHealthWorks Logistics team turned one organ procurement organization's carrier invoices into data, then proposed a 24/7 control center to another.

At a glance

  • A carrier-invoice audit and transport data review for an organ procurement organization (2019).
  • A proposal to a second OPO (2020), built on recovery times checked against flight departures.
  • A proposed 24/7 control center: one call, tracked handoffs, managed exceptions and audited bills.
  • An animated map of historical transportation movements originating from the second OPO's donation service area, built from national transplant registry data.

The problem

An organ procurement organization (OPO) moves organs, recovery teams, blood samples and equipment, often in the evening or early morning. Operating-room times change. One move can take several legs: a driver, a flight, then another driver.

At my former company, cHealthWorks Logistics, a team of five former UPS people, me included, took this problem on twice: a discovery review for one OPO in 2019, and a proposal to a second OPO in 2020.

What the invoices and the data showed

Carrier invoices, turned into data (2019)

My team and I audited the OPO’s carrier invoices and turned them into data that could be sorted and compared. Interviews during discovery filled in what the invoices couldn’t show.

  • Few agreements. Interviews showed that most transport providers worked without a written agreement or service levels.
  • Billing errors. Many of the invoices audited had errors. Two kinds made up most of the errors found: charges for extra pieces or deliveries that the piece count didn’t show, and line-item detail compressed so far that the charges couldn’t be audited.
  • No common language. Invoice lines described the same service in many different ways, so spend was hard to group and compare until the invoices became data.
  • More than organs. Most moves went by road, and more of the spend went to moving recovery teams and blood samples than to moving organs.
  • Repeat routes. Similar local stops came up day after day, so dispatch could be planned better.

The gaps were in how transport was set up. Without agreements, standard invoice data or shared metrics, problems like these are hard to see.

Recovery times, checked against flights (2020)

For the second OPO, the question was kidney transport by air. My team and I compared recovery times, from national transplant registry data, with flight departures by hour, from airline schedule data for sample days in late 2020.

  • Late recoveries, few late flights. Recoveries often ran into the evening. On the sample days, during COVID-19 schedule cuts, the airlines in regular use had few departures left by then.
  • More capacity than was in use. All airlines together had far more departures, spread through the day. Cargo-airline departures were checked as another option.

The conclusion: there was enough flight capacity to solve the problem, but the solution would be more complex than the process in place.

An animated map of the network

For the proposal, I also built an animated map of historical transportation movements originating from the OPO’s donation service area. Built from national transplant registry data, it plays each recovery by organ type and time, then shows the transplant centers that received the organs. It made the network visible at a glance. It isn’t shown here, because it plots individual records.

Registry data: The data reported here have been supplied by the Hennepin Healthcare Research Institute (HHRI) as the contractor for the Scientific Registry of Transplant Recipients (SRTR). The interpretation and reporting of these data are the responsibility of the author(s) and in no way should be seen as an official policy of or interpretation by the SRTR or the U.S. Government.

What I borrowed, and from where

Package and freight operations, where my whole team had worked, applied to organ and team transport: carrier agreements with service levels; the same data fields on every invoice, so each bill can be audited; shared metrics and carrier reviews; tracking, with custody confirmed at handoffs; exception management; and one point of coordination.

For the first OPO, the review recommended:

  • agreements with service levels, and quarterly business reviews with carriers;
  • standard data on every invoice;
  • a set of service and cost measures, including on-time pickup and delivery, invoice error frequency, cost per donor and cold ischemic time by organ;
  • a single point of coordination for transport.

For the second OPO, my team and I proposed two phases. Phase 1, discovery and solution development, would assess current capabilities and each provider’s performance and cost, find more carriers and couriers, and work with providers on service levels, metrics and operating plans. In Phase 2, every move would run from a 24/7 logistics operation control center.

The control-center vision

One call to the center would start a move. The center would set out transport options, with timing and cost, for the OPO to accept. It would track each leg by GPS and flight status, confirm custody at every handoff, and manage exceptions with a remedy and a revised arrival time. Everyone involved would get updates by text, by email and online. After delivery, the center would audit the bill, authorize payment and review the carrier.

The proposal covered every organ and team move. The second OPO wanted help with kidney transport only, and preferred not to share its past transport data. With a narrower scope and no baseline to measure the work against, my team and I decided not to go ahead, so the control center stayed a proposal.

Who made it work

My cHealthWorks Logistics team of five did the 2019 discovery review, the 2020 analysis and the proposal, and the first OPO opened its carrier invoices to the review. I built the animated map.

What carries over today

The records a process already keeps often show where it breaks. Before you renegotiate rates or add a carrier, turn the bills into data and look at every handoff.

  • Organ transport data. The flight database my cHealthWorks Logistics team built, and how much commercial air capacity organ transport lost early in COVID-19.

Working on a process with too many handoffs and too much at stake?

Tell me what it is and where it goes wrong. A few lines are enough. Or email