HL7 FHIR Procedure Resource: US Core Profile, Status Codes, and CPT/SNOMED/ICD-10-PCS Mapping

The HL7 FHIR Procedure resource (Procedure) is the core Fast Healthcare Interoperability Resources (FHIR) clinical event structure used to record an action that is or was currently being performed on, with, or for a patient—spanning inpatient surgical operations, endoscopic and catheterization interventions, physical and occupational therapy sessions, bedside nursing actions, and counseling services. In U.S. health IT interoperability, Procedure is constrained by the US Core Procedure Profile under the US Core FHIR Implementation Guide to satisfy federal ONC certification criteria.

What Is FHIR Procedure and How Is It Used in Clinical Research and Healthcare?

Defined in the HL7 FHIR Release 4 specification (hl7.org/fhir/R4/procedure.html), Procedure models the event of a clinical intervention rather than the request or the diagnostic interpretation:

• Distinction from ServiceRequest and DiagnosticReport: A planned or ordered future procedure is represented by a FHIR ServiceRequest (which Procedure.basedOn references once execution begins), whereas narrative or structured findings from an imaging or pathology study are captured in DiagnosticReport or Observation.
• Core Structural Elements: Every Procedure links the intervention (code) and its lifecycle state (status) to a target FHIR Patient resource (subject), an optional FHIR Encounter resource (encounter), the timing of execution (performedDateTime, performedPeriod, or performedString), the operating clinician (performer.actor and performer.function), anatomical target (bodySite), clinical indication (reasonCode or reasonReference), and implanted/manipulated medical devices (focalDevice).
• Clinical Research & CDISC SDTM Mapping: In EHR-to-EDC clinical trial pipelines and HL7 Vulcan real-world data (RWD) studies, FHIR Procedure instances map directly to the CDISC SDTM Procedures (PR) domain (mapping Procedure.code to PRTRT/PRDECOD, performedPeriod.start to PRSTDTC, and performedPeriod.end to PRENDTC).

What Standards or Regulatory Requirements Govern FHIR Procedure?

Under the ONC Cures Act and HTI-1 Final Rules (45 CFR § 170.315(g)(10) and USCDI), certified electronic health record (EHR) APIs must expose patient procedures conforming to the US Core Procedure Profile:

US Core Element	Cardinality & Conformance	Binding / Invariant Rules
status	1..1 (Mandatory, Must Support)	Required binding to EventStatus: preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown. When status = not-done, statusReason (why the procedure was omitted) should be populated.
code	1..1 (Mandatory, Must Support)	Extensible binding to US Core Procedure Codes spanning SNOMED CT (http://snomed.info/sct), CPT (http://www.ama-assn.org/go/cpt), ICD-10-PCS (http://www.cms.gov/Medicare/Coding/ICD10-PCS), HCPCS Level II, CDT (dental), and LOINC.
subject	1..1 (Mandatory, Must Support)	Must reference a valid USCorePatientProfile instance (Patient/[id]).
performed[x]	0..1 (Must Support)	Enforced by invariant us-core-7: performedDateTime or performedPeriod SHALL be present whenever status is completed or in-progress.
basedOn, reasonCode, reasonReference	0..* (USCDI v3+ Must Support)	Links the procedure back to the originating order (ServiceRequest) and clinical indication (ICD-10-CM / SNOMED CT diagnosis).

How Does FHIR Procedure Integrate with EHR and Health Informatics Workflows?

In hospital perioperative systems (such as Epic OpTime or Oracle Health SurgiNet) and ambulatory billing engines, a single clinical procedure is often dual-coded inside Procedure.code.coding[]—pairing a clinical SNOMED CT concept with an institutional ICD-10-PCS code or professional AMA CPT code—and linked to any implanted Unique Device Identifier (UDI) via focalDevice:

{
  "resourceType": "Procedure",
  "id": "cardiac-pacemaker-implantation-01",
  "meta": {
    "profile": [
      "http://hl7.org/fhir/us/core/StructureDefinition/us-core-procedure"
    ]
  },
  "status": "completed",
  "code": {
    "coding": [
      {
        "system": "http://www.ama-assn.org/go/cpt",
        "code": "33208",
        "display": "Insertion of new or replacement of permanent pacemaker with transvenous electrodes; atrial and ventricular"
      },
      {
        "system": "http://snomed.info/sct",
        "code": "307280005",
        "display": "Implantation of cardiac pacemaker"
      }
    ],
    "text": "Dual-chamber permanent pacemaker implantation"
  },
  "subject": { "reference": "Patient/example-patient-101" },
  "encounter": { "reference": "Encounter/inpatient-stay-402" },
  "performedPeriod": {
    "start": "2026-11-08T09:15:00Z",
    "end": "2026-11-08T10:40:00Z"
  },
  "reasonCode": [{
    "coding": [{
      "system": "http://hl7.org/fhir/sid/icd-10-cm",
      "code": "I44.2",
      "display": "Atrioventricular block, complete"
    }]
  }],
  "focalDevice": [{
    "action": {
      "coding": [{
        "system": "http://snomed.info/sct",
        "code": "129326001",
        "display": "Insertion - action"
      }]
    },
    "manipulated": { "reference": "Device/udi-pacemaker-lead-88" }
  }]
}

Frequently Asked Questions

What is FHIR Procedure and how is it used in clinical research and healthcare?

The HL7 FHIR Procedure resource is a standardized clinical data model that records surgical operations, diagnostic interventions, therapies, and counseling performed on or for a patient, serving as the primary source for EHR surgical histories, quality measure denominators, and CDISC SDTM Procedures (PR) domain extraction in clinical trials.

What standards or regulatory requirements govern FHIR Procedure?

In the United States, FHIR Procedure exchange is governed by ONC certification criterion 45 CFR § 170.315(g)(10), the United States Core Data for Interoperability (USCDI), and the HL7 US Core Procedure Profile, which mandates EventStatus tracking, performed timestamps for completed procedures, and extensible bindings to SNOMED CT, CPT, ICD-10-PCS, HCPCS, CDT, and LOINC.

How does FHIR Procedure integrate with EHR and health informatics workflows?

EHRs generate FHIR Procedure resources from perioperative surgical logs, procedure notes, and CPT/ICD-10-PCS charge capture events, linking each procedure to the patient, encounter, ordering ServiceRequest, performing clinician, and any implanted UDI Device resource.