Quick answer
Build two linked chronologies: a clinical timeline showing what happened to the patient, and a legal-administrative timeline showing records requests, complaints, discovery of possible fault, defendant identity and notices. Every entry should identify its source and confidence level. Do not merge a record timestamp with a later recollection or turn a gap into an allegation.
How to use this guide
The timeline should expose decision points for expert review. It does not decide negligence. A bad outcome, departure from professional practice, causal connection and compensable harm remain separate questions.
Start with the baseline, not the disputed event
Record the patient's condition before the relevant attendance: symptoms, diagnosis, functional level, medication, allergies, comorbidities, earlier tests and reason for seeking care. Include the source date and provider. This allows a reviewer to distinguish pre-existing disease from new injury or deterioration.
If the baseline is disputed, create separate entries for each source. Do not rewrite a later description as if it appeared in the admission note. State that a fact is unavailable when the earlier record has not been obtained.
Use a structured event table
Useful columns are date and time, location, clinical event, information available, decision or omission, person or role, source document and page, patient consequence, and confidence label. A final column can state the expert question raised without answering it.
Use exact time where the source gives one and a range where it does not. Preserve the provider's notation and explain abbreviations in a glossary. If electronic systems show entry time and event time separately, record both. Never sort only by when a note was signed because that can distort the care sequence.
Confidence labels might be “contemporaneous record,” “device or system timestamp,” “patient recollection,” “witness recollection,” “later clinical opinion,” “disputed” and “missing source.” These labels stop a visually neat table from creating false certainty.
Mark clinical decision points
For each assessment, test, observation or result, show what was known and what followed. Examples include triage category, abnormal vital signs, imaging order, laboratory availability, referral request, specialist review, medication administration, consent discussion, procedure, post-operative monitoring, escalation, transfer and discharge.
Avoid judging the decision in the event column. “Blood pressure recorded at 80/50; repeat observation not located” is a source-led entry. Whether a reasonable practitioner should have intervened and whether intervention would have altered the outcome require discipline-specific analysis.
Link referenced material. If a progress note mentions a scan, place the report and image identifier on the same row. If a medication is ordered but administration is uncertain, show the order and administration record separately.
Track symptom and harm development
Create a parallel symptom line using contemporaneous records where possible. Record pain, fever, neurological signs, mobility, wound changes, consciousness, foetal monitoring or other relevant observations without selecting only values that support one theory.
Show when the adverse condition was first detected, what corrective treatment followed and the patient's response. Include later diagnosis, surgery, rehabilitation and current prognosis in date order. Do not write that the alleged delay caused permanent harm unless a qualified opinion supports the mechanism and counterfactual.
The Supreme Court of Appeal's reasoning in Louw v Patel demonstrates why the passage of time can be medically important yet still require careful expert evaluation of probabilities. A timeline supplies the facts on which that opinion depends.
Create a record-conflict log
When two records conflict, do not overwrite one with the other. Add both entries and create a conflict number. Describe the inconsistency, source, author, creation time and whether clarification was requested.
Common conflicts include different procedure times, copy-forward medication lists, retrospective notes, inconsistent discharge dates and later summaries that compress events. A discrepancy may reflect error, documentation practice or a substantive factual dispute. The timeline should preserve the issue without accusing anyone of falsification.
Keep missing periods in a gap register. For each gap, name the record category, custodian, date requested, response and why it may matter. “No record supplied” is not the same as “no care occurred.”
Add consent and communication events
Record when information was provided, who participated, what procedure or alternative was discussed, when consent was signed and any interpreter or capacity issue. Include refusals, discharge-against-advice discussions and instructions about warning signs.
The National Health Act addresses user information and consent as distinct protections. A timeline may reveal whether the relevant discussion occurred, but a signature or recollection requires context. Keep competence-of-treatment and information-and-consent theories on separate tags.
Build the legal-administrative track
Below the clinical events, record when the patient or representative first received records, learned a later diagnosis, obtained information suggesting possible fault, identified each provider, requested expert input and received an opinion. Add internal complaints, HPCSA or Health Ombud submissions, responses, invoices, offers and legal consultations.
Prescription under section 12 is knowledge-sensitive, but the legal start date cannot be read from one timeline entry without analysis. Include facts that cut both ways. Do not omit an earlier concern because a later expert opinion is more helpful.
Where public treatment may produce a claim against an organ of state, create a separate Act 40 line for the potential debt-due date, six-month notice assessment, intended recipient, service evidence and any condonation question. Never mark a hospital complaint as statutory notice unless its legal content and delivery were checked.
Preserve the source behind every entry
Use stable exhibit codes and page references. Keep source files read-only, preserve native images or messages, and log any redacted review copy. Do not paste isolated screenshots into the chronology without the complete original context.
Health records are confidential and protected under the National Health Act. Restrict access to those who need the file and confirm representative authority. If a timeline is shared with an expert, identify which records were included so the opinion's factual basis can later be reproduced.
Produce two useful views
Maintain a full master chronology and a shorter issue timeline. The master file contains every relevant source-led event. The issue version shows only entries needed for the alleged departure, causal mechanism, harm and dates. Never delete adverse events from the master when shortening the working view.
End with an unresolved-questions table: missing record, clinical-standard question, causation question, defendant question, prescription or notice issue, and person responsible. Update by version rather than silently changing past entries.
A defensible timeline helps experts and lawyers test the case. It should make uncertainty easier to see, not make the conclusion appear predetermined.
Important limitation
This chronology method does not authenticate a record, resolve conflicts, determine the medical standard, prove causation or calculate prescription or Act 40 notice.
FAQs
How should I label a recollection that is not in the medical record?
Mark it as patient or witness recollection, add the date the recollection was recorded and do not present it as record-confirmed. Keep the underlying account intact.
What if two medical records show different times?
Enter both times with their sources, note the conflict and avoid silently choosing one. Device clocks, retrospective notes and copied entries may require clinical or technical interpretation.
Should prescription and state-notice events appear in the clinical timeline?
Keep them in a parallel legal-date track linked to the relevant treatment and knowledge events. This prevents a complaint date or record request from being mistaken for legal protection.
Why keep both a full chronology and a shorter issue timeline?
The full chronology preserves context and adverse facts, while the issue view helps reviewers focus on breach, causation, harm and dates. The shorter view should never replace the master source record.
Related Lexuno paths
Related articles
Source notes
Legal note
This article is general legal information for South African readers. It is not legal advice. Speak to a qualified legal professional about your specific facts before taking action.