Update – Epic Setup for Red Flags on Q22/K22 Interface

8.14.2015 – During our weekly deployment last evening, we added Red Flag alerts to our Patient Identity Verification (PIV) module that are now returned as part of the Experian address verification response.

However, this has resulted in some minor Epic interface errors.   This can happen if the interface build within Epic is not set up to handle the values we are now sending back in ZMS-3 and ZMS-4.  More information about this Epic functionality and setup is provided below.

  1. A translation table in Epic needs to be set up to translate the values we are now sending back in ZMS-3. The default table in Epic is 175425 (ADDR VER IN RED FLAG ACTION) so that’s likely the one the customer needs to set up. However, there is a small chance it could be different in their system, in which case they will have to contact their Epic TS to find the table if they don’t know themselves.
  2. The values to set up are (both 4 and 6 map to “Deceased”):
    1. 1 – Name and SSN Discrepancy (or input SSN is invalid)
      2 – Name and Address Discrepancy
      3 – Address and SSN Discrepancy (or input SSN is invalid)
      4, 6 – Deceased
      5 – Credit Report Fraud Alert (initial fraud alert, extended fraud alert or active duty fraud alert)
      7 – Inquiry SSN Not Issued
      8 – Inquiry age < SSN Issue Date
      9 – Date Credit Established < SSN Issue Date
      10 – Non-Residential Inquiry Address
      0 – No red flags found
    2. We send the numeric value in ZMS-3. ZMS-4 contains text associated with that flag.

If you are experiencing this issue, please feel free to contact us.

This entry was posted in Archived Posts. Bookmark the permalink.