Skip Navigation Links
Centers for Disease Control and Prevention
CDC
CDC CDC Home Search Health Topics A-Z
Contact Help Travelers Health n i p Home NIP header
Health Care Professionals

Registries: Immunization Information Systems (IIS)
IIS Home
What's New?
Upcoming Events
Parents menu
Providers menu
States/Territories menu
Partner Organizations
Pubs & Resources
Contacts
Acronyms

NIP:
NIP HOME
First time visitor?
About NIP
Data and Statistics
International Efforts
Links to other web sites 
bullet Glossary/ Acronyms 

NIP sub-sites:
ACIP
Flu Vaccine
Immunization Registries
Vaccines for Children Program
CASA (Clinic Assessment Program)
AFIX (Grantee Assessment)
VACMAN
 

NIP Site Search
 
For Immunization Information, call the
CDC-INFO Contact Center:
English and Spanish
800-CDC-INFO
800-232-4636
TTY
888-232-6348

Get Acrobat Reader
Get Adobe Reader
Home Health Care Professionals Homepage Partners Homepage Media Homepage Informacion en Espanol Health Care Professionals
 
Registries: Immunization Information Systems
States/Cities/Territories
IIS logo
Recommended Core Data Set

Contents of this page:


What is the core data set?
This core data set was prepared in 1995 by the National Immunization Program (NIP) in consultation with the Immunization Grantee Working Group. It was reviewed by the National Vaccine Advisory Committee (NVAC), and recommendations of NVAC were incorporated. Contributions were also made by public health representatives and private providers.

The core data elements fall into two categories: required and optional. In addition, two functions for future consideration are presented here. Required core data elements are listed in bold print. These elements represent fundamental attributes necessary for identifying individuals and for describing immunization events. Required elements are critical to the record exchange process. Optional core data elements are less important for record exchange. Some optional items (e.g., address) may be useful only at the local level.

The purpose of the core data set is to facilitate record exchange between immunization information systems (IIS). It is imperative that, at a minimum, each IIS include in its database schema a method to receive and store all of the required core data elements, even if the IIS does not routinely collect the information. Thus, if an IIS receives a record from one system and subsequently transfers it to another, no required core data elements will be lost in the process. It is strongly recommended that IIS also collect data on all of the required core data elements for their own patients.


printable version of file in .pdf format Printable version of Core Data Set (.pdf)

Listing of Core Data Set
(Required data elements are listed in bold print.)

Patient/System/State Identifiers
(Until a unique personal identifier can be established on a national basis, multiple means of identification must be used.)
Patient name: first, middle, last
Patient alias name: first, middle, last
(former names for management of adoptions & name changes)
Patient address, phone number, birthing facility
(these variables should be locally defined)
Patient Social Security number (SSN)
Patient birth date
Patient sex
Patient race
Patient primary language
Patient birth order
Patient birth registration number
Patient birth State/country
Patient Medicaid number
Mother's name: first, middle, last, maiden
Mother's SSN
Father's name: first, middle, last

Father's SSN

 

Immunization Event Identifiers
Vaccine type
(Use HL7-defined Table 0292 - Vaccines Administered (code=CVX) found in Appendix 1. Note that up-to-date cvx versions of this table will be maintained on the NIP website at <www.cdc.gov/nip/registry>.)
Vaccine Manufacturer
(Use HL7-defined Table 0227 - Manufacturers of vaccines (code=MVX) found in Appendix 1. Note that up-to-date mvx versions of this table will be maintained on the NIP website at <www.cdc.gov/nip/registry>.)
Vaccine dose number
NOTE: With a fully operating system, this variable is not needed. However, in the real world, and particularly during the initial startup phase, many systems will be gathering partial histories; therefore, to evaluate histories properly, dose number becomes very important. The ultimate goal would be to remove this variable from the core data set, within the first 2 to 3 years of system operation.
Vaccine expiration date
Vaccine injection site
Vaccination date
Vaccine lot number

Vaccine provider

 

Functions for Future Consideration
Vaccine adverse events monitoring
[Such events must be linkable to the existing national adverse events surveillance system, with immunization information systems having ability to electronically report, without redundant keying of information to the Vaccine Adverse Events Reporting System (VAERS).]

Vaccine preventable disease reporting

[Such disease events must be linkable to existing local, state and national disease reporting systems, with the immunization information systems having ability to electronically report, without redundant keying of information to the appropriate disease reporting systems.]

Top of page


National Immunization Program (NIP)
NIP Home | Contact Us | Help | Glossary | About | Accessibility

This page last modified on September 7, 2005

   

Department of Health and Human Services
Centers for Disease Control and Prevention
CDC Home
  |  CDC Search  |  CDC Health Topics A-Z