Social Security's ERE system that attorneys use to access their clients' files is only partially functional this morning.
Does this also affect Social Security's internal systems?
7 comments:
Anonymous
said...
I tried to log into a file to upload some records and I couldn't so I gave my secretary the records and the bar code to fax it in the old way. Then I tried to log into a file to check something and couldn't. I realized ERE was down so I tried to call the local office to ask why my client received a random letter from the local office telling her when her birthday is. (Hopefully an error and not fraud). I was kicked off the queue the first time. Now I've been on hold for 15 minutes on my second attempt. THIS IS DYSFUNCTIONAL!!! The government needs to hold this agency accountable.
Seattle Washington area affected re ERE since Friday afternoon (10/27/23) with sluggish performance and trouble logging in. 10/30/23 OVH - hearing scheduled for 9 a.m. PST from a central time region has not begun yet, no word from OHO via phone or email.
When my office called SSA to ask why I no longer had access to my claims, I was told it was a system wide issue - and that it was affecting them internally as well. My understanding is Judges were unable to look at certain cases today as well.
I have hearings tomorrow that I am unable to finish reading...
Assume an ERE limited to light duty, occasional interaction with the public, and simple and routine tasks, with breaks for 10 minutes every hour and absent 2 days per month.
ERE is in maintenance mode. No development or support funding. SSA tried to rewrite it using a no-code low-code platform, new team that does not have a clue and failed. SSA is not interested in supporting it. Funny thing is it handles a number of critical and significant workloads (appointed representative, consultative exam and MER requests/responses). Just because it’s deemed legacy SSA figures it does not need funding and support. So short sighted on executives part.
7 comments:
I tried to log into a file to upload some records and I couldn't so I gave my secretary the records and the bar code to fax it in the old way. Then I tried to log into a file to check something and couldn't. I realized ERE was down so I tried to call the local office to ask why my client received a random letter from the local office telling her when her birthday is. (Hopefully an error and not fraud). I was kicked off the queue the first time. Now I've been on hold for 15 minutes on my second attempt.
THIS IS DYSFUNCTIONAL!!! The government needs to hold this agency accountable.
Seattle Washington area affected re ERE since Friday afternoon (10/27/23) with sluggish performance and trouble logging in. 10/30/23 OVH - hearing scheduled for 9 a.m. PST from a central time region has not begun yet, no word from OHO via phone or email.
When my office called SSA to ask why I no longer had access to my claims, I was told it was a system wide issue - and that it was affecting them internally as well. My understanding is Judges were unable to look at certain cases today as well.
I have hearings tomorrow that I am unable to finish reading...
Just so you guys know, that’s how SSA’s systems work for us in the agency as well. This isn’t just a ERE thing.
Trust me, stuff rarely works completely as intended. We always have new “work arounds” being issued.
Assume an ERE limited to light duty, occasional interaction with the public, and simple and routine tasks, with breaks for 10 minutes every hour and absent 2 days per month.
So…NOT DISABLED! 😂
ERE is in maintenance mode. No development or support funding. SSA tried to rewrite it using a no-code low-code platform, new team that does not have a clue and failed. SSA is not interested in supporting it. Funny thing is it handles a number of critical and significant workloads (appointed representative, consultative exam and MER requests/responses). Just because it’s deemed legacy SSA figures it does not need funding and support. So short sighted on executives part.
Post a Comment