Northstar Care Network is a fictional example. This reference page was authored for the sample scope of clinics and ambulatory services on 14 October 2026. It does not monitor systems, confirm an outage, or declare an incident.

Start with the approved reference for your setting

For care teams affected by an unavailable system or workflow

Identify the affected workflow and location, then use the authorized published downtime material that applies to that setting. This page helps coordinate access and communication; it does not establish clinical or operational policy.

Next: Obtain the current approved reference through the local operational coordinator or established downtime-access route. If it does not clearly apply to your workflow or location, ask the local operational coordinator before treating another site's material as applicable.

Coordinate the handoff

Keep the coordination record focused on context and ownership—not patient-identifying details.

Worked example: a Northstar clinic team identifies its check-in workflow and asks its designated local operational coordinator which published reference applies. It does not assume that a similarly named hospital-unit reference is interchangeable. The example demonstrates coordination only; it is not a clinical procedure.

  1. 1

    Name the affected workflow and location

    For example, distinguish a clinic check-in workflow from a hospital-unit workflow. Share only the operational context needed by the responsible roles.

  2. 2

    Open the authorized reference

    Use the authorized published downtime material supplied through that route, and check that its stated scope matches the location and workflow. Do not assume a reference for one site applies everywhere.

  3. 3

    Route questions to the responsible role

    Ask the local operational coordinator about workflow or site applicability. Route system status and recovery coordination to the relevant system support owner; use the clinical or domain owner for questions requiring approved domain guidance.

  4. 4

    Make the recovery handoff clear

    When coordination moves to recovery, share the affected workflow, location, outstanding questions, and the roles already involved through the authorized communication route.

A blank white card beside a kraft envelope; illustrative image, not an approved downtime document.

Who coordinates what

Local operational coordinator
Workflow and location questions
Clinical Operations
Relevant system support owner
System status and recovery coordination
Support Services
Clinical or domain owner
Questions requiring approved domain guidance
Clinical or service domain

Recovery handoff

As recovery coordination begins, pass the affected workflow and location, the operational roles already engaged, and any outstanding coordination questions to the designated operational and system-support roles. Follow the authorized recovery communications for the applicable setting.

Owner: Clinical Operations and Support Services share responsibility for this page's scope, reference-access guidance, and role routes. Review when the approved reference, covered settings, or ownership changes; refresh the authored notice when its scope or date is no longer accurate.

Terms: “Downtime reference” means the authorized published material applicable to a stated workflow and setting. “Recovery handoff” means the transfer of coordination context and outstanding needs to the responsible roles; it is not a declaration that a system is restored.