Home / Technical Dress Rehearsal

Find the broken printer before go-live does

A technical dress rehearsal tests every workstation, printer and device in the place it will actually be used, with the workflows it will actually run. We plan it, staff it and track every issue to closed.

Why TDR matters

  • On day one, a label printer that maps to the wrong unit looks exactly like an Epic failure to the nurse standing at it.
  • Device and printing problems are among the most common go-live calls, and nearly all of them can be found in advance.
  • Your desktop team knows the hardware and your analysts know the build. TDR is where the two meet.
  • A late or partial TDR pushes hundreds of avoidable tickets into the command center.
  • New sites, renovations and hardware refreshes change the floor after the device inventory was taken.

What we do

A structured, scripted rehearsal across every department and location.

  • Planning and scheduling. Scope by site and department, test scripts, schedules and logistics agreed with your leaders.
  • Workstation testing. Each device checked for login, the right department context and the workflows used at that location.
  • Printing. Every printer and label printer mapped and tested for the documents that location produces.
  • Peripherals. Barcode scanners, signature pads, card readers, document scanners and other attached devices.
  • Issue tracking. Every failure logged with location and device, assigned, fixed and retested.
  • Reporting. Pass and fail by site and department, so leaders know what is ready and what is not.

How it runs

  1. Plan

    Inventory, scripts and a schedule that works around patient care.

  2. Test

    Trained technicians work unit by unit with a script for each device type.

  3. Fix

    Issues go to the right owner, whether that is desktop, network or the Epic build team.

  4. Retest and sign off

    Nothing is marked ready until it passes in place.

Questions buyers ask

When should TDR happen?

In the weeks before go-live, early enough to fix what you find and late enough that the hardware is in its final place. We set the dates with your project team.

Can you staff the whole event?

Yes. We size the team to your sites and device counts. Tell us the footprint and the date.

How does it connect to go-live support?

A clean TDR means fewer device tickets on day one. It pairs with our project management and the AI Go-Live Command Center.

Do you work with our desktop and network teams?

Yes. TDR works when the technical teams and the Epic analysts run it together.

Go-live on the calendar?

Tell us the date, the sites and the device count. We will tell you what a TDR would take.