Logical Model for Information on the trusted list and its issuing scheme

TSL version identifier (clause 5.3.1)

TSL sequence number (clause 5.3.2)

TSL type (clause 5.3.3)

Scheme operator name (clause 5.3.4)

Scheme operator address (clause 5.3.5)

Scheme Operator Postal Address

Scheme Operator Electronic Address

Scheme name (clause 5.3.6) CC:EN_name_value

Scheme information URI (clause 5.3.7)

Status determination approach (clause 5.3.8)

Scheme type/community/rules (clause 5.3.9)

Scheme territory (clause 5.3.10)

TSL policy/legal notice (clause 5.3.11)

Historical information period (clause 5.3.12)

Pointers to other TSLs (clause 5.3.13)

List issue date and time (clause 5.3.14)

Next update (clause 5.3.15)

Distribution points (clause 5.3.16)

Scheme extensions (clause 5.3.17)

Logical Model for Information on the trusted list and its issuing scheme

TSL version identifier (clause 5.3.1)

TSL sequence number (clause 5.3.2)

TSL type (clause 5.3.3)

Scheme operator name (clause 5.3.4)

Scheme operator address (clause 5.3.5)

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 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. 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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Scheme Operator Postal Address

Scheme Operator Electronic Address

Scheme name (clause 5.3.6) CC:EN_name_value

Scheme information URI (clause 5.3.7)

Status determination approach (clause 5.3.8)

Scheme type/community/rules (clause 5.3.9)

Scheme territory (clause 5.3.10)

TSL policy/legal notice (clause 5.3.11)

Historical information period (clause 5.3.12)

Pointers to other TSLs (clause 5.3.13)

List issue date and time (clause 5.3.14)

Next update (clause 5.3.15)

Distribution points (clause 5.3.16)

Scheme extensions (clause 5.3.17)

Logical Model for Information on the trusted list and its issuing scheme

TSL version identifier (clause 5.3.1)

TSL sequence number (clause 5.3.2)

TSL type (clause 5.3.3)

Scheme operator name (clause 5.3.4)

Scheme operator address (clause 5.3.5)

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.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained 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 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. 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.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Scheme Operator Postal Address

Scheme Operator Electronic Address

Scheme name (clause 5.3.6) CC:EN_name_value

Scheme information URI (clause 5.3.7)

Status determination approach (clause 5.3.8)

Scheme type/community/rules (clause 5.3.9)

Scheme territory (clause 5.3.10)

TSL policy/legal notice (clause 5.3.11)

Historical information period (clause 5.3.12)

Pointers to other TSLs (clause 5.3.13)

List issue date and time (clause 5.3.14)

Next update (clause 5.3.15)

Distribution points (clause 5.3.16)

Scheme extensions (clause 5.3.17)