Canonical intermediate logical model for Problem to Condition translation. It is shaped to the full Condition core structure, aligned with eu-base as the structural baseline, and extended with Dutch zib and nl-core problem 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.

Problem identifiers.

Clinical status of the condition.

Verification status of the asserted problem.

Problem categories.

Dutch problem type semantics represented from the profiled category slice.

Severity of the problem.

Problem or diagnosis code.

Dutch further specification of the problem name when carried by the dedicated extension.

Affected body site details, including laterality when supplied.

Subject of the problem.

Encounter context in which the problem was recorded or discussed.

Recorded onset date or time.

Age at onset when recorded as an age.

Onset period when recorded as a date range.

Onset range when recorded as an estimated range.

Narrative onset expression.

Recorded abatement date or time.

Age at abatement when recorded as an age.

Abatement period when recorded as a date range.

Abatement range when recorded as an estimated range.

Narrative abatement expression.

Date the condition assertion was made when populated through the eu-base asserted-date extension.

Related artifacts associated with the problem in the eu-base layer.

Date the problem was first recorded.

Who recorded the problem.

Who asserted the problem.

Staging details associated with the problem.

Evidence supporting the problem or diagnosis.

Narrative notes.

Canonical intermediate logical model for Problem to Condition translation. It is shaped to the full Condition core structure, aligned with eu-base as the structural baseline, and extended with Dutch zib and nl-core problem 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.

Problem identifiers.

Clinical status of the condition.

Verification status of the asserted problem.

Problem categories.

Dutch problem type semantics represented from the profiled category slice.

Severity of the problem.

Problem or diagnosis code.

Dutch further specification of the problem name when carried by the dedicated extension.

Affected body site details, including laterality when supplied.

Subject of the problem.

Encounter context in which the problem was recorded or discussed.

Recorded onset date or time.

Age at onset when recorded as an age.

Onset period when recorded as a date range.

Onset range when recorded as an estimated range.

Narrative onset expression.

Recorded abatement date or time.

Age at abatement when recorded as an age.

Abatement period when recorded as a date range.

Abatement range when recorded as an estimated range.

Narrative abatement expression.

Date the condition assertion was made when populated through the eu-base asserted-date extension.

Related artifacts associated with the problem in the eu-base layer.

Date the problem was first recorded.

Who recorded the problem.

Who asserted the problem.

Staging details associated with the problem.

Evidence supporting the problem or diagnosis.

Narrative notes.

Canonical intermediate logical model for Problem to Condition translation. It is shaped to the full Condition core structure, aligned with eu-base as the structural baseline, and extended with Dutch zib and nl-core problem 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.

Problem identifiers.

Clinical status of the condition.

Verification status of the asserted problem.

Problem categories.

Dutch problem type semantics represented from the profiled category slice.

Severity of the problem.

Problem or diagnosis code.

Dutch further specification of the problem name when carried by the dedicated extension.

Affected body site details, including laterality when supplied.

Subject of the problem.

Encounter context in which the problem was recorded or discussed.

Recorded onset date or time.

Age at onset when recorded as an age.

Onset period when recorded as a date range.

Onset range when recorded as an estimated range.

Narrative onset expression.

Recorded abatement date or time.

Age at abatement when recorded as an age.

Abatement period when recorded as a date range.

Abatement range when recorded as an estimated range.

Narrative abatement expression.

Date the condition assertion was made when populated through the eu-base asserted-date extension.

Related artifacts associated with the problem in the eu-base layer.

Date the problem was first recorded.

Who recorded the problem.

Who asserted the problem.

Staging details associated with the problem.

Evidence supporting the problem or diagnosis.

Narrative notes.