DSTU2 QA Preview

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

4.8.6 Resource Procedure - Detailed Descriptions

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.

Control1..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).

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Requirements

Need to allow connection to a wider workflow.

Summarytrue
Procedure.subject
Definition

The person on whom the procedure was performed.

Control1..1
TypeReference(Patient | Group)
Summarytrue
Procedure.status
Definition

A code specifying the state of the procedure record. Generally this will be in-progress or completed state.

Control1..1
BindingProcedureStatus: A code specifying the state of the procedure record (Required)
Typecode
Is Modifiertrue
Summarytrue
Procedure.category
Definition

A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure").

Control0..1
BindingProcedure Category Codes (SNOMED CT): A code that classifies a procedure for searching, sorting and display purposes (Example)
TypeCodeableConcept
Summarytrue
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").

Control1..1
BindingProcedure Codes (SNOMED CT): A code to identify a specific procedure (Example)
TypeCodeableConcept
Summarytrue
Procedure.notPerformed
Definition

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

Control0..1
Typeboolean
Is Modifiertrue
Meaning if MissingIf this is missing, then the procedure was performed
Procedure.reasonNotPerformed
Definition

A code indicating why the procedure was not performed.

Control0..*
BindingProcedure Not Performed Reason (SNOMED-CT): A code that explains a reason why a procedure was not performed (Example)
TypeCodeableConcept
InvariantsDefined 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.

Control0..*
BindingSNOMED CT Body Structures: Codes describing anatomical locations. May include laterality (Example)
TypeCodeableConcept
Summarytrue
To DoIs 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.

Control0..1
BindingProcedure Reason Codes: A code that explains a reason why a procedure is required. (Example)
TypeCodeableConcept|Reference(Condition)
[x] NoteSee Choice of Data Types for further information about how to use [x]
Summarytrue
Comments

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

Procedure.performer
Definition

Limited to 'real' people rather than equipment.

Control0..*
Summarytrue
Procedure.performer.actor
Definition

The practitioner who was involved in the procedure.

Control0..1
TypeReference(Practitioner | Organization | Patient | RelatedPerson)
Summarytrue
Procedure.performer.role
Definition

E.g. surgeon, anaethetist, endoscopist.

Control0..1
BindingProcedure Performer Role Codes: A code that identifies a role of a performer in a procedure process (Example)
TypeCodeableConcept
Summarytrue
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.

Control0..1
TypedateTime|Period
[x] NoteSee Choice of Data Types for further information about how to use [x]
Summarytrue
Procedure.encounter
Definition

The encounter during which the procedure was performed.

Control0..1
TypeReference(Encounter)
Summarytrue
Procedure.location
Definition

The location where the procedure actually happened. e.g. a newborn at home, a tracheostomy at a restaurant.

Control0..1
TypeReference(Location)
Summarytrue
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?

Control0..1
BindingProcedure Outcome Codes (SNOMED CT): An outcome of a procedure - whether it resolveed the reasons why the procedure was performed (Example)
TypeCodeableConcept
Summarytrue
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.

Control0..*
TypeReference(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.

Control0..*
TypeCodeableConcept
Comments

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

To DoNeed 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.

Control0..*
BindingProcedure Follow up Codes (SNOMED CT): Specific follow up required for a procedure e.g. removal of sutures (Example)
TypeCodeableConcept
Procedure.request
Definition

A reference to a resource that contains about this procedure's request.

Control0..1
TypeReference(CarePlan | DiagnosticOrder | ProcedureRequest | ReferralRequest)
Procedure.notes
Definition

Any other notes about the procedure - e.g. the operative notes.

Control0..*
TypeAnnotation
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.

Control0..*
Procedure.focalDevice.action
Definition

The kind of change that happened to the device during the procedure.

Control0..1
BindingProcedure Device Action Codes: A kind of change that happened to the device during the procedure (Required)
TypeCodeableConcept
Procedure.focalDevice.manipulated
Definition

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

Control1..1
TypeReference(Device)
Procedure.used
Definition

Identifies medications, devices and other substance used as part of the procedure.

Control0..*
TypeReference(Device | Medication | Substance)
Requirements

Used for tracking contamination, etc.

Comments

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