First one was an id coming back as invalid. Ok, so I dug in. I opened a log file for one of the jobs that ran and discovered the problem fairly quickly. In fact, I didn't even need to look in a log file, since this info would have been just as easily found on the screen where the accounts are stored. Just how valid would a user id of "none" be anyway? Literally, someone typed the word none in the field. I gave Optimus 5 seconds to find the problem, and he found it.
Then he did the same to me moments later and started counting before I got ot his desk. Of course, it didn't take long to see the reason that person's claims weren't processing. You see, last week was what we refer to as an F.I. transition. That's where the payer that actually pays the claim submitted to Medicare transitions their connection to someone else, and that usually entails new IDs. What we do is disable the old IDs and markthem with TBR, which means to be removed. Optimus' person had a page full of these IDs. Think we got them figured out.
My last one was about secondary claims not being created all week. I looked into their jobs and found none of the necessary jobs had processed at all. A little further in showed no calid IDs. I went to that screen and found, once again, TBR off to the side of three IDs.
The point of all this is this: all of these could have been done in a few minutes by the people who submitted the tickets to make someone else do it for them. Sure, the call takers have a 10 minute time limit, but these were seconds to figure out and deliver the message. Why did people have to wait for this?
Well, the answer is simple: "not my job."
No comments:
Post a Comment