The individual's own statement about information they asked to have corrected and the custodian
refused to correct.
Salient fields
The profile's synthesized-accessor contract: fields TypedFhir surfaces as first-class typed properties, each computed from the instance by a restricted FHIRPath expression. See Salient Fields for what they are, how they shape LLM contexts, and how to declare them.
The lifecycle of the MESSAGE, not of the obligation. completed means the statement was received
and recorded. It does not mean the matter is closed, and it has no bearing on whether the
statement must still be included in a disclosure -- it must.
entered-in-error is the only route to withdrawing a statement, and it must be used only where
the statement was recorded in error. An individual who wishes to change their statement supplies a
new one; the original remains in version history, because a custodian deleting an individual's
account of a dispute is the shape of the problem the right exists to prevent.
Comments
Internal chat writes completed on send. For eReferral traffic the partner's lifecycle applies and status is pass-through -- do not infer local workflow state from it.
Carries the HL7 correction vocabulary's disagreement code, so that a consumer scanning a patient's
Communications can find every statement of disagreement without knowing this guide's profile URL.
The parent profile leaves category unbound and text-tolerant. This profile requires a coded one,
because a statement nobody can find is a statement nobody will include.
Comments
⚠ FIRST PASS -- no value set is bound yet, deliberately. Binding one requires deciding the pass-through boundary first (a partner-supplied category must remain conformant), and that decision is not made. Until then this is text-or-code and readers MUST tolerate text-only. A local NexusEmrCommunicationCategoryVS is the intended follow-up.