Source Authority
Who determines source authority?
Last reviewed
Direct answer
The executive accountable for decisions made with a measure should approve its source-authority rule, advised by the teams that run the systems involved. IT and vendors can recommend, but the rule belongs to the operator. Authority decisions should be recorded with the approver and date, and reviewed whenever systems or processes change.
Videos that answer this question
Watch: One Community. One Morning. One Question. · 1:12
Watch: Coherence before Intelligence · 9:24
Watch: Why SeniorCRE · 2:09
Watch: Can You Trust the Operating Picture of Your Enterprise? · 1:39
Watch: Can You Defend Every Number? · 1:37
Watch: You Run the Community. You Deserve Information You Can Trust. · 2:43
Watch: How Do You Scale Operating Consistency? · 1:48
Watch: The Information Behind Every Care Decision · 1:21
Watch: SeniorCRE Architecture of Coherence — Full Film · 3:45
Watch: SeniorCRE Clinical Record · 8:18
Watch: Senior Care Tech Paradigm · 8:30
Watch: RIDEA Governance Gap · 7:15
Watch: The Blind Spot: Connecting Capital to Care · 5:11
Watch: Truth before Intelligence · 10:50
Watch: Governing SI Truth · 7:34
Watch: The Architecture of Operational Truth · 7:45
Watch: The Monday Morning Number · 9:14
Watch: Owner and Operator: Whose Number Is True? · 1:16
Watch: When Your Software Disagrees · 6:50
Watch: The Institutional Operator · 5:31
Watch: The Operator Authority Chain · 6:50
Watch: Capital Decisions on Governed Operating Truth · 0:58
Watch: SeniorCRE for Operators · 0:51
Watch: Where Do I Start? · 1:30
Watch: Clinical Operations Explained · 1:28
Watch: The Executive Briefing · 1:32
Watch: The SeniorCRE Manifesto · 1:35
Watch: The SeniorCRE Platform · 1:36
Watch: Co-Development Operating Partner (Walkthrough) · 5:16
Watch: Coherence Before Intelligence: Your Systems Disagree · 1:05
Why this happens
Authority set by a vendor’s defaults reflects that vendor’s design, not the operator’s accountability.
Recording who approved a rule makes it possible to challenge and update it without starting the argument over from scratch.
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.
