EHDI Database
Iowa Newborn Screening Information System (INSIS) is a NEW integrated, web-based data system that serves as the statewide tracking and surveillance system for children from birth to age 3 for all newborn screening programs in Iowa. These programs are; EHDI, Critical Congenital Heart Disease (CCHD) and Dried Blood Spot.
INSIS is password-protected data system and access into the system is only available to approved parties. To gain access into INSIS (because you screen or diagnose children under the age of 3), receive a copy of a previously recorded training or to schedule a live training, please contact EHDI staff.
INSIS Supporting Documents:
Newborn Admission Notification Interface (NANI) Tool:
NANI is the application that accepts and processes ADT messages that contain demographic (contact) information about newborn patients. The information is used to follow-up with a newborn’s contact for follow-up care. Therefore, it is critical that the contact information be as complete and accurate as possible when the outreach takes place. NANI outperforms human data entry in two measurable ways: it works during labor shortages and outages, and it gathers even the most up-to-date information available for the patient’s contact. Addresses and phone numbers are not infrequently updated after a patient is discharged, and if that new information is shared with your facility, NANI will receive and process it. All data is exchanged using industry standards to protect patient information.
Importing Demographics Tool:
Hospitals have the ability to electronically import all important demographic information directly from their electronic medical health records system (or admitting or patient account systems) using the demographic import tool in INSIS. No software is needed to set up the import. INSIS has the capability of electronically populating the majority of the required reporting fields- except for the infant’s primary care provider at this time. An import file is created by the hospital’s IT department that contains demographic information for each patient born the previous day. Many IT departments write ASCII files to interface with other hospital databases and this is the same concept.
You might ask how this works. The hospital IT department will run a query or job to create an import file on a daily basis. This file will contain the demographic information that you select as necessary for your patient records in INSIS. An INSIS user at your hospital will use the import function daily to import the demographics file which will automatically create new patient records.
The hospital’s hearing screening manager, along with the hospital’s IT department should work together to determine the contents of the ASCII file. Please set up your import to capture as many fields as you can. Most hospitals choose to enter risk factors manually versus through the import but some have also been able to import those. If you import all the necessary fields, you will only need to enter the primary care provider, risk factors (if you cannot capture them through the import) and then move the patient from inpatient to outpatient and enter the discharge date! Importing information from hospital records saves time and also reduces the number of data entry errors. Below you will find a data dictionary which includes a list of possible elements to include in the file and how they must be coded. It is NOT necessary to include every element, if you do not have that element, however, some are required fields that you will recognize. Once you have a sample file ready, OZ Systems (our vendor), will test the file before going “live.” This helps us to ensure the file is set up correctly and everything is working properly. Please contact EHDI staff when you are ready to have the file tested or have specific questions about the process.
Once IT creates the file and it has been tested by the vendor, a one-time setup in INSIS is required and the configuration can be saved for repeated use. The final document below, Importing Instruction Sheet, is for creation of the import map. It outlines the decisions that will need to be made as to what type of file to create (i.e. tab delimited, inclusion of headers, etc.) EHDI staff will schedule an online meeting to walk INSIS users through the steps to set up the import map and do the import after the file is tested and approved by the vendor.
These example test files will provide a visual of what a sample file may look like. It is not complete but will give your IT contacts an idea of what is needed
