System Security Functions: SIIS Technical Architecture (NJ-CIP)

Architecture diagram

Major components of the architecture:

• Database: The database management system will be the Oracle 7 RDBMS running on an HP-UX server.
• Client Computers: The client computers will be industry-standard personal computers running MS-Windows 3.1 (at least initially). Typical configuration will probably include a 66Mhz Intel 80486 or Pentium processor, 500+MB of disk space, 16MB of RAM, and a 15 inch SVGA monitor.
• Network Protocol: TCP/IP will be used exclusively for this project.
• Wide-area Network: The Internet will be the wide area network connecting client sites with the database server.
• Applications: Client applications are expected to be written in MS-Visual Basic, relying on Oracle SQL*Net, Oracle Glue, and/or ODBC as middleware connecting the client applications to the Registry database via TCP/IP.
• Query Tools: Additional "off-the-shelf" commercial SQL query tools are expected to be deployed, likely relying on SQL*Net connectivity.
• Data Collection: Data will be harvested into the Registry via custom interface to the WIC/AFDC KISS system, via custom interface to the Electronic Birth System, and via standard interface to other local data systems found in clinical provider locations.
• Data Access: Eventually, an applications program interface (API) will be developed to allow vendors to write software that accesses data in the Registry for transfer to local data systems found in clinical provider locations.
• User Access: Database users normally do not receive Unix login privileges, but rather receive database usernames and passwords only. SQL*Net encrypts the database password as it travels across the network, with a session key, but does not support user alteration of the password.