Nexus EMR profile for Communication, covering three distinct populations: WELL-internal staff chat about a patient, eReferral correspondence passed through from or to external partners, and outbound delivery (one fax, SMS or email sent to one recipient through a delivery service). First pass -- the pass-through boundary and message threading are not yet settled.
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.
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.
Which population: internal staff chat, or external eReferral correspondence
Definition
Which population this Communication belongs to. Readers should scope on it -- internal chat and
external eReferral correspondence have different authorities over their content, and a chat surface
that does not scope will surface partner correspondence into a panel never designed for it.
Outbound delivery is not chat. A Communication carrying outbound-delivery from
nexus-communication-category records a fax, SMS or email sent through a delivery service. A chat
surface must exclude it, including one that today selects everything that is not eReferral.
⚠ HERITAGE EMR SITUATION -- UNRESOLVED. If heritage-EMR message history is ever migrated (see
identifier), it becomes a THIRD population alongside internal chat and eReferral, and this element
is where that distinction would have to live. No code for it exists, because the migration decision
has not been made. Anyone binding a value set here must resolve that first, or the binding will need
widening the moment migration is agreed.
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.