160 likes | 304 Views
Project UpdateCMSEarly Test PartnerFile ReadinessClarified requirements for Response File, Business Process and Error HandlingHealth Event TypesClarified requirements for Original Hire Date, FERP dates, NameTesting with PERT4UCampus Pilot Testing Scheduled to begin week of May 23Campus
E N D
2. Project Update
CMS/Campus Pilot Testing
The PSR Interface Process
Health Event Types, Health Transaction Rescissions
Data Elements; PSR Error Handling
Seed Data
Health Reason Codes (Permitting Event Codes)
Demonstration of PSR
Timelines and Activities
Questions/Resources
Agenda 1 MHMH
3. Project Update
CMS
Early Test Partner
File Readiness
Clarified requirements for Response File, Business Process and Error Handling
Health Event Types
Clarified requirements for Original Hire Date, FERP dates, Name
Testing with PERT4U
Campus Pilot Testing
Scheduled to begin week of May 23
Campus Pilot Testing Teleconference meeting scheduled
Project Update 2 THTH
4. PSR Health Event Types - Revision 3 MHMH
5. PSR will allow rescission of certain health transactions
Effective date of the transaction must occur in the future and the health transaction must be permissive
Permissive transactions are those not required by law and that were made at the request of the employee – examples include
Voluntary cancellation or deletion of a dependent
Open Enrollment - Prior to the January 1 effective date, if a participant decides they no longer want to change carriers, employers may rescind the transaction within my|CalPERS
Only three (3) Rescission Codes are applicable to CSU
Health Transaction Rescissions - Revision 4 MHMH
6. Employee
Person ID (SSN)
Prefix
First Name
Middle Name
Last Name
Birth Date
Gender
Suffix
Address 1*
Address 2*
Address 3
City (Country)
State
Zip Code 5
FERP Status Begin Date
FERP Status End Date
Original Hire Date
CBU (Union Code)
PSR Data Element Fields – CSU Key Fields to be Cleansed - Revised 5 TH/MPTH/MP
7. 6 PSR Data Element Fields – Required TH/MPTH/MP
8. Outbound – Errors identified by CSU
CSU will validate data to ensure required information is extracted
Inbound – Errors identified by CalPERS
Level 1: Validation of file
Validation completed by CSU PSR Project Team during testing
Level 2: Validation via business logic PSR Error Handling 7 TH/MPTH/MP
9. Seed Data
CalPERS will provide a file with Seed Data for each campus
The file will populate the CalPERS Participant ID and CalPERS Dependent ID
Campuses will load the Seed Data into Production
Seed Data – Clarified 8 TH/MPTH/MP
10. Health Reason Codes will be applicable by Health Event Type – Refer to handout
Health Event Reason Codes - Revised 9 TH/MPTH/MP
11. Setup
CSU Installation page
CSU FTP page
Data Entry
CSU Health Permitting Event page(s) (Health Reason Codes)
CSU COBRA Enrollment: Employee, dependents
CSU Retiree Dental Enrollment: Employee, dependents
Processing, Errors and Exceptions
CSU PSR Interface (Run Control)
Seed Data
Outbound
Inbound
CSU PSR Transactions
CSU PSR Errors
CSU PSR ID Table
Demonstration of PSR 10 MP/TH
BB 4 - COBRA
BB 7 - Retiree Dental
TL 02 – New Enrollment
PSR 15 – Add Dependent
PSR 22 – Delete Dependent
MP/TH
BB 4 - COBRA
BB 7 - Retiree Dental
TL 02 – New Enrollment
PSR 15 – Add Dependent
PSR 22 – Delete Dependent
12. Timelines and Activities 11 TH/MPTH/MP
13. May
Data clean up
Identify campus PSR test instance
Pilot testing with CalPERS /PERT4U
June
Apply PSR project to campus test database
Campus Acceptance Testing begins (cloned copy of production)
Participate in PSR Training (CSU/CalPERS)
Campus Activities (Dates are Tentative) 12 TH/MPTH/MP
14. Questions 13 AllAll
15. 14 Resources PSR Tech Letter
PSR Data Elements
PSR Health Event Reason Codes (Permitting Event Codes)
HUG Benefits Subcommittee Postings website
16. 15