<status value="active"/> <kind value="operation"/> <date value="2026-08-06T13:29:38+00:00"/> <publisher value="Den telemedicinske infrastruktur (eHealth Infrastructure)"/> <contact> <name value="Den telemedicinske infrastruktur (eHealth Infrastructure)"/> <telecom> <system value="url"/> <value value="http://ehealth.sundhed.dk"/> </telecom> </contact> <description value="Sends a message to a [RelatedPerson](StructureDefinition-ehealth-relatedperson.html) associated with a video appointment ([ehealth-videoappointment](StructureDefinition-ehealth-videoappointment.html) or [ehealth-group-videoappointment](StructureDefinition-ehealth-group-videoappointment.html)) via the specified channel. The recipient must be a RelatedPerson listed as a participant on the target Appointment. The created [ehealth-message](StructureDefinition-ehealth-message.html) resource is system-generated; its `sender` is a contained Device representing the issuing system."/> <jurisdiction> <coding> <system value="urn:iso:std:iso:3166"/> <code value="DK"/> <display value="Denmark"/> </coding> </jurisdiction> <affectsState value="true"/> <code value="send-message"/> <comment value="The following preconditions must be satisfied — otherwise the operation returns `HTTP 400 Bad Request` with an OperationOutcome describing the violated rule: * `Appointment.meta.profile` is [ehealth-videoappointment](StructureDefinition-ehealth-videoappointment.html) or [ehealth-group-videoappointment](StructureDefinition-ehealth-group-videoappointment.html). * `Appointment.status` is `booked` or `pending`. * The `recipient` RelatedPerson is on `Appointment.participant[]` with `status` `accepted`, `tentative`, or `needs-action`. * `RelatedPerson.active` = `true`. * `RelatedPerson.period` has begun and has not ended. * `RelatedPerson.telecom[]` has exactly one element with `system` = `sms` and an [ehealth-telecom-purpose](StructureDefinition-ehealth-telecom-purpose.html) extension bound to `video-appointment-reminder-sms`. The operation is synchronous and idempotent only from the FHIR caller's point of view: every successful call dispatches a new outbound message and creates a new Communication. The returned Communication has `status` = `completed` on successful dispatch or `status` = `stopped` when the downstream gateway rejected the send (the resource is still persisted so the failed attempt is auditable)."/> <resource value="Appointment"/> <system value="false"/> <type value="false"/> <instance value="true"/> <parameter> <name value="recipient"/> <use value="in"/> <min value="1"/> <max value="1"/> <documentation value="The related person to receive the message. Must be listed as a participant on the target Appointment."/> <type value="Reference"/> <targetProfile value="http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-relatedperson"/> </parameter> <parameter> <name value="channel"/> <use value="in"/> <min value="1"/> <max value="1"/> <documentation value="The channel to use when sending the message."/> <type value="code"/> <binding> <strength value="required"/> <valueSet value="http://ehealth.sundhed.dk/vs/ehealth-message-channel"/> </binding> </parameter> <parameter> <name value="return"/> <use value="out"/> <min value="1"/> <max value="1"/> <documentation value="The created Communication resource, conforming to the [ehealth-message](StructureDefinition-ehealth-message.html) profile. `Communication.status` is `completed` on successful dispatch or `stopped` when the downstream gateway rejected the send."/> <type value="Communication"/> </parameter> </OperationDefinition>

Generated Narrative: OperationDefinition Appointment-send-message

URL: [base]/Appointment/[id]/$send-message

Parameters

Use Name Scope Cardinality Type Binding Documentation

recipient

1..1

Reference (ehealth-relatedperson)

The related person to receive the message. Must be listed as a participant on the target Appointment.

channel

1..1

code

eHealth Message Channel (Required)

The channel to use when sending the message.

OUT

return

1..1

Communication

The created Communication resource, conforming to the ehealth-message profile. Communication.status is completed on successful dispatch or stopped when the downstream gateway rejected the send.

The following preconditions must be satisfied — otherwise the operation returns HTTP 400 Bad Request with an OperationOutcome describing the violated rule:

Appointment.meta.profile is ehealth-videoappointment or ehealth-group-videoappointment.
Appointment.status is booked or pending.
The recipient RelatedPerson is on Appointment.participant[] with status accepted, tentative, or needs-action.
RelatedPerson.active = true.
RelatedPerson.period has begun and has not ended.
RelatedPerson.telecom[] has exactly one element with system = sms and an ehealth-telecom-purpose extension bound to video-appointment-reminder-sms.

The operation is synchronous and idempotent only from the FHIR caller's point of view: every successful call dispatches a new outbound message and creates a new Communication. The returned Communication has status = completed on successful dispatch or status = stopped when the downstream gateway rejected the send (the resource is still persisted so the failed attempt is auditable).