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 / Key elements
The working view: must-support, required, modifier and sliced elements from the effective (snapshot) definition.
| Element | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
| Communication | 0..* | Nexus EMR Communication Core Invariants: dom-2, dom-3, dom-4, dom-5, dom-6, nexus-note-extension-not-where-native, communication-has-category |
||
| meta | 0..1 | Meta | Metadata about the resource Invariants: ele-1 |
|
| source | S | 0..1 | uri | Identifies EMR instance & pipeline version the resource came from i Invariants: ele-1 |
| implicitRules | ?! | 0..1 | uri | A set of rules under which this content was created i Invariants: ele-1 |
| text | S | 0..1 | Narrative | Narrative i Invariants: ele-1 |
| identifier | 0..* | Identifier | Business identifier(s) for the communication i Invariants: ele-1 |
|
| use | ?! | 0..1 | code | usual | official | temp | secondary | old (If known) i Binding: identifier-use ( required)Invariants: ele-1 |
| system | 1..1 | uri | The namespace for the identifier value i Invariants: ele-1 |
|
| value | 1..1 | string | The value that is unique i Invariants: ele-1 |
|
| inResponseTo | S | 0..* | Reference(Communication Profile) | The message this one replies to i Invariants: ele-1 |
| status | S ?! | 1..1 | code | preparation | in-progress | not-done | completed | entered-in-error | ... i Binding: event-status ( required)Invariants: ele-1 |
| category | S | 0..* | CodeableConcept | Which population: internal staff chat, or external eReferral correspondence i Binding: communication-category ( example)Invariants: ele-1 |
| subject | S | 0..1 | Reference(Patient Profile) | The patient the communication is about i Invariants: ele-1 |
| sent | S | 0..1 | dateTime | When the message was sent Invariants: ele-1 |
| received | S | 0..1 | dateTime | When the message was received Invariants: ele-1 |
| recipient | S | 0..* | Reference(Practitioner Profile | PractitionerRole Profile | Patient Profile | RelatedPerson Profile | Organization Profile | CareTeam Profile) | Who the message was addressed to Invariants: ele-1 |
| sender | S | 0..1 | Reference(Practitioner Profile | PractitionerRole Profile | Patient Profile | RelatedPerson Profile | Organization Profile | App Device Profile) | Who sent the message i Invariants: ele-1 |
| payload | S | 0..* | BackboneElement | The message content i Invariants: ele-1 |
| content[x] | 1..1 | string, Attachment, Reference(Resource) | Message part content Invariants: ele-1 |