MS v22 "Not a valid Medicare Beneficiary Identification" number format

Technical problems with Medisoft.
Post Reply
prosete
Posts: 204
Joined: Tue Feb 22, 2011 1:00 pm

MS v22 "Not a valid Medicare Beneficiary Identification" number format

Post by prosete » Fri Apr 27, 2018 1:04 pm

Since installing v22 SP1, I've been getting a yellow error message next to the Policy 1 Member ID field telling me the 9-digit+letter suffix Medicare ID number entered is not in a valid format and to consult the Help table for assistance. I am aware there are new Medicare ID cards being issued as of April 1st but somehow I didn't think SP1 would auto reject members' Medicare ID legacy formats that were still valid March 31.

Any reason why this is going on?

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: MS v22 "Not a valid Medicare Beneficiary Identification" number format

Post by Gavin Walker » Mon Apr 30, 2018 5:37 pm

If you don't want the warning about the new Medicare Beneficiary ID (MBI), then go to Program Options -> General Tab -> Account Alert Settings frame and uncheck MBI. Keep in mind the yellow highlight is just a warning letting you know that you don't have a valid MBI entered. You can still save the information with the old policy #.
Gavin Walker
Walker Tek Solutions, LLC
417-890-6777 x0
fax: 417-763-6386

prosete
Posts: 204
Joined: Tue Feb 22, 2011 1:00 pm

Re: MS v22 "Not a valid Medicare Beneficiary Identification" number format

Post by prosete » Mon Apr 30, 2018 5:41 pm

Yes, thanks, Gavin! And I just found out there's a grace period (don't know how long) during which the legacy ID can still be used in place of the new MBI.

User avatar
Gavin Walker
Posts: 4625
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Re: MS v22 "Not a valid Medicare Beneficiary Identification" number format

Post by Gavin Walker » Wed May 02, 2018 8:23 am

Medicare is currently showing the deadline to adopt MBI is 1/2020. They will start returning MBI on remittances on 10/2018 so that could affect auto-remit posting if you use that function of Medisoft..

Post Reply