The patient who underwent the procedure.
One or more external identifiers for the patient
When the procedure was performed.
The status of the procedure: preparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
A code to identify the procedure
Response to a Procedure search operation
Identifies the type of the resource
Identifies this bundle as a response to a search
The total number of matches
A resource matching the search criteria or related to a matching resource
A record of an action that was performed on or for a patient
Identifies the type of the resource
A code specifying the state of the procedure. Generally, this will be the in-progress or completed state.
This element contains extensions for status. Depending on the extensions present it could be used in place of status or contain additional information about status. See the extension element for more details on the possible extensions being sent.
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.
A human language representation of the concept (resource/element) as seen/selected/uttered by the user who entered the data and/or which represents the full intended meaning of the user.
See http://hl7.org/fhir/StructureDefinition/originalText for more information
Source of the definition for the extension code - a logical name or a URL.
The original text
The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy").
A reference to a code defined by a terminology system.
The identification of the code system that defines the meaning of the symbol in the code.
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
The person, animal or group on which the procedure was performed.
Must be a resource of type Patient.
A reference to another resource. This is typically either a relative reference which includes the resource type and ID, or an internal reference which starts with # and refers to a contained resource.
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
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.
May be used to represent additional information that is not part of the basic definition of the element. 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.
Source of the definition for the extension code - a logical name or a URL.
A single value for the extension.
The purpose of this identifier.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
A code that classifies the procedure for searching, sorting and display purposes (e.g. "Surgical Procedure").
A reference to a code defined by a terminology system.
The identification of the code system that defines the meaning of the symbol in the code.
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
The Encounter during which this Procedure was created or performed or to which the creation of this record is tightly associated.
Must be a resource of type Encounter.
A reference to another resource. This is typically either a relative reference which includes the resource type and ID, or an internal reference which starts with # and refers to a contained resource.
Limited to "real" people rather than equipment.
The practitioner who was involved in the procedure.
Must be a resource of type Practitioner.
A reference to another resource. This is typically either a relative reference which includes the resource type and ID, or an internal reference which starts with # and refers to a contained resource.
Distinguishes the type of involvement of the performer in the procedure. For example, surgeon, anaesthetist, endoscopist.
A reference to a code defined by a terminology system.
The identification of the code system that defines the meaning of the symbol in the code.
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
The location where the procedure actually happened. E.g. a newborn at home, a tracheostomy at a restaurant.
Must be a resource of type Location.
A reference to another resource. This is typically either a relative reference which includes the resource type and ID, or an internal reference which starts with # and refers to a contained resource.
Detailed and structured anatomical location information. Multiple locations are allowed - e.g. multiple punch biopsies of a lesion.
A reference to a code defined by a terminology system.
The identification of the code system that defines the meaning of the symbol in the code.
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
Any other notes and comments about the procedure.
The text of the annotation in markdown format.
The individual responsible for making the annotation.
Only one of authorReference, authorString may be present.
Must be a resource of type Practitioner.
A reference to another resource. This is typically either a relative reference which includes the resource type and ID, or an internal reference which starts with # and refers to a contained resource.
The individual responsible for making the annotation.
Only one of authorReference, authorString may be present.
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.
The device that was manipulated (changed) during the procedure.
Must be a resource of type Device.
A reference to another resource. This is typically either a relative reference which includes the resource type and ID, or an internal reference which starts with # and refers to a contained resource.
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.
Only one of performedDateTime, performedPeriod may be present.
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.
Only one of performedDateTime, performedPeriod may be present.
The start of the period. The boundary is inclusive.
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
Information about the search process that lead to the creation of this entry.
Identifies the Procedure as matching the search parameters