This profile sets minimum expectations for the Procedure resource to record, search, and fetch procedures associated with a patient. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile.

Example Usage Scenarios:

The following are example usage scenarios for the US Core-Procedure profile:

• Query for procedures performed on a Patient
• Record or update a procedure performed on a Patient

Mandatory and Must Support Data Elements

The following data-elements are mandatory (i.e data MUST be present) or must be supported if the data is present in the sending system (Must Support definition). They are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.

Each Procedure must have:

1. a status
2. a code that identifies the type of procedure performed on the patient
3. a patient
4. when the procedure was performed

Profile specific implementation guidance:

• Procedure codes can be taken from SNOMED-CT, CPT, HCPCS II, ICD-10-PCS, or CDT.
• A procedure including an implantable device SHOULD use Procedure.focalDevice with a reference to the US Core Implantable Device Profile.

Examples

• procedure-rehab
• procedure-implant

• Text Summary
• Differential Table
• Snapshot Table
• Snapshot Table (Must Support)
• All

This structure is derived from Procedure

Name	Flags	Card.	Type	Description & Constraints
Procedure		0..*	Procedure	An action that is being or was performed on a patient
status	S	1..1	code	preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown Binding: EventStatus (required)
code	S	1..1	CodeableConcept	Procedure codes from SNOMED CT, CPT, HCPCS II, ICD-10PC, or CDT Binding: US Core Procedure Codes (required): Codes describing the type of Procedure
subject	S	1..1	Reference(US Core Patient Profile)	Who the procedure was performed on
performed[x]	S	1..1		When the procedure was performed
performedDateTime			dateTime S
performedPeriod			Period
Documentation for this format

Name	Flags	Card.	Type	Description & Constraints
Procedure		0..*	Procedure	An action that is being or was performed on a patient
id	Σ	0..1	string	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred) Max Binding: AllLanguages: A human language.
text		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	External Identifiers for this procedure
instantiatesCanonical	Σ	0..*	canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)	Instantiates FHIR protocol or definition
instantiatesUri	Σ	0..*	uri	Instantiates external protocol or definition
basedOn	Σ	0..*	Reference(CarePlan | ServiceRequest)	A request for this procedure
partOf	Σ	0..*	Reference(Procedure | Observation | MedicationAdministration)	Part of referenced event
status	?!SΣ	1..1	code	preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown Binding: EventStatus (required)
statusReason	Σ	0..1	CodeableConcept	Reason for current status Binding: ProcedureNotPerformedReason(SNOMED-CT) (example): A code that identifies the reason a procedure was not performed.
category	Σ	0..1	CodeableConcept	Classification of the procedure Binding: ProcedureCategoryCodes(SNOMEDCT) (example): A code that classifies a procedure for searching, sorting and display purposes.
code	SΣ	1..1	CodeableConcept	Procedure codes from SNOMED CT, CPT, HCPCS II, ICD-10PC, or CDT Binding: US Core Procedure Codes (required): Codes describing the type of Procedure
subject	SΣ	1..1	Reference(US Core Patient Profile)	Who the procedure was performed on
encounter	Σ	0..1	Reference(Encounter)	Encounter created as part of
performed[x]	SΣ	1..1		When the procedure was performed
performedDateTime			dateTime S
performedPeriod			Period
recorder	Σ	0..1	Reference(Patient | RelatedPerson | Practitioner | PractitionerRole)	Who recorded the procedure
asserter	Σ	0..1	Reference(Patient | RelatedPerson | Practitioner | PractitionerRole)	Person who asserts this procedure
performer	Σ	0..*	BackboneElement	The people who performed the procedure
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
function	Σ	0..1	CodeableConcept	Type of performance Binding: ProcedurePerformerRoleCodes (example): A code that identifies the role of a performer of the procedure.
actor	Σ	1..1	Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)	The reference to the practitioner
onBehalfOf		0..1	Reference(Organization)	Organization the device or practitioner was acting for
location	Σ	0..1	Reference(Location)	Where the procedure happened
reasonCode	Σ	0..*	CodeableConcept	Coded reason procedure performed Binding: ProcedureReasonCodes (example): A code that identifies the reason a procedure is required.
reasonReference	Σ	0..*	Reference(Condition | Observation | Procedure | DiagnosticReport | DocumentReference)	The justification that the procedure was performed
bodySite	Σ	0..*	CodeableConcept	Target body sites Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.
outcome	Σ	0..1	CodeableConcept	The result of procedure Binding: ProcedureOutcomeCodes(SNOMEDCT) (example): An outcome of a procedure - whether it was resolved or otherwise.
report		0..*	Reference(DiagnosticReport | DocumentReference | Composition)	Any report resulting from the procedure
complication		0..*	CodeableConcept	Complication following the procedure Binding: Condition/Problem/DiagnosisCodes (example): Codes describing complications that resulted from a procedure.
complicationDetail		0..*	Reference(Condition)	A condition that is a result of the procedure
followUp		0..*	CodeableConcept	Instructions for follow up Binding: ProcedureFollowUpCodes(SNOMEDCT) (example): Specific follow up required for a procedure e.g. removal of sutures.
note		0..*	Annotation	Additional information about the procedure
focalDevice		0..*	BackboneElement	Manipulated, implanted, or removed device
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
action		0..1	CodeableConcept	Kind of change to device Binding: ProcedureDeviceActionCodes (preferred): A kind of change that happened to the device during the procedure.
manipulated		1..1	Reference(Device)	Device that was changed
usedReference		0..*	Reference(Device | Medication | Substance)	Items used during procedure
usedCode		0..*	CodeableConcept	Coded items used during the procedure Binding: FHIRDeviceTypes (example): Codes describing items used during a procedure.
Documentation for this format

Name	Flags	Card.	Type	Description & Constraints
Procedure		0..*	Procedure	An action that is being or was performed on a patient
status	?!Σ	1..1	code	preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown Binding: EventStatus (required)
code	Σ	1..1	CodeableConcept	Procedure codes from SNOMED CT, CPT, HCPCS II, ICD-10PC, or CDT Binding: US Core Procedure Codes (required): Codes describing the type of Procedure
subject	Σ	1..1	Reference(US Core Patient Profile)	Who the procedure was performed on
performed[x]	Σ	1..1		When the procedure was performed
performedDateTime			dateTime
Documentation for this format

This structure is derived from Procedure

Summary

Mandatory: 4 elements
Must-Support: 4 elements

Structures

This structure refers to these other structures:

• http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient

Differential View

This structure is derived from Procedure

Name	Flags	Card.	Type	Description & Constraints
Procedure		0..*	Procedure	An action that is being or was performed on a patient
status	S	1..1	code	preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown Binding: EventStatus (required)
code	S	1..1	CodeableConcept	Procedure codes from SNOMED CT, CPT, HCPCS II, ICD-10PC, or CDT Binding: US Core Procedure Codes (required): Codes describing the type of Procedure
subject	S	1..1	Reference(US Core Patient Profile)	Who the procedure was performed on
performed[x]	S	1..1		When the procedure was performed
performedDateTime			dateTime S
performedPeriod			Period
Documentation for this format

Snapshot View

Name	Flags	Card.	Type	Description & Constraints
Procedure		0..*	Procedure	An action that is being or was performed on a patient
id	Σ	0..1	string	Logical id of this artifact
meta	Σ	0..1	Meta	Metadata about the resource
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
language		0..1	code	Language of the resource content Binding: CommonLanguages (preferred) Max Binding: AllLanguages: A human language.
text		0..1	Narrative	Text summary of the resource, for human interpretation
contained		0..*	Resource	Contained, inline Resources
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
identifier	Σ	0..*	Identifier	External Identifiers for this procedure
instantiatesCanonical	Σ	0..*	canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)	Instantiates FHIR protocol or definition
instantiatesUri	Σ	0..*	uri	Instantiates external protocol or definition
basedOn	Σ	0..*	Reference(CarePlan | ServiceRequest)	A request for this procedure
partOf	Σ	0..*	Reference(Procedure | Observation | MedicationAdministration)	Part of referenced event
status	?!SΣ	1..1	code	preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown Binding: EventStatus (required)
statusReason	Σ	0..1	CodeableConcept	Reason for current status Binding: ProcedureNotPerformedReason(SNOMED-CT) (example): A code that identifies the reason a procedure was not performed.
category	Σ	0..1	CodeableConcept	Classification of the procedure Binding: ProcedureCategoryCodes(SNOMEDCT) (example): A code that classifies a procedure for searching, sorting and display purposes.
code	SΣ	1..1	CodeableConcept	Procedure codes from SNOMED CT, CPT, HCPCS II, ICD-10PC, or CDT Binding: US Core Procedure Codes (required): Codes describing the type of Procedure
subject	SΣ	1..1	Reference(US Core Patient Profile)	Who the procedure was performed on
encounter	Σ	0..1	Reference(Encounter)	Encounter created as part of
performed[x]	SΣ	1..1		When the procedure was performed
performedDateTime			dateTime S
performedPeriod			Period
recorder	Σ	0..1	Reference(Patient | RelatedPerson | Practitioner | PractitionerRole)	Who recorded the procedure
asserter	Σ	0..1	Reference(Patient | RelatedPerson | Practitioner | PractitionerRole)	Person who asserts this procedure
performer	Σ	0..*	BackboneElement	The people who performed the procedure
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
function	Σ	0..1	CodeableConcept	Type of performance Binding: ProcedurePerformerRoleCodes (example): A code that identifies the role of a performer of the procedure.
actor	Σ	1..1	Reference(Practitioner | PractitionerRole | Organization | Patient | RelatedPerson | Device)	The reference to the practitioner
onBehalfOf		0..1	Reference(Organization)	Organization the device or practitioner was acting for
location	Σ	0..1	Reference(Location)	Where the procedure happened
reasonCode	Σ	0..*	CodeableConcept	Coded reason procedure performed Binding: ProcedureReasonCodes (example): A code that identifies the reason a procedure is required.
reasonReference	Σ	0..*	Reference(Condition | Observation | Procedure | DiagnosticReport | DocumentReference)	The justification that the procedure was performed
bodySite	Σ	0..*	CodeableConcept	Target body sites Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.
outcome	Σ	0..1	CodeableConcept	The result of procedure Binding: ProcedureOutcomeCodes(SNOMEDCT) (example): An outcome of a procedure - whether it was resolved or otherwise.
report		0..*	Reference(DiagnosticReport | DocumentReference | Composition)	Any report resulting from the procedure
complication		0..*	CodeableConcept	Complication following the procedure Binding: Condition/Problem/DiagnosisCodes (example): Codes describing complications that resulted from a procedure.
complicationDetail		0..*	Reference(Condition)	A condition that is a result of the procedure
followUp		0..*	CodeableConcept	Instructions for follow up Binding: ProcedureFollowUpCodes(SNOMEDCT) (example): Specific follow up required for a procedure e.g. removal of sutures.
note		0..*	Annotation	Additional information about the procedure
focalDevice		0..*	BackboneElement	Manipulated, implanted, or removed device
id		0..1	string	Unique id for inter-element referencing
extension		0..*	Extension	Additional content defined by implementations
modifierExtension	?!Σ	0..*	Extension	Extensions that cannot be ignored even if unrecognized
action		0..1	CodeableConcept	Kind of change to device Binding: ProcedureDeviceActionCodes (preferred): A kind of change that happened to the device during the procedure.
manipulated		1..1	Reference(Device)	Device that was changed
usedReference		0..*	Reference(Device | Medication | Substance)	Items used during procedure
usedCode		0..*	CodeableConcept	Coded items used during the procedure Binding: FHIRDeviceTypes (example): Codes describing items used during a procedure.
Documentation for this format

Quick Start

Below is an overview of the required set of Server RESTful FHIR interactions - for example, search and read operations - for this profile. See the Capability Statements for a complete list of supported RESTful interactions for this IG.

• The syntax used to describe the interactions is described here.
• See the General Guidance section for additional rules and expectations when a server requires status parameters.
• See the General Guidance section for additional guidance on searching for multiple patients.

Mandatory Search Parameters:

The following search parameters and search parameter combinations SHALL be supported.:

1. SHALL support searching for all procedures for a patient using the patient search parameter:

   GET [base]/Procedure?patient={Type/}[id]

   Example:

   1. GET [base]/Procedure?patient=1291938

   Implementation Notes: Fetches a bundle of all Procedure resources for the specified patient (how to search by reference)

2. SHALL support searching using the combination of the patient and date search parameters:

   • including support for these date comparators: gt,lt,ge,le
   • including optional support for composite AND search on date (e.g.date=[date]&date=[date]]&...)

   GET [base]/Procedure?patient={Type/}[id]&date={gt|lt|ge|le}[date]{&date={gt|lt|ge|le}[date]&...}

   Example:

   1. GET [base]/Procedure?patient=1137192&date=ge2019-01-14

   Implementation Notes: Fetches a bundle of all Procedure resources for the specified patient and date (how to search by reference and how to search by token)

Optional Search Parameters:

The following search parameter combinations SHOULD be supported.:

1. SHOULD support searching using the combination of the patient and status search parameters:
   • including support for composite OR search on status (e.g.status={system|}[code],{system|}[code],...)

   GET [base]/Procedure?patient={Type/}[id]&status={system|}[code]{,{system|}[code],...}

   Example:

   1. GET [base]/Procedure?patient=1137192&status=completed

   Implementation Notes: Fetches a bundle of all Procedure resources for the specified patient and status (how to search by reference and how to search by token)

2. SHOULD support searching using the combination of the patient and code and date search parameters:
   • including optional support for composite OR search on code (e.g.code={system|}[code],{system|}[code],...)
   • including support for these date comparators: gt,lt,ge,le
   • including optional support for composite AND search on date (e.g.date=[date]&date=[date]]&...)

   GET [base]/Procedure?patient={Type/}[id]&code={system|}[code]{,{system|}[code],...}&date={gt|lt|ge|le}[date]{&date={gt|lt|ge|le}[date]&...}

   Example:

   1. GET [base]/Procedure?patient=1137192&date=ge2019-01-14T00:00:00Z&code=http://snomed.info/sct|35637008

   Implementation Notes: Fetches a bundle of all Procedure resources for the specified patient and date and procedure code(s). SHOULD support search by multiple codes. (how to search by reference and how to search by token and how to search by date)