â€¢ 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.)
Walker Tek Solutions, LLC