EARS Data Requirements
EARS can accept data in one of the following five formats:
Format 1
The example below shows the minimum data required by EARS when the event that EARS is monitoring is already included in the record.
View text version of this image.
In this situation, the minimum data fields required for EARS processing are the event, date, and count fields.
Format 2
EARS can search a text field for key event words that you specify. The example below shows the minimum data required by EARS when a text field is searched in order to determine the event.
View text version of this image.
In this example, EARS uses an internal function called Indicator Processing to search the chief_complaint field for specific words that are embedded within the EARS code. These key words describe important events that EARS should monitor. Therefore, the minimum requirements for EARS when using Indicator Processing are a date field (numeric type), a record identification field (character type), and a field that contains text for Indicator Processing to search (character type).
Format 3 (only accepted by EARS-SAS v5.1)
This example is similar to Format 2, but the chief_complaint values have already been assigned to an Indicator. EARS will sum up the Indicator values resulting in a table that resembles Format 1 in structure.
DATE * |
Patient ID |
chief_complaint |
INDICATOR* |
8/29/2004 |
22 |
RESPIRATORY DISTRESS |
Respiratory |
8/29/2004 |
23 |
ALLERGIC REACTION RASH, LT EAR ACHE |
Rash, Respiratory |
8/29/2004 |
24 |
SEVERE SORE THROAT |
Respiratory |
8/29/2004 |
25 |
SORE THROAT AND FEVER |
Influenza-like Illness |
8/30/2004 |
26 |
WANTS PRESCRIPTION REFILL |
|
8/30/2004 |
27 |
CHEST TIGHTNESS SOB |
Dyspnea |
In this situation the minimum field requirements are a date, a record identification field, and an indicator (like a syndrome category).
Format 4
Data is sometimes submitted in a form such as the following example:
View text version of this image.
In the above example, the column heading (illness_a) is followed by a series of numbers in the column. The column heading represents an event name; the numbers below it represent the total occurrences of the event on a particular date. EARS transposes this type of field into two individual fields. The resulting fields are: (1) a field that lists the event name, and (2) a field that lists the total count for that event.
EARS transposes the data above into data as shown below. After transposing the data, EARS analyzes and reports the data.
View text version of this image.
Format 5 (only accepted by EARS-SAS v5.1)
Data can also be analyzed by EARS-SAS v5.1 if in the following form:
DATE* |
Patient ID |
illness_a* |
illness_b* |
illness_c |
illness_d |
8/29/2004 |
22 |
0 |
1 |
0 |
0 |
8/29/2004 |
23 |
1 |
0 |
0 |
0 |
8/29/2004 |
24 |
1 |
0 |
0 |
1 |
8/29/2004 |
25 |
0 |
0 |
1 |
0 |
In this form individual records have already been assigned to Indicator categories using a binary system, but more than one indicator exists. The binary values must be “1” and “0”, with a value of “1” designating the record maps to the indicator, and a value of “0” designating the record does not map to the indicator. One record may map to multiple observations (as is shown with patient ID #24).
If you provide this structure, EARS will sum the data in the indicator fields and then transpose them. EARS transposes the indicator fields into two individual fields. The resulting fields, as shown below are: (1) a field that lists the event name, and (2) a field that lists the total count for that event. After transposing the data, EARS analyzes and reports the data.
- Page last updated November 3, 2005
- Content source: CDC Emergency Risk Communication Branch (ERCB), Division of Emergency Operations (DEO), Office of Public Health Preparedness and Response (OPHPR)
Get email updates
To receive email updates about this page, enter your email address:
Contact Us:
- Centers for Disease Control and Prevention
1600 Clifton Rd
Atlanta, GA 30333 - 800-CDC-INFO
(800-232-4636)
TTY: (888) 232-6348 - Contact CDC-INFO
