CommunicationRequest resource (FHIR R4)
CommunicationRequest is the FHIR R4 resource for a request to convey information; e.g.
| Resource | CommunicationRequest |
|---|---|
| FHIR version | R4 (4.0.1) |
| Canonical URL | http://hl7.org/fhir/StructureDefinition/CommunicationRequest |
| Required elements | status (1..1) |
| IG profiles in this catalog | 2 |
Example
{
"resourceType": "CommunicationRequest",
"id": "communicationrequest-ab73a01617fe6bb9379a209dcca2d706",
"status": "active",
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/communication-category",
"code": "reminder",
"display": "Reminder"
}
]
}
],
"priority": "routine",
"medium": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ParticipationMode",
"code": "PHONE",
"display": "telephone"
}
]
}
],
"subject": {
"reference": "Patient/patient-L46A6EIB9J"
},
"payload": [
{
"contentString": "Notify the patient that updated visit instructions are available."
}
],
"authoredOn": "2026-07-01T12:00:00Z",
"requester": {
"display": "Care Coordination Desk"
},
"recipient": [
{
"display": "Patient Outreach Team"
}
]
}Generated by the Pidgeon engine: pidgeon generate CommunicationRequest --seed 20260722.
Validation context
- strict pidgeon validate grades a CommunicationRequest instance against the base R4 structure definition: missing required elements raise REQUIRED_FIELD_MISSING and cardinality violations raise CARDINALITY_MIN or CARDINALITY_MAX.(REQUIRED_FIELD_MISSING)
- strict Profile validation grades the same instance against an installed IG profile: profile cardinality findings carry FHIR-PROFILE-CARDINALITY and terminology binding findings carry FHIR-PROFILE-BINDING.(FHIR-PROFILE-CARDINALITY)
This answer, in your terminal
pidgeon lookup CommunicationRequestWire it into your AI agent:
claude mcp add pidgeon -- npx -y @pidgeonhealth/mcpDownload Post free to browse this reference with generation attached.