winoms update v10

[rorozco]

Inquiring when version 10 will be available?  I was told by Carestream -we need this version before we can update Epayments to V3.    Carestream mentioned in December that an email will be sent in January with information on version 10 for winoms.   Still waiting...

Thanks in advance for any information you can share

[rorozco]

I hope this gets resolved for both of us sooner than later.  Carestream keeps calling to see if we upgraded to payment manager yet (epayments V3)?  Frustrating is an understatment.

[eastonoms]

We would love to know the answer as well. We cannot submit claims attachments without getting NEA attachment log not found. This has been going on for months and no one can tell us when it will be fixed. Our IT said this morning that they were previously told it would not be fixed until the update to WINOMS v10. WE HAVE TO BE ABLE TO SUBMIT CLAIMS ELECTRONICALLY, OTHERWISE WE DON'T GET PAID. HOWEVER, WE HAVE TO PAY OUR CARESTREAM BILL MONTHLY!

[rich_omsafw]

@eastonoms   How many attachments do you send out via NEA per week/month.  You are cloud correct?  I checked with our insurance department they don't usually get that message.  Just wondered if volume was the reason for this issue by chance.

@rorozco Do you like ePayments?  We looked at it last year and the powers that be decided to go in different direction.  I haven't heard anyone mention much about it. Just curious if you have any issues and if it works as smoothly as they say it does.

[eastonoms]

We usually send 5 or 6 attachments per day.  The error occurs every couple of days.  Twice last week and again today. This was never an issue until the transition to citrix.  So annoying!!!! 

[rich_omsafw]

I talked to our Ins department and they estimated they send 40-50 attachments per week so we are slightly higher value than you guys.  you guys did migrate to Azure (project elevate) right?  Have you ever made it past the first layer of support and get escalations involved in this?  I usually don't even call in anymore, I just email escalations and usually get a call back in a day.  There has to be an actual fix for this, otherwise we would be in the same situation.

[SOS_Tech]

Our practice sends out at least that many attachments every week.  It wouldn't surprise me if the total was closer to 100 or more.  We have not had this issue with NEA.  I brought up this specific issue up prior to migration with the transition team.  I was trying to head off any issues as what eastonoms has had to go thru would have been unacceptable.

eastonoms... you did let the pre-migration team know what workstations would be using NEA Fast Attach?

Also, and I don't know if this is pure coincidence, on the mapped shared drive for all workstations there is a folder for NEA logs that was created the first time one was sent post migration.  I don't see any evidence that anything is saved in that folder but maybe its existence is why we don't have the issue.  The folder path in the mapped share is <ourcloudserver>.MyPractice.Local\DPMS\WinOms\<our.ID>\FastAttach\NEA\LOGS\   Rich... do you have a similar folder on a mapped share?

[eastonoms]

We use to send attachments on almost every claim. I did some research, and don't send them unless absolutely necessary, otherwise I would be here all night with all the errors. Yes, escalations has been involved, but CareStream makes me go thru all the hoops to get there. It got to the point, CareStream would not call back. I'm so busy, that I usually email our IT and ask them to take care of it. They have done the NEA fix so many times, they are now getting frustrated.

[rich_omsafw]

@SOS_Tech I am unable to browse to any folders containing Fast Attach.  We have one mapped drive from Carestream and I can't browse to any folders from that path.  If I try to access \\cloud server\any folder i get access to the resource has been disallowed.