First Nations Management & Leadership · Arcus perspective
How to Integrate Health Programs That Were Built in Silos
A merger can leave the fragmentation intact
Placing several health programs under one director does not necessarily make them operate as a coherent service. Separate intake rules, approval processes, information arrangements and funding conditions can continue to shape the person’s experience after the organizational chart has changed.
Arcus’s management thesis is to integrate at the level where the consequential break occurs. If the problem is a lost handoff, redesign the handoff. If the problem is scarce administrative expertise, compare shared support. If the programs require incompatible decisions about the same resources, a wider operating-model change may be justified. Structural consolidation should be an option supported by diagnosis, rather than the definition of integration.
This distinction matters for First Nations health organizations inheriting programs established through different agreements and delivery relationships. Leaders need to improve access and coordination while preserving Nation-defined priorities, appropriate professional responsibilities and funding and information obligations. The approach below is management synthesis, not a universal clinical pathway or legal interpretation.
The evidence distinguishes several kinds of integration
ISC’s Cluster Evaluation of Health Infrastructure Support for First Nations and Inuit examined programs over 2015–2021. Its Health Services Integration Fund analysis distinguishes coordination across funding jurisdictions, incorporating community priorities, transfers of control, organizational consolidation and integration of traditional approaches. The evaluation also identifies resource, coordination and reporting constraints.[1] Its scope and mixed program evidence do not establish that merging local departments is the best remedy for a specific service problem.
FNHA’s funding guidance states that organizations holding several contribution agreements may face different terms and conditions in each.[2] That practical distinction matters: a common manager or a combined internal plan does not itself authorize funds to be used interchangeably. Applicable agreements need to be reviewed by the appropriate finance and advisory functions.
FNIGC’s explanation of OCAP® places collection, use, sharing and control of information within Nation-specific information governance.[3] Integrating programs therefore requires an authorized information design. Combining databases is a separate choice from improving a referral or sharing an administrative function.
The management inference is that integration has several dimensions that may move at different speeds. Leadership can strengthen a service interface while retaining separate financial accountability. It can share support while preserving local service decisions. The local evidence must show which combination addresses the actual constraint.
Trace the failure from the person’s perspective
Select a bounded pathway that crosses program boundaries. Describe the intended journey from initial contact through the relevant services and follow-up. Use aggregate operational evidence, staff observation and appropriately authorized community input to identify where people repeat information, wait without an owner or receive contradictory instructions. Avoid collecting additional personal health information merely to illustrate an organizational problem.
Then locate the mechanism. Does the sending team lack a reliable receiving contact? Do program criteria leave a group outside both services? Are schedules incompatible? Is information unavailable under current arrangements? Is there insufficient capacity after an otherwise sound referral? Each can appear as fragmentation, but each requires a different response.
Consider a hypothetical family referred between two programs. A common intake contact may reduce repeated calls, but it will not create capacity in the receiving program. A shared manager may help resolve conflicting priorities, but it will not change external eligibility conditions. A new information platform may make the referral visible, but visibility is not the same as acceptance and completed follow-up.
Establish a baseline of handoff completion, elapsed time, repeated requests and staff coordination effort. Interpret the numbers with those who know the work. A low referral count may reflect poor awareness or a genuine mismatch between the services; it does not by itself establish that a common intake model is needed.
Test whether the silo is structural, contractual or operational
An operational interface problem
The programs may already have compatible purposes and sufficient authority but lack a clear process. Specify the handoff, information required, receiving responsibility and escalation route. This is a plausible first option where a bounded break can be corrected without reorganizing the wider portfolio.
A support-capacity problem
Teams may spend excessive effort reproducing finance, scheduling, purchasing or reporting work because each program maintains a small administrative arrangement. Compare shared support with simpler common tools or specialist access. Validate the work that would actually transfer; a shared function that requires each program to redo its outputs may increase the burden.
A mandate or funding constraint
Programs may have different authorized populations, service purposes or expenditure conditions. Leadership can identify the practical problem and seek an agreed change, but an internal merger cannot remove an external obligation. Make the constraint explicit and identify the party able to approve an alternative.
A governance or resource-allocation problem
Separate teams may compete for the same staff, facilities or priorities without an agreed decision process. Common planning and clear authority may be necessary. A wider structural change may be warranted if the problem repeatedly spans several services and cannot be resolved through a manageable interface.
These explanations can coexist. The useful diagnosis states how each contributes to the problem and which remedy addresses it. Do not describe disagreement as resistance until leadership understands whether it concerns a legitimate obligation, service risk or unresolved priority.
Choose the least disruptive model that can resolve the constraint
Coordinated programs retain their identities and accountabilities while using agreed handoffs, common planning or a shared service calendar. This can be relatively quick and preserve specialist knowledge. It depends on reliable cooperation and a clear route when priorities conflict. Coordination without authority can fail where resource disputes are the main constraint.
A shared access or navigation function can provide a clearer entry point across services. Compare its benefit with the risk that it becomes another layer through which people must pass. Define what it can resolve, what it can refer and who accepts responsibility after the handoff. Appropriate service leaders must determine any professional or clinical requirements.
Shared administrative support can concentrate scarce expertise while programs retain distinct delivery responsibilities. Define the service agreement, cost allocation, response commitments and local work retained. It can improve management capacity without creating a single clinical program, but may reduce responsiveness if the shared team is remote from the work or inadequately resourced.
An integrated management team or consolidated organization may align planning, supervision and resource decisions when the mandate and authority support it. It also creates transition work, wider spans of responsibility and potential loss of local or specialist focus. Compare it with stronger coordination before assuming the additional disruption is justified.
These options are not a compulsory maturity ladder. A coherent operating model may deliberately combine shared administration with locally controlled services and program-specific funding accountability. Judge the arrangement by whether it fixes the pathway and supports the Nation’s choices, rather than by how completely it resembles a single institution.
Make the economics visible before promising savings
Separate the cost of integration from its recurring operating effect. Transition costs may include design work, staff participation, role changes, training, information preparation, contract advice, technology and temporary overlap. Recurring costs include coordination, supervision, support services, travel and reporting. An integration plan can be worthwhile for service reasons even when it does not reduce expenditure.
Distinguish cash savings, released staff time and improved capacity. Removing duplicate data entry may free time without reducing a funded position. That can still improve delivery, but it should not be presented as an immediately available budget saving. State how released time will be used and how leadership will verify that it is actually released.
Compare the full cost boundary across options. A shared support invoice should include the coordination and work that remain locally. A new management role should include its continuing support and supervision requirements. A technology proposal should include maintenance, user support, access management and the process changes needed to make it useful.
Review proposed cost allocations and pooled resources against the relevant agreements. Where authorization or partner participation is uncertain, show it as a dependency with an owner and decision date. Do not build a business case on assumed flexibility that has not been established.
Integration Boundary Test
This original Arcus diagnostic links the integration choice to the failure it must resolve. It is a management framework, not a validated score, clinical standard or authorization to alter agreements.
Break
Question: Which service or management failure requires integration?
Warning sign: A broad desire to break silos substitutes for a defined problem.
Boundary
Question: Is the constraint a handoff, capacity, mandate, information or authority issue?
Warning sign: A structural change is proposed for an external condition it cannot alter.
Model
Question: Which combination of coordination, shared support or consolidation addresses it?
Warning sign: Every option is compared against an idealized version of the preferred model.
Economics
Question: Are transition costs, retained work and recurring costs explicit?
Warning sign: Released time is reported as cash savings without a feasible budget change.
Proof
Question: How will the organization test that the original break has improved?
Warning sign: The merger is declared complete when reporting lines change.
Start with one cross-program pathway before committing to a broad merger.
Implement one pathway, then decide what to scale
Agree the problem, baseline and authorized scope with the relevant leaders. Include program staff, finance, information stewardship and the people responsible for the affected service interfaces. Establish how community priorities and feedback will inform the design through the Nation’s own processes.
Develop a small set of feasible options with clear responsibilities. Identify which changes can proceed internally and which require agreement amendments, partner commitments or specialist advice. Assign an implementation owner with available time and a route to resolve cross-program decisions.
Test a bounded arrangement where uncertainty is material. For example, trial an agreed handoff and receiving-owner process before redesigning all intake functions. Set review conditions and protect the existing service pathway during the change. A trial should answer a consequential question rather than postpone an already established requirement.
Review completion and access alongside staff effort and cost. If the handoff improves but the receiving queue grows, the next constraint may be capacity. If shared support reduces duplication but slows urgent requests, revise the service agreement or resourcing. Use these findings to decide whether to scale, adapt or choose another model.
Arcus can support pathway mapping, root-cause assessment, operating-model options, role and decision-rights design, and staged implementation planning. Agreed outputs may include an integration map, a costed options case, a support-service model and a practical pilot and review plan. Nation leadership retains its choices, and relevant clinical, legal, employment and information expertise must inform implementation.
Discuss the right level of integration for your health programs →
Sources and limits of the evidence
- Indigenous Services Canada. Cluster Evaluation of Health Infrastructure Support for First Nations and Inuit. Evaluation scope 2015–2021; Health Services Integration Fund analysis and cross-program constraints. Mixed program evidence and reported experience do not establish a universally preferred local structure.
- FNHA. Funding arrangements. Notes that terms and conditions may differ across contribution agreements; local agreements require review.
- First Nations Information Governance Centre. The First Nations Principles of OCAP®. Nation-specific information governance. OCAP® is a registered trademark of the First Nations Information Governance Centre (FNIGC).
Research reviewed October 17, 2026. The thesis, integration framework, hypothetical scenarios and operating-model comparisons are Arcus management synthesis. No client results, guaranteed savings or universal clinical model are claimed.
Health Transformation collection · Health governance decision rights · Organization design services · Arcus consultant directory