Skip to content

Review and Attestation

Two clinicians can put their name to the same piece of clinical content and mean entirely different things by it. This guide keeps the two apart, because a reader who confuses them gets the record's responsibility wrong.

  • Review says I received this and I have read it. A family physician acknowledging a lab result, or a specialist's letter that arrived by fax, is reviewing it. They take responsibility for having seen and understood it. They do not take responsibility for its content being correct.
  • Attestation says this is right, and I stand behind it under my own name. The author signing their note attests it. So does a supervisor signing off a learner's note, and a colleague co-signing at the author's request. An attester is one of the document's signatories.
Review Attestation
What the clinician claims received and read professional responsibility for the content
Usually on content that arrived from elsewhere: results, filed documents content authored in this EMR: notes, letters
Resources DiagnosticReport, Observation, DocumentReference Composition
Recorded as nexus-emr-reviewed Composition.attester, typed by nexus-attestation-function
More than one? yes: one stamp per reviewer, where the profile allows yes: attester is 0..*
Absent means unreviewed unsigned (and a final note must not be)

Why the split follows the resource

A Composition is a document authored in this EMR: an encounter note, a letter, a summary. A DocumentReference is a document that came from outside: a scanned referral, a hospital report, a consult letter received by fax. The people who wrote a Composition are here, so it is attested. The people who wrote a DocumentReference are not, so here it can only be reviewed.

The same document can be both, in two different records. A specialist at a large site writes a consult report, signs it, and has a colleague co-sign it: in the specialist's EMR it is a Composition with two attesters. The report is sent to the patient's family physician, whose EMR files it as a DocumentReference; the family physician reads it and stamps it reviewed. They have not taken responsibility for the specialist's findings, only for having received and understood them, and nothing on their copy says otherwise.

Which resource a received report lands on, who it was sent to, and who is responsible for acting on it are in Incoming reports.

Review

nexus-emr-reviewed is stamped on the artifact itself: who reviewed it (reviewer) and when (time). Absent means unreviewed, so an artifact that has just arrived needs nothing written on it to be waiting. Each profile sets how many stamps its artifact carries: a result carries one acknowledgement, while a document can be assigned to several named reviewers and carries one stamp each.

The work of getting something reviewed is a task, coded review-report for the inbound results stream and document-review for a document assigned to a named reviewer. Completing the task writes the stamp; the stamp never drives the task. A viewer reads the stamp and needs no task join to show a checkmark.

Where a user interface says "sign off" on a result or a filed document, it means this: a review.

Attestation

Composition.attester lists everyone who has taken responsibility for the document. R4 types each entry with mode, bound to four required codes -- personal, professional, legal, official. That is not fine enough: a supervisor's sign-off and a peer's co-signature are both professional, and a reader has to be able to tell them apart to print "Signed off by" or "Co-signed by" beside the name. nexus-attestation-function carries the distinction, with HL7 v3 ParticipationType codes:

Code Function mode Reads as
LA legal authenticator: the author signing their own document legal Signed by
VRF verifier: a supervisor signing off a learner's document professional Signed off by
AUTHEN authenticator: a peer co-signing at the author's request professional Co-signed by

These are HL7's codes, used as three distinct functions rather than with v3's own distinctions: in v3, LA and AUTHEN are both kinds of VRF, and AUTHEN is a signer without privileges to legally authenticate (v3's example is a resident). Here a learner's own signature is LA, and the supervisor's approval is VRF. Match the code exactly; never test for a sign-off by subsumption under VRF, which would match every signature.

Every attester other than the author's legal signature carries the extension. An attester with mode legal and no extension is the author's signature. Read the label from the code, never from mode.

An attester records an attestation that has been given. One that has only been asked for -- a co-signature or a sign-off requested and not yet given -- is a task, not an attester.

Each attestation is its own entry, with its own party and time, and adding one changes nothing else on the document. A supervisor's sign-off also names the version of the note it approved, in nexus-attested-version, because a note is approved per version and an edit does not carry a sign-off forward. An attester is always a person, never a Device: software can author content, but it cannot take responsibility for it.

The rules for co-signature and sign-off -- how a request is raised, how a note reads as awaiting, signed off or returned, and how an edit withdraws a sign-off -- are in Clinical Documents.

Who has to review or attest

Nothing in this guide says which documents need a second attester or a reviewer. That is set outside it: by the clinic, by the program a learner trains in, and by professional regulation. The guide records what was done, and who did it, in a form every reader interprets the same way. It does not decide what should have been done.