There is one integration conflict we walk into on roughly two of every three healthcare technology engagements, and it almost always surfaces at the three-week mark — sometimes the second week, sometimes the fourth, but the cluster lands on week three. The conflict is predictable. The readiness list has a cell for it. The named owners are known before the engagement starts.
The conflict is between the new system and the older scheduling system it has to coexist with for ninety days after cutover. The product team has the integration tested in the sandbox. The vendor has signed off on the data contract. The clinical informatics lead has reviewed the schema. None of that matters at week three.
At week three, the floor is running. Two adjacent units are scheduling against the new system, and one is still scheduling against the older system. A patient moves between units. The schedule that was clean in the new system does not reflect the schedule that was kept in the older system. The handoff is wrong. The handoff is wrong because the integration was written against the test, not against the floor.
This is not a technical failure. The integration contract is correct. The Technical Readiness cell is signed. This is an operational failure — the integration was tested against a clean handoff pattern, and the floor does not run clean handoff patterns. Patient movement on a clinical floor is governed by triage, throughput, and the staffing of the receiving unit, not by the timestamp on the schedule.
The readiness list has a cell for this — the Workflow Drift cell, owned by the named clinical informatics lead and the named frontline operations manager on the client side. They are the ones who knew, on day one, that the integration was written against a clean handoff and that the floor does not run clean handoffs. They are also the ones who will be in the room at week three when the conflict shows up. The named operator side of the engagement has been tracking the cell with them since week one. When the conflict surfaces, the surface is already warm.
The pattern is the pattern. The integration lands at week three. The named owners are known. The cell closes. If you are scoping a vendor before signing, read the buyer-side checklist for vetting track records before the contract goes out.