pub struct ProcedureInner {Show 64 fields
pub id: Option<String>,
pub meta: Option<Meta>,
pub implicit_rules: Option<String>,
pub language: Option<String>,
pub text: Option<Narrative>,
pub contained: Vec<Resource>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub identifier: Vec<Option<Identifier>>,
pub identifier_ext: Vec<Option<FieldExtension>>,
pub instantiates_canonical: Vec<Option<String>>,
pub instantiates_canonical_ext: Vec<Option<FieldExtension>>,
pub instantiates_uri: Vec<Option<String>>,
pub instantiates_uri_ext: Vec<Option<FieldExtension>>,
pub based_on: Vec<Option<Reference>>,
pub based_on_ext: Vec<Option<FieldExtension>>,
pub part_of: Vec<Option<Reference>>,
pub part_of_ext: Vec<Option<FieldExtension>>,
pub status: EventStatus,
pub status_ext: Option<FieldExtension>,
pub status_reason: Option<CodeableConcept>,
pub status_reason_ext: Option<FieldExtension>,
pub category: Vec<Option<CodeableConcept>>,
pub category_ext: Vec<Option<FieldExtension>>,
pub code: Option<CodeableConcept>,
pub code_ext: Option<FieldExtension>,
pub subject: Reference,
pub subject_ext: Option<FieldExtension>,
pub focus: Option<Reference>,
pub focus_ext: Option<FieldExtension>,
pub encounter: Option<Reference>,
pub encounter_ext: Option<FieldExtension>,
pub occurrence: Option<ProcedureOccurrence>,
pub occurrence_ext: Option<ProcedureOccurrenceExtension>,
pub recorded: Option<DateTime>,
pub recorded_ext: Option<FieldExtension>,
pub recorder: Option<Reference>,
pub recorder_ext: Option<FieldExtension>,
pub reported: Option<ProcedureReported>,
pub reported_ext: Option<ProcedureReportedExtension>,
pub performer: Vec<Option<ProcedurePerformer>>,
pub performer_ext: Vec<Option<FieldExtension>>,
pub location: Option<Reference>,
pub location_ext: Option<FieldExtension>,
pub reason: Vec<Option<CodeableReference>>,
pub reason_ext: Vec<Option<FieldExtension>>,
pub body_site: Vec<Option<CodeableConcept>>,
pub body_site_ext: Vec<Option<FieldExtension>>,
pub outcome: Option<CodeableConcept>,
pub outcome_ext: Option<FieldExtension>,
pub report: Vec<Option<Reference>>,
pub report_ext: Vec<Option<FieldExtension>>,
pub complication: Vec<Option<CodeableReference>>,
pub complication_ext: Vec<Option<FieldExtension>>,
pub follow_up: Vec<Option<CodeableConcept>>,
pub follow_up_ext: Vec<Option<FieldExtension>>,
pub note: Vec<Option<Annotation>>,
pub note_ext: Vec<Option<FieldExtension>>,
pub focal_device: Vec<Option<ProcedureFocalDevice>>,
pub focal_device_ext: Vec<Option<FieldExtension>>,
pub used: Vec<Option<CodeableReference>>,
pub used_ext: Vec<Option<FieldExtension>>,
pub supporting_info: Vec<Option<Reference>>,
pub supporting_info_ext: Vec<Option<FieldExtension>>,
/* private fields */
}Expand description
An action that is or was performed on or for a patient, practitioner, device, organization, or location. For example, this can be a physical intervention on a patient like an operation, or less invasive like long term services, counseling, or hypnotherapy. This can be a quality or safety inspection for a location, organization, or device. This can be an accreditation procedure on a practitioner for licensing.
Procedure v5.0.0
An action that is being or was performed on an individual or entity
An action that is or was performed on or for a patient, practitioner, device, organization, or location. For example, this can be a physical intervention on a patient like an operation, or less invasive like long term services, counseling, or hypnotherapy. This can be a quality or safety inspection for a location, organization, or device. This can be an accreditation procedure on a practitioner for licensing.
Fields§
§id: Option<String>Logical id of this artifact
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
meta: Option<Meta>Metadata about the resource
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.
implicit_rules: Option<String>A set of rules under which this content was created
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.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
language: Option<String>Language; Language of the resource content
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
text: Option<Narrative>Text summary of the resource, for human interpretation
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.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a “text blob” or where text is additionally entered raw or narrated and encoded information is added later.
contained: Vec<Resource>Contained, inline Resources
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
extension: Vec<Extension>Additional content defined by implementations
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 managable, 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.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
modifier_extension: Vec<Extension>Extensions that cannot be ignored
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 managable, 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).
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
identifier: Vec<Option<Identifier>>External Identifiers for this procedure
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.
This is a business identifier, not a resource identifier (see discussion). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and Person resource instances might share the same social insurance number.
identifier_ext: Vec<Option<FieldExtension>>Extension field.
instantiates_canonical: Vec<Option<String>>Instantiates FHIR protocol or definition
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.
instantiates_canonical_ext: Vec<Option<FieldExtension>>Extension field.
instantiates_uri: Vec<Option<String>>Instantiates external protocol or definition
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.
This might be an HTML page, PDF, etc. or could just be a non-resolvable URI identifier.
instantiates_uri_ext: Vec<Option<FieldExtension>>Extension field.
based_on: Vec<Option<Reference>>A request for this procedure
A reference to a resource that contains details of the request for this procedure.
based_on_ext: Vec<Option<FieldExtension>>Extension field.
part_of: Vec<Option<Reference>>Part of referenced event
A larger event of which this particular procedure is a component or step.
The MedicationAdministration resource has a partOf reference to Procedure, but this is not a circular reference. For example, the anesthesia MedicationAdministration is part of the surgical Procedure (MedicationAdministration.partOf = Procedure). For example, the procedure to insert the IV port for an IV medication administration is part of the medication administration (Procedure.partOf = MedicationAdministration).
part_of_ext: Vec<Option<FieldExtension>>Extension field.
status: EventStatusProcedureStatus; preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
A code specifying the state of the procedure. Generally, this will be the in-progress or completed state.
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.
status_ext: Option<FieldExtension>Extension field.
status_reason: Option<CodeableConcept>ProcedureNegationReason; Reason for current status
Captures the reason for the current state of the procedure.
This is generally only used for “exception” statuses such as “not-done”, “suspended” or “aborted”. The reason for performing the event at all is captured in reasonCode, not here.
status_reason_ext: Option<FieldExtension>Extension field.
category: Vec<Option<CodeableConcept>>ProcedureCategory; Classification of the procedure
A code that classifies the procedure for searching, sorting and display purposes (e.g. “Surgical Procedure”).
category_ext: Vec<Option<FieldExtension>>Extension field.
code: Option<CodeableConcept>ProcedureCode; Identification of the procedure
The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. “Laparoscopic Appendectomy”).
code_ext: Option<FieldExtension>Extension field.
subject: ReferenceIndividual or entity the procedure was performed on
On whom or on what the procedure was performed. This is usually an individual human, but can also be performed on animals, groups of humans or animals, organizations or practitioners (for licensing), locations or devices (for safety inspections or regulatory authorizations). If the actual focus of the procedure is different from the subject, the focus element specifies the actual focus of the procedure.
subject_ext: Option<FieldExtension>Extension field.
focus: Option<Reference>Who is the target of the procedure when it is not the subject of record only
Who is the target of the procedure when it is not the subject of record only. If focus is not present, then subject is the focus. If focus is present and the subject is one of the targets of the procedure, include subject as a focus as well. If focus is present and the subject is not included in focus, it implies that the procedure was only targeted on the focus. For example, when a caregiver is given education for a patient, the caregiver would be the focus and the procedure record is associated with the subject (e.g. patient). For example, use focus when recording the target of the education, training, or counseling is the parent or relative of a patient.
focus_ext: Option<FieldExtension>Extension field.
encounter: Option<Reference>The Encounter during which this Procedure was created
The Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated.
This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter.
encounter_ext: Option<FieldExtension>Extension field.
occurrence: Option<ProcedureOccurrence>When the procedure occurred or is occurring
Estimated or actual date, date-time, period, or age when the procedure did occur or is occurring. 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.
This indicates when the procedure actually occurred or is occurring, not when it was asked/requested/ordered to occur. For the latter, look at the occurence element of the Request this Procedure is “basedOn”. The status code allows differentiation of whether the timing reflects a historic event or an ongoing event. Ongoing events should not include an upper bound in the Period or Timing.bounds.
Age is generally used when the patient reports an age at which the procedure was performed. Range is generally used when the patient reports an age range when the procedure was performed, such as sometime between 20-25 years old. dateTime supports a range of precision due to some procedures being reported as past procedures that might not have millisecond precision while other procedures performed and documented during the encounter might have more precise UTC timestamps with timezone.
occurrence_ext: Option<ProcedureOccurrenceExtension>Extension field.
recorded: Option<DateTime>When the procedure was first captured in the subject’s record
The date the occurrence of the procedure was first captured in the record regardless of Procedure.status (potentially after the occurrence of the event).
recorded_ext: Option<FieldExtension>Extension field.
recorder: Option<Reference>Who recorded the procedure
Individual who recorded the record and takes responsibility for its content.
recorder_ext: Option<FieldExtension>Extension field.
reported: Option<ProcedureReported>Reported rather than primary record
Indicates if this record was captured as a secondary ‘reported’ record rather than as an original primary source-of-truth record. It may also indicate the source of the report.
reported_ext: Option<ProcedureReportedExtension>Extension field.
performer: Vec<Option<ProcedurePerformer>>Who performed the procedure and what they did
Indicates who or what performed the procedure and how they were involved.
performer_ext: Vec<Option<FieldExtension>>Extension field.
location: Option<Reference>Where the procedure happened
The location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant.
location_ext: Option<FieldExtension>Extension field.
reason: Vec<Option<CodeableReference>>ProcedureReason; The justification that the procedure was performed
The coded reason or reference why the procedure was performed. This may be a coded entity of some type, be present as text, or be a reference to one of several resources that justify the procedure.
Use Procedure.reason.concept when a code sufficiently describes the reason. Use Procedure.reason.reference when referencing a resource, which allows more information to be conveyed, such as onset date. For a single Procedure.reason, if both Procedure.reason.concept and Procedure.reason.reference are present, they are expected to be consistent with each other.
reason_ext: Vec<Option<FieldExtension>>Extension field.
body_site: Vec<Option<CodeableConcept>>BodySite; Target body sites
Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion.
If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension http://hl7.org/fhir/StructureDefinition/procedure-targetBodyStructure.
body_site_ext: Vec<Option<FieldExtension>>Extension field.
outcome: Option<CodeableConcept>ProcedureOutcome; The result of procedure
The outcome of the procedure - did it resolve the reasons for the procedure being performed?
If outcome contains narrative text only, it can be captured using the CodeableConcept.text.
outcome_ext: Option<FieldExtension>Extension field.
report: Vec<Option<Reference>>Any report resulting from the procedure
This could be a histology result, pathology report, surgical report, etc.
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.
report_ext: Vec<Option<FieldExtension>>Extension field.
complication: Vec<Option<CodeableReference>>ProcedureComplication; Complication following the procedure
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.
If complications are only expressed by the narrative text, they can be captured using the CodeableReference.concept.text.
complication_ext: Vec<Option<FieldExtension>>Extension field.
follow_up: Vec<Option<CodeableConcept>>ProcedureFollowUp; Instructions for follow up
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.
follow_up_ext: Vec<Option<FieldExtension>>Extension field.
note: Vec<Option<Annotation>>Additional information about the procedure
Any other notes and comments about the procedure.
note_ext: Vec<Option<FieldExtension>>Extension field.
focal_device: Vec<Option<ProcedureFocalDevice>>Manipulated, implanted, or removed device
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.
focal_device_ext: Vec<Option<FieldExtension>>Extension field.
used: Vec<Option<CodeableReference>>ProcedureUsed; Items used during procedure
Identifies medications, devices and any other substance used as part of the procedure.
For devices actually implanted or removed, use Procedure.focalDevice.manipulated.
used_ext: Vec<Option<FieldExtension>>Extension field.
supporting_info: Vec<Option<Reference>>Extra information relevant to the procedure
Other resources from the patient record that may be relevant to the procedure. The information from these resources was either used to create the instance or is provided to help with its interpretation. This extension should not be used if more specific inline elements or extensions are available.
supporting_info_ext: Vec<Option<FieldExtension>>Extension field.
Trait Implementations§
Source§impl Clone for ProcedureInner
impl Clone for ProcedureInner
Source§fn clone(&self) -> ProcedureInner
fn clone(&self) -> ProcedureInner
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more