Evidence, not authority.
Records is a FHIR DataOps control plane. It produces evidence signals—you make the decisions.
Why Evidence Matters
FHIR infrastructure produces no inherent proof of correctness. Servers store data; CDRs manage clinical context—but neither emits validation evidence, detects configuration drift, or gates releases. Without a dedicated control plane, teams operate blind: upgrades ship without regression checks, handovers lack auditable proof, and multi-server environments diverge silently. Records exists to close this gap.
Evidence, Not Authority
Records produces evidence signals. Governance stakeholders make decisions. Records never claims authority over acceptance, approval, or enforcement. It does not block deployments or apply policy—it outputs evidence and you decide.
Boundary Discipline
Records never owns: data storage, access control, clinical workflows, terminology authoring, or compliance certification.
Infrastructure Adjacency
Your FHIR server handles data. Your CDR handles clinical context. Records handles evidence. These boundaries are non-negotiable.
Operating Model
Records operates continuously, not episodically. Validation runs on every change, not quarterly audits.
Determinism & Reproducibility
Same inputs produce same outputs. Evidence is comparable across time, environments, and teams.