The practical test of an integrated system is what happens when a person needs care to move from one team to another.

A healthcare strategy can describe a connected system while its implementation plan remains a collection of institutional projects. A hospital improves its processes. Community services redesign their offer. A digital team develops a platform. Each programme has a sponsor and milestones, but the responsibility for making them work together remains unclear.

For an executive team, the challenge is to make the connections explicit. Which part of a person's experience should improve? Which organisations must act differently? What must be true before a service can accept a new responsibility?

WHO's framework places people's needs at the centre of service design and identifies coordination and accountability among its core strategies. That provides a useful starting point for the operating questions below. WHO: Integrated people-centred care.

Define the change from the person's perspective

Begin with a bounded journey rather than a promise to transform the whole system. Identify the population, the point at which the journey starts, the services involved and the experience the proposed change is intended to improve.

For illustration, a review of the transition from hospital to community support could examine whether people understand the next step, whether the receiving service has accepted responsibility and whether necessary information is available when needed. This is a proposed diagnostic approach, not a reported client case or a clinical protocol.

The resulting aim should describe a service outcome. Launching a referral tool is an output. Making a referral visible, accepted and actionable is an operating change. The executive team needs to understand both, and avoid treating completion of the first as proof of the second.

Examine the hand-offs in detail

Ask the participating teams to walk through the journey together. Focus on the points where responsibility moves, a decision is required or someone has to chase information. Include the perspective of people using the services and staff doing the work.

A useful review records five things at each transition:

  • The condition that makes the next step necessary
  • The team responsible for initiating it
  • The information and capacity needed by the receiving team
  • How acceptance and completion become visible
  • The route for resolving an incomplete or rejected hand-off

Distinguish the agreed process from what actually happens. An undocumented workaround may be keeping a service functioning, while a formal pathway may depend on capacity that is not consistently available. Both matter to the design.

Match responsibility with the ability to act

An executive sponsor can hold a programme together without holding every operational decision. The task is to specify who can change referral arrangements, allocate support, approve service standards and resolve disagreements across organisations.

Record the decisions that each organisation controls and those that require joint agreement. A shared ambition does not automatically create shared authority. Where an owner depends on another institution, define the commitment, the escalation route and the point at which leaders must intervene.

Keep clinical decisions with the appropriately accountable clinical teams. Executive governance should establish the service conditions, resources and assurance needed for those teams to work effectively. A programme office should not become an alternative clinical authority.

Test capacity before moving work

A redesigned pathway changes workload. Tasks may move between professions, locations or organisations; new coordination work may also appear. Ask where that work will sit and what existing activity must change to accommodate it.

The capacity discussion should cover staffing, skills, supervision, scheduling, information access and contingency arrangements. A service cannot be assumed ready simply because it has agreed with the proposal in principle.

Request an explicit readiness decision from the receiving service. What can it support now? What depends on further preparation? What would require a slower introduction? This makes the implementation sequence a joint operational judgement rather than a centrally announced date.

Give information a defined purpose

Digital tools should support a known task or decision. Before specifying another dashboard or interface, describe what a professional or service manager needs to know, when they need it and how they will use it.

For each information exchange, identify an accountable owner, the minimum necessary information, its source and how errors will be corrected. Data access and sharing arrangements need review by the relevant privacy, security and clinical governance functions before use.

Also agree what happens when a tool is unavailable or a record is incomplete. The operational design should make these exceptions visible and manageable instead of assuming that every interaction follows the intended path.

Measure the whole journey

A single organisation's improvement may move delay or workload to another part of the system. An executive review should therefore combine local performance with measures of the complete journey.

Select a small set of questions before choosing indicators:

  • Can people reach and understand the next service?
  • Does responsibility transfer reliably between teams?
  • Are delays, repeat requests or unresolved exceptions visible?
  • What do patients, carers and staff say has changed?
  • Has the change affected workload, access or experience differently across groups?

Establish the starting position and agree consistent definitions. Interpret operational measures alongside appropriate quality and safety review. Avoid claiming that a programme caused a wider health outcome merely because the outcome changed during implementation.

Make the first implementation a test of the design

Choose a manageable setting in which the main assumptions can be examined. Agree the scope, accountable leaders, readiness conditions and evidence required before expanding. A pilot should have a decision purpose: it should resolve uncertainty about how the model works.

At each review, separate issues with the underlying design from issues with preparation or execution. More training will not resolve an unclear hand-off. A new escalation meeting will not create missing capacity. The response should address the identified constraint.

Before expansion, record what must be consistent across settings and what can be adapted locally. This gives subsequent teams a practical basis for implementation without assuming that one setting represents every community or provider.

Executive questions

  • Which patient journey best exposes the gap between our strategy and current operating arrangements?
  • Who can resolve a failed hand-off when the organisations involved have different priorities?
  • What evidence would make us slow, redesign or extend the first implementation?
  • Are we assessing the experience across services, or only reporting each institution's activity?

JP Associates helps leaders frame healthcare transformation around clear service responsibilities, operating requirements and decisions that support delivery across organisational boundaries.