1503 - Client-Index-Number/MEDS-ID Conflict Critical

This alert is generated when:

There is a CIN on the transaction that is known to MEDS;
The MEDS-ID reported on the transaction does not match the MEDS-ID associated with that CIN on the MEDS CIN Cross Reference File; AND
The MEDS-ID reported on the transaction is not a previously used MEDS-ID associated with the CIN Cross Reference File MEDS-ID.

Refer to Researching and Resolving File Clearance Alerts. Determine which scenario(s) best describes the circumstances for this alert. Follow the steps outlined in that document for the selected scenario.

Sample Alert

Click herehere to view the sample alert.

Possible Screens to Resolve This Alert

PerformPerform INQR Client Inquiry Request using TRAN HDR MEDS-ID.

The NO RECORD FOUND message indicates that the transaction MEDS ID is not known to MEDS.

PerformPerform INQR Client Inquiry Request using X REF MEDS ID.
This screenThis screen indicates that the XREF MEDS ID is known to MEDS and has eligibility in a special program.
This screenThis screen indicates all county cases including CalHEERS cases. In this case there are no previously used MEDS IDs displayed for this MEDS ID. If there were any, they would be displayed here.
PerformPerform a Client ID search for the transaction CIN displayed on the alert.
The Client IDThe Client ID search indicates that the MEDS ID most recently reported to SCI is associated with the transaction CIN.
The Scored NameThe Scored Name search indicates that no matching records were found on SCI for the name, birthdate, and gender entered.
The Fuzzy NameThe Fuzzy Name search indicates the same matching record as that on the Client ID search.

In this particular scenario it appears that the MEDS ID has been changed in CalSAWS and in SCI from the Pseudo MEDS ID to the real SSN but that MEDS has not been updated with the MEDS ID change.

Action Required

Use the following chart to determine corrective action when an individual is known to MEDS with a pseudo.

IF the individual is already known to MEDS with a Pseudo...	THEN...
	Navigate to the Individual Demographics Detail page Select the individual whose record needs correction Open/Edit SSN Detail page Delete the social security number Rerun EDBC and authorize. Ensure SSN is also removed in CalHEERS if there is a CalHEERS case associated to the CalSAWS case. Check MEDS 2 days later. If MEDS is updated correctly, then Enter the social security number in CalSAWS Rerun EDBC and authorize Check MEDS 2 days later. Delete any unnecessary client correspondence that was generated.

IF the individual is already known
to MEDS with a Pseudo...

THEN...

Navigate to the Individual Demographics Detail page
Select the individual whose record needs correction
Open/Edit SSN Detail page
Delete the social security number
Rerun EDBC and authorize.
Ensure SSN is also removed in CalHEERS if there is a CalHEERS case associated to the CalSAWS case.
Check MEDS 2 days later. If MEDS is updated correctly, then
Enter the social security number in CalSAWS
Rerun EDBC and authorize
Check MEDS 2 days later.
Delete any unnecessary client correspondence that was generated.

Use the following chart to determine corrective action when an individual is known to MEDS with an incorrect social security number.

IF the individual is already known to MEDS with an incorrect social security number...	THEN...
	Navigate to the Individual Demographics Detail page Select the individual whose record needs correction Open/Edit SSN Detail page Enter the correct social security number Rerun EDBC and authorize. Ensure correct SSN is updated in CalHEERS if there is a CalHEERS case associated to the CalSAWS case. Check MEDS 2 days later Delete any unnecessary client correspondence that was generated.

1503 - Client-Index-Number/MEDS-ID Conflict Critical

Sample Alert

Possible Screens to Resolve This Alert

Action Required

Related Topics