Tennessee Online Real Estate Schools

Document Sample
Tennessee Online Real Estate Schools Powered By Docstoc
					            RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
            V.I.P. INTERFACE




            Tennessee Department         United States                Univ of Tenn
                                                                                                    Tennessee                                                      Tennessee
              of Human Services          Department of                 Center for                                                     Tennessee                                      Tennessee
                                                                                                   Department of                                                  Department of
                   Disability             Health and                  Business and                                                     PORTAL                                      State University
                                                                                                    Correction                                                       Safety
            Determination System            Human                      Economic
                    (DDS)                  Services                    Research                                                            (15)                                          (17)
                                                                                                              (14)                                                     (16)
                      (11)                    (12)                        (13)


  Tennessee
Department of
    Human                                                                                                                                                                            Tennessee
   Services                                                                                                                                                                         Department of
Clearinghouse                                                                                                                                                                          Mental
   System                                                                                                                                                                            Retardation
     (10)                                                                                                                                                                             Services
                                                                                                                                                                                         (18)
                                                   6 In



                                                                                  1 Inter




                                                                                                                      2
                                                                                                        1 Interface
  Tennessee




                                                                                                                                                ce


                                                                                                                                                 e
                                                1




Department of




                                                                                                                        Inte
                              1




                                                                                                                                               ac
                                                       In




                                                                                                                                             fa
 Finance and                                                                                                                                                                         Tennessee
                                   In




                                                        ter




                                                                                                                                            rf
                                                                                                                                                                                       State
                                                         te




                                                                                                                                          er
Administration
                                     te




                                                                                                                                         te
                                                                                                                            rfac
                                                                                                                                                                                    Comptrollers
     (9)
                                                                                                                                                              s
                                                            f ac
                                                            rfa
                                       rf




                                                                                                                                      nt
                                                                                                                                                           ce




                                                                                                                                      In
                                                                                         face
                                                                                                                                                                                       Office
                                         ac




                                                                                                                               1I
                                                                                                                                                         fa
                                                                ce




                                                                                                                                                                                        (19)




                                                                                                                                    1
                                                                 es
                                           e




                                                                                                                                                        r

                                                                                                                      es
                                                                                                                                                      te
                                                                   (7




 Tennessee
                                     3I                                                                                                             In
                                                                      M




Department of
                                       nt                                                                                                         2            ce
                                                                       at




  Childrens
                                          er                                                                                                                fa
                                                                                                                                                          er
                                                                         ch




  Services
                                             fac
                                                                                                                                                        nt
                                                                           es




   TNKIDS
                                                 es                                                                                                  1I
                                                                                                                                                                                     EBT Vendor
     (8)
                                   2 In
                                                                              )




                                                                                                                                                                                        (20)
                                        ter
                                           fac                                                                                                                   es
 Tennessee
                                               es                                                                                                           rfac
Department of
   Human                                                                                                                                            7  Inte
  Services                                                                                                                                                                           Tennessee
  (TCSES)
                              9 Interfaces                                                                                                                                           Child Care
     (7)
                                                                                                                                                        1 Interface                 Management
                                                                                                                                                                                       System

                                               face                                             V.I.P.                                                                                (TCCMS)

                               1 Inter
  Tennessee                                                                                                                                                                             (21)
  Education                                                                                                                                             3 In
    Lottery                                                                                                                                                  terf
 Commission                                                                                                                                                      ace
                                             s                                                                                                                       s
                                          ce
                                                                                                                                                                                     BellSouth
      (6)                                                                                                                                                1I
                                     rfa
                                                                                                                                                                                   Sprint Citizens
                                                                                                                                                            nt
                                 nte
                                                                                                                                                                                      Lifeline
                                              s                                                                                                               er
 Tennessee                     6I          ce
                                                                                                                                                                fa
                                                                                                                                                                  ce                     (22)
Department of                          r fa
                                    te
                                                                                                                                                         1




   Health
                                  In
                                                                                                                                                           In




   (DOH)
                                9
                                                            es




                                                                                                                                                              t  er




                                                                                                                                                                                    United States
                                                  rfa fac




      (5)
                                                                                                                                                                    fa




                                                                                                                                                                                    Department of
                                                                                                                                                        31




                                                                                                                                                                                     Homeland
                                                                                                                                                                       c
                                                          r




                                                                                                                                                          e
                                                       te




                                                                                                                                                                                      Security
                                                                                                                                                          In
                                                     ce




 United States
                                                     In




                                                                                                                                                                                     SAVE Alien
                                                                                                                                                            te




    Dept. of                                                                                                                                                                         Verification
                                   2




                                                                                                                                                               rfa




  Agriculture,                                                                                                                                                                           (23)
                                                                                                                      1 Inter
                                                                                                1 Interf




                                                                                                                                           1 In
                                                                         e




                                                                                                                                                       1I
                                               te




   Food and
                                               s




                                                                                                                                                                  ce
                                                                        c




   Nutrition
                                           ce
                                            In




                                                                    rfa




                                                                                                                                                         nte


                                                                                                                                                                     s




Services (FNS)
                                                                                                                                             ter
                                         fa
                                     1




      (4)
                                                                   nte




                                                                                                                                                                                     Tennessee
                                                                                                                                                             r
                                       er




                                                                                                                                                fac


                                                                                                                                                                       fac
                                                                                                                             face




                                                                                                                                                                                    Department of
                                                                                                        ace
                                    nt



                                                                 1I




 Tennessee                                                                                                                                                                           Education
                                                                                                                                                                           e
                                                                                                                                                   e




Department of                                                                                                                                                                       (Free Lunch)
                                       7I




 Labor and                                                                                                                                                                              (24)
 Workforce
Development
     (3)

                                                                                                                                                                                      Bureau of
United States                                                                                                                                                                         TennCare
  Internal
  Revenue                                                                                                                                                                                (25)
  Service
     (2)



                                                                                  Tennessee
 United States                                                                  Department of                               Tennessee                        Tennessee                Tennessee
                               Metro Development and
Social Security                                                                Human Services                               Secretary of                    Department of           Department of
                               Housing Agency Match
Administration                                                                Appeals Resolution                               State                       Human Services          Human Services
      (1)                                                                      Tracking System                                                             Data Warehouse         Service Center IVR
                                            (30)
                                                                                     (29)                                           (28)                         (27)                    (26)
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

V.I.P. INTERFACE CONTENTS
1.1   U.S. Social Security Admini stration (SS A) Beneficiary Data Exchange (BENDEX)
1.2   U.S. Social Security Admini stration (SSA) State Verification and Eligibility System (SV ES)
      (formerly Wire-to-Wire – WTPY)
1.3   U.S. Social Security Admini stration (SS A) State Data Exchange – (SDX)
1.4   U.S. Social Security Admini stration (SS A) SSN Number Validation/Enumeration
1.5   U.S. Social Security Admini stration (SS A) State On-Line Query (SOLQ)
1.6   U.S. Social Security Admini stration (SS A) SSA Pri soner Match
1.7   U.S. Social Security Admini stration (SS A) SSI File for Tennessee Common Application
      (TNCAP )

2.1   U.S. Internal Revenue Service (IRS)

3.1   Tennessee Department of Labor and Workforce Development Food Stamp Employment
      and Training
3.2   Tennessee Department of Labor and Workforce Development Able Bodied Adults without
      Dependents (ABAW D)

4.1   U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Di squalification
      Recipient System State file
4.2   U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Di squalification
      Recipient System National file
4.3   U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Di squalification
      Recipient System Edit file
4.4   U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Trea sury Offse t
      Program Pre-Offset Addre ss Reque st file
4.5   U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Trea sury Offse t
      Program Addre ss Reque st Match/No Match file
4.6   U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Trea sury Offse t
      Program Weekly Collections file
4.7   U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Trea sury Offse t
      Program Weekly Unproce ssables file
4.8   U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Treasury Offset
      Program Weekly Update file
4.9   U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Federal Quality Control
      (QC) Federal Interface


5.1   Tennessee   Department of Health Birth Inquiry
5.2   Tennessee   Department of Health Death Files
5.3   Tennessee    Department of Health Early Periodic Screening, Diagnosis & Treatment
      (EPS D&T)
5.4   Tennessee   Department of Health Women with Infant Children (WIC)
5.5   Tennessee   Department of Health Immunization Records
5.6   Tennessee   Department of Health Home Visit Tracking

6.1   Tennessee Education Lottery Commission (TELC)

7.1   Tennessee Department of Human Services Child Support Enforcement System (TCS ES)
      Custodial Parent Dependant (CP/DP) Update
7.2   Tennessee Department of Human Services Child Support Enforcement System (TCS ES)
      Information on Absent Parent
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

7.3    Tennessee Department of Human Services Child    Support Enforcement System (TCS ES)
       Re-determination Notice Extract
7.4    Tennessee Department of Human Services Child    Support Enforcement System (TCS ES)
       Child Support Pa ss-through Payment (TCS ES)
7.5    Tennessee Department of Human Services Child    Support Enforcement System (TCS ES )
       B3/B5 (Exceeds and Adjustments) File
7.6    Tennessee Department of Human Services Child    Support Enforcement System (TCS ES)
       Families First Referral to Child Support
7.7    Tennessee Department of Human Services Child    Support Enforcement System (TCS ES)
       Families First I ssuance File
7.8    Tennessee Department of Human Services Child    Support Enforcement System (TCS ES )
       Child Support Court Order
7.9    Tennessee Department of Human Services Child    Support Enforcement System (TCS ES)
       Child Support Reimbursement Data


8.1    Tennessee Department of Childrens Service s TnKids IV-E and Medicaid Eligibility
       Determination
8.2    Tennessee Department of Childrens Service s TnKids V.I.P Interface to TNKI DS

9.1    Tennessee Department of Finance and Administration Payments to STARS (State of
       Tennessee Accounting and Reporting
9.2    Tennessee Department of Finance and Administration Families First Fi nancial
       Transactions to STARS
9.3    Tennessee Department of Finance and Administration RACF Validation

10.1   Tennessee Department of Human Services Clearinghouse System

11.1   Tennessee Department of Human Services Di sability Determination System (DDS)

12.1   U.S. Department of Health and Human Services PARIS (Public Assi stance Reporting
       Information System)
12.2   U.S. Department of Health and Human Services Temporary Assi stance for Needy Families
       (TANF) External Federal Reporting
12.3   U.S. Department of Health and Human Services Separate State Program -Maintenance of
       Effort (SSP-MOE) Federal Reporting
12.4   U.S. Department of Health and Human Services Temporary Assi stance for Needy Families
       (TANF) and Separate State program-Maintenance of Effort (SSP-MOE) High Performance
       Bonus (HP B) Work Measure s Federal Reporting
12.5   U.S. Department of Health and Human Services Temporary Assi stance for Needy Families
       (TANF) High Performance Bonus-Medicaid and State Children’s Health Insurance Program
       (SCHIP) Federal Reporting
12.6   U.S. Department of Health and Human Services Child Care Case-Level Federal Report
       (ACF-801)

13.1   University of Tennessee Center for Busine ss/ Economic Re search

14.1   Tennessee Department of Correction

15.1   Tennessee State Services Portal – Self-Screening and Application Filing
15.2   Tennessee State Services Portal – Childcare Enrollment Attendance and Verification (EAV )

16.1   Tennessee Department of Safety

17.1   Tennessee State University
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE


18.1    Tennessee Department of Mental Retardation Services

19.1    Tennesee State Comptroller’s Office Tax Relief Data Sample

20.1    Electronic   Benefit Transfer   (EBT) Families First and Food Stamp Ca se Set-up
20.2    Electronic   Benefit Transfer   (EBT) Families First and Food Stamp Benefit Authoriz ations
20.3    Electronic   Benefit Transfer   (EBT) Child Care Case Set-up
20.4    Electronic   Benefit Transfer   (EBT) Child Care Time and Attendance
20.5    Electronic   Benefit Transfer   (EBT) Families First Service s Ca se Set-up
20.6    Electronic   Benefit Transfer   (EBT) Families First Service s Time and Attendance
20.7    Electronic   Benefit Transfer   (EBT) Vendor Return Files

21.1    Tennessee Department of Human Services Child Care Management System (TCCMS)

22.1    BellSouth, Sprint, Citizens Monthl y Lifeline

23.1    U.S. Department of Homeland Security Systematic Alien Verification for Entitlements
        System (SAV E)

24.1    Tennessee Department of Education Free Lunch Interface

25.1    Tennessee Bureau of TennCare Medicaid Eligibility File
25.2    Tennessee Bureau of TennCare Third Party Liability (TPL) File
25.3    Tennessee Bureau of TennCare Medicaid Medical Evaluation Unit Interim Benefits (MEU)
        File
25.4    Tennessee Bureau of TennCare Medicaid Benefits File
25.5    Tennessee Bureau of TennCare Medicaid Reconciliation File
25.6    Tennessee Bureau of TennCare Medicaid 1610 Manual Transaction File
25.7    Tennessee Bureau of TennCare Medicaid Patient Liability File
25.8    Tennessee Bureau of TennCare Standard Referral File
25.9    Tennessee Bureau of TennCare Standard Response File
25.10   Tennessee Bureau of TennCare Standard Syntax Error File
25.11   Tennessee Bureau of TennCare Standard Eligibility Error File
25.12   Tennessee Bureau of TennCare Immediate Eligibility File
25.13   Tennessee Bureau of TennCare Standard Response Error File
25.14   Tennessee Bureau of TennCare SSN Match File
25.15   Tennessee Bureau of TennCare Address Match File
25.16   Tennessee Bureau of TennCare Pending File
25.17   Tennessee Bureau of TennCare Denial File
25.18   Tennessee Bureau of TennCare On-Line Match
25.19   Tennessee Bureau of TennCare Managed Care Organization (MCO) Selection File
25.20   Tennessee Bureau of TennCare Medicaid and TennCare Standard Overpayment File
25.21   Tennessee Bureau of TennCare Medicaid and TennCare Standard Updated Overpayment
        File
25.22   Tennessee Bureau of TennCare Health Check Visit Match File
25.23   Tennessee Bureau of TennCare Medicaid Eligibility Error File
25.24   Tennessee Bureau of TennCare Standard Referral Error File
25.25   Tennessee Bureau of TennCare Medicaid Response File
25.26   Tennessee Bureau of TennCare Medicaid Response Error File
25.27   Tennessee Bureau of TennCare SSI Terminates from TennCare
25.28   Tennessee Bureau of TennCare SSI Terminates Information to TennCare
25.29   Tennessee Bureau of TennCare Recovery Match
25.30   Tennessee Bureau of TennCare Refugee File
25.31   Tennessee Bureau of TennCare Referrals for Newborns
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE


26.1   Tennessee Department of Human Services Service Center IVR (Interactive Voice
       Response)

27.1   Tennessee Department of Human Services Data Warehouse

28.1   Tennessee Department of Human Services Voter Registration System

29.1   Tennessee Department of Human Services Appeals Resolution Tracking System (ARTS)

30.1   Metro Development and Housing Agency (MDHA) match
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

        1.1 U.S. Social Security Admini stration (SSA) Beneficiary Data Exchange (BENDEX )


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch
System Interface with:
      Agency: Social Security Administration (SSA)
      System: BENDE X
Purpose of the Interface
      BENDE X is a Federal interface designed to provide states with initial and updat ed information on
      Title II (Regular Social Security) eligibility and benefits received by the states‟ Families First,
      Food Stamp and TennCare Medicaid and TennCare Standard recipients .

        The file contains three types of transactions. Accretion requests (add individuals) initiate the
        BENDE X dat a exchange for individuals who have become eligible since the last monthly run.
        Alteration requests are generat ed by the Bureau of TennCare to c onvey a change in the state
        category of assistance or to reflect a state BUY-IN of insurance premiums. Deaccretion
        requests (delete individuals) discontinue the BENDE X exchange for accreted individuals who
        have bec ome ineligible since the last monthly run. Deaccretion requests are also created when
        an individual‟s SSN changes to delete the individuals under the old SSN. In this instance, an
        accretion transaction is also created to re -accrete the individual under the new SSN.

        For each accretion record received, the SSA generates a response record indicating that the
        individual is accreted. Any demographic mismatches bet ween the data sent by Tennessee and
        the data on the SSA‟s own master beneficiary rec ord are indicated on the response rec ord. If
        the individual is receiving Title II benefits or has applied for these, the record contains detailed
        information about the active benefits or the disposition of the application. Once the individual is
        accreted on the SSA side, any change to the individual‟s Title II status by the SSA will trigger an
        update record to Tennessee. This accretion remains in place on the BENDE X system until
        Tennessee sends a de-accretion transaction.

        BENDE X files are processed monthly. Resolved matches are generated when there are no
        discrepancies. Unresolved matches and alerts are generated for rec ords that are processed with
        discrepancies. If there are no discrepancies, the individual's SSA income and/or Medicare
        premium are updated and Families First, Food Stamp and TennCare benefi ts are recalculated
        through mass change. A COLA SDX file is received from SSA and processed on an annual
        basis. Resolved matches are generated when there are no discrepancies. If there are no
        discrepancies, the individual's SSA income and/or Medicare premi um are updated. Families
        First, Food Stamp, TennCare Medicaid, and TennCare Standard are recalculat ed through mass
        change.
Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown


Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

   1.2 U.S. Social Security Admini stration (SSA) State Verification and Eligibility System (SVES )
                                  (formerly Wire-to-Wire – WTPY)

Existing Interface:               Yes
Existing Interface Method:        Batch
Proposed Interface Method:        Batch
System Interface with:
      Agency: Social Security Administration (SSA)
      System: SVES
Purpose of the Interface
      SVES is a Federal interface designed to provide states with client SSN validation and current
      information pertaining to any Title II (Regular Social Security ) and Title XV I (SSI) eligibility and
      benefits received by persons applying for Family Assistance benefit programs.

        On a nightly basis a file is created of requests for information on the Social Security Numbers of
        individuals entered in the application registration process that day, and also the Social Security
        Numbers of individuals added to cases in approved status.

        SSN verification information on individuals applying for benefits will be returned from SSA
        through the Wire-to-Wire process on a daily basis. The SSA sends three types of responses:
        match records indicating the SSA has the information requested, a conflict record indicating a
        disagreement bet ween the data sent and the SSA databases, or a no match record indicating
        that the requested information did not match anyone on SSA's databases. An alert is generated
        for the case manager for each of the SSA responses.

        If the record was free of conflicts and discrepancies, detailed information pertaining to the
        individual's Title II and Title XV I eligibility and payments (if any) is returned. This information is
        stored as a match and an alert is generated to the caseworker to review the SSA information.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

             1.3 U.S. Social Security Admini stration (SSA) State Data Exchange – (SDX)

Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch
System Interface with:
      Agency: Social Security Administration (SSA)
      System: SDX
Purpose of the interface
      SDX is a one-way Federal batch interface designed to provide states with current and ongoing
      information pertaining to all Tennesseans receiving or applying for Title XVI (S SI) eligibility and
      benefits.

        The SSA generates transactions on a daily basis based on changes to the records of anyone
        with a Tennessee mailing address. The incoming transactions are matched against active FA
        recipients. Matches are processed and resol ved matches are generated when there are no
        discrepancies. Unresolved matches and alerts are generated for rec ords that are processed with
        discrepancies. If there are no discrepancies, the individual's SSI income is updat ed and Families
        First, Food Stamp and TennCare benefits are recalculated through mass change. A COLA S DX
        file is received from the SSA and processed on an annual basis. Resolved matches are
        generated when there are no discrepancies. If there are no discrepancies, the individual's SSI
        income is updated and Families First, Food Stamp and TennCare are recalculat ed through mass
        change.

        Inquiry capability is also available into a cumulative database of all SDX updates received
        through the Tennessee Clearinghouse. Using this repository, SSI Eligibles are matched on a
        quarterly basis with all active TennCare and QMB individuals to verify on-going eligibility. If a
        discrepancy is found as defined by policy, a caseworker alert is generat ed.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

        1.4 U.S. Social Security Admini stration (SSA) SS N Number Validation/Enumeration

Existing Interface:               Yes
Existing Interface Method:        Batch
Proposed Interface Method:        Batch
System Interface with:
      Agency: Social Security Administration (SSA)
      System: Numident (Database of Individuals and their SSNs)
Purpose of the interface
      FA recipients are required to have a valid SSN or to have applied for one. In the county offices,
      eligibility counselors assist applicants in filling out an SS-5 form which is used to request either
      the re-issuance of a lost SS card with a previously existing number or the assignment of a new
      SSN and creation of a new card. The worker writes the individual's recipient ID on the form,
      which is rout ed to the local SSA office for proc essing.

        On a monthly basis a file is received from the SSA. The file contains all SSNs that have been
        newly assigned or reverified and a replacement card is sued. Using the recipient ID from the
        record, the individual's „SSN verified indicator‟ is set to „Federally verified‟ and/or a worker alert is
        generated for each discrepancy.

        On a periodic basis, a SSN verification request file is sent to SSA. All indi viduals, who have not
        previously had their SSN federally verified by either the enumeration (assignment of SSN) or
        Numident (Database of Individuals and their SSN‟s) processes, are sent.

        A response file is received from SSA based on the above transmission. Using the Recipient ID
        from the rec ord, the individual's „SSN verified indicator‟ is set to „Federally verified‟ and/or a
        work er alert is generated for each discrepancy.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

             1.5 U.S. Social Security Admini stration (SSA) State On Line Query (SOLQ)

Existing Interface:              Yes
Existing Interface Method:       On Line Real Time
Proposed Interface Method:       On Line Real Time
System Interface with:
      Agency: Social Security Administration (SSA)
      System: SOLQ
Purpose of the interface
      SOLQ is an on-line real-time system offering states direct access to the SSA's master
      beneficiary records. The system provides immediate verification of SS N's and provides det ailed
      eligibility and benefit data pertaining to bot h SSA and SSI.

        Currently SOLQ is used in a stand -alone mode. While this capability will continue to exist, the
        SOLQ processes will be included with the new system as an on-line interfac e.

        As applicants are keyed into the system or individuals are added to existing active cases, on -line
        transactions to the SSA will be generat ed. The responses to these will be immediat ely
        presented to the caseworker, providing virtually instantaneous feedback as to the validity of the
        Social Security Numbers keyed. Errors will be corrected on -line resulting in another trans action
        generated to the SSA and the response presented to the caseworker.

       Once the SSN is validated, the response form the SSA will contain any applicable Title II and
       Title XV I benefit data. This dat a will be associated to the individual, and will be used by the
        worker in determining eligibility for Family Assistance programs.

        The capability to generat e on-demand transactions will also be needed to respond to client calls
        and to verify reported and suspected changes in SSA eligibility and benefits.

        All SOLQ transactions will be generated by the system and the respons es will be received and
        processed by the system.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Existing process for sending/receiving data
        IBM SDLC Prot ocol
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                 1.6 U.S. Social Security Admini stration (SSA) SS A Prisoner Match


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: SSA
      System: Prisoner

Purpose of the interface
      This interface is maintained by the SSA to provide states with in formation concerning the
      incarceration status of Family Assistance recipients.
        On a monthly basis, a file of individuals to be matched is created and transmitted to SSA. Two
        files are ret urned to DHS reporting individuals that are currently incarcerated or previously
        incarcerated. If a match is identified, a match segment and an alert to the case worker are
        generated.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                 1.7 U.S. Social Security Admini stration (SSA) SSI File for TNCAP


Existing Interface:            No
Existing Interface Method:     Batch
Proposed Interface Method:     Batch

System Interface with:
      Agency: SSA
      System: State Data Exchange

       Purpose of the interface
       This interface is maintained by the SSA to provide states with information to establish Food
       Stamp case and to authorize Food Stamp benefits. TNCAP is not currently operational but is
       planned for implementation with the replacement system. TNCAP will be a partnership between
       the Department of Human S ervices and the U.S. Department of Agriculture Food and Nutrition
       Service.
       TNCAP provides an easy method of delivering food assistance to elderly individuals receiving
       SSI. TNCAP will have to be approved as an FNS waiver.
Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Existing process for sending/receiving data
        CONNE CT:DIRECT (anticipated implementation)
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                                2.1 U.S. Internal Revenue Service (IRS)


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Internal Revenue Service
      System: IRS System

Purpose of the interface
   The purpose of this interface is to provide DHS with unearned income data pert aining to active
   recipients.

    On a monthly basis, a transaction file of match requests is sent to the IRS Data Operations. The file
    contains one record for each recipient who has become eligible since the last monthly run. The IRS
    generates a match record for each request received and returns the tape to Tennessee for
    processing. Income amounts checked against certain tolerance levels required by program pol icy. If
    a match is identified, the caseworker is alerted. If discrepancies exist, the caseworker is alerted to
    take appropriate action to resolve the discrepancy.
    The IRS dat abas es are updated on an annual basis. When Tennessee is advised that the IRS
    databases have been updated, a match request file of all eligible individuals is sent to the IRS. This
    process is in addition to the monthly process described above.
Platform
      Hardware: Unknown
      Software: Unknown
      Database: Unknown
      Operating System: Unknown
Existing process for sending/receiving data
        Physical Tape Exchange. Tape format is Fixed Block, EBCDIC.
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

   3.1 Department of Labor and Workforce Development Food Stamp Employment and Training


Existing Interface:             Yes
Existing Interface Method:      Report
Proposed Interface Method:      Batch
System Interface with:
      Agency: Tennessee Department of Labor and Workforce Development (TDLW D)
      System: eCMA TS (Case Management Activity Tracking System)

Purpose of the interface

       This monthly interface serves to provide the TDLWD wit h data pertaining to Food Stamp
       recipients who were referred for Employment and Training Services. Referrals will include those
       required to participate in E & T activity as well as those not required but who are volunteering to
       participat e. The new system should provide automat ed referrals. Individuals registered or de-
       registered for FS work requirements must be passed to the TDLWD. Currently no information is
       sent to the TDLWD concerning de-registered individuals.

       There will be a return file from the TDLWD to DHS that will have complianc e information on the
       individuals that had previously been referred.

       The system will be populated with data coming from TDLW D. The individual's compliance field
        will be updated with the compliance status. The compliance date will be updated with the date
        the compliance was received or the date of non -compliance indicated on the file. The
        compliance verification will be updated as verified by the TDLWD. The non-compliance reason
        field will be updated with the reason for the non-compliance, if applicable. If there is a non-
        compliance reason, the case worker will receive an alert. The alert will define the reason for
        the non-compliance and date of non-compliance.

Platform
        Hardware: Sun
        Software: Unknown
        Database: Oracle 9I
        Operating System: Sun Solaris Server 2.7
Existing process for sending/receiving data
        Report
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

  3.2 Department of Labor and Workforce Development Able Bodied Adults without Dependents
                                          (ABAW D)


Existing Interface:              Yes
Existing Interface Method:       Report
Proposed Interface Method:       Batch

System Interface with:
      Agency: Tennessee Department of Labor and Work forc e Development (TDLWD)
      System: eCMA TS
Purpose of the interface
      Under Food Stamp Able Bodied Adults without Dependents (ABAWD) eligibility rules, individuals
      in this category must participat e in specified employment training activities. Currently there is a
      report provided by DHS to TDLWD containing the names of these individuals. This report should
      be replaced with a file in the new system.

        Monthly response files will be generated to DHS indic ating whether the individual has complied.

        Files are requested instead of the current reports so the data will no longer have to be re -keyed.
        The ABAWD Report will be eliminated once files are provided.

        The system will be populated with data coming from TDLW D. The individual's compliance field
         will be updated with the compliance status. The compliance date will be updated with the date
         the compliance was received or the date of non -compliance indicated on the file. The
         compliance verification will be updated as verified by the TDLWD. The non-compliance reason
         field will be updated with the reason for the non-compliance, if applicable. If there is a non-
         compliance reason, the case worker will receive an alert. The alert will define the reason for the
         non-compliance.

Platform
        Hardware: Sun
        Software: Unknown
        Database: Oracle 9I
        Operating System: Sun Solaris Server 2.7
Existing process for sending/receiving data
        Report
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

 4.1 U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Di squalification Recipient
                                        System State file


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: United States Department of Agriculture (USDA) - Food and Nut rition Services
      System: Disqualific ation Recipient System (DRS)

Purpose of the interface
      Individuals may be disqualified from participation in the FS program for deliberate violations of
      program rules. This monthly interface sends a file of new, deleted or changed FS dis qualified
      individuals to the national Disqualification Recipient System. State data is combined with other
      state's data and shared so that disqualifications can be initiated and tracked nationwide.
Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

 4.2 U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Di squalification Recipient
                                             Match


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: United States Department of Agriculture (USDA) - Food and Nut rition Services
      System: Disqualific ation Recipient System (DRS)

Purpose of the interface
      To provide each state with a mont hly update of national FS disqualifications (new or deleted) so
      that disqualification's can be initiated and tracked.
        Individuals on the file will be compared to the active Food Stamp recipients in the system.
        If a match is found, the system will determine if a match res ult is needed and if a work er in-box
        match notification is needed. If a match result is needed, the system will determine if a
        unresolved or a resolved match is needed and if a worker notification is needed. If the
        disqualification is an out-of-state disqualification, the system will associate the match data to
        the individual, if not already on the system.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Process for receiving data
       CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

 4.3 U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Di squalification Recipient
                                         System Edit file


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: United States Department of Agriculture (USDA) - Food and Nut rition Services
      System: Disqualific ation Recipient System (DRS)

Purpose of the interface
      To notify the State of the status of each of its monthly DRS State Transmitter records (whether
      records were accept ed, accepted with warnings, or rejected with fatal errors). The fatal errors
      must be reset on the database so they can be corrected by Investigations staff before they are
      resent to the national DRS database.
Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

 4.4 U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Treasury Offset Program
                                 Pre-Offset Addre ss Request file


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: United States Department of Agriculture (USDA) - Food and Nut rition Services
      System: Treas ury Offset Program (TOP )

Purpose of the interface
      To submit a monthly file of address requests to the U.S. Treasury for FS claims that could
      potentially be referred to the national Treasury Offset Program (TOP). The file is mat ched wit h
      IRS data for the purpose of returning current client addresses to the state.
Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Process for sending data
       CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

 4.5 U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Treasury Offset Program
                             Addre ss Request Match/No Match file


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: United States Department of Agriculture (USDA) - Food and Nut rition Services
      System: Treas ury Offset Program (TOP )

Purpose of the interface
      To receive addresses previously requested from the U. S. Treas ury for use on the TOP 60-Day
      Notice letter. In addition to the addresses returned (matches ), the monthly file will also include
      any address request rec ords for which a match was not made (no matches ). These No Match
      records will include an error code identifying the specific error condition.
Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Process for receiving data
       CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

 4.6 U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Treasury Offset Program
                                     Weekly Collections file


Existing Interface:            Yes
Existing Interface Method:     Batch
Proposed Interface Method:     Batch

System Interface with:
      Agency: United States Department of Agriculture (USDA) - Food and Nut rition Services
      System: Treas ury Offset Program (TOP )
Purpose of the interface
      To receive a file of collection offsets and spousal reversals from the national Treasury Offset
      Program System. The collections represent IRS, SSA and other federal funds, which have been
      intercept ed and returned to the State of Tennessee to be applied to FS claims. The reversals
      represent prior offsets that may require adjustment on the claims database. When the file is
      processed, the system will update the account rec eivable balance (claim balanc e) with the
      amount that was offs et, and generate a notice to the client. Reports will also be generated.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Process for sending data
       CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

 4.7 U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Treasury Offset Program
                                   Weekly Unproce ssable s file


Existing Interface:            Yes
Existing Interface Method:     Batch
Proposed Interface Method:     Batch

System Interface with:
      Agency: United States Department of Agriculture (USDA) - Food and Nut rition Services
      System: Treas ury Offset Program (TOP )

Purpose of the interface
      To receive unprocessable records from the TOP Weekly Update file. Records submitted on the
      TOP Weekly Updat e file are edited prior to processing against the US DA national TOP database
      and unprocessable records are ret urned to the State with appropriate error codes.
Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Process for receiving data
       CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

 4.8 U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Treasury Offset Program
                                       Weekly Update file


Existing Interface:            Yes
Existing Interface Method:     Batch
Proposed Interface Method:     Batch

System Interface with:
      Agency: United States Department of Agriculture (USDA) - Food and Nut rition Services
      System: Treas ury Offset Program (TOP )

Purpose of the interface
      To submit a weekly file of new, deleted or changed Food Stamp claim data to the national
      Treas ury Offset Program System for possible offs et.
Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Process for sending data
       CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

  4.9 U.S. Department of Agriculture, Food and Nutrition Services (FNS ) Federal Quality
                                  Control (QC) Interface


Existing Interface:             No
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: United States Department of Agriculture (USDA) - Food and Nut rition Services
      System: Quality Control


Purpose of the interface
       Currently, DHS Quality Control transmits QC data to FNS utilizing equipment supplied by FNS.
       This interface will select the data from the new system and create a file that can be loaded to the
       Federal QC system for transmission to FNS.
Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Process for sending data
       Unknown
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                  5.1 Tennessee Department of Health (DOH) Birth Inquiry


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      On Line Real Time

System Interface with:
      Agency: Tennessee Department of Healt h
      System: AIRS (Automated Index Retrieval System)

Purpose of the interface
      As applicants are keyed into the system or individuals are added to active cases or a date of
      birth is changed, on line real-time transactions to the A IRS database will be generated. The user
      will be presented birth information match results/segments that can be selected as birt h
      verification. The system will notify the user if information is missing or unobtainable through
      DOH. The system will auto-populate the appropriate fields if an exact match is found. The
      caseworker can also inquire on any individual at anytime.
Platform
        Hardware: IBM Mainframe
        Software: Unknown
        Database: DB2
        Operating System: z/OS V1.4
Existing process for sending/receiving data
        Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                     5.2 Tennessee Department of Health Death Files


Existing Interface:            Yes
Existing Interface Method:     Batch
Proposed Interface Method:     On Line Real Time

System Interface with:
      Agency: Tennessee Department of Healt h
      System: Vital Statistics

Purpose of the interface
       Currently, a death file is received from the Department of Healt h on a monthly and yearly basis
       containing the individuals whose deaths were reported in a given month or a given year. The
       death files are matched for eac h active individual and a worker alert is generated for each
       match, and monthly and yearly reports are produced of the deceased individuals in active cases.
       In the new system, each individual on the application and for whom an SSN is added or changed
       will be matched against the Department of Health‟s DEA TH file. On line matching will take place
       in real time during the interview process. The user will be presented death match results whic h
       contain information that can be selected as death verification. If a match is found, an in-box
       match transaction for the worker will be generated.
       The monthly and annual files will be processed against active recipients in the system. A match
       result and worker in-box transaction will be generated for each active in dividual found in the
       matching process. A report of active individuals found will be generated.
Platform
        Hardware: IBM Mainframe
        Software: Unknown
        Database: DB2
        Operating System: z/OS V1.4
Existing process for sending/receiving data
        Monthly and Annual Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

  5.3 Tennessee Department of Health Early Periodic Screening, Diagnosi s & Treatment
                                      (EPS D&T)


Existing Interface:             Yes
Existing Interface Method:      Manual
Proposed Interface Method:      Batch

System Interface with:
      Agency: Tennessee Department of Healt h
      System: EPSD& T

Purpose of the interface
      EPSD&T is a health-screening program for children in low-income families. A referral report is
      generated on a periodic basis to the Department of Health.
       Notices are generated to the client for each individual in Families First or TennCare -Medic aid
       cases who are qualified for the EPSD& T program.
Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Existing process for sending/receiving data
        Pamphlet given to the client.
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

   5.4 Tennessee Department of Health (DOH) Department of Health Women with Infant
                                    Children (WIC)


Existing Interface:            Yes
Existing Interface Method:     Batch
Proposed Interface Method:     Batch

System Interface with:
      Agency: Tennessee Department of Healt h
      System: WIC

Purpose of the interface
      DHS currently produces a mont hly file for the Department of Health to identify pregnant women
      and children under 5 years of age who are pot entially eligible for the WIC Program.
Platform
        Hardware: IBM Mainframe
        Software: IMS
        Database: IMS
        Operating System: z/OS V1.4
Existing process for sending/receiving data
        Batch.
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

 5.5 Tennessee Department of Health (DOH) Department of Health Immunization Records


Existing Interface:             No
Existing Interface Method:      None
Proposed Interface Method:      On Line Real Time
System Interface with:
      Agency: Tennessee Department of Healt h
      System: (SIIS) Statewide Immunization Information System

Purpose of the interface
      Maintaining current immunizations for a child is a Families First program requirement. DHS
      needs access to DOH immuniz ation information to determine compliance with this FF
      requirement.
        Specified applicant children and specified children being added to an existing active case,
        whose immuniz ation is due or over due, shall be matched on -line real time against the
        Department of Health‟s Immunization Records. Also, children will be matched at reverification if
        their immunization is due or overdue. If the individual is found, a match segment will be created,
        and an in-box match notification generated for the worker. The system shall record when a
        match was not found.

        The match request record shall be in the Health Insurance P ortability & Accountability Act
        (HIPAA) standard 834 record layout.

Platform
        Hardware: AS400
        Software: Unknown
        Database: DB2
        Operating System: OS/400
Existing process for sending/receiving data:
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

              5.6 Tennessee Department of Health (DOH) Home Visit Tracking


Existing Interface:             No
Existing Interface Method:      None
Proposed Interface Method:      On Line Real Time
System Interface with:
      Agency: Tennessee Department of Healt h
      System:
Purpose of the interface
      DHS needs to capture information relative to referrals made by DHS on Families First clients
      who are having their cases closed. When DOH receives these referrals, they are required to
      make a home visit, or an attempt, within 30 days from the effective closure date. DHS needs to
      track referrals, visits, outcomes, recommendations for auxiliary payments, referrals generated to
      other resources, etc.

Platform
        Hardware: AS400
        Software: Unknown
        Database: DB2
        Operating System: OS/400
Existing process for sending/receiving data:
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                   6.1 Tennessee Education Lottery Commi ssion (TELC)


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: Tennessee Educ ation Lottery Commission (TELC)
      System: N/A

Purpose of the interface
      A monthly file to refer all delinquent overpayments of $101 or more to the TELC for possible
      offset.
Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Existing process for sending/receiving data
        Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

    7.1 Tennessee Department of Human Services Child Support Enforcement System
                 (TCS ES) Custodial Parent Dependant (CP/DP) Update


Existing Interface:           Yes
Existing Interface Method:    Batch
Proposed Interface Method:    Batch

System Interface with:
      Agency: Department of Human Services Child Support Division
      System: Tennessee Child Support Enforc ement System (TCSES)

Purpose of the interface
      To inform the caseworker of any applicable updates to a Families First caretaker (custodial
      parent) or child (dependent ) processed in TCSES. When applicable, the system shall be
      updated with the information coming from TCSES. An example would be if the custodial parent
      is not cooperating, the Child Support worker would enter non -cooperation information into
      TCSES. When the TCSES file is processed, the system will update the case and generate an
      alert to the caseworker.
Platform
        Hardware: IBM Mainframe, Server, PC
        Software: Advantage Gen, COB OL, DB2 Connect, PC Forms, IMS DC
        Database: DB2
        Operating System: z/OS V1.4, Multiple PC OS
Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

    7.2 Tennessee Department of Human Services Child Support Enforcement System
                        (TCS ES) Information on Absent Parent


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: Department of Human Services Child Support Division
      System: Tennessee Child Support Enforc ement System (TCSES)

Purpose of the interface
      To alert the DHS caseworker of any applicable updat es to a Non -Custodial Parent (Absent
      Parent), such as an address change.
        Specified absent data received from the Tennessee Child Support Enforcement System
        (TCSES ) shall automatically populate the absent parent data on the new system. Verification
        data will be updated to indicate that the information was received from TCSES.

        The system will determine if an absent parent is also head of his/her own assistance group. If
        an absent parent is also head of his/her own Family Assistance (FA) case and the individual's
        case address is different that the absent parent address, an alert will be generated to the worker.

        The system will determine if the address of an absent parent is the same as the caret aker of the
        Families First (FF) case. If the address is the same, an alert will be generated for the worker.


Platform
        Hardware: IBM Mainframe, Server, PC
        Software: Advantage Gen, COB OL, DB2 Connect, PC Forms, IMS DC
        Database: DB2
        Operating System: z/OS V1.4, Multiple PC OS

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

    7.3 Tennessee Department of Human Services Child Support Enforcement System
                       (TCS ES) Redetermination Notice Extract


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch
System Interface with:
      Agency: Department of Human Services Child Support Division
      System: Tennessee Child Support Enforc ement System (TCSES)

Purpose of the interface
      To inform the caseworker of a possible need for re -determination of eligibility on the custodial
      parent's Families First case. If the monthly distribution process in TCSES determines that
      collections are equal to or great er than the obligation, and the obligation is greater than the
      deficit, this may indicate that the caseworker should re -determine the Families First case
      eligibility. An alert is generated to the user and a report is generated.

Platform
        Hardware: IBM Mainframe, Server, PC
        Software: Advantage Gen, COB OL, DB2 Connect, PC Forms, IMS DC
        Database: DB2
        Operating System: z/OS V1.4, Multiple PC OS

Existing process for sending/receiving data
        Monthly Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

    7.4 Tennessee Department of Human Services Child Support Enforcement System
                (TCS ES) Child Support Pa ss-through Payment (TCS ES)


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: Department of Human Services Child Support Division
      System: Tennessee Child Support Enforc ement System (TCSES)

Purpose of the interface
      On a monthly basis, a file containing child support pass -through payments is received from the
      Tennessee Child Support Enforcement System (TCSES). These payments are processed in a
      monthly mass change. This monthly mass change includes posting the pass -through payments
      to the individual who rec eived child support monies, and the automatic recalculation of Food
      Stamp benefits to include the additional monies. All changes that affect an assistance group's
      eligibility or benefit amount result in an aut omated notice being generated and sent to the
      assistance group. When a case that has been selected for update cannot be updated via mass
      change, an alert is sent to the assigned worker with instructions to update the case online. Mass
      change reports that identify cases that were mass changed and were not mass changed are
      generated.

Platform
        Hardware: IBM Mainframe, Server, PC
        Software: Advantage Gen, COB OL, DB2 Connect, PC Forms, IMS DC
        Database: DB2
        Operating System: z/OS V1.4, Multiple PC OS

Existing process for sending/receiving data
        Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

    7.5 Tennessee Department of Human Services Child Support Enforcement System
                    (TCS ES) B3/B5 (Exceeds and Adjustments) File


Existing Interface:            Yes
Existing Interface Method:     Batch
Proposed Interface Method:     Batch

System Interface with:
      Agency: Department of Human Services Child Support Division
      System: Tennessee Child Support Enforc ement System (TCSES)

Purpose of the interface
      To notify the caseworker of monthly excess collections (B3) and adjustments (B5) to collections
      amounts An alert is generat ed to the casework er and a report is produced.

Platform
        Hardware: IBM Mainframe, Server, PC
        Software: Advantage Gen, COB OL, DB2 Connect, PC Forms, IMS DC
        Database: DB2
        Operating System: z/OS V1.4, Multiple PC OS

Existing process for sending/receiving data
        Monthly Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

    7.6 Tennessee Department of Human Services Child Support Enforcement System
              (TCS ES) Families First or Medicaid Referral to Child Support


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: Department of Human Services Child Support Division
      System: Tennessee Child Support Enforc ement System (TCSES)

Purpose of the interface
      To inform the Child Support worker of any new eligible Families First or Medicaid case or
      referable changes to active Families First or Medicaid cases.

Platform
        Hardware: IBM Mainframe, Server, PC
        Software: Advantage Gen, COBOL, DB 2 Connect, PC Forms, IMS DC
        Database: DB2
        Operating System: z/OS V1.4, Multiple PC OS

Existing process for sending/receiving data
        Daily and Mass Change Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

    7.7 Tennessee Department of Human Services Child Support Enforcement System
                         (TCS ES) Families First I ssuance File


Existing Interface:           Yes
Existing Interface Method:    Batch
Proposed Interface Method:    Batch

System Interface with:
      Agency: Department of Human Services Child Support Division
      System: Tennessee Child Support Enforc ement System (TCSES)

Purpose of the interface
      To send TCSES the monthly Families First grant amount and budget dat a for TCSES to use in
      determine the Families First deficit amount.

Platform
        Hardware: IBM Mainframe, Server, PC
        Software: Advantage Gen, COB OL, DB2 Connect, PC Forms, IMS DC
        Database: DB2
        Operating System: z/OS V1.4, Multiple PC OS

Existing process for sending/receiving data
        Monthly Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE



    7.8 Tennessee Department of Human Services Child Support Enforcement System
                  (TCS ES) Child Support Enforcement Inquiry (TCSES )


Existing Interface:             No
Existing Interface Method:      None
Proposed Interface Method:      On Line Real Time

System Interface with:
      Agency: Department of Human Services Child Support Division
      System: Tennessee Child Support Enforc ement System (TCSES)
Purpose of the interface
       Specified individual applying for assistance and specified individuals for whom a S SN is being
       added or changed shall be matched on-line real time against the Tennessee Child Support
       Enforcement System (TCSES) data base. The match is to assist the worker in determining if an
       individual/state is receiving child support payments from an absent parent and/or if an individual
       has an in-state court order to pay child support and/or alimony. Specified individuals will also be
       matched at reverification. If a match is found, a match result/segment and a worker In-Box match
       notification shall be generated. If an individual/state is receiving absent parent payments, a
       match result/segment containing data regarding the last date monies was received from an
       absent parent shall be generated. If an individual has a court order to pay child support and/or
       alimony, a match result/segment contain the court data shall be generated. The system shall
       record when a match is not found.


Platform
        Hardware: IBM Mainframe, Server, PC
        Software: Advantage Gen, COB OL, DB2 Connect, PC Forms, IMS DC
        Database: DB2
        Operating System: z/OS V1.4, Multiple PC OS

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

    7.9 Tennessee Department of Human Services Child Support Enforcement System
                     (TCS ES) Child Support Reimbursement Data


Existing Interface:            No
Existing Interface Method:     None
Proposed Interface Method:     On Line Real Time

System Interface with:
      Agency: Department of Human Services Child Support Division
      System: Tennessee Child Support Enforc ement System (TCSES)

Purpose of the interface
       This interface will be used to report the collections and benefit levels that have been reimbursed
       to the Federal Child Support Enforc ement system. The purpose of the Interface is to adjust the
       claim balanc e based on the Child Support reimbursement amount. This interface will result in an
       ongoing update to the claim balance based on the client‟s payments as well as the Child support
       payments.

Platform
        Hardware: IBM Mainframe, Server, PC
        Software: Advantage Gen, COB OL, DB2 Connect, PC Forms, IMS DC
        Database: DB2
        Operating System: z/OS V1.4, Multiple PC OS

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

   8.1 Tennessee Department of Childrens Services TnKids IV-E and Medicaid Eligibility
                                     Determination


Existing Interface:              No
Existing Interface Method:       None
Proposed Interface Method:       On Line Real Time

System Interface with:
      Agency: Department of Children‟s Services (DCS)
      System: TNK IDS

Purpose of the interface
      Financial, resource, household composition and demographic information must be transmitted
      from the TNK IDS system at the Department of Children‟s Services via an on-line interface when
      a child is taken into state custody. A Child Welfare Benefits Worker will receive an alert, verify
      the information transmitted and proceed to determine the child‟s eligibility through V.I.P. The
      child‟s eligibility for Immediate Medicaid eligibility, IV-E Adoption Assistance and IV-E Foster
      Care, State Funded Adoption Assistance and IV -D childc are is determined through the
      Department of Human Services new eligibility determination system.
        DCS Referral information from the SACWIS TNK IDS System and eligibility results, including
        status changes, from the V.I.P. System shall be exchanged through an online, real-time, robust
        (bi-directional) interface. TNK IDS is the database of record for IV -E client data. DCS case
        manager staff shall record and update the client information in TNK IDS before re ferral
        information for IV-E is transmitted to the V.I.P. DCS defines the user roles and business rules
        for data validation in TNKIDS. All data necessary for the initial determination and subs equent re -
        determination of title IV-E eligibility is captured and validat ed in TNK IDS and sent to V.I.P
        through the online real-time int erface.

        If data is recorded incorrectly in TNKIDS resulting in an incorrect eligibility decision in the V.I.P,
        the TNK IDS case manager shall be notified to update the client information. The corrected
        information will be transmitted to the V.I.P. through the online real -time interface and processed
        for immediate results. The V.I.P System shall dynamically re-calculat e eligibility as the values of
        pertinent factors change.

        TNKIDS shall collect required information regarding reasonable efforts and shall send a Legal
        Basis indicator to V.I.P. to indicate that the client has passed/ failed the reasonable efforts test.
        This indicator shall be used to support business rules for the IV -E population in the V.I.P system.

        The V.I.P system shall capture and age all IV -E pending applications, reapplications and client
        status changes and shall also have the ability to generate and escalate alerts based on the IV -E
        eligibility requirements.

        The V.I.P system shall have the capability to override IV-E eligibility determination and is to be
        used only if new or changing system functionality can not be implemented on time and to allow
        eligibility processing to be performed manually using the override capability until the functionality
        change is completed. Through the use of a security role, only limited management personnel
        shall have this capability.

        The V.I.P system will retain the TNKIDS information that is necessary for IV -E eligibility
        determination and will retain all history of case and client changes. Since TNK IDS is the
        database of record, dat a transmitted from TNK IDS will be read -only in the V.I.P. All changes to
        that data must be made in TNKIDS and transmitted to the V.I.P. to ens ure data consistency in
        these two systems.
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

Platform
        Hardware: SUN and Intel
        Software: PowerBuilder 8.03 and EA Studio v4.2.3
        Database: Oracle
        Operating System: Solaris and Windows

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

    8.2 Tennessee Department of Childrens Services TnKids V.I.P. Interface to TNKIDS


Existing Interface:            No
Existing Interface Method:     None
Proposed Interface Method:     On Line Real Time

System Interface with:
      Agency: Department of Children‟s Services
      System: TNK IDS

Purpose of the interface
      To notify the Department of Children‟s Services that the Department of Human Services has
      completed determining the eligibility IV-E Adoption Assistance, IV-E Foster Care, State Funded
      Adoption Assistance and IV -D child care on a child that has been taken into custody by the
      Department of Children‟s Services, and updat e TNK IDS with the res ults of the eligibility
      determination.
       DCS Referral information from the SACWIS TNK IDS System and eligibility results, including
       status changes, from the V.I.P. System shall be exchanged through an online, real-time, robust
       (bi-directional) interface. TNK IDS is the database of record for IV -E client data.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

 9.1 Tennessee Department of Finance and Administration Payments to STARS (State of
                   Tennessee Accounting and Reporting System)


Existing Interface:            Yes
Existing Interface Method:     Batch
Proposed Interface Method:     Batch

System Interface with:
      Agency: Department of Finance and Administration
      System: STA RS

Purpose of the interface
      The purpose of the interface is to send approved Child Care payment records to STA RS for
      vendor payment. Warrants are printed by S TARS and the vendor payment and history files are
      updated with warrant number.
       STA RS returns a record which will be used to update the V.I.P system information related to the
       processed payments.

Platform
        Hardware: Mainframe
        Software: Cobol
        Database: IMS
        Operating System: ZOS 1.4

Existing process for sending/receiving data
        Batch File
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

 9.2 Tennessee Department of Finance and Administration Payments to STARS (State of
 Tennessee Accounting and Reporting System) Families First Financial Transaction s to
                                      STARS


Existing Interface:            No
Existing Interface Method:     Manual Entry
Proposed Interface Method:     Batch

System Interface with:
      Agency: Department of Finance and Administration
      System: STA RS - State Accounting and Reporting System

Purpose of the interface
      The purpose of the interface is to send Families First Provider payments from the new system to
      STA RS for payment. These payments will include specified Transportation payments and
      specified Support Services payments.
       STA RS in return will return the payment information for system update.

Platform
        Hardware: IBM Mainframe
        Software: IMS, Cobol
        Database: IMS
        Operating System: z/OS V1.4

Existing process for sending/receiving data
        Manual Entry
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

        9.3 Tennessee Department of Finance and Administration RACF Validation


Existing Interface:           Yes
Existing Interface Method:    Batch
Proposed Interface Method:    Batch

System Interface with:
      Agency: Department of Finance and Administration (OIR)
      System: Unknown

Purpose of the interface
      The Department of Hum an Services receives an Info Pac report (USERPE RS), a file from
      Department of Finance and Administration. The Department of Human Services uses that report
      to set all system user IDs that are not in us e to inactive status.

Platform
        Hardware: IBM Mainframe
        Software: RACF
        Database:
        Operating System: z/OS V1.4
Existing process for sending/receiving data
        Info Pac report
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                 10.1 Department of Human Services Clearinghouse System


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       On Line Real Time, Batch

System Interface with:
      Agency: DHS
      System: Clearinghouse
Purpose of the interface

 Tennessee Clearinghouse is a DHS application consisting of a group of dat abases organized under a
single main menu, permitting access through batch interface and also via a statewide on-line inquiry
system. The databases available for inquiry include Wage (by quart er), Unemployment, New Hire, SSI
Eligibles (SDX), and US Department of Agriculture Disqualified Recipients. A pass -through transaction
available through the main menu directly queries a Birth database maint ained by the Department of
Healt h and returns and displays birth matches.

The Wage, Unemployment and Federal New Hire data is maintained through updat es from the TDLWD.
The SSI Eligibles information is updated through daily updates from the SSA rec eived over the Connect:
Direct utility. Birth data is obtained by directly accessing the Department of Health‟s Birth Dat abase
(AIRS).

The new system shall interface wit h Cle aringhouse in the following manner:

As applicants are keyed into the system or individuals are added to existing active cases or an SS N is
changed, on-line transactions to Clearinghouse dat abases will be generated. The responses to these
will be immediately present ed to the casework er in form of a match result/segment, providing Wage,
Unemployment Compensation, New Hire, SSI, and Disqualified Recipient data to be us ed in the eligibility
determination processes. Using a pass-through transaction, birth dat a will also be requested and
displayed, as described in 5.1 of this document. An in-box match transaction will be generated to the
work er for each match performed. The system shall record when a match is not found.

The State Clearinghous e is updated with unemployment/new hire information on a weekly basis from the
Department of Employment Security. On a monthly basis, eligible individuals will be matched against the
State Clearinghouse dat a base. If a match is found, a match segment will be creat ed. An alert will be
generated if the calculated amount of monthly unemployment on the unemployment file is different than
the amount in the system. If the calculated amount and the amount on the system is the same, a system
resolved match segment will be generated, and no alert will be issued to the worker.
When new hire data is receive, a match will be generated. The system will alert the worker so that hours
and wages can be verified, and used in the determination of eligibility.
The State Clearinghous e is updated with wage information on a quarterly basis from the Department of
Employment Security. On a quart erly basis, eligible individuals will match against the State
Clearinghouse data base. When clearinghouse is updated, the system will compare by employer number
the earnings for the current quarter to the previous available quarter. If there is a discrepancy greater
than the State of Tennessee tolerance level, an alert and unresolved match will be generated. If the
discrepancy is equal or less then the tolerance level, a system resolved match will be generat ed. A
work er alert will not be generated. If an individual is due for recertification in a given quarter, a match
segment will be created, but the alert shall not be generated until the month bef ore the recertification is
due.

The system will auto-populate the Unemployed Parent work quarter grid wit h wages from the
Clearinghouse system as part of this interface.
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

Platform
        Hardware: IBM Mainframe
        Software: IMS
        Database: IMS
        Operating System: z/OS V1.4

Existing process for sending/receiving data
        Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

  11.1 Tennessee Department of Human Services Di sability Determination System (DDS )


Existing Interface:              No
Existing Interface Method:       None
Proposed Interface Method:       On Line Real Time

System Interface with:
      Agency: Disability Determination Section (DDS)
      System: VERSA

Purpose of the interface
      Medical social information will be gathered on an individual, and will generate an electronic
      referral to DDS. DDS will return the decision status of that individual.
        At the time DDS updates the disability status, an on-line real time alert shall be generated to the
        worker responsible for the case.


Platform
        Hardware: AS400
        Software: VERSA Application
        Database: Unknown
        Operating System: OS/400

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

 12.1 U.S. Department of Health and Human Services PARIS (Public Assi stance Reporting
                                  Information System)


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch
System Interface with:
      Agency: SSA (Social Security Administration)
      System: PARIS

Purpose of the interface
      The PARIS file is prepared by DHS on a quarterly basis. It is sent to the SSA by Connect: Direct
      and then forwarded to the Department of Defense for matching with other states, VA and
      Federal employment files. The return files are used to det ermine individuals that are receiving
      benefits in more than one state or are not financially eligible to receive benefits.
        The system will process the returned SSA PARIS Int erstate file, the SSA PARIS VA file, and the
        SSA PARIS Federal Benefits file. If a match is found on any of the three files for an individual
        currently receiving benefits, a match result/ segment and an alert will be generated for each type
        match found. The match results will be associated to the individual. A report of found individuals
        will also be generated for each type match.


Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

  12.2 U.S. Department of Health and Human Services Temporary Assi stance for Needy
                      Families (TANF) External Federal Reporting


Existing Interface:           Yes
Existing Interface Method:    Batch
Proposed Interface Method:    Batch

System Interface with:
      Agency: U.S. Department of Health and Human Services (USDHHS)
      System: Administration for Children and Families (ACF) TANF Data Reporting

Purpose of the interface
      To generate and provide data necessary to meet TANF Federal reporting requirements to ACF.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown
Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

12.3 U.S. Department of Health and Human Services Separate State Program -Maintenance
                         of Effort (SSP-MOE) Federal Reporting


Existing Interface:          Yes
Existing Interface Method:   Batch
Proposed Interface Method:   Batch

System Interface with:
      Agency: U.S. Department of Health and Human Services (USDHHS)
      System: Administration for Children and Families (ACF) SSP-MOE Data Reporting

Purpose of the interface
      To generate and provide data necessary to meet SSP-MOE Federal reporting requirements to
      ACF.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

  12.4 U.S. Department of Health and Human Services Temporary Assi stance for Needy
   Families (TANF) and Separate State program-Maintenance of Effort (SSP-MOE) High
              Performance Bonus (HPB) Work Measure s Federal Reporting


Existing Interface:            Yes
Existing Interface Method:     Batch
Proposed Interface Method:     Batch

System Interface with:
      Agency: U.S. Department of Health and Human Services (USDHHS)
      System: Administration for Children and Families (ACF) TANF and SSP -MOE HPB Dat a
      Reporting

Purpose of the interface
      High Performanc e Bonus is a competitive program whereby states may receive enhanced
      funding for good performance in employment and job retention for FF clients. This interfac e
      generates the data necessary to display appropriate Maintenance of Effort to compete in the
      HPB.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

  12.5 U.S. Department of Health and Human Services Temporary Assi stance for Needy
Families (TANF) High Performance Bonus-Medicaid and State Children’s Health Insurance
                           Program (SCHIP) Federal Reporting


Existing Interface:            Yes
Existing Interface Method:     Batch
Proposed Interface Method:     Batch

System Interface with:
      Agency: U.S. Department of Health and Human Services (USDHHS)
      System: Administration for Children and Families (ACF) TANF HPB Data Reporting

Purpose of the interface
      High Performanc e Bonus is a competitive program whereby states may receive enhanced
      funding for good performance in the areas of placing clients in employment and keeping them
      there. This interface extracts and correlat es the data necessary to participate in the HPB
      program.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

12.6 U.S. Department of Health and Human Services Child Care Case -Level Federal Report
                                      (ACF-801)


Existing Interface:           Yes
Existing Interface Method:    Batch
Proposed Interface Method:    Batch

System Interface with:
      Agency: U.S. Department of Health and Human Services (USDHHS) – Administration of
      Children and Families (A CF) – Child Care Bureau
      System: Child Care and Development Fund Submission of Case-Level Reporting (A CF-801)

Purpose of the interface
      To provide case-level Child Care program information for the Child Care and Development Fund
      (ACF-801) Federal report.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

           13.1 Uni versity of Tenne ssee Center for Busine ss/ Economic Re search


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch
System Interface with:
      Agency: University of Tennessee Center for Business/Economic Research
      System: Admiral
Purpose of the interface
      The individual extract, case extract, case applications extract and PRP extract are provided by
      Families First to the University of Tennessee Center for Business/Economic Research on a
      monthly basis for independent analysis of data on the new system.

Platform
        Hardware: Micron 4-processor
        Software: DataJunction 6.5 (for exporting EBCDIC files to Microsoft SQL Server )
        Database: Microsoft SQL Server 7.0
        Operating System: Windows NT SP 6a
Existing process for sending/receiving data
        Monthly Batch / Physical Tape Exchange, Fixed Block EBCDIC
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                          14.1 Tennessee Department of Correction


Existing Interface:             No
Existing Interface Method:      None
Proposed Interface Method:      On Line Real Time

System Interface with:
      Agency: Tennessee Department Correction
      System: TOMIS (Tennessee Offenders Management Information System)


Purpose of the interface
       Individuals applying for assistance and individuals for whom a SSN is being added or changed
      shall be matched on-line real time against the DHS TOMIS file. If a match is found, a match
      result/segment and a worker In-Box match notification shall be generated. The system shall
      record when a match is not found.

       A file is received monthly from the Department of Correction. The system will process file from
       the Department of Corrections. If a match is found for an individual currently receiving benefits, a
       match result/segment and alert will be generated for the work er. A report of all individuals for
       whom a match was found will also be generat ed.


Platform
        Hardware: IBM Mainframe
        Software: CICS, COB OL, INS TALL/1
        Database: DB2
        Operating System: z/OS V1.4


Existing process for sending/receiving data
       None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

       15.1 Tennessee State Services Portal – Self-Screening and Application Filing


Existing Interface:              No
Existing Interface Method:       None
Proposed Interface Method:       On Line Real Time
System Interface with:
      Agency: State Office for Information Resources
      System: State Portal
      Purpose of the interface
      The State has established a State Service Portal to provide a single access point that functions
      as an interactive information and trans action gateway to improve the way citizens and
      businesses access State government services and information over the internet. It is State
      policy that all internet services provided to citizens and businesses shall go through this portal.

        The State's citizens will access the State Service Portal via the Internet to perform two V.I.P
        process functions: Eligibility Screening for Family Assistance Programs and Filing an In ternet
        Application for these programs.


Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

15.2 Tennessee State Services Portal – Childcare Enrollment Attendance and Verification
                                         (EAV)


Existing Interface:            No
Existing Interface Method:     None
Proposed Interface Method:     On Line Real Time
System Interface with:

       Agency: State Office for Information Resources
       System: State Portal
       Purpose of the interface
       Child Care providers have the capability currently to register with the State Portal to complete
       and submit a billing document called an EAV on line. A file of Child Care providers that have
       registered will be sent to V.I.P. The V.I.P. system will send a file of Child Care provider's EAV
       information to the State Port al so the providers can complete and submit the EAVs on line. The
       State Portal will send a file of the completed EAVs to V.I.P. for payment processing.


Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                             16.1 Tennessee Department of Safety


Existing Interface:             No
Existing Interface Method:      None
Proposed Interface Method:      On Line Real Time

System Interface with:
      Agency: Tennessee Department of Safety
      System: Title and Vehicle Registration
Purpose of the interface
      To obtain vehicle ownership and registration data for use in verifying data us ed in determining
      eligibility for Family Assistance programs.

        Individuals applying for assistance and individuals for whom a SSN is being added or changed
        shall be matched on-line real time against the Department of Safety data base. If a match is
        found, a match result/segment and a worker In -Box match notific ation will be generated. The
        System shall also record if a match is not found.


Platform
        Hardware: IBM Mainframe
        Software: IMS, COBOL
        Database: IMS, DB2
        Operating System: z/OS V1.4

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                             17.1 Tennessee State University


Existing Interface:           Yes
Existing Interface Method:    Report
Proposed Interface Method:    File

System Interface with:
      Agency: Tennessee State University
      System: N/A
Purpose of the interface
      A file of Food Stamp Demographics Trends by County will be produced on a monthly basis and
      will provide demographic information concerning individuals in Food Stamp Cases.


Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        Monthly Report
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                18.1 Tennessee Department of Mental Retardation Services


Existing Interface: No
Existing Interface Method:
Proposed Interface Method:

System Interface with:
      Agency: Department of Mental Retardation Services
      System: New System Development

Purpose of the interface
       An automated referral from the Department of Mental Ret ardation Services (DMRS) for home
       and community based individuals. When the Pre -Admission E valuation (PAE) packet is
       approved, A DMRS referral will be sent for the determination of Medicaid financial liability for
       Home and Community based services.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE




             19.1 Tennessee State Comptroller’s Office Tax Relief Data Sample


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Tennessee State Comptroller‟s Office
      System: Tax Relief

Purpose of the interface
      A monthly file to verify the most current SSI information for a sample of Tax Relief eligible
      individuals.

Platform
        Hardware: Client Server based
        Software: Visual Basic 6.0
        Database: Oracle 9.x
        Operating System: Windows (compatible with Windows 2000 and Windows XP)

Existing process for sending/receiving data
        Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

20.1 Electronic Benefit Transfer (EBT) Vendor Families First and Food Stamp Case Set-up


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: EBT Vendor
      System: EBT

Purpose of the interface
      To trans fer files for FF and FS programs to the EB T Vendor for the purpose of setting up and
      maintaining their EB T case or account.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

  20.2 Electronic Benefit Transfer (EBT) Vendor Families First and Food Stamp Benefits
                                      Authorization


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: EBT Vendor
      System: EBT

Purpose of the interface
      To trans fer files for FF and FS daily and monthly benefits to the EBT Vendor for the purpose of
      issuing benefits to clients.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

           20.3 Electronic Benefit Transfer (EBT) Vendor Child Care Case Set-up


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: EBT Vendor
      System: EBT

Purpose of the interface
      To trans fer files for Child Care to the EB T Vendor for the purpose of setting up and maintaining
      the client‟s child care EBT case. Tennessee is planning to expand the EB T program to include
      Child Care Attendance but at this time this expansion has not been designed by Tennessee or
      the EBT Vendor. An EBT Card could be issued to a parent when the parent is deemed eligible
      for child care assistance. The EB T card would be used to relay information to the provider
      regarding the parent‟s out-of-pocket responsibility and the state‟s contribution when the EB T
      card is swiped on a POS device at the child care cent er. The information from the card swipe on
      the child‟s arrival and departure times from the child care center would be used to determine
      payment amounts and attendance irregularities. The location of the card swipe could be
      recorded by EBT and populate in the new system.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

      20.4 Electronic Benefit Transfer (EBT) Vendor Child Care Ti me and Attendance


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: EBT Vendor
      System: EBT

Purpose of the interface
      To trans fer files for Child Care to the EB T Vendor for the purpose of reporting child care time
      and attendance. Tennessee is planning to expand the EBT program to include Child Care
      Attendance but at this time this expansion has not been designed by Tennessee or the EB T
      Vendor. An EBT Card could be issued to a parent when the parent is deemed eligible for child
      care assistance. The EBT card would be used to relay information to the provider regarding the
      parent‟s out-of-pocket responsibility and the state‟s contribution when the EBT card is swiped on
      a POS devic e at the child care center. The information from the card swipe on the child‟s arrival
      and departure times from the child care center would be used to determine payment amounts
      and attendance irregularities. The location of the card swipe could be recorded by EB T and
      populate in the new system.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

    20.5 Electronic Benefit Transfer (EBT) Vendor Families First Services Ca se Set-up


Existing Interface:            Yes
Existing Interface Method:     Batch
Proposed Interface Method:     Batch

System Interface with:
      Agency: EBT Vendor
      System: EBT

Purpose of the interface
      To trans fer files for Families First Services for the purpose of case setup and maintenance.
      Tennessee is planning to ex pand the EB T program to include Families First Services attendance
      but at this time, this expansion has not been designed by Tennessee or the EB T Vendor. When
      each is designed the process will need to be modified to support this expansion of the EB T
      program. In practical terms, an EBT Card could be issued when a person is assigned activities
      to perform as part of the person‟s PRP (Personal Responsibility Plan). The EB T card would be
      used to relay information to the provider regarding the person‟s attending the activity.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

20.6 Electronic Benefit Transfer (EBT) Vendor Families First Services Time and Attendance


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: EBT Vendor
      System: EBT

Purpose of the interface
      To trans fer files for Families First Services to the EB T Vendor for the purpose of Time and
      Attendance. Tennessee is planning to expand the EBT program to include Families First
      Services attendance but at this time, this expansion has not been designed by T ennessee or the
      EBT Vendor. When each is designed the process will need to be modified to support this
      expansion of the EB T program. In practical terms, an EB T Card could be issued when a person
      is assigned activities to perform as part of the person‟s PRP (Personal Res ponsibility Plan). The
      EBT card would be used to relay information to the provider regarding the person‟s attending the
      activity

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                 20.7 Electronic Benefit Transfer (EBT) Vendor Return Files


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: EBT Vendor
      System: EBT

Purpose of the interface
    This process uses the various transmissions of data from the EBT vendor and posts information to
    V.I.P. and prepares notices and sends these notices to the clients. These various transmissions of
    data are:
     Aged Benefits – Each issued benefit/authorization, to the client, that still has an open remaining
                      balance is aged on last date used. The aging categories are 30, 60 and 90 days
                      of no activity on each of the authorizations. Any authorizations in the 90-day
                      category also represent those authorizations that the EBT vendors has removed
                      from the client‟s EBT case on the Vendor‟s database and need to be posted to
                      the Issuance History as a returned benefit. Any authorizations in the 60-day
                      category will need to have aged notices sent to the client informing the client that
                      this benefit has had no activity for 60 days and will be removed from the EB T
                      Vendors database if this benefit reaches 90 days with no activity.

    Swept Accounts – Thes e are EBT FS Authorized Reps and/or EBT Cash Protective Payees and/ or
                     EBT cases that the EBT vendor has removed from the EB T databas e because
                     the client record has had no activity for 365 days.
    Daily EBT Client History – These are the transactions that access an EBT Case Number on a given
                      day. These transactions include all the transactions that the client creates by
                      using an A TM or POS device. The EB T Vendor only provides this file on a daily
                      basis.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        CONNE CT:DIRECT
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE


21.1 Tennessee Department of Human Services Child Care Management System (TCCMS)


Existing Interface:              No
Existing Interface Method:       No
Proposed Interface Method:       On Line Real Time

System Interface with:
      Agency: DHS
      System: TCCMS (Tennessee Child Care Management System)

Purpose of the interface
      To access Child Care licensing information on line real time for the purpose of enrolling eligible
      children into Child Care facilities that are in compliance with Federal laws.
        Also, specified individuals applying for assistance or for whom a SSN is being added or changed
        shall be matched on-line real time against the Tennessee Child Care Management System
        (TCCMS). Data bas e. The match is to assist the worker in determining if an individual is a child
        care provider, dates child care was received, and amounts received. Individuals will also be
        matched at reverification. If a match is found, a match result/segment and a work er In-B ox
        match notification shall be generated. The system shall record if a match is not found.

Platform
        Hardware: SUN
        Software: Oracle forms/Cobol
        Database: Oracle
        Operating System: Solaris

Existing process for sending/receiving data
        Daily Batch.
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                   22.1 BellSouth, Sprint, Citizens Monthly Lifeline Match


Existing Interface:            Yes
Existing Interface Method:     Batch
Proposed Interface Method:     Batch

System Interface with:
      Agency: DHS
      System: V.I.P.

Purpose of the interface
      Some telephone companies in Tennessee offer discount or reduction on telephone services
      called “Lifeline” to individuals on TANF, Food Stamp, or Medicaid. The telephone companies
      send DHS files of applicants who applied for the discount. DHS verifies that the Lifeline
      applicants are recipients of TANF, FS, or MA benefits.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        Physical File Exchange (CD)
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE


23.1 U.S. Department of Homeland Security Systematic Alien Verification for Entitlements
                                   System (SAV E)


Existing Interface:              Yes
Existing Interface Method:       Manual
Proposed Interface Method:       On Line Real Time

System Interface with:
      Agency: Department of Homeland Security
      System: SAVE - Systematic Alien Verification for Entitlements System

Purpose of the interface
      The purpose of this interface is to verify an alien's immigration status by validating the alien's
      INS documents through the Department of Homeland Security.
       Specified us ers shall be able to inquire on -line real time inquiry into the SAVE system.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

               24.1 Tennessee Department of Education Free Lunch Interface


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: Tennessee Department of Education (TDE )
      System: File trans fer

Purpose of the interface
      A monthly file to provide the TDE with a file of school age Children on Families First and Food
      Stamps. TDE distributes the file to schools in Tennessee. Children on the file qualify for the Free
      Lunch Program.

Platform
        Hardware: Mainframe
        Software: SAS
        Database: none
        Operating System: ZOS

Existing process for sending/receiving data
        File Transfer Protoc ol (FTP)
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                       25.1 Bureau of TennCare Medicaid Eligibility File


Existing Interface:              Yes
Existing Interface M ethod:      Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A TennCare Medicaid eligibility file is produced daily, monthly and at mass change for
      TennCare, and provides individual demographic and TennCare Medicaid eligibility information.
      This file is the vehicle to establish coverage periods for TennCare Medicaid recipients who have
      been processed. Records are produced when new periods of TennCare Medicaid eligibility are
      added, when ongoing periods of TennCare Medicaid eligibility are ended, when modifications
      are made, when auxiliary benefits are issued, when cases are transferred to another county, and
      when cases are reinstated.

        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.

        This file may be consolidat ed with the current TennCare Medicaid Patient Liability file, the
        TennCare Medicaid Medical E valuation Unit Interim Benefits (MEU) file, and the TennCare
        Standard Referral file.

        Individuals who were denied for TennCare Medicaid and ineligible caretakers of a TennCare
        Medicaid case shall be added to this file.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9. 2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch.
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                   25.2 Bureau of TennCare Third Party Liability (TPL) File


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A TennCare Third Party Liability file (TPL) is produced for TennCare and provides provider
      information about medical insurance coverage for individuals in TennCare Medicaid and
      TennCare Standard cases.

        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on-line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

  25.3 Bureau of TennCare Medicaid Medical Evaluation Unit Interim Benefits (MEU) File


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A TennCare Medicaid Medical E valuation Unit Interim Benefits (MEU) file is produced daily for
      TennCare and provides information on MEU interim benefit recipients. Records are generated
      when MEU interim benefits are requested to begin, change, stop, or be replaced.

        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.

        This file may be consolidat ed with the current TennCare Medicaid Eligibility file, the TennCare
        Medicaid Patient Liability file, and the TennCare Standard Referral file.

        Individuals who were denied for TennCare Medicaid and ineligible caretakers of a TennCare
        Medicaid case shall be added to this file.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                        25.4 Bureau of TennCare Medicaid Benefits File


Existing Interface:               Yes
Existing Interface Method:        Batch
Proposed Interface Method:        Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A Medicaid Benefits file is produced daily and monthly for TennCare and identifies recipients
      eligible for TennCare Medic aid benefits.

        This file is only used by TennCare to issue client ID cards for Qualified Medicare Beneficiary
        (QMB). This file may be eliminated, if TennCare can use the TennCare Medicaid Eligibility file to
        determine the QMB individuals that need ID cards.

        If this file is not eliminated, it shall be in the Health Insurance Portability & Accountability Act
        (HIPAA) standard 834 record layout plus a companion record wit h additional information.


Platform
        Hardware: Client/Server architecture with the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily and Monthly Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                    25.5 Bureau of TennCare Medicaid Reconciliation File


Existing Interface:               Yes
Existing Interface Method:        Batch
Proposed Interface Method:        Batch
System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A TennCare Reconciliation file is produced monthly for TennCare and includes all current
      TennCare Medicaid eligible recipients. The file is intended to keep eligibility information
      synchronized.

        This file may be eliminat ed if the daily Medicaid files were processed in a tim ely manner at
        TennCare.

        If this file is not eliminated, it shall be in the Health Insurance Portability & Accountability Act
        (HIPAA) standard 834 record layout plus a companion record wit h additional information.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily and Monthly Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

              25.6 Bureau of TennCare Medicaid 1610 Manual Transaction File


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A TennCare Medicaid 1610 Manual Transaction file is produced daily for TennCare and provides
      individual eligibility information that cannot be processed through the normal daily TennCare
      Medicaid eligibility file. Rec ords are generated when TennCare Medicaid eligibility is started,
      changed or stopped.

        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.

        This manual transaction shall be made available for the TennCare Standard cases as well as the
        TennCare Medicaid cases.

        This information shall be stored on the new system, and the capability shall be available to
        generate notices for the transactions.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                   25.7 Bureau of TennCare Medicaid Patient Liability File


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A TennCare Medicaid patient liability file is produc ed daily, mont hly, and at mass change for
      TennCare and identifies TennCare Medicaid recipients who are responsible for reimbursing
      some nursing home charges. Records are produced when patient liability is newly authorized,
      when patient liability is modified and when patient liability ends.

        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.

        This file may be consolidat ed with the current TennCare Medicaid Eligibility file, the TennCare
        Medicaid Medical E valuation Unit Interim Benefits (MEU) file, and the TennCare Standard
        Referral file.

        Individuals who were denied for TennCare Medicaid and ineligible caretakers of a TennCare
        Medicaid case shall be added to this file.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily, Monthly and Mass Change Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                       25.8 Bureau of TennCare Standard Referral File


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A TennCare Standard referral file is produced on a daily basis and at mass change for
      TennCare, and provides individual demographic/eligibility inf ormation for all individuals in a
      TennCare Standard family group. This file is a vehicle to establish coverage for TennCare
      Standard and Medically Eligible recipients who have been processed. Records are produced
      when individuals have been denied or approved for the two categories of TennCare Standard,
      when individual coverage for the two categories have ended, when modifications have been
      made to the TennCare Standard family group, when auxiliary benefits are issued, when family
      groups are trans ferred to another county, and when family groups are reinstated.

        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.

        This file may be consolidat ed with the current TennCare Medicaid Patient Liability file, the
        TennCare Medicaid Patient Liability file, and the TennCare Medicaid Medical E valuation Unit
        Interim Benefits (MEU) file.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily and Mass Change Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                      25.9 Bureau of TennCare Standard Response File


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange

Purpose of the interface
      A TennCare Standard Respons e file is produc ed on a daily basis by TennCare, and includes
      information on how TennCare responded to the TennCare Standard referrals to TennCare,
      whet her TennCare accepted the response or reversed the referral back as unacceptable. It
      includes such information as eligibility begins and end dates, reas on why TennCare did not
      process an individual, and date premium was paid. The file is processed by DHS, resulting in
      updates to begin and end dates for individuals, automatic closure of family groups for specific
      reasons, or generation of alerts for the caseworkers.
       This file may be consolidated with the new TennCare Medicaid response file.
        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                     25.10 Bureau of TennCare Standard Syntax Error File


Existing Interface:               Yes
Existing Interface Method:        Batch
Proposed Interface Method:        Batch
System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A TennCare Standard Syntax error file is produced on a daily basis by TennCare. This file
      contains TennCare Standard referral records that were rejected by TennCare as syntax errors
      and the reas on for the rejection. The file is processed by DHS and reports are created that are
      used by Systems and Policy personnel to resolve the errors that resulted in the rec ords being
      rejected

        Since DHS is determining the eligibility for TennCare Standard and will be generating the notices
        for TennCare Standard recipients, TennCare shall rarely, if ever, override an approval referral
        from DHS for TennCare Standard eligibility with a syntax error.

        This interface may be eliminat ed if more edits are created to assure the information on the
        referral is accurate. DHS needs to work with TennCare on these edits for the new system to
        eliminate the different types of syntax errors and possibly the file. The new TennCare Standard
        Referral Error file may replace this file.

        If this file is not eliminated, it shall be in the Health Insurance Portability & Accountability Act
        (HIPAA) standard 834 record layout plus a companion record wit h additional information.
Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                   25.11 Bureau of TennCare Standard Eligibility Error File


Existing Interface:               Yes
Existing Interface Method:        Batch
Proposed Interface Method:        Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A TennCare Standard Eligibility error file is produced on a daily basis by TennCare. This file
      contains TennCare Standard referral records that were rejected by TennCare as eligibility errors
      and the reas on for the rejection. The file is processed by DHS and reports are c reated that are
      used by Systems and Policy personnel to resolve the errors that resulted in the rec ords being
      rejected.

        Since DHS is determining the eligibility for TennCare Standard and will be generating the notices
        for TennCare Standard recipients, TennCare shall rarely, if ever, override an approval referral
        from DHS for TennCare Standard eligibility with an eligibility error.

        This interface may possibly be eliminat ed if more edits are created to assure the information on
        the referral is accurate. DHS needs to work with TennCare on these edits for the new system to
        eliminate the different types of eligibility errors and possibly the file. The new TennCare
        Standard Referral Error file may replace this file.

        If this file is not eliminated, it shall be in the Health Insurance Portability & Accountability Act
        (HIPAA) standard 834 record layout plus a companion record wit h additional information.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                      25.12 Bureau of TennCare Immediate Eligibility File


Existing Interface:               Yes
Existing Interface Method:        Batch
Proposed Interface Method:        Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange

Purpose of the interface
      A TennCare Immediate Eligibility file is produc ed on a daily basis for TennCare an d provides
      eligibility information on the individuals who are eligible for the Immediate Eligibility category of
      Medicaid.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9. 2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                  25.13 Bureau of TennCare Standard Response Error File


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A TennCare Standard Respons e Error file is produced on a daily basis for TennCare and reflects
      why TennCare‟s responses to individuals sent to TennCare on the TennCare Standard referral
      file were rejected.

        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.

        This file may be consolidat ed with the new TennCare Medicaid Response Error File.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on-line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                          25.14 Bureau of TennCare SSN Match File


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A file is received from TennCare containing SSNs of individuals possibly due for closure or that
      have applied for benefits through the Health Department.

        This file is matched at DHS, and a file is creat ed reporting current Medicaid status of the
        individual at DHS. This match will tell TennCare if the individual has re -applied for Medicaid
        through DHS, if they are currently active, or if they have been closed or denied benefits. This
        match file is sent back to TennCare. This process occurs on a daily basis.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on-line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                         25.15 Bureau of TennCare Address Match File


Existing Interface:                Yes
Existing Interface Method:         Batch
Proposed Interface Method:         Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A file is received from TennCare containing a list of individuals and their SSN and address on an
      „on request‟ basis.

        This information is compared to DHS information, and if address is different, it is written to a
        Non-match file. If it matches, it is written to a Match file. All others are written to the error file.
        The match and non-match files are sent back to TennCare.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        On-Request Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                             25.16 Bureau of TennCare Pending File


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange

Purpose of the interface
      A daily pending file is produced for TennCare to be us ed in conjunction with the daily denial file
      to inform TennCare of individuals who registered at DHS. TennCare will extend TennCare
      eligibility for any individual on the file until disposed at DHS. TennCare will not end TennCare
      eligibility for any individual on the file unless later denied at DHS.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU p er box. One box is the on-line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                             25.17 Bureau of TennCare Denial File


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A daily denial file is produced for TennCare to be used in conjunction with the daily pending file
      to inform TennCare of any denial disposition. With this denial file, TennCare will end TennCare
      eligibility for individuals who were extended by the daily pending file.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                           25.18 Bureau of TennCare on Line Match


Existing Interface:              No
Existing Interface Method:       None
Proposed Interface Method:       On Line Real Time

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange

Purpose of the interface
      A front end on-line match with the TennCare system shall be needed when new applicants are
      being added on the new system to capture existing individual TennCare Medicaid, TennCare
      Standard, SSI, and Medicare eligibility information, if the individual exists on the TennCare
      System.
        When a match is found, the individual segment shall be updated with the TennCare
        Medicaid/TennCare Standard/SS I/Medicare eligibility begin and end dates and the type of
        Coverage.
        This on-line match/inquiry shall also be needed at other times during the eligibility determination
        process to provide additional information, such as if a service is not covered due to a limit in
        benefits (e.g. 6 prescriptions per month, 45 days hospital stay, etc). as defined by policy.

Platform
        Hardware: Client/Server architecture wit h the Client ru nning on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9. 2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

        25.19 Bureau of TennCare Managed Care Organization (MCO) Selection File


Existing Interface:              No
Existing Interface Method:       None
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange

Purpose of the interface
      A TennCare Managed Care Organization (MCO) Update file shall be needed on a daily basis
      from TennCare reflecting the final MCO selection for individuals eligible for TennCare Medicaid
      or TennCare Standard. This file shall be proc essed by DHS, and the final selection shall be
      updated on the new system.
        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

      25.20 Bureau of TennCare Medicaid and TennCare Standard Overpayment File


Existing Interface:              No
Existing Interface Method:       None
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare, Program Integrity
      System: Int erchange

Purpose of the interface
      A TennCare Medicaid and TennCare Standard Overpayment file shall be needed daily for
      TennCare reflecting overpayment claim information due to Intentional Program Violation (IPV) or
      Inadvert ent Client Error (ICE ) on individuals in TennCare Medicaid and TennCare Standard
      cases. It shall also be sent if an investigation is requested. Information for estate recovery when
      an institutionalized case is closed due to the death of an individual shall also be on the file.
        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on-line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

  25.21 Bureau of TennCare Medicaid and TennCare Standard Updated Overpayment File


Existing Interface:             No
Existing Interface Method:      None
Proposed Interface Method:      Batch

System Interface with:
      Agency: Bureau of TennCare, Program Integrity
      System: Int erchange

Purpose of the interface
      A TennCare Medicaid and TennCare Standard Updat ed Overpayment file shall be needed daily
      from TennCare reflecting updated overpayment claim information on individuals in TennCare
      Medicaid and TennCare Standard cases. This file shall be processed by DHS, and overpayment
      claim information shall be updated on the new system.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                   25.22 Bureau of TennCare Health Check Vi sit Match File


Existing Interface:              No
Existing Interface Method:       None
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange

Purpose of the interface
      DHS needs to know if a health check visit was made for Families First clients to track
      compliance with the program. It was decided that it was more feasible to get this information
      from the Bureau of TennCare instead of the Department of Health.
        A file shall be needed daily for TennCare containing information for children on Families First.
        TennCare shall use this information to match against the TennCare system to determine if an
        actual health visit was made for the children. This match shall be sent back to DHS to be
        processed and update the new system.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                   25.23 Bureau of TennCare Medicaid Eligibility Error File


Existing Interface:              No
Existing Interface Method:       None
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange

Purpose of the interface
      A TennCare Medicaid Eligibility Error file shall be needed on a daily basis from TennCare in
      response to the daily TennCare Medicaid Eligibility file, TennCare Medicaid Patient Liability file
      and the TennCare Medicaid Medical E valuation Unit Interim Benefits (MEU) file. It shall include
      the reason why TennCare rejected a Medicaid eligibility record. The file shall be processed by
      DHS and generate alerts to the caseworker.
        This file may be consolidat ed with the new TennCare Standard Referral Error file.
        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionali ty
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                    25.24 Bureau of TennCare Standard Referral Error File


Existing Interface:              No
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange

Purpose of the interface
      A TennCare Standard Referral Error file shall be needed on a daily basis from TennCare in
      response to the daily TennCare Standard Referral file. It shall include the reason why TennCare
      rejected a TennCare Standard referral. The file shall be processed by DHS and generate alerts
      to the caseworker.
        This file may be consolidat ed with the new TennCare Medicaid Eligibility Error file.
        This file may also replac e the current TennCare Standard Syntax Error file and the TennCare
        Eligibility Error file.
        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Daily Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                      25.25 Bureau of TennCare Medicaid Response File


Existing Interface:              No
Existing Interface Method:       None
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange

Purpose of the interface
      A TennCare Medicaid Response file shall be needed on a daily basis from TennCare in
      response to the daily TennCare Medicaid Eligibility file, TennCare Medicaid Patient Liability file
      and the TennCare Medicaid Medical E valuation Unit Interim Benefits (MEU) file. The file shall
      indicate what updates were applied on TennCare. The file shall be proc essed by DHS to
      generate a report.
        The file may be consolidated with the current TennCare Standard Response file.
        The file shall be in the Health Insurance Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                  25.26 Bureau of TennCare Medicaid Response Error File


Existing Interface:              No
Existing Interface Method:       None
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange
Purpose of the interface
      A TennCare Medicaid Response Error file shall be needed on a daily basis for TennCare and
      reflects why TennCare‟s responses to individuals sent to TennCare on the TennCare Medicaid
      Eligibility file, TennCare Medicaid Medical E valuation Unit Int erim Benefits (MEU) file and
      TennCare Medicaid Patient Liability file were rejected.

        This file shall be in the Health Insuranc e Portability & Accountability Act (HIPAA) standard 834
        record layout plus a companion record with additional information.

        This file may be consolidat ed with the current TennCare Standard Respons e Error File.


Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on-line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                 25.27 Bureau of TennCare SSI Terminates from TennCare


Existing Interface:             No
Existing Interface Method:      None
Proposed Interface Method:      Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange

Purpose of the interface
      A file shall be needed monthly from TennCare listing thos e individuals whose SSI cash
      assistance is ending. Selection of individuals shall be made by TennCare based on reason
      codes for closure to insure no notice is sent to deceased or out of state individuals.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

             25.28 Bureau of TennCare SSI Terminates Information to TennCare


Existing Interface:               No
Existing Interface Method:        None
Proposed Interface Method:        Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Int erchange

Purpose of the interface
      A file shall be needed monthly for TennCare including those SSI terminate individuals that have
      not reapplied or filed an application by a specified timeframe.
        The file shall also include those SS I terminate individuals who did reapply but are denied for both
        TennCare Medicaid and TennCare standard (including the ME process as appropriate).
        The file shall also include those SS I terminate individuals who did reapply within a specified
        timeframe but are still in „pending‟ status to prevent any closure action prior to the eligibility
        determination be completed.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix Farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        None
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                         25.29 Bureau of TennCare Recovery Match


Existing Interface:             Yes
Existing Interface Method:      Batch
Proposed Interface Method:      Batch

System Interface with:
      Agency: TennCare Program Integrity
      System: Recipients System

Purpose of the interface
      On a quarterly basis the new system receives a file from TennCare of nursing home recipients
      who died over the age of fifty-five. This file is matched against the new system to create three
      files – TennCare Individuals not found (on the new system), TennCare Individuals with a
      surviving spouse, and TennCare Individuals without a surviving spouse and if they owned a
      home. The value of this real estate can then be used to pay the nursing home bills when there is
      no surviving spouse.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9. 2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Quarterly Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                             25.30 Bureau of TennCare Refugee File


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Interchange

Purpose of the interface
      On a monthly basis the new system shall receive a file from TennCare of refugees who receive
      TennCare and Medicaid. This file will be used to generate a report for the Federal government.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Monthly Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                      25.31 Bureau of TennCare Referrals for Newborns


Existing Interface:             No
Existing Interface Method:      None
Proposed Interface Method:      Batch

System Interface with:
      Agency: Bureau of TennCare
      System: Interchange

Purpose of the interface
      The purpose of this interface is to receive an automated referral from TennCare for any
      newborns reported to TennCare by the Managed Care Organizations (MCO). These referrals
      will be for existing V.I.P. cases. The newborns are eligible for Medicaid coverage at birth.
      Currently the Medicaid Unit is notified of the newborns via paper referral or phone call.

Platform
        Hardware: Client/Server architecture wit h the Client running on a Citrix farm. The Servers are
        two SUN 4800‟s with 12 1.2Ghz CPU per box. One box is the on -line database server/claims
        engine and the ot her is the history server whic h includes the MARS/SURS functionality
        Software: EDS in-house developed utilizing „C‟ coding language for the claims engine and
        PowerBuilder for the on-line screens
        Database: Oracle RDBMS Version 9.2
        Operating System: Solaris Version 9.0

Existing process for sending/receiving data
        Paper referral or phone call.
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE


                    26.1 Service Center IVR (Interactive Voice Response)


Existing Interface:              No
Existing Interface Method:       None
Proposed Interface Method:       On Line Real Time with Telephony System IVR

System Interface with:
      Agency: Servic e Center IVR
      System: Telephony System currently utilized by the Family Assistance Service Cent ers
Purpose of the interface
       To support on line real time client inquiries into cases, claim, appointment information from the
       new system via a telephone IV R (Interactive Voic e Response) system.

        The new system will support IV R look-ups such as status of case, status of application, benefit
        amount, and availability, location of nearest county office, appointment, date and amount of last
        claim payment received or due, and claim balance. The system shall return information to the
        IVR system via screen scraper or by query response. The sy stem shall also select a file of a
        cases for outbound reminders to be used by the Service Center telephony system automated
        dialer. Some examples of files to be used by the aut omated dialer are: Appointment notification,
        overdue verification notification and overdue claim balance notification.


Platform
        Hardware: Telephony System
        Software: Net-VU Contact Manager
        Database: N/A
        Operating System: N/A

Existing process for sending/receiving data
        None.
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

              27.1 Tennessee Department of Human Services Data Warehouse


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: DHS
      System: Data Warehouse

Purpose of the interface
      The purpose of this interface is to provide periodic files reflecting daily updates to V.I.P. Family
      Assistance Case, Individual and Issuance data. The Contractor shall provide sufficiently detailed
      data to ensure the continued viability of the existing Families First Data Warehouse/ Data Marts.
      Updates to the Data Warehous e databases will be accomplished through existing Data
      Warehouse programs and jobs external to V.I.P. Files provided to the Data Warehouse for
      processing shall be incremental and not a full load of the Data Warehouse other than at initial
      conversion.

Platform
        Hardware: IBM Mainframe, Microstrategy servers are windows
        Software: State DW Architecture using the Microstrategy products (desktop, web professional,
        OLAP servic es, report services, narrowcast services, db2connect)
        Database: DB2 version 7 OS/390 for dat a; oracle for metadata, DQL server for statistics
        Operating System: z/OS V1.4, Microstrategy Int elligent Server

Existing process for sending/receiving data
        Daily, Weekly and Mont hly Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

                               28.1 Tennessee Secretary of State


Existing Interface:              Yes
Existing Interface Method:       Report
Proposed Interface Method:       Batch

System Interface with:
      Agency: Secretary of State
      System: Voter Registration Tracking System (VRTS)

       Purpose of the interface
       During the application process or during any contact, the client will have the opport unity to apply
       to register to vote. The system will create a nightly batch file to trans fer to the Vot er Registration
       system.
       The Secretary of State requires a record of all instances of contact with clients and the data
       related to each client being given the opportunity to apply to register to vote as required by
       Federal law.

Platform
        Hardware: Mainframe
        Software: COBOL
        Database: IBM IMS
        Operating System: ZOS

Existing process for sending/receiving data
        Report
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

   29.1 Tennessee Department of Human Services Appeals Re solution Tracking System
                                      (ARTS)


Existing Interface:              Yes
Existing Interface Method:       Batch
Proposed Interface Method:       Batch

System Interface with:
      Agency: Tennessee Department of Human Services
      System: Appeals Resolution Tracking System (ARTS)
Purpose of the interface
      Appeal tracking and outcome for cases whose eligibility or benefit is being appealed by the
      recipient is maintained in the DHS Appeal Resolution Tracking System (ARTS).

        Data is received from the A RT System on a daily basis. Data from the ARTS system shall be
        processed and linked to the case(s) and individual(s) in the new syst em. When a match is
        found the case, individual, claims data shall be updated and linked to the appeal. An alert
        shall be generat ed to the worker. If a match is not found, the system shall generat e a file to
        ARTS indicating the inability to link the appeal.

        If there is a sanction/penalty/disqualification, the system may either reinstate or suspend. When
        the appeal is not bas ed on an adjudicat ed claim/accounts receivable, the system will determine if
        benefits must be reinstated. If benefits are not to be reinstated, the client will be notified. The
        system shall create a file to send to ARTS containing reinstatement data.


Platform
        Hardware: Compaq Proliant server ML370T03 G3
        Software: Microsoft .NE T Framework v1.1
        Database: Microsoft SQL Server 2000 edition
        Operating System: Microsoft Windows Server 2003

Existing process for sending/receiving data
        Batch
RFP ATTACHMENT 6.1, PRO FORMA CONTRACT ATTACHMENT D:
V.I.P. INTERFACE

               30.1 Metro Development and Housing Agency (MDHA) match


Existing Interface:            Yes
Existing Interface Method:     Batch
Proposed Interface Method:     Batch

System Interface with:
      Agency: Metro Development and Housing Agency (MDHA)
      System: File Transfer

Purpose of the interface
      A monthly file to match individuals on MDHA databases to V.I.P. The V. I.P. match will send
      MDHA FF and FS data for V.I.P. individuals.

Platform
        Hardware: Unknown
        Software: Unknown
        Database: Unknown
        Operating System: Unknown

Existing process for sending/receiving data
        File Transfer Protoc ol (FTP).

				
DOCUMENT INFO
Description: Tennessee Online Real Estate Schools document sample