PATIENT ADMINISTRTAION (PA) Workgroup Development Draft

4.8 Resource Procedure - Content

This resource maintained by the Patient Care Work Group

An action that is or was performed on a patient. This can be a physical 'thing' like an operation, or less invasive like counseling or hypnotherapy.

4.8.1 Scope and Usage

This resource is used to record the details of procedures performed on a patient. A procedure is an activity that is performed with or on a patient as part of the provision of care. Examples include surgical procedures, diagnostic procedures, endoscopic procedures, biopsies, counselling, physiotherapy, exercise, etc. Procedures may be performed by a healthcare professional, a friend or relative or in some cases by the patient themselves.

This resource provides summary information about the occurrence of the procedure and is not intended to provide real-time snapshots of a procedure as it unfolds, though for long-running procedures such as psychotherapy, it could represent summary level information about overall progres. The creation of a resource to support detailed real-time procedure information awaits the identification of a specific implementation use-case to share such information.

4.8.2 Boundaries and Relationships

Procedures do not include actions things for which there are specific resources, such as immunizations, drug administrations and communications. The boundary between determining whether an action is considered to be training or counselling (and thus a procedure) as opposed to a Communication is based on whether there's a specific intent to change the mind-set of the patient. Mere disclosure of information would be considered a Communication. A process that involves verification of the patient's comprehension or to change the patient's mental state would be a Procedure.

Note that many diagnostic processes are procedures that generate Observations and DiagnosticReports. In many cases, such an observation does not require an explicit representation of the procedure used to create the observation, but where there are details of interest about how the diagnostic procedure was performed, the procedure resource is used to describe the activity.

This resource is referenced by ClinicalImpression, Condition and Observation

4.8.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Procedure DomainResourceAn action that was or is currently being performed on a patient
... identifier Σ0..*IdentifierExternal Ids for this procedure
... patient Σ1..1PatientWho procedure was performed on
... status Σ1..1codein-progress | aborted | completed | entered-in-error
ProcedureStatus (Required)
... category Σ0..1CodeableConceptClassification of the procedure
Procedure Category Codes (SNOMED CT) (Example)
... type Σ1..1CodeableConceptIdentification of the procedure
Procedure Type Codes (SNOMED CT) (Example)
... bodySite Σ0..*ElementPrecise location details
.... site[x] ΣPrecise location details
..... siteCodeableConcept1..1CodeableConcept
..... siteReference1..1BodySite
... indication Σ0..*CodeableConceptReason procedure performed
... performer Σ0..*ElementThe people who performed the procedure
.... person Σ0..1Practitioner | Patient | RelatedPersonThe reference to the practitioner
.... role Σ0..1CodeableConceptThe role the person was in
... performed[x] ΣDate/Period the procedure was performed
.... performedDateTime0..1dateTime
.... performedPeriod0..1Period
... encounter Σ0..1EncounterThe encounter when procedure performed
... location Σ0..1LocationWhere the procedure happened
... outcome Σ0..1CodeableConceptWhat was result of procedure?
Procedure Outcome Codes (SNOMED CT) (Example)
... report 0..*DiagnosticReportAny report that results from the procedure
... complication 0..*CodeableConceptComplication following the procedure
... followUp 0..*CodeableConceptInstructions for follow up
Procedure Follow up Codes (SNOMED CT) (Example)
... relatedItem 0..*ElementA procedure that is related to this one
.... type 0..1codecaused-by | because-of
ProcedureRelationshipType (Required)
.... target 0..1AllergyIntolerance | CarePlan | Condition | DiagnosticReport | FamilyMemberHistory | ImagingStudy | Immunization | ImmunizationRecommendation | MedicationAdministration | MedicationDispense | MedicationPrescription | MedicationStatement | Observation | ProcedureThe related item - e.g. a procedure
... notes 0..1stringAdditional information about procedure
... device 0..*ElementDevice changed in procedure
.... action 0..1CodeableConceptKind of change to device
Procedure Device Action Codes (Required)
.... manipulated 1..1DeviceDevice that was changed
... used 0..*Device | Medication | SubstanceItems used during procedure

UML Diagram

Procedure (DomainResource)This records identifiers associated with this procedure that are defined by business processed and/ or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation)identifier : Identifier 0..*The person on whom the procedure was performedpatient : Reference(Patient) 1..1A code specifying the state of the procedure record. Generally this will be in-progress or completed statestatus : code 1..1 « A code specifying the state of the procedure recordProcedureStatus »A code that classifies the procedure for searching, sorting and display purposescategory : CodeableConcept 0..1 « (A code that classifies a procedure for searching, sorting and display purposesProcedure Category Codes (SNOMED CT)) »The specific procedure that is performed. Use text if the exact nature of the procedure can't be codedtype : CodeableConcept 1..1 « (A code for a type of procedureProcedure Type Codes (SNOMED CT)) »The reason why the procedure was performed. This may be due to a Condition, may be coded entity of some type, or may simply be present as textindication : CodeableConcept 0..*The date(time)/period over which the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be capturedperformed[x] : dateTime|Period 0..1The encounter during which the procedure was performedencounter : Reference(Encounter) 0..1The location where the procedure actually happened. e.g. a newborn at home, a tracheostomy at a restaurantlocation : Reference(Location) 0..1What was the outcome of the procedure - did it resolve reasons why the procedure was performed?outcome : CodeableConcept 0..1 « (The outcome of a procedure - whether it resolveed the reasons why the procedure was performedProcedure Outcome Codes (SNOMED CT)) »This could be a histology result. There could potentially be multiple reports - e.g. if this was a procedure that made multiple biopsiesreport : Reference(DiagnosticReport) 0..*Any complications that occurred during the procedure, or in the immediate post-operative period. These are generally tracked separately from the notes, which typically will describe the procedure itself rather than any 'post procedure' issuescomplication : CodeableConcept 0..*If the procedure required specific follow up - e.g. removal of sutures. The followup may be represented as a simple note, or potentially could be more complex in which case the CarePlan resource can be usedfollowUp : CodeableConcept 0..* « (Specific follow up required for a procedure e.g. removal of suturesProcedure Follow up Codes (SNOMED CT)) »Any other notes about the procedure - e.g. the operative notesnotes : string 0..1Identifies medications, devices and other substance used as part of the procedureused : Reference(Device|Medication|Substance) 0..*BodySiteDetailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesionsite[x] : CodeableConcept|Reference(BodySite) 1..1PerformerThe practitioner who was involved in the procedureperson : Reference(Practitioner|Patient| RelatedPerson) 0..1E.g. surgeon, anaethetist, endoscopistrole : CodeableConcept 0..1RelatedItemThe nature of the relationshiptype : code 0..1 « The nature of the relationship with this procedureProcedureRelationshipType »The related item - e.g. a proceduretarget : Reference(AllergyIntolerance|CarePlan| Condition|DiagnosticReport| FamilyMemberHistory|ImagingStudy| Immunization|ImmunizationRecommendation| MedicationAdministration| MedicationDispense| MedicationPrescription| MedicationStatement|Observation| Procedure) 0..1DeviceThe kind of change that happened to the device during the procedureaction : CodeableConcept 0..1 « The kind of change that happened to the device during the procedureProcedure Device Action Codes »The device that was manipulated (changed) during the proceduremanipulated : Reference(Device) 1..1Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesionbodySite0..*Limited to 'real' people rather than equipmentperformer0..*Procedures may be related to other items such as procedures or medications. For example treating wound dehiscence following a previous procedurerelatedItem0..*A device change during the proceduredevice0..*

XML Template

<Procedure xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External Ids for this procedure --></identifier>
 <patient><!-- 1..1 Reference(Patient) Who procedure was performed on --></patient>
 <status value="[code]"/><!-- 1..1 in-progress | aborted | completed | entered-in-error -->
 <category><!-- 0..1 CodeableConcept Classification of the procedure --></category>
 <type><!-- 1..1 CodeableConcept Identification of the procedure --></type>
 <bodySite>  <!-- 0..* Precise location details -->
  <site[x]><!-- 1..1 CodeableConcept|Reference(BodySite) Precise location details --></site[x]>
 </bodySite>
 <indication><!-- 0..* CodeableConcept Reason procedure performed --></indication>
 <performer>  <!-- 0..* The people who performed the procedure -->
  <person><!-- 0..1 Reference(Practitioner|Patient|RelatedPerson) The reference to the practitioner --></person>
  <role><!-- 0..1 CodeableConcept The role the person was in --></role>
 </performer>
 <performed[x]><!-- 0..1 dateTime|Period Date/Period the procedure was performed --></performed[x]>
 <encounter><!-- 0..1 Reference(Encounter) The encounter when procedure performed --></encounter>
 <location><!-- 0..1 Reference(Location) Where the procedure happened --></location>
 <outcome><!-- 0..1 CodeableConcept What was result of procedure? --></outcome>
 <report><!-- 0..* Reference(DiagnosticReport) Any report that results from the procedure --></report>
 <complication><!-- 0..* CodeableConcept Complication following the procedure --></complication>
 <followUp><!-- 0..* CodeableConcept Instructions for follow up --></followUp>
 <relatedItem>  <!-- 0..* A procedure that is related to this one -->
  <type value="[code]"/><!-- 0..1 caused-by | because-of -->
  <target><!-- 0..1 Reference(AllergyIntolerance|CarePlan|Condition|
    DiagnosticReport|FamilyMemberHistory|ImagingStudy|Immunization|
    ImmunizationRecommendation|MedicationAdministration|MedicationDispense|
    MedicationPrescription|MedicationStatement|Observation|Procedure) The related item - e.g. a procedure --></target>
 </relatedItem>
 <notes value="[string]"/><!-- 0..1 Additional information about procedure -->
 <device>  <!-- 0..* Device changed in procedure -->
  <action><!-- 0..1 CodeableConcept Kind of change to device --></action>
  <manipulated><!-- 1..1 Reference(Device) Device that was changed --></manipulated>
 </device>
 <used><!-- 0..* Reference(Device|Medication|Substance) Items used during procedure --></used>
</Procedure>

JSON Template

{doco
  "resourceType" : "Procedure",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External Ids for this procedure
  "patient" : { Reference(Patient) }, // R!  Who procedure was performed on
  "status" : "<code>", // R!  in-progress | aborted | completed | entered-in-error
  "category" : { CodeableConcept }, // Classification of the procedure
  "type" : { CodeableConcept }, // R!  Identification of the procedure
  "bodySite" : [{ // Precise location details
    // site[x]: Precise location details. One of these 2:
    "siteCodeableConcept" : { CodeableConcept }
    "siteReference" : { Reference(BodySite) }
  }],
  "indication" : [{ CodeableConcept }], // Reason procedure performed
  "performer" : [{ // The people who performed the procedure
    "person" : { Reference(Practitioner|Patient|RelatedPerson) }, // The reference to the practitioner
    "role" : { CodeableConcept } // The role the person was in
  }],
  // performed[x]: Date/Period the procedure was performed. One of these 2:
  "performedDateTime" : "<dateTime>",
  "performedPeriod" : { Period },
  "encounter" : { Reference(Encounter) }, // The encounter when procedure performed
  "location" : { Reference(Location) }, // Where the procedure happened
  "outcome" : { CodeableConcept }, // What was result of procedure?
  "report" : [{ Reference(DiagnosticReport) }], // Any report that results from the procedure
  "complication" : [{ CodeableConcept }], // Complication following the procedure
  "followUp" : [{ CodeableConcept }], // Instructions for follow up
  "relatedItem" : [{ // A procedure that is related to this one
    "type" : "<code>", // caused-by | because-of
    "target" : { Reference(AllergyIntolerance|CarePlan|Condition|
    DiagnosticReport|FamilyMemberHistory|ImagingStudy|Immunization|
    ImmunizationRecommendation|MedicationAdministration|MedicationDispense|
    MedicationPrescription|MedicationStatement|Observation|Procedure) } // The related item - e.g. a procedure
  }],
  "notes" : "<string>", // Additional information about procedure
  "device" : [{ // Device changed in procedure
    "action" : { CodeableConcept }, // Kind of change to device
    "manipulated" : { Reference(Device) } // R!  Device that was changed
  }],
  "used" : [{ Reference(Device|Medication|Substance) }] // Items used during procedure
}

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Procedure DomainResourceAn action that was or is currently being performed on a patient
... identifier Σ0..*IdentifierExternal Ids for this procedure
... patient Σ1..1PatientWho procedure was performed on
... status Σ1..1codein-progress | aborted | completed | entered-in-error
ProcedureStatus (Required)
... category Σ0..1CodeableConceptClassification of the procedure
Procedure Category Codes (SNOMED CT) (Example)
... type Σ1..1CodeableConceptIdentification of the procedure
Procedure Type Codes (SNOMED CT) (Example)
... bodySite Σ0..*ElementPrecise location details
.... site[x] ΣPrecise location details
..... siteCodeableConcept1..1CodeableConcept
..... siteReference1..1BodySite
... indication Σ0..*CodeableConceptReason procedure performed
... performer Σ0..*ElementThe people who performed the procedure
.... person Σ0..1Practitioner | Patient | RelatedPersonThe reference to the practitioner
.... role Σ0..1CodeableConceptThe role the person was in
... performed[x] ΣDate/Period the procedure was performed
.... performedDateTime0..1dateTime
.... performedPeriod0..1Period
... encounter Σ0..1EncounterThe encounter when procedure performed
... location Σ0..1LocationWhere the procedure happened
... outcome Σ0..1CodeableConceptWhat was result of procedure?
Procedure Outcome Codes (SNOMED CT) (Example)
... report 0..*DiagnosticReportAny report that results from the procedure
... complication 0..*CodeableConceptComplication following the procedure
... followUp 0..*CodeableConceptInstructions for follow up
Procedure Follow up Codes (SNOMED CT) (Example)
... relatedItem 0..*ElementA procedure that is related to this one
.... type 0..1codecaused-by | because-of
ProcedureRelationshipType (Required)
.... target 0..1AllergyIntolerance | CarePlan | Condition | DiagnosticReport | FamilyMemberHistory | ImagingStudy | Immunization | ImmunizationRecommendation | MedicationAdministration | MedicationDispense | MedicationPrescription | MedicationStatement | Observation | ProcedureThe related item - e.g. a procedure
... notes 0..1stringAdditional information about procedure
... device 0..*ElementDevice changed in procedure
.... action 0..1CodeableConceptKind of change to device
Procedure Device Action Codes (Required)
.... manipulated 1..1DeviceDevice that was changed
... used 0..*Device | Medication | SubstanceItems used during procedure

UML Diagram

Procedure (DomainResource)This records identifiers associated with this procedure that are defined by business processed and/ or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation)identifier : Identifier 0..*The person on whom the procedure was performedpatient : Reference(Patient) 1..1A code specifying the state of the procedure record. Generally this will be in-progress or completed statestatus : code 1..1 « A code specifying the state of the procedure recordProcedureStatus »A code that classifies the procedure for searching, sorting and display purposescategory : CodeableConcept 0..1 « (A code that classifies a procedure for searching, sorting and display purposesProcedure Category Codes (SNOMED CT)) »The specific procedure that is performed. Use text if the exact nature of the procedure can't be codedtype : CodeableConcept 1..1 « (A code for a type of procedureProcedure Type Codes (SNOMED CT)) »The reason why the procedure was performed. This may be due to a Condition, may be coded entity of some type, or may simply be present as textindication : CodeableConcept 0..*The date(time)/period over which the procedure was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of the procedure to be capturedperformed[x] : dateTime|Period 0..1The encounter during which the procedure was performedencounter : Reference(Encounter) 0..1The location where the procedure actually happened. e.g. a newborn at home, a tracheostomy at a restaurantlocation : Reference(Location) 0..1What was the outcome of the procedure - did it resolve reasons why the procedure was performed?outcome : CodeableConcept 0..1 « (The outcome of a procedure - whether it resolveed the reasons why the procedure was performedProcedure Outcome Codes (SNOMED CT)) »This could be a histology result. There could potentially be multiple reports - e.g. if this was a procedure that made multiple biopsiesreport : Reference(DiagnosticReport) 0..*Any complications that occurred during the procedure, or in the immediate post-operative period. These are generally tracked separately from the notes, which typically will describe the procedure itself rather than any 'post procedure' issuescomplication : CodeableConcept 0..*If the procedure required specific follow up - e.g. removal of sutures. The followup may be represented as a simple note, or potentially could be more complex in which case the CarePlan resource can be usedfollowUp : CodeableConcept 0..* « (Specific follow up required for a procedure e.g. removal of suturesProcedure Follow up Codes (SNOMED CT)) »Any other notes about the procedure - e.g. the operative notesnotes : string 0..1Identifies medications, devices and other substance used as part of the procedureused : Reference(Device|Medication|Substance) 0..*BodySiteDetailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesionsite[x] : CodeableConcept|Reference(BodySite) 1..1PerformerThe practitioner who was involved in the procedureperson : Reference(Practitioner|Patient| RelatedPerson) 0..1E.g. surgeon, anaethetist, endoscopistrole : CodeableConcept 0..1RelatedItemThe nature of the relationshiptype : code 0..1 « The nature of the relationship with this procedureProcedureRelationshipType »The related item - e.g. a proceduretarget : Reference(AllergyIntolerance|CarePlan| Condition|DiagnosticReport| FamilyMemberHistory|ImagingStudy| Immunization|ImmunizationRecommendation| MedicationAdministration| MedicationDispense| MedicationPrescription| MedicationStatement|Observation| Procedure) 0..1DeviceThe kind of change that happened to the device during the procedureaction : CodeableConcept 0..1 « The kind of change that happened to the device during the procedureProcedure Device Action Codes »The device that was manipulated (changed) during the proceduremanipulated : Reference(Device) 1..1Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesionbodySite0..*Limited to 'real' people rather than equipmentperformer0..*Procedures may be related to other items such as procedures or medications. For example treating wound dehiscence following a previous procedurerelatedItem0..*A device change during the proceduredevice0..*

XML Template

<Procedure xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier External Ids for this procedure --></identifier>
 <patient><!-- 1..1 Reference(Patient) Who procedure was performed on --></patient>
 <status value="[code]"/><!-- 1..1 in-progress | aborted | completed | entered-in-error -->
 <category><!-- 0..1 CodeableConcept Classification of the procedure --></category>
 <type><!-- 1..1 CodeableConcept Identification of the procedure --></type>
 <bodySite>  <!-- 0..* Precise location details -->
  <site[x]><!-- 1..1 CodeableConcept|Reference(BodySite) Precise location details --></site[x]>
 </bodySite>
 <indication><!-- 0..* CodeableConcept Reason procedure performed --></indication>
 <performer>  <!-- 0..* The people who performed the procedure -->
  <person><!-- 0..1 Reference(Practitioner|Patient|RelatedPerson) The reference to the practitioner --></person>
  <role><!-- 0..1 CodeableConcept The role the person was in --></role>
 </performer>
 <performed[x]><!-- 0..1 dateTime|Period Date/Period the procedure was performed --></performed[x]>
 <encounter><!-- 0..1 Reference(Encounter) The encounter when procedure performed --></encounter>
 <location><!-- 0..1 Reference(Location) Where the procedure happened --></location>
 <outcome><!-- 0..1 CodeableConcept What was result of procedure? --></outcome>
 <report><!-- 0..* Reference(DiagnosticReport) Any report that results from the procedure --></report>
 <complication><!-- 0..* CodeableConcept Complication following the procedure --></complication>
 <followUp><!-- 0..* CodeableConcept Instructions for follow up --></followUp>
 <relatedItem>  <!-- 0..* A procedure that is related to this one -->
  <type value="[code]"/><!-- 0..1 caused-by | because-of -->
  <target><!-- 0..1 Reference(AllergyIntolerance|CarePlan|Condition|
    DiagnosticReport|FamilyMemberHistory|ImagingStudy|Immunization|
    ImmunizationRecommendation|MedicationAdministration|MedicationDispense|
    MedicationPrescription|MedicationStatement|Observation|Procedure) The related item - e.g. a procedure --></target>
 </relatedItem>
 <notes value="[string]"/><!-- 0..1 Additional information about procedure -->
 <device>  <!-- 0..* Device changed in procedure -->
  <action><!-- 0..1 CodeableConcept Kind of change to device --></action>
  <manipulated><!-- 1..1 Reference(Device) Device that was changed --></manipulated>
 </device>
 <used><!-- 0..* Reference(Device|Medication|Substance) Items used during procedure --></used>
</Procedure>

JSON Template

{doco
  "resourceType" : "Procedure",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // External Ids for this procedure
  "patient" : { Reference(Patient) }, // R!  Who procedure was performed on
  "status" : "<code>", // R!  in-progress | aborted | completed | entered-in-error
  "category" : { CodeableConcept }, // Classification of the procedure
  "type" : { CodeableConcept }, // R!  Identification of the procedure
  "bodySite" : [{ // Precise location details
    // site[x]: Precise location details. One of these 2:
    "siteCodeableConcept" : { CodeableConcept }
    "siteReference" : { Reference(BodySite) }
  }],
  "indication" : [{ CodeableConcept }], // Reason procedure performed
  "performer" : [{ // The people who performed the procedure
    "person" : { Reference(Practitioner|Patient|RelatedPerson) }, // The reference to the practitioner
    "role" : { CodeableConcept } // The role the person was in
  }],
  // performed[x]: Date/Period the procedure was performed. One of these 2:
  "performedDateTime" : "<dateTime>",
  "performedPeriod" : { Period },
  "encounter" : { Reference(Encounter) }, // The encounter when procedure performed
  "location" : { Reference(Location) }, // Where the procedure happened
  "outcome" : { CodeableConcept }, // What was result of procedure?
  "report" : [{ Reference(DiagnosticReport) }], // Any report that results from the procedure
  "complication" : [{ CodeableConcept }], // Complication following the procedure
  "followUp" : [{ CodeableConcept }], // Instructions for follow up
  "relatedItem" : [{ // A procedure that is related to this one
    "type" : "<code>", // caused-by | because-of
    "target" : { Reference(AllergyIntolerance|CarePlan|Condition|
    DiagnosticReport|FamilyMemberHistory|ImagingStudy|Immunization|
    ImmunizationRecommendation|MedicationAdministration|MedicationDispense|
    MedicationPrescription|MedicationStatement|Observation|Procedure) } // The related item - e.g. a procedure
  }],
  "notes" : "<string>", // Additional information about procedure
  "device" : [{ // Device changed in procedure
    "action" : { CodeableConcept }, // Kind of change to device
    "manipulated" : { Reference(Device) } // R!  Device that was changed
  }],
  "used" : [{ Reference(Device|Medication|Substance) }] // Items used during procedure
}

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON)

4.8.3.1 Terminology Bindings

PathDefinitionTypeReference
Procedure.status A code specifying the state of the procedure recordRequiredhttp://hl7.org/fhir/procedure-status
Procedure.category A code that classifies a procedure for searching, sorting and display purposesExamplehttp://hl7.org/fhir/vs/procedure-category
Procedure.type A code for a type of procedureExamplehttp://hl7.org/fhir/vs/procedure-type
Procedure.outcome The outcome of a procedure - whether it resolveed the reasons why the procedure was performedExamplehttp://hl7.org/fhir/vs/procedure-outcome
Procedure.followUp Specific follow up required for a procedure e.g. removal of suturesExamplehttp://hl7.org/fhir/vs/procedure-followup
Procedure.relatedItem.type The nature of the relationship with this procedureRequiredhttp://hl7.org/fhir/procedure-relationship-type
Procedure.device.action The kind of change that happened to the device during the procedureRequiredhttp://hl7.org/fhir/vs/device-action

4.8.4 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
datedateDate/Period the procedure was performedProcedure.performed[x]
encounterreferenceThe encounter when procedure performedProcedure.encounter
(Encounter)
locationreferenceWhere the procedure happenedProcedure.location
(Location)
patientreferenceThe identity of a patient to list procedures forProcedure.patient
(Patient)
performerreferenceThe reference to the practitionerProcedure.performer.person
(Practitioner, Patient, RelatedPerson)
typetokenType of procedureProcedure.type