In most sectors that integrate, the question is mainly organisational: which systems, which teams, which customers. In healthcare there's an additional dimension that makes the process heavier than the organisational structure alone. Most of what comes together is not just a system or a team, but a care process with clients or patients right in the middle of it. A merger of two healthcare providers is therefore not just combining schedules and files, it's combining two ways in which care is provided, accounted for and monitored. That difference isn't found in a percentage, it's found in what's at stake when something goes wrong.
Healthcare organisations operate under the supervision of authorities that set requirements for record-keeping, incident reporting and accountability. Merging two organisations often means having two quality systems, two ways of incident registration and two interpretations of the same standard existing side by side. Before a generator can draw up a synergy baseline, it must be clear which quality system will become the leading one and what that means for certification and oversight. That is not a technical choice; it affects the way care providers account for their work.
Healthcare staff often work under specific collective labour agreements, with their own arrangements for irregular shifts, training requirements and registration in professional registers. In an integration, the question is not only who will work where, but under which employment terms and with which registration obligation. A Day 1 plan that fails to take this into account gets stuck within the first weeks on questions that directly affect staff. This is one of the places where a dependency list proves useful: registration requirements, application of the collective labour agreement and professional registration are interrelated and should not be treated separately.
Care doesn't stop for the weekend or for a system changeover. Schedule integration in healthcare is therefore different from most other sectors: an error in the transition doesn't just affect operations, but the availability of care at the moment it's needed. A Day 100 plan that treats scheduling and shift planning as an IT project without attention to continuity of care misses a risk that carries less weight in other sectors. For comparison: where in retail the shop floor gets stuck on checkout systems and inventory, healthcare gets stuck on the question of whether a client sees the right care provider on time.
In healthcare too, the standing question applies: does this part actually need to be merged? Combining two treatment locations with their own specialisations into a single process can cost quality rather than deliver it. Merging two record systems can create more risk than letting two systems exist side by side, as long as the accountability is sound. The decision list in the integration office is meant to raise that question for each part, not to work by default towards full merger. This also applies to supporting functions: where business services can often quickly merge overhead, that is less self-evident in healthcare as soon as the primary process touches that overhead, think of planning or quality registration.
The synergy baseline, the Day 1 plan and the Day 100 plan structure what comes together and what dependencies exist. They do not show experience with previous healthcare integrations and they do not guarantee an outcome. They do help to get the questions that weigh more heavily in healthcare — oversight, registration, continuity — onto the list early, rather than discovering them only once things have already gone wrong. Just as with production lines in manufacturing the physical nature of the process slows the integration, in healthcare the nature of oversight and accountability obligations slows the process. Other sectors have their own bottleneck in turn: in education, funding and inspection determine the pace, in transport it is often permits and planning.
An integration in healthcare makes visible how much work is being done twice: keeping records twice, checking schedules twice, reporting to supervisory bodies twice. Before those tasks are merged or discontinued, it's useful to know which part of them can already be largely supported by AI, so that the choice is not only about who takes over the work, but also about what will still need to be done manually afterwards. The work scan from FTE TO AI calculates this per task and provides a concrete picture of which part of the work can be taken over, as a starting point for the integration choices described here.
The generators and the integration office for healthcare are under construction. Anyone who wants to use this as soon as it becomes available can sign up for the waiting list. Nothing is being delivered right now that isn't ready yet.
Vraag maar wat er op Day 1 moet staan, of wat integreren juist kapotmaakt.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.