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.
For an outbound delivery, status is the delivery lifecycle:
- queued, not yet accepted by the delivery service: preparation
- accepted by the delivery service: in-progress
- delivered: completed
- failed for good: not-done, with statusReason carrying the delivery service's error code and text
- cancelled before the delivery service accepted it: not-done
- cancelled after the delivery service accepted it: stoppedsent is when the delivery service accepted the message, and received is when it reported delivery. A retry after failure is a new Communication whose basedOn names the attempt it repeats; a failed attempt keeps not-done.
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 binds category extensible and tolerates text-only. This profile requires a
coded one, because a statement nobody can find is a statement nobody will include.
Comments
Bound extensible to nexus-communication-category, which includes every HL7 communication-category code (staff chat writes notification) plus this guide's outbound-delivery. Extensible because the pass-through boundary is not yet decided: a partner-supplied category, and the Patient Request for Corrections codes a statement of disagreement carries, must stay conformant. Readers MUST still tolerate a text-only category, and must not treat an unrecognized one as invalid.