Vigor Billing Interface™ for Medisoft®

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

Re: Announcing Vigor Billing Interface™ for Medisoft®

Post by Gavin Walker » Thu Mar 24, 2011 6:16 pm

There is no holding option in Vigor like Communication Manager, but the patient will instead get created in Medisoft when the message is processed. We try to be smart about creating cases in Medisoft. Vigor will try to match the insurance and facility and put the transactions to that case. If a matching case is not found, a new case is created. We also match cases by auth number.

I'll have to get back to you about pricing. It takes time to come up with an accurate quote, but I don't mind if you want to split the development cost with others.

mbpros
Posts: 312
Joined: Fri Mar 11, 2011 6:59 pm

Re: Announcing Vigor Billing Interface™ for Medisoft®

Post by mbpros » Thu Mar 24, 2011 6:18 pm

Okay, thanks for the info.
Steven Zats
Medical Billing Professionals

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

Re: Announcing Vigor Billing Interface™ for Medisoft®

Post by Gavin Walker » Thu Apr 07, 2011 7:45 pm

Version 2.12
  • • Bugs Fixed
    • Apostrophes in some data could cause errors; fixed;
    • Enhancements
    • Improvements to support utility, including the ability to export query results;
    • Enhanced NPI matching – removed Legacy Qualifier 1 as a criterion; this fixed the problem that NPIs were not matching to a provider even though the NPI was entered correctly.
    • The file HL7AdsViewer.exe (in the application folder under "Program Files") now reflects the version number of the interface. Previously, this was only discernable from either the event log or the date/time of the assemblies.
    • Improved support when all ADS (Advantage Database Server) licenses are in use – when interfacing with Cedaron and no charges are sent to the interface, the interface uses no ADS user seats. The interface opens a connection to ADS only when there is activity. When there is activity, however, the interface keeps its connection open continuously until it processes all queued messages; this performance enhancement from version 2.0.5 is maintained.
    • Likewise, the support utility uses a user seat only when executing a database query, then immediately releases it by closing the connection.
Version 2.11
  • • Improvements to support utility.
    • Added support for single-user Medisoft under 64-bit Windows; Now, all versions of Medisoft v16+ are supported in 32- and 64-bit.
Version 2.10
Setup now includes a support utility that allows querying the database.

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

Re: Announcing Vigor Billing Interface™ for Medisoft®

Post by Gavin Walker » Wed Jun 22, 2011 10:53 pm

We found the following causes of duplicate patients/guarantors in Medisoft:
  • • Interface bug—If the guarantor was an existing patient (Patient Type = Patient), the interface would never find it and always create a duplicate record (Patient Type = Guarantor). Fixed.
    • After initially sending insured/guarantor (ins/gt), a future message specified a different SSN. Since ins/gt do not have a special unique key like a Medisoft chart #, we use SSN for this if it is present.
    Solution: if the SSN for a guarantor changes (and it’s the same person), change it in Medisoft first, then in the EHR. Otherwise you will still get a duplicate created.
    • After initially sending insured/guarantor (ins/gt) when SSN is not present, a future message specified a different last name, first name, or DOB. When SSN is not present, we use last name + first name + DOB to search.
    Solution: if SSN is not present and the name or DOB for a ins/gt changes (and it’s the same person), change it in Medisoft first, then in the EHR. Otherwise you will still get a duplicate created.
    • Ins/gt info was the same as the patient, but relationship was Spouse.
    Solution: Enter the correct relationship.
Other improvements:
  • • If the SSN or Name/DOB matches the patient, but relationship is not “Self”, the interface will nevertheless treat the ins/gt as “Self”.
    • If the patient in a message is an existing guarantor (Medisoft Patient Type = Guarantor), the interface will now change the Patient Type to Patient (it never did this before).
    • When an ins/gt is matched up to an existing Medisoft record, the interface will now update name, DOB, sex, address, phone, & marital status with the ins/gt information sent. As before, updates to policy # and group # flow to the case, but this is the first time the interface has processed updates to the guarantor’s person record in Medisoft (Patient Type = Patient or Guarantor).
    • When ins/gt info is inconsistent w/the relationship, a Work Administrator message notifies you, so you can fix this.
    • Eliminated "DG1 - Segment too short" error. I don’t know why Connect sometimes sends empty diagnoses lists, but that is no reason to stop processing the charges.

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

Re: Announcing Vigor Billing Interface™ for Medisoft®

Post by Gavin Walker » Thu Jul 07, 2011 10:47 pm

Version 2.21
Assignment of Benefits on Transactions—In some circumstances, the interface set the Assignment of Benefits flag on a transaction to False when the case value was True for that insurance carrier. Fixed.

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

Re: Announcing Vigor Billing Interface™ for Medisoft®

Post by Gavin Walker » Wed May 09, 2012 5:01 pm

Here are the changes to the interface. There is a new option to support syncing Medisoft cases with Connect episodes – which should make the Medisoft visit counter feature work rather well.

There are some interface mappings that Cedaron needs to turn on for you to see things like Initial Treatment Date and discipline to auto-populate in Medisoft through the interface.

Adding the option to include Initial Treatment Date + discipline as additional case-selection criteria was necessary to accommodate episodes where no auth# is required, as with Medicare.

We have been (erroneously) populating Medisoft emergency home # from business phone in Connect.

Version 2.44
Fixed—When generating a chart # for a new patient, the interface checks only active patients to make sure the new chart # is not already in use. This causes the interface to assign a chart # in use by an inactive patient, resulting in an error when the interface attempts to insert the new patient into Medisoft.
Enhancements—various enhancements on charge messages inbound-to-Medisoft. NOTE: You must ask your EHR vendor to map these values for your site:
• APTA Connect is now populating Patient Language
• APTA Connect is now populating Patient Ethnicity
• APTA Connect is now populating Patient Race
• If you set race to "Hispanic" in Connect, this will not populate Medisoft, since Medisoft does not have such a value. Other values should populate correctly to Medisoft.
• Populate full Emergency Contact information. The following Emergency Contact fields are populated on the patient "Other Information" tab in Medisoft:
• Emergency Contact Name
• Emergency Contact Home Phone
• Emergency Contact Cell Phone
• Populate Discipline Type Code on the case "EDI" tab—from the Connect episode discipline
• Populate Initial Treatment Date on the case "Condition" tab—from the Connect episode date
• Populate case Policy Start Date for insurance carriers 1, 2, 3
• Added ability to match Medisoft cases to episodes in Cedaron APTA Connect – this is done by adding Connect discipline and Initial Treatment Date to case-matching criteria. If this option is turned on, the interface matches the incoming charges to a case w/matching insurance 1/2/3, authorization #, facility, discipline, and Initial Treatment Date. By default, this option is NOT turned on.
• Before pushing charges with this option turned on, to avoid the interface creating extra cases, audit all your active cases and make sure these fields are populated to match the EHR:
• Initial Treatment Date on the case Condition tab
• Discipline Type Code on the case EDI tab. If the EHR discipline is longer than two characters, only enter the first two characters (the field in Medisoft is only two characters). The first two characters must match, so don't enter "ST" in Medisoft for "SLP" in the EHR. For "SLP" in the EHR, enter "SL" in Medisoft.
• Treatment Authorization (#) on the case Policy 1 tab
• Enhancement: Visit Count Processing
• Interface now populates case Authorized Number of Visits
• Each new charge message increments case Last Visit Number by 1
• When the visit counter already = Authorized Number of Visits, e.g., processing visit 5 of 4, the interface sets case Last Visit Number to zero, flagging over-utilization.
• When processing a charge update, first the original charge transactions are deleted from Medisoft, then the new transactions are saved, completely replacing the original list of charges for this visit. When the interface deletes the original transactions, it also decrements the case Last Visit Number. This is important, because one of the reasons for pushing charge updates is to correct case selection. If transactions end up flowing to the same case as the original set, the Last Visit Number remains the same in the end (it gets decremented, then immediately incremented). However, if new transactions flow to a different case than the original one, Last Visit Number remains decremented on the original case and is incremented on the newly-selected case.
• Visit Series ID (label on Medisoft field just says, "ID")
• For context, when entering charges manually in Medisoft,
• Medisoft sets the case Visit Series ID to "A" with the first charge transaction saved;
• If/when a visit beyond the total is entered on the same case, e.g., visit 4 of 3, Medisoft sets the Visit Series ID to "B" and the Last Visit Number to 1.
• Many customers do not use Visit Series ID letter. With regard to Visit Series ID, the interface works differently than the interactive Transaction Entry function in Medisoft. The interface assigns a different letter of the alphabet to each case for a patient, and Visit Series ID stays the same on each case:
• If the interface finds an existing, matching case, it assumes the Visit Series ID has been set previously, and does not change it.
• If the interface must create a new case, it considers all (active and inactive) cases for a patient, and then chooses the next available letter. Looking at the Visit Series ID, the cases become designated A, B, C, all the way to Z.
• In the unlikely event a 27th case is needed, a 2nd "A" comes after Z, then a 2nd "B", and so on. This "alphabet wrap around" will occur indefinitely.

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

Re: Announcing Vigor Billing Interface™ for Medisoft®

Post by Gavin Walker » Wed May 09, 2012 5:05 pm

One other change note I forgot:
Fixed—
The interface was populating patient phone 5 with the emergency phone. Patient phone 5 is not defined as an emergency # and the interface no longer populates this.

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

Re: Announcing Vigor Billing Interface™ for Medisoft®

Post by Gavin Walker » Sat Aug 25, 2012 1:15 pm

Version 2.52
Fixed bug - when the interface creates a new insurance carrier in Medisoft, the insurance Phone was not formatted correctly. When tabbing into or out of the insurance Phone field, the field flashed red or displayed an error. This was only an issue on creating new carriers, not with updating existing carriers.

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

ifa EHR is now live w/Vigor on ADT!

Post by Gavin Walker » Wed Oct 17, 2012 5:19 pm

ifa just called and the interface is live and working properly. So this is the 4th EHR that is live (after Cedaron, AllScripts, & gMed) on Vigor.

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

Re: Announcing Vigor Billing Interface™ for Medisoft®

Post by Gavin Walker » Thu Nov 15, 2012 10:54 pm

I am pleased to announce that we have Vigor for Medisoft interface live with a Quest Care360. Patient demographics and appointments flow outbound from Medisoft into Care360.

Post Reply