Child Care Licensing

1

• Child Care Licensing
• Mobile Client Server System
• Richard Wyatt, CIO
• Arkansas Department of Health and Human Services

2
DEVELOPMENT HISTORY

• Arkansas DHHS began development of a new Child
  Care Licensing System in October 2000 to replace
  a mainframe system
• One of the requirements was to record Child Care
  Center inspection results on a mobile device to
  eliminate paper forms in the field and re-keying
  in the office
• Initially the field portion of the application
  was written on a Palm Pilot. User feedback
  showed Palm Pilot not acceptable-
• Small screen real estate
• Difficult to navigate through regulations
• Difficulty in character recognition
• Users rejected Laptops due to size and inability
  to capture signature

3
DEVELOPMENT HISTORY (continued)

• The Child Care Licensing System was released
  without a mobile device in October 2002
• Client-Server application VB6 with SQL Server
  backend
• Began investigating Tablet PC in early 2005.
  Purchased three different models for evaluation
  and test. Chose HP 1100 Tablets
• Once Tablet was selected made minor modifications
  to port application ( 2 person months effort)
• Moved production database to MS Database Engine
• Developed stored procedures to move data between
  tablet and server
• Developed method to store signatures digitally

4
SYSTEM STATUS

• In production for five months
• Approximately fifteen users in three field
  offices
• Significant time savings and positive response
  from users
• Evaluating potential use in other components
  within Child Care system as well as other health
  and human services applications

5
Download Data, this is when the Tablet is hooked
up to the network, the user can download all of
their particular case load before going out into
the field.
6
All of the data for this particular Licensing
Specialist is now on the Tablet, the system is
now fully functional without being hooked up to
any sort of network, the data is completely
mobile.
7
(No Transcript)
8
(No Transcript)
9
(No Transcript)
10
(No Transcript)
11
(No Transcript)
12
(No Transcript)
13
Upload Changes, if changes are detected the user
is only allowed to upload changes, not overwrite
their updates. System synchronization keeps user
from overwriting work.
14
The user receives a message telling them that
changes have been updated.
15

• QUESTIONS