Layered Case Note¶
Record template — instantiates Capture-Latency Evidence Stratification
A record template with separate fields for what was observed, what is inferred, and what was reconstructed later, so a single note keeps its evidentiary strata visible.
A Layered Case Note builds the stratification into the shape of the document itself. Rather than relying on a separate protocol or a later reviewer to keep observation apart from interpretation, it gives them different boxes on the page. Its defining property is structural: a single note is pre-divided into fields keyed to evidentiary status — what was directly observed, what is concluded from it, and what was pieced together after the fact — so that the act of writing forces the author to sort each claim into its stratum. The note is not a store, a ledger, or a gate; it is a form whose fields are the layers. Because the structure does the sorting, a reader can trust that a fact in the "observed" box was observed and a judgment in the "assessment" box is a judgment, without excavating which is which.
Example¶
A child-protection caseworker visits a family after a school referral. In a free-text note, "the home was unsafe and the mother seemed hostile" reads as fact — but it fuses an observation, an inference, and a possibly late impression. The Layered Case Note splits it. Under Observed: "no working smoke detector; two children sharing one bed; mother raised her voice twice." Under Inference: "conditions suggest supervision concerns; hostility may reflect stress from the visit rather than toward the children." Under Later reconstruction: "on reviewing the school's earlier reports two days after the visit, the pattern appears consistent with prior concerns" — dated to when that synthesis was actually done.
When the note reaches a supervisor or a court, the difference is preserved: the smoke detector is a fact, the "supervision concerns" is the worker's reasoned judgment, and the pattern-matching is an after-the-fact synthesis. A decision can rest on the observed facts and weigh the inferences appropriately, instead of inheriting a single confident paragraph in which observation and conclusion have already melted together.
How it works¶
- Scoped header. The note opens by fixing the event it documents — the visit, date, participants, and context — so every layer below refers to a known referent.
- Observation field. A box for what was directly sensed, phrased to exclude interpretation. Discipline here is to write only what a camera could have caught.
- Inference field. A separate box for conclusions drawn from the observations, explicitly marked as reasoning rather than fact.
- Reconstruction field. A dated box for anything synthesized after the event — later cross-referencing, hindsight, corrected chronology — kept visibly apart from the live observation.
Tuning parameters¶
- Field granularity — three strata versus finer splits (observation / report / inference / plan). More fields sharpen the distinctions but raise authoring effort and the chance of mis-filing.
- Enforcement — whether fields are mandatory and validated or merely suggested headings. Enforcement guarantees separation but can push authors to write to the form rather than the facts.
- Observation-language strictness — how aggressively interpretive words are disallowed in the observation box. Strict rules keep the layer clean but slow writing and can feel pedantic.
- Reconstruction dating — whether after-the-fact additions must carry their own date. Dating preserves latency; omitting it collapses the reconstruction layer back toward looking original.
When it helps, and when it misleads¶
Its strength is that separation becomes the path of least resistance: because the form already has the boxes, keeping observation apart from inference costs nothing extra, and the discipline scales to every author who uses the template. This is the logic of the SOAP note in clinical practice — Subjective, Objective, Assessment, Plan — a structured format designed precisely so that the reader can tell what was observed from what was judged.[n1]
Its failure mode is that a form can be filled without being honored: an author can drop an inference into the observation box, and the structure will then lend that misfiling false authority ("it's in the Observed field, so it must be fact"). The classic misuse is treating the template's tidiness as truthfulness — a well-formatted note that quietly mis-sorts its claims is more dangerous than a messy honest one. The guarding discipline is periodic review of whether entries actually sit in the right layer, and observation-box language rules that make interpretation hard to smuggle in.
How it implements the components¶
event_reference_scope— the note's header fixes the event, participants, and context that all its strata refer to.inference_annotation_layer— the dedicated inference field marks conclusions as concluded, keeping them out of the observation record.delayed_reconstruction_layer— the dated reconstruction field holds after-the-fact synthesis without letting it impersonate live observation.
It does not implement uncertainty_and_confidence_label or independent_corroboration_channel — attaching confidence and cross-checking against outside sources is the work of Delayed Interview Protocol; this template separates the layers within one authored note but does not grade or corroborate their claims.
Related¶
- Instantiates: Capture-Latency Evidence Stratification — bakes observation/inference/reconstruction separation into the record's structure.
- Sibling mechanisms: Delayed Interview Protocol · Contemporaneous Event Log · Late-Entry and Backfill Protocol · Reconstruction Workspace or Replay Table
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: The note durably preserves observed, inferred, and later-reconstructed information as distinct evidentiary strata in the case history.
Nearest alternative: Interface, Display & Cue — Layering makes status visible, but the primary value is the accountable case record.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Medicine & Healthcare
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Clinical documentation developed structured case notes separating observation, assessment, and later correction.
Related originating lineages:
- Criminology & Forensic Studies — Forensic casework materially shaped explicit evidentiary strata.
- Ethnography & Qualitative Methods — Field-note methods contributed explicit distinctions among observation, interpretation, and reflexive comment.
- Law & Governance — Evidentiary recordkeeping independently requires distinctions among contemporaneous fact, inference, and later reconstruction.
Review resolution: Both independent reviews place the primary lineage in medicine_healthcare. The queued differences (alternate_origin_disagreement, origin_mode_disagreement) concern secondary metadata rather than primary provenance. The final retains criminology_forensic, law_governance, ethnography_qualitative_methods only where a reviewer supplied a formative-lineage rationale; downstream application by itself is not treated as origin. origin_mode=cross_disciplinary_synthesis records the relationship among origin traditions, while domain_reach=multi_domain records application breadth separately. encyclopedia_synthesis=true reflects whether either reviewer identified a corpus-specific synthesis, and confidence=medium preserves the more cautious evidence assessment.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] The SOAP note (Subjective, Objective, Assessment, Plan), introduced within Lawrence Weed's problem-oriented medical record, is a widely used clinical template whose separate sections keep directly observed findings distinct from clinical inference — the archetypal layered note structure. ↩