Service mandate and decision rights · Lesson 2

Who decides and who receives? Design the governance and escalation matrix

6 min read

Lesson objectives

  • Map actors, accountable owners and clinical escalation handoffs.
Reading tools

A digital health platform may say a message was sent while the clinical team assumes operations monitors replies, operations assumes the vendor does, and the vendor only maintains transport. This is more than an untidy organization chart: a handoff gap can leave a case without an owner. Distinguish the person doing a task from the role accountable for its outcome, the specialist consulted, and the people merely informed. A department label is insufficient. The operating procedure needs a current duty role, an alternative channel and evidence that responsibility transferred at the locally approved trigger.

Break an event into tasks with one observable verb. 'Verify receipt of a follow-up message flagged as time-sensitive' is different from 'interpret its clinical content' and from 'repair the messaging interface'. Give each task one accountable owner even when another team performs it. Define the clock start: system dispatch, arrival in a receiving queue and human acknowledgment are different events. One timestamp cannot stand in for the others. State what the user sees when delivery fails and who takes over. A vendor does not acquire clinical judgment authority by operating the software. When staff change shifts, transfer open cases with acknowledgment rather than assuming that forwarding an inbox transfers responsibility.

The case matrix separates four tasks. First, delivery monitoring is performed by operations, accountable to the service owner, with technical advice when a log is missing. Second, message content is handled by the clinical duty holder, accountable to the institution's authorized clinical leadership; operations needs only the minimum receipt status. Third, the interface repair is carried out by the technical team or contracted supplier, accountable to the technology owner, and tested with operations. Fourth, the governance body makes the expansion decision after reviewing the evidence, with its formally designated decision holder accountable for that decision. The matrix does not authorize every role to read message contents. Each role receives only the information necessary for its task. Named duty positions and a backup channel belong in the institution's actual procedure rather than being invented by a teaching case.

A completed matrix is only a design hypothesis. Test a change of duty holder with a synthetic message containing no real patient data. Send a follow-up flag, then interrupt the primary transport route or place the message in a queue. Operations should detect the failure. The backup duty holder should know exactly which case has moved to them. The register should show acknowledgment without exposing content to roles that do not need it. If recovery creates a second copy, both copies need a shared case identifier or a documented link so that two conflicting actions are not taken. Test notification delivery separately from the duty holder's substantive decision: the first is a technical and operational test; the second belongs under qualified clinical oversight. Record each handoff time according to the institution's procedure instead of using dispatch time as a proxy for receipt.

An exception rule names temporary decision authority when the normal path fails. An absent duty holder does not automatically transfer authority to a vendor or a shared inbox. A predesignated alternative escalation route is activated, with a record of why, who accepted the case, and who closed it. At incident close, do not report only the 84% aggregate. Reconcile each of the eight unconfirmed messages because an average can conceal a small number of consequential cases. If the three messages without an arrival record were actually duplicates of messages received by another route, prove the link through identifiers and timestamps before removing them from the receipt gap. Arithmetic reconciliation is no excuse to lose a genuine report.

The committee record separates observation, decision and missing evidence. Observation: the system dispatched 50 messages but only 42 were acknowledged. Decision: do not expand the messaging function yet. Missing evidence: the fate of eight messages and the performance of the backup channel during transport failure or a shift change. State what would reopen the decision: reconcile the eight, pass a synthetic alternative-delivery test, and designate an ongoing monitoring owner. Do not write that the supplier is 'responsible for messages' if its contract covers transport only. Name its repair duty and keep content judgment with the clinical team. Nor should the committee claim that 84% breaches a universal legal threshold. It is a rate from this fictional data; the institution must establish its own operational acceptance criterion after reviewing risks and applicable local requirements.

The worked case has 36 acknowledgments among 40 messages, or 90%, with four unresolved: two unreviewed and two without an arrival record. We separated transport monitoring, clinical content interpretation and expansion authority.

The clinical duty holder checks the four through the alternative pathway, the technology owner tests transport, and messaging expansion waits for a demonstrable receipt or visible failure for every message.

Dispatch is not acknowledgment, and acknowledgment is not evidence of a clinically sound response. The case specifies no universal legal escalation time or actual institution's decision powers.

If all four remaining messages were acknowledged, the recorded acknowledgment rate would become 40÷40=100% and the receipt gap would close. Clinical handling quality and the expansion decision would still need their own review.

Lesson summary

The worked case has 36 acknowledgments among 40 messages, or 90%, with four unresolved: two unreviewed and two without an arrival record. We separated transport monitoring, clinical content interpretation and expansion authority. The clinical duty holder checks the four through the alternative pathway, the technology owner tests transport, and messaging expansion waits for a demonstrable receipt or visible failure for every message. Dispatch is not acknowledgment, and acknowledgment is not evidence of a clinically sound response. The case specifies no universal legal escalation time or actual institution's decision powers. If all four remaining messages were acknowledged, the recorded acknowledgment rate would become 40÷40=100% and the receipt gap would close. Clinical handling quality and the expansion decision would still need their own review.