Case History¶
Document — instantiates Layered Record Accumulation
Accumulates observations, interventions, decisions, and outcomes for a person, client, patient, asset, project, or legal matter.
A Case History is the running record of a single continuing matter — one patient, one client, one aircraft, one legal case — accumulated so that its trajectory can be read. Its defining idea is continuity over a long life: each encounter, observation, intervention, and outcome is deposited as a layer and cross-referenced to the others, so that a reader can trace how a recurring symptom, a repeated fault, or an escalating dispute developed across many separate episodes. What makes it THIS mechanism and not a fast event log is that it is organized around the entity whose story it tells, is expected to outlive any one episode, and earns its value from the links between distant entries rather than from the precise ordering of a single burst of activity.
Example¶
A regional airline keeps a condition-monitoring case history for each engine, filed by tail number. Over four years the file accumulates layers: quarterly borescope inspections, oil-analysis chip-detection readings, a bearing replacement, exhaust-gas-temperature margin trends, and a pilot-reported vibration event. Each layer records its source — which shop, which inspector, which instrument produced the reading — and proprietary manufacturer data in the file is access-restricted, with commercially sensitive fields redacted for line mechanics who only need the maintenance actions.
Setup to outcome: preparing a mid-life overhaul, a reliability engineer opens the case history and follows the cross-references. A "one-off" chip detection three years earlier links forward to two smaller findings and the recent vibration report — together a slow bearing-degradation trend that no single inspection flagged. Reliability-centred maintenance[n1] then justifies pulling the engine before failure rather than at the scheduled interval. The decision is possible only because the file preserved and connected observations that were, individually, unremarkable.
How it works¶
- Deposit each episode as a layer. Every encounter — an inspection, a treatment, a filing, a reading — is appended to the entity's file rather than overwriting the last state.
- Cross-reference across the trajectory. Related layers are linked: this reading to that later finding, this complaint to that intervention, so a pattern spanning years is navigable rather than buried.
- Attach provenance at deposit. Each layer records where it came from — the instrument, clinician, inspector, or source — so a later reader can weigh its reliability.
- Govern sensitive access. Because the file concerns a specific person, asset, or matter, access and redaction rules protect what must not be seen by every reader.
Tuning parameters¶
- Episode granularity — whether each contact is one layer or is broken into finer sub-entries. Finer records reconstruct the trajectory in detail but swell the file.
- Cross-reference density — how aggressively entries are linked. Rich linking surfaces long-range patterns but takes curation effort and can create false trails.
- Provenance depth — naming a source versus fully documenting instrument, method, and conditions. Deeper provenance supports trust but adds recording burden at every entry.
- Access partitioning — how finely the file is compartmented by role. Tight partitions protect privacy but can hide relevant history from a reader who needs the whole arc.
- Active horizon — how long the matter stays open and appended-to before it is closed and handed to an archive.
When it helps, and when it misleads¶
Its strength is trajectory: it turns a scatter of isolated episodes into a legible life-story of one entity, which is exactly what handoffs, second opinions, and long-horizon decisions depend on. A clinician, a successor case-worker, or an overhaul planner inherits not just the current state but the path that produced it.
Its failure mode is context collapse: an old layer reused without the conditions under which it was created — a lab value read years later as if current, a note whose caveats were dropped. The classic misuse is treating the accumulated file as automatically trustworthy when its entries carry no provenance, so a stale or mis-sourced observation drives a present decision. The discipline that guards against this is to record provenance at the moment of deposit and to read each layer against its own context, not the reader's present assumptions.
How it implements the components¶
layer_record— each encounter, observation, intervention, and outcome is a preserved layer in the entity's continuing file.cross_layer_index— links across episodes make a multi-year pattern navigable, connecting distant entries into a single trajectory.provenance_record— every layer names its source (instrument, clinician, inspector, filing party) so reliability can be judged later.access_and_redaction_rule— role-scoped access and redaction protect the sensitive, entity-specific material the file holds.
It does NOT order a fast-moving event with timestamp_or_sequence_marker or mark observations evidence_confidence_marker as provisional-versus-confirmed — that is Incident Timeline; nor does it capture the rationale for an approved change in change_context — that is Change Ledger.
Related¶
- Instantiates: Layered Record Accumulation — it preserves the longitudinal, cross-referenced history of one continuing matter.
- Sibling mechanisms: Incident Timeline · Change Ledger · Version History · Archival Layer · Learning Portfolio · Commit History · Stratigraphic Record · Chain-of-Custody Record
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Accumulates observations, interventions, decisions, and outcomes for a person, client, patient, asset, project, or legal matter, making its operative form a durable record, ledger, register, or trace whose value depends on preserving actual state or history.
Independent corroboration: The frozen evidence defines Case History as 'Accumulates observations, interventions, decisions, and outcomes for a person, client, patient, asset, project, or legal matter', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Medicine & Healthcare
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Clinical practice established longitudinal case histories organized around one patient and their trajectory across encounters.
Related originating lineages:
- Law & Governance — Legal matter files independently preserve a continuing case across decisions, interventions, and outcomes.
Review resolution: Medicine is primary because the longitudinal case history became a formal diagnostic record there, while law developed an independent dossier tradition for facts, events, and procedural state. The two established lineages support a convergent, multi-domain classification.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
A case history tracks the whole life of one entity across many episodes; a Chain-of-Custody Record tracks the possession of one artifact across handoffs. They can coexist — an evidence item may have both — but they answer different questions: "how did this matter develop?" versus "who held this item, unbroken, and when?"
[n1] Reliability-centred maintenance is an analysis method that schedules maintenance from an asset's actual failure behaviour and consequence, rather than from fixed calendar intervals. It depends on exactly the kind of accumulated condition history a case history preserves — without the trajectory, there is nothing to reason from. ↩