STATE OF LORIDA · and the family. Nonintegrated view: CPIs and Case Workers currently have a disintegrated view into family history. CPIs and Case Workers must review several files

STATE OF FLORIDA

DEPARTMENT OF CHILDREN & FAMILIES

CHILD PROTECTION TRANSFORMATION PROJECT

REQUIREMENTS DEFINITION DOCUMENT

Florida Department of Children & Families

Child Protection Transformation Project

Requirements Definition Document Page 2 of 70

December 16, 2011 Version: 1.00(Final)

TABLE OF CONTENTS

1. EXECUTIVE SUMMARY................................................................................................................. 4

1.1. INTRODUCTION ................................................................................................................................................. 4

1.2. BUSINESS PROBLEMS ......................................................................................................................................... 4

1.3. STAKEHOLDER ENGAGEMENT .............................................................................................................................. 5

1.4. TRANSFORMATION REQUIREMENTS ...................................................................................................................... 5

2. PROGRAM OVERVIEW .................................................................................................................. 8

2.1. CHILD PROTECTIVE INVESTIGATIONS ................................................................................................................... 10

2.2. CASE MANAGEMENT SERVICES THROUGH COMMUNITY BASED CARE ORGANIZATIONS ................................................. 11

2.3. SERVICE DELIVERY MODEL ................................................................................................................................ 12

2.4. BUSINESS PROBLEMS ....................................................................................................................................... 13

3. CURRENT TECHNOLOGY ENVIRONMENT ........................................................................... 15

3.1. CURRENT SYSTEMS THAT SUPPORT CHILD PROTECTION SERVICE DELIVERY ................................................................. 15

3.2. CURRENT SYSTEM TECHNOLOGY ........................................................................................................................ 19

3.2.1 Current System Resource Requirements ................................................................................................ 26

4. FUTURE STATE ENVIRONMENT .............................................................................................. 28

4.1. SACWIS COMPLIANCE AND FSFN ENHANCEMENTS .............................................................................................. 28

4.2. MOBILE DEVICES AND APPLICATIONS .................................................................................................................. 30

4.3. DOCUMENT MANAGEMENT .............................................................................................................................. 32

4.4. DATA EXCHANGE INTERFACES WITH OTHER AGENCIES ............................................................................................. 32

4.5. DATA ANALYTICS AND ALERTS ........................................................................................................................... 33

4.6. PERFORMANCE MANAGEMENT AND DASHBOARDS ................................................................................................ 34

4.6.1 Architecture of Proposed Solution ......................................................................................................... 37

5. CHILD PROTECTION TRANSFORMATION REQUIREMENTS .......................................... 39

5.1. ASSUMPTIONS ................................................................................................................................................ 64

APPENDIX - A: STANDARD FORMS .................................................................................................. 65

APPENDIX - B: LEGAL FORMS .......................................................................................................... 68

LIST OF FIGURES

FIGURE 1 – DCF REGIONAL , CIRCUIT AND COUNTY DELINEATION ............................................................ 9

FIGURE 2 – CHILD PROTECTION SERVICE DELIVERY MODEL .................................................................... 12

FIGURE 3 – CURRENT TECHNOLOGY FUNCTIONAL OVERVIEW .................................................................. 15

FIGURE 4 – CURRENT TECHNOLOGY FUNCTIONAL DETAIL ....................................................................... 18

FIGURE 5 – CURRENT TECHNOLOGY CONCEPTUAL ARCHITECTURE .......................................................... 19





FIGURE 6 – CURRENT TECHNOLOGY TECHNICAL ARCHITECTURE ............................................................. 22

FIGURE 7 – FUTURE TECHNOLOGY FUNCTIONAL VIEW ............................................................................. 35

FIGURE 8 – FUTURE TECHNOLOGY DETAILED FUNCTIONAL VIEW ............................................................ 36

FIGURE 9 – FUTURE TECHNOLOGY CONCEPTUAL ARCHITECTURE ............................................................ 37

FIGURE 10 – FUTURE TECHNOLOGY TECHNICAL ARCHITECTURE ............................................................. 38

LIST OF EXHIBITS

TABLE 1 – CURRENT TECHNOLOGY FUNCTIONAL DETAIL – CPI USE ....................................................... 15

TABLE 2 – CURRENT TECHNOLOGY FUNCTIONAL DETAIL – CBC USE ...................................................... 16

TABLE 3 – CURRENT TECHNOLOGY CONCEPTUAL ARCHITECTURE – CPI USE ......................................... 19

TABLE 4 – CURRENT TECHNOLOGY CONCEPTUAL ARCHITECTURE – CBC USE ........................................ 20

TABLE 5 – DCF/CBC MOBILE APPLICATION DEVELOPMENT HISTORY ..................................................... 21

TABLE 6 – CURRENT TECHNOLOGY TECHNICAL ARCHITECTURE – CPI USE ............................................. 22

TABLE 7 – CURRENT TECHNOLOGY TECHNICAL ARCHITECTURE – CBC USE ........................................... 23

TABLE 8 – CURRENT TECHNOLOGY TECHNICAL ARCHITECTURE – FSFN STATISTICS DETAIL ................ 23

TABLE 9 – CURRENT TECHNOLOGY TECHNICAL ARCHITECTURE – FSFN INTERFACES DETAIL ............... 24

TABLE 10 – CURRENT TECHNOLOGY TECHNICAL ARCHITECTURE – FSFN TIERS AND SOFTWARE DETAIL

............................................................................................................................................................ 24

TABLE 11 – CURRENT SYSTEM RESOURCES ............................................................................................... 26

TABLE 12 – FSFN MAINTENANCE & OPERATIONS SUPPORT TEAM OVERVIEW ......................................... 26

TABLE 13 – BUSINESS PROBLEMS AND SOLUTIONS.................................................................................... 28

TABLE 14 – MOBILE TECHNOLOGY CAPABILITIES AND APPLICATIONS ..................................................... 30

TABLE 15 – DATA EXCHANGE INTERFACES WITH OTHER AGENCIES......................................................... 32

TABLE 16 – REQUIREMENTS MATRIX ......................................................................................................... 40





1. EXECUTIVE SUMMARY

1.1. INTRODUCTION

The Florida Department of Children and Families (DCF) is charged with administering the child welfare

program throughout the State, with community-based care lead agencies and certain sheriff’s offices. The

DCF acts as an important safety net for Florida’s most vulnerable children. To keep children safe, prevent

further re-abuse and address underlying conditions contributing to or causing harm. DCF provides a

spectrum of services, from in-home supervision services to referrals for parenting classes, and child care,

to foster care placement in a licensed setting or placement with a non-licensed relative or non-relative.

1.2. BUSINESS PROBLEMS

Problems with the current DCF Child Protection environment include the following.

Limited access to data in the field: Child Protective Investigators (CPIs) and Case Workers do

not have full access to data from critical systems in the field, inhibiting their ability to make better

informed decisions when working with vulnerable children and families.

Duplicate and inefficient data entry: CPIs and Case Workers spend a significant amount of

their time transcribing and entering data into the current Florida Safe Families Network (FSFN)

system. Inefficiencies in the FSFN system force CPIs and Case Workers to re-enter the same data

in and between different modules within the system.

Process inefficiencies (travel to and from): Several process inefficiencies are introduced into

the child protection program as critical data is not available to the CPIs and Case Workers during

their field work. CPIs and Case Workers need to make multiple trips to their offices everyday to

read case history, gather background information, enter case notes and conduct other activities.

Limited data: While there is limited access to system data in the field, CPIs and Case Workers

have limited access to critical data even when they are in the office. The FSFN system does not

have interfaces with critical partners such as Medicaid, the Department of Education, the

Department of Health and the Department of Juvenile Justice to obtain a holistic view of the child

and the family.

Nonintegrated view: CPIs and Case Workers currently have a disintegrated view into family

history. CPIs and Case Workers must review several files (paper and electronic) to understand the

complete picture of the family, child, investigation and Case.

Unstructured data: CPIs and Case Workers do not have a structured view even into the data that

is currently available. The data must be organized and presented in a usable and readable manner

(e.g. Family, Person, Investigation, and Case).





Performance Metrics not available: CPIs and Case Workers are challenged to manage their

workload and yet DCF management cannot get an “at-a-glance” view into practice and operations

performance metrics due to the limitations of the current FSFN system.

No document management capability: Currently CPIs and Case Workers produce, file and

archive at least 80 pages of documents per Case. The filing cabinet feature in FSFN cannot

support the needs of the CPIs and Case Workers. The FSFN system attaches all documents at the

Case level and does not provide the ability to classify documents. CPIs and Case Workers must

open and review all documents to find the correct document.

Lack of meaningful alerts: The FSFN system does not provide meaningful alerts to the CPIs,

Case Workers and management on critical events and data changes in a family’s record. Even

though there are many alerts in the current system, they are not based on an analysis of data from

partner organizations such as Medicaid, the Department of Juvenile Justice, the Department of

Education, the Department of Health, Department of Corrections, etc.

1.3. STAKEHOLDER ENGAGEMENT

The project team engaged with key stakeholders and external partners in several ways to discuss and

document the requirements, including:

Several ride-alongs with CPI(s) in multiple counties to understand the current business processes,

existing technology usage, business needs and technology needs.

Two days of meetings with CBCs and service providers to understand the current business

processes, existing technology usage, business needs and technology needs.

Several meetings with key business users and stakeholders to understand the current business


A three day Business Process Redesign session with CPIs, CPIs supervisors, Case Workers,

Children’s Legal Services attorneys, and key stakeholders and external partners from throughout

the State including local law enforcement and service providers representing substance abuse,

mental health and domestic violence.

1.4. TRANSFORMATION REQUIREMENTS

The project team identified and documented 323 specific requirements for the Child Protection

Transformation project across eight key areas:

Statewide Automated Child Welfare Information System (SACWIS) Compliance Changes:

The federal Department of Health and Human Services Administration for Children and Families,

Children’s Bureau completed a SACWIS compliance assessment in 2011. Thirty-nine items were

identified as either “conditional” or “negative.” Many of these items are addressed outside the

Child Protection Transformation Project. The remaining items will be addressed in the Child

Protection Transformation project.





FSFN Enhancements: Modifications to FSFN are required to support the programmatic changes

envisioned by the Child Welfare Transformation project.

Mobile Devices: Mobile devices with a capability to access critical data in the field would

enhance both the effectiveness and efficiency of CPI tasks. The project would procure up-to-date

mobile devices for CPIs and their supervisors.

Mobile Applications: Mobile applications help enable CPIs and Case Workers to access FSFN,

outside data, performance reporting, Case status and many other important aspects of managing

investigations and Cases while in the field. Some of the features and functions of mobile

applications include:

Forms to be signed by parents/caregivers

Case Notes/ Chronological notes

Emergency placements

Initial and Updated Child Safety Assessments

Safety Planning

Pre-Commencement Face Sheet (summary of past history)

Summary of Case

Referral forms- substance abuse/mental health/domestic violence

Case History Details

Search

Case file (equivalent paper file)

Upload pictures

Ability to contact supervisor

Unified Home Study

Emergency Intake Form (information about the child’s doctor, medical contact, medication

and/or mental health history, allergies, etc.)

Data Exchanges with other agencies: DCF is proposing to build data exchange interfaces with

17 external partner systems (located in Table 15) to gather a variety of additional information to

support the child protection decision making and business processes.

Data Analytics and Alerts: The data gathered from external partners would be analyzed and

meaningful alerts would be generated. Data analytics and alerts would provide better decision

support for CPIs and Case Workers– enabling them to make better use of available data about

children and families. Alerts could be presented at three levels: simple alerts such as when

something exceeds a time limit; complex alerts such as a pre-determined set of relationship





between data (i.e. a number of emergency room visits along with an arrest for a violent crime);

and potentiality alerts based on a rules engine that identifies relationships in the data that

programs might not have anticipated.

Document Management: Improved document management functionality would:

Provide an ability to upload and attach documents at Case, family, person, and provider levels

or a combination thereof.

Capture documents electronically in the field.

Scan documents that must originate as a paper file.

Index documents to make the repository searchable.

Performance Management and Dashboards: DCF would develop a dashboard at two levels.

The first level is for CPIs and Case Workers, presenting current case and performance status

through the new user screens described above. This dashboard might be the home page for CPIs

and Case Workers – it is their life line to managing progress of their cases, identifying sudden

changes in a case, and following performance metrics. The second dashboard level is a new tool

providing management a window into practice and operating performance. This tool would

reflect the metrics by which DCF manages CPIs, CBCs and Case Workers.

The proposed Child Protection Transformation project goes beyond “stop gap” fixes to Florida’s current

child protection problems, to building permanent improvements to enhance child safety resulting in

stronger families, safer children and saved lives.

The remainder of this document provides programmatic background, a discussion of the current

technology environment, an envisioned future state environment, and high level technology requirements.





2. PROGRAM OVERVIEW

The Child Welfare Program Office (Office) works in partnership with six regions, 20 community-based

care (CBC) lead agencies and seven sheriff’s offices to develop and oversee policy and practice

requirements for child protective investigations and case management services. The Office is responsible

for complying with state and federal reporting requirements linked to financial awards and performance

expectations. All contracts with the CBC lead agencies are developed and monitored by the Office. In

addition, the Office manages contracts with Healthy Families Florida, One Church One Child, the

University of South Florida (website and training standards, Title IV-E Waiver Evaluation), Florida

International University (professional child welfare training curriculum development), the Florida State

University Visitation Clearinghouse and others.

The Child Welfare Program Office is the central programmatic knowledge repository for services that

support safe and stable families, including providing protection and permanent families to children and

monitoring the safety and well-being of children. To maintain the funding for these services, the Office

engages in activities and develops products that support compliance with federal and state law. The

Office also works closely with the CBC agencies to develop policy for their lead and subcontracted

agency services.

Office responsibilities to support federal and state requirements include:

Mandated annual reporting of the Federal Child and Family Services Plan

On-going statewide agency rule development and oversight of the child welfare system

Federal Child and Family Services Reviews that link performance with funding

Adoption and Foster Care Analysis and Reporting System (AFCARS), National Child Abuse and

Neglect Data System (NCANDS), and National Youth in Transition Database (NYTD) federal

data reporting

Federal funds though Title IV-E that are allocated to lead agencies and are periodically audited to

include:

Coordination of annual state Auditor General audits of IV-E eligibility

Coordination of periodic federal reviews of IV-E eligibility

Coordination and reporting on the federally mandated improvement; and plans resulting from

the IV-E eligibility reviews

Figure 1 represents the delineation of each of the Department’s six regions and the 20 circuits therein,

which align with each of the 20 Judicial Circuits within the state.





Figure 1 – DCF Regional , Circuit and County Delineation





2.1. CHILD PROTECTIVE INVESTIGATIONS

In Florida, DCF conducts child protective investigations in 60 of the 67 counties employing

approximately 1,075 Child Protective Investigators (CPIs). Seven Sheriffs’ offices perform child

protective investigations under grant agreements with the Department in the remaining seven counties:

Broward, Citrus, Hillsborough, Manatee, Pasco, Pinellas, and Seminole. The seven Sheriffs’ offices

employ approximately 380 CPIs.

CPIs are responsible for conducting two types of child protective investigations when an alleged instance

of abuse or neglect occurs: 1) in-home investigations for a child residing with their parent or other legal

custodian, and 2) institutional investigations involving a child who is temporarily located at a facility,

child care program, school, foster home, or other institution.

In addition, CPIs respond to Special Conditions referrals which do not meet the statutory definition of

abuse, neglect or exploitation, but the circumstances are such that without intervention, abuse, neglect or

exploitation is likely to occur. Special Conditions referrals are further divided into the categories of Parent

Needs Assistance, Child-on-Child Sexual Abuse, Foster Care Referral and Parent/Caregiver Unavailable

(Deceased, Hospitalized, Incarcerated)

In Fiscal Year 2010-2011, CPI staff conducted 184,121 protective investigations (initials and additional,

excluding duplicate and no jurisdiction reports. During the course of an investigation, the primary role of

the CPI is to assess the safety of child(ren) in the household and to identify who is responsible for the

alleged abuse or neglect and to arrange for services or resources to address the underlying conditions

contributing to the maltreatment.

Specifically, DCF and the sheriffs’ offices:

Investigate all reports of child abuse, neglect and exploitation and respond to Special Conditions

Referrals

Respond to out-of-town or out-of-state inquires or requests pertaining to alleged child abuse,

neglect or exploitation

Provide availability of child protective investigations 24 hours a day, seven days a week

Commence investigations within 24 hours of report receipt (2 hours for immediate)

Complete investigations within 60 days

Use the Department’s decision support tools for investigators

Complete the paperwork necessary to determine a child’s eligibility for Temporary Assistance for

Needy Families (TANF) funding and determine Native American/Alaskan Native affiliation

pursuant to the Indian Child Welfare Act (ICWA)

Provide testimony and support to enable judicial or administrative hearings

Conduct supervisory reviews of cases within established timeframes





Comply with legislative performance measures and standards

Document and maintain a master record of investigative and case management activities utilizing

the SACWIS system - the Florida Safe Families Network (FSFN).

2.2. CASE MANAGEMENT SERVICES THROUGH COMMUNITY BASED

CARE ORGANIZATIONS

In 1998 the Florida Legislature mandated the outsourcing of child welfare services to community based

care (CBC) lead agencies. The intent of the legislation was to strengthen and garner the support and

commitment of local communities toward the “reunification of families and care of children and their

families.” Under this service delivery model, lead agencies are responsible for providing foster care and

related services including prevention and diversion, family preservation, emergency shelter, in-home non-

court ordered case management, out-of-home care and case management, independent living services, and

adoption. Most lead CBCs procure subcontractors for case management and direct care services to

children and their families. This service delivery model allows local CBC lead agencies to engage

community stakeholders in designing their local model of care and to develop and maintain a service

delivery network within their service area that meets local needs. The Department maintains

responsibility for program oversight, operating the Abuse Hotline, conducting child protective

investigations (except in the seven counties as previously noted, above) and providing legal representation

in court proceedings.

The twenty CBCs have created, designed, and implemented intervention strategies demonstrating

potential promising practices that could help improve the safety, permanency and well-being of Florida’s

children. Because of the decentralization of the service delivery system, the Florida CBC services

continuum is quite diverse, providing an opportunity for DCF and its partners to assess, share and select

the best and most innovative practices for implementation.

Florida uses a family centered case planning process to help ensure the involvement and participation of

family members in case planning, so services are tailored to best address the family's needs and strengths.

It includes the family members' recommendations regarding the types of services that will be most helpful

to them, timelines for achieving the plan, and expected outcomes for the child and family. Case planning

requires frequent updates based on the Case Worker’s and family's assessment of progress toward goals.





2.3. SERVICE DELIVERY MODEL

The business of delivering child protection services is complex, constantly evolving, and is accomplished

primarily through different delivery models (Figure 2).

Figure 2 – Child Protection Service Delivery Model

DCF performs child protective investigations in 60 counties statewide through its organizational structure,

which includes regional directors, circuit community development administrators, operational program

administrators/program operations administrators, CPI supervisors and CPI units. Sheriffs’ offices

perform child protective investigations under grant agreements with DCF in the remaining seven counties.

Sheriff’s Offices administer the child protective investigations function either as a separate division or a

bureau within their investigations division. These units are supported and supervised by a combination of

civilian (non-sworn) and sworn law enforcement personnel in most of the sheriffs’ offices, although the

Pasco County child protective investigation unit is staffed and operated solely by civilian personnel. CPIs

and their immediate supervisors are civilian personnel in all seven counties.

Florida Legislature Department of

Children and Families

Hotline DCF Investigators CBC’s Florida Children

and Adults

Sheriff’s Office

Investigators

(7 Counties –

contracted by DCF)

Statutes

Laws

Funding

Monitoring

Florida Abuse

Hotline

ACCESS Florida

Prevention Services

Children, Youth, and Family Services

Substance Abuse and

Mental Health Services

Call Floor Unit

Diligent Search

Unit

Criminal Intelligence Unit

Quality Assurance

Unit

System Management/ Data

Unit

Receiving Unit

Child Protection

Investigators

Adult Protection Investigators

Counseling

Educating

Supervising

Therapy

Tutoring





2.4. BUSINESS PROBLEMS

Problems with the current DCF Child Protection environment include the following.

Limited access to data in the field: Child Protective Investigators (CPIs) and Case Workers do

not have full access to data from critical systems in the field, inhibiting their ability to make better

informed decisions when working with vulnerable children and families.

Duplicate and inefficient data entry: CPIs and Case Workers spend significant amount of their

time transcribing and entering data into the current FSFN system. Inefficiencies in the FSFN

system force CPIs and Case Workers to re-enter the same data in and between different modules

within the system.

Process inefficiencies (travel to and from): Several process inefficiencies are introduced into

the child protection program as critical data is not available to the CPIs and Case Workers during

their field work. CPIs and Case Workers need to make multiple trips to their office everyday to

read case history, gather background information, and enter case notes and conduct other

activities.

Limited data: While there is limited access to system data in the field, CPI and Case Workers

have limited access to critical data even when they are in the office. The FSFN system does not

have interfaces with critical partners such as Medicaid, the Department of Education, the

Department of Health, and the Department of Juvenile Justice to obtain a holistic view of the

child and the family.

Nonintegrated view: CPIs and Case Workers currently have a disintegrated view into family

history. CPIs and Case Workers must review several files (paper and electronic) to understand the

complete picture of the family, child, case and investigation.

Unstructured data: CPIs and Case Workers do not have a structured view even into the data that

is currently available. The data must be organized and presented in a usable and readable manner

(e.g. Family, Person, Investigation and Case).

Performance Metrics not available: CPIs and Case Workers are challenged to manage their

workload and DCF management cannot get an “at-a-glance” view into practice and operations

performance metrics due to the limitations of the current FSFN system.

No document management capability: Currently CPIs and Case Workers produce, file and

archive at least 80 pages of documents per Case. The filing cabinet feature in FSFN cannot

support the needs of the CPIs and Case Workers. The FSFN system attaches all documents at the

case level and does not provide the ability to classify documents. CPIs and Case Workers must

open and review all documents to find the correct document.

Lack of meaningful alerts: The FSFN system does not provide meaningful alerts to the CPIs,

Case Workers and management on critical events and data changes in a family’s record. Even

though, there are many alerts in the current system, they are not based on an analysis of data from





partner organizations such as Medicaid, the Department of Juvenile Justice, the Department of

Education, the Department of Health and the Department of Corrections, etc.





3. CURRENT TECHNOLOGY ENVIRONMENT

3.1. CURRENT SYSTEMS THAT SUPPORT CHILD PROTECTION

SERVICE DELIVERY

The CPI and CBC technology environment involves a complex set of interactions between people and

disparate technology systems using separately configured devices in the field. Figure 3 provides a

systems level functional overview of the current technology system utilized by the CPIs and Case

Workers.

Figure 3 – Current Technology Functional Overview

Table 1 – Current Technology Functional Detail – CPI Use

System How Utilized

FSFN CPIs access FSFN to view work queues, assignments, on-call schedules,

historical and current Case information and abuse reports; complete assessments

and plans; download forms for review and/or signature; request child welfare

services; enter case notes; document child placements; update and maintain the

person/Case/provider record (demographic information, medical, mental health,

education); conduct person/Case/provider information, and upload documents

and child abuse/neglect photographic evidence and child identity photographs to

the File Cabinet located within the system. Federally mandated reports

(Adoptions and Foster Care Analysis and Reporting System- AFCARS,

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

Youth in Transition Database- (NYTD) are based on case management

information.

phoeniX Online/CIU

Document

CPIs access phoeniX Online through FSFN to view state and federal criminal

records information which has been authorized and released to DCF by the

Florida Department of Law Enforcement (FDLE) and the Federal Bureau of

CP

IC

AS

E

WO

RK

ER

FSFN phoeniX

Online

Criminal

Intelligence

Unit (CIU)

Document

Management

Judicial

Inquiry

System

(JIS)

Link to

External

Systems

Paper Forms

FSFN CBC Systems

Link to

External

Systems





System How Utilized

Management Investigations (FBI) and posted by the Criminal Intelligence Unit (CIU) and

stored in the CIU Document Management data store.

JIS CPIs with authorized limited security access the Judicial Inquiry System (JIS)

to search, view and print state (jail booking information in Florida and 42 other

states, Florida Clerk of Courts, Florida Driver and Vehicle History, Florida

Department of Juvenile Justice, Florida Department of Corrections) and judicial

data sources for investigations. Currently, information from state and federal

criminal agencies (Florida Crime Information (FCIC) and National Crime

Information Center (NCIC) both traditional and summarized formats, Hot files

(property and person files such as warrants, injunctions, probation statuses and

risk identifications such as felony offender, high risk sexual offender, career

offender, etc,) are only authorized and accessible by the CIU via access to e-

Agent and other databases.

Links to External

Systems

CPIs use links to multiple local (Property Appraiser, County Clerks,

Sheriff/Police Departments, School System), state (ACCESS, Clerk of Courts,

Driver and Vehicle History, Vital Statistics, Florida Crime Information Center )

and federal (National Crime Information Center) data sources for investigation

information about the alleged child victims and siblings, the caregiver allegedly

responsible for the alleged maltreatment of the child, other household members

with access to the alleged child victims and siblings. The information is a subset

of the information collected and analyzed to assess the safety of a child and the

risk of future maltreatment.

Paper Forms CPIs use paper forms or pamphlets such as: the Rights and Responsibilities

pamphlet (statutorily required disclosure associated with each child protection

investigation related to the parents’ rights), Consent and Authorization form for

release of protected health, mental health, and substance abuse information in

accordance with the Health Information Portability and Accountability Act

(HIPAA) a state Waiver of Free Communication Assistance form which is

completed during any investigation associated with the deaf or hard of hearing

population, and (in the event of a child’s removal from his/her home) the federal

Indian Child Welfare Act (ICWA) form which requires that the department

inquire of the child and family any heritage, affiliation, or registration as a

federally recognized Native American/Alaskan Native tribe.

Table 2 – Current Technology Functional Detail – CBC Use

System How Utilized

FSFN CBCs access FSFN to view schedules, assignments, case information and abuse

reports; complete assessments and plans; download forms for review and/or

signature; request child welfare services; enter case notes; document legal

actions and create court reports and other documents, medical information,

education information, child placements and adoptions; upload documents and





System How Utilized

pictures to the File Cabinet; and access financial functionality. Federally

mandated reports (AFCARS, NCANDS and NYTD) are based on ongoing case

management information.

Links to External

Systems

CBCs use links to multiple local (Property Appraiser, County Clerk of Courts,

Sheriff/Police Departments, School System), state (Driver and Vehicle History,

Vital Statistics, Florida Crime Information Center) and federal (National Crime

Information Center) data sources for ongoing case management.

CBC Systems CBCs maintain administrative systems to manage their organization/service

providers, supplement case information (FSFN downloads, document

management - ChildNet, monitor/alerts/reports/dashboards - Mindshare) and

provide mobile device management.

Note: The department does not have “ready” access to any of this information,

which creates a threat to a child’s safety if new information or allegations are

received on a family served under the CBC case management. Given the instant

unavailability of this information, it cannot be used to conduct a comprehensive

or fully accurate assessment of the child and family’s circumstances. All of this

information is statutorily required: furthermore it is a SACWIS requirement, to

be maintained solely in the state’s SACWIS master file/database. Ancillary data

systems are a direct violation of statutory and federal system requirements.

A more detailed functional view is depicted in Figure 4.





Figure 4 – Current Technology Functional Detail

FSFNReceiving Unit List

Investigations

Maintain Case *

Case Assignment *

Child Safety Assessment

Case Notes*

TANF Assessment *

SEARCH

Safety Plan *

Child Care APPN (form) *

Voluntary Protective

Services Agmnt (form) *

Individual Referral form *

Family Referral form *

CPT Exception Report

Closure Letter (to family)

Authorization for release of

Information form *

Medical Mental Health *

Education *

Meetings *

Placement/Services *

Special Conditions

referral*

On Call Schedule

Missing Child Report *

Alert (missing child, foster

care, under investigation) *

Reporting *

Provider Inquiry *

Maintain providers *

Unified Home Study *

Ticklers (sys reminders)*

Automated Messages (sys

gen emails)*

Approvals (supervisory)*

Person Management *

De-Link Intake

Case Split/Merge *

Investigation move*

File Cabinet*

Legal (pre dispo study,

diligent search) *

Paper Forms

Parents Rights ICWA (Indian Child Welfare Act)

FSFN CBC Systems

Family Assessment

Judicial Reviews

Adoption

Independent Living

Case Assignment *

Maintain Case *On Call Schedule

Approvals (supervisory

fn)*


gen emails)*



Person Management *


TANF Assessment *


Meetings *




Reporting *


Investigation move*

Case Notes*



File Cabinet*

Service Referral

Prevention

JR Review Notices

Visitation Plan

Reunification Home Study


Information form *

Special Conditions

referral*


diligent search) *

Education *


Safety Plan *

Case Split/Merge *


Provider Inquiry *

Case Plan

Out of Home Plan


IC PC forms (interstate

compact placement of

Children)De-Link Intake

Statewide Laptop

RDC

ChildNet (CBC

specific)

CBC Specific -

COBRIS

Statewide Mobile

solutions

DCF – Blackberry

Remote Data

Capture

CBC Specific-

MindShare

Mobile Solution

Windows, Android

Statewide ICPC

System

CBC Specific DOC

Mgmt System

CP

IC

as

e M

an

ag

er

phoeniX Online

Background Check Search

Background Check Report

CIU Document Management

Federal Background

Check

State Background Check

JIS (External System)

APPRISS

CCIS

DAVID

DJJ

DOC

Link to External Systems

NCIC

FCIC

CCIS

Access

DAVID

ACCURINT

ASIS

E-Agent

Vital Stats

Waiver of Free Communication AssistanceHIPAA

SHOTS

Property Appraiser Sheriff/Police Dept

SEARCH

Link to External Systems

NCIC

FCIC

CCIS

Access

DAVID

ACCURINT

ASIS

E-Agent

Vital StatsSHOTS

Property

Appraiser

Sheriff/Police

DeptFSFN Downloads

Reporting/Alerts/Monitoring

Invest. Closure Summary

Local Systems of

Case Forms

Child on Child Assessment





3.2. CURRENT SYSTEM TECHNOLOGY

The current DCF technical environment used by both CPIs and CBC caseworkers consists of field

devices, networks, user interfaces, business modules, data stores and external systems. A conceptual

technical view of the DCF technical environment is depicted in Figure 5 and Tables 3 and 4.

Figure 5 – Current Technology Conceptual Architecture

Table 3 – Current Technology Conceptual Architecture – CPI Use

System How Utilized

Devices

CPIs are provided any combination of the following: work stations with a desk

top computer or laptop docking station and monitor and LAN line phone at the

office, laptops and a cell phone or Smartphone. Some CPIs are also assigned

Blackberries and GPS devices.

Networks CPIs connect with the FSFN user interface over the State intranet (Aventail) and

with External Systems over the public internet.

FSFN User Interface CPIs interact with the FSFN business modules, phoeniX application, data

warehouse, and data stores through a common FSFN user interface.

Smart Phone

RDC App

FSFN

Production

Database

FSFN

Data

Warehouse /

Data Mart

CPI CBC

EXTERNAL SYSTEMS

(ACCESSED INDIVIDUALLY)

NCIC

FCIC

CCIS

Access

DAVID

ACCURINT

ASIS

E-AGENT

VITAL STATS

SHOTS

PROPERTY APPRAISER

SHERIFF / PD SYSTEM

FSFN USER INTERFACE

Public Internet

Intranet

Public Internet

FSFN BUSINESS MODULES

INVESTIGATION

ASSESSMENTS

CASE ASSIGNMENTS

Tablet PC

RDC App

Data

Extracts

CBC

Analytics

JIS

CIU

Document

Management

MANAGE PERSON

CASE MANAGEMENT

PLACEMENTS

We

b S

erv

ice

s

Ba

tch

Pro

ce

ss

es Business Objects

Info View

OTHER FUNCTIONALITY





System How Utilized

FSFN Business

Modules

CPIs functionality is delivered through the FSFN business modules.

FSFN Data CPIs access FSFN production data and report from the data warehouse/data

mart.

CBC Interface CPIs do not use the CBC interface.

External Systems CPIs link to multiple local, state and federal data sources for investigative

information.

Table 4 – Current Technology Conceptual Architecture – CBC Use

System How Utilized

Devices CBC caseworkers are provided tablet PCs and Smartphones.

Networks CBCs connect with the FSFN user interface over the State intranet (Aventail)

and with External Systems over the public internet.

User Interfaces CBCs interact with the FSFN business modules, data warehouse, and data stores

through a common FSFN user interface.

FSFN Data

CBCs access FSFN production data, report from the data warehouse/data mart,

and extract case data (CBC extracts) from the data warehouse/data mart to the

CBC data store.

CBC Interface

CBCs maintain administrative systems to manage their organizations and

relationships with the State and other service providers. CBC mobile devices

connect to FSFN through web services.

External Systems CBCs link to multiple local, state and federal data sources for case information.





Mobile devices such as Smartphones and Tablet PCs have been used by CBCs for case management since

2009.

Table 5 – DCF/CBC Mobile Application Development History

Group Device OS App Functionality Note

DCF

Developed

Blackberry

Laptop/Tablet

PC

Blackberry OS

Windows

Case

Management

Children’s

Legal Services

1. See assigned cases

2. Participants in the case

3. Child visit notes

4. Photo and GPS coordinates

5. Upload Pictures

CBC

Developed

(example-

OurKids)

Blackberry

Windows mobile

platform ->

switched to DCF

APP

Case

Management

1. Similar functionality to

DCF App (Sept 2009)

2. Children Legal Services

have their own APP-

Digital Pen (Dec 2010)

CBC

Developed

(example-

ChildNet)

Smartphone

Windows (March

2010) mobile

platform ->

Android (Sept

2011)

Case

Management

1. Present case details

2. Present participant details.

3. Child visit notes, Photo,

GPS, Upload

FSFN is a tiered, web based system using Java programming languages and J2EE framework. IBM DB2

UDB is the database manager. A technical architecture view of the FSFN and its surrounding technical

environment is depicted in the following Figure 6 and Tables 6 and 7.





Figure 6 – Current Technology Technical Architecture

Table 6 – Current Technology Technical Architecture – CPI Use

System How Utilized

Devices CPIs access FSFN through work stations or laptops which are all MS Windows-

based.

Client Tier CPIs MS Windows-based devices use Internet Explorer browser ActiveX

installed to access FSFN.

Presentation Tier CPIs are presented (session state management) FSFN screens based on Java

Server Pages (JSP) with embedded Java Scripts (JS).

Business Tier CPIs use FSFN business logic written in the Java programming language and

supported by Enterprise Java Beans (EJB) as a container for Java programs and

Java Message Services (JMS) for communication between programs.

Data Tier CPIs use FSFN data from an IBM DB2 UDB production database and report

from IBM DB2 UDB data warehouse/data mart.

External Systems CPIs link to external systems from MS Windows browser Internet Explorer.

FSFN

DEVICES

DEVICES

Laptop Computer

Desktop Computer

CPI

Case

Worker PR

ES

EN

TA

TIO

N T

IER

BU

SIN

ES

S T

IER

DA

TA

TIE

R

EX

TE

RN

AL S

YS

TE

MS

(AC

CE

SS

ED

IN

DIV

IDU

AL

LY)

FSFN Business Logic

Session State

Management

Java Message Queues

Data Access Objects

JDBC

FSFN

Data

Warehouse /

Data Mart

FSFN

Production

Database

CCIS

VITAL

STATS

NCIC FCIC JIS

SHOTS E-AGENT

PROPERTY

APPRAISE

R

Presentation Logic

Processing

Enterprise Java BeansJava Script

Java Server

Pages

CLIENT

TIER

Browser

ActiveX

Tablet PC

Case

Worker

CLIENT TIER

Application

Application

FSFN RDC

Smart Phone

Browser

ACCESS

ASIS

ACCURINT

SHERIFF/

POLICE

DEPT

Authentication

Interface Logic

(Florida Interface

Framework)

Web Services (RDC)

Business Objects

Info View

FLORIDA

Production

Database

CIU

Document

Management





Table 7 – Current Technology Technical Architecture – CBC Use

System How Utilized

Devices CBCs access FSFN through work stations or laptops or tablet PCs, all MS

Windows based, and a Blackberry Smartphone.

Client Tier CBCs use MS Windows based devices with Internet Explorer browser and

ActiveX installed to access FSFN. The Blackberry Smartphone based devices

use a custom Blackberry specific app and FSFN RDC web services.

Presentation Tier CBCs are presented (session state management) FSFN screens based on Java

Server Pages (JSP) with embedded Java Script (JS).

Business Tier CBCs use FSFN business logic written in the Java programming language and

supported by Enterprise Java Beans (EJB) as a container for Java programs and

Java Message Services (JMS) for communication between programs.

Data Tier CBCs use FSFN data from an IBM DB2 production database and report using

Business Objects Enterprise (BOE) from IBM DB2 data warehouse/data mart.

Data extracts are downloaded from the FSFN IBM DB2 data warehouse/data

mart to the CBC administrative system. Data from the Blackberry device

updates the FSFN production database using web services.

External Systems CPIs link to external systems from MS Windows browser Internet Explorer.

Table 8 – Current Technology Technical Architecture – FSFN Statistics Detail

Component Name Counts

JSP Pages 1735

Java Script Pages 832

Java Batches 30

Cobol 3

OLTP Tables 445

UDB Tables 1255

CBC Extracts 50

CBC Files 50

Reports 280

Universes 56

DB Views 67

ETLs 150

Autosys Jobs 500





Component Name Counts

Web Services Components 20

Table 9 – Current Technology Technical Architecture – FSFN Interfaces Detail

Interface Name Architecture Complexity Interface

Type

Agency

Interface

Description

Adoption and Foster Care

Analysis and Reporting System

(AFCARS)

Flat File Very Complex FSFN-> Feds Feds Flat file with

AFCARS data to

Feds

Adoption Exchange System (AES) Flat File Moderate FSFN->

Adoption

Website

DCF

(internal)

Data to support

Adoption web

site

Community Based Care (CBC)

Fiscal Agency Accounting System Flat File Very Complex FSFN -> CBC CBC’s Daily Extracts to

CBCs

Child Support Enforcement (CSE) Flat File Very Complex FSFN <->

CAMS

DOR Data exchange to

Child Support

Department of Health (DOH) Flat File Moderate DOH -> FSFN DOH Data extract from

DOH

Missing Children Tracking

System (MCTS)- Florida

Department of Law Enforcement

(FDLE) Link

Web service/Servlet Moderate FSFN <-> FDLE FDLE Data transfer to

FDLE for

Missing Child

System

Florida Online Recipient

Integrated Data Access

(FLORIDA) System

FLORIDA

framework

Very Complex FSFN <->

FLORIDA

DCF

(internal)

Data exchange

for child

eligibility

calculation

Hotline phoeniX System Web service/Servlet Complex FSFN <->

phoeniX

DCF

(internal)

Data exchanges

to Hotline

applications

National Child Abuse and Neglect

Data System (NCANDS) Flat File Complex FSFN ->Feds Feds Data extract to

Feds

Department of Children and

Families (DCF) Data Extract Moderate FSFN ->

Dashboards

DCF

(internal)

Data extract to

Dashboard

National Youth in Transition

Database (NYTD) Data Flat File Complex FSFN ->Cb25

5 points<->

FSFN

Connected

By25 and 5

Points

Data exchanges

to Connected

By25

National Youth in Transition

Database (NYTD) Flat File Complex FSFN -> Feds Feds Data extract to

Feds

Remote Data Capture (RDC)-

Mobility Applications Web services Very Complex FSFN<-> RDC DCF

(internal)

Data exchange to

support Mobility

applications

Checkprint/Checkwrite-Financials Flat File/Web

services

Moderate FSFN <-> CBS DCF

(internal)

Data exchange to

CBC’s for

financial data

Table 10 – Current Technology Technical Architecture – FSFN Tiers and Software Detail

Tier Hardware/Software Requirement/Configuration





Tier Hardware/Software Requirement/Configuration

Client Tier Microsoft Internet Explorer (version between 5.5 and 8.0)

Microsoft Word 97 through Word 2010

Microsoft Excel

Java Script

Word Processing ActiveX component installed

FSFN customized Word template

Application Tier 3 Linux Redhat 5 servers in a clustered configuration

RadWare Network Appliance balancing the workload with session affinity and

failover support

Each Linux Server hosts 10 BEA WebLogic 9.2.3 J2EE Application Server

Instances on two servers

28 Application Server Instances are configured in a single cluster with session

replication to support failover

Auditing/Messaging

Tier

FSFN JMS message servers handle background interface processing with the

FLORIDA online IMS system and Audit logging in FSFN

The JMS message servers are configured as a distributed queue spanning

WebLogic 9.2.3 application servers

Database Tier The FSFN database tier consists of a middle-tier component in addition to the

z/OS DB2.8.1.

The middle-tier component of the FSFN on-line database is hosted on DB2 UDB

9.5 running on Linux Redhat 5

Reporting Tier The FSFN reporting tier consists of a cluster Business Objects Enterprise (BOE)

XI R2 servers.

FSFN application is integrated with the BOE web based infoView platform

through a single sign-on.

The reporting tier data base is hosted on DB2 UDB 9.5 running on Linux Redhat

5





3.2.1 Current System Resource Requirements

CPIs and CBCs utilize five main State system resources:

FSFN

The phoeniX Online/CIU Document Management

Mobile Phones

Laptop PCs

Tablet PCs

The components of these resources are listed below.

Table 11 – Current System Resources

System Accessibility Usage Hardware

Platform

Software

Platform

Database

Platform

Program

Languages

FSFN

Hotline, CPIs,

CBCs

5,900

unique users

per day

HP Dual Core

Intel Xeon

3GHZ, HP Dual

Core AMD

Opteron 3GHZ,

IBM

Mainframe

J2EE, Linux

Redhat 5, BOE

XIR2, Web

Logic Linux,

zOS

DB2 UDB

9.5 on

mainframe

Java,

Cobol

phoeniX online Hotline, CPI,

CBCs

IIS 6.0 server .net web app EMC

Documentum

C#, VB

Smartphones CBCs 650 Blackberry Blackberry OS

Laptops/Tablet

PCs

CBCs 2,000 Dell ATG

Laptop, Dell

XT2 Tablet,

Panasonic

Tablet

Windows XP

These system resources are supported by a team comprised of 36 total staff members located at the

Northwood complex. Table 12 depicts FSFN support staff, their roles and skill sets.

Table 12 – FSFN Maintenance & Operations support team overview

People Role Number of Staff Skill Set

FSFN Support

Developer

1 (Full Time

Employee-FTE)

14 (Contractors)

J2EE/Java, BOE, Mainframe Cobol

BA 5 (Contractors) Business Analysis, FSFN Functional Knowledge

Production Support 2 (FTE) FSFN Functional Knowledge





People Role Number of Staff Skill Set

5 (Contractors)

QA 1 (FTE)

3 (Contractors) Testing, FSFN Functional Knowledge

Manager 5 (FTE) Program, Technical, QA, Production Support

and Business Analysis Management

Total 36





4. FUTURE STATE ENVIRONMENT

The future state environment is envisioned to solve most of the problems with the current technology

used for child protection. Table 13 provides a snapshot of problems and proposed solutions.

Table 13 – Business Problems and Solutions

Problems (Current State) Solution (Future State)

Limited access to data in the field Real time access to data using mobile applications

Duplicate/inefficient data entry Mobile Application (Voice, Digitizer Pen, Soft Keyboard)

Simplified User Interface

Process inefficiencies (travel to and from) Cases on the Mobile Device

Limited data Data exchanges with several other entities.

Comprehensive history from existing and new sources.

Nonintegrated view A complete picture of the family, child, investigation and

case (e.g. Family Genogram)

Unstructured data Data organized and presented in a usable and readable

manner (e.g. Family, Person, Investigation, Case)

Performance Metrics not available New Performance Dashboards and Reporting.

No document management capability Document Management solution

No meaningful alerts Data Analytics and Alerts based on data from other

Agencies.

The proposed solution includes the following components:

4.1. SACWIS COMPLIANCE AND FSFN ENHANCEMENTS

The FSFN enhancements would help DCF achieve SACWIS compliance, and also provide important new

functionality.

A Federal Department of Health and Human Services compliance assessment was completed in

September 2011. Thirty-nine items were identified as either “conditional” or “negative.” Many

of these items are addressed outside the Child Protection Transformation Project. The remaining

items will be addressed in the Child Protection Transformation project.

FSFN enhancements will do more than achieve federal compliance – they would provide useful

capabilities for the CPI and Case Worker. At their core, FSFN enhancements would create a new

user interface to the FSFN. They would create a new method for accessing FSFN data based on

the flexible tools of the Internet. FSFN enhancements would add four fundamental types of





functionality. First, they would create a new method of accessing data. Alternatively called “face

sheet” or “at-a-glance”, CPIs and Case Workers need to see the whole picture of a child and the

family. FSFN enhancements would enable users to view a child’s history in the system, as well

as the whole family including members that have “come and gone” over time. This is important,

since child abuse happens in the context of an ever-changing and often dynamic household

setting.

FSFN enhancements would facilitate field access through various technology platforms, such as

tablets. Today, FSFN is presented in screens that can only be viewed through certain older

version of Internet Explorer. This is because FSFN was originally designed and developed in

another state long before web access was a standard. FSFN enhancements would change the

technology behind presenting the information on a screen, enabling FSFN to be viewed through

iPads, Android devices (Smartphones) or browsers other than Internet Explorer. This would open

up a host of new ways of using and sharing FSFN across the child protection stakeholders.

Modifications to FSFN are required to support the programmatic changes envisioned by the Child

Protection Transformation project. Some of the significant enhancements include:

Child Safety Assessment Tool

Case Plan

Safety Planning

Family Assessment Tool

Judicial Review Tool

Unified Home Study

Re-unification Home Study

Out of Home plan

Visitation Plan

Investigation Closure Summary

Pre-Commencement At a Glance view

Reduce duplicative data entry in case notes

Advanced search

Medical/Mental Health and Education modules

Voluntary Protective Services Agreement form

Child on Child Sexual Abuse Referral template

FSFN enhancements would facilitate new FSFN functions and features. For example,

investigation and case management field workers would be supported with:





Remote access to case information

Ongoing records check capacity

Automated data sharing with stakeholders

Continuous reporting on child safety and well being

Accountability and performance metrics

All services input into electronic case file including prevention, diversion and Family

Preservation cases

Dispatch that is properly prioritized

Standardized and automated child safety assessment

Access to services that can be provided immediately upon contact

Ability to record services into electronic case file

FSFN enhancements would create an environment of interoperability with CBCs and other

stakeholders. Today, many CBCs maintain separate operation-support systems because FSFN

does not provide fully for their document imaging and other needs. FSFN enhancements would

allow Case Workers to make better use of their existing technology while moving to full reliance

on FSFN as the single record for every case. Likewise, FSFN enhancements would improve

access for members of the judiciary and other stakeholders.

4.2. MOBILE DEVICES AND APPLICATIONS

Mobile devices can be leveraged to provide real time access to case data within the field. Table 14

provides a list of mobile technologies, capabilities and application across child protection business

processes.

Table 14 – Mobile Technology Capabilities and Applications

Mobile Capability

Investigative

Workflow

Mobile Technology

Pre

-

Co

mm

ence

men

t

Co

mm

ence

men

t

Det

erm

ina

tio

n

Dis

po

siti

on

Cel

l P

ho

ne

Sm

art

ph

on

e

Wir

eles

s T

ab

let

Wir

eles

s T

ab

let

PC

Wir

eles

s L

ap

top

Voice Call

Text Message





Mobile Capability

Investigative

Workflow

Mobile Technology

Pre

-

Co

mm

ence

men

t

Co

mm

ence

men

t

Det

erm

ina

tio

n

Dis

po

siti

on

Cel

l P

ho

ne

Sm

art

ph

on

e

Wir

eles

s T

ab

let

Wir

eles

s T

ab

let

PC

Wir

eles

s L

ap

top

Instant Message

Email

Video Conferencing

Wiki/Blog Discussion

Events and Alerts

Internet Access for Research

Contact Manager

Calculator

GPS Mapping and Routing

GPS Mileage Tracking

GPS Location and Time Tracking

Voice Recording

Video Recording

Speech to Text Capture

Picture Capture

Document Capture

Fingerprint Capture

FSFN Remote Data Capture

Interface

Document Management System

Interface

Case List

Case Display

Case History

Document Display

Assessments

Emergency Intake

Plans

Case Notes

Forms

Signature Capture

Remotely Wipe Data





New system capabilities would be necessary to link mobile devices and FSFN so that CPIs and Case

Workers can use any variety of devices to access FSFN, outside data, performance reporting, case status

and the other important aspects of managing investigations, cases, and their workday. Devices could be

laptops, tablets, tablet computers, or even Smartphones. In addition to system changes (i.e. web services

layer), the Project would procure up-to-date mobile devices for CPIs and their supervisors. In addition to

a mobile device, this could include the tools of a remote office including printer, remote access

connection, and backup batteries – everything a CPI needs to be productive without successive trips back

to the office.

The technology supporting the mobile devices should be platform independent. Thus, as technology

improves the solution would be able to adapt.

4.3. DOCUMENT MANAGEMENT

While FSFN has the ability to store documents as objects, it lacks the capability to link those objects to a

Case, and to index them. The Project would overcome a current situation in which CPIs and Case

Workers produce, file and archive at least 80 pages of documents per case. The solution would allow

most of those documents to be created and signed electronically (screens above and mobile devices

below). Document management would involve three main aspects. The first is the screens developed for

FSFN enhancements. These would include functionality for storing and completing documents on line.

This would alleviate the necessity to ever print many of the documents. The CPI or Case Worker can

complete the document and attach an electronic signature. Second, the document management system

would enable CPIs and Case Workers to capture all documents electronically in the field. The Project

would enable CPIs and Case Workers to capture documents that originate as paper (or have to be printed

and signed). This could be through a portable scanner. Lastly, field workers could capture documents

using their tablet or phone camera. Then, all digital documents will be organized and accessible in a

useful manner by case.

4.4. DATA EXCHANGE INTERFACES WITH OTHER AGENCIES

The Department is proposing to build data exchange interfaces with 17 external systems to gather a

variety of additional information to support the child protection decision making and business processes.

Table 15 – Data Exchange Interfaces with Other Agencies

Interface Purpose

National Crime Information Center (NCIC) Criminal History - Background Checks

Florida Crime Information Center (FCIC) Criminal History - Background Checks

Judicial Inquiry System (JIS) Criminal History - Background Checks

Florida’s public assistance eligibility System

(Access Florida)

Eligibility and history of public assistance provided

Florida’s Driver and Vehicle Information Database Florida driver’s license (DL) information: name,





Interface Purpose

System (DAVID) address, date of birth, valid or not, past DL photos,

citations, and DL activity history – Background

Check – Person Identification

Department of Education (DOE) Education records – attendance, grades, school

changes, address changes

LexisNexis Accurint Background Checks

Adult Services Information System (ASIS) Screened out records

e-Agent National Law Enforcement Telecommunications

System (NLETS) and state Criminal Justice

Information Systems (CJIS) – Criminal History -

Background Checks

Florida Department of Health Vital Stats System Florida birth, death, marriage, divorce and historic

vital records

Florida Department of Health SHOTS system Immunization Records

Florida County Sheriff’s Systems Local Criminal Records – Background Checks,

Call-out information

Florida Department of Juvenile Justice (DJJ) Children under DCF care who are jointly served

Florida Department of Corrections (DOC) Incarceration, Probation and Parole, Criminal

Records – Background Checks

Florida Agency for Health Care Administration

(AHCA)

Medicaid Claims Information

National Child Abuse and Neglect Data System

(NCANDS)

Allegation records in other States - Background

Checks

Florida Department of Health Child Protection

Team Information System (CPTIS)

Medical evaluations, specialized and forensic

interviews, psychological evaluations, and multi

disciplinary team (MDT) staffing information

4.5. DATA ANALYTICS AND ALERTS

Data analytics and alerts would provide better decision support for CPIs and Case Worker – enabling

them to make better use of available data about children and families. The Project would improve

information management in three ways: access, organization and alerts.

It would expand the access CPIs and Case Worker have to data. Today, data is accessed by

calling someone to have them run and print a special report. The CPI and Case Worker need data

from FSFN as well as data from other sources such as law enforcement or schools. Decisions are

not well supported by information today because the pertinent information is difficult to obtain.





The Project would study historical data usage patterns as well as the potential of future data

sources to determine the most useful sources of data. DCF would then create new data exchange

with key data sources such as the Agency for Health Care Administration (AHCA), Department

of Education (DOE), National Child Abuse and Neglect Data System (NCANDS) and the various

judicial and law enforcement agencies.

Data analytics and alerts would help CPIs and Case Workers organize both current FSFN data

and the added data from other agencies. Presently, DCF has more data on each child and family

than CPIs and Case Workers can track and effectively make use of with today’s screen layouts

and functionality. New user screens would present information organized in a manner that is

most useful for making decisions to support families. New screens would structure data

presentation so that the information content is easier to utilize to factor into decisions. New

screens would also provide CPIs and Case Workers the ability to drill into data to explore case-

specific information about children on their caseload.

Data analytics and alerts would build data analysis tools to help CPIs and Case Workers by

electronically tracking data to create alerts. These alerts would help CPIs and Case Workers

identify the information that is most relevant to identifying risk and emerging threat to the child

safety. Alerts would allow CPIs and Case Workers to follow much more data than is possible for

a human to independently obtain, analyze and react to. Alerts might be presented at three levels:

simple alerts such as when something exceeds a time limit; complex alerts such as a pre-

determined set of relationship between data (i.e. a number of ER visits along with an arrest for a

violent crime); and potentiality alerts based on a rules engine that identifies relationships in the

data that programs might not have anticipated.

4.6. PERFORMANCE MANAGEMENT AND DASHBOARDS

DCF would develop a dashboard at two levels. The first level is for CPIs and Case Worker. This

presents current case and performance status through the new user screens described above. This

dashboard should be the home page for CPIs and Case Worker – it is their life line to managing progress

of their cases, identifying sudden and emerging changes in a Case, and following performance metrics.

The second dashboard level is a new tool providing each level of management a window into practice and

operating performance. This tool would reflect the metrics by which DCF manages CPIs, CBCs and Case

Worker.

The dashboards are a crucial element in improving accountability throughout the child protection system.

It would increase visibility at all levels into performance issues and opportunities. Along with creating

the tool, DCF would expand its thinking about performance tracking, introducing new metrics that focus

more directly on child and family outcomes. These would include both quantitative and qualitative

performance metrics.





Figure 7 shows the proposed solution elements. It presents the vision of CPI and case management.

Color coded into the diagram are the years in which the Project would implement the changes (green is

FY 2013 and white is FY 2014).

Figure 7 – Future Technology Functional View

CP

IC

AS

E

WO

RK

ER

phoeniX

OnlineDocument

Management

Data

Exchange

with External

Systems

Performance

Management /

Dashboards

CBC Systems

Data

Exchange

with External

Systems

FSFN

FSFN

Data

Analytics /

Alerts

Mobile

Applications

Year - 1 Year - 2LEGEND No Change





Figure 8 – Future Technology Detailed Functional View

FSFNReceiving Unit List

Investigations

Maintain Case *

Case Assignment *

Child Safety Assessment

Case Notes*

TANF Assessment *

SEARCH

Safety Plan *






CPT Exception Report

Closure Letter (to family)


Information form *


Education *

Meetings *


Special Conditions

referral*

On Call Schedule




Reporting *

Provider Inquiry *





gen emails)*

Approvals (supervisory)*

Person Management *

De-Link Intake

Case Split/Merge *

Investigation move*

File Cabinet*


diligent search) *

FSFN CBC Systems

Family Assessment

Judicial Reviews

Adoption

Independent Living

Case Assignment *

Maintain Case *On Call Schedule

Approvals (supervisory

fn)*


gen emails)*



Person Management *


TANF Assessment *


Meetings *




Reporting *


Investigation move*

Case Notes*



File Cabinet*

Service Referral

Prevention

JR Review Notices

Visitation Plan

Reunification Home Study


Information form *

Special Conditions

referral*


diligent search) *

Education *


Safety Plan *

Case Split/Merge *


Provider Inquiry *

Case Plan

Out of Home Plan


IC PC forms (interstate

compact placement of

Children)De-Link Intake

Statewide Laptop

RDC

ChildNet (CBC

specific)

CBC Specific -

COBRIS

Statewide Mobile

solutions

DCF – Blackberry

Remote Data

Capture

CBC Specific-

MindShare

Mobile Solution

Windows, Android

Statewide ICPC

System

CBC Specific DOC

Mgmt System

CP

IC

as

e M

an

ag

er

phoeniX Online

Background Check Search

Background Check Report

Mobile Application

SEARCH

FSFN Downloads

Reporting/Alerts/Monitoring

Invest. Closure Summary

Child on Child Assessment

Data Exchange with External Systems

NCIC

FCIC

CCIS

Access

DAVID

ACCURINT

ASIS

E-Agent

Vital StatsSHOTSSheriff/Police

Dept

JIS

DOE

AHCA

NCANDS

Performance Management /

Dashboards

Data Analytics/Alerts

Document Management

Mobile Application

Performance Management /

Dashboards


Document Management






4.6.1 Architecture of Proposed Solution

The conceptual and technical architectures which support the proposed solution are depicted in Figure 9.

Figure 9 – Future Technology Conceptual Architecture

Smart Phone

RDC App

FSFN

Production

Database

FSFN

Data

Warehouse /

Data Mart

CPI CBC

FSFN USER INTERFACE

Public Internet

Intranet

Public Internet

FSFN BUSINESS MODULES

Case Management

Data Exchange

Interface

Management

Tablet PC

RDC App

Data

Extracts

CBC

Analytics


Document

Management We

b S

erv

ice

s

Tablet

Mobile App

EX

TE

RN

AL

SY

ST

EM

S NCIC FCIC JIS Access DAVID

VITAL

STATSSHOTSAccurint ASIS E-Agent

DOE AHCA

DJJ

DOCFSFN

Document

Management

Mobile

Device

Management

Sheriff

System

REPORTING

Dashboards

Reporting

Mo

bile

De

vic

e

Ma

na

ge

me

nt

Pro

ce

ss

ing

NCANDS






Figure 10 – Future Technology Technical Architecture

DEVICES

CPI

Case

Worker

PR

ES

EN

TA

TIO

N T

IER

BU

SIN

ES

S T

IER

DA

TA

TIE

R

FSFN Business Logic

Session State

Management

Java Message Queues

Data Access Objects

JDBC

FSFN

Data

Warehouse /

Data Mart

FSFN

Production

Database

Presentation Logic

Processing

Enterprise Java Beans

Java Script

Java Server

Pages

CLIENT

TIER

Browser

ActiveX

Authentication

Interface Logic

(Florida Interface

Framework)

Data Exchange Web

Services

FLORIDA

Production

Database

EX

TE

RN

AL S

YS

TE

MS

NCIC FCIC JIS

Access DAVID

VITAL

STATSSHOTS

Accurint ASIS E-Agent

DOE

AHCADJJ DOC

Sheriff

System

Reporting

User Interface

Mobile App Web

Services

Web Services

DEVICES

Tablet PC

Case

Worker

CLIENT TIER

Application

Application

FSFN RDC

Smart Phone

CPI

DEVICES

Tablet

CLIENT TIER

Applications

User Interface

Validations

Mobile

Device

Management

Mobile Device Management

Processing

NCANDS

Document

Management

Analytics / Alerts






5. CHILD PROTECTION TRANSFORMATION

REQUIREMENTS

The project team engaged with key stakeholders and external partners in several ways to discuss and

document the requirements, including:

Several ride-alongs with CPI(s) in multiple counties to understand the current business processes,

existing technology usage, business needs and technology needs.

Two days of meetings with CBCs and service providers to understand the current business


Several meetings with key business users and stakeholders to understand the current business


A three day Business Process Redesign session with CPIs, CPIs supervisors, Case Workers,

Children’s Legal Services attorneys, and key stakeholders and external partners from throughout

the State including local law enforcement and service providers representing substance abuse,

mental health, and domestic violence.

The project team identified and documented 323 specific requirements for the Child Protection

Transformation project across eight key areas:

SACWIS Compliance Changes

FSFN Enhancements

Mobile Devices

Mobile Applications

Data Exchanges with other agencies

Data Analytics and Alerts

Document Management

Performance Management and Dashboards

Table 16 provides a description of each requirement:





Table 16 – Requirements Matrix

Index Requirement Description Requirement

Type Work Stream

1. The system shall conform to all State/DCF child welfare standards and best

practices for security, usability, performance and reliability. General Applies to All Work Streams

2.

The system integrator shall ensure compliance with all federal/State/DCF

child welfare statutes, policies and requirements during the development of

the solution.

General Applies to All Work Streams

3. The system shall comply with the Americans with Disabilities Act (ADA)

and Section 508 of the Rehabilitation Act of 1973. General Applies to All Work Streams

4. The system shall be developed using industry standard, non-proprietary and

commercially available technologies. General Applies to All Work Streams

5. The system shall display business user oriented error messages upon

exception error handling. General Applies to All Work Streams

6. The system shall include on line context sensitive help. General Applies to All Work Streams

7. The system shall include end user documentation. General Applies to All Work Streams

8. The system shall include technical documentation. General Applies to All Work Streams

9. The mobile device shall provide processing capabilities to adequately

support all operating system and applications’ functions Technical Mobile Devices

10. The mobile device shall provide storage capabilities to adequately support

all operating system, applications’ functions, picture storage, etc. Technical Mobile Devices

11. The mobile device shall provide at least an eight inch color screen display. Technical Mobile Devices

12. The mobile device shall provide brightness settings for the screen. Technical Mobile Devices

13. The mobile device shall provide a touch screen including features such as

swipe and pinch to zoom. Technical Mobile Devices

14. The mobile device shall provide the ability to work with a stylus. Technical Mobile Devices

15. The mobile device shall provide a front facing camera. Technical Mobile Devices






Type Work Stream

16. The mobile device shall provide a rear facing camera. Technical Mobile Devices

17. The mobile device shall allow for wireless internet access via 3G, 4G,

WiMax or a combination thereof. Technical Mobile Devices

18. The mobile device shall support wireless Wi-Fi connectivity. Technical Mobile Devices

19. The mobile device shall allow for wired network access. Technical Mobile Devices

20. The mobile device shall allow for secure network access. Technical Mobile Devices

21. The mobile device shall provide the ability to attach peripherals including

but not limited to a keyboard, mouse, and printer. Technical Mobile Devices

22. The mobile device shall provide the ability to attach an external monitor and

docking station. Technical Mobile Devices

23. The mobile device shall allow display screen privacy. Technical Mobile Devices

24. The mobile device shall provide the capability to attach a headset. Technical Mobile Devices

25. The mobile device shall provide speakers with volume control. Technical Mobile Devices

26. The mobile device shall provide a microphone. Technical Mobile Devices

27. The mobile device shall provide removable storage capabilities including

but not limited to USB port, SD port, and Micro SD port. Technical Mobile Devices

28. The mobile device shall provide GPS capability. Technical Mobile Devices

29. The mobile device shall accommodate everyday use in the field

environment. Technical Mobile Devices

30. The mobile device shall have the ability to fit into a protective case. Technical Mobile Devices

31. The mobile device shall allow users to work in both portrait and landscape

mode. Technical Mobile Devices






Type Work Stream

32. The mobile device shall provide adequate battery life for daily use in a field

environment without recharging. Technical Mobile Devices

33. The mobile device shall provide the capability to charge using a standard

U.S. wall outlet. Technical Mobile Devices

34. The mobile device shall provide the capability to charge using a car charger. Technical Mobile Devices

35. The mobile device shall provide a screen that is clearly readable in both an

indoor and outdoor settings. Technical Mobile Devices

36. The mobile application shall provide a visual layout which takes advantage

of the mobile device screen. Business Mobile Application

37. The mobile application shall provide the capability to receive, store, edit

and send email messages with attachments. Business Mobile Application

38. The mobile application shall provide the capability for individual and group

video/voice conferencing. Business Mobile Application

39. The mobile application shall provide the capability for wiki/blog

discussions. Business Mobile Application

40.

The mobile application shall provide the capability to send an alert to law

enforcement and supervisors with minimal interaction in an emergency

situation.

Business Mobile Application

41. The mobile application shall provide contact manager capability including

but not limited to name, address, phone numbers, email addresses and notes. Business Mobile Application

42. The mobile application shall provide the capability to store one or more

calendars. Business Mobile Application

43. The mobile application shall provide the capability to schedule calendar

appointments. Business Mobile Application

44. The mobile application shall provide numeric business calculator capability. Business Mobile Application

45. The mobile application shall provide the capability to create and store text

on a notepad. Business Mobile Application






Type Work Stream

46. The mobile application shall provide the capability to store and retrieve text

on a notepad. Business Mobile Application

47. The mobile application shall provide the capability to create, edit and store

MS Word documents, Excel workbooks, and PowerPoint presentations. Business Mobile Application

48. The mobile application shall provide file browser capabilities to locate and

read MS Word documents, Excel workbooks, and PowerPoint presentations. Business Mobile Application

49. The mobile application shall provide the capability to convert MS Word

documents to Adobe PDF documents. Business Mobile Application

50. The mobile application shall provide the capability to read Adobe PDF

documents. Business Mobile Application

51.

The mobile application shall provide web browser capabilities which

include but are not limited to forward/back navigation, tabs, favorites, print,

file, and safety functionality.


52. The mobile application shall provide web browser access to native FSFN. Business Mobile Application

53. The mobile application shall provide web browser access to the internet. Business Mobile Application

54. The mobile application shall provide web browser access to the document

management system. Business Mobile Application

55. The mobile application shall accept interactive text and voice commands for

GPS capabilities. Business Mobile Application

56. The mobile application shall provide office, residence and case location

mapping. Business Mobile Application

57. The mobile application shall provide map and direction list routing from a

specified location to one or more case locations. Business Mobile Application

58. The mobile application shall provide mileage tracking and reporting based

on case routing. Business Mobile Application

59. The mobile application shall provide location, time tracking and reporting

based on case routing. Business Mobile Application






Type Work Stream

60. The mobile application shall provide the capability to capture voice

recording and upload to FSFN. Business Mobile Application

61. The mobile application shall provide the capability to capture video

recording and upload to FSFN. Business Mobile Application

62. The mobile application shall provide the capability to capture pictures and

upload to FSFN. Business Mobile Application

63. The mobile application shall provide the capability to capture documents

and upload to FSFN. Business Mobile Application

64. The mobile application shall provide the capability to capture fingerprints

and upload to FSFN. Business Mobile Application

65. The mobile application shall provide the capability to capture electronic

signatures for documents and upload to FSFN. Business Mobile Application

66. The mobile application shall provide the capability to convert speech to

text. Business Mobile Application

67. The mobile application shall provide the capability to convert text to

speech. Business Mobile Application

68. The mobile application shall display case assignments (all, current, active,

etc.) with “drill down” capabilities. Business Mobile Application

69. The mobile application shall display individual and case face sheets with

“drill down” capabilities. Business Mobile Application

70. The mobile application shall display the case history summary with “drill

down” capabilities for notes. Business Mobile Application

71. The mobile application shall display the case related document summary

with “drill down” capabilities for individual documents. Business Mobile Application

72. The mobile application shall create, read and update the family assessment. Business Mobile Application

73. The mobile application shall create, read and update the child safety

assessment. Business Mobile Application

74. The mobile application shall create, read and update the safety plan. Business Mobile Application






Type Work Stream

75. The mobile application shall create, read and update the case plan. Business Mobile Application

76. The mobile application shall create, read and update the case plan notes. Business Mobile Application

77. The mobile application shall create, read and update the judicial review. Business Mobile Application

78. The mobile application shall create, read and update the unified home study. Business Mobile Application

79. The mobile application shall display and allow updates to other forms (TBD

during design). Business Mobile Application

80. The mobile application shall integrate contact manager, email, GPS, data

recording and capture, and case management capabilities. Business Mobile Application

81. The mobile application shall pre-populate forms, dashboards and face sheets

with existing FSFN data. Business Mobile Application

82. The mobile application shall allow input data form capture and database

storage. Business Mobile Application

83. The mobile application shall allow for “copy forward” capabilities within

and between forms, dashboards and face sheets. Business Mobile Application

84. The mobile application shall provide soft keyboard input capabilities. Business Mobile Application

85. The mobile application shall provide swipe entry input. Business Mobile Application

86. The mobile application shall support offline operation and data storage

while not connected to the network. Business Mobile Application

87. The mobile application shall support data encryption on the mobile device. Business Mobile Application

88. The mobile application shall support data synchronization and deletion from

the device upon network re-connection. Business Mobile Application

89. The mobile application shall support printing of selected documents. Business Mobile Application

90. The mobile application shall support secure VPN access to DCF’s intranet. Business Mobile Application






Type Work Stream

91.

The mobile application shall provide mobile device management (MDM)

capabilities including but not limited to provisioning, asset management,

security, policy definition and enforcement, application management, and

data synchronization.


92. The FSFN system shall be enhanced to create, read and update up to 100

standard non-legal forms (see Appendix A). (SAR Requirement #12, 18) Business SACWIS Compliance Changes

93. The FSFN system shall be enhanced to store the standard non-legal forms in

PDF format. (SAR Requirement #12) Business SACWIS Compliance Changes

94. The FSFN system shall be enhanced to pre-populate the non-legal forms

with existing data elements from FSFN. (SAR Requirements #12, 18) Business SACWIS Compliance Changes

95. The FSFN system shall be enhanced to capture and store data elements

input into the non-legal forms. (SAR Requirements #12, 18) Business SACWIS Compliance Changes

96. The FSFN system shall be enhanced to allow CBCs to customize the non-

legal forms. (SAR Requirements #12, 18) Business SACWIS Compliance Changes

97. The FSFN system shall be enhanced to create, read and update up to 70

standard legal forms (see Appendix B). (SAR Requirement #12 Business SACWIS Compliance Changes

98. The FSFN system shall be enhanced to store the standard legal forms in

PDF format. (SAR Requirement #12) Business SACWIS Compliance Changes

99. The FSFN system shall be enhanced to pre-the legal forms with existing

date elements from FSFN. (SAR Requirement #12) Business SACWIS Compliance Changes

100. The FSFN system shall be enhanced to capture and store data elements

input into the legal forms. (SAR Requirement #12 Business SACWIS Compliance Changes

101. The FSFN system shall be enhanced to allow CLS to customize the legal

forms. (SAR Requirement #12) Business SACWIS Compliance Changes

102. The FSFN system shall be enhanced to allow CLS read/write/ print access

to standard legal forms. (SAR Requirement #12) Business SACWIS Compliance Changes

103.

The FSFN system shall be enhanced to pre-populate the case staffing and

case transfer face sheets with existing data elements from FSFN. (SAR

Requirement #12)

Business SACWIS Compliance Changes






Type Work Stream

104.

The FSFN system shall be enhanced to provide “drill down” capabilities

based on data elements on the case staffing and case transfer face sheets.

(SAR Requirement #12)


105. The FSFN system shall be enhanced to provide up to five child placement

and diligent search reports. (SAR Requirement #12) Business SACWIS Compliance Changes

106. The FSFN system shall be enhanced to allow CBCs to customize up to five

reports. (SAR Requirement #12) Business SACWIS Compliance Changes

107.

The FSFN system shall be enhanced to provide a standard, streamlined

family and safety assessment which support DCF’s January 2008 Quality

Improvement Plan Goal #3. (SAR Requirement #13)


108.

The FSFN system shall be enhanced to provide a standard streamlined

family assessment which supports DCF’s January 2008 Quality



109.

The FSFN system shall be enhanced to provide a standard streamlined child

safety assessment which supports DCF’s January 2008 Quality



110.


safety plan which supports DCF’s January 2008 Quality Improvement Plan

Goal #3. (SAR Requirement #13)


111.

The FSFN system shall be enhanced to provide a standard streamlined case

plan which supports DCF’s January 2008 Quality Improvement Plan Goal

#3. (SAR Requirements #13, 29)


112.


judicial review which supports DCF’s January 2008 Quality Improvement

Plan Goal #3. (SAR Requirement #13)


113.


unified home study which supports DCF’s January 2008 Quality








Type Work Stream

114.

The FSFN system shall be enhanced to provide an integrated family and

safety assessment, safety and case plan, judicial review and unified home

study supporting DCF’s January 2008 Quality Improvement Plan Goal 3.

(SAR Requirement #13)


115.

The FSFN system shall be enhanced to incorporate “copy forward”

capabilities within one assessment/plan/review/study tab to another. (SAR

Requirement #13)


116.

The FSFN system shall be enhanced to incorporate “copy forward”

capabilities from one assessment/plan/review/study version to another. (SAR

Requirements #13, 29)


117.

The FSFN system shall be enhanced to align the medical/ mental health

disabilities data elements captured to the AFCARS data elements. (SAR

Requirement #15)


118. The FSFN system shall be enhanced to date/time stamp the medical/ mental

health disabilities data. (SAR Requirement #15) Business SACWIS Compliance Changes

119.

The FSFN system shall be enhanced to maintain a medical/ mental health

disabilities data element history by date/time stamp. (SAR Requirement

#15)


120.

The FSFN system shall be enhanced to identify and match children and

family services available to those needs identified in the case plan. (SAR

Requirements #16, 30 )


121. The FSFN system shall be enhanced to eliminate duplicate narratives upon

printing the case plan. (SAR Requirement #29) Business SACWIS Compliance Changes

122.

The FSFN system shall be enhanced to recognize the addition of the father

after the initial case plan is created without generating separate judicial

reviews. (SAR Requirement #29)


123. The FSFN system shall be enhanced to allow insertion of addendums into

frozen case plans. (SAR Requirement #29) Business SACWIS Compliance Changes

124. The FSFN system shall be enhanced to modify RDC to allow for capturing

and uploading case notes. (SAR Requirement #29) Business SACWIS Compliance Changes






Type Work Stream

125. The FSFN system shall be enhanced to de-couple FSFN documents

generated by MS Word templates (SAR Requirement #29) Business SACWIS Compliance Changes

126.

The FSFN system shall be enhanced to include an interactive unified home

study module which produces an updated unified home study form. (SAR

Requirement #50)


127.

The FSFN system shall be enhanced to incorporate family violence

considerations into family and child safety assessments, safety and case

plan, judicial review and unified home study.

Business Child Protection Transformation

Functionality Changes

128. The FSFN system shall be enhanced to allow access to case notes by person

and case number. Business

Child Protection Transformation


129. The FSFN system shall be enhanced to create a case note drop down tab for

adoption categories. Business



130. The FSFN system shall be enhanced to create a case note category for post

adoption with up to nine note types. Business



131. The FSFN system shall be enhanced to create a one page case history

summary in reverse chronological order. Business



132. The FSFN system shall be enhanced to allow “drill down” capabilities with

the one page case history summary. Business



133. The FSFN system shall be enhanced to allow for searches of FSFN data

based on person, case, worker, provider organization, or provider service. Business



134.

The FSFN system shall be enhanced to allow for standard search criteria

based on a person, case, worker, provider organization, or provider service

search.



135.

The FSFN system shall be enhanced to incorporate advanced search

algorithms including but not limited to phonetics, transliteration,

deterministic and probabilistic.



136. The FSFN system shall be enhanced to match and link similar search

results. Business



137. The FSFN system shall be enhanced to detect search result aliases. Business Child Protection Transformation







Type Work Stream

138. The FSFN system shall be enhanced to identify irregularities in user input

(data entry anomalies). Business



139.

The FSFN system shall be enhanced to protect individual privacy concerns

through anonymous resolution, displaying either the full matching records

or simply a ‘Yes’ or ‘No’.



140. The FSFN system shall be enhanced to reduce false positives through multi-

attribute matching. Business



141. The FSFN system shall be enhanced to return graded search results. Business Child Protection Transformation


142. The FSFN system shall be enhanced to provide an ability to perform full

text searches. Business



143. The FSFN system shall be enhanced to provide an ability to perform "fuzzy

logic" searches. Business



144. The FSFN system shall be enhanced to provide an ability to perform

geographic-based "vicinity" searches (e.g., ZIP code, crossing streets). Business




soundexing searches. Business




keyword searches. Business



147.

The FSFN system shall be enhanced to perform searches based on root

expansions or stemming (e.g., search for submit and find submitted,

submitting).




advanced searches based on configurable criteria. Business




wildcard character searches. Business



150.

The FSFN system shall be enhanced to provide an ability to combine

multiple search criteria using logical ‘AND’, ‘OR’ and ‘BETWEEN’

operators.








Type Work Stream

151. The FSFN system shall be enhanced to provide an ability to sort search

results. Business



152.

The FSFN system shall be enhanced to provide an ability to search on

information stored in separate repositories with a single query (i.e. federated

search).



153. The FSFN system shall be enhanced to provide an ability to execute

advanced search functionality from any area within the system. Business



154.

The FSFN system shall be enhanced to provide the user with the total

number of records found and total number of unduplicated records found

matching the user's query.



155.

The FSFN system shall be enhanced to provide a context sensitive search

mechanism while executing searches. The context shall be based on the

system area from which the search was initiated (e.g., search for provider

when executing search from case management functionality).



156. The FSFN system shall be enhanced to provide an ability to navigate to the

appropriate record selected (within the context of the search). Business



157. The FSFN system shall be enhanced to allow users to save searches with

user-defined names. Business



158. The FSFN system shall be enhanced to provide an ability to export the

search results in multiple formats. Business



159. The FSFN system shall be enhanced to provide an ability to specify the

limit of the maximum number of records retrieved by a single query. Business



160. The FSFN system shall be enhanced to provide an ability to filter the search

results based on the user's security profile. Business



161.

The FSFN system shall be enhanced to provide an ability to rank and score

the search results based on the search criteria and the context in which the

search is executed.



162. The FSFN system shall be enhanced to require at least one search criteria to

be populated prior to executing a search. Business








Type Work Stream

163.

The FSFN system shall be enhanced to provide an ability to search and

retrieve records (or logical groups of records) matching compound search

criteria (e.g., search for all open cases within a zip code, by protective

investigator).



164. The FSFN system shall be enhanced to provide ability to group search

results. Business



165. The FSFN system shall be enhanced to streamline the family member

lists/relationships on the relationships tab. Business



166. The FSFN system shall be enhanced to streamline the medical tab. Business Child Protection Transformation


167. The FSFN system shall be enhanced to pre-populate the medical tab from

the AHCA data. Business



168. The FSFN system shall be enhanced to streamline the educational tab. Business Child Protection Transformation


169. The FSFN system shall be enhanced to add the daycare option to the

educational tab. Business



170. The FSFN system shall be enhanced to create a dropdown of all county

schools to the educational tab. Business



171. The FSFN system shall be enhanced to add a historical narrative box to the

educational tab. Business



172. The FSFN system shall be enhanced to pre-populate the educational tab

from DOE data. Business



173. The FSFN system shall be enhanced to include tracking of educational data

in FSFN. Business



174. The FSFN system shall be enhanced to reduce the workflow complexity of

independent living placements. Business



175. The FSFN system shall be enhanced to capture additional data elements on

the independent living tab. Business



176. The FSFN system shall be enhanced to track additional data elements on the

independent living tab. Business








Type Work Stream

177. The FSFN system shall be enhanced to “carry forward” independent living

tab data elements to the case plan. Business



178. The FSFN system shall be enhanced to “carry forward” independent living

tab data elements to the judicial reviews. Business



179. The FSFN system shall be enhanced to reduce the complexity of opening

cases. Business



180. The FSFN system shall be enhanced to reduce the complexity of assigning

cases. Business



181. The FSFN system shall be enhanced to reduce the complexity of closing

cases. Business



182. The FSFN system shall be enhanced to automate workflow based on a

placement change from a completed exit interview to approvals. Business




the legal module. Business



184. The FSFN system shall be enhanced to allow identical data be applied to

other case participants in the legal module court hearings. Business




other case participants in the legal module dependency adjudications. Business



186.

The FSFN system shall be enhanced to automatically update each

participant’s permanency goal in the legal module dependency

adjudications.




other case participants in the legal module judicial review. Business




other case participants in the legal module termination of parental rights. Business



189. The FSFN system shall be enhanced to allow for recording all legal actions

in the legal module. Business



190. The FSFN system shall be enhanced to streamline the workflow that allows

splitting a case to satisfy case management and legal needs. Business








Type Work Stream


one time payments. Business




creating payments. Business




assigning services to providers. Business



194. The FSFN system shall be enhanced to allow the ability to open intakes via

hyperlink. Business



195. The FSFN system shall be enhanced to allow viewing of legacy

HomeSafenet (HSn) abuse history reports. Business



196. The FSFN system shall be enhanced to allow viewing of legacy Florida

Abuse History and Information System (FAHIS) abuse history reports. Business



197. The FSFN system shall be enhanced to list all the children of the client on

the member’s page. Business



198. The FSFN system shall be enhanced to streamline the licensing module. Business Child Protection Transformation


199. The FSFN system shall be enhanced to create the ability to make changes to

submitted inquiries in the licensing module. Business



200. The FSFN system shall be enhanced to streamline the view of the payment

history for a child. Business



201. The FSFN system shall be enhanced to redesign the reunification home

study including the capture of new data elements. Business



202. The FSFN system shall be enhanced to redesign the special conditions

referral template. Business



203. The FSFN system shall be enhanced to redesign the child on child sexual

abuse referral template. Business



204. The FSFN system shall be enhanced to provide a standard family closure

letter. Business



205. The FSFN system shall be enhanced to provide the ability to customize the

family closure letter. Business








Type Work Stream

206. The FSFN system shall be enhanced to provide an electronic voluntary

protective services agreement form and capture data elements. Business



207. The FSFN system shall be enhanced to streamline and incorporate specific

threats to child safety in the out of home plan. Business



208. The FSFN system shall be enhanced to streamline and incorporate specific

threats to child safety in the visitation plan. Business



209. The FSFN system shall be enhanced to provide read only access to the

Florida courts and DJJ personnel. Business



210. The FSFN system shall be enhanced to provide read/write access to

Guardian ad Litem program (GAL). Business



211. The system shall provide a daily batch interface with National Crime

Information Center (NCIC) for background checks information. Business

Data Exchange Interfaces

w/Other Agencies

212. The system shall provide a daily batch interface with Florida Crime

Information Center (FCIC) for background checks information. Business


w/Other Agencies

213. The system shall provide a daily batch interface with Judicial Inquiry

System (JIS) for background checks information. Business


w/Other Agencies

214.

The system shall provide a daily batch interface with Florida’s public

assistance eligibility System (ACCESS Florida) for Eligibility and history

of public assistance information.

Business Data Exchange Interfaces

w/Other Agencies

215.

The system shall provide a daily batch interface with Florida’s Driver and

Vehicle Information Database System (DAVID) for State of Florida driver’s

license information.


w/Other Agencies

216.

The system shall provide a daily batch interface with Florida Department of

Education (DOE) for Education records – attendance, grades, school

changes, address changes.


w/Other Agencies

217. The system shall provide a daily batch interface with LexisNexis Accurint

system for background checks information. Business


w/Other Agencies

218. The system shall provide a daily batch interface with Adult Services

Information System (ASIS) screened out records. Business


w/Other Agencies






Type Work Stream

219.

The system shall provide a daily batch interface with e-Agent system

(National Law Enforcement Telecommunications System (NLETS) and

state Criminal Justice Information Systems (CJIS) for criminal history and

background checks information.


w/Other Agencies

220.


Health Vital Stats System for Florida birth, death, marriage, divorce and

historic vital records information.


w/Other Agencies

221. The system shall provide a daily batch interface with Florida Department of

Health SHOTS system for Immunization Records information. Business


w/Other Agencies

222.

The system shall provide a daily batch interface with Florida County

Sheriff’s System for Local Criminal Records, Background Checks, and

Call-outs information.


w/Other Agencies

223.


Juvenile Justice (DJJ) for information pertaining to jointly served children

under DCF care.


w/Other Agencies

224.


Corrections (DOC) for Incarceration, Probation/Parole, Criminal Records,

and Background Checks information.


w/Other Agencies

225. The system shall provide a daily batch interface with Florida Agency for

Health Care Administration (AHCA) for Medicaid Claims Information. Business


w/Other Agencies

226.

The system shall provide a daily batch interface with National Child Abuse

and Neglect Data System (NCANDS) for Allegation records in other States,

and Background Checks.


w/Other Agencies

227. The system shall provide a real-time interface with National Crime

Information Center (NCIC) for background checks information. Business


w/Other Agencies

228. The system shall provide a real-time interface with Florida Crime

Information Center (FCIC) for background checks information. Business


w/Other Agencies

229. The system shall provide a real-time interface with Judicial Inquiry System

(JIS) for background checks information. Business


w/Other Agencies






Type Work Stream

230.

The system shall provide a real-time interface with Florida’s public

assistance eligibility System (ACCESS Florida) for Eligibility and history

of public assistance information.


w/Other Agencies

231.

The system shall provide a real-time interface with Florida’s Driver and

Vehicle Information Database System (DAVID) for State of Florida driver’s

license information.


w/Other Agencies

232.

The system shall provide a real-time interface with Florida Department of

Education (DOE) for Education records – attendance, grades, school

changes, address changes.


w/Other Agencies

233. The system shall provide a real-time interface with LexisNexis Accurint

system for background checks information. Business


w/Other Agencies

234. The system shall provide a real-time interface with Adult Services

Information System (ASIS) screened out records. Business


w/Other Agencies

235.

The system shall provide a real-time interface with e-Agent system

(National Law Enforcement Telecommunications System (NLETS) and

state Criminal Justice Information Systems (CJIS) for criminal history and

background checks information.


w/Other Agencies

236.


Health Vital Stats System for Florida birth, death, marriage, divorce and

historic vital records information.


w/Other Agencies

237. The system shall provide a real-time interface with Florida Department of

Health SHOTS system for Immunization Records information. Business


w/Other Agencies

238.

The system shall provide a real-time interface with FL County Sheriff’s

System for Local Criminal Records, Background Checks, and Call-outs

information.


w/Other Agencies

239.


Juvenile Justice (DJJ) for information pertaining to jointly served children

under DCF care.


w/Other Agencies






Type Work Stream

240.


Corrections (DOC) for Incarceration, Criminal Records, and Background

Checks information.


w/Other Agencies

241. The system shall provide a real-time interface with Florida Agency for

Health Care Administration (AHCA) for Medicaid Claims Information. Business


w/Other Agencies

242.

The system shall provide a real-time interface with National Child Abuse

and Neglect Data System (NCANDS) for Allegation records in other States,

and Background Checks.


w/Other Agencies

243.


Health’s Child Protection Tracking Information System (CPTIS) for

medical evaluations


w/Other Agencies

244.


Health’s Child Protection Tracking Information System (CPTIS) for

medical evaluations


w/Other Agencies

245. The data analytics tool shall have the capability to access one or more data

sources. Business Data Analytics and Alerts

246. The data analytics tool shall parse both structured and unstructured data. Business Data Analytics and Alerts

247. The data analytics tool shall provide the ability to identify key data elements

in the structured data and extract. Business Data Analytics and Alerts

248. The data analytics tool shall identify key entities and facts in unstructured

data and extract. Business Data Analytics and Alerts

249. The data analytics tool shall cleanse the extracted data. Business Data Analytics and Alerts

250. The data analytics tool shall store the extracted data in a relational database. Business Data Analytics and Alerts

251. The data analytics relational database shall be structured for reporting at the

unit, county, circuit, CBC, Region and Statewide level. Business Data Analytics and Alerts

252. The data analytics tool shall append people and event information to the

data in the database. Business Data Analytics and Alerts






Type Work Stream

253. The data analytics tool shall add chronology information to the data in the

database. Business Data Analytics and Alerts

254. The data analytics tool shall add relationship information to the data in the

database. Business Data Analytics and Alerts

255. The data analytics tool shall incorporate new data in the database as it

becomes available. Business Data Analytics and Alerts

256. The data analytics tool shall assess all data in the database pertaining to risk

to a child. Business Data Analytics and Alerts

257. The data analytics tool shall determine the risk and safety level for a child. Business Data Analytics and Alerts

258. The data analytics tool shall alert investigators and Case Workers based on

the level of risk and safety situations. Business Data Analytics and Alerts

259. The data analytics tool data element selection and assessment, and

determination of child risk/safety level shall be research based. Business Data Analytics and Alerts

260. The system shall provide an ability to scan all documents. Business Document Management

261. The system shall provide an ability to scan documents in bulk. Business Document Management

262. The system shall provide an ability to adjust scanner characteristics prior to

initiation of scanning – e.g. simplex, duplex, page orientation, etc. Business Document Management

263. The system shall provide an ability to perform both simplex and duplex

scanning within the same batch. Business Document Management

264. The system shall provide an ability to view images during scanning. Business Document Management

265. The system shall provide an ability to group related documents when

scanned. Business Document Management

266. The system shall provide an ability to perform quality control review on

images of scanned documents. Business Document Management






Type Work Stream

267.

The system shall provide an ability to perform the following actions on an

image:

1. Magnify portions of image in separate window

2. Navigate image

3. Fit to window options

4. Zoom image

5. Rotate image

6. Enhance image – lighten, darken

7. Advance forward or backward pages

8. Print image

Business Document Management

268. The system shall provide an ability to delete or re-index individual pages of

scanned documents (i.e. poor image quality) Business Document Management

269. The system shall provide an ability to delete or re-index scanned document

(i.e. poor image quality) Business Document Management

270. The system shall provide an ability to delete or re-index groups of scanned

documents (i.e. poor image quality). Business Document Management

271. The system shall provide an ability to rescan deleted pages (i.e. to replace

rejected pages). Business Document Management

272. The system shall provide an ability to rescan deleted documents (i.e. to

replace rejected images). Business Document Management

273. The system shall provide an ability to rescan deleted scan batch (i.e. to

replace the rejected images). Business Document Management

274. The system shall provide an ability to add additional pages to batch after

scanner has stopped. Business Document Management

275.

The system shall provide an ability to compare the manual counts of pages

and documents with the actual system counts of pages and documents

scanned.


276. The system shall provide a pre-defined list of document types. Business Document Management






Type Work Stream

277. The system shall provide an ability to manage (Create, Read, Update,

Delete) the pre-defined list of document types. Business Document Management

278. The system shall provide an ability to identify documents by “Document

Type” when scanned. Business Document Management

279. The system shall provide an ability to identify the document type of newly

added documents. Business Document Management

280. The system shall provide an ability to modify the document type of scanned

documents. Business Document Management

281. The system shall provide the ability to link scanned batches to a case,

investigation or person record. Business Document Management

282. The system shall provide an ability to link scanned document to a case,

investigation or person record. Business Document Management

283.

The system shall provide an ability to search existing records (e.g. case,

investigation and person) to locate the record that should be linked to a scan

batch.


284.

The system shall provide an ability to search existing records (e.g. case,

investigation and person) to locate the record that should be linked to a

scanned document.


285. The system shall provide an ability to re-index documents (e.g. document

was associated with a record in error). Business Document Management

286. The system shall provide the ability to “Bates” stamp individual pages

based upon user criteria (Ex. 001, 002, 003, AA-1, AA-2). Business Document Management

287. The system shall provide an ability to identify a document as a newer

version of an existing document when adding documents. Business Document Management

288. The system shall ensure that all documents (scanned or uploaded) are

associated with a record(s) in the system. Business Document Management

289. The system shall provide an ability to delete a batch and all documents

associated with the batch. Business Document Management

290. The system shall provide the ability to index documents at the document

level (index values may be different based on document type). Business Document Management






Type Work Stream

291. The system shall provide the ability to index documents by batch. Business Document Management

292. The system shall pre-fill index field values. Business Document Management

293. The system shall provide an ability to modify pre-filled index fields. Business Document Management

294. The system shall default index fields to null if the fields are not pre-filled by

the system. Business Document Management

295. The system shall provide an ability to carry forward any individual index

values or all index values from a previous document. Business Document Management

296.

The system shall provide an ability to enforce mandatory index information

capture (i.e. document will not be saved until all required index fields are

complete)


297. The system shall provide an ability to open certain types of documents

(TBD e.g. MS Word, MS Excel etc) in their native applications. Business Document Management

298. The system shall provide an ability to view a list of all documents related to

a case, investigation, person, provider and a combination thereof. Business Document Management

299. The system shall provide an ability to filter the list of documents related to a

case, investigation, person, and provider. Business Document Management

300. The system shall provide an ability to sort the list of documents related to a

case, investigation, person, and provider. Business Document Management

301. The system shall provide the ability to access previous versions of

documents. Business Document Management

302. The system shall provide an ability to upload documents from a range of

devices (e.g. Smartphone, PC, Laptop, Tablet PC, Tablet) Business Document Management

303.

The system shall provide an ability to upload documents in different file

formats (e.g. htm, html, pdf, txt, doc, xls, tif, tiff, ppt, jpg, jpeg, wav, and

rtf)


304. The system shall reject any document upload attempt where the file format

on the user’s document is a restricted format (e.g. .exe, .zip) Business Document Management






Type Work Stream

305. The system shall scan all uploaded documents for viruses before hardening

them to disk. Business Document Management

306. The system shall provide an ability to upload multiple documents in a single

transaction. Business Document Management

307. The system shall provide an ability to link uploaded documents with a case,

investigation, person, provider and a combination thereof. Business Document Management

308. The system shall provide an ability to index uploaded documents Business Document Management

309. The system shall provide performance management dashboards for users

based on user role. Business

Performance Management and

Dashboards

310. The system shall provide the users with an ability to customize their

dashboard. Business


Dashboards

311. The system shall provide an ability to design and execute dashboards based

on user role in the system and in the organization. Business


Dashboards

312. The system shall provide drilldown capabilities for dashboards. Business Performance Management and

Dashboards

313. The system shall provide an ability to design and execute ad-hoc

dashboards. Business


Dashboards

314. The system shall provide an ability to publish ad-hoc dashboards (i.e. to

share the dashboards with other users). Business


Dashboards

315. The system shall provide the ability to include graphics in dashboards. Business Performance Management and

Dashboards

316. The system shall provide the ability to take the user step-by-step through

report creation. Business


Dashboards

317. The system shall provide the ability to generate dashboards based on

calendar year and fiscal year (i.e., federal or state) data. Business


Dashboards

318. The system shall provide the ability to generate a dashboard based on any

data element in the system. Business


Dashboards

319. The system shall provide the ability to categorize dashboard components

into categories. Business


Dashboards






Type Work Stream

320. The system shall provide the ability to generate dashboards based on data

from a date range. Business


Dashboards

321. The system shall limit a user’s access to dashboard components based on

the user’s security profile. Business


Dashboards

322. The system shall provide investigation, case, and performance status

dashboards for CPIs and Case Workers Business


Dashboards

323. The system shall provide practice and operating performance dashboards. Business Performance Management and

Dashboards

5.1. ASSUMPTIONS

The future state conceptual system architecture and future state technical system architecture presented in this document are not intended

to be a final representation of the architecture. The final architectures will be developed during the functional and technical design phases

of the project based on the technologies, hardware and software products proposed by the system integration vendor.

The selected system integration vendor will validate and refine the system requirements.





APPENDIX - A: STANDARD FORMS

Form # Form Name

CF 0791 ICPC Financial - Medical Plan for Interstate Compact

CF 0792 ICPC Receiving State's Priority Home Study (ICPC 102)

CF 0793 ICPC Priority Community Based Care Transmittal

CF 0794 ICPC Placement Request (ICPC 100A)

CF 0795 ICPC Report of Placement Status (ICPC 100B)

CF 0797 ICPC Community Based Care Transmittal

CF 0798 ICPC Sending State Priority Home Study Request (ICPC 101)

CF 1649 Affidavit of Good Moral Character

CF FSP 4006 Consent for Treatment and Release of Medical Information for Family Safety

Program

CF FSP 4008 Affidavit of Understanding for Person Receiving Family Safety Records

CF FSP 4014 Child (Abuse) File Closure Checklist

CF FSP 4018 Security Agreement for Vital Statistics System

CF FSP 5004 Voluntary Placement Agreement

CF FSP 5004S Voluntary Placement Agreement (Spanish)

CF FSP 5009 Adoption Affidavit - Surrender/Consent/Notice Waiver

CF FSP 5026 Closing of Licensed Home for Dependent Children

CF FSP 5027 Relicensing Summary for Licensed Home for Dependent Children

CF FSP 5065 Client Referral for Services

CF FSP 5071 Adoptive Home Application

CF FSP 5073 Physician's Report on Child Placed for Adoption

CF FSP 5074 Family, Social and Medical Information About Child to be Adopted

CF FSP 5075 Subsidized Adoption Program - Child's Summary

CF FSP 5076 Birth and Delivery Information on Child Placed for Adoption

CF FSP 5077 Subsidized Adoption Program Disposition Sheet

CF FSP 5078 Subsidized Adoption Program Data Sheet

CF FSP 5079 Adoption Assistance Agreement

CF FSP 5081 Recommendation For and Consent To Adoption

CF FSP 5087 Confidentiality Agreement for Foster Parent Application

CF FSP 5090 Release of Information for Foster/Adoptive Parent Application

CF FSP 5108 Background Information on Prospective Adoptive Child

CF FSP 5117 Personal Reference for Foster Care Application

CF FSP 5118 Substitute Care School Reference

CF FSP 5135 Master License Application for Accredited Child-Placing Agencies (Microsoft





Form # Form Name

Word)

CF FSP 5146 Adoption Subsidy Title IV-E Eligibility/Screening Worksheet

CF FSP 5172 Adoption Subsidy Disclaimer

CF FSP 5208 Flex Dollar Request

CF FSP 5220 Undergraduate Fee Exemption for Students in FC/IL/Adoptions

CF FSP 5222 Notarized Designation of Client Money and Property

CF FSP 5228 Psychotropic Medication Informed Consent Facilitation

CF FSP 5230 Authorization for Release of Health & Medical Info for Prospective

Foster/Adoptive Parents

CF FSP 5233 Relative Caregiver Communication

CF FSP 5239 Agreement To Provide Informal Child Care

CF FSP 5240 Abuse Background Check for Informal Child Care Provider

CF FSP 5244 Request for TANF Funds/Eligibility Determination - 2010/2011 and 2011-2012

CF FSP 5244,

7/2007

Request for TANF Funds/Eligibility Determination - 2007-2008

CF FSP 5244S Request for TANF Funds/Eligibility Determination - 2010/2011 and 2011/2012

(Spanish)

CF FSP 5254 Title IV-A Emergency Assistance Application

CF FSP 5262 Statewide Critical Incident Report

CF FSP 5263 Maintenance Adoption Subsidy - TANF Worksheet/Application

CF FSP 5264 Voluntary Protective Supervision Agreement

CF FSP 5264S Voluntary Protective Supervision Agreement (Spanish)

CF FSP 5275 ICPC Motion for Order of Compliance

CF FSP 5276 ICPC Priority Order of Compliance

CF FSP 5277 ICPC Motion for Order of Compliance and Priority Placement

CF FSP 5279 Psychotherapeutic Medication Treatment Plan Review

CF FSP 5280 ICPC Order of Compliance (not priority)

CF FSP 5291 Psychotherapeutic Medication Treatment Plan

CF FSP 5292 Transitional Support Eligibility or Education Training Vouchers (ETV) Funds

Application

CF FSP 5293 Transitional Plan for Recipient of Transitional Support Services

CF FSP 5294 Aftercare Support Services - Cash Assistance Application

CF FSP 5295 Initial Road to Independence Program Application

CF FSP 5296 Road to Independence Program Funds Renewal Checklist

CF FSP 5297 Road to Independence Program Reinstatement Application

CF FSP 5298 Road to Independence Program Needs Assessment Face-to-Face Consultation

CF FSP 5299 RTI Program High School Needs Assessment Tool

CF FSP 5300 RTI Program Post Secondary Needs Assessment - Academic Year





Form # Form Name

CF FSP 5300A RTI Program Post Secondary Needs Assessment - Summer - Attending School

CF FSP 5300B RTI Program Post Secondary Needs Assessment - Summer - Not Attending School

CF FSP 5302 Request for Road to Independence Program Documentation

CF FSP 5303 Independent Living Program Oral Request for Fair Hearing

CF FSP 5304 Request for Fair Hearing on Denial/Termination/Reduction of Independent Living

Benefits

CF FSP 5311 Notice of Changed Circumstances (re: Master Trust Account)

CF FSP 5312 Master Trust Expenditure Plan

CF FSP 5313 Plan for Achieving Self-Support (Non-Disabled)

CF FSP 5314 Emergency Intake for Protective Investigations

CF FSP 5322 Early Steps Referral Checklist

CF FSP 5323 Verification of Indian Child Welfare Act Eligibility

CF FSP 5323S Verification of Indian Child Welfare Act Eligibility (Spanish)

CF FSP 5328 Disclosure Information to Adoptive Parents

CF FSP 5339 Medical Report for Prescribing Psychotropic Medication to a Child in Out-of-

Home Care

CF FSP 5341 Psychiatric Evaluation Referral for Child Protective Services

CF FSP 5343 Acknowledgement of Firearms Safety Requirements

CF FSP 5344 Performance Assessment for Child Protective Investigator Candidates

CF FSP 5351 Client Education Verification

DH 0527 Certified Statement of Final Decree of Adoption

DOR CS-AP 80 Request for Authorization to Use State Parent Locator Service

ICAMA 6.01 ICAMA Notice of Medicaid Eligibility/Case Activation

ICAMA 6.02 ICAMA Notice Action

ICAMA 6.03 ICAMA Report of Change in Child/Family Status

Unified home study

Transfer Form

Safety Plan





APPENDIX - B: LEGAL FORMS

Form # Form Name

8.901 Caption of Pleadings and Orders

8.902 Verification

8.903 Certificate of Service

8.904 Affidavit for Order to Take Into Custody

8.905 Order to Take Into Custody

8.906 Release Order

8.907 Transfer Order

8.908 Summons

8.909 Plan for Treatment, Training, Or Conduct

8.911 Uniform Child Custody Jurisdiction And Enforcement Act Affidavit

8.912 Petition to Show Cause

8.913 Order to Show Cause

8.929 Detention Order

8.930 Juvenile Notice to Appear

8.931 Delinquency Petition

8.932 Application for Counsel And Order

8.933 Waiver of Counsel

8.934 Order to Determine Mental Condition

8.935 Order of Incompetency

8.936 Order of Competency

8.937 Demand for Voluntary Waiver

8.938 Order of Voluntary Waiver

8.939 Motion for Involuntary Waiver

8.940 Motion to Compile Report

8.941 Order to Compile Report

8.942 Order of Involuntary Waiver

8.947 Disposition Order — Delinquency

8.948 Petition for Revocation of Juvenile Probation

8.949 Order for HIV Testing

8.950 Restitution Order

8.951 Motion for Juvenile Sexual Offender Placement

8.958 Order Appointing Surrogate Parent

8.959 Summons for Dependency Arraignment

8.960 Shelter Petition





Form # Form Name

8.961 Shelter Order

8.962 Motion for Injunction

8.963 Injunction Order

8.964 Dependency Petition

8.965 Arraignment Order

8.966 Adjudication Order — Dependency

8.967 Order of Disposition, Acceptance of Case Plan, And Notice of Hearing

8.968 Affidavit of Diligent Search

8.969 Sworn Statement Regarding Identity or Location of Father

8.970 Order on Judicial Review

8.971 Motion to Terminate Jurisdiction

8.972 Order Terminating Jurisdiction

8.973 Order on Judicial Review for Child Age 17 Or Older

8.974 Petition to Extend or Reinstate Court’s Jurisdiction

8.975 Dependency Order Withholding Adjudication

8.976 Proposed Relative Placement

8.977 Order Authorizing Child to Enter Into Residential Leasehold And Secure Utility

Services Before The Child’s 18th Birthday

8.978 Order Authorizing Child to Secure Depository Financial Services before the Child’s

18th Birthday

8.979 Summons for Advisory Hearing

8.980 Petition for Termination of Parental Rights Based On Voluntary Relinquishment

8.981 Petition for Involuntary Termination of Parental Rights

8.982 Notice of Action for Advisory Hearing

8.983 Adjudication Order And Judgment of Involuntary Termination of Parental Rights

8.984 Judgment of Voluntary Termination of Parental Rights

8.985 Motion to Terminate Supervision And Jurisdiction

8.986 Order Terminating Supervision And Jurisdiction

8.987 Petition for Judicial Waiver of Parental Notice of Termination of Pregnancy

8.988 Sworn Statement of True Name And Pseudonym

8.989 Advisory Notice to Minor

8.990 Final Order Granting Petition for Judicial Waiver of Parental Notice of Termination

of Pregnancy

8.991 Final Order Dismissing Petition for Judicial Waiver of Parental Notice of

Termination of Pregnancy

8.992 Minor’s Petition to Chief Judge to Require A Hearing On Her Petition for Judicial

Waiver of Notice

8.961(a) Order Authorizing Access to Child’s Medical And Educational Records





Form # Form Name

8.978(a) Order Concerning Youth’s Eligibility for Florida’s Tuition And Fee Exemption

Documents

STATE OF LORIDA · and the family. Nonintegrated view: CPIs and Case Workers currently have a disintegrated view into family history. CPIs and Case Workers must review several files