Communication Profile

Canonical	../StructureDefinition/nexus-emr-core-communication
Status	draft (experimental) · 1.26.0
Base	Communication (constraint)
Source	FSH · JSON

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.

Elements / Differential

What this profile constrains beyond Communication. Anything not listed is unchanged from the base; muted type/cardinality values are the base's, shown for context.

Element	Flags	Card.	Type	Description & Constraints
Communication				Nexus EMR Communication Core Invariants: nexus-note-extension-not-where-native, communication-has-category
meta		0..1	Meta
source	S	0..1	uri	Identifies EMR instance & pipeline version the resource came from i
text	S	0..1	Narrative	Narrative i
identifier		0..*	Identifier	Business identifier(s) for the communication i
system		1..1	uri	i
value		1..1	string	i
inResponseTo	S	0..*	Reference(Communication Profile)	The message this one replies to i
status	S	1..1	code	preparation | in-progress | not-done | completed | entered-in-error | ... i
category	S	0..*	CodeableConcept	Which population: internal staff chat, or external eReferral correspondence i
subject	S	0..1	Reference(Patient Profile)	The patient the communication is about i
sent	S	0..1	dateTime	When the message was sent
received	S	0..1	dateTime	When the message was received
recipient	S	0..*	Reference(Practitioner Profile | PractitionerRole Profile | Patient Profile | RelatedPerson Profile | Organization Profile | CareTeam Profile)	Who the message was addressed to
sender	S	0..1	Reference(Practitioner Profile | PractitionerRole Profile | Patient Profile | RelatedPerson Profile | Organization Profile | App Device Profile)	Who sent the message i
payload	S	0..*	BackboneElement	The message content i