Skip to content

Communication Request Profile

Canonicalhttps://fhir.apps.health/StructureDefinition/nexus-core-communicationrequest
Statusdraft · 1.33.0
BaseCommunicationRequest (constraint)
SourceFSH · JSON

The request a client submits to send one message by fax, SMS or email: to which recipients, by which channel and sending account, and what to send. It is the input to the message exchange service's $send-message operation, validated against this profile and not stored. Each send is recorded as an outbound-delivery Communication. One channel, or fax with email. Recipients are contained Organizations holding the name and address to use. First pass.

Access

What the endpoint offers

CommunicationRequest is modelled by this IG but is not offered as an API surface.

No capability statement in this IG names CommunicationRequest, 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 CommunicationRequest.

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 CommunicationRequest will be granted, and a wildcard scope (patient/*.rs) does not expand over it.