Canonical intermediate logical model for Procedure translation. It is shaped to the full Procedure core structure, aligned with eu-base as the structural baseline, and extended with Dutch zib and nl-core procedure semantics using future-oriented normalized field names.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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.

Source profile used to populate this logical model.

Target profile intended for this logical model instance.

Canonical URL of a source-side profile-specific extension or profile element preserved by this logical model.

Serialized source-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.

Canonical URL of a target-side profile-specific extension or profile element preserved by this logical model.

Serialized target-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.

Profile-specific extension data carried explicitly by the logical model alongside the normalized R4 payload.

Dutch procedure method semantics represented from the dedicated procedure-method extension.

Procedure identifiers.

Canonical definitions instantiated by the procedure.

External definitions instantiated by the procedure.

Requests or plans that the procedure fulfills.

Larger events or procedures of which this procedure is a part.

Procedure status.

Reason for the current procedure status.

Procedure category.

Procedure code.

Subject of the procedure.

Encounter context for the procedure.

When the procedure was performed as a single instant.

When the procedure was performed as an interval.

Narrative performed timing.

Age at which the procedure was performed.

Estimated age or time range at which the procedure was performed.

Date and time when the procedure was recorded in the eu-base layer.

Who recorded the procedure.

Who asserted the procedure.

People, organizations, or devices performing the procedure.

Location where the procedure occurred.

Clinical reason codes for the procedure.

Clinical reason references for the procedure.

Procedure body site details, including laterality when supplied.

Structured body site references aligned with eu-base body structure semantics when available.

Outcome of the procedure.

Reports generated by or associated with the procedure.

Dutch text-result reports represented from the dedicated report slice.

Complications associated with the procedure.

Detailed complication resources.

Follow-up actions or recommendations.

Narrative notes.

Devices that were manipulated during the procedure.

Devices, medications, or substances used during the procedure.

Coded representations of items used during the procedure.

Canonical intermediate logical model for Procedure translation. It is shaped to the full Procedure core structure, aligned with eu-base as the structural baseline, and extended with Dutch zib and nl-core procedure semantics using future-oriented normalized field names.

Source profile used to populate this logical model.

Target profile intended for this logical model instance.

Canonical URL of a source-side profile-specific extension or profile element preserved by this logical model.

Serialized source-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.

Canonical URL of a target-side profile-specific extension or profile element preserved by this logical model.

Serialized target-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.

Profile-specific extension data carried explicitly by the logical model alongside the normalized R4 payload.

Dutch procedure method semantics represented from the dedicated procedure-method extension.

Procedure identifiers.

Canonical definitions instantiated by the procedure.

External definitions instantiated by the procedure.

Requests or plans that the procedure fulfills.

Larger events or procedures of which this procedure is a part.

Procedure status.

Reason for the current procedure status.

Procedure category.

Procedure code.

Subject of the procedure.

Encounter context for the procedure.

When the procedure was performed as a single instant.

When the procedure was performed as an interval.

Narrative performed timing.

Age at which the procedure was performed.

Estimated age or time range at which the procedure was performed.

Date and time when the procedure was recorded in the eu-base layer.

Who recorded the procedure.

Who asserted the procedure.

People, organizations, or devices performing the procedure.

Location where the procedure occurred.

Clinical reason codes for the procedure.

Clinical reason references for the procedure.

Procedure body site details, including laterality when supplied.

Structured body site references aligned with eu-base body structure semantics when available.

Outcome of the procedure.

Reports generated by or associated with the procedure.

Dutch text-result reports represented from the dedicated report slice.

Complications associated with the procedure.

Detailed complication resources.

Follow-up actions or recommendations.

Narrative notes.

Devices that were manipulated during the procedure.

Devices, medications, or substances used during the procedure.

Coded representations of items used during the procedure.

Canonical intermediate logical model for Procedure translation. It is shaped to the full Procedure core structure, aligned with eu-base as the structural baseline, and extended with Dutch zib and nl-core procedure semantics using future-oriented normalized field names.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

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.

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.

Source profile used to populate this logical model.

Target profile intended for this logical model instance.

Canonical URL of a source-side profile-specific extension or profile element preserved by this logical model.

Serialized source-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.

Canonical URL of a target-side profile-specific extension or profile element preserved by this logical model.

Serialized target-side profile-specific extension or profile element payload when it cannot be represented by the generic R4 base shape.

Profile-specific extension data carried explicitly by the logical model alongside the normalized R4 payload.

Dutch procedure method semantics represented from the dedicated procedure-method extension.

Procedure identifiers.

Canonical definitions instantiated by the procedure.

External definitions instantiated by the procedure.

Requests or plans that the procedure fulfills.

Larger events or procedures of which this procedure is a part.

Procedure status.

Reason for the current procedure status.

Procedure category.

Procedure code.

Subject of the procedure.

Encounter context for the procedure.

When the procedure was performed as a single instant.

When the procedure was performed as an interval.

Narrative performed timing.

Age at which the procedure was performed.

Estimated age or time range at which the procedure was performed.

Date and time when the procedure was recorded in the eu-base layer.

Who recorded the procedure.

Who asserted the procedure.

People, organizations, or devices performing the procedure.

Location where the procedure occurred.

Clinical reason codes for the procedure.

Clinical reason references for the procedure.

Procedure body site details, including laterality when supplied.

Structured body site references aligned with eu-base body structure semantics when available.

Outcome of the procedure.

Reports generated by or associated with the procedure.

Dutch text-result reports represented from the dedicated report slice.

Complications associated with the procedure.

Detailed complication resources.

Follow-up actions or recommendations.

Narrative notes.

Devices that were manipulated during the procedure.

Devices, medications, or substances used during the procedure.

Coded representations of items used during the procedure.