Data elements for the DIVOC Core Data Set.

The official DIVOC documentation appears to be at https://divoc.digit.org. However, this does not include a full list of elements included in DIVOC certificates.

There is a JSON-LD context referenced in DIVOC certificate examples (https://cowin.gov.in/credentials/vaccination/v1), which would provide some element-level information, but this URL does not resolve. There is a copy of this JSON-LD context at https://github.com/egovernments/DIVOC/blob/main/vaccination-context/vaccination-context.js.

It was not possible to find any online documentation regarding DIVOC proof of testing. Information on this was provided by the DIVOC team via email.

Some element descriptions in this logical model provide details that are not in publicly available DIVOC documentation.

Context (JSON-LD) - should actually be @context but this name isn't supported by FHIR.

JSON-LD Type

Issuer identifier URI. generally a DID

Date and time when a credential becomes valid

indicates that a verifiable credential must only be encapsulated into a verifiable presentation whose proof was issued by the credentialSubject

Contains claims about one or more objects (Patients)

Type of credential. Generally 'Person'

another id

reference id

A name associated with the patient

Gender (Male or Female; unknown if there are other options)

Sex (not used in examples; presumably Male or Female; unknown if there are other options)

Age

The date of birth for the individual (V2 only)

Nationality

Address

Line 1 of the address

Line 2 of the address

District name (aka county)

Name of city, town etc.

Sub-unit of country (abbreviations ok)

Country (e.g. may be ISO 3166 2 or 3 letter code)

Postal code for area

Vaccination Information

URL for feedback

URL for more information on this record

Certificate Unique Identifier

Type of evidence record. Generally Vaccination or TestDetails

Vaccine lot number

Vaccine description. Might include vaccine type and brand

Name of the Vaccine/Test Manufacturer

Date of immunization

Effective immunization start date

Effective immunization end date

Dose Number

Total doses for this vaccine protocol regimen

Practitioner that oversaw the application

Name of the practitioner

Facility where the immunization took place

Name of the facility/entity

Address of the facility

Line 1 of the address

Line 2 of the address

District name (aka county)

Name of city, town etc.

Sub-unit of country (abbreviations ok)

Country (e.g. may be ISO 3166 2 or 3 letter code)

Postal code for area

The specification for DIVOC does not provide any information beyond that this is an ICD-11 code, so correspondingly there is no required binding to a specific ValueSet in this logical model.

Descriptive details of the vaccine type

Lab test results: Test name

Lab test results: Type of test, either RT-PCR or Rapid Antigen Test (RAT)

Lab test results: Type of sample that was taken (e.g., nasal swab

Lab test results: Disease or agent targeted

Lab test results: Sample collection date and time; complete date, with time and time zone, following ISO 8601

Lab test results: Results date and time; complete date, with time and time zone, following ISO 8601

Lab test results: result of test

One or more cryptographic proofs that can be used to detect tampering and verify the authorship of a credential or presentation

Type of proof

Signature date and time

Resolvable issuer identifier

Clearly expresses the purpose for the proof and ensures this information is protected by the signature

Signature

Data elements for the DIVOC Core Data Set.

The official DIVOC documentation appears to be at https://divoc.digit.org. However, this does not include a full list of elements included in DIVOC certificates.

There is a JSON-LD context referenced in DIVOC certificate examples (https://cowin.gov.in/credentials/vaccination/v1), which would provide some element-level information, but this URL does not resolve. There is a copy of this JSON-LD context at https://github.com/egovernments/DIVOC/blob/main/vaccination-context/vaccination-context.js.

It was not possible to find any online documentation regarding DIVOC proof of testing. Information on this was provided by the DIVOC team via email.

Some element descriptions in this logical model provide details that are not in publicly available DIVOC documentation.

Context (JSON-LD) - should actually be @context but this name isn't supported by FHIR.

JSON-LD Type

Issuer identifier URI. generally a DID

Date and time when a credential becomes valid

indicates that a verifiable credential must only be encapsulated into a verifiable presentation whose proof was issued by the credentialSubject

Contains claims about one or more objects (Patients)

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.

Type of credential. Generally 'Person'

another id

reference id

A name associated with the patient

Gender (Male or Female; unknown if there are other options)

Sex (not used in examples; presumably Male or Female; unknown if there are other options)

Age

The date of birth for the individual (V2 only)

Nationality

Address

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.

Line 1 of the address

Line 2 of the address

District name (aka county)

Name of city, town etc.

Sub-unit of country (abbreviations ok)

Country (e.g. may be ISO 3166 2 or 3 letter code)

Postal code for area

Vaccination Information

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.

URL for feedback

URL for more information on this record

Certificate Unique Identifier

Type of evidence record. Generally Vaccination or TestDetails

Vaccine lot number

Vaccine description. Might include vaccine type and brand

Name of the Vaccine/Test Manufacturer

Date of immunization

Effective immunization start date

Effective immunization end date

Dose Number

Total doses for this vaccine protocol regimen

Practitioner that oversaw the application

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.

Name of the practitioner

Facility where the immunization took place

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.

Name of the facility/entity

Address of the facility

The purpose of this address.

Applications can assume that an address is current unless it explicitly says that it is temporary or old.

The use of an address.

Allows an appropriate address to be chosen from a list of many.

Name of city, town etc.

District name (aka county)

District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.

Postal code for area

Line 1 of the address

Line 2 of the address

Sub-unit of country (abbreviations ok)

Country (e.g. may be ISO 3166 2 or 3 letter code)

The specification for DIVOC does not provide any information beyond that this is an ICD-11 code, so correspondingly there is no required binding to a specific ValueSet in this logical model.

Descriptive details of the vaccine type

Lab test results: Test name

Lab test results: Type of test, either RT-PCR or Rapid Antigen Test (RAT)

Lab test results: Type of sample that was taken (e.g., nasal swab

Lab test results: Disease or agent targeted

Lab test results: Sample collection date and time; complete date, with time and time zone, following ISO 8601

Lab test results: Results date and time; complete date, with time and time zone, following ISO 8601

Lab test results: result of test

One or more cryptographic proofs that can be used to detect tampering and verify the authorship of a credential or presentation

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.

Type of proof

Signature date and time

Resolvable issuer identifier

Clearly expresses the purpose for the proof and ensures this information is protected by the signature

Signature

Data elements for the DIVOC Core Data Set.

The official DIVOC documentation appears to be at https://divoc.digit.org. However, this does not include a full list of elements included in DIVOC certificates.

There is a JSON-LD context referenced in DIVOC certificate examples (https://cowin.gov.in/credentials/vaccination/v1), which would provide some element-level information, but this URL does not resolve. There is a copy of this JSON-LD context at https://github.com/egovernments/DIVOC/blob/main/vaccination-context/vaccination-context.js.

It was not possible to find any online documentation regarding DIVOC proof of testing. Information on this was provided by the DIVOC team via email.

Some element descriptions in this logical model provide details that are not in publicly available DIVOC documentation.

Context (JSON-LD) - should actually be @context but this name isn't supported by FHIR.

JSON-LD Type

Issuer identifier URI. generally a DID

Date and time when a credential becomes valid

indicates that a verifiable credential must only be encapsulated into a verifiable presentation whose proof was issued by the credentialSubject

Contains claims about one or more objects (Patients)

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.

Type of credential. Generally 'Person'

another id

reference id

A name associated with the patient

Gender (Male or Female; unknown if there are other options)

Sex (not used in examples; presumably Male or Female; unknown if there are other options)

Age

The date of birth for the individual (V2 only)

Nationality

Address

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.

Line 1 of the address

Line 2 of the address

District name (aka county)

Name of city, town etc.

Sub-unit of country (abbreviations ok)

Country (e.g. may be ISO 3166 2 or 3 letter code)

Postal code for area

Vaccination Information

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.

URL for feedback

URL for more information on this record

Certificate Unique Identifier

Type of evidence record. Generally Vaccination or TestDetails

Vaccine lot number

Vaccine description. Might include vaccine type and brand

Name of the Vaccine/Test Manufacturer

Date of immunization

Effective immunization start date

Effective immunization end date

Dose Number

Total doses for this vaccine protocol regimen

Practitioner that oversaw the application

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.

Name of the practitioner

Facility where the immunization took place

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.

Name of the facility/entity

Address of the facility

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.

The purpose of this address.

Applications can assume that an address is current unless it explicitly says that it is temporary or old.

The use of an address.

Allows an appropriate address to be chosen from a list of many.

Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both.

The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).

The type of an address (physical / postal).

Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.

Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.

A renderable, unencoded form.

This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.

Name of city, town etc.

District name (aka county)

District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.

Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (e.g. US 2 letter state codes).

Postal code for area

Country - a nation as commonly understood or generally accepted.

ISO 3166 3 letter codes can be used in place of a human readable country name.

Time period when address was/is in use.

Allows addresses to be placed in historical context.

Line 1 of the address

Line 2 of the address

Sub-unit of country (abbreviations ok)

Country (e.g. may be ISO 3166 2 or 3 letter code)

The specification for DIVOC does not provide any information beyond that this is an ICD-11 code, so correspondingly there is no required binding to a specific ValueSet in this logical model.

Descriptive details of the vaccine type

Lab test results: Test name

Lab test results: Type of test, either RT-PCR or Rapid Antigen Test (RAT)

Lab test results: Type of sample that was taken (e.g., nasal swab

Lab test results: Disease or agent targeted

Lab test results: Sample collection date and time; complete date, with time and time zone, following ISO 8601

Lab test results: Results date and time; complete date, with time and time zone, following ISO 8601

Lab test results: result of test

One or more cryptographic proofs that can be used to detect tampering and verify the authorship of a credential or presentation

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.

Type of proof

Signature date and time

Resolvable issuer identifier

Clearly expresses the purpose for the proof and ensures this information is protected by the signature

Signature