Source Authority
Can an operator override an authoritative system?
Last reviewed
Direct answer
Yes. The operator can override an authoritative system for a specific decision when the evidence supports it, but the override must be recorded as a determination with its reason, approver and the original value kept. Authority belongs to the operator, not the software. An authoritative system is the default source, and the operator can depart from it deliberately and visibly.
Why this happens
Systems lag behind reality. A resident discharged this afternoon may still be active in a source until tomorrow.
Overrides without records destroy trust. Overrides with records make the organization’s reasoning inspectable.
Hypothetical example: authority depends on the decision
Clinical system
Authoritative for level of care
Assessments are recorded and signed there.
Billing system
Authoritative for the rate billed
The contract and payer terms are applied there.
Payroll
Authoritative for hours paid
It is the system of record for compensation.
- Evidence
- Disagreement
- Authority
- Operator-Controlled Operating Record
- Intelligence
- Execution
Illustrative figures. Coherence before Intelligence.
No single system is authoritative for everything. Authority is assigned per field and per decision.
The governance question
Authority is an organizational decision that software should record, not invent. When the authoritative source is wrong, the right response is a documented override with the original value preserved, not a silent edit.
Evidence → Disagreement → Authority → Operator-Controlled Operating Record → SeniorCRE Intelligence → Execution
What good operating infrastructure should do
- Per-field, per-decision authority rules approved by named owners.
- Visible authority: users can see which source governs a number.
- Override workflows that capture reason, approver and time.
- Original values preserved after every override.
- Periodic review of authority rules as systems change.
SeniorCRE perspective
SeniorCRE’s architecture records authority as a rule the operator approves, applies it when sources disagree, and keeps the overridden value with its reason and approver. Software can recommend; only the operator’s authority decides what governs. Status: the Operator-Controlled Operating Record is designed and not yet implemented in any community. Current capability states and production-entry gates are published in the Evidence Record at the Trust Center; nothing here should be read as a production result.
