Record of vaccine administration.
Data Element
|
Texas IIS Consent Date
Description
This variable contains the date consent was obtained or changed. When a provider queries ImmTrac for a patient and a patient who has already consented is found, the query will return the Texas IIS Consent Date stored in the registry. The provider, at the patient’s (or parent/guardian’s direction, as appropriate) can change the consent status. If there is a change, the updated Texas IIS Consent Date should be submitted to the IIS. Texas IIS Consent Date should be stored in date format: YYYYMMDD.
|
| Submitted By: Texas Immunization Registry - ImmTrac
|
| Data Element Information |
| Use Case Description(s) |
| Use Case Description |
The Texas Immunization Information System (ImmTrac), operated by the Department of State Health Services (DSHS) currently provides services for over 2,900 health care providers (including hospitals, clinical practices, and providers). ImmTrac has information for XXXXXXXX individuals. The ImmTrac staff continues to work with Texas providers to onboard into ImmTrac.
Texas state law requires that DSHS operate the ImmTrac IIS as an opt-tin registry.Registry consent is sent only once at the time it was obtained from the individual
• Organizations utilize their EHR vendor to send Texas’ = registry consent values to the Texas IIS.
• Registry record is created based on the values submitted by the provider.
• Immunizations reported are stored in their record and available to authorized providers when the IIS is queried.
2) Capture date of registry consent
• Only required when sending affirmation of consent via PD1-12
• Captures the date the registry consent was signed by the individual or the individual’s legal guardian.
2) Capture disaster consent (TXD)
• Captured iusing unique value of TXD
• TXD is not age-specific |
| Estimate the breadth of applicability of the use case(s) for this data element
|
2,900 health care providers (including hospitals, clinical practices, and providers). ImmTrac has information for XXXXXXXX individuals. |
| Link to use case project page |
https://www.dshs.texas.gov/immunize/immtrac/forms.shtm#For General Public |
| Healthcare Aims |
- Improving patient experience of care (quality and/or satisfaction)
- Improving the health of populations
- Reducing the cost of care
- Improving provider experience of care
|
| Maturity of Use and Technical Specifications for Data Element |
| Applicable Standard(s) |
N/A |
| Additional Specifications |
N/A |
| Current Use |
In limited use in test environments only |
| Extent of exchange
|
N/A |
| Potential Challenges |
| Restrictions on Standardization (e.g. proprietary code) |
Most states use protection indicators (Y,N), which are captured in PD1-12 to determine whether or not a registry record is created for an individual. Texas being one of two Opt-In states, does not utilize Y or N to create registry records. Patients must provide their written consent using an official DSHS consent form. The consent form will determine which unique value will be populated in PD1-12.
EHR vendors are finding it difficult to accommodate Texas’s unique values because a majority of the other states only utilize Y or N values.
EHR vendors are also finding it difficult to send registry consent only once (at the time it was obtained) and not at every occurrence of reporting data (not saving an individual’s response in PD1-12).
|
| Restrictions on Use (e.g. licensing, user fees) |
Only cost associated would be to the EHR vendors who would have to build to meet to the PD1-12 requirements for Texas. |
| Privacy and Security Concerns |
None |
| Estimate of Overall Burden |
The EHR vendors are the ones currently facing the burden of trying to determine how they’ll build to meet Texas’s requirements. |
|
Comment