Vigor Billing Interface now supports Medisoft v18

Post your topics about Medisoft Interfacing here.
Post Reply
User avatar
Gavin Walker
Posts: 4204
Joined: Wed Apr 04, 2007 10:11 pm
Location: Springfield, MO
Contact:

Vigor Billing Interface now supports Medisoft v18

Post by Gavin Walker » Wed Jan 23, 2013 3:18 pm

Notes:
• This v3.01 Vigor is still compatible w/v15-17 as well, w/the same caveats as before (pre-17, there was no race, etc., so these fields can't be sent/received).
• The primary change is in how Vigor processes charge updates. Previously, we relied on the Document Number field in the transaction table to hold a "charge set identifier" for us. Vigor uses this value to locate and delete the old version of the charges being updated. W/Cedaron, charge set identifier had to be alphanumeric – a no-no in v18 (must be numeric now). So the interface creates new table vbiChargeSet, and we track this information there. The DocNum config option still controls how Vigor populates the Document Number field, except in the case of Connect, which will always get CCYYMMDDHH (all the other EHR options generate a numeric value). Because Vigor automatically creates and populates this table, no special steps are needed when installing. If Vigor detects this setup has not been done/completed, after creating the table, it loads table vbiChargeSet w/entries for the last 12 months of charges. This is overkill, but insures we have the data to process any charge updates the EHR may send.

This also includes a fix for the stopping of charge processing when records get locked. Locking the record in Medisoft that Vigor is trying to update still prevents charges from processing, but once the lock is released, charge processing should begin again w/o having to take any actions (e.g., restart services.)
Gavin Walker
Walker Tek Solutions, LLC
866-890-6777
417-890-6777

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

Vigor v3.11 now available

Post by Gavin Walker » Fri Sep 20, 2013 12:12 pm

Version 3.11
• Fixed error where insurance matched incorrectly. This only involved scenarios where address already matched more than one Medisoft insurance carrier. Specifically, if the inbound insurance name was longer than Medisoft insurance company name, Vigor would match if the inbound company started with the Medisoft company. This is a refining fix to a previous fix. When the inbound company is name longer than the Medisoft company name, it makes sense to only compare the first portion, but only when the inbound company name is longer than what can fit in the Medisoft database field. We here had Medisoft insurance on file:
LENGTH NAME
18 Independent Health
31 Independent Health Encompass 65
The msg value, “Independent Health Encompass 65”, should have matched the 2nd insurance but was being matched to the first one because, “Independent Health Encompass 65” starts with, “Independent Health”. This only makes sense when the message value exceeds the max length we can store in the Medisoft field, which is 45 characters in this case. So when the inbound insurance company name is 45 characters or less, Vigor now turns off the logic described above and requires a direct match. This fixes the problem and causes Vigor to correctly match the 2nd insurance carrier, in the example above.
• Added support for not pausing the Vigor engine for 1 minute on startup. This requires setting configuration tag <StartupDelayMinutes>0</StartupDelayMinutes> or removing the <StartupDelayMinutes> tag entirely. This was originally added because on a slow machine, Vigor was starting before ADS service finished starting, and always defaulted to 1 minute. But the need for this turned out to be rare, and it got very old debugging at live sites, having to wait that minute. So we now support and default to a value of 0 [zero], which skips the wait.

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

Re: Vigor Billing Interface now supports Medisoft v18

Post by Gavin Walker » Tue Feb 04, 2014 4:13 pm

Version 3.14
  • • Vigor now populates Medisoft Annual Deductible from IN1.37 of the primary insured
    • Vigor now populates Medisoft Copay Amount from IN2.29.4.2 of the primary insured *
    • In preparation for supporting receiving patient co-payments and patient payments via P03 messaging, Vigor now screens FT1 segments and ignores anything that's not a charge. Vigor treats all FT1 segments with FT1.6 omitted, "CG", or "CH" as a charge and currently ignores anything else. Later, Vigor will also process payments based on new values of FT1.6.

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

Re: Vigor Billing Interface now supports Medisoft v18

Post by Gavin Walker » Mon Feb 10, 2014 5:46 pm

Vigor now supports
1. Accident “Related To” dropdown / Illness/Injury/LMP Date
2. Set Insurance Type when Vigor creates an insurance carrier on-the-fly.

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

Re: Vigor Billing Interface now supports Medisoft v18

Post by Gavin Walker » Fri Feb 21, 2014 3:44 pm

• ADT now sends patient balances in PV1 segment:
o PV1.26 - Medisoft Patient Reference Balance = outstanding A/R for this patient, money due including portions not yet paid by insurance or other parties.
o PV1.46 - Medisoft Patient Remainder Balance = the remainder due from patient after expected insurance payments
For obvious reasons, Vigor does not accept this field on inbound messages.
These changes were made for I.T. Pacs Pro, but are not conditional – they will be included anytime Vigor sends ADT, regardless of vendor.

Post Reply