First Nations Management & Leadership · Arcus perspective
Designing Patient Navigation and Advocacy Services for Remote First Nations
A navigator needs an operating mandate, not an unlimited promise
A new navigation role can become the place where every unresolved service problem lands. The organization then has a visible point of contact, but the navigator has neither the authority nor the capacity to resolve the underlying barriers. Counting calls can make this arrangement look productive while people continue to repeat their story across organizations.
Arcus’s management thesis is that navigation should be designed around completed handoffs and defined escalation rights. The service needs to say what support it provides, when it follows a person across a boundary, and who must act when the next organization cannot or will not accept responsibility. Advocacy adds a further requirement: a credible route to challenge an experience or decision without simply returning the person to the team they are concerned about.
This article concerns organizational design for First Nations leadership and health managers. Local patients, families and appropriate clinical, cultural, privacy and service leaders must shape the model. Navigators should not be expected to make clinical decisions beyond their qualifications or promise benefits, appointments or transportation they cannot authorize.
What concrete service models show
Kingston Health Sciences Centre describes Ininew Patient Services as a partner of the Weeneebayko Area Health Authority supporting Cree patients and families from specified northern communities. Its published service design brings together referrals, admission and discharge planning, interpretation, accommodation and transportation.[1] This is useful evidence of an operating model connecting several practical functions. It is not a comparative evaluation proving that the same configuration will work everywhere.
FNHA’s Preparing for the Journey booklet identifies Indigenous patient navigators or liaisons within health-authority teams alongside distinct spiritual and other supports.[2] Its palliative-care context illustrates why support roles should connect without being treated as interchangeable. It does not establish a universal navigation mandate or current local availability.
FNIGC explains that First Nations determine how information governance principles are expressed within their own protocols.[3] A cross-organization navigation model therefore needs approved information arrangements. A helpful relationship between staff does not itself authorize the exchange of every record. The design implication is to map responsibilities and permissions before announcing an all-purpose navigation service.
Choose the barrier before choosing the job title
Trace a small set of actual service journeys with the appropriate consent and protections. Include people who did not complete the journey, not just those who reached an appointment. Identify where the difficulty occurred: finding an entry point, obtaining an authorized referral, arranging travel, understanding a communication, reaching the next provider or obtaining support after return.
Consider a hypothetical person whose specialist appointment was missed. One explanation is an uncommunicated schedule change. Another is transport that could not operate. Another is an unclear funding decision. Another is that the person did not feel safe attending. These explanations call for different responses: reliable notification, transport contingency, an authorized decision or an appropriate advocacy and cultural-safety response. A reminder call cannot resolve all four.
Distinguish navigation failures from service scarcity. A navigator can help clarify a waiting-list position and escalate an unresolved request, but cannot create an unavailable clinician. Record the underlying constraint so repeated individual workarounds do not conceal a capacity problem requiring leadership action. Avoid describing people as non-compliant when the pathway itself has not been examined.
Also test whether the organization is adding another intake layer. If the person must repeat information to a community worker, regional navigator and hospital liaison without a clear handoff, the new service may increase burden. Agree who remains the main contact and how that responsibility changes, with the person’s preferences and permissions respected.
Compare four configurations
Community-based navigation. A local role can offer familiarity, continuity and knowledge of community resources. Its limitations may include specialist-system access, small-team absence coverage and confidentiality concerns in a close-knit setting. Build a backup arrangement and a way for people to request a different contact without having to justify personal circumstances publicly.
Receiving-centre liaison. A role embedded at a hospital or regional centre may be well placed to resolve internal processes and support admission or discharge communication. It may have less visibility of the conditions before travel and after return. Define the link to community teams and retain an independent escalation route where advocacy concerns the host institution.
A shared regional navigation team. Pooling can provide specialist knowledge and coverage across participating Nations. It also creates allocation, travel, language and accountability questions. Agree service commitments with each Nation, how urgent organizational barriers are escalated and how regional capacity will avoid being absorbed by the largest or most connected community.
A distributed model with one accountable coordinator. Existing workers can retain their specialist responsibilities while a coordinator tracks handoffs. This may use established relationships and avoid duplicating services. It fails if coordination is added without protected time or partners are free to ignore requests. Test whether the partners will accept explicit responsibilities before choosing this model.
The choice should follow the dominant barriers, community preferences and partner commitments. A hybrid may be appropriate, but each interface still needs an owner. A diagram containing every possible role is not a functioning service.
Separate navigation, interpretation, advocacy and clinical responsibility
Define what the navigator can explain, arrange, record and escalate. Specify which matters require a qualified interpreter, clinician, benefits decision-maker or complaints function. Do not assume that cultural familiarity alone establishes medical interpretation competence, or that a navigator’s availability permits them to undertake every kind of support.
For advocacy, agree how a person can raise a concern about the service employing the navigator. Explain confidentiality and its limits through an appropriate process, protect access to support, and identify where an unresolved matter goes next. The model should support the person’s choices rather than substituting organizational preferences for their wishes.
Create a minimum handoff agreement with each key partner: what constitutes an accepted request, what acknowledgement is expected, who contacts the person next, what information is necessary and who follows up when acceptance is delayed. Partner-specific expectations should be negotiated and feasible; an internal target cannot compel another organization to provide a service.
Remote-access design must account for contact interruptions and travel disruption without making assumptions about every community. Ask how people prefer to be reached, what alternatives are usable and how changes are communicated. A virtual channel can supplement the service, but a digital-only entry point may exclude the very journeys requiring support.
Cost the difficult work as well as the visible contacts
Estimate workload by journey type and complexity, including preparation, unsuccessful contact attempts, partner follow-up, documentation, travel and support after an incident. A short call that closes a simple request and a complex cross-organization case should not be assigned identical capacity assumptions. Use a time-limited local workload study rather than importing an unsupported caseload ratio.
The budget should include supervision, protected learning, interpretation access, coverage, secure communication, travel and appropriate staff support. Separate the cost of navigation from patient travel, accommodation or treatment budgets: the navigator’s salary does not fund those services. Identify who authorizes exceptional costs and how a pending decision is communicated.
Compare shared and local provision on the full operating cost. A regional team may reduce duplicate training but add coordination and travel. An embedded role may gain system access but require additional community liaison. Savings should not be claimed merely because work moves from a clinician to a navigator; show whether paid capacity is actually released or simply used for other work.
Before expansion, test the service against an absence, an unaccepted handoff and a travel interruption. If the proposed coverage depends on one person answering indefinitely, the service promise exceeds the operating model. Narrow or phase the promise, fund suitable coverage, or negotiate support before demand grows.
Navigation Completion Test
This original Arcus decision framework is a management aid for local adaptation. It is not a validated assessment instrument or a substitute for the Nation’s authority and relevant professional requirements.
Entry
Question: Can the person reach a trusted, usable route into support?
Decision evidence: Confirm channels, hours, alternatives and preferences with intended users.
Ownership
Question: Who follows the request until the next team accepts it?
Decision evidence: Name the handoff owner and acceptance evidence.
Authority
Question: Can the role resolve the barrier or reach someone who can?
Decision evidence: Document decision limits and an escalation route.
Advocacy
Question: Can a concern challenge the organization providing the service?
Decision evidence: Provide an appropriate route beyond the immediate service team.
Continuity
Question: What happens after travel, discharge or staff absence?
Decision evidence: Test the return handoff, follow-up and backup coverage.
Turn the design into an operating commitment
Begin with one defined pathway and a small set of willing partners. Agree scope with the Nation and intended users, establish information arrangements and record the current handoff problems. Set a bounded trial period appropriate to the service cycle, with a named operational sponsor and a funded staffing plan.
Track accepted handoffs, unresolved barriers, time awaiting an organizational response and the person’s experience where they choose to provide feedback. Include reasons for closure and cases still open. A high closure count is not success if staff close difficult cases without resolving the next step. Review the patterns with partners and change the process that repeatedly creates avoidable work.
At the review, decide whether to expand the model, alter the role, secure a missing partner commitment or address a service-capacity constraint. Keep the rationale visible. Arcus can support pathway mapping, role and service design, workload analysis, partner responsibility agreements and implementation planning; clinical and individual care decisions remain with appropriately authorized people.
Sources and limits of the evidence
- KHSC. Ininew Patient Services. Primary description of a specific northern referral and support arrangement; not evidence of comparative effectiveness.
- FNHA. Preparing for the Journey, p. 30. Palliative-care information describing navigation and spiritual supports; not a general staffing standard.
- FNIGC. The First Nations Principles of OCAP®. Nation-specific information governance guidance. OCAP® is a registered trademark of the First Nations Information Governance Centre (FNIGC).
Research reviewed October 17, 2026. Decision frameworks, options and hypothetical illustrations are Arcus management synthesis. No client outcomes or universal staffing, savings or impact benchmarks are claimed.
Health Transformation collection · Integrating health programs · Organization design services · Arcus consultant directory