This page is part of the FHIR Specification (v1.0.0: DSTU 2 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2
Detailed Descriptions for the elements in the Procedure resource.
Procedure | |
Definition | 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. |
Control | 1..1 |
Procedure.identifier | |
Definition | 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). |
Note | This is a business identifer, not a resource identifier (see discussion) |
Control | 0..* |
Type | Identifier |
Requirements | Need to allow connection to a wider workflow. |
Summary | true |
Procedure.subject | |
Definition | The person on whom the procedure was performed. |
Control | 1..1 |
Type | Reference(Patient | Group) |
Summary | true |
Procedure.status | |
Definition | A code specifying the state of the procedure record. Generally this will be in-progress or completed state. |
Control | 1..1 |
Binding | ProcedureStatus: A code specifying the state of the procedure record (Required) |
Type | code |
Is Modifier | true |
Summary | true |
Procedure.category | |
Definition | A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure"). |
Control | 0..1 |
Binding | Procedure Category Codes (SNOMED CT): A code that classifies a procedure for searching, sorting and display purposes (Example) |
Type | CodeableConcept |
Summary | true |
Procedure.code | |
Definition | The specific procedure that is performed. Use text if the exact nature of the procedure can't be coded (e.g. "Laparoscopic Appendectomy"). |
Control | 1..1 |
Binding | Procedure Codes (SNOMED CT): A code to identify a specific procedure (Example) |
Type | CodeableConcept |
Summary | true |
Procedure.notPerformed | |
Definition | Set this to true if the record is saying that the procedure was NOT performed. |
Control | 0..1 |
Type | boolean |
Is Modifier | true |
Meaning if Missing | If this is missing, then the procedure was performed |
Procedure.reasonNotPerformed | |
Definition | A code indicating why the procedure was not performed. |
Control | 0..* |
Binding | Procedure Not Performed Reason (SNOMED-CT): A code that explains a reason why a procedure was not performed (Example) |
Type | CodeableConcept |
Invariants | Defined on this element pro-1: Reason not performed is only permitted if notPerformed indicator is true (xpath: not(exists(f:reasonNotPerformed) and f:notPerformed/@value='false')) Affect this element |
Procedure.bodySite | |
Definition | Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion. |
Control | 0..* |
Binding | SNOMED CT Body Structures: Codes describing anatomical locations. May include laterality (Example) |
Type | CodeableConcept |
Summary | true |
To Do | Is this approach or target site? RIM mapping inconsistent with ProcedureRequest which lists target site. Recommend calling field targetBodySite or targetSite. |
Procedure.reason[x] | |
Definition | 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 text. |
Control | 0..1 |
Binding | Procedure Reason Codes: A code that explains a reason why a procedure is required. (Example) |
Type | CodeableConcept|Reference(Condition) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Summary | true |
Comments | e.g. endoscopy for dilatation and biopsy, combination diagnosis and therapuetic. |
Procedure.performer | |
Definition | Limited to 'real' people rather than equipment. |
Control | 0..* |
Summary | true |
Procedure.performer.actor | |
Definition | The practitioner who was involved in the procedure. |
Control | 0..1 |
Type | Reference(Practitioner | Organization | Patient | RelatedPerson) |
Summary | true |
Procedure.performer.role | |
Definition | E.g. surgeon, anaethetist, endoscopist. |
Control | 0..1 |
Binding | Procedure Performer Role Codes: A code that identifies a role of a performer in a procedure process (Example) |
Type | CodeableConcept |
Summary | true |
Procedure.performed[x] | |
Definition | 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 captured. |
Control | 0..1 |
Type | dateTime|Period |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Summary | true |
Procedure.encounter | |
Definition | The encounter during which the procedure was performed. |
Control | 0..1 |
Type | Reference(Encounter) |
Summary | true |
Procedure.location | |
Definition | The location where the procedure actually happened. e.g. a newborn at home, a tracheostomy at a restaurant. |
Control | 0..1 |
Type | Reference(Location) |
Summary | true |
Comments | Ties a procedure to where the records are kept. |
Procedure.outcome | |
Definition | What was the outcome of the procedure - did it resolve reasons why the procedure was performed? |
Control | 0..1 |
Binding | Procedure Outcome Codes (SNOMED CT): An outcome of a procedure - whether it resolveed the reasons why the procedure was performed (Example) |
Type | CodeableConcept |
Summary | true |
Comments | If outcome contains the narrative text only, it can be captured using the CodeableConcept.text. |
Procedure.report | |
Definition | This could be a histology result. There could potentially be multiple reports - e.g. if this was a procedure that made multiple biopsies. |
Control | 0..* |
Type | Reference(DiagnosticReport) |
Procedure.complication | |
Definition | 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' issues. |
Control | 0..* |
Type | CodeableConcept |
Comments | If complications are only expressed by the narrative text, it can be captured using the CodeableConcept.text. |
To Do | Need harmonization proposal for new ActRelationshipType code. |
Procedure.followUp | |
Definition | 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 used. |
Control | 0..* |
Binding | Procedure Follow up Codes (SNOMED CT): Specific follow up required for a procedure e.g. removal of sutures (Example) |
Type | CodeableConcept |
Procedure.request | |
Definition | A reference to a resource that contains about this procedure's request. |
Control | 0..1 |
Type | Reference(CarePlan | DiagnosticOrder | ProcedureRequest | ReferralRequest) |
Procedure.notes | |
Definition | Any other notes about the procedure - e.g. the operative notes. |
Control | 0..* |
Type | Annotation |
Procedure.focalDevice | |
Definition | A device that is implanted, removed or otherwise manipulated (calibration, battery replacement, fitting a prosthesis, attaching a wound-vac, etc.) as a focal portion of the Procedure. |
Control | 0..* |
Procedure.focalDevice.action | |
Definition | The kind of change that happened to the device during the procedure. |
Control | 0..1 |
Binding | Procedure Device Action Codes: A kind of change that happened to the device during the procedure (Required) |
Type | CodeableConcept |
Procedure.focalDevice.manipulated | |
Definition | The device that was manipulated (changed) during the procedure. |
Control | 1..1 |
Type | Reference(Device) |
Procedure.used | |
Definition | Identifies medications, devices and other substance used as part of the procedure. |
Control | 0..* |
Type | Reference(Device | Medication | Substance) |
Requirements | Used for tracking contamination, etc. |
Comments | For devices actually implanted or removed, use Procedure.device. |