What kind of attestation this Composition.attester is: the author's own signature, a supervisor's
sign-off on a learner's note, or a peer's co-signature. R4's attester.mode cannot say: both a
sign-off and a co-signature are professional.
What kind of attestation this is: LA | VRF | AUTHEN
Definition
What kind of attestation this Composition.attester is: the author's own signature, a supervisor's
sign-off on a learner's note, or a peer's co-signature. R4's attester.mode cannot say: both a
sign-off and a co-signature are professional.
Codes are HL7's.LA (legal authenticator) is the author signing their own note; VRF
(verifier) is a supervisor signing off a learner's note; AUTHEN (authenticator) is a peer
co-signing at the author's request. A display reads from the code, never from mode: VRF reads
"Signed off by", AUTHEN "Co-signed by".
Every attester other than the author's legal signature carries it, so a sign-off and a
co-signature can never be confused. Each sign-off is its own attester: party is the supervisor,
time is when they signed off, and a note can carry several over time. A sign-off also names the
version it approved, in nexus-attested-version.
Adding one changes nothing else on the note.
How these codes are used here, against their v3 definitions. In v3 ParticipationType, LA and
AUTHEN are both specializations of VRF, and v3 tells them apart by signing privilege: AUTHEN is a
signer without privileges to legally authenticate (v3's example is a resident signing their own
note) and LA is one with them. This guide uses the three as distinct functions instead: LA is the
author's own signature, VRF a supervisor's sign-off, AUTHEN a peer's co-signature, and a learner
who signs their own note is LA here. Two consequences for a reader: do not test for a sign-off by
subsumption under VRF, which would match every signature -- match the code exactly; and when mapping
to CDA, the LA attester is the legalAuthenticator and the others are authenticators, whatever
v3's examples suggest.
An attestation is not a review. An attester takes professional responsibility for the note under
their own name. A clinician who has only received and read something is a reviewer, recorded with
nexus-emr-reviewed, and is not an attester. See
Review and attestation.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.