DSTU2 Ballot Source

This page is part of the FHIR Specification (v0.5.0: DSTU 2 Ballot 2). 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.patient
Definition

The person on whom the procedure was performed.

Control1..1
TypeReference(Patient)
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: Required: http://hl7.org/fhir/procedure-status (A code specifying the state of the procedure record)
Typecode
Summarytrue
Procedure.category
Definition

A code that classifies the procedure for searching, sorting and display purposes.

Control0..1
BindingProcedureCategory: Example: See http://hl7.org/fhir/vs/procedure-category (A code that classifies a procedure for searching, sorting and display purposes)
TypeCodeableConcept
Summarytrue
Procedure.type
Definition

The specific procedure that is performed. Use text if the exact nature of the procedure can't be coded.

Control1..1
BindingProcedureType: Example: See http://hl7.org/fhir/vs/procedure-type (A code for a type of procedure)
TypeCodeableConcept
Summarytrue
Procedure.bodySite
Definition

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

Control0..*
Summarytrue
To DoIs this approach or target site? RIM mapping inconsistent with ProcedureRequest which lists target site. Recommend calling field targetBodySite or targetSite.
Procedure.bodySite.site[x]
Definition

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

Control1..1
TypeCodeableConcept|Reference(BodySite)
Summarytrue
Procedure.indication
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..*
TypeCodeableConcept
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.person
Definition

The practitioner who was involved in the procedure.

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

E.g. surgeon, anaethetist, endoscopist.

Control0..1
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
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
BindingProcedureOutcome: Example: See http://hl7.org/fhir/vs/procedure-outcome (The outcome of a procedure - whether it resolveed the reasons why the procedure was performed)
TypeCodeableConcept
Summarytrue
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
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..*
BindingProcedureFollowUp: Example: See http://hl7.org/fhir/vs/procedure-followup (Specific follow up required for a procedure e.g. removal of sutures)
TypeCodeableConcept
Procedure.relatedItem
Definition

Procedures may be related to other items such as procedures or medications. For example treating wound dehiscence following a previous procedure.

Control0..*
Procedure.relatedItem.type
Definition

The nature of the relationship.

Control0..1
BindingProcedureRelationshipType: Required: http://hl7.org/fhir/procedure-relationship-type (The nature of the relationship with this procedure)
Typecode
To DoExisting codes sound like synonyms. Suggest caused-by and caused.
Procedure.relatedItem.target
Definition

The related item - e.g. a procedure.

Control0..1
TypeReference(AllergyIntolerance | CarePlan | Condition | DiagnosticReport | FamilyMemberHistory | ImagingStudy | Immunization | ImmunizationRecommendation | MedicationAdministration | MedicationDispense | MedicationPrescription | MedicationStatement | Observation | Procedure)
Procedure.notes
Definition

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

Control0..1
Typestring
Procedure.device
Definition

A device change during the procedure.

Control0..*
Procedure.device.action
Definition

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

Control0..1
BindingDeviceActionKind: Required: See http://hl7.org/fhir/vs/device-action (The kind of change that happened to the device during the procedure)
TypeCodeableConcept
Procedure.device.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.