Service mandate and decision rights · Lesson 4

Operational exceptions: when to change a pathway and how to restore it

6 min read

Lesson objectives

  • Decide, document and retire operational policy exceptions without creating an uncontrolled bypass.
Reading tools

A person using a digital health service may need an alternative route when the usual identity check fails. An exception is not permission to ignore the rule. It is a bounded decision that meets a service need while controlling an additional risk. If support staff bypass identity checks and leave the new access open, a temporary remedy becomes a standing back door. An exception record names the case, the rule that could not be met, the alternative, the decision holder, the expiry point, and the evidence that returns the case to the normal route or closes it. Sensitive health content calls for a clear division between those who can see data and those who decide what action is safe, under verified institutional and local requirements.

First ask whether the obstacle is a rare case or a design defect affecting many users. If many people fail at the same step, do not label each failure an individual exception; investigate the service rule itself. For a genuinely exceptional case, state the function narrowly. 'Change one non-urgent appointment through an alternative channel' is narrower than 'access the health record'. Use an alternative identity check approved by the relevant identity owner, and avoid collecting extra information without a purpose. Record approval by an authorized role, an expiry time or closing event, and the person who completed the task. Afterward check whether the privilege stayed within scope, was removed, and arose from a recurring cause that calls for a rule change. A time-sensitive report is not a blanket reason to waive identity protection. Route the report to qualified human handling through an established safe pathway.

A useful decision record has seven practical elements: case identifier without unnecessary disclosure, reason for exception, task scope, alternative verification, approver and performer, expiry point, and closure evidence. One approved case might read: 'Non-urgent booking internal number 104; name mismatch; alternative verification accepted by the identity owner under institutional procedure; permission to change this booking only through the current support cycle; staff confirm the outcome and remove channel access.' A denial records the reason and a safe service alternative, not merely the word 'denied'. A pending case stays visible with an owner and is counted as neither approved nor denied. Exception quality is not the approval percentage alone. More revealing checks are documentation completeness, actual expiry, and whether access was used outside its approved scope.

Exception review combines a count with an explanation. Seven approvals among twelve requests do not reveal whether all twelve came from one person, many people, or a particular channel. Record requests and unique people using only the information needed for analysis, the kind of mismatch, entry route and case outcome. Two weeks cannot be compared if the logging rule changed: a drop may look like improvement because support staff stopped recording denials. If mismatches concentrate in alternative Arabic name spellings across two systems, test synthetic inputs that represent the pattern, then review real cases under appropriate permission and controls to confirm the explanation. Do not solve the defect by demanding more personal data from every user without a purpose. Any proposal to change the matching rule also needs a test that it will not merge two different identities. Better access cannot justify exposing another person's information.

Writing 'expires in one day' in a register is insufficient if the system never enforces expiry. Run a synthetic test: grant access to one booking, complete the change, then attempt to reuse the privilege on both the same booking and another one. Both later attempts should fail after closure and be logged without unnecessary disclosure. If access remains active, pause the affected exception privileges and investigate possible past out-of-scope use before granting more. Where automatic removal is unavailable, named staff must demonstrably monitor and revoke access rather than assuming somebody will remember. The governance decision states who may reopen a closed case and on what evidence, so 'reopen' cannot become an invisible bypass.

In the worked case, 7+3+2=12 requests and 7÷12≈58.3% approvals. That rate does not prove the seven privileges closed, so each requires checks on booking scope, expiry and removal.

An approved exception covers one non-urgent booking with an accepted alternative identity check, short validity and proven closure. A time-sensitive flag goes to the qualified team, while repeated name-matching failures trigger a rule test.

All figures are fictional. Neither the number of unique users nor the safety effect of the alternative route is known. The identity method, time window and approving authority come from verified institutional and local requirements.

If all twelve requests were proven to arise from the same faulty name rule, repairing that rule would take priority over administering twelve separate exceptions. Access already granted would still need a scope and closure review.

Lesson summary

In the worked case, 7+3+2=12 requests and 7÷12≈58.3% approvals. That rate does not prove the seven privileges closed, so each requires checks on booking scope, expiry and removal. An approved exception covers one non-urgent booking with an accepted alternative identity check, short validity and proven closure. A time-sensitive flag goes to the qualified team, while repeated name-matching failures trigger a rule test. All figures are fictional. Neither the number of unique users nor the safety effect of the alternative route is known. The identity method, time window and approving authority come from verified institutional and local requirements. If all twelve requests were proven to arise from the same faulty name rule, repairing that rule would take priority over administering twelve separate exceptions. Access already granted would still need a scope and closure review.