prorso Guide Library Articles Features Enterprise
For teams
Sign inCreate account

Rollout approach for an electronic prescribing and medicines administration system

Open in the app

By · Published

A three-site hospital group decides how to deploy electronic prescribing: pilot, phase by specialty, a single date, or phase by site with a printed paper copy of each chart kept until steady state. Th...

The options

The question: How should the electronic prescribing and medicines administration system be deployed across the organisation: a single-ward pilot, a phased rollout by specialty, a single deployment date for all sites, or a phased rollout with paper retained until each site reaches steady state?

Option 1: Pilot on one ward, evaluate, then decide again

For

  • Benefit. A single-ward pilot exposes the fewest patients to the transition, and would surface configuration-driven error modes on a small scale where they can be corrected before wider use.

Against

  • Risk. A single ward cannot generate enough prescribing volume to detect rare system-related error types within the pilot period. The pilot would most likely conclude that the system is safe without having been able to test the question it was set up to answer.
  • Risk. A ward on the system while every other ward is on paper creates a boundary that patients cross when they transfer, and transfers across that boundary are the point at which medicines are most often mis-transcribed. The pilot introduces a risk that a single-date deployment does not have.

Option 2: Phase by specialty across the three sites over eighteen months

For

  • Benefit. Phasing by specialty spreads backfill demand rather than concentrating it, and it is the only full-deployment option that fits within the cap on releasable clinical staff with a clear margin.
  • Benefit. Under phasing by specialty, lessons from each specialty inform the next, and the configuration can be corrected between phases rather than only after full deployment.

Against

  • Risk. Sequencing specialties keeps some part of the organisation inside a transition for about thirty months, from the first go-live to twelve months after the last. The admissions exposed are no more than under the other deployment options, but monitoring, floor-walking and heightened vigilance must be sustained for the whole period, and the steady-state benefit is not reached everywhere until the end of it.
  • Risk. For eighteen months the organisation runs two prescribing methods simultaneously, and every patient transferred between a live specialty and a paper one crosses the boundary that transcription errors occur at.

Option 3: Deploy to all three sites on a single date

For

  • Benefit. Deploying on a single date is the only option with no boundary between live and paper prescribing at any point, within a site or between sites, so it removes the transfer-transcription risk entirely.

Against

  • Risk. Thirty-eight whole-time equivalents of clinical backfill, against a releasable maximum of about 22, cannot be released without reducing planned activity at two sites already above planned occupancy. The option fails the constraint rather than scoring badly against it.
  • Risk. A configuration-driven error mode discovered after go-live affects every ward at once, and the option's reversibility is the lowest available. The evidence review's own caution about low-quality evidence bears most heavily on the option that commits everything at once.
  • Evidence quality. The reviews caution that the underlying literature is heterogeneous and that much of it is of low quality, with the certainty of evidence rated very low in places. The numeric criterion values in this log are therefore hypothetical estimates that indicate direction and rough magnitude, not parameters.

Option 4: Phase by site over nine months, with paper charts retained alongside the system at each site until it reaches steady state

For

  • Benefit. Keeping a printed copy of each chart at the bedside, refreshed from the system every shift, means a site can revert within a shift without transcribing live prescriptions, which is the step that makes reversal dangerous under the other deployment options.
  • Benefit. Phasing by site keeps each site on one method, so the boundary between live and paper prescribing is crossed only on transfers between sites, which are far fewer than transfers between specialties within a site.
  • Recommendation. Phase by site over nine months, with a printed paper copy of each chart kept at the bedside until each site reaches a defined steady state. The single-date option is not available: its peak backfill of 38 whole-time equivalents exceeds the 22 that can be released without cutting planned activity. The pilot defers the decision and, on one ward's prescribing volume, cannot detect the rare error modes it would be set up to find. Every full deployment exposes about the same number of admissions to the transition, so the choice between the two phased options turns on how that exposure is managed. Phasing by site avoids eighteen months of mixed methods within each site, reaches full coverage in half the time, and keeps the ability to stop without transcription, which matters most where the published evidence is weakest: whether a new system-related error mode will appear that configuration did not anticipate. It costs more than phasing by specialty and leaves little margin on backfill, so the intervals between sites cannot be compressed.

Against

  • Risk. Two live records of the same prescription can disagree, and a nurse administering from the chart that was not updated is a failure mode this option creates and the others do not. Dual running is a safety measure that carries its own hazard.
  • Risk. Dual running tends to persist. Without a defined end condition each site keeps paper indefinitely, the organisation never reaches steady state, and it pays the cost of both methods permanently.

Criteria and values

CriterionOption 1Option 2Option 3Option 4
Peak clinical backfill (lower is better)3143821
Admissions exposed to the transition (lower is better)3,000118,000118,000118,000
Mixed methods within a site (lower is better)—18 month0 month0 month
Programme cost (lower is better)410,000 GBP2,350,000 GBP1,980,000 GBP2,610,000 GBP
Ability to stop or reverse (higher is better)moderatemoderatelowhigh
Time to full coverage (lower is better)—18 month0 month9 month
Elevated-error period per area (lower is better)12 month12 month12 month12 month

What constrained the decision

Evidence

Related decisions

Open the decision log in the app

Spotted an error? Report a problem (ivan@ivanjureta.com). Corrections are listed on the page with their date.