Patient Demographics/Information

Description: When a patient was part of a multiple birth a number is defined in this element (e.g., 1, 2, 3). Typically received from Vital Records or birthing facility.

Rationale for inclusion:

• Ensures accurate validation of birth order to distinguish between siblings in immunization records, supporting individualized vaccination tracking.
• Drives implementation of security safeguards including encryption, access restrictions, and audit trails to protect birth order information as protected health information under HIPAA regulations.

Functional Standard(s): 1.0, 4.0

Repeat: No

Data Source: Vital Records

Description: Whether the patient was part of a multiple birth (yes/no). Typically received from Vital Records or birthing facility.

Rationale for inclusion:

• Necessitates the IIS to employ comprehensive security safeguards such as data encryption, role-based access restrictions, and activity monitoring in compliance with HIPAA and established security frameworks.
• Patient multiple birth indicator is used during the process to validate patient demographic data.

Functional Standard(s): 1.0,4.0

Repeat: No

Data Source: Vital Records

Description: State of the birthing facility location.

Rationale for inclusion:

• Information on the state of the patient's birth helps to validate patient records.
• Ensures adherence to federal security standards that safeguard this sensitive demographic identifier from unauthorized access or disclosure.

Functional Standard(s): 1.0, 4.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The street component of the patient's address.

Rationale for inclusion:

• Validates patient demographic and vaccination data by ensuring that street address information is up-to-date, preventing errors in vaccine tracking and facilitating accurate follow-up.
• Supports the generation of coverage reports by incorporating street address data to track immunization coverage in specific regions, helping to identify geographic areas with lower vaccination rates.
• Assists in the reporting of vaccine adverse events by ensuring that accurate street address information is available for follow-up and investigation into adverse events.
• Supports ad-hoc queries to verify vaccination status and demographic data based on specific street address information, ensuring correct data association.

Functional Standard(s): 4.0, 10.0, 11.0, 12.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The city component of the patient's address.

Rationale for inclusion:

• Validates patient demographic and vaccination data by ensuring that city-level information is included and accurate, enabling more precise tracking of vaccination rates by location.
• Supports the generation of coverage reports by organizing data based on city information, helping to assess vaccine coverage and identify areas where additional resources or interventions may be needed.
• Aids in reporting of vaccine adverse events by ensuring that city-specific details are included for effective follow-up and investigation of reported adverse events.
• Enables ad-hoc queries of vaccination data and demographic information based on city, helping health authorities monitor trends in vaccine uptake and assess whether there are any disparities.
• Mandates the application of appropriate security controls including data encryption, role-based access restrictions, and activity monitoring to protect patient city information as PHI under HIPAA regulations. Ensures compliance with federal privacy and security standards that safeguard patient address data from unauthorized viewing or breaches.
• Enables the IIS to aggregate and report vaccination coverage data by geographic area, allowing federal and jurisdictional immunization programs to identify coverage gaps and target interventions to specific cities or communities.
• Enables the IIS to generate geographically-targeted reminder/recall campaigns and ensures notifications are sent to patients at their correct city location.
• Supports targeted vaccine distribution and allocation by identifying patient populations and provider networks within cities experiencing disease outbreaks or requiring emergency immunization response.

Functional Standard(s): 1.0, 4.0, 9.0, 10.0, 11.0, 12.0, 13.0, 17.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The state component of the patient's address.

Rationale for inclusion:

• Validates patient demographic and vaccinationdata by confirming that state-level information is accurate, ensuring proper jurisdictional tracking of vaccination efforts and consistency across state boundaries.
• Supports the generation of coverage reports by enabling users to access state-specific immunization data, making it easier to identify and address vaccination gaps and ensure alignment with state immunization goals.
• Aids in reporting of vaccine adverse events by providing accurate state-level data for follow-up, ensuring that any adverse events are properly investigated within the relevant jurisdiction.
• Supports ad-hoc queries to verify vaccination status and demographic data at the state level, allowing for detailed analysis and reporting of immunization data within specific states.
• Requires the IIS to implement security controls such as encryption, access restrictions, and audit logging to protect patient state information as protected health information (PHI) under HIPAA.
• Ensures accurate jurisdictional reporting and compliance with state-specific immunization program requirements by identifying which state's regulations and reporting standards apply to each patient record.
• Ensures reminder/recall notifications comply with state-specific regulations and are sent to patients at their correct state address.
• Allows vaccines to be allocated, tracked, and reported according to the correct state's program requirements and regulations, as vaccine inventory accountability often differs by jurisdiction. Supports proper reconciliation of federally-supplied vaccines like VFC by identifying which state program is responsible for managing and monitoring vaccine distribution for each patient.
• Enables the IIS to coordinate with the appropriate state health department and activate state-specific emergency response protocols when onboarding partners and managing vaccine distribution during outbreaks.

Functional Standard(s): 1.0, 4.0, 9.0, 10.0, 11.0, 12.0, 13.0, 15.0, 17.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The zip code component of the patient's address.

Rationale for inclusion:

• Validates patient demographic and vaccinationdata by ensuring that zip code information is accurately associated with patients, enabling targeted outreach and ensuring that vaccination data is linked to specific geographic areas.
• Supports the generation of coverage reports by using zip code data to identify regional disparities in vaccine coverage and target areas where vaccine availability or uptake may need improvement.
• Aids in reporting of vaccine adverse events by ensuring that accurate zip code information is available, enabling appropriate geographic follow-up for any reported adverse events.
• Supports ad-hoc queries to verify vaccination status and demographic information by using zip code data to refine searches based on location and track vaccination trends within specific areas.
• Mandates implementation of appropriate safeguards including data encryption, role-based access controls, and activity monitoring to protect patient state information as PHI in compliance with HIPAA regulations.
• Supports accurate reporting to the correct jurisdiction by determining which state's immunization program regulations and standards apply to each patient's vaccination records.
• Facilitates compliant reminder/recall campaigns by ensuring notifications follow applicable state regulations and reach patients at their proper state location.
• Enables proper vaccine allocation, tracking, and reporting aligned with jurisdiction-specific program rules, supporting accurate accountability for federally-supplied vaccines such as VFC by identifying the responsible state program for each patient.
• Facilitates coordination with relevant state health authorities to implement jurisdiction-specific emergency protocols and manage vaccine distribution to partners and providers during disease outbreaks.

Functional Standard(s): 1.0, 4.0, 9.0, 10.0, 11.0, 12.0, 13.0, 15.0, 17.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The county component of the patient's address.

Rationale for inclusion:

• Validates patient demographic and vaccinationdata by ensuring that county-level information is accurate, facilitating proper tracking of immunization efforts within individual counties and ensuring geographic-specific vaccine management.
• Supports the generation of coverage reports by using county data to assess vaccine coverage at a localized level, enabling focused interventions in areas with lower vaccination rates.
• Aids in reporting of vaccine adverse events by ensuring accurate county-level data for follow-up and investigation, helping to identify and manage adverse events on a localized scale.
• Supports ad-hoc queries of vaccination data and demographic information at the county level, allowing for targeted analysis and intervention within specific counties.
• Requires the IIS to implement security measures including encryption, access controls, and audit logging to protect patient county information as protected health information (PHI) under HIPAA regulations.
• Enables the IIS to conduct geographically-targeted reminder/recall campaigns at the county level, allowing immunization programs to coordinate with local health departments and community organizations.

Functional Standard(s): 1.0, 4.0, 10.0, 11.0, 12.0, 13.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)
• Generated by IIS

Description: The country component of the patient's address.

Rationale for inclusion:

• Validates patient demographic and vaccination data by ensuring that country-level information is included, enabling global reporting and consistency in vaccination tracking, especially for international health programs.
• Supports the generation of coverage reports by including country data to track immunization efforts across countries, helping to identify trends, gaps, and progress toward global immunization goals.
• Aids in the reporting of vaccine adverse events by ensuring that country information is linked to patient records for follow-up and investigation, particularly in multi-country vaccination programs.
• Supports ad-hoc queries to verify vaccination status and demographic data by utilizing country information, ensuring that vaccine tracking is consistent across borders for international reporting purposes.
• Mandates implementation of appropriate safeguards such as data encryption, role-based access controls, and activity monitoring to protect patient country information as PHI in compliance with HIPAA and relevant privacy laws.
• Facilitates accurate jurisdictional reporting by distinguishing between domestic and international addresses, ensuring vaccination data is properly categorized for CDC and state immunization program requirements.
• Enables the IIS to appropriately route or exclude reminder/recall notifications based on international addresses, preventing mailings to countries where the program doesn't operate or where notifications may not be deliverable.
• Supports identification of patient populations outside the United States who may require special vaccine distribution channels or coordination with foreign healthcare authorities during disease outbreaks or emergency vaccination campaigns.

Functional Standard(s): 1.0, 4.0, 9.0, 10.0, 11.0, 12.0, 13.0, 17.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: Unique identifier assigned by the data source to the patient.

Rationale for inclusion:

• Enhances demographic validation efforts by integrating patient ID information into records, which helps ensure accurate linkage of vaccination data to individuals and improves the overall reliability of demographic information within the IIS.
• Requires implementation of appropriate safeguards such as data encryption, role-based access controls, and activity monitoring to protect patient ID information as PHI in compliance with HIPAA requirements.

Functional Standard(s): 1,0, 4.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The type of identifier (e.g., medical record number) assigned to the patient.

Rationale for inclusion:

• Improves demographic validation processes by incorporating various patient identifier types (such as Medical Record Number) into records, which aids in accurately linking vaccination data to individuals and enhances the overall integrity of demographic information within the IIS.
• Drives implementation of security measures including data encryption, access restrictions, and audit trails to protect patient ID information as PHI under HIPAA regulations.

Functional Standard(s): 1.0, 4.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The unique identifier assigned by IIS to each patient.

Rationale for inclusion:

• Assists in validating patient IDs to link them with vaccination data, ensuring accurate immunization tracking.
• Facilitates accurate immunization forecasting and supports the integration of patient data with external systems.
• Supports partner onboarding and vaccine management during public health emergencies, such as vaccine-preventable disease outbreaks.
• Ensures compliance with federal and jurisdictional vaccine program reporting requirements.
• Necessitates the application of protective controls such as encryption, role-based access, and activity logging to secure patient ID information as PHI in accordance with HIPAA.

Functional Standard(s): 1.0, 4.0, 6.0, 9.0, 17.0

Repeat: No

Data Source: Generated by IIS

Description: The first name of the patient's mother.

Rationale for inclusion:

• Validates patient demographic and vaccination data by ensuring the patient's first name is accurately recorded.
• Supports the reporting needs of federal and jurisdictional immunization programs by linking the first name to vaccination records for accurate identification and reporting.
• Drives implementation of protective measures such as data encryption, role-based access controls, and activity monitoring to secure mother's first name as PHI in compliance with HIPAA requirements.

Functional Standard(s): 1.0, 4.0, 9.0, 10.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The middle name of the patient's mother.

Rationale for inclusion:

• Ensures that the middle name is accurately recorded, aiding in the validation of patient demographic and vaccination data.
• Supports compliance with federal privacy and security standards that safeguard this sensitive demographic identifier from unauthorized access or disclosure.

Functional Standard(s): 1.0, 4.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The last name of the patient's mother.

Rationale for inclusion:

• Helps validate patient demographic and vaccination data by accurately recording the last name, which is essential for ensuring the correct patient is associated with their vaccination history.
• Supports the reporting needs of federal and jurisdictional immunization programs by ensuring the patient's last name is included in all reports.
• Requires application of security safeguards including encryption, access restrictions, and audit trails to protect mother's married name as protected health information under HIPAA regulations.

Functional Standard(s): 1.0, 4.0, 9.0, 10.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The last name under which the mother was born (i.e., before marriage)

Rationale for Inclusion:

• Enhances demographic validation processes by incorporating mother's maiden name as an additional identifier, which helps to accurately match patient records and reduce the risk of misidentification within the IIS.
• Requires the IIS to implement appropriate security controls including encryption, access restrictions, and audit trails to safeguard this PHI under HIPAA regulations.

Functional Standard(s): 1.0, 4.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: Formal name which corresponds to patient's legal name, as recorded on official documentation.

Rationale for inclusion:

• Supports electronic data exchange by facilitating precise record matching during system-to-system data transfers.
• Enhances immunization forecasts by improving accuracy when combined with other data for tailored vaccination schedules.
• Aids vaccine adverse event reporting, ensuring adverse documentation events is associated with the correct individual.
• Improves partner and provider onboarding processes by ensuring data consistency.
• Supports ad-hoc queries and reminder/recall activities, directing search results and outreach efforts to the right person and minimizing errors or confusion.
• Supports accurate immunization forecasting by ensuring each patient has a unique record in the IIS, preventing vaccination histories from being incorrectly combined across different individuals.
• Facilitates ad-hoc patient record searches and retrieval, particularly when used in combination with other identifying information such as date of birth or last name.
• Assists in adverse event surveillance by enabling proper patient identification, allowing healthcare providers and public health staff to accurately link safety reports to the correct vaccination records and monitor cases throughout the investigation process.

Functional Standard(s): 1.0, 4.0, 5.0, 6.0, 9.0, 10.0, 11.0, 13.0, 17.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The patient's legal given name.

Rationale for inclusion:

• Supports partner onboarding and vaccine management during vaccine-preventable disease responses and public health emergencies by ensuring accurate data entry and record matching.
• Enables ad-hoc queries of patient demographic and vaccination data, assisting providers and public health officials in verifying patient records and immunization statuses.
• Facilitates reminder/recall activities by accurately identifying patients who are due or overdue for vaccinations, improving coverage rates.
• Validates patient demographic and vaccination data, reducing errors and enhancing data quality across systems.
• Helps maintain separate patient records in the IIS to ensure immunization forecasts reflect each individual's actual vaccination history rather than merged or confused data from multiple patients.
• Allows users to search for and locate patient information through ad-hoc queries, working together with other demographic fields like surname and birth date to identify specific records.
• Enables accurate tracking and investigation of vaccine adverse events by helping to correctly identify patients and connect safety reports to their corresponding immunization records during surveillance activities.

Functional Standard(s): 1.0, 4.0, 5.0, 6.0, 9.0, 10.0, 11.0, 13.0, 17.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The patient's legal middle name.

Rationale for inclusion:

• Improves the accuracy of patient identification by incorporating middle names, which helps minimize data duplication and misidentification within the IIS, thereby safeguarding the integrity of protected health information.
• Enhances demographic validation efforts by ensuring that vaccination records are accurately associated with individuals, thus improving the quality and reliability of data.
• Facilitates effective onboarding for partners and providers by offering comprehensive patient identifiers, which are vital during vaccine management activities in response to public health emergencies or disease outbreaks.
• Bolsters outreach initiatives by enabling more targeted reminder and recall campaigns based on complete patient demographics, ultimately increasing vaccination compliance rates among diverse populations.
• Prevents confusion between different patients' vaccination records, ensuring that recommended immunization schedules and forecasts are based on the correct individual's history.
• Serves as a key search field for locating patient records on demand, especially when paired with additional identifiers such as last name or date of birth.
• Supports vaccine safety monitoring by ensuring adverse event reports are accurately matched to the right patient and their immunization history during investigation and surveillance efforts.

Functional Standard(s): 1.0, 4.0, 5.0, 6.0, 9.0, 10.0, 11.0, 13.0, 17.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The patient's legal surname.

Rationale for inclusion:

• Strengthens patient record accuracy by incorporating last names, which are essential for distinguishing between individuals with similar first names, thereby enhancing the reliability of health information within the IIS.
• Improves demographic data validation by ensuring that last names are part of the comprehensive dataset used to cross-reference and confirm vaccination records, thus supporting high-quality data management practices.
• Facilitates seamless partner and provider collaboration during vaccine distribution efforts by utilizing last names as key identifiers, which aids in maintaining clear and effective communication in public health initiatives.
• Enhances targeted public health outreach by allowing for more precise segmentation of patient populations based on complete demographic profiles, leading to more effective reminder and recall strategies that can boost vaccination rates.
• Ensures immunization forecasts are aligned by maintaining accurate individual patient records and preventing confusion between different patients' vaccination histories.
• Functions as a primary search criterion for retrieving patient information, particularly effective when combined with other demographic details like surname or birth date.
• Facilitates proper linkage of adverse event reports to the correct patient's vaccination records, supporting effective safety monitoring and investigation activities.

Functional Standard(s): 1.0, 4.0, 5.0, 6.0, 9.0, 10.0, 11.0, 13.0, 17.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The patient's alternate or also-known-as name.

Rationale for inclusion:

• Used to validate patient demographic and vaccination data by ensuring records with alternate names (e.g., nicknames or maiden names) are correctly matched and maintained in the IIS, reducing duplication and errors.
• Facilitates record linking across systems where different aliases might have been used, improving interoperability and ensuring comprehensive vaccination histories.

Functional Standard(s): 1.0, 4.0

Repeat: Yes

Data Source: Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The patient's alternate or also-known-as-first name.

Rationale for inclusion:

• Enhances patient identification accuracy by allowing for the documentation of patient's alias first names, which helps distinguish individuals who may go by different names in various settings, thereby minimizing the risk of record mismatches.
• Strengthens demographic validation efforts by integrating patient's alias first names into the dataset, ensuring that vaccination records are correctly associated with individuals who may be known by multiple names, thus bolstering overall data quality.

Functional Standard(s): 1.0, 4.0

Repeat: No

Data Source: Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The patient's alternate or also-known-as-middle name.

Rationale for inclusion:

• Improves patient identification precision by incorporating patient's alias middle names, which can help differentiate individuals with similar first and last names, thereby reducing the likelihood of record confusion.
• Enhances demographic validation capabilities by including patient's alias middle names in the dataset, ensuring that vaccination records are accurately matched to individuals who may use different names in various contexts, thus reinforcing data integrity.

Functional Standard(s): 1.0, 4.0

Repeat: No

Data Source: Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The patient's alternate or also-known-as-surname.

Rationale for inclusion:

• Enhances patient identification accuracy by allowing for the inclusion of patient alias last names, which helps distinguish individuals who may share similar first names or have common surnames, thereby reducing potential record conflicts.
• Strengthens demographic validation processes by integrating patient alias last names into the dataset, ensuring that vaccination records are correctly associated with individuals who may be known by different surnames in various situations, thus improving overall data quality.

Functional Standard(s): 1.0, 4.0

Repeat: No

Data Source: Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The current active/inactive status of the patient in relation to the provider organization.

Rationale for inclusion:

• Facilitates ad-hoc queries of patient demographic and vaccination data by incorporating the active/inactive status, allowing healthcare providers and public health officials to quickly filter and access relevant records based on patient engagement levels.
• Ensure the ability to generate coverage reports that are relevant to active patients, thereby improving the reliability of the data and reducing the need for assistance from IIS staff.

Functional Standard(s): 10.0, 12.0

Repeat: No

Data Source: Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The current active/inactive status of the patient in relation to the jurisdiction.

Rationale for inclusion:

• Supports the ability to generate coverage reports by including jurisdiction data, which helps in tracking immunization status across different regions and meeting jurisdictional reporting requirements.
• Enables flexible searching of patient demographics and vaccination records by including active/inactive status, allowing providers and public health officials to efficiently filter results based on current patient engagement.
• Helps the IIS target reminder/recall activities to active patients within the jurisdiction's authority, avoiding outreach to patients who have moved away or are no longer engaged with local providers.

Functional Standard(s): 10.0, 12.0, 13.0

Repeat: No

Data Source: Generated by IIS

Description: The patient's phone number.

Rationale for inclusion: Facilitates reminder and recall initiatives by offering a direct line of communication with patients, allowing for timely outreach regarding vaccination reminders and follow-up appointments, thereby increasing vaccination compliance rates.

Functional Standard(s): 13.0

Repeat: No

Description: The type of phone number (e.g., home) for each patient's telephone number.

Rationale for inclusion: Supports reminder and recall activities by allowing healthcare providers to tailor communication strategies based on the type of phone number provided, ensuring that outreach efforts are effective and reach patients through their preferred contact method.

Functional Standard(s): 13.0

Repeat: No

Description: Indicates whether a patient's information may be shared with others.

Rationale for inclusion: Enhances the security of the IIS by identifying and flagging sensitive patient information that requires additional safeguards.

Functional Standard(s): 1.0

Repeat: No

Data Source: Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The effective date for the protection indicator.

Rationale for inclusion:

• Strengthens the security of the IIS by identifying and marking sensitive patient information that necessitates extra protections.
• Implements role-based access controls to ensure that authorized users can access only the sensitive information pertinent to their roles and permissions, thereby improving data security and safeguarding patient privacy.

Functional Standard(s): 1.0, 7.0

Repeat: No

Data Source: Vaccination Event (for example, reported by an EHR of a hospital system)

Description: Indicates whether a person consents to being contacted for reminder or recall purposes.

Rationale for inclusion: Tracks the status of reminder/recall activities, ensuring that notifications are properly sent and followed up on, improving vaccination compliance.

Functional Standard(s): 13.0

Repeat: No

Data Source: Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The effective date for the patient's reminder/recall status.

Rationale for inclusion: Specifies the date when a reminder or recall becomes effective, ensuring timely notification for vaccination follow-ups.

Functional Standard(s): 13.0

Repeat: No

Data Source: Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The first name of the person responsible for the patient.

Rationale for inclusion:

• Validates patient demographic and vaccination data by associating the patient with a responsible person's first name, ensuring accurate tracking and identification of guardians or caregivers.
• Drives application of protective measures such as data encryption, role-based access controls, and activity monitoring to secure responsible person name information as PHI in compliance with HIPAA requirements.

Functional Standard(s): 1.0, 4.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The middle name of the person responsible for the patient.

Rationale for inclusion:

• Ensures that middle names of responsible persons are recorded for validation purposes, linking accurate demographic and vaccination data.
• Supports compliance with federal privacy and security standards that prevent unauthorized users from accessing or disclosing this sensitive contact data.

Functional Standard(s): 1.0, 4.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The last name of the person responsible for the patient.

Rationale for inclusion:

• Supports the validation of patient data by ensuring the last name of the responsible person is correctly recorded, aiding in accurate tracking of vaccination data and ensuring proper identification for reporting.
• Ensures adherence to federal security standards that safeguard this sensitive contact identifier from unauthorized access or disclosure.

Functional Standard(s): 1.0, 4.0

Repeat: No

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)

Description: The personal relationship that the responsible person has to the patient.

Rationale for inclusion:

• Validates patient demographic and vaccination data by categorizing the relationship type between the patient and their responsible person (e.g., mother, father, guarantor), ensuring the data reflects the correct familial link.
• Drives implementation of security safeguards including encryption, access restrictions, and audit trails to protect responsible person relationship type information as protected health information under HIPAA regulations.

Functional Standard(s): 1.0, 4.0

Repeat: Yes

Data Source:

• Vital Records
• Vaccination Event (for example, reported by an EHR of a hospital system)