Staffing model
US-based, Rely-supervised, and assigned to programs they are trained for.
How Rely works / Rely navigators
When included in scope, a Rely navigator accepts permitted nonclinical work and follows it to a documented state.
The navigator receives the history, allowed actions, deadline, and next owner in one packet.
Navigators own permitted nonclinical work, not diagnosis, treatment, or triage.
Staffing
US-based, Rely-supervised, and assigned to programs they are trained for.
Your workflow, systems, permissions, stops, disclosures, and population.
A named supervisor owns the queue; sampled work feeds training and controlled workflow changes.
The context packet
Enough context to act without guessing.
| Field | What it carries |
|---|---|
| Trigger | What caused this case to exist, and when. |
| Prior attempts | What has already been tried, by whom, and what happened. |
| Approved data | The minimum-necessary fields this navigator is permitted to see for this workflow. |
| Permitted actions | The specific steps this person may take without asking anyone. |
| Destination | Where the case goes next if it cannot be completed here. |
| Fallback | What happens if the destination does not accept, or is unavailable. |
The fields are standard. Their contents are program-specific and are agreed during scoping.
Assignment and acceptance are separate events. A case remains open until it reaches one of three documented states.
The permitted action finished and the result was recorded.
The path could not finish, and the defined closure reason was recorded.
A named owner explicitly accepted the next action. Sending or assigning alone does not count.
Bring the exceptions that keep returning to your clinical team.