A liability claim rarely reaches a hospital on the day of the procedure. It often comes years later: a patient claims they were not informed about a particular complication. The file contains a signed consent form. For many hospitals, that feels like a secure position. Legally, it is not necessarily one — and the reason lies in a question that is asked too rarely in everyday hospital work: in a dispute, who actually has to prove what?

The burden of proof lies with the treating party

The answer is in the law, and it is clearer than many expect. Under Section 630h(2) of the German Civil Code (BGB), the treating party must prove that it obtained consent in accordance with § 630d BGB and provided information in line with the requirements of § 630e BGB. The burden of proof therefore does not lie with the patient who alleges a deficiency in the information — it lies with the hospital, which must prove the opposite.

This reverses the intuitive expectation. The patient does not have to prove that they were not informed. The hospital has to prove that it informed them properly. If it cannot provide this proof, the case is ultimately treated as if no valid patient information had taken place — with the corresponding consequences under liability law. If you want to explore the duty to inform in more detail, you will find it in the legal basis of patient education.

A comparable principle applies in Austria: under established case law of the Austrian Supreme Court (OGH), the treating party bears the burden of proving that proper information was provided, or that the patient would have consented even if sufficiently informed — see, for example, the OGH decision on the duty to inform a minor patient. The details differ from the German rules, but the basic logic is the same — more on this in the article on informed consent in Austria.

What a signature proves — and what it does not

A signed consent form is evidence. But it proves a narrower set of facts than is often assumed: that a document was presented and signed. On its own, it does not prove

  • that the patient understood the specific risks relevant to their case,
  • that there was sufficient time between the patient information and the procedure,
  • that there was an opportunity to ask questions and that it could be used,
  • or that a personal discussion took place at all.

These are precisely the points that claims of inadequate patient information target in practice. A standard form that looks identical for every patient is at a structural disadvantage here: it documents the result (a signature), not the process (individual patient information). Why standardised documents carry a risk of their own is the subject of the article on generic consent sheets as a liability risk.

Important — and this belongs to an honest account: no digital process replaces the consent discussion with a physician. Under § 630e(2) no. 1 BGB, the mandatory personal discussion remains the core element of patient information. Digital tools can prepare, structure and document it — they do not take its place. A provider that promises otherwise misjudges the legal situation.

What courts actually consider: the traceability of the process

In court practice, a single document rarely counts on its own; what counts is the plausibility and traceability of the entire consent process. The more completely it can be reconstructed what happened when, the more robust the hospital’s position.

Paper-based processes reach a limit here. They record an end state — the completed, signed sheet. The path there remains undocumented: which information the patient saw, for how long, whether they went back or asked questions, exactly when they signed. In a paper process, this information simply does not exist.

This is where the real difference of digital processes lies — and it directly affects the question of proof. A consent trail — the complete, audit-proof documentation of every step of the consent process — records not only the signature but the path to it: which patient education content was viewed when, which passages were opened again, which questions were asked and when consent was signed.

With medudoc, a medical component is added: through digital annotation, physicians can add to the Informed Consent Sheet (IC Sheet) — the electronically signed consent document generated individually for each patient — before it is signed, thereby documenting the individual, case-specific patient information. The IC Sheet itself is archived in an audit-proof way as PDF/A. This creates exactly what the burden of proof requires: a traceable process instead of an isolated signature sheet. How these patient-specific digital informed consent sheets are created is described in detail elsewhere.

An honest assessment applies here, too: a consent trail is an instrument of proof, not a guarantee against liability. It considerably strengthens the evidential position because it makes the process reconstructable — but medical responsibility and the conduct of the consent discussion remain with the physician. Digital documentation does not replace good patient information; it makes good patient information provable.

What a robust process should be able to reconstruct

As practical guidance for evaluating a solution — regardless of the provider — it should be possible to reconstruct the following in a dispute:

  1. Which content the patient saw (and that it was relevant to their specific procedure).
  2. When the patient information took place — with a reliable timestamp, in particular regarding the interval between patient information and procedure.
  3. Whether and how there was an opportunity to ask questions.
  4. Who signed and with which signature level — which eIDAS level is appropriate here is covered in the article on which electronic signature is legally sound for surgical consent.
  5. That the document could not be altered afterwards without detection (audit-proof storage).

A process that can fully document these five points addresses the burden of proof where it is decided when it matters.