The following disability variables are available in the PTC:
- ANY_HEALTH_ALERT_FIRST_TERM -- DO NOT USE, see note below
- ANY_HEALTH_ALERT_CODE -- DO NOT USE, see note below
- ANY_HEALTH_ALERT_DESC -- DO NOT USE, see note below
- WHEELCHAIR_FIRST_TERM -- DO NOT USE, see note below
- WHEELCHAIR_CODE -- DO NOT USE, see note below
- WHEELCHAIR_DESC -- DO NOT USE, see note below
- BLIND_FIRST_TERM -- DO NOT USE, see note below
- BLIND_CODE -- DO NOT USE, see note below
- BLIND_DESC -- DO NOT USE, see note below
- BRACES_AND_CRUTCHES_FIRST_TERM -- DO NOT USE, see note below
- BRACES_AND_CRUTCHES_CODE -- DO NOT USE, see note below
- BRACES_AND_CRUTCHES_DESC -- DO NOT USE, see note below
- DEAF_FIRST_TERM -- DO NOT USE, see note below
- DEAF_CODE -- DO NOT USE, see note below
- DEAF_DESC -- DO NOT USE, see note below
- NEUROLOGICAL_FIRST_TERM -- DO NOT USE, see note below
- NEUROLOGICAL_CODE -- DO NOT USE, see note below
- NEUROLOGICAL_DESC -- DO NOT USE, see note below
- SPEECH_IMPAIRMENT_FIRST_TERM -- DO NOT USE, see note below
- SPEECH_IMPAIRMENT_CODE -- DO NOT USE, see note below
- SPEECH_IMPAIRMENT_DESC -- DO NOT USE, see note below
- CARDIAC_CONDITION_FIRST_TERM -- DO NOT USE, see note below
- CARDIAC_CONDITION_CODE -- DO NOT USE, see note below
- CARDIAC_CONDITION_DESC -- DO NOT USE, see note below
- SEIZURES_FIRST_TERM -- DO NOT USE, see note below
- SEIZURES_CODE -- DO NOT USE, see note below
- SEIZURES_DESC -- DO NOT USE, see note below
- LEARNING_DISABILITY_TERM -- DO NOT USE, see note below
- LEARNING_DISABILITY_CODE -- DO NOT USE, see note below
- LEARNING_DISABILITY_DESC -- DO NOT USE, see note below
- OTHER_IMPAIRMENT_TERM -- DO NOT USE, see note below
- OTHER_IMPAIRMENT_CODE -- DO NOT USE, see note below
- OTHER_IMPAIRMENT_DESC -- DO NOT USE, see note below
- UNSPECIFIED_ALERT_TERM -- DO NOT USE, see note below
- UNSPECIFIED_ALERT_CODE -- DO NOT USE, see note below
- UNSPECIFIED_ALERT_DESC -- DO NOT USE, see note below
- DISABLED_FIRST_TERM_DATE
- DISABLED_FLAG
- SINGLE_PARENT_FLAG
- LIMITED_ENGLISH_FLAG
- EDUCATIONAL_DISADVANTAGE_FLAG
- POOR_FIRST_TERM_DATE
- POOR_LAST_TERM_DATE
- ECONOMIC_DISADVANTAGE_FLAG
In the previous PTC syntax, we have drawn disability data from two tables:
- HEALTH_ALERT_DIM (ANY_HEALTH_ALERT_FIRST_TERM -UNSPECIFIED_ALERT_DESC)
- SPECIAL_POPULATION_DIM (DISABLED_FIRST_TERM_DATE - ECONOMIC_DISADVANTAGE_FLAG)
The first table (HEALTH_ALERT_DIM) is one that we should no longer use. It was populated with data from the UAPC from a question that was asked on the application. It came in with the SHOW data. In 2000, this question was challenged by advocates and removed from the application. Starting in 2001, we shifted the reporting to the campus disability service offices. Now the offices update the student’s file to indicate that they have requested services and we receive that data with the PERF data (in case a student doesn’t request services until just before the final).
There will always be a difference between the numbers that we come up from the IRDB and those we report to the state because Caryn has to use the flat files due to the time constraint of when the state wants the numbers.
As a note, the % of students requesting services always seems to float around 2%. This is less than SUNY’s 4% (and national averages). Interestingly, the 6 year grad rates are similar for those using disability services and the rest of CUNY’s undergrads.
All of this means that we only should be using data from the SPECIAL_POPULATION_DIM, and that we only really need the field DISABLED_FLAG if all we are concerned with is who requested ANY services (and not what particular kind of services they needed). Caryn states that these data can be separated out into semester-based versions and that it is possible for the designation to change (if a student breaks a leg and needs mobility services for that semester, for example).
A final note: because the data collection policy changed in 2000, the first year for which we have good DISABLED_FLAG data is 2002. There are some cases in 2001, but it’s about half the number it should be. I will include this constraint in the extract. I will also update the data dictionary to include this information (I really need to do an update with the new extract anyway).