IN03: NCANDS (National Child Abuse and Neglect Data System)centerforchildwelfare.fmhi.usf.edu/kb/FSFN/NCANDS Topic Paper.pdf · IN03: National Child Abuse and Neglect Data System

IN03: NCANDS (National Child Abuse and Neglect Data System)

May 12, 2017

Change History

Release # or

Date

CR# or

Incident # Change Description Author(s) Section Modified

12/15/2013 Updates to support FSFN

R2 system enhancements

FSFN

Enhancements

Team

All

7/30/2014 –

8/1/2014

Updates based on

collaborative review

between IBM and DCF

Amy Jenks All

9/4/2014 Updates based on DCF

review and feedback

Amy Jenks Page 14 – clarifications

regarding the NCANDS

error file versus the

NCANDS Exception

Report

2/2/2015 CR-530 Updates based on CR Leah Dienger

2/2/2015 CR-531 Updates based on CR Leah Dienger

2/20/2015 Updates based on new

Encryption logic

Leah Dienger

2/23/2015 –

2/24/2015

Peer Review and Updates

based on additional

feedback from the

Department

Amy Jenks Encryption logic; Element

12, 43, 52-55 and all

elements related to

encryption

2/25/2015 Additional feedback

received from Robin, as

well as additional

corrections to ensure

Elements 56-85 do not

reference the access

report received date. This

is per CR531.

Amy Jenks Confirmed Robin’s

corrections were accurate

and do not require any

code changes, only

clarifications/ corrections

to the Topic Paper

language. Also made

additional corrections to

Elements 56-85 to ensure

access report received is

not referenced in the logic

which is consistent with

the previous code

changes for CR531.

03/08/2017 CR639 Updates to Elements 9,

26, 28, 30, 32 and 52

Amy Jenks Page 21 Field 9; Page 49

Field 52; and Page 105

Section 2.2.4 Mapping

Florida Safe Families Network

IN03: National Child Abuse and Neglect Data System (NCANDS) May 12, 2017 Topic Paper Page 4 of 112

Table of Contents

1.1 Component Architecture ............................................................................................. 5

1.2 NCANDS_EXTRACT_T Table Details **CHANGE** ................................................... 6

1.3 Interface Definition ...................................................................................................... 7 1.3.1 The Child Data File .................................................................................................................. 8 1.3.2 Selection Logic ........................................................................................................................ 9 1.3.3 Transformations..................................................................................................................... 13 1.3.4 Encryption Logic **CHANGE** .............................................................................................. 14 1.3.5 Report Construction .............................................................................................................. 14 1.3.6 The Agency Data File ............................................................................................................ 15 1.3.7 Data Encryption/Decryption Utility ......................................................................................... 15 1.3.8 Encrypted Element Construction ........................................................................................... 15

2 NCANDS Child File Retrieval Logic or Calculation............................................. 17

2.1 Agency Data File .......................................................................................................96

2.2 FSFN Reference Values Document ...........................................................................98 2.2.1 Reporter – NC08 ................................................................................................................... 98 2.2.2 NC09, NC27, NC29, NC31, NC33 Disposition Levels ........................................................ 100 2.2.3 Living Arrangement (Family) – NC23 .................................................................................. 102 2.2.4 NC26, NC28, NC30, NC32 – Maltreatment Types .............................................................. 103 2.2.5 NC52 – NC55 Characteristics ............................................................................................. 105 2.2.6 NC90, 109, 128 Perpetrator as Parent ................................................................................ 106 2.2.7 Race-Ethnicity Matrix .......................................................................................................... 111



1.1 Component Architecture Figure 1 shows the National Child Abuse and Neglect Data System (NCANDS) batch process.

Two programs are involved in the NCANDS Federal report. The

B_IN0301_CREATE_NCANDS_EXT Java program collects and populates the database table

with Florida Safe Families Network (FSFN) data and the NCANDS_FLATFILE_GENERATOR

produces the Federal Report file from data collected in the previous program.

Figure 1 - NCANDS Batch Process



1.2 NCANDS_EXTRACT_T Table Details **CHANGE** The table below depicts the current columns in the NCANDS_EXTRACT_T Table. The Child

ID and Report ID contained within this table also need to be provided in the table unencrypted.

Currently the Child ID and Report ID are encrypted within this table, but not unencrypted. Just

as it is in the AFCARS and NYTD tables, these 2 IDs need to be provided in the table

unencrypted. The file generated and sent to the FEDs will include the encrypted IDs, but those

with FSFN access, having the security to access the NCANDS_EXTRACT_T Table, will have

the ability to pull data without having to unencrypt the IDs.



1.3 Interface Definition

Item Description

Interface Number 3

Interface Name NCANDS (National Child Abuse and Neglect Data System)

Program Name:

Topic: IN03

Interface Description This interface creates extract files of abuse and neglect report information from

SACWIS to comply with ACF reporting requirements.

Type Extracts of SACWIS data

Frequency Annually (Federal Fiscal Year – 10/01/CCYY – 9/30/CCYY); The submission

date is no later than January 31 annually.

Input SACWIS Data

The input parameter card for the NCANDS program contains the four-digit



reporting year in the format CCYY.

Output NCANDS Child File and Agency File

NCANDS (National Child Abuse and Neglect Data System) is a voluntary child abuse reporting

system that was designed in response to the Child Abuse Prevention, Adoption, and Family

Services Act of 1988. NCANDS is administered through the Data Team, under the Deputy

Associate Commissioner of the Children’s Bureau, U.S. Department of Health and Human

Services. The system’s purpose is to collect, compile, analyze, and make available child abuse

and neglect reporting information on a state-by-state basis. Regular NCANDS reporting is done

annually, submitting information by January 31 for the Federal Fiscal Year ending the previous

September.

The NCANDS report consists of two components:

The Child Data File – This is a 146-field file, compiled from the FSFN application, listing

individual reports of alleged child abuse and neglect and includes records for all children

involved in an investigation whether they are a child in the home or a victim.

The file contains significant information concerning:

o The report

o The child

o The alleged maltreatment

o Child risk factors

o Caregiver risk factors

o Services provided

o The staff involved at report disposition

o The perpetrators

The Agency Data File – This is a 26-field file, compiled by the DCF Program Office, of

computed values that provides data that cannot be derived from the Child Data File. The file

contains summary data at the state agency level.

1.3.1 The Child Data File

The Child Data File is a fixed-length record ASCII file. The file contains 146 fields and is 312

bytes long. Each field is fixed-width with no delimiters.

Each record in the file represents a unique report of abuse or neglect and pertains to exactly one

child. In the event that multiple children are involved in a single SACWIS report or



investigation, a different NCANDS record is created for each child. The record includes various

pieces of information that describe the demographics of the child and the alleged perpetrator.

Also included in each record is information that details the alleged maltreatment of the child. All

children involved in the investigation are reported, including those children where no allegations

are documented.

1.3.2 Selection Logic

NCANDS selection logic relies on an input parameter, the “submission year,” which is in four-

digit format. NCANDS requires that only investigations with completion dates that fall within

the reporting federal fiscal year be included on the report. For the Statewide Automated Child

Welfare Information Systems (SACWIS), the “Investigation Completed Date” on the

Investigation table is used to select the appropriate records. Use of the completion date ensures

that only records that have received the final level of approval are included.

The logic for this selection is as follows:

SELECT all Investigations where INVESTIGATION.DT_INVS_CMPL is greater than or equal

to the report period begin date and less than or equal to the report period end date and

ACCESS_REPORT.CD_INTL_SUB=1(Initial Intake) and

INVESTIGATION.CD_ACCESS_TYPE=1 (Child Intake) and

INTAKE_PART.CD_INTK_TYPE=“5” (Investigation Participant) and

(INTAKE_PART.CD_ROLE1 in (1, 15) or (INTAKE_PART.CD_ROLE2 in (1, 15)) or

(INTAKE_PART.CD_ROLE3 in (1, 15)) or (INTAKE_PART.CD_ROLE4 in (1, 15)) or

(INTAKE_PART.CD_ROLE5 in (1, 15))). (1 = Victim; 15 = Child In-Home)

Exclude Investigation’s where CD_DETERMINATION in (1, 2, 3, 4, 5, 6, 9, 10, 11, 12, 13, 14,

15, 16, 17, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36 and 38).

Therefore, we must include Investigation’s where CD_DETERMINATION in (7, 8, 18, 37 and

39). However, the logic will be written as an exclusion to ensure that if any new values are

added in the future, they will be “included” since they aren’t specified in the code as an

“exclusion”.

ID_GRP ID_GRPI CD_ACTIVE TX_DESC_LRG

CSADET 1 A Closing-Duplicate

CSADET 2 A Closing-No Jurisdiction-Official Capacity

CSADET 3 A Closing-No Jurisdiction-Non Caregiver

CSADET 4 A Closing-No Jurisdiction-Victim Out of State

CSADET 5 A Closing-No Jurisdiction-Federal Property



CSADET 6 A Closing-No Jurisdiction-Victim over 18

CSADET 7 A Closing-Services

CSADET 8 A Closing-No Services

CSADET 9 I Closing-Shell Investigation

CSADET 10 I Closing-Child-on-Child Sexual Abuse

CSADET 11 I Closing-Child-on-Child Sexual Abuse

CSADET 12 I Closing-Caregiver Hospitalized

CSADET 13 I Closing-Caregiver Incarcerated

CSADET 14 I Closing-Instititional Investigation

CSADET 15 I Closing-Caregiver Deceased

CSADET 16 I Closing- No Jurisdiction

CSADET 17 I Closing-Parent need Assistance

CSADET 18 I Closing-Patently unfounded

CSADET 19 I Closing-Wages Referral

CSADET 20 I Closing-Foster Care Referral

CSADET 21 I Closing-Alleged Perpetrator not responsible

CSADET 22 I Closing-Harasment-false report

CSADET 23 I Closing-Indian Reservation

CSADET 24 I Closing-Military installation

CSADET 25 I Closing-Other

CSADET 26 I Closing-Degree reletionship unmet***

CSADET 27 I Closing-Custody dispute

CSADET 28 I Closing-Move Investigation

CSADET 29 I Closing-Child Aged Out

CSADET 30 I Closing-Death Report

CSADET 31 I Closing-Emancipated Minor

CSADET 32 I Closing-Family Whereabouts Unknown/Reasonable Efforts Met

CSADET 33 I Closing-Investigation Complete

CSADET 34 I Closing-No Jurisdiction-Correctional Facility

CSADET 35 I Closing-No Jurisdiction-Federal Installation/Institution

CSADET 36 I Closing-Victim Deceased

CSADET 37 A Closing-Patently Unfounded

CSADET 38 A Closing-Unable to Locate

CSADET 39 A Closing-Open Ongoing Case Management Services

For each investigation found, various pieces of information are read from associated pieces of

work. Each piece of information is transformed from the SACWIS format into values that are



acceptable to NCANDS. The transformations are included in a mapping that is located at the end

of the document.

From the investigation, the following information is read:

Investigation Start Date

Investigation Determination Code

Investigation Completion Date

The program then finds the intake related to the investigation. If multiple intakes are related to an

investigation, only the information from the initial intake is used for NCANDS reporting. From

the intake, the following pieces of information are read:

Intake Report ID

Report Date

Reporter Type

County of Report

The program reads the demographic information about the victim from his or her person record.

If multiple children exist for the investigation in FSFN, each child becomes a different NCANDS

record. The following pieces of information are read:

Person ID

Birth Date

Gender

Race

Ethnicity

Military Family Membership

The program reads information about the allegation(s) in the current investigation for the victim.

The following pieces of information are read:

Maltreatment Code

Finding Code

The Perpetrator

NCANDS requires the record to indicate if the current victim has been the subject of abuse

previously. Using the Person ID, the program searches for previously verified allegations in

other investigations where this person is the victim.



Another NCANDS requirement is that each distinct maltreatment value be reported only once

per record. In the event that multiple SACWIS abuse/neglect codes map to a single NCANDS

Maltreatment type in a given record, that Maltreatment type is reported only once on the

NCANDS record.

NCANDS allows no more than four (4) allegations per record. If more than four (4) allegations

exist after all translation is complete, only the first four (4) are added to the NCANDS record.

The NCANDS Disposition Level corresponds to the finding code of the allegation in SACWIS.

The NCANDS program applies a hierarchy to determine the Disposition Level of the allegation

on the NCANDS record. Only the highest magnitude of finding is reported to NCANDS.

“Substantiated” or “Verified” is the highest level of disposition for NCANDS, and is therefore

never overwritten with another value. See Section 2.2.2 for hierarchical mapping.

The program reads demographic information about each perpetrator. Note that perpetrators are

persons involved in a report of child abuse and neglect that have at least one (1) substantiated or

verified allegation against them. If no persons have substantiated or verified allegations, this

section is left blank in the NCANDS record. NCANDS allows no more than three (3)

perpetrators per record. If more than three (3) perpetrators are found, only the first three (3)

perpetrators are selected. For each perpetrator, the following pieces of information are read:

Person ID

Birth Date

Gender

Race

Ethnicity

Military Membership

In the event that more than four (4) allegations exist and one (1) or more are not to be included in

the NCANDS record, and if a perpetrator is not linked to at least one of the included allegations,

that perpetrator is not included on the NCANDS record. The perpetrator may be replaced with

another perpetrator, if applicable. Furthermore, if the situation arises that insufficient space on

the NCANDS record exists to include a perpetrator that is responsible for an allegation for which

no other perpetrator on that record is also responsible, that allegation is removed from the

NCANDS record.

The program reads information about the relationship between the victim and each perpetrator.



Using the Person ID of each perpetrator, the program searches for previously substantiated or

verified allegations where the person was the perpetrator.

In addition, when determining the maltreatments associated with each alleged perpetrator, only

those maltreatments which are “Verified”, and therefore an associated Caregiver Responsible

identified, will tie the Alleged Perpetrator and Maltreatment together. As a result, there may be

some Alleged Perpetrators for whom there are no associated Maltreatments identified in the

extract. This is due to findings other than “Verified” not having an associated, identified

Caregiver Responsible.

The program reads disability information about the caregiver(s) of the child in the investigation.

A caregiver is anyone in the investigation with a role of either “Adult” or “Both” (meaning both

“Adult” and “Child/Kid”). If any caretaker in the investigation has a disability value that has

been clinically diagnosed or professionally documented, the NCANDS question is marked

“Yes.” If none of the caregivers in the investigation has a disability value that has been clinically

diagnosed or professionally documented, the NCANDS question is marked “No.” The possible

disabilities are:

Alcohol Abuse

Drug Abuse

Mental Retardation

Emotionally Disturbed

Visual or Hearing Impaired

Learning Disability

Physical Disability

Other Medical Condition

The same values are read for the child.

The program reads the investigation worker’s ID based on assignment to the shell of the

investigation at the time of the report run. The program then finds the ID of the worker’s

supervisor.

1.3.3 Transformations

Most data elements required by NCANDS are not stored in FSFN in the same fashion as they

must be reported. As a result, data elements that are stored in a different format or style are

transformed from the FSFN format into the NCANDS format. For a complete mapping of each

element to be transformed, see the mapping table attached to the end of the document.



1.3.4 Encryption Logic **CHANGE**

A requirement of NCANDS is to ensure the confidentiality of all people and reports submitted in

the report. Therefore, the TX_IDTFCN_TYPEassociated with the Person ID within the

Person_Identification table is encrypted.

The following data fields of the submitted file are encrypted:

Intake Report ID

Person ID of the Child

Worker ID of the State Employee

Supervisor ID of the Worker

Person ID of the Perpetrator (3)

AFCARS ID

The following method is used for encrypting the Child Person ID, Worker ID, Supervisor ID,

and each Perpetrator ID:

For FSFN TX_IDTFCN_TYPEs that are less than 11 characters long, left-pad the ID

with zeros to make a 10-digit character, then take characters 6-10, append

characters 1-5, and append 01

For FSFN TX_IDTFCN_TYPEs that are 11 characters long, take characters 6-10,

append characters 1-5, append character 11, and finally append a 9

There should not be any logic for 12 characters since the FSFN database will not accept a

12 digit ID.

**The encryption method identified directly above will be employed for all 3 Federal Reports

which include the following: AFCARS, NYTD and NCANDS**

The following is the method used for encrypting the Intake ID:

Step 1: Left pad with zeros to create a 12-character ID

Step 2: Flip first six (6) characters and last six (6) characters (move last six (6) characters

to front)

1.3.5 Report Construction

Every NCANDS Child File record has the same format. Therefore, the construction logic applies

to every record in the report.



The report is written applying the transformation logic and encryption logic when applicable.

The attached mapping document describes each NCANDS data field, its FSFN source, and the

transformation logic of each field.

1.3.6 The Agency Data File

The NCANDS Agency Data file is a Word file that contains 26 questions. The answers are

written to an online report via the NCANDS web portal. DCF Program Office staff is responsible

for transferring the responses contained in the report to the online form that NCCAN requires for

submission.

1.3.7 Data Encryption/Decryption Utility

To facilitate the generation of the encrypted NCANDS report, a separate encryption/decryption

utility is responsible for the transformation logic in the NCANDS report. The encryption process

is performed as part of the NCANDS Batch which generates the flat file. The encryption process

is the same as that which is performed for AFCARS and NYTD, and is detailed out in Section

1.3.4 above.

1.3.8 Encrypted Element Construction

A relatively small number of fields on the NCANDS report are encrypted. Therefore, the

program ignores most of the data included in the file. All non-encrypted data is read and then

written as-is to the target report. When an encrypted field is found, the program applies the

encryption logic to the field. The modified field is written to the flat file accessed from the FSFN

Report Portal.

The report writes one record to the output report for every record in the report used as input.

The TX_IDTFCN_TYPE associated with the Person ID within the Person_Identification table is

encrypted.

Because a NCANDS record may contain zero, one, two, or three perpetrators, if no Perpetrator

ID is found for an input section, spaces are moved to the output report. The program moves to

the next record in the file and continues without writing errors to the error file. The error file is

generated, capturing any errors encountered when the batch is run to generate the NCANDS

Extract and is stored on the BODI Batch Server.

In addition, there is an NCANDS Exception Report which is located in Business Objects within

the Go Live Validation folder, which is accessible by those with the Reporting Security Group of

“Statewide Power User”. The NCANDS Exception Report contains the following columns:

Intake Number; report Period; Case ID; Case Name (Last, First); Child ID; Child’s Name (Last,

First); Perpetrator 1 ID; Perpetrator 1 Name; Perpetrator 2 ID; Perpetrator 2 Name; Perpetrator 3



ID; Perpetrator 3 Name; NCANDS Element; Message; District; Agency; Unit; and Primary

Investigator.



2 NCANDS Child File Retrieval Logic or Calculation

Field Type Length Source/Mapping/Transformation Column/Table Name NCANDS Federal

Valid Values

Field 1:

Submission

Year

Numeric 4 Four-digit year passed as a parameter. -- --

Field 2:

State /

Territory

Alphanumeric 2 Hard Code to “FL.” --

Field 3:

Report ID

Alphanumeric 12 The Initial Intake Report ID associated with this investigation

record. Investigation ID selected according to the selection

logic in Section 1.2.

SELECT ID_ACCSS_RPT_SEQ from ACCESS_REPORT

join INVESTIGATION on

ACCESS_REPORT.ID_INVS=(Investigation ID) for NC03

and add encryption:

- Step 1: Left pad with zeros to create a 12-character

ID

- Step 2: Flip first six (6) characters and last six (6)

characters (move last six (6) characters to front)

ACCESS_REPORT/

ID_ACCESS_REPORT

--

Field 4:

Child ID

Alphanumeric 12 Children are pulled from the Investigation to ensure that all

children whether victim or not, are included in the report.

SELECT the ID_PRSN from INTAKE_PART JOIN

INVESTIGATION on

INTAKE_PART.ID_INTK=INVESTIGATION.ID_INVS

join PERSON_IDENTIFICATION on

INTAKE_PART.ID_PRSN=PERSON_IDENTIFICATION.I

ID_PRSN/

INTAKE_PART

TX_IDTFCN_TYPE/

PERSON_IDENTIFICATI

ON

--




Valid Values

D_PRSN and

PERSON_IDENTIFICATION.CD_IDTFCN_TYPE=25

Populate NC04 with

PERSON_IDENTIFICATION.TX_IDTFCN_TYPE value

(HSN ID or FSFN ID) AND add encryption for NC04

NOTE: The TX_IDTFCN_TYPE associated with the Person

ID within the Person_Identification table is encrypted.

Field 5:

County of

Report

Numeric 3 This is the FIPS code for the county of the intake.

SELECT CD_COUNTY from ACCESS_REPORT join

CODE_DESC on

ACCESS.CD_COUNTY=CODE_DESC.IDGRPI and

ID_GRP= “REGION” and SELECT

CODE_DESC.TX_DESC_TYP for NC05

CD_COUNTY/

ACCESS_REPORT

FIPS

Blank = not collected

999 = out of state

Field 6:

Report Date

Date 8 The date of Initial Intake report.

Use the INVESTIGATION.ID_INVS to search the

ACCESS_REPORT table for the Initial Intake associated with

the Investigation.

SELECT DT_ACCESS_RCVD from ACCESS_REPORT

join INVESTIGATION on INVESTIGATION.ID_INVS =

ACCESS_REPORT.ID_INVS and

ACCESS_REPORT.CD_INTL_SUB=“1”(Initial)

Because Investigations are pulled into the extract based on the

Completed Date being equal to or greater than the Report

Period Begin Date, for non-fatality records, this Report Date

DT_ACCESS_RCVD/

ACCESS_REPORT

DATE (mmddyyyy)




Valid Values

(NC6) must not be earlier than the first day of the submission

period minus one year. Old fatality records are accepted, non-

fatality records are not. NOTE: Fatality records are defined

as Maltreatment = Death and the associated Finding =

Verified. (NC26; NC28; NC30 and NC31 all capture the

Maltreatment Codes)

Field 7:

Investigation

Start Date

Date 8 The logic for this field searches for the note with the category

of “Child Investigation” and a note type of “Initial” and

selects the Begin Date for the Investigation Start Date.

SELECT DT_BEGIN from CAN_EVENT_TYPE join

INVESTIGATION on

CAN_EVENT_TYPE.ID_INVS=INVESTIGATION.ID_INV

S where CAN_TEXT_EVENT.CD_CTGRY=3(child

Investigation) and

CAN_EVENT_TYPE.CD_CAN_EVENT_TYPE=1(Initial)

OR

SELECT DT_BEGIN from CAN_TEXT_EVENT join

INVESTIGATION on

CAN_TEXT_EVENT.ID_INVS=INVESTIGATION.ID_INV

S where CAN_TEXT_EVENT.CD_CTGRY=3(child

Investigation) and

CAN_TEXT_EVENT.CD_TYPE=1(Initial)

NOTE: We must continue to look at the old table to ensure

DT_BEGIN/

CAN_TEXT_EVENT

DT_BEGIN/

CAN_EVENT_TYPE

DATE (mmddyyyy)

blank = not collected




Valid Values

we capture all applicable data.

Field 8:

Report Source

Numeric 2 Note: The logic for this field selects the Reporter Type from

the initial intake associated to the completed investigation.

SELECT CD_RPTR_DSCR from ACCESS REPORT and

CODE_DECODE.

CD_RPTR_DSCR/

ACCESS REPORT


01 Social services

personnel

02 Medical personnel

03 Mental Health

personnel

04 Legal, law

enforcement, or

criminal justice

personnel

05 Education

personnel

06 Child day care

provider

07 Foster care

provider

08 Alleged victim

09 Parent

10 Other relative

11 Friends/neighbor

12 Alleged perpetrator

13 Anonymous

reporter

88 Other

99 Unknown or




Valid Values

missing

Field 9:

Report

Disposition

Numeric 2 **CHANGE**

The logic for this field selects all allegations for the

investigations and calculates based upon the following logic.

There is a 3 tiered hierarchy which is as follows: First, the

logic will look to see if the value selected in the

Determination drop down of the Investigation = Closing –

False Report; if the Determination is NOT Closing – False

Report, the logic will look to see if check box on the Results

tab of the Investigation labeled “Referred to Law Enforcement

or State Attorney for False Report” is selected; if not selected,

the logic will lastly look to see, if on the Recommended

Disposition tab, the child has a recommended service of

“Referral to State Attorney as Possible False Report”

(DISPOSITION_DETAIL /FL_C_RSA_PFP); in any of the 3

scenarios above, the logic is looking for that criteria and that

there are no allegations that are “Verified”; if so, then set the

report disposition to “Unsubstantiated due to intentionally

false reporting.”

In addition, based on the online change to include the

“Referral to State Attorney for Possible False Report” check

box, this logic must be modified to look at this new check box

for new FSDMM Investigation. However, the logic must

continue to also use the old logic to ensure no missing data.

CD_FIND/

ALLEGATION

01 Substantiated

02 Indicated or reason

to suspect

03 Alternative

response disposition-

victim

04 Alternative

response disposition-

not a victim

05 Unsubstantiated

06 Unsubstantiated

due to intentionally

false reporting

07 Closed-no finding

88 Other

99 Unknown or

missing




Valid Values

If any allegation has a finding of “Verified” set report

disposition level to Substantiated, if there are no “Verified”

maltreatments but maltreatments with a finding of “Some

Indicator” or “Not Substantiated” or “No Indicator” set equal

to “Unsubstantiated.” If there are no records found set

disposition to “Unknown or missing.”

SELECT DISTINCT

CD_CAN,ID_PRSN_VCTM,ID_PRSN_PERP,FL_C_RSA_P

FP,CD_FIND,FL_FATALITY from ALLEGATION

join DISPOSITION_DETAIL on

ALLEGATION.ID_INVS=DISPOSITION_DETAIL.ID_INV

S and

ALLEGATION.ID_PRSN_VCTM=DISPOSITION_DETAIL

.ID_PRSN

where ALLEGATION.ID_INVS=(Investigation ID) order by

ID_PRSN_VCTM,CD_CAN

If ALL FL_C_RSA_PFP=“Y” and no records where

CD_FIND=1 then set NC09=06

If any CD_FIND=1 set NC09=01

If any CD_FIND <> 1 and any CD_FIND=2, or CD_FIND=3,

or CD_FIND =4 set NC09=05 and NC88-NC144=blank

If all CD_FIND is null set NC09=99 and NC88-

NC144=blank

The minimum (most severe finding) value of all Maltreatment

Levels (NC27, NC29, NC31, NC33) in the report should be

equal to the Report Disposition Value (NC9). (i.e. a

Substantiated (01) finding in NC29 cannot then show an

Unsubstantiated (05) Report Disposition NC9)




Valid Values

Field 10:

Report

Disposition

Date

Date 8 This logic for this field uses the date the investigation was

approved by the supervisor for closure.

SELECT DT_INVS_CMPL from INVESTIGATION

DT_INVS_CMPL/

INVESTIGATION

--

Field 11:

Notifications

Numeric 1 This is the notification to other entities. Since there can be

multiple notification the following logic will apply. If any

investigation has both a police and a licensing agency

notification then NC11 will equal 4.

SELECT TX_AGENCY_NM from INVS_NOTIFICATION

where

INVESTIGATION.ID_INVS=INVS_NOTIFICATION.

ID_INVS

If there are any records where TX_AGENCY_NM =“1” and

TX_AGENCY_NM “9” then set NC11=4

If any combination where TX_AGENCY_NM in (1,2) and

TX_AGENCY_NM in (3,4,5,6,7,8,10,11,12,13,14,15) set to

“2”

If any combination where TX_AGENCY_NM =“9” and

TX_AGENCY_NM in (3,4,5,6,7,8,10,11,12,13,14,15) set to

“3”

If any combination where TX_AGENCY_NM in

(3,4,5,6,7,8,15) and TX_AGENCY_NM in (10,11,12,13,14)

set to “8”

CODE_DESC.ID_GRP = “AGNCYNTF”

TX_AGENCY_NM

TX_AGENCY_NM/

INVS_NOTIFICATION


1 None

2 Police/prosecutor

3 Licensing agency

4 Both

8 Other

9 Unknown or missing




Valid Values

Field 12:

Child Age At

Report

Numeric 2 This is a calculated field based of the person’s date of birth

and the date the report was received.

SELECT DT_BRTH from PERSON join INTAKE_PART on

INTAKE_PART.ID_PRSN=PERSON.ID_PRSN

join INVESTIGATION on INTAKE_PART.

ID_INTK=INVESTIGATION.ID_INVS join

ACCESS_REPORT on

ACCESS_REPORT.ID_INVS=INVESTIGATION.ID_INVS

Compute (ACCESS_REPORT.DT_ACCESS_RCVD) –

(PERSON.DT_BRTH) Child’s age in years for NC12

If the child is less than 1 year old, the field’s value is “00”

If the child is unborn, the field’s value is “77”

If unknown or missing, the field’s value is “99”

DT_ACCESS_RCVD/

ACCESS_REPORT

&

DT_BRTH/

PERSON

00 = under one year

enter Age using two

digits (e.g., 09=9yrs)

18 18 or older

77 Unborn

99 Unknown or

missing

Field 13:

Child Date of

Birth

Date 8 Uses the child’s DOB from the Person Management Module.

Date format is MMDDYYYY.

SELECT DT_BRTH from PERSON for NC13

IF DT_BRTH is null set NC13= blank

DT_BRTH/

PERSON

DATE (mmddyyyy)


Field 14:

Child Sex

Numeric 1 Use the Child’s Person ID to select the CD_GNDR in the

PERSON table.

SELECT CD_GNDR from PERSON

If CD_GNDR = “M” (Male), set NC14 to “1”

If CD_GNDR = “F” (Female), set NC14 to “2”

If CD_GNDR= “U” or “null” set NC14 to 9

CD_GNDR/

PERSON


1 Male

2 Female


Field 15: Numeric 1 This selects FL_RACE_AMERICAN from PERSON table for FL_RACE_AMERICAN/ Blank = not collected




Valid Values

Child Race

(American

Indian or

Alaska

Native)

Child’s Person ID.

SELECT FL_RACE_AMERICAN from PERSON

If FL_RACE_AMERICAN =“Y” set NC15=1

If FL_RACE_AMERICAN=“N” set NC15=2

PERSON 1 Yes

2 No

3 Unable to determine

9Unknown or missing

Field 16:

Child Race

(Asian)

Numeric 1 This selects the FL_RACE_ASIAN from PERSON table for


SELECT FL_RACE_ASIAN from PERSON

If FL_RACE_ASIAN=“Y” set NC16=1

If FL_RACE_ASIAN=“N” set NC16=2

Reference table 2.2.7 is for mapping based on Ethnicity when

Race is missing

FL_RACE_ASIAN/

PERSON


1 Yes

2 No



Field 17:

Child Race

(Black or

African

American)

Numeric 1 This selects FL_RACE_BLACK from PERSON table for


SELECT FL_RACE_BLACK from PERSON

If FL_RACE_BLACK=“Y” set NC17=1

If FL_RACE_BLACK=“N” set NC17=2


Race is missing

FL_RACE_BLACK/

PERSON


1 Yes

2 No



Field 18:

Child Race

(Native

Hawaiian or

Other Pacific

Islander)

Numeric 1 This selects FL_RACE_HAWAIIAN from PERSON table for


SELECT FL_RACE_HAWAIIAN from PERSON

If FL_RACE_HAWAIIAN=“Y” set NC18=1

If FL_RACE_HAWAIIAN=“N” set NC18=2

FL_RACE_HAWAIIAN/

PERSON


1 Yes

2 No



Field 19:

Child Race

Numeric 1 This selects the FL_RACE_WHITE from PERSON table for

Child’s Person ID. FL_RACE_WHITE/ Blank = not collected

1 Yes




Valid Values

(White)

SELECT FL_RACE_WHITE from PERSON

If FL_RACE_WHITE =“Y” set NC19=1

If FL_RACE_WHITE =“N” set NC19=2

PERSON 2 No



Field 20:

Child Race

(Unable to

Determine)

Numeric 1 This selects the FL_RACE_UNBL_DTRMN from PERSON

table for Child’s Person ID.

Screen Location: Person Management > Basic tab.

SELECT FL_RACE_UNBL_DTRMN from PERSON IF

FL_RACE_UNBL_DTRMN=“Y” set NC20=1

IF FL_RACE_UNBL_DTRMN=“N” set NC20=2

SELECT FL_RACE_UNKNOWN from PERSON IF

FL_RACE_UNKNOWN=”Y” set NC20=9

SELECT FL_RACE_DCLND from PERSON IF

FL_RACE_DCLND=”Y” set NC20=9

FL_RACE_UNBL_DTRM

N/

PERSON


1 Yes

2 No


Field 21:

Child

Ethnicity

Numeric 1 Selects the Hispanic/Latino for the child from the PERSON

table.

SELECT ID_PRSN from INTAKE_PART join PERSON

where INTAKE_PART.ID_PRSN=PERSON.ID_PRSN

and decode PERSON.CD_HSPNC

If CD_HSPNC=Y set NC21=1

If CD_HSPNC=N set NC21=2

If CD_HSPNC=U set NC21=3

If CD_HSPNC=null set NC21=9

If CD_HSPNC=D set NC21=3

CD_HSPNC/

PERSON

Blank = not

collected/not

applicable

1 Yes, Hispanic or

Latino

2 Not Hispanic or

Latino






Valid Values

Field 22:

County of

Residence

Numeric 3 Child/Victim location at the time of intake. Uses the FIPS

code for the county of the address for the initial intake.

SELECT CODE_DESC.TX_DESC_TYP FROM ADDRESS

join

PERSON on PERSON.ID_PRSN=ADDRESS.

ID_ADRSS_GRP join INTAKE_PART on

PERSON.ID_PRSN=INTAKE_PART.ID_PRSN join

INVESTIGATION on INTAKE_PART.ID_INTK =

INVESTIGATION.ID_INVS join

ACCESS_REPORT on ACCESS_REPORT.ID_INVS =

INVESTIGATION.ID_INVS join

CODE_DESC on

ADDRESS.CD_CNTY=CODE_DESC.ID_GRPI and

CODE_DESC.ID_GRP=“REGION” and

(ADDRESS.CD_GRP=1

If no record found look for ADDRESS.CD_GRP=3) where

PERSON.ID_PRSN=(Child)ID_PRSN

If no record found set NC22=999

Need to update the logic above to ensure that the extract is

pulling the county from the address in effect on or prior to the

date of initial intake, or the county from the first address

known after the initial intake date. This should be derived

from the child’s Person Management record; if no address is

found on the child’s Person Management record, then pull the

County associated with the Unit of the Primary Investigator

identified on the Intakes tab of the Investigation page.

FIPS


998 = out of state

999=Unknown/Missin

g




Valid Values

Field 23:

Living

Arrangement

Numeric 2 The logic for this field uses the Investigation ID to search for

the initial intake then decodes the child’s living arrangement.

SELECT CD_CHILD_LIVING_ARRANGEMENT from

INVESTIGATION

CODE_DESC_LRG.ID_GRP = “CHLDLVNG”

NOTE: An online change is required to add this drop down to

the FSDMM Investigation page. As a result, the logic must

continue to look at the old, and new logic must be included to

look at the new FSDMM Investigations.

CD_CHILD_LIVING_AR

RANGEMENT/

INVESTIGATION

Blank = not collected.

01 Married two parent

household, with two

biological/adoptive

parents

02 Married two parent

household, with one

biological/adoptive

and one step parent

03 Unmarried two

parent household with

two

biological/adoptive

parents

04 Unmarried two

parent household with

one

biological/adoptive

parent and one

cohabitating partner

05 Two parent

household, marital

status unknown

06 Single parent

household, mother

only

07 Single parent

household, father only




Valid Values

08 Single parent

household mother

with other adult

(grandmother, sister,

unrelated adult)

09 Single parent

household father with

other adult

(grandmother, sister,

unrelated adult, etc.).

10 Non-parent relative

caregiver household

(includes relative

foster care)

11 Non-relative

caregiver household

(includes non-relative

foster care)

12 Group home or

residential treatment

setting

88 Other setting

(hospital, secure

facilities, etc.)

99 Unknown

Field 24:

Military

Numeric 1 Use the Child’s Person ID to search the PERSON table for the

Military Dependent flag; if the flag is not checked on the

FL_PRN_ACV_DT_MLT Blank = not

collected/not




Valid Values

Family

Member

child’s Person Management record THEN check the Person

Management record of the Mother and/ or Father identified on

the Additional tab to see if the Mother or Father’s “Active

Duty” flag is checked. If checked, set NC24=1.

SELECT FL_PRN_ACV_DT_MLTY from PERSON

If FL_PRN_ACV_DT_MLTY=“N” set NC24=2

If FL_PRN_ACV_DT_MLTY=“Y” set NC24=1

If FL_PRN_ACV_DT_MLTY=null set NC24=2

NOTE: The label on the screen in FSFN reflects “active duty”

while the flag in the database table is showing as “dependent”.

This is known and is acceptable because the users are

accurately selecting if they are an active duty member and the

logic here is accurately pulling the incorrectly reflected flag

label.

Y/PERSON applicable

1 Yes

2 No


Field 25:

Prior Victim

Numeric 1 The logic for this field selects all allegations where the intake

is less than the current reports received date and checks if

there are any allegations associated with the investigation that

are “Verified.” If so, the field is set equal to 1, otherwise if no

records found or there are no “Verified” maltreatments it is set

to 2.

SELECT CD_FIND from ALLEGATION join

INVESTIGATION on

ALLEGATION.ID_INVS=INVESTIGATION.ID_INVS join

ACCESS_REPORT on INVESTIGATION.ID_INVS

=ACCESS_REPORT.ID_INVS join INTAKE_PART on

INVESTIGATION.ID_INVS=INTAKE_PART.ID-INTK

where ALLEGATION.ID_PRSN_VCTM=

INTAKE_PART.ID_PRSN where ACCESS_REPORT.

DT_ACCESS_RCVD < NC06 and

CD_FINDING/

ALLEGATION


1 Yes

2 No





Valid Values

ALLEGATION.CD_FIND=1

then set NC25=1 else set NC25=2

Field 26:

Maltreatment-

1 Type

Numeric 1 The logic for this field selects all the distinct maltreatment

types and populatesNC26-NC34.

The hierarchy should be based upon the finding, meaning the

most severe finding for a particular maltreatment gets

populated first, example “Verified” maltreatments get

populated first then “Some Indicated” or “Not Substantiated”;

then “No Indicator”.

If there are only two allegations and findings then set the rest

of the fields blank.

Note: The same maltreatment types cannot be in any one of

NC26, NC28, NC30, or NC32. Duplicate maltreatment types

are not allowed.

SELECT DISTINCT CD_CAN,CD_FIND,FL_C_RSA_PFP

from ALLEGATION


ALLEGATION.ID_INVS=INVESTIGATION.ID_INVS

join INTAKE_PART on

INVESTIGATION.ID_INVS=INTAKE_PART.ID_INTK

join ACCESS_REPORT on

INVESTIGATION.ID_INVS=ACCESS_REPORT.ID_INVS

join DISPOSITION_DETAIL on

ALLEGATION.ID_INVS=DISPOSITION_DETAIL.ID_INV

S and

ALLEGATION.ID_PRSN_VCTM=DISPOSITION_DETAIL

.ID_PRSN

where ID_PRSN_VCTM=(Childs) ID_PRSN order by

CD_FIND

CD_CAN/

ALLEGATION

Blank = not

collected/not

applicable

1 Physical Abuse

2 Neglect or

deprivation of

necessities

3 Medical neglect

4 Sexual abuse

5 Psychological or

emotional

maltreatment

6 No alleged

maltreatment

8 Other





Valid Values

If all FL_C_RSA_PFP=Y and no records where CD_FIND

=(1,2,4) then populate NC26, NC28,NC30,NC32 with up to

the first four maltreatment types, and set the same number

disposition levels for the number of maltreatments

(NC27,NC29,NC31,NC33)=“6”

else populate (NC26,NC27) with the first maltreatment and

finding (NC28,29) with the second maltreatment and finding

(NC30,NC31) with the third maltreatment and finding

(NC32,NC33) with the fourth maltreatment finding.

If no record found set NC26=06 AND NC27=08

*See Mappings for Maltreatment (Section 2.2.4) and

Disposition Mapping (Section 2.2.2)

Screen location: Child Intake > Allegations tab

Field 27:

Maltreatment-

1 Disposition

Level

Numeric 2 SEE Field 26 CD_FIND/

ALLEGATION

Blank = not

collected/not

applicable

01 Substantiated

02 Indicated or reason

to suspect

03 Alternative

response disposition -

victim

04 Alternative

response disposition -

not a victim

05 Unsubstantiated

06 Unsubstantiated




Valid Values

due to intentionally

false reporting

07 Closed - no finding

08 No alleged

maltreatment

88 Other

99 Unknown or

missing

Field 28:

Maltreatment-

2 Type

Numeric 1 SEE Field 26 CD_CAN/

ALLEGATION

SAME AS Field 26,

Maltreatment 1 Type

Field 29:

Maltreatment-

2 Disposition

Level


ALLEGATION

SAME AS Field 27,

Maltreatment 1

Disposition Level

Field 30:

Maltreatment-

3 Type


ALLEGATION

SAME AS Field 26,

Maltreatment 1 Type

Field 31:

Maltreatment-

3 Disposition

Level


ALLEGATION

SAME AS Field 27,

Maltreatment 1

Disposition Level

Field 32:

Maltreatment-

4 Type


ALLEGATION

SAME AS Field 26,

Maltreatment 1 Type

Field 33: Numeric 2 SEE Field 27 CD_FIND/ SAME AS Field 27,




Valid Values

Maltreatment-

4 Disposition

Level

ALLEGATION Maltreatment 1

Disposition Level

Field 34:

Maltreatment

Death

Numeric 1 The logic for this field checks all allegations for a child to see

if the result of any maltreatment is a Fatality. If one of the

allegations for the child is found to be a fatality then set

NC09=1 and NC34=1.

SELECT DISTINCT CD_CAN,CD_FIND from

ALLEGATION



join INTAKE_PART on




where ALLEGATION.ID_INVS=(Investigation ID) and

ID_PRSN_VCTM=(Child ID)ID_PRSN order by CD_CAN

If any CD_CAN=6 and CD_FIND=“1” set NC34=1

Else SET NC34=2

FL_FATALITY/

ALLEGATION

Blank = not

collected/not

applicable

1 Yes

2 No


Field 35:

Alcohol

Abuse-Child

Numeric 1/101 The logic for this field selects the child’s Person ID

(ID_PRSN) from the INTAKE_PART table matches it to the

MENTAL_HEALTH_PROFILE table based on (ID_PRSN)

and selects the value in FL_ALCOHOL

If FL_ALCOHOL = “Y” set NC35 = 1

If FL_ALCOHOL= “N” set NC35=2

If no record found set NC35= 9

FL_ALCOHOL/

MENTAL_HEALTH_PRO

FILE/

Blank = not

collected/not

applicable

1 Yes

2 No


Field 36:

Drug Abuse-

Child

Numeric 1/102 The logic for this field selects the Child’s Person ID

(ID_PRSN) from the INTAKE_PART table matches it to the

MENTAL_HEALTH_PROFILE table based on (ID_PRSN)

FL_DRUGS/

MENTAL_HEALTH_PRO

Blank = not

collected/not




Valid Values

and selects the value in FL_DRUGS

If FL_MARIJUANA or FL_DRUGS = “Y” set NC36 = 1

If FL_MARIJUANA and FL_DRUGS = “N” set NC36=2

If no record found set NC36= 9

FILE/

applicable

1 Yes

2 No


Field 37:

Mental

Retardation-

Child

Numeric 1/103 If MENT_HLTH_COND.CD_MED_COND_TYPE equals

any of the following:

2559 - Borderline Intellectual Functioning

2561 - Down Syndrome

2562- Hydrocephalus

2563 - Intellectual Disability (Mental

Retardation, all degrees)

2565 - Microcephaly

And the Condition Type Begin Date is on or before the Report

Completion Date and the Condition Type End Date is null or

after the Report Completion Date, set NC37-1

If MENT_HLTH_COND.CD_MED_COND_TYPE exists,

but the date does not fall within the range specified OR the

value is not one of the values specified above, then set

NC37=2

If MENT_HLTH_COND.CD_MED_COND_TYPE unknown

or missing set NC37=9

Screen Location: Medical/ Mental Health >

CD_MED_COND_TYPE/

MENT_HLTH_COND

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

Disability Information tab

Field 38:

Emotionally

Disturbed-

Child

Numeric 1/104 If MENT_HLTH_COND.CD_MED_COND_TYPE contains

any disabilities in the Behavioral/Mental Health category and

the Condition Type Begin Date is on or before the Report


after the Report Completion Date, set NC38-1




NC38=2



CD_MED_COND_TYPE/

MENT_HLTH_COND

Blank = not

collected/not

applicable

1 Yes

2 No


Field 39:

Visually or

Hearing

Impaired-

Child

Numeric 1/105 If MENT_HLTH_COND.CD_MED_COND_TYPE equals

and of the following:

o 2572 - Blindness and Low Vision (ICD-9: 369)

o 2576 - Cataracts

o 2583 - Congenital Anomaly of the Eye

o 2589 - Deaf

o 2591 - Diabetic Retinopathy

o 2598 - Glaucoma

o 2599 - Hearing Loss (ICD-9: 389)

o 2624 - Retinal Detachment and Defects (ICD-9: 361)

CD_MED_COND_TYPE/

MENT_HLTH_COND

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

o 2630 – Visual Disturbances (ICD0=-9: 368)

and the Condition Type Begin Date is on or before the Report


after the Report Completion Date, then set NC39=1




NC39=2



o Screen Location: Medical/ Mental Health >

Disability Information tab

Field 40:

Learning

Disability-

Child


2564 – Learning Disability and the Condition Type Begin

Date is on or before the Report Completion Date and the

Condition Type End Date is null or after the Report

Completion Date, then set NC40=1




NC40=2



Screen Location: Medical/ Mental Health > Disability

CD_MED_COND_TYPE/

MENT_HLTH_COND

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

Information tab

Field 41:

Physically

Disabled-

Child



-2570 - Arthritis

-2574 - Brittle Bones/Osteogenesis Imperfectus

-2577 - Cerebral Palsy

-2579 - Chronic Motor Tic Disorder

-2581 - Club Foot

-2592 - Diplegia

-2616 - Multiple Sclerosis

-2617 - Muscular Dystrophy

-2618 - Myasthenia Gravis

-2622 - Paralysis - Paraplegic, Quadriplegic, Diplegic

-2623 - Poliomyelitis

-2625 - Rheumatoid Arthritis (juvenile)

-2629 - Spina Bifida




CD_MED_COND_TYPE/

MENT_HLTH_COND

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values




NC41=2




Information tab

Field 42:

Behavior

Problem-

Child

Numeric 1/108 The logic for this field selects the Child’s Person ID

(ID_PRSN) from the INTAKE_PART table, matches it to the

PERSON table based on (ID_PRSN), and selects the value in

Person Management.

If CD_HSRS_CLIENT_CHAR1 or

If CD_HSRS_CLIENT_CHAR2 or

If CD_HSRS_CLIENT_CHAR3 = “4” then set NC 42=1

ELSE set NC42=2

CD_HSRS_CLIENT_CHA

R1/PERSON or

CD_HSRS_CLIENT_CHA

R2/PERSON or

CD_HSRS_CLIENT_CHA

R3/PERSON

Blank = not

collected/not

applicable

1 Yes

2 No


Field 43:

Other Medical

Condition-

Child



-2557 - Asperger’s Syndrome

-2558 - Autistic Disorder

-2560 - Childhood Disintegrative Disorder

-2566 - Pervasive Developmental Disorders Not Otherwise

CD_MED_COND_TYPE/

MENT_HLTH_COND

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

Specified

-2567 - Rett Syndrome

-2568 - Acquired Immunodeficiency Syndrome (AIDS)

-2569 - Aplastic Anemia

-2571 - Asthma

-2573 - Blood disorder that required hospitalization once a

month

-2575 - Cancers

-2578 - Chronic Granulomatous Disease

-2580 - Cleft Palate

-2582 - Coagulation Defects

-2584 - Congenital Cystic Lung

-2585 - Congenital Heart Anomaly

-2586 - Crohn's Disease

-2587 - Cushing’s Syndrome

-2588 - Cystic Fibrosis

-2590 - Diabetes

-2593 - Disorders Involving The Immune Mechanism (code

279)

-2594 - Encephalopathy




Valid Values

-2595 - Epilepsy

-2596 - Fetal alcohol syndrome

-2597 - Fetal drug addiction

-2600 - Heart disease

-2601 - Heart murmur, vigorous activity curtailed

-2602 - Hemophilia

-2603 - Human Immunodeficiency HIV Disease (HIV)

-2604 - Human T-Cell Lymphotropic Virus-III

-2605 - Hypertension

-2606 - Immunodeficiency

-2607 - Kidney disease

-2608 – Klienefelter’s syndrome

-2609 - Late Effects Of Tuberculosis (ICD-9: 137)

-2610 - Leukemia

-2611 - Liver disease

-2612 - Lupus

-2613 - Malignant Neoplasms (Malignant tumors)

-2614 - Misplaced facial feature

-2619 - Organic Brain Syndrome




Valid Values

-2620 - Other Human T-Cell Lymphotropic Virus-III

-2621 - Pancreatic Disease

-2626 - Sarcomas

-2627 - Seizure Disorder

-2628 - Sickle cell anemia







NC43=2




Information tab

NOTE – Ensure that Learning Disability is not mapped to this

Element because it was previously included in this list and it

should not be. It should only map to Element 40.

Field 44:

Alcohol

Abuse

Caretaker(s)

Numeric 1/110 The logic for this field selects the Medical Mental Health

record for the child based upon his or her Person ID and the

Case ID attached to the investigation and select the decodes

CD_NCAND_ALCOHOL.

CD_NCAND_ALCOHOL/

MENTAL_HEALTH_PRO

FILE/

Blank = not

collected/not

applicable

1 Yes




Valid Values

SELECT CD_NCAND_ALCOHOL from

MENTAL_HEALTH_PROFILE


INVESTIGATION.ID_CASE=MENTAL_HEALTH_PROFI

LE.ID_CASE

join INTAKE_PART on

INTAKE_PART.ID_PRSN=MENTAL_HEALTH_PROFILE

.ID_PRSN

If CD_NCAND_ALCOHOL= 1 set NC44= 1

If CD_NCAND_ALCOHOL=2 set NC44=2

If CD_NCAND_ALCOHOL= 9 set NC44= 9

If CD_NCAND_ALCOHOL= null set NC44= 9

If no record found set NC44 = 9

NOTE: Ensure this logic is pulling from the “Caregiver(s)

Information at time of Intake” group box on the Disability

Information tab of the child’s Medical Mental Health page. If

not, the logic must be updated as such. In addition, an online

change is needed to make the font color of the “Alcohol

Abuse” drop down label red instead of black.

2 No


Field 45:

Drug Abuse-

Caretaker(s)




CD_NCAND_DRUG.

SELECT CD_NCAND_DRUG from




LE.ID_CASE

CD_NCAND_DRUG/ME

NTAL_HEALTH_PROFIL

E

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

join INTAKE_PART on


.ID_PRSN

If CD_NCAND_DRUG= 1 set NC45= 1

If CD_NCAND_DRUG=2 set NC45=2

If CD_NCAND_DRUG= 9 set NC45= 9

If CD_NCAND_DRUG= null set NC45= 9






change is needed to make the font color of the “Drug Abuse”

drop down label red instead of black.

Field 46:

Mental

Retardation-

Caretaker(s)




CD_NCAND_MENTAL_RETARDATION.

SELECT CD_NCAND_MENTAL_RETARDATION from




LE.ID_CASE

join INTAKE_PART on


.ID_PRSN

If CD_NCAND_MENTAL_RETARDATION = 1 set NC46=

1

If CD_NCAND_MENTAL_RETARDATION =2 set NC46=2

If CD_NCAND_MENTAL_RETARDATION = 9 set NC46=

CD_NCAND_MENTAL_

RETARDATION/MENTA

L_HEALTH_PROFILE

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

9

If CD_NCAND_MENTAL_RETARDATION = null set

NC46= 9






change is needed to make the font color of the “Mental

Retardation” drop down label red instead of black.

Field 47:

Emotionally

Disturbed-

Caretaker(s)

Numeric 1/113 The logic for this field select the Medical Mental Health

record for the child based upon his or her person ID and the


CD_NCAND_EMTNLY_DSTRB.

SELECT CD_NCAND_EMTNLY_DSTRB from




LE.ID_CASE

join INTAKE_PART on


.ID_PRSN

If CD_NCAND_EMTNLY_DSTRB = 1 set NC47= 1

If CD CD_NCAND_EMTNLY_DSTRB =2 set NC47=2

If CD_NCAND_EMTNLY_DSTRB = 9 set NC47= 9

If CD_NCAND_EMTNLY_DSTRB = null set NC47= 9


CD_NCAND_EMTNLY_

DSTRB/MENTAL_HEAL

TH_PROFILE/

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values





change is needed to make the font color of the “Emotionally

Disturbed” drop down label red instead of black.

Field 48:

Visually or

Hearing

Impaired-

Caretaker(s)




CD_NCAND_IMPRD.

SELECT CD_NCAND_IMPRD from




LE.ID_CASE

join INTAKE_PART on


.ID_PRSN

If CD_NCAND_IMPRD = 1 set NC48= 1

If CD_NCAND_IMPRD =2 set NC48=2

If CD_NCAND_IMPRD = 9 set NC48= 9

If CD_NCAND_IMPRD = null set NC48=9






CD_NCAND_IMPRD/

MENTAL_HEALTH_PRO

FILE/

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

change is needed to make the font color of the “Visually or

Hearing Impaired” drop down label red instead of black.

Field 49:

Learning

Disability-

Caretaker(s)




CD_NCAND_LD.

SELECT CD_NCAND_LD from




LE.ID_CASE

join INTAKE_PART on


.ID_PRSN

If CD_NCAND_LD = 1 set NC49= 1

If CD_NCAND_LD =2 set NC49=2

If CD_NCAND_LD = 9 set NC49= 9

If CD_NCAND_LD = null set NC49=9






change is needed to make the font color of the “Learning

Disability” drop down label red instead of black.

CD_NCAND_LD/

MENTAL_HEALTH_PRO

FILE

Blank = not

collected/not

applicable

1 Yes

2 No


Field 50: Numeric 1/116 The logic for this field selects the Medical Mental Health CD_NCAND_PHYS_DSB Blank = not




Valid Values

Physically

Disabled-

Caretaker(s)

record for the child based upon their Person ID and the Case

ID attached to the Investigation and select the decodes

CD_NCAND_PHYS_DSBLD.

SELECT CD_NCAND_PHYS_DSBLD from




LE.ID_CASE

join INTAKE_PART on


.ID_PRSN

If CD_NCAND_PHYS_DSBLD = 1 set NC50= 1

If CD_NCAND_PHYS_DSBLD =2 set NC50=2

If CD_NCAND_PHYS_DSBLD = 9 set NC50= 9

If CD_NCAND_PHYS_DSBLD = null set NC50= 9






change is needed to make the font color of the “Physically

Disabled” drop down label red instead of black.

LD/

MENTAL_HEALTH_PRO

FILE

collected/not

applicable

1 Yes

2 No


Field 51:

Other Medical

Condition-

Caretaker(s)


record for the child based upon their Person ID and the Case

ID attached to the Investigation and select the decodes

CD_NCAND_OTHR

SELECT CD_NCAND_OTHR from

CD_NCAND_OTHR/

MENTAL_HEALTH_PRO

FILE

Blank = not

collected/not

applicable

1 Yes

2 No




Valid Values




LE.ID_CASE

join INTAKE_PART on


.ID_PRSN

If CD_NCAND_OTHR = 1 set NC51= 1

If CD_NCAND_OTHR =2 set NC51=2

If CD_NCAND_OTHR = 9 set NC51= 9

If CD_NCAND_OTHR = null set NC51= 9






change is needed to make the font color of the “Other Medical

Condition” drop down label red instead of black.


Field 52:

Domestic

Violence

Numeric 1/118 The logic for this field selects the investigation associated

with the intake and looks to see if there is an allegation of

“Family Violence Threatens Child”; Intimate Partner

Violence Threatens Child; or Household Family Violence

Threatens Child that is “substantiated.” If not the logic looks

to see if “Domestic Violence Among Adults in Household” is

selected as any of the family characteristic in the

Investigation.

SELECT CD_CAN from ALLEGATIONS, if

CD_CAN=“10” and CD_FIND=“1” set NC52=1

CD_CAN &

CD_FIND/ALLEGATION

Or

CD_FMLY_CHAR,

CD_FMLY_CHAR1,

CD_FMLY_CHAR2/

INVESTIGATION

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

ELSE

SELECT CD_FMLY_CHAR, CD_FMLY_CHAR1,

CD_FMLY_CHAR2 from INVESTIGATION



where INVESTIGATION.ID_INVS

If any CD_FMLY_CHAR, CD_FMLY_CHAR1,

CD_FMLY_CHAR2 in (4) or

INVS_BASIC_TAB_QSTN.ID_QSTN = 493 set NC52=1

else NC52=2

NOTE: Ensure this logic is correctly looking at both the old

and new FSDMM Investigations and also ensure that it is

pulling based on the check boxes which replaced the three

drop downs.

Or

INVS_BASIC_TAB_QST

N.ID_QSTN

Field 53:

Inadequate

Housing


with the intake and looks to see if “Homeless” or “Inadequate

housing” or “problems maintaining housing” is selected as

any of the family characteristic in the Investigation.






If any CD_FMLY_CHAR, CD_FMLY_CHAR1,

CD_FMLY_CHAR2 in (14,12) or

INVS_BASIC_TAB_QSTN.ID_QSTN = 501 or 503 set

NC53=1 ELSE set NC53=9 (12 = Inadequate housing or

problems maintaining housing; 14 = Homeless)

NOTE: Ensure this logic is correctly looking at both the old

CD_FMLY_CHAR,

CD_FMLY_CHAR1,

CD_FMLY_CHAR2/

INVESTIGATION

Or

INVS_BASIC_TAB_QST

N.ID_QSTN

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

and new FSDMM Investigations and also ensure that it is

pulling based on the check boxes which replaced the three

drop downs.

Field 54:

Financial

Problem


with the intake and looks to see if Insufficient Financial

Resources, Other financial stress, Employed poverty level, is

selected as any of the family characteristic in the

Investigation.






IF any CD_FMLY_CHAR, CD_FMLY_CHAR1,

CD_FMLY_CHAR2 in (13, 15, 22, 23, 24, 28) or

INVS_BASIC_TAB_QSTN.ID_QSTN = 502; 504; 511; 512;

513 or 517 set NC54=1

ELSE set NC54=9 (13 = Poor/Violent neighborhood

conditions; 15 = Single parent household; 22 =

Unemployment; 23 = Employed Poverty Level; 24 = Other

Financial Stress; 28 = Insufficient Financial Resources)

CD_FMLY_CHAR,

CD_FMLY_CHAR1,

CD_FMLY_CHAR2/

INVESTIGATION

Or

INVS_BASIC_TAB_QST

N.ID_QSTN

Blank = not

collected/not

applicable

1 Yes

2 No


Field 55:

Public

Assistance

Numeric 1/121 SELECT CD_FMLY_CHAR, CD_FMLY_CHAR1,





IF any CD_FMLY_CHAR, CD_FMLY_CHAR1,

CD_FMLY_CHAR2 in (29) or

INVS_BASIC_TAB_QSTN.ID_QSTN = 518 set NC55=1

CD_FMLY_CHAR,

CD_FMLY_CHAR1,

CD_FMLY_CHAR2/

INVESTIGATION

Or

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

ELSE set NC55=9 (29 = Receiving Public Assistance) INVS_BASIC_TAB_QST

N.ID_QSTN

Field 56:

Post

Investigation

Services

Numeric 1/122 The logic for this field looks to see if any of the Elements

between NC58-NC85 =1 if they do set NC56=1 Else

Set NC56=2.

If any Service Type field (NC58-85) is set to 1 (Yes) the Post

Services field (NC56) must be set to 1 (Yes) and the date must

be supplied in NC57 (Service Date).

The Service Begin Date must be less than the date of

investigation completion plus 90 days, and the end date of the

service greater than the date the investigation was completed,

or is null:

DT_BGN < DT_INVS_CMPL + 90 days, and the DT_END >

DT_INVS_CMPL or is null

Blank = not

collected/not

applicable

1 Yes

2 No


Field 57:

Service Date

Date 8/123-

130

The logic for this element looks at all services that were

provided elements# 58 – 85 and populates the earliest one’s

begin date.

If any Service Type field (NC58-85) is set to 1 (Yes) the Post

Services field (NC56) must be set to 1 (Yes) and the date must

be populated in NC57 (Service Date). If there are multiple

Service Types between Elements NC58-NC85 that meet the

criteria which set NC56 = 1, then pull the minimum Service

Date.

The Service Begin Date must be less than the date of

investigation completion plus 90 days, and the end date of the

service greater than the date the investigation was completed,

DT_BGN/

EPISODE

DATE (mmddyyyy)





Valid Values

or is null:

DT_BGN < DT_INVS_CMPL + 90 days, and the DT_END >


Field 58:

Family

Support

Services

Numeric 1/131 The logic for this element indicates a post-investigation

service associated with a statewide reporting category equal to

Family Support Services (CD_SW_RPT_GRP=1013) and has

a Service Begin Date that is less than the date of investigation

completion plus 90 days, and an end date of the service

greater than the date the investigation was completed, or is

null:

Select DT_BGN and DT_END from episode where DT_BGN

is < DT_INVS_CMPL + 90 days, and the DT_END >


CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Blank = not

collected/not

applicable

1 Yes

2 No


Field 59:

Family

Preservation

Services

Numeric 1/132 The logic for this element checks to see if any service is

associated with a statewide reporting category equal to Family

Preservation Services (CD_SW_RPT_GRP=1014) and a

Service Begin Date that is less than the date of investigation

completion plus 90 days, and an end date of the service

greater than the date the investigation was completed, or is

null:

.

Select DT_BGN and DT_END from episode where DT_BGN

is < (DT_INVS_CMPL + 90 days) and the DT_END is

greater than the DT_INVS_CMPL or is null and

CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

DT_ACCESS_RCVD/

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

CD_SW_RPT_GRP=1014 ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Field 60:

Foster Care

Services

Numeric 1/133 The logic for this element checks to see if there is a removal

episode which has a removal date which is before the

investigation completion date plus 90 days and the discharge

date for that removal is greater than investigations completion

date or is null.

Select DT_RMVL from episode where DT_RMVL is <

(DT_INVS_CMPL + 90 days) and the discharge date for that

removal episode is >the DT_INVS_CMPL or is null. If record

found, set this element to 1 else set this element to 2

If a removal date is provided (NC61), the Foster Care Services

field (NC60) must be coded as 1 (Yes)

DT_RMVL/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

Blank = not

collected/not

applicable

1 Yes

2 No


Field 61:

Removal Date

Date 8/134-

141

If element #60 is = 1 (Yes) then use the applicable record to

populate Date of Removal

The Removal Date (NC61) cannot be greater than the Report

Disposition Date (NC10) plus 90 days. It must be less than the

Report Disposition Date plus 90 days.

DT_RMVL/

EPISODE

DATE (mmddyyyy)


Field 62:

Juvenile Court

Petition

Numeric 1/142 The logic for this element checks to see if any legal action

with a type of “Shelter Petition” and has a completion date

less than the investigation completion date + 90 days.

Select DT_COMPLETED from LEGAL_ACTION WHERE

DT_COMPLETED/

LEGAL_ACTION

DT_INVS_CMPL/

Blank = not

collected/not

applicable

1 Yes

2 No




Valid Values

CD_INITIATE=842 or 844 or 845 AND DT_COMPLETED

< DT_INVS_CMPL + 90_days (842 = Shelter Petition; 844 =

Shelter Hearing – Initial Removal; 845 = Shelter Hearing –

Subsequent Removal)

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT


Field 63:

Petition Date

Date 8/143-

150

The logic for this element gets the completion date of a legal

action with a type of “Shelter Petition” if the completion date

is less than the investigation completion date + 90 days.

DT_COMPLETED/

LEGAL_ACTION

DATE (mmddyyyy)


Field 64:

Court-

Appointed

Representativ

e

Numeric 1/151 The logic for this element checks to see if any legal action

with a type of “Guardian ad Litem Appointed” and has a

completion date that is less than the investigation completion

date + 90 days and no other legal record exists with a type of

“Guardian ad Litem Discharged” or record exist with a type of

“Guardian ad Litem Discharged” and the date completed is

greater than the investigations completed date.

Select DT_COMPLETED from LEGAL_ACTION WHERE

CD_INITIATE = 1200 AND DT_COMPLETED <

DT_INVS_CMPL + 90 DAYS AND either no other record

exists with a CD_INITIATE = 1201 or record exists and the

DT_COMPLETED for that record is > DT_INVS_CMPL. If

record found, set this element to 1 else set this element to 2

DT_COMPLETED/

LEGAL_ACTION

CD_INITIATE/

LEGAL_ACTION

Blank = not

collected/not

applicable

1 Yes

2 No


Field 65:

Adoption

Services

Numeric 1/152 The logic for this element checks to see if any service

associated with a statewide reporting category equal to

Adoption Services (CD_SW_RPT_GRP=1016) and has a

begin date less than the investigation completion date plus 90

days and the services end date is greater than investigations

completion date or is null.

SELECT DT_BGN, DT_END from episode where DT_BGN

CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

< (DT_INVS_CMPL + 90) days and the DT_END is greater

the DT_INVS_CMPL or is null and

CD_SW_RPT_GRP=1016. If record found, set this element to

1 else set this element to 2

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Field 66:

Case

Management

Services


associated with a statewide reporting category equal to Case

Management Services (CD_SW_RPT_GRP=1017) and has a









CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Blank = not

collected/not

applicable

1 Yes

2 No


Field 67:

Counseling

Services



Counseling Services (CD_SW_RPT_GRP=1018) and has a




CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

Blank = not

collected/not

applicable

1 Yes

2 No




Valid Values






INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE


Field 68:

Day Care

Services-

Child



Daycare Services-Child (CD_SW_RPT_GRP=1019) and has

a begin date less than the investigation completion date plus

90 days and the services end date is greater than investigations







CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Blank = not

collected/not

applicable

1 Yes

2 No


Field 69:

Educational

and Training

Services



Educational and Training Services

(CD_SW_RPT_GRP=1020) and has a begin date less than

the investigation completion date plus 90 days and the

services end date is greater than investigations completion

date or is null.

CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

Blank = not

collected/not

applicable

1 Yes

2 No




Valid Values






INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE


Field 70:

Employment

Services



Employment Services (CD_SW_RPT_GRP=1021) and has a









CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Blank = not

collected/not

applicable

1 Yes

2 No


Field 71:

Family

Planning

Services


associated with a statewide reporting category equal to Family

Planning Services (CD_SW_RPT_GRP=1022) and has a




CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

Blank = not

collected/not

applicable

1 Yes

2 No




Valid Values






INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE


Field 72:

Health-

Related and

Home Health

Services



Health-Related and Home Health Services




date or is null.






CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Blank = not

collected/not

applicable

1 Yes

2 No


Field 73:

Home-Based

Services


associated with a statewide reporting category equal to Home-

Based Services (CD_SW_RPT_GRP=1024 and has a begin

date less than the investigation completion date plus 90 days

and the services end date is greater than investigations


CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

Blank = not

collected/not

applicable

1 Yes

2 No




Valid Values






INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE


Field 74:

Housing

Services



Housing Services (CD_SW_RPT_GRP=1025) and has a









CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Blank = not

collected/not

applicable

1 Yes

2 No


Field 75:

Independent

and

Transitional

Living

Services



Independent and Transitional Living Services

(CD_SW_RPT_GRP=1026) and has a begin less than the

investigation completion date plus 90 days and the services

end date is greater than investigations completion date or is

null.

CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

Blank = not

collected/not

applicable

1 Yes

2 No




Valid Values

.






INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE


Field 76:

Information

and Referral

Services



Information and Referral Services




date or is null.






CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Blank = not

collected/not

applicable

1 Yes

2 No


Field 77:

Legal

Services


associated with a statewide reporting category equal Legal

Services (CD_SW_RPT_GRP=1028) and has a begin date

less than the investigation completion date plus 90 days and

the services end date is greater than investigations completion

date or is null.

CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

Blank = not

collected/not

applicable

1 Yes

2 No




Valid Values






INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE


Field 78:

Mental Health

Services


associated with a statewide reporting category equal to Mental

Health Services (CD_SW_RPT_GRP=1029) and has a begin

date less than the investigation completion date plus 90 days

and the services end date is greater than investigations







CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Blank = not

collected/not

applicable

1 Yes

2 No


Field 79:

Pregnancy

and Parenting

Services for

Young

Parents



Pregnancy/Parenting Services for Young Parents




date or is null.

CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

Blank = not

collected/not

applicable

1 Yes

2 No




Valid Values

.






INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE


Field 80:

Respite Care

Services



Respite Care Services (CD_SW_RPT_GRP=1031) and has a









CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Blank = not

collected/not

applicable

1 Yes

2 No


Field 81:

Special

Services-

Disabled



Special Services-Disabled (CD_SW_RPT_GRP=1032) and

has a begin date less than the investigation completion date

plus 90 days and the services end date is greater than

investigations completion date or is null.

CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

Blank = not

collected/not

applicable

1 Yes

2 No




Valid Values




CD_SW_RPT_GRP=1032. If record exists, set this element to

1, otherwise set this element to 2

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE


Field 82:

Special

Services-

Juvenile

Delinquent



Special Services-Juvenile Delinquent




date or is null.






CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Blank = not

collected/not

applicable

1 Yes

2 No


Field 83:

Substance

Abuse

Services



Substance Abuse Services (CD_SW_RPT_GRP=1034) and

has a begin date less than the investigation completion date

plus 90 days and the services end date is greater than

investigations completion date or is null.

CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

Blank = not

collected/not

applicable

1 Yes

2 No




Valid Values






INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE


Field 84:

Transportatio

n Services



Transportation Services (CD_SW_RPT_GRP=1035) and has

a begin date less than the investigation completion date plus

90 days and the services end date is greater than investigations







CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE

Blank = not

collected/not

applicable

1 Yes

2 No


Field 85:

Other

Services


associated with a statewide reporting category equal Other

Services (CD_SW_RPT_GRP=1036) and has a begin date

less than the investigation completion date plus 90 days and

the services end date is greater than investigations completion

date or is null.

CD_SW_RPT_GRP/

SERVICE_TYPE

DT_BGN & DT_END/

EPISODE

DT_INVS_CMPL/

Blank = not

collected/not

applicable

1 Yes

2 No




Valid Values






INVESTIGATION

DT_ACCESS_RCVD/

ACCESS_REPORT

CD_SW_RPT_GRP/

SERVICE_TYPE


Field 86:

Worker ID

Numeric 12/173-

184

If Worker ID is shorter than 12 bytes, the existing encryption

logic is used. The Worker ID is referenced within the

Encryption Section 1.3.4.

The logic for this field selects the primary investigator

assigned to the investigation from the Investigation shell and

encrypts it.

The TX_IDTFCN_TYPE associated with the Person ID for

the Worker within the Person_Identification table is

encrypted.

SELECT ID_WORKER from INVESTIGATION

join ORG_WORKER_ROLE on

ORG_WORKER_ROLE.ID_WORKER_ROLE=INVESTIG

ATION.ID_WRKR_PRMRY

ID_WORKER/

ORG_WORKER_ROLE

--

Field 87:

Supervisor ID

Numeric 12/185/1

96

The logic for this field selects the Supervisor ID for the unit of

the worker at the time of the disposition of the report. The

encryption logic used is applied to the TX_IDTFCN_TYPE associated with the Person ID for the Supervisor within the

Person_Identification table. The Supervisor ID is referenced

within the Encryption Section 1.3.4.

ID_SUPRV/ORG_UNIT --




Valid Values

SELECT ORG_WORKER_ROLE.ID_UNIT,

ORG_WORKER_ROLE.ID_WORKER from

INVESTIGATION

join ORG_WORKER_ROLE on

ORG_WORKER_ROLE.ID_WORKER_ROLE=INVESTIG

ATION.ID_WRKR_PRMRY

where ID_UNIT= (Unit ID of the worker) and

ID_JOB_CLASS IN (1,2)

and (INVESTIGATION.DT_INVS_CMPL >=

ORG_WORKER_ROLE.DT_START

and (INVESTIGATION.DT_INVS_CMPL <=

ORG_WORKER_ROLE.DT_END or

ORG_WORKER_ROLE.DT_END is null))

Field 88:

Perpetrator-1

ID

Numeric 12/197-

208

The logic for this field selects all Perpetrators identified on the

investigation for the child and populates NC88, NC107, and

NC126.

SELECT Distinct ID_PRSN_PERP from ALLEGATION

join person on

ALLEGATION.ID_PRSN_PERP=PERSON.ID_PRSN

where ID_PRSN_VCTM=(Child’s) ID_PRSN and CD_CAN

in (NC26,NC28,NC30,NC32) and populate NC88,NC107,

and NC126.

Note: Do not populate any Perpetrator (NC88-NC144)

information if there are no maltreat disposition levels equal 01

in NC27, NC29, NC31, and NC33.

NOTE: The TX_IDTFCN_TYPE associated with the Person

ID for the Perpetrator within the Person_Identification table is

encrypted.. The Perpetrator ID is referenced within the

Encryption Section 1.3.4.

ID_PRSN_PERP/

ALLEGATION

--




Valid Values

Field 89:

Perpetrator-1

Relationship

Numeric 2/209-

210

The logic for this field looks for a documented relationship

between the Perpetrator-1 and the Child. If it finds one decode

the relationship code, if no record found it then looks to see if

there is a reciprocal relationship.

For example the logic looks first for a Perpetrator-1 to Child

relationship, if none found it looks for a Child to Perpetrator-1

relationship.

The following two conditions need to be checked in case the

user documents just a reciprocal relationship.

Condition 1

SELECT CD_RLTN from RELATIONSHIP WHERE

ID_WRK_TYPE=(Case ID) and CD_WRK_TYPE=2

AND ID_PRSN1= (Perpetrator-1) and ID_PRSN2=(Child)

If CD_RLTN IN (6,14,25,26,42,43,44 ,46,57,58,59,82,85)

SET NC89=01

If CD_RLTN IN

(2,7,8,18,20,27,32,33,34,35,36,37,38,49,50,51,52,64,66,67,70,

71,72,76,77,80,83,84,88) SET NC89=02

If CD_RLTN=31 and the removal date is <= intake date with

substantiated findings then SET NC89=03, else NC89=88

If CD_RLTN IN (29,30,56) and the removal date is <= intake

date with substantiated findings then SET NC89=04, else

NC89=88



NC89=88

If CD_RLTN=75 SET NC89=06

If CD_RLTN IN (68,19) SET NC89=07


CD_RLTN/

RELATIONSHIP

Blank = not

collected/not

applicable

01 Parent

02 Other relative (non-

foster parent)

03 Relative foster

parent

04 Non-relative foster

parent

05 Group home or

residential facility

staff

06 Child day care

provider

07 Unmarried partner

of parent

08 Legal guardian

09 Other professionals

10 Friends or

neighbors

88 Other

99 Unknown or

missing




Valid Values

If CD_RLTN IN (47,69,) SET NC89=09


If CD_RLTN IN (45,,21,16,3,5,16,17,65,) SET NC89=88

If no record found (check Condition 2)

Condition 2



AND ID_PRSN1=(Child) and ID_PRSN2=(Perpetrator-1)

If CD_RLTN in (23,39,40,73,74) SET NC89=01

If CD_RLTN IN

(18,20,34,35,36,37,38,48,53,60,61,62,63,64,66,67,81,86,87)

SET NC89=02


If CD_RLTN IN (16,17,65) SET NC89=88

If NO RECORD FOUND SET NC89=99

Field 90:

Perpetrator-1

as a Parent

Numeric 1/211 The logic for this field looks to see if the relationship between

Perpetrator 1 is “Parent” (NC89=1). If so, find the specific

relationship, otherwise, if NC89 not equal to 1 then set

NC90=blank

The follow two conditions need to be check if the user

documents a reciprocal relationship.

Condition 1 IF NC89<>01 set NC90=blank

ELSE

SELECT CD_RLTN from RELATIONSHIP where

ID_PRSN1=(Perpetrator 1) ID_PRSN and

ID_PRSN2=(child’s ID_PRSN)

If CD_RLTN=(6,14,43,58,82,85) set NC90=1

CD_RLTN/

RELATIONSHIP

Blank = not

collected/not

applicable

1 Biological parent

2 Step-parent

3 Adoptive parent

8 Other parent





Valid Values

If CD_RLTN=(25,26,44,46,59) set NC90=2

If CD_RLTN=(42,57) set NC90=3

If no record found check (Condition 2)

Condition 2


ID_PRSN1=(child’s) ID_PRSN and ID_PRSN2=

(Perpetrator 1) ID_PRSN

If CD_RLTN in (23,39,73) set NC90=1

If CD_RLTN in(40,74) set NC90=2


Field 91:

Perpetrator-1

as a Caretaker

Numeric 1/212 HARD CODE NC91=1 Blank = not

collected/not

applicable

1 Yes

2 No


Field 92:

Perpetrator-1

Age at Report

Numeric 2/213-

214

The logic for this field calculates the Responsible Caregiver

age based upon his or her (Date of Birth –Date of Report).

SELECT

ACCESS_REPORT.DT_ACCESS_RCVD,PERSON.DT_BR

TH from ALLEGATION

join PERSON on



ALLEGATION.ID_INVS=ACCESS_REPORT.ID_INVS

where ACCESS_REPORT.ID_INVS=(investigation ID) and

ALLEGATION.ID_PRSN_PERP=NC88 and calculate age in

years.

DT_ACCESS_RCVD/

ACCESS_REPORT

DT_BRTH/PERSON

Blank = not

collected/not

applicable

Enter Age using two

digits (e.g., 09=9 yrs.)

75 = 75 years or older

99 = Unknown or

missing




Valid Values

If age < 06 set NC92=blank

If age > 75 set NC92=75

Field 93:

Perpetrator-1

Sex

Numeric 1/215 Use the Perpetrator ID to select the CD_GNDR in the

PERSON table.

SELECT CD_GNDR from PERSON join ALLEGATION on

PERSON.ID_PRSN=ALLEGATION. ID_PRSN_PERP

where ID_PRSN_PERP=NC88

If CD_GNDR = “M” (Male), set to “1”

If CD_GNDR = “F” (Female), set to “2”

If CD_GNDR = “U” (Unknown) set to “9”

If CD_GNDR= “null” set NC93 to 9

CD_GNDR/PERSON Blank = not

collected/not

applicable

1 Male

2 Female


Field 94:

Perpetrator-1

Race

(American

Indian or

Alaska

Native)

Numeric 1/216 This selects FL_RACE_AMERICAN from PERSON table for

Perpetrator-1.




FL_RACE_AMERICAN/

PERSON


1 Yes

2 No



Field 95:

Perpetrator-1

Race (Asian)

Numeric 1/217 This selects the FL_RACE_ASIAN from the PERSON table

for Perpetrator-1.





Race is missing

FL_RACE_ASIAN/

PERSON


1 Yes

2 No



Field 96:

Perpetrator-1

Numeric 1/218 **CHANGE**

FL_RACE_BLACK/ Blank = not collected

1 Yes




Valid Values

Race (Black

or African

American)

This selects FL_RACE_BLACK from the PERSON table for

Perpetrator-1.





Race is missing

PERSON 2 No



Field 97:

Perpetrator-1

Race (Native

Hawaiian or

Other Pacific

Islander)

Numeric 1/219 This selects FL_RACE_HAWAIIAN from the PERSON table

for Perpetrator-1.




FL_RACE_HAWAIIAN/

PERSON


1 Yes

2 No



Field 98:

Perpetrator-1

Race (White)

Numeric 1/220 This selects the FL_RACE_WHITE from the PERSON table

Perpetrator-1.




FL_RACE_WHITE/

PERSON


1 Yes

2 No



Field 99:

Perpetrator-1

Race (Unable

to Determine)

Numeric 1/221 This selects the FL_RACE_UNBL_DTRMN from the

PERSON table for Perpetrator-1.

SELECT FL_RACE_UNBL_DTRMN from PERSON

If FL_RACE_UNBL_DTRMN=“Y” set NC99=1

If FL_RACE_UNBL_DTRMN=“N” set NC99=2

Screen Location: Person Management > Basic tab

SELECT FL_RACE_UNKNOWN from PERSON

FL_RACE_UNBL_DTRM

N/

PERSON

FL_RACE_UNKNOWN/

PERSON


1 Yes

2 No





Valid Values

IF FL_RACE_UNKNOWN =“Y” set NC99=9

IF FL_RACE_DCLND = “Y” set NC99=9

Field 100:

Perpetrator-1

Ethnicity

Numeric 1/222 **CHANGE**

This selects the Hispanic/Latino for the Perpetrator-1 from the

PERSON table.

SELECT CD_HSPNC from PERSON join ALLEGATION on


where ALLEGATION.ID_PRSN_PERP=NC88






Screen Location: Person Management > Basic tab

Same as NC21

CD_HSPNC/

PERSON

Same as NC21

Blank = not

collected/not

applicable

1 Yes, Hispanic or

Latino

2 Not Hispanic or

Latino



Field 101:

Perpetrator-1

Military

Member

Numeric 1/223 The logic for this field looks to see if the Perpetrator-1 is an

active member of the military.

SELECT FL_PRN_LG_DPN_AV_DT from PERSON

JOIN ALLEGATION on

ID_PRSN_PERP=PERSON.ID_PRSN where

ID_PRSN_PERP=NC88

If FL_PRN_LG_DPN_AV_DT= “Y” set NC101=1

If FL_PRN_LG_DPN_AV_DT=“N” set NC101=2


FL_PRN_LG_DPN_AV_D

T/

PERSON

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values





label.

Field 102:

Perpetrator-1

Prior Abuser

Numeric 1/224 The logic for this field selects all allegations where the intake

is less than the current report’s received date and checks to see

if there are any allegations associated with the Perpetrator that

are “Verified” If there are the field is set equal to 1 else if no

records founds or there are no “Verified” maltreatments we

set it to 2.

SELECT CD_FIND,ID_PRSN_PERP from ALLEGATION

join

INVESTIGATION on


join ACCESS_REPORT on INVESTIGATION.ID_INVS

=ACCESS_REPORT.ID_INVS

join INTAKE_PART on


where

ALLEGATION.ID_PRSN_PERP=INTAKE_PART.ID_PRS

N and DATE(DT_ACCESS_RCVD) <= NC06

and ALLEGATION.CD_FIND=1 and

ALLEGATION.ID_PRSN_PERP=NC88

If record is found set to 1,else set to 2

ID_PRSN_PERP/

ALLEGATION

CD_FIND/ALLEGATION

Blank = not

collected/not

applicable

1 Yes

2 No


Field 103:

Perpetrator-1

Maltreatment-

1

Numeric 1/225 The logic for this field selects the maltreatment code from

NC26 and checks to see if the Perpetrator identified in NC88

was the one that caused the maltreatment.

SELECT CD_CAN from ALLEGATION where

CD_CAN/ALLEGATION

Blank = not

collected/not

applicable

1 Yes, Child

Maltreatment-1 Type




Valid Values

CD_CAN=NC26 and ID_PRSN_PERP=(Perpetrator-1)

ID_PRSN and ID_PRSN_VCTM=(Child’s) ID_PRSN

If record found set NC103=1


2 No, Child

Maltreatment-1 Type

Field 104:

Perpetrator-1

Maltreatment-

2

Numeric 1/226 The logic for this field selects the Maltreatment Code from

NC28 and checks to see if Perpetrator-1 identified in NC88 is

the person responsible for the maltreatment.






CD_CAN/ALLEGATION Blank = not

collected/not

applicable

1 Yes, Child

Maltreatment-2 Type

2 No, Child

Maltreatment-2 Type

Field 105:

Perpetrator-1

Maltreatment-

3



the person responsible for the maltreatment.







collected/not

applicable

1 Yes, Child

Maltreatment-3 Type

2 No, Child

Maltreatment-3 Type

Field 106:

Perpetrator-1

Maltreatment-

4



the person responsible for e maltreatment.







collected/not

applicable

1 Yes, Child

Maltreatment-4 Type

2 No, Child

Maltreatment-4 Type




Valid Values

Field 107:

Perpetrator-2

ID

Numeric 12/229-

240

SEE Field 88

ID_PRSN_PERP/

ALLEGATION

This is the identifier

for the second

perpetrator on the

record. Perpetrators

included in a record

should only be the

perpetrators for the

specific child record.

Field 108:

Perpetrator-2

Relationship

Numeric 2/241-

242

The logic for this field is for a documented relationship

between the Perpetrator-2 and the child. If a relationship is

found, one decodes the relationship code, if no record found it

then looks to see if there is a reciprocal relationship

documented. For example the logic looks first for a

Perpetrator-2 to Child relationship, if none found it looks for a

Child to Perpetrator-2 relationship and decodes the values.

The following two conditions need to be checked to ensure

the user documents just a reciprocal relationship.

Condition 1




If CD_RLTN IN (6,14,25,26,42,43,44 ,46,57,58,59,82,85)

SET NC108=01

If CD_RLTN IN

(2,7,8,18,20,27,32,33,34,35,36,37,38,49,50,51,52,64,66,67,70,

71,72,76,77,80,83,84,88) SET NC108=02



CD_RLTN/

RELATIONSHIP

Blank = not

collected/not

applicable

01 Parent


foster parent)

03 Relative foster

parent


parent

05 Group home or


staff

06 Child day care

provider


of parent

08 Legal guardian





Valid Values



NC108=88



NC108=88








Condition 2





If CD_RLTN IN

(18,20,34,35,36,37,38,48,53,60,61,62,63,64,66,67,81,86,87)

SET NC108=02




10 Friends or

neighbors

88 Other

99 Unknown or

missing

Field 109:

Perpetrator-2

as a Parent


Perpetrator 2 is “Parent” (NC108=1) if so, find the specific

relationship else if NC108 not equal to 1 then set

NC109=blank.

The follow two conditions need to be checked to ensure the

CD_RLTN/

RELATIONSHIP

Blank = not

collected/not

applicable

1 Biological parent

2 Step-parent




Valid Values

user documents just a reciprocal relationship

Condition 1 If NC108<>01 set NC109=blank

ELSE




If CD_RLTN=(6,14,43,58,82,85) set NC109=1

If CD_RLTN=(25,26,44,46,59) set NC109=2



Condition 2







3 Adoptive parent

8 Other parent


Field 110:

Perpetrator-2

as a Caretaker

Numeric HARD CODE=1 Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values

Field 111:

Perpetrator-2

Age at Report

Numeric 2/245-

246


age based upon there (Date of Birth –Date of Report).

SELECT


TH from ALLEGATION

join PERSON on





ALLEGATION.ID_PRSN_PERP=NC107 and calculate age

in years.



DT_ACCESS_RCVD/

ACCESS_REPORT

DT_BRTH/PERSON

Blank = not

collected/not

applicable

Enter Age using two



99 = Unknown or

missing

Field 112:

Perpetrator-2

Sex

Numeric 1/247 Use the Perpetrator ID to select the CD_GNDR in the

PERSON table.








collected/not

applicable

1 Male

2 Female


Field 113:

Perpetrator-2

Race

(American

Indian or

Numeric 1/248 This selects FL_RACE_AMERICAN from the PERSON table

for Perpetrator-2.



FL_RACE_AMERICAN/

PERSON


1 Yes

2 No





Valid Values

Alaska

Native)

If FL_RACE_AMERICAN=“N” set NC113=2 9 Unknown or missing

Field 114:

Perpetrator-2

Race (Asian)

Numeric 1/249 This selects the FL_RACE_ASIAN from PERSON table for

Perpetrator-2.





Race is missing

FL_RACE_ASIAN/

PERSON


1 Yes

2 No



Field 115:

Perpetrator-2

Race (Black

or African

American)

Numeric 1/250 This selects FL_RACE_BLACK from PERSON table for

Perpetrator-2.





Race is missing

FL_RACE_BLACK/

PERSON


1 Yes

2 No



Field 116:

Perpetrator-2

Race (Native

Hawaiian or

Other Pacific

Islander)

Numeric 1/251 This selects FL_RACE_HAWAIIAN from the PERSON table

for Perpetrator-2.




FL_RACE_HAWAIIAN/

PERSON


1 Yes

2 No



Field 117:

Perpetrator-2

Race (White)

Numeric 1/252 This selects the FL_RACE_WHITE from the PERSON table

Perpetrator-2.




FL_RACE_WHITE/

PERSON


1 Yes

2 No





Valid Values


Field 118:

Perpetrator-2

Race (Unable

to Determine)

Numeric 1/253 This selects the FL_RACE_UNBL_DTRMN from PERSON

table for Perpetrator-2.

SELECT FL_RACE_UNBL_DTRMN from PERSON

If FL_RACE_UNBL_DTRMN=“Y” set NC118=1


SELECT PERSON.FL_RACE_UNKNOWN from PERSON

IF PERSON.FL_RACE_UNKNOWN =“Y” set NC118=9


FL_RACE_UNBL_DTRM

N/PERSON

FL_RACE_UNKNOWN/

PERSON


1 Yes

2 No


Field 119:

Perpetrator-2

Ethnicity

Numeric 1/254 Selects the Hispanic/Latino for the Perpetrator-2 from the

PERSON table.









CD_HSPNC/PERSON

Same as NC21

Blank = not

collected/not

applicable

1 Yes, Hispanic or

Latino

2 Not Hispanic or

Latino



Field 120:

Perpetrator-2

Military



FL_PRN_LG_DPN_AV_D

T/PERSON

Blank = not

collected/not




Valid Values

Member SELECT FL_PRN_LG_DPN_AV_DT from PERSON

JOIN ALLEGATION on


ID_PRSN_PERP=NC107








label.

applicable

1 Yes

2 No


Field 121:

Perpetrator-2

Prior Abuser


is less than the current reports received date and checks to see


are “Verified.”

If there are allegations the field is set to equal 1, else if no

records founds or there are no “Verified” maltreatments it is

set to 2.


join

INVESTIGATION on




join INTAKE_PART on


where

ID_PRSN_PERP/

ALLEGATION

CD_FIND/ALLEGATION

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values





If record found set to 1, else set to 2

Field 122:

Perpetrator-2

Maltreatment-

1





CD_CAN=NC26 and ID_PRSN_PERP=(Perpetrator-2

ID_PRSN ) and ID_PRSN_VCTM=(Child’s ID_PRSN )



CD_CAN/

ALLEGATION

Blank = not

collected/not

applicable

1 Yes, Child

Maltreatment-1 Type

2 No, Child

Maltreatment-1 Type

Field 124:

Perpetrator-2

Maltreatment-

3


NC30 and checks to see if the perpetrator identified in NC107







CD_CAN /

ALLEGATION

Blank = not

collected/not

applicable

1 Yes, Child

Maltreatment-3 Type

2 No, Child

Maltreatment-3 Type

Field 125:

Perpetrator-2

Maltreatment-

4








CD_CAN/

ALLEGATION

Blank = not

collected/not

applicable

1 Yes, Child

Maltreatment-4 Type

2 No, Child




Valid Values

If no record found set NC125=2 Maltreatment-4 Type

Field 126:

Perpetrator-3

ID

Numeric 12/261-

272

See logic for Field 88. ID_PRSN_PERP/

ALLEGATION

A unique

identification assigned

to the third person

who caused or

knowingly allowed

child maltreatment to

occur.

This is the ID of the

third perpetrator

associated with this

record. All three

perpetrator sections in

this record should be

left blank if the child

does not have at least

one Maltreatment

Disposition Level

equal to Substantiated,

Indicated, or Alternate

Response Victim.

This identification is

not the actual State

perpetrator

identification but is an




Valid Values

encrypted

identification assigned

by the State for

purposes of the Child

File data collection.

The Perpetrator ID

should be unique

within the State, only

used for this

perpetrator and never

used again.

The encrypted

identifier should be

left-filled with zeros,

as needed, to the 12

character length.

Field 127:

Perpetrator-3

Relationship

Numeric 2/273-

274

The logic for this field is for a documented relationship

between the Perpetrator-3 and the Child. If it finds one, it

decodes the relationship code, if no record found it then looks

to see if there is a reciprocal relationship documented. For

example the logic looks first for a Perpetrator-3 to Child

relationship, if none found it looks for a Child to Perpetrator-3

relationship and decodes the values.

The following two conditions need to be checked in case the

user documents just a reciprocal relationship.

Condition 1

CD_RLTN/

RELATIONSHIP Blank = not

collected/not

applicable

01 Parent


foster parent)

03 Relative foster

parent


parent




Valid Values




If CD_RLTN IN (6,14,25,26,42,43,44 ,46,57,58,59,82,85)

SET NC127=01

If CD_RLTN IN

(2,7,8,18,20,27,32,33,34,35,36,37,38,49,50,51,52,64,66,67,70,

71,72,76,77,80,83,84,88) SET NC127=02





NC127=88



NC127=88

SET NC127=05








Condition 2





If CD_RLTN IN

05 Group home or


staff

06 Child day care

provider


of parent

08 Legal guardian


10 Friends or

neighbors

88 Other

99 Unknown or

missing




Valid Values

(18,20,34,35,36,37,38,48,53,60,61,62,63,64,66,67,81,86,87)

SET NC127=02




Field 128:

Perpetrator-3

as a Parent


Perpetrator 3 is “Parent” (NC127=1)if they are find specific

relationship else if NC127 not equal to 1 then set

NC128=blank

The follow two conditions need to be check in case the user

documents just a reciprocal relationship.

Condition 1

IF NC127<>01 set NC128=blank

ELSE




If CD_RLTN=(6,14,43,58,82,85) set NC128=1

If CD_RLTN=(25,26,44,46,59) set NC128=2



Condition 2






CD_RLTN/

RELATIONSHIP

Blank = not

collected/not

applicable

1 Biological parent

2 Step-parent

3 Adoptive parent

8 Other parent





Valid Values


Field 129:

Perpetrator-3

as a Caretaker

Numeric 1/276 HARDCODE=1 Blank = not

collected/not

applicable

1 Yes

2 No


Field 130:

Perpetrator-3

Age at Report

Numeric 2/277-

278


age based upon there (Date of Birth –Date of Report)

SELECT


TH from ALLEGATION

join PERSON on





ALLEGATION.ID_PRSN_PERP=NC126 and calculate age

in years.



DT_ACCESS_RCVD/

ACCESS_REPORT

DT_BRTH/PERSON

Blank = not

collected/not

applicable

Enter Age using two



99 = Unknown or

missing

Field 131:

Perpetrator-3

Sex

Numeric 1/279 Use the Perpetrator -3 ID to select the CD_GNDR in the

PERSON table.





collected/not

applicable

1 Male

2 Female




Valid Values





Field 132:

Perpetrator-3

Race

(American

Indian or

Alaska

Native)

Numeric 1/280 This selects FL_RACE_AMERICAN from PERSON table for

Perpetrator-3




FL_RACE_AMERICAN/

PERSON


1 Yes

2 No



Field 133:

Perpetrator-3

Race (Asian)

Numeric 1/281 This selects the FL_RACE_ASIAN from PERSON table for

Perpetrator-3





Race is missing

FL_RACE_ASIAN/

PERSON


1 Yes

2 No



Field 134:

Perpetrator-3

Race (Black

or African

American)

Numeric 1/282 This selects FL_RACE_BLACK from PERSON table for

Perpetrator-3.





Race is missing

FL_RACE_BLACK/

PERSON


1 Yes

2 No



Field 135:

Perpetrator-3

Race (Native

Numeric 1/283 This selects FL_RACE_HAWAIIAN from PERSON table for

Perpetrator-3

FL_RACE_HAWAIIAN/

PERSON


1 Yes

2 No




Valid Values

Hawaiian or

Other Pacific

Islander)






Field 136:

Perpetrator-3

Race (White)

Numeric 1/284 This selects the FL_RACE_WHITE from PERSON table

Perpetrator-3




FL_RACE_WHITE/

PERSON


1 Yes

2 No



Field 137:

Perpetrator-3

Race (Unable

to Determine)

Numeric 1/285 This select the FL_RACE_UNBL_DTRMN from PERSON

table for Perpetrator-3

SELECT FL_RACE_UNBL_DTRMN from PERSON IF

FL_RACE_UNBL_DTRMN=“Y” set NC137=1


SELECT PERSON.FL_RACE_UNKNOWN from PERSON

IF PERSON.FL_RACE_UNKNOWN =“Y” set NC137=9


FL_RACE_UNBL_DTRM

N/PERSON

FL_RACE_UNKNOWN/

PERSON


1 Yes

2 No


Field 138:

Perpetrator-3

Ethnicity

Numeric 1/286 Selects the Hispanic/Latino for the Perpetrator-3 from the

PERSON table.








CD_HSPNC/PERSON

Same as NC21

Blank = not

collected/not

applicable

1 Yes, Hispanic or

Latino

2 Not Hispanic or

Latino






Valid Values


Same as NC21

Field 139:

Perpetrator-3

Military

Member



SELECT FL_PRN_LG_DPN_AV_DT from PERSON

JOIN ALLEGATION on


ID_PRSN_PERP=NC126








label.

FL_PRN_LG_DPN_AV_D

T/PERSON

Blank = not

collected/not

applicable

1 Yes

2 No


Field 140:

Perpetrator-3

Prior Abuser


is less than the current reports received date and checks to see


are “Verified” If there are set this field equal to 1 else if no

records founds or there are no “Verified” maltreatments we

set it to 2.


join

INVESTIGATION on


ID_PRSN_PERP/

ALLEGATION

CD_FIND/ALLEGATION

Blank = not

collected/not

applicable

1 Yes

2 No





Valid Values



join INTAKE_PART on


where





If yes set to 1 else set NC140=2

Field 141:

Perpetrator-3

Maltreatment-

1






ID_PRSN ) and ID_PRSN_VCTM=(Childs ID_PRSN )



CD_FIND/ALLEGATION Blank = not

collected/not

applicable

1 Yes, Child

Maltreatment-1 Type

2 No, Child

Maltreatment-1 Type

Field 142:

Perpetrator-3

Maltreatment-

2










collected/not

applicable

1 Yes, Child

Maltreatment-2 Type

2 No, Child

Maltreatment-2 Type

Field 143:

Perpetrator-3

Maltreatment-

Numeric 1/291 The logic for this field selects the maltreatment code from

NC30 and checks to see if the perpetrator identified in NC126



collected/not




Valid Values

3






applicable

1 Yes, Child

Maltreatment-3 Type

2 No, Child

Maltreatment-3 Type

Field 144:

Perpetrator-3

Maltreatment-

4










collected/not

applicable

1 Yes, Child

Maltreatment-4 Type

2 No, Child

Maltreatment-4 Type

Field 145:

AFCARS ID

Numeric 12/293-

304

SAME AS NC04

Field 146:

Incident Date

Date 8/305-

312

This is the most recent incident date that occurred for any

maltreatment associated with this investigation. The incident

date reported is based upon the seriousness of the finding.

First look at all “Verified” incident dates then “Some

Indicator”, then “Not Substantiated”, then “No Indicator.”

SELECT MAX DT_INCIDENT from ALLEGATION where

ID_PRSN_VCTM=(Child’s ID_PRSN) where

ID_INVS=(Investigation ID)

where DT_INCIDENT < DT_ACCESS_RCVD

and((CD_FIND=1) else CD_FIND=2 else CD_FIND=4 else

CD_FIND=3)

DT_INCIDENT/

ALLEGATION

DATE (mmddyyyy)





Valid Values

If DT_INCIDENT > DT_ACCESS_RCVD set

NC146=DT_ACCESS_RECVD **Ensure this logic is

working properly because if the DT_INCIDENT >

DT_ACCESS_RCVD, this date should reflect the Initial

Intake Received Date, which is the Report Date captured in

Element NC6.

If NULL or no record found set NC146=blank

Field 147:

Report Time

Numeric 4 digit Report Time: the exact time (hour and minute) that the report

was received by the hotline or other intake unit, formatted in

24 hour format HHMM. Note – this is not the decision time,

this is the time the report was received. This should be the

time from the date that was used for NC6.

DT_ACCESS_RCVD/

ACCESS_REPORT

Time (HHMM) 24

hour format

Field 148:

Investigation

Start Time

Numeric Investigation Start Time - the exact time (hour and minute)

the CPS agency's response was initiated, formatted in 24-hour

format HHMM. This should be the time for the date that was

used for NC7.

DT_BEGIN/CAN_TEXT_

EVENT or

DT_BEGIN/CAN_EVENT

_TYPE as applicable

Time (HHMM) 24

hour format

Field 149:

Maltreatment

Death Date

Date Maltreatment Death Date - the exact day (day, month, and

year) that a child died due to child abuse or neglect, reported

in MMDDYYYY format. A date should only be captured here

if one of the child’s maltreatments = Death (code value 6 in

FSFN) and the associated Finding = Verified; this should only

be reported for the current record that this Element is

associated with if the criteria identified here are met.

PERSON/DT_DTH

Where verified

maltreatment is Death (6)

DATE (mmddyyyy)

Field 150:

Foster Care

Discharge

Date

Date Foster Care Discharge Date - the exact date (day, month, and

year) that the child was discharged from the foster care

episode for those records where there was a removal, reported

in MMDDYYY format. It is important to note that this is not

just whenever the last foster care discharge date is, they

DT_END/EPISODE DATE (mmddyyyy)




Valid Values

specifically want to see the discharge that is related to the

specific removal that resulted from the specific investigation

record identified in the row. So they expect the discharge date

to be after the report disposition date. They do not want foster

care episodes that ended before the report disposition date,

those should be excluded, unless they truly were removed and

discharged before the investigation that resulted in the

removal was ever finished.

This Element should capture the “Discharge Date” of the

Removal Episode identified for Element 61. As long as

Element 61 is captured accurately, which reflects the logic for

pulling that date field, this Element will be the Discharge Date

of that Removal, if discharged within the Report Period.

Otherwise, this Element will be set to “null”.



2.1 Agency Data File

PREVENTIVE SERVICES

1. Children Who Received Preventive Services From the State During the Year Children

Funding Source: Child Abuse and Neglect State Grant:

2. Families Who Received Preventive Services From the State During the Year Families

Funding Source: Child Abuse and Neglect State Grant:


Funding Source: Community-Based Prevention of Child Abuse and Neglect Grant:


Funding Source: Community-Based Prevention of Child Abuse and Neglect Grant:


Funding Source: Promoting Safe and Stable Families ProgramT:


Funding Source: Promoting Safe and Stable Families Program:


Funding Source: Social Services Block Grant


Funding Source: Social Services Block Grant


Funding Source: Other


Funding Source: Other

11. Number of Referrals Screened Out

12. Number of Children Screened Out

13. Response Time with Respect to the Initial Investigation or Assessment:

14. Number of Staff Responsible for CPS Functions (Screening, Intake, and

Investigation/Assessment of Reports) During the Year:

15. Number of Staff Responsible for the Screening and Intake of Reports During the Year:

CHILD VICTIMS:

16. Child Victims (substantiated, indicated or alternative response victim) Whose Families

Received Family Preservation Services in the Previous Five Years:

:

17. Child Victims (substantiated, indicated or alternative response victim) Who Were

Reunited with Their Families in the Previous Five Years:



18. Average Number of Out-of-Court Contacts Between the Court-Appointed

Representatives and the Child Victims (substantiated, indicated or alternative response

victim) They Represent

CHILD FATALITIES:

19. Child Victims (substantiated, indicated or alternative response victim) Who Died as a

Result of Maltreatment and Whose Families Had Received Family Preservation Services

in the Previous Five Years:

20. Child Victims (substantiated, indicated or alternative response victim) Who Died as a

Result of Maltreatment and Had Been Reunited with Their Families in the Previous Five

Years

21. Child Maltreatment Fatalities Not Reported in the Child File

22. Child Victims Who Died as a Result of Maltreatment While in Foster Care Not Reported

in the Child File

23. Child Victims Who Died as a Result of Maltreatment and Whose Families Had Received

Family Preservation Services in the Previous Five Years Not Reported in the Child File

24. Child Victims Who Died as a Result of Maltreatment and Had Been Reunited with Their

Families in the Previous Five Years Not Reported in the Child File

25. Children Eligible for Referral-Individuals with Disabilities Education Act

26. Children Referred-Individuals with Disabilities Education Act



2.2 FSFN Reference Values Document

2.2.1 Reporter – NC08

ID_GRPI TX_DESC_MED

NCANDS Application

Mapping

-------- ---------------

1 Anonymous 13

2 Attorney 4 NCANDS Federal Values

3 Babysitter 11 blank = not collected

4 B/CU/S&L E/T 88 01 Social services personnel

5 Caregiver 88 02 Medical personnel

6 CBC employee 01 03 Mental Health personnel

7 Clergy 88 04 Legal, law enforcement, or criminal justice personnel

8 Court Personnel 04 05 Education personnel

9 DCare Ownr/Empl 06 06 Child day care provider

10 Dept. Employee 01 07 Foster care provider

11 Dept. Bus.&RE 88 08 Alleged victim

12 DJJ/DOC/CJP 01 09 Parent

13 FLAC/CRC 88 10 Other relative

14 Guardian 04 11 Friends/neighbor

15 GuardianAdLitem 04 12 Alleged perpetrator

16 HospitalSocWrkr 02 13 Anonymous reporter

17 Inst. Employee 01 88 Other

18 Judge 04 99 Unknown or missing

19 Law Enforcement 04

20 Long-Term COC 88

21 Med.Examiner 02

22 Mental HP 03

23 Med. Personnel 02

24 Neighbor/Friend 11



ID_GRPI TX_DESC_MED

NCANDS Application

Mapping

25 Nurse 02

26 NH/ALF/AFCH Stf n/a

27 Other 88

28 Other H/MH Prf 01

29 Oth. School Stf 05

30 Paramedic/EMT 02

31 Parent 09

32 Physician 02

33 Prcpl/AsstPrcpl 05

34 Relative 10

35 SclCnlr/SocWrkr 05

36 School Nurse 05

37 SocServPrsn 01

38 PAgcySocServStf 01

39 SpiritualHealer 88

40 Teacher 05

105 Victim 08



2.2.2 NC09, NC27, NC29, NC31, NC33 Disposition Levels

ALLEGATIONS FINDINGS Application Mapping NCANDS Federal Values

ID_GRPI TX_DESC_LRG 01 Substantiated

02 Indicated or reason to suspect

1 Verified 1 03 Alternative response disposition-victim

2 Some Indicator 5 04 Alternative response disposition-not a victim

3 No Indicator 5 05 Unsubstantiated

4 Not Substantiated 5 06 Unsubstantiated due to intentionally false reporting

07 Closed-no finding

88 Other




NC11 Notifications

D_GRPI TX_DESC_LRG Application Mapping NCANDS Values

---------- ---------------------------------- blank = not collected

1 State Attorney 2 1 None

2 Law Enforcement 2 2 Police/prosecutor

3 Florida Local Advocacy Council 8 3 Licensing agency

4 District/Region Administration 8 4 Both

5 Child Protection Team 8 8 Other

6 Parents/Legal Custodian 8 9 Unknown or missing

7 Contracting Unit 8

8 Facility Administration 8

9 Licensing Unit 3

10 Reporter 1

11 Rights and Responsibility Pamphlet 1

12 ICWA 1

13 TANF 1

14 HIPAA 1

15 Other 8



2.2.3 Living Arrangement (Family) – NC23

SACWIS Reference Value NCANDS Mapped Value

1 Married two parent household, with two

biological/adoptive parents

01 Married two parent household, with two


2 Married two parent household with one

biological/adoptive and one step parent

02 Married two parent household, with one

biological/adoptive and one step parent

3 Unmarried two parent household with two


03 Unmarried two parent household with two


4 Unmarried two parent household with one

biological/adoptive parent and one cohabitating partner

04 Unmarried two parent household with one

biological/adoptive parent and one cohabitating partner

5 Two parent household, marital status unknown 05 Two parent household, marital status unknown

6 Single parent household, mother only 06 Single parent household, mother only

7 Single parent household, father only 07 Single parent household, father only

8 Single parent household mother with other adult

(grandmother, sister, unrelated adult, etc.)

08 Single parent household mother with other adult

(grandmother, sister, unrelated adult)

9 Single parent household, father with other adult

(grandmother, brother, unrelated adult, etc.)

09 Single parent household father with other adult

(grandmother, sister, unrelated adult, etc.)

10 Non-parent relative caregiver household (includes

relative foster care)

10 Non-parent relative caregiver household (includes


11 Non-relative caregiver household (includes non-


11 Non-relative caregiver household (includes non-


12 Group home or residential treatment setting 12 Group home or residential treatment setting

88 Other setting (hospital, secure facilities, etc.) 88 Other setting (hospital, secure facilities, etc.)

99 Unknown 99 Unknown

101 Not Collected Blank = not collected



2.2.4 NC26, NC28, NC30, NC32 – Maltreatment Types

ID_GRPI TX_DESC_LRG Application Mapping NCANDS Values

ID_GRPI TX_DESC_LRG Blank = not collected/not applicable

---------- --------------------------------------------------- 1 Physical Abuse

1 Abandonment 2 2 Neglect or deprivation of necessities

2 Asphyxiation 1 3 Medical neglect

3 Bizarre Punishment 5 4 Sexual abuse

4 Bone Fracture 1 5 Psychological or emotional maltreatment

5 Burns 1 6 No alleged maltreatment

6 Death 8 8 Other

7 Environmental Hazards 2 9 Unknown or missing

8 Failure to Protect 2

9 Failure to Thrive 2

10 Family Violence Threatens Child 8

11 Inadequate Supervision 2

12 Internal Injuries 1

13 Malnutrition/Dehydration 2

14 Medical Neglect 3

15 Mental Injury 5

16 Physical Injury 1

17 Sexual Abuse (inactive value) 4

18 Substance Misuse 2

19 Threatened Harm 8

40 Alcohol Exposed Child (inactive value) 2

41 Beatings (inactive value) 1

43 Bruises/Welts (inactive value) 1

45 Child Well-Being (inactive value) 2

46 Child-on-Child (inactive value) 8

47 Cuts/Punctures/Bites (inactive value) 1




49 Deadly Weapon (inactive value) 8

51 Deadly Weapon Injury (inactive value) 8

53 Dislocation (inactive value) 1

55 Excessive Corporal Punishment (inactive value) 1

56 Failure to Provide Medical Care (Religious Reasons) (inactive value) 3

58 Family Assessment (for Miami-Dade County Only) n/a

60 Foster Care Referral (inactive value) 8

62 Har/Bel/Rid by Staff n/a

64 Inadequate Clothing n/a

66 Inadequate Food n/a

68 Inadequate Shelter n/a

70 Inadequate Supervision - Parent Absent n/a

72 Inadequate Supervision-Lockout n/a

74 Inad-Supv/DJJ-Restorative n/a

76 Inapp/Excess Drug Given (inactive value) 8

77 Inappropriate/Excessive Isolation (Facility Only) n/a

79 Inappropriate/Excessive Restraints (Facility Only) n/a

81 Other Child Dead Abuse/Neglect (inactive value) 8

82 Other Sexual Maltreatment (inactive value) 4

84 Parent Needs Assistance (inactive value) 6

85 Parent(s) Deceased n/a

86 Parent(s) Hospitalized n/a

87 Parent(s) Incarcerated n/a

88 Physically Drug Dependent Newborn (inactive value) 2

89 Poisoning n/a

91 Sexual Abuse - Other Child (inactive value) 8

92 Sexual Battery (Incest) n/a

94 Sexual Battery (Not Incest) n/a

96 Sexual Exploitation n/a

98 Sexual Molestation n/a




100 Skull/Brain/Spinal Injury N/A

102 Substance Exposed Child (inactive value) 2

103 Violated Access Order n/a

105 WAGES Referral (inactive value) 8

112 Human Trafficking (inactive value) 1

Human Trafficking CSES 4

Human Trafficking Labor 5

119 Sexual Abuse – Sexual Battery 4

120 Sexual Abuse – Exploitation by Parent/Legal Guardian 4

121 Sexual Abuse – Sexual Molestation 4

122 Substance Misuse - Alcohol 2

123 Substance Misuse – Illicit drugs 2

124 Substance Misuse – Prescription Drugs 2

125 Failure to Thrive/ Malnutrition/ Dehydration 2

126 Household Violence Threatens Child 8

127 Intimate Partner Violence Threatens Child 8

128 Substance Exposed Newborn 2

2.2.5 NC52 – NC55 Characteristics ID_GRPI TX_LDESC_MED ELEMENT # NCANDS Values

---------- ----------------------------------------------------------------- Blank = not collected/not applicable

1 Alcohol and Drug abuse by caregiver both apparent/significant 1 Yes

2 Alcohol abuse by caregiver (no drugs apparent/significant) 2 No

3 Drug abuse by caregiver - (no alcohol abuse apparent/significant) 9 Unknown or missing

4 Domestic violence among adults in household 52

5 Chaotic/disorganized/crisis lifestyle of caregiver(s)

6 Life crises or external stressor affecting caregiver

7 Developmental disability of caregiver

8 Diagnosed mental illness of caregiver



ID_GRPI TX_LDESC_MED ELEMENT # NCANDS Values

9 Serious illness/phys. disability affects caregiver capacity

10 Unresolved history of trauma affects caregiver

11 Blurred roles and boundaries within family

12 Inadequate housing or problems maintaining housing 53

13 Poor/Violent neighborhood conditions

14 Homeless 53

15 Single parent household

16 Partner/non-family member in household which poses a concern

17 Social isolation/lack of support systems

18 Heavy child care responsibility

19 Child with special needs

20 Inadequate child care

21 Lack of motivation/skill/knowledge in parenting

22 Unemployment

23 Employed poverty level 54

24 Other financial stress 54

25 Other

26 None Observed

27 Not Applicable - No allegation relating to primary caregiver

28 Insufficient Financial Resources 54

29 Receiving Public Assistance

2.2.6 NC90, 109, 128 Perpetrator as Parent

ID_GRPI TX_DESC_LRG Mapping to NC90,109,128 NCANDS

39 Daughter 1 Blank = not collected/not applicable

43 Father-Biological 1 1 Biological parent

58 Mother-Biological 1 2 Step-parent

73 Son 1 3 Adoptive parent

82 Father 1 8 Other parent



85 Mother 1 9 Unknown or missing

6 Father 1

14 Mother 1

40 Daughter-Step 2

44 Father-Legal by Wedlock 2

46 Father-Step 2

59 Mother-Step 2

74 Son-Step 2

42 Father-Adoptive 3

57 Mother-Adoptive 3



NC89, 108, 127 Relationship to Perpetrator

ID_GRPI TX_DESC Application Mapping for NC89,108,127 NCANDS Values

14 Mother 01 Blank = not collected/not applicable

23 Son/Daughter 01 01 Parent

25 Stepfather 01 02 Other relative (non-foster parent)

26 Stepmother 01 03 Relative foster parent

39 Daughter 01 04 Non-relative foster parent

40 Daughter-Step 01 05 Group home or residential facility staff

42 Father-Adoptive 01 06 Child day care provider

43 Father-Biological 01 07 Unmarried partner of parent

44 Father-Legal by Wedlock 01 08 Legal guardian

46 Father-Step 01 09 Other professionals

57 Mother-Adoptive 01 10 Friends or neighbors

58 Mother-Biological 01 88 Other

59 Mother-Step 01 99 Unknown or missing

6 Father 01

73 Son 01

74 Son-Step 01

82 Father 01

85 Mother 01

18 Other Relative 02

2 Aunt 02

20 Sibling 02

27 Uncle 02

32 Aunt-Maternal 02

33 Aunt-Paternal 02

34 Brother 02

35 Brother-Half 02

36 Brother-Step 02




37 Cousin-Maternal 02

38 Cousin-Paternal 02

48 Granddaughter 02

49 Grandfather-Maternal 02

50 Grandfather-Paternal 02

51 Grandmother-Maternal 02

52 Grandmother-Paternal 02

53 Grandson 02

60 Nephew-Maternal 02

61 Nephew-Paternal 02

62 Niece-Maternal 02

63 Niece-Paternal 02

64 Other-Maternal Relative 02

66 Other-Paternal Relative 02

67 Other-Relative 02

7 Grandfather 02

70 Sister 02

71 Sister-Half 02

72 Sister-Step 02

76 Uncle-Maternal 02

77 Uncle-Paternal 02

8 Grandmother 02

80 Aunt 02

81 Cousin 02

83 Grandfather 02

84 Grandmother 02

86 Nephew 02

87 Niece 02

88 Uncle 02

31 Approved Relative Caregiver 03




29 Adoptive Parent - Non-Finalized Adoption 04

30 Approved Non-Relative Caregiver 04

56 Licensed Family Shelter/Foster Parent 04

12 Institution Employee 05

13 Institution /Facility/Owner/Operator 05

41 Facility Staff 05

19 Paramour 07

21 Significant Other 07

68 Paramour-Parent/Caregiver 07

54 Guardian/Custodian-Not Parent 08

9 Guardian/Custodian - Not Parent 08

10 HCDA/HCE Provider 09

11 Home Health Care 09

4 DCF Employee - Not Institution 09

47 FS Employee/Designee 09

69 School Personnel/Teacher 09

15 Neighbor/Friend 10

22 Sitter 10

75 Sitter 10

1 Attorney 88

16 Other 88

17 Other Client/Patient 88

3 Bank Employee 88

45 Father-Prospective 88

5 Employer of Victim 88

65 Other-Non-Relative 88

28 Unknown 99

78 Unknown 99



2.2.7 Race-Ethnicity Matrix

The table below maps race fields to possible ethnicities. If a primary race field is not found, the program looks to ethnicity to try and determine

the race if there is a mapping. These fields are contained on the Person Management page, Basic tab, under the race and ethnicity field labels.

Table 1 - Race-Ethnicity Matrix

Race Ethnicity

American Indian/Alaskan Native No Mapping

Asian Asian Indian

Cambodian

Chinese

Hmong

Japanese

Korean

Laotian

Other Southeast Asian

Thai

Vietnamese

Black/African American African American/Black

Native Hawaiian/Other Pacific Islander No Mapping

White No Mapping

Unable to Determine No Mapping

Declined No Mapping



Race Ethnicity

No Mapping Arabic

Cuban

Declined

Eastern European

Filipino

German

Haitian

Hispanic/Latino

Italian

Mexican/Chicano/Mexican American

Other

Puerto Rican

Russian

Unable to Determine

Unknown

Documents

IN03: NCANDS (National Child Abuse and Neglect Data System)centerforchildwelfare.fmhi.usf.edu/kb/FSFN/NCANDS Topic Paper.pdf · IN03: National Child Abuse and Neglect Data System