Data elements for the IMMZ.C Client registration Data Dictionary.

Unique identifier for the client, according to the policies applicable to each country. There can be more than one unique identifier used to link records (e.g. national identification [ID], health ID, immunization information system ID, medical record ID)

The full name of the client

Client's first name or given name

Client's family name or last name

Documentation of a specific instance of sex information for the client

Client's date of birth (DOB) if known; if unknown, use assigned DOB for administrative purposes

The client's calculated age (presented as number of years, months, weeks, days) based on the DOB and the visit date

Details of the client's caregiver (person) who could be next of kin (e.g. partner, husband, mother, sibling, etc.)

The full name of the client's caregiver

First or given name of the client's caregiver

Family name or last name of the client's caregiver

Client's phone number; can be a landline or a mobile phone number

Client's home address or address that the client is consenting to disclose

Data elements for the IMMZ.C Client registration Data Dictionary.

Unique identifier for the client, according to the policies applicable to each country. There can be more than one unique identifier used to link records (e.g. national identification [ID], health ID, immunization information system ID, medical record ID)

The full name of the client

Client's first name or given name

Client's family name or last name

Documentation of a specific instance of sex information for the client

Client's date of birth (DOB) if known; if unknown, use assigned DOB for administrative purposes

The client's calculated age (presented as number of years, months, weeks, days) based on the DOB and the visit date

Details of the client's caregiver (person) who could be next of kin (e.g. partner, husband, mother, sibling, etc.)

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.

The full name of the client's caregiver

First or given name of the client's caregiver

Family name or last name of the client's caregiver

Client's phone number; can be a landline or a mobile phone number

Client's home address or address that the client is consenting to disclose

Data elements for the IMMZ.C Client registration Data Dictionary.

Unique identifier for the client, according to the policies applicable to each country. There can be more than one unique identifier used to link records (e.g. national identification [ID], health ID, immunization information system ID, medical record ID)

The full name of the client

Client's first name or given name

Client's family name or last name

Documentation of a specific instance of sex information for the client

Client's date of birth (DOB) if known; if unknown, use assigned DOB for administrative purposes

The client's calculated age (presented as number of years, months, weeks, days) based on the DOB and the visit date

Details of the client's caregiver (person) who could be next of kin (e.g. partner, husband, mother, sibling, etc.)

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.

The full name of the client's caregiver

First or given name of the client's caregiver

Family name or last name of the client's caregiver

Client's phone number; can be a landline or a mobile phone number

Client's home address or address that the client is consenting to disclose