Nexus EMR profile for Communication, covering two distinct populations: WELL-internal staff chat about a patient, and eReferral correspondence passed through from or to external partners. First pass -- the pass-through boundary and message threading are not yet settled.
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.
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.
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.
⚠ 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
⚠ 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.