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.
Access
What the endpoint offers¶
Communication is modelled by this IG but is not offered as an API surface.
No capability statement in this IG names Communication, so there are no interactions and no search parameters declared for it. This IG publishes Server Capability Statement; profiling a resource and offering it are two different decisions, and each statement's own description says which types it covers and which it deliberately leaves out.
SMART on FHIR scopes¶
A SMART on FHIR app cannot reach Communication.
This is the default, not an omission. A resource is unreachable unless its profile declares smart-exposed, because profiling a resource and exposing it to a third-party app are two different decisions: the first is modelling, the second is authorization. No scope naming Communication will be granted, and a wildcard scope (patient/*.rs) does not expand over it.