Procedure resource (FHIR R4)
Procedure is a FHIR R4 resource. The Pidgeon engine generates synthetic Procedure instances and validates them against the R4 structure definitions.
| Resource | Procedure |
|---|---|
| FHIR version | R4 (4.0.1) |
| Canonical URL | http://hl7.org/fhir/StructureDefinition/Procedure |
| Required elements | status (1..1), subject (1..1) |
| IG profiles in this catalog | 1 |
Example
{
"resourceType": "Procedure",
"id": "procedure-633290a318844135e391dee9e9c324bc",
"status": "completed",
"code": {
"coding": [
{
"system": "http://www.ama-assn.org/go/cpt",
"code": "omitted",
"display": "CPT code omitted from this published example"
},
{
"system": "http://snomed.info/sct",
"code": "omitted",
"display": "SNOMED CT code omitted from this published example"
}
],
"text": "Colonoscopy"
},
"subject": {
"reference": "Patient/patient-L46A6EIB9J"
},
"performedDateTime": "2026-04-18T12:00:00Z"
}Generated by the Pidgeon engine: pidgeon generate Procedure --seed 20260722. Codes from licensed terminologies (LOINC, SNOMED CT, CPT, RxNorm) are omitted from published examples.
Validation context
- strict pidgeon validate grades a Procedure 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 ProcedureWire it into your AI agent:
claude mcp add pidgeon -- npx -y @pidgeonhealth/mcpDownload Post free to browse this reference with generation attached.