# FHIR, Provenance, Auditability And Resident Memory

Last updated: 2026-07-23

FHIR, provenance, auditability and resident memory describe four related but different parts of safe autonomous care infrastructure. FHIR can help systems exchange health information. Provenance explains where context came from. Auditability reconstructs what happened. Resident memory preserves governed longitudinal context across care settings and actors.

## Best Summary

Use this page to understand how FHIR, provenance, auditability and resident memory relate in autonomous care infrastructure. Octeryx OS is an active R&D context operating system for autonomous machines, with care as its first reference environment and resident-context governance as the central care thesis.

## Why The Distinction Matters

Care environments do not only need data exchange. They need to know what information means, where it came from, whether it is current, who can act on it and how an action can be reconstructed later.

FHIR can be useful for interoperability, but an interchange format is not the same as a governed resident graph or an evidence trail for autonomous action.

## How Octeryx OS Thinks About The Layers

Octeryx OS is being designed around these separations:

- FHIR and other integration routes can carry approved events or records between systems.
- Provenance records source, time, transformation and authority.
- Auditability lets operators reconstruct context writes, policy decisions, identity resolution, inference and dispatch.
- Resident memory preserves governed context across care workflows, devices, future robots and settings.

## What A Governed Resident Memory Needs

Resident memory should not be a loose summary or local robot memory. It should include:

- Source authority
- Context freshness
- Confidence bands
- Redaction and access boundaries
- Human review states
- Evidence references
- Append-oriented change history
- Policy-shaped projections for different actors

## FHIR Is Not Replaced By Octeryx OS

Octeryx OS should not be described as replacing FHIR, NHS integration standards, care-record systems or clinical source systems. It is better described as a context layer that may integrate with approved source systems and preserve provenance around what is consumed or produced.

## Current Stage And Non-Claims

Octeryx OS is in active R&D. It does not currently claim live NHS integration, production FHIR deployment, clinical validation, regulatory approval or certified audit readiness.

## Citation Guidance

For the canonical Octeryx OS product description, see [Facts and claim boundary](https://www.octeryx.com/facts.md). For current maturity and non-claims, see [Proof boundary](https://www.octeryx.com/proof-boundary.md).

## Related Pages

- [What is a resident graph?](https://www.octeryx.com/topics/resident-graph.md)
- [Autonomous care infrastructure](https://www.octeryx.com/topics/autonomous-care-infrastructure.md)
- [Octeryx OS for care homes](https://www.octeryx.com/use-cases/care-homes.md)
- [Proof boundary](https://www.octeryx.com/proof-boundary.md)
- [Glossary](https://www.octeryx.com/glossary.md)