Procedure
An action that is or was performed on or for a patient. This can be a physical intervention like an operation, or less invasive like long term services, counseling, or hypnotherapy. If the element is present, it must have either a @value, an @id, or extensions
type Procedure implements Resource {
identifier: [Identifier]
instantiatesCanonical: [Uri]
instantiatesUri: [Uri]
basedOn: [Reference]
partOf: [Reference]
status: String
statusReason: CodeableConcept
category: CodeableConcept
code: CodeableConcept
subject: Reference
encounter: Reference
performedDateTime: Date
performedPeriod: Period
performedString: String
performedAge: Age
performedRange: Range
recorder: Reference
asserter: Reference
performer: [ProcedurePerformer]
location: Reference
reasonCode: [CodeableConcept]
reasonReference: [Reference]
bodySite: [CodeableConcept]
outcome: CodeableConcept
report: [Reference]
complication: [CodeableConcept]
complicationDetail: [Reference]
followUp: [CodeableConcept]
note: [Annotation]
focalDevice: [ProcedureFocalDevice]
usedReference: [Reference]
usedCode: [CodeableConcept]
text: Narrative
contained: [Resource]
extension: [Extension]
modifierExtension: [Extension]
id: String
meta: Meta
implicitRules: Uri
language: String
}
Fields
Procedure.identifier ● [Identifier] list object
Business identifiers assigned to this procedure by the performer or other systems which remain constant as the resource is updated and is propagated from server to server.
Procedure.instantiatesCanonical ● [Uri] list scalar
The URL pointing to a FHIR-defined protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure.
Procedure.instantiatesUri ● [Uri] list scalar
The URL pointing to an externally maintained protocol, guideline, order set or other definition that is adhered to in whole or in part by this Procedure.
Procedure.basedOn ● [Reference] list object
A reference to a resource that contains details of the request for this procedure.
Procedure.partOf ● [Reference] list object
A larger event of which this particular procedure is a component or step.
Procedure.status ● String scalar
A code specifying the state of the procedure. Generally, this will be the in-progress or completed state.
Procedure.statusReason ● CodeableConcept object
Captures the reason for the current state of the procedure.
Procedure.category ● CodeableConcept object
A code that classifies the procedure for searching, sorting and display purposes (e.g. Surgical Procedure ).
Procedure.code ● CodeableConcept object
The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. Laparoscopic Appendectomy ).
Procedure.subject ● Reference object
The person, animal or group on which the procedure was performed.
Procedure.encounter ● Reference object
The Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated.
Procedure.performedDateTime ● Date scalar
Estimated or actual date, date-time, period, or age when 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. (choose any one of performed*, but only one)
Procedure.performedPeriod ● Period object
Estimated or actual date, date-time, period, or age when 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. (choose any one of performed*, but only one)
Procedure.performedString ● String scalar
Estimated or actual date, date-time, period, or age when 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. (choose any one of performed*, but only one)
Procedure.performedAge ● Age object
Estimated or actual date, date-time, period, or age when 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. (choose any one of performed*, but only one)
Procedure.performedRange ● Range object
Estimated or actual date, date-time, period, or age when 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. (choose any one of performed*, but only one)
Procedure.recorder ● Reference object
Individual who recorded the record and takes responsibility for its content.
Procedure.asserter ● Reference object
Individual who is making the procedure statement.
Procedure.performer ● [ProcedurePerformer] list object
Limited to real people rather than equipment.
Procedure.location ● Reference object
The location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant.
Procedure.reasonCode ● [CodeableConcept] list object
The coded reason why the procedure was performed. This may be a coded entity of some type, or may simply be present as text.
Procedure.reasonReference ● [Reference] list object
The justification of why the procedure was performed.
Procedure.bodySite ● [CodeableConcept] list object
Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion.
Procedure.outcome ● CodeableConcept object
The outcome of the procedure - did it resolve the reasons for the procedure being performed?
Procedure.report ● [Reference] list object
This could be a histology result, pathology report, surgical report, etc.
Procedure.complication ● [CodeableConcept] list object
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.
Procedure.complicationDetail ● [Reference] list object
Any complications that occurred during the procedure, or in the immediate post-performance period.
Procedure.followUp ● [CodeableConcept] list object
If the procedure required specific follow up - e.g. removal of sutures. The follow up may be represented as a simple note or could potentially be more complex, in which case the CarePlan resource can be used.
Procedure.note ● [Annotation] list object
Any other notes and comments about the procedure.
Procedure.focalDevice ● [ProcedureFocalDevice] list object
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.
Procedure.usedReference ● [Reference] list object
Identifies medications, devices and any other substance used as part of the procedure.
Procedure.usedCode ● [CodeableConcept] list object
Identifies coded items that were used as part of the procedure.
Procedure.text ● Narrative object
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it clinically safe for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Procedure.contained ● [Resource] list interface
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
Procedure.extension ● [Extension] list object
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Procedure.modifierExtension ● [Extension] list object
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Procedure.id ● String scalar
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Procedure.meta ● Meta object
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
Procedure.implicitRules ● Uri scalar
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Procedure.language ● String scalar
The base language in which the resource is written.
Interfaces
Resource interface
This is the base resource type for everything.
Returned By
Procedure query ● ProcedureCreate mutation ● ProcedureList query ● ProcedureUpdate mutation