DSTU2 FHIR Release 3 (STU)

This page is part of the FHIR Specification (v1.0.2: DSTU (v3.0.2: STU 2). 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 R3 R2

Patient Care Work Group Maturity Level : 3   Trial Use Compartments : Encounter , Patient , Practitioner , RelatedPerson

Detailed Descriptions for the elements in the Procedure resource.

Is Modifier Type To Do Is this approach or target site? RIM mapping inconsistent with ProcedureRequest which lists target site. Recommend calling field targetBodySite or targetSite.
Procedure
Definition

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

Control 1..1
Invariants Defined on this element
pro-1 : Reason not performed done is only permitted if notPerformed notDone indicator is true (xpath: not(exists(f:reasonNotPerformed)) ( expression : notDoneReason.empty() or f:notPerformed/@value=true()) notDone = true, xpath: not(exists(f:notDoneReason)) or f:notDone/@value=true())
Procedure.identifier
Definition

This records identifiers associated with this procedure that are defined by business processes 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 Procedure.definition
Definition

The person, animal A protocol, guideline, orderset or group on which the procedure other definition that was performed. adhered to in whole or in part by this procedure.

Control 1..1 0..*
Type Reference ( Patient PlanDefinition | Group ActivityDefinition | HealthcareService )
Summary true
Procedure.status Procedure.basedOn
Definition

A code specifying the state reference to a resource that contains details of the procedure. Generally request for this will be in-progress or completed state. procedure.

Control 1..1 0..*
Binding Type ProcedureStatus: A code specifying the state of the procedure. Reference ( Required CarePlan ) Type | ProcedureRequest code | ReferralRequest )
Alternate Names true fulfills
Summary true
Procedure.category Procedure.partOf
Definition

A code that classifies the larger event of which this particular procedure for searching, sorting and display purposes (e.g. "Surgical Procedure"). is a component or step.

Control 0..1 0..*
Binding Type Procedure Category Codes (SNOMED CT): A code that classifies a procedure for searching, sorting and display purposes. Reference ( Example Procedure | Observation | MedicationAdministration )
Alternate Names CodeableConcept container
Summary true
Comments

The MedicationAdministration has a partOf reference to Procedure, but this is not a circular reference. For a surgical procedure, the anesthesia related medicationAdministration is part of the procedure. For an IV medication administration, the procedure to insert the IV port is part of the medication administration.

Procedure.code Procedure.status
Definition

The specific procedure that is performed. Use text if A code specifying the exact nature state of the procedure cannot procedure. Generally this will be coded (e.g. "Laparoscopic Appendectomy"). in-progress or completed state.

Control 1..1
Terminology Binding Procedure Codes (SNOMED CT): A code to identify a specific procedure . EventStatus ( Example Required )
Type CodeableConcept code
Is Modifier true
Summary true
Comments

The unknown code is not to be used to convey other statuses. The unknown code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure.

This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.

Procedure.notPerformed Procedure.notDone
Definition

Set this to true if the record is saying that the procedure was NOT performed.

Control 0..1
Type boolean
Is Modifier true
Default Value false
Summary true
Comments

If true, it means the procedure did not occur as described. Typically it would be accompanied by attributes describing the type of activity. It might also be accompanied by body site information or time information (i.e. no procedure was done to the left arm or no procedure was done in this 2-year period). Specifying additional information such as performer, outcome, etc. is generally inappropriate. For example, it's not that useful to say "There was no appendectomy done at 12:03pm June 6th by Dr. Smith with a successful outcome" as it implies that there could have been an appendectomy done at any other time, by any other clinician or with any other outcome.

This element is labeled as a modifier because it indicates that a procedure didn't happen.

Procedure.reasonNotPerformed Procedure.notDoneReason
Definition

A code indicating why the procedure was not performed.

Control 0..* 0..1
Terminology Binding Procedure Not Performed Reason (SNOMED-CT): A code that identifies the reason a procedure was not performed. (SNOMED-CT) ( Example )
Type CodeableConcept
Summary true
Invariants Affect this element
pro-1 : Reason not performed done is only permitted if notPerformed notDone indicator is true (xpath: not(exists(f:reasonNotPerformed)) ( expression : notDoneReason.empty() or f:notPerformed/@value=true()) notDone = true, xpath: not(exists(f:notDoneReason)) or f:notDone/@value=true())
Procedure.bodySite Procedure.category
Definition

Detailed A code that classifies the procedure for searching, sorting and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion. display purposes (e.g. "Surgical Procedure").

Control 0..* 0..1
Terminology Binding SNOMED CT Body Structures: Procedure Category Codes describing anatomical locations. May include laterality. (SNOMED CT) ( Example )
Type CodeableConcept
Summary true
Procedure.reason[x] Procedure.code
Definition

The reason why the specific procedure was that is performed. This may be due to a Condition, may be coded entity Use text if the exact nature of some type, or may simply the procedure cannot be present as text. coded (e.g. "Laparoscopic Appendectomy").

Control 0..1
Terminology Binding Procedure Reason Codes: A code that identifies the reason a procedure is required. Codes (SNOMED CT) ( Example )
Type CodeableConcept | Reference ( Condition )
[x] Note Requirements See Choice of Data Types for further information about how

0..1 to use [x] account for primarily narrative only resources.

Alternate Names type
Summary true
Procedure.subject
Comments Definition

e.g. endoscopy for dilatation and biopsy, combination diagnosis and therapeutic. The person, animal or group on which the procedure was performed.

Control 1..1
Type Reference ( Patient | Group )
Alternate Names patient
Summary true
Procedure.performer Procedure.context
Definition

Limited to 'real' people rather than equipment. The encounter during which the procedure was performed.

Control 0..* 0..1
Type Reference ( Encounter | EpisodeOfCare )
Alternate Names encounter
Summary true
Procedure.performer.actor Procedure.performed[x]
Definition

The practitioner who date(time)/period over which the procedure was involved in performed. Allows a period to support complex procedures that span more than one date, and also allows for the procedure. length of the procedure to be captured.

Control 0..1
Type Reference ( Practitioner dateTime | Organization Period | Patient
[x] Note See Choice of Data Types | RelatedPerson for further information about how to use [x]
Summary ) true
Procedure.performer
Definition

Limited to 'real' people rather than equipment.

Control 0..*
Summary true
Procedure.performer.role
Definition

For example: surgeon, anaethetist, endoscopist.

Control 0..1
Terminology Binding Procedure Performer Role Codes: A code that identifies the role of a performer of the procedure. Codes ( Example )
Type CodeableConcept
Summary true
Procedure.performed[x] Procedure.performer.actor
Definition

The date(time)/period over which the procedure practitioner who was performed. Allows a period to support complex procedures that span more than one date, and also allows for the length of involved in the procedure to be captured. procedure.

Control 0..1 1..1
Type dateTime Reference ( Practitioner | Period Organization | Patient | RelatedPerson | Device )
[x] Note Requirements See Choice of Data Types for further information about how

A reference to Device supports use [x] cases, such as pacemakers.

Summary true
Procedure.encounter Procedure.performer.onBehalfOf
Definition

The encounter during which organization the procedure device or practitioner was performed. acting on behalf of.

Control 0..1
Type Reference ( Encounter Organization )
Summary Requirements true

Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when performing the action.

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 )
Requirements

Ties a procedure to where the records are likely kept.

Summary true
Procedure.reasonCode
Definition

The coded reason why the procedure was performed. This may be coded entity of some type, or may simply be present as text.

Control 0..*
Terminology Binding Procedure Reason Codes ( Example )
Type CodeableConcept
Summary true
Procedure.reasonReference
Definition

The condition that is the reason why the procedure was performed.

Control 0..*
Type Reference ( Condition | Observation )
Summary true
Comments

e.g. endoscopy for dilatation and biopsy, combination diagnosis and therapeutic.

Procedure.bodySite
Definition

Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion.

Control 0..*
Terminology Binding SNOMED CT Body Structures ( Example )
Type CodeableConcept
Summary true
Procedure.outcome
Definition

The outcome of the procedure - did it resolve reasons for the procedure being performed?

Control 0..1
Terminology Binding Procedure Outcome Codes (SNOMED CT): An outcome of a procedure - whether it was resolved or otherwise. CT) ( Example )
Type CodeableConcept
Summary true
Comments

If outcome contains narrative text only, it can be captured using the CodeableConcept.text.

Procedure.report
Definition

This could be a histology result, pathology report, surgical report, etc..

Control 0..*
Type Reference ( DiagnosticReport )
Comments

There could potentially be multiple reports - e.g. if this was a procedure which took multiple biopsies resulting in a number of anatomical pathology reports.

Procedure.complication
Definition

Any complications that occurred during the procedure, or in the immediate post-performance period. These are generally tracked separately from the notes, which will typically describe the procedure itself rather than any 'post procedure' issues.

Control 0..*
Terminology Binding Condition/Problem/Diagnosis Codes: Condition/Problem/Diagnosis Codes describing complications that resulted from a procedure. ( Example )
Type CodeableConcept
Comments

If complications are only expressed by the narrative text, they can be captured using the CodeableConcept.text.

Procedure.complicationDetail
To Do Definition Need harmonization proposal

Any complications that occurred during the procedure, or in the immediate post-performance period.

Control 0..*
Type Reference ( Condition )
Requirements

This is used to document a condition that is a result of the procedure, not the condition that was the reason for new ActRelationshipType code. the procedure.

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 could potentially be more complex in which case the CarePlan resource can be used.

Control 0..*
Terminology Binding Procedure Follow up Codes (SNOMED CT): Specific follow up required for a procedure e.g. removal of sutures. CT) ( Example )
Type CodeableConcept
Procedure.request Definition A reference to a resource that contains details of the request for this procedure. Control 0..1 Type Reference ( CarePlan | DiagnosticOrder | ProcedureRequest | ReferralRequest ) Procedure.notes Procedure.note
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
Terminology Binding Procedure Device Action Codes: A kind of change that happened to the device during the procedure. Codes ( Required Preferred )
Type CodeableConcept
Procedure.focalDevice.manipulated
Definition

The device that was manipulated (changed) during the procedure.

Control 1..1
Type Reference ( Device )
Procedure.used Procedure.usedReference
Definition

Identifies medications, devices and any 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.

Procedure.usedCode
Definition

Identifies coded items that were used as part of the procedure.

Control 0..*
Terminology Binding FHIR Device Types ( Example )
Type CodeableConcept
Comments

For devices actually implanted or removed, use Procedure.device.