Canonical intermediate logical model for Consent translation. It is source-family neutral and maps the R4 Consent shape that can be reached from STU3/BgZ sources through the converter.

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.

FHIR Resource.language carried independently from resource-specific language concepts.

FHIR DomainResource.text carried without translating clinical XHTML content.

Profile route name or concept label used by the source-target pair.

FHIR source resource type accepted on the source side.

FHIR target resource type produced on the target side.

Consent identifiers.

Contained resources needed by local consent references, retained in same-version R4 routes.

Consent status.

Consent scope.

Consent category.

Patient the consent applies to.

Consent date and time.

Original 2017 BeginDatum; not the 2020 most recent discussion date.

This source requires the 2017 verification-to-agreement migration rules.

People or parties associated with the consent decision.

Patient, representative, or health professional who agreed the treatment directive.

Custodian organizations responsible for the consent.

Whether the directive was verified.

Date on which the directive was verified.

Parties or roles with whom the directive was verified.

R4 person or organization with whom the directive was verified.

Native R4 verification occurrences with their own date and party; not a flattened legacy history.

Free-text comment carried by Dutch Consent comment extensions.

Policy URI associated with the consent.

Regulatory or policy basis for the consent.

Source attachment for an advance directive.

Referenced primary source for an advance directive.

Additional directive source supplied as an attachment.

Identifier of an additional directive source.

Reference to an additional directive source.

Consent validity period.

Modifier qualifying the treatment directive; never optional to preserve when present.

Reason the directive's provision ended.

Type of advance directive.

Condition under which the directive applies.

Problem or condition to which the advance directive applies.

Advance directive linked from a treatment directive.

Structured directive detail with an explicit target home.

Review due date for the directive.

Witness associated with the directive.

Mandate or representative authority associated with the directive.

Digital representation of the directive.

Location where the directive can be found.

Person or organization holding a copy of the directive.

Date and time this directive information was last updated.

Provision type used for treatment directive semantics.

Provision or exception code associated with the directive.

Canonical intermediate logical model for Consent translation. It is source-family neutral and maps the R4 Consent shape that can be reached from STU3/BgZ sources through the converter.

Source profile used to populate this logical model.

Target profile intended for this logical model instance.

FHIR Resource.language carried independently from resource-specific language concepts.

FHIR DomainResource.text carried without translating clinical XHTML content.

Profile route name or concept label used by the source-target pair.

FHIR source resource type accepted on the source side.

FHIR target resource type produced on the target side.

Consent identifiers.

Contained resources needed by local consent references, retained in same-version R4 routes.

Consent status.

Consent scope.

Consent category.

Patient the consent applies to.

Consent date and time.

Original 2017 BeginDatum; not the 2020 most recent discussion date.

This source requires the 2017 verification-to-agreement migration rules.

People or parties associated with the consent decision.

Patient, representative, or health professional who agreed the treatment directive.

Custodian organizations responsible for the consent.

Whether the directive was verified.

Date on which the directive was verified.

Parties or roles with whom the directive was verified.

R4 person or organization with whom the directive was verified.

Native R4 verification occurrences with their own date and party; not a flattened legacy history.

Free-text comment carried by Dutch Consent comment extensions.

Policy URI associated with the consent.

Regulatory or policy basis for the consent.

Source attachment for an advance directive.

Referenced primary source for an advance directive.

Additional directive source supplied as an attachment.

Identifier of an additional directive source.

Reference to an additional directive source.

Consent validity period.

Modifier qualifying the treatment directive; never optional to preserve when present.

Reason the directive's provision ended.

Type of advance directive.

Condition under which the directive applies.

Problem or condition to which the advance directive applies.

Advance directive linked from a treatment directive.

Structured directive detail with an explicit target home.

Review due date for the directive.

Witness associated with the directive.

Mandate or representative authority associated with the directive.

Digital representation of the directive.

Location where the directive can be found.

Person or organization holding a copy of the directive.

Date and time this directive information was last updated.

Provision type used for treatment directive semantics.

Provision or exception code associated with the directive.

Canonical intermediate logical model for Consent translation. It is source-family neutral and maps the R4 Consent shape that can be reached from STU3/BgZ sources through the converter.

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.

FHIR Resource.language carried independently from resource-specific language concepts.

FHIR DomainResource.text carried without translating clinical XHTML content.

Profile route name or concept label used by the source-target pair.

FHIR source resource type accepted on the source side.

FHIR target resource type produced on the target side.

Consent identifiers.

Contained resources needed by local consent references, retained in same-version R4 routes.

Consent status.

Consent scope.

Consent category.

Patient the consent applies to.

Consent date and time.

Original 2017 BeginDatum; not the 2020 most recent discussion date.

This source requires the 2017 verification-to-agreement migration rules.

People or parties associated with the consent decision.

Patient, representative, or health professional who agreed the treatment directive.

Custodian organizations responsible for the consent.

Whether the directive was verified.

Date on which the directive was verified.

Parties or roles with whom the directive was verified.

R4 person or organization with whom the directive was verified.

Native R4 verification occurrences with their own date and party; not a flattened legacy history.

Free-text comment carried by Dutch Consent comment extensions.

Policy URI associated with the consent.

Regulatory or policy basis for the consent.

Source attachment for an advance directive.

Referenced primary source for an advance directive.

Additional directive source supplied as an attachment.

Identifier of an additional directive source.

Reference to an additional directive source.

Consent validity period.

Modifier qualifying the treatment directive; never optional to preserve when present.

Reason the directive's provision ended.

Type of advance directive.

Condition under which the directive applies.

Problem or condition to which the advance directive applies.

Advance directive linked from a treatment directive.

Structured directive detail with an explicit target home.

Review due date for the directive.

Witness associated with the directive.

Mandate or representative authority associated with the directive.

Digital representation of the directive.

Location where the directive can be found.

Person or organization holding a copy of the directive.

Date and time this directive information was last updated.

Provision type used for treatment directive semantics.

Provision or exception code associated with the directive.