Free Service Packs for Medisoft

• Billing and Collections
• Reports
• Patient Quick Entry
• Office Hours/Office Hours Pro
• Utilities
• List Entry
• Administrative Dashboard
• Claims Manager
• Eligibility Verification
• Communications Manager
• Backup Changes
• Work Administration
• Miscellaneous

• Appointment Phone Number changes will now affect future appointments.
• Error "System cannot find the file specified" when accessing eligibility in Office Hours Pro stand alone has been corrected. 13016
• Notes will now appear on appointments in the resource columns within Office Hours Professional. 11898
• When creating a new Reason code within Office Hours Professional, the Date Created date will now create properly. 12045
• Error "Query: Field 'Type' not found" when editing a template in office hours has been corrected. 11619
• You can now exit Office Hours Pro from the login screen without freezing the program. 11713
• Creating a patient from within the appointment in Office Hours Pro now displays the correct patient next to the chart number field after save. 13459
• Creating a new appointment without a case but with a patient no longer defaults the case field to the first case in the case list. 13473
• Office Hours Pro now allows for cases to be edited from the Appointment Entry screen. 13427

• Version 14.13
• All Modules
  • 14626 – Corrected and issue with a payee number (Providers window, Default PINs tab, Payee Number) not populated in Loop 2010AB Segment REF: Pay-to-Provider Secondary ID REF02.
• RelayHealth
• 14650 – Modified the code for Loop 2010BB Segment REF: Payer Secondary ID for BCBS South Carolina payer number 2410 to send 2U in the REF01 segment instead of FY. The crosswalk was also updated to reflect the change.
• 14882 – Corrected an issue with a qualifier not populated in Loop 2310A REF01 segment and the state license number not populated in Loop 2310A REF02 segment for payor ID 1421 and 2426. The crosswalk was also updated to reflect the change.
• ERA
• 14190 –Corrected a delimiter formatting translation issue that was impacting ERA posting. Added a new routine to the application code that translates various delimiters into a common format.
• 14599 – Corrected an issue encountered by some users with ERA auto posting with Claims Manager. Some users encountered a situation in which the patient account number was not appearing on the preverification report leading to payments not posting. The application logic was updated.
• 14736 – Corrected an error that occurred for some users when downloading ERA files. When downloading, the system would display the error message “LX#01 is not a Valid Integer Value for field "Entry Number" and close.
• Version 14.12
  • All Modules
  • 14711 – Modified the code to use either the NPI Only check box or the NPI: trigger to transmit NPI Only data. Both options suppress tax IDs/social security numbers in various data segments; however, neither option suppresses legacy IDs and qualifiers in Loop 2010AA Segment REF and Loop 2310B Segment REF—some carriers still request NPI only data along with legacy data, and these segments pull legacy data if it is in the PIN matrix.
    
    If your carrier requires true NPI only data (no legacy numbers in the claim), you will need to remove the pin number and qualifier and the group ID and qualifier from the PIN matrix on the Insurance Carrier window, PINs tab. If your practice has many insurance companies with multiple PIN numbers, you can contact EDI Customer Support at (800) 334-4006, and Support can run a script in the practice to automatically remove the PIN numbers.
    
    Then either:
    
    Go to the Lists menu and select Insurance and then select Carriers. On the Address tab of the Insurance Carriers window, click the NPI Only check box.
    
    —OR—
    
    On the Insurance Carrier Entry window, Address tab, in the Practice ID field, enter NPI:.
    
    If your carrier requires NPI data along with legacy data, you will need to select the NPI Only check box or enter the NPI: trigger in Medisoft and then on a carrier-by-carrier basis, remove the PIN numbers for carriers that require NPI only data, but leave the PIN numbers for carrier that require NPI only data plus legacy data.
  • ERA
  • 13551 and 13558 – Modified the application to address issues with compound remittance files being split into single remittance files. Previous versions of ERA used the ST: trigger in the Ext. field to split compound remittance files. The application no longer uses the ST: trigger for this functionality and automatically splits compound ERA files into individual files. The file splitting automatically occurs for a compound remittance file when users download reports or apply payments. The application backs up the original file with a timestamp record before the split occurs in the Medidata\Practice Name\ NDC\ERA\BackUp\Current Year\Current Month.
    
    When viewing a report or posting payment, if you select a compound remittance, the Information window will appear noting that the compound remittance file has been split into single remittance files. You will click OK on the window and then on the Open window, select one of the split remittance files to view or post.
• Version 14.11
• Phoenix
• 13850 – Corrected an issue with claim status not being updated after successfully sending a primary/secondary claim. After transmitting the claim, the application was looking in the wrong folder for an REC file, which in turn caused the application not properly update claim status.
• Phoenix Broadband
• 14488 – Corrected the issue in the code that pointed at an incorrect IP address. Some users were experiencing an I/O exception error when transmitting claims. The code update corrects this situation.
• Medisoft 14 SP1
• The Medisoft SP1 installation now features an NPI Only check box. This check box replaces the functionality of the NPI: trigger that was introduced in release 14.04. If your insurance carrier requires NPI only data, go to the Lists menu and select Insurance and then select Carriers. On the Address tab of the Insurance Carriers window, click the NPI Only check box. For each carrier be sure to remove the custom NPI: trigger from the Insurance Carrier Entry window, Address tab, Practice ID field. Check with your insurance carriers to see if they require NPI only data. If your carrier requires NPI data along with legacy data, you will need to select the NPI Only check box and then enter a trigger in Medisoft on the Insurance Carrier Entry window, Address tab, Practice ID field. In this field enter NPI:. Loop 2010AA Segment REF and Loop 2310B Segment REF features a new REF segment that will pull this data for claims directed to this carrier.
• Version 14.09
• ERA
• 13622 – Corrected an error in the application code that produced an error message when downloading new remittance files.
• NYEB
• 13741 – The manual and checklist were updated to reflect the new payer IDs associated with the Medicare J13 transition to NYEB. The new payer numbers are:
  
  

  Region	Payor Number
  Connecticut	13102
  New York (Downstate)	13202
  New York (Upstate)	13282
  New York (Queens)	13292

  
  
• RelayHealth
• 14038 – Corrected a file formatting situation in which the delimiters used by RelayHealth were not creating a valid file format for reports. Added a new routine to the application code that translates various delimiters into a common format.
• 14190 – Corrected a delimiter formatting translation issue that was impacting ERA posting. Added a new routine to the application code that translates various delimiters into a common format.
• All Modules
• 14005 – Modified the application code to correct missing delimiters in Loop 2430 DTP.
• 14005 – Modified the application code to correct missing delimiters in Loop 2430 DTP.
• Version 14.08
• All Modules
• 13966 – Corrected an issue with using the new Taxonomy utility with Medisoft Network
• Version 14.07 8/08/2008
• All Modules
• 13770 – Modified the application to transmit taxonomy information in one of two segments or in some cases, if a new utility is used to further customize the application, in both segments. The crosswalk was also updated to reflect the change.
  
  If you are sending claims as a group (EDI Receivers window, ID tab, Group Practice box is selected) the taxonomy (Provider, Default PINs tab, Taxonomy Code field) is always sent in the Loop 2310B Segment PRV: Rendering Provider Specialty Info.
  
  If you are not sending claims as a group (EDI Receivers window, ID tab, Group Practice box is not selected) the taxonomy (Provider, Default PINs tab, Taxonomy Code field) is always sent in Loop 2000A Segment PRV: Billing/Pay-to-Provider Specialty.
  
  Some of your payers might require the taxonomy in both of these segments. If your payer requires this, you will need to use the Taxonomy utility. For more information on setting up the Taxonomy utility, search for the topic Taxonomy Utility in the crosswalk help file or download the instructions for using the utility from the KB.
• Version 14.06 7/31/2008
• RelayHealth
• 13549 – Modified the application with a reworded error message to describe a situation that can occur with the RelayHealth module when transmitting claims if the EDI receiver has an invalid submitter ID.
• 13659 – Modified the application to correct an access violation error that could occur in the RelayHealth module after claims transmittal and after viewing and then closing a report.
• 13745 – Modified the application to support a URL change on 8-15-2008 by RelayHealth. On this date the application will use a new URL, https://mbox.collaborationcompass.com/EMFInfoExchange/jsp/login.jsp, for processing transactions. You do not have to make any changes to your setup other than installing the new EDI release.
• ERA
• 13607 – Corrected a build issue for the 14.05 EDI release that contained the 12.01 version of the ERA module.
• FLCT
• 13625 – Updated the FLCT checklist and Direct Module manual to include more information on changing passwords. Before running the updated module, change your password using a web tool from FLCT at http://www.floridamedicare.com/EDI/Gateway/. You will put the new password in the EDI Receivers window, ID and Extras tab, Submitter Password 1 field.
• GPNT
• 13411 – The GPNT Trailblazers module was updated to support submitting to Palmetto GBA in South Carolina. The checklist and direct module manual were also updated with the required settings information along with adding information to the ISA05 field in the crosswalk.
• Version 14.05 6/27/2008
• All Modules
• 13080 – The application was modified to correct an issue in Loop2430 SVD in which the application was transmitting the NDC code instead of the procedure code.
• 13412 and 13414 – Corrected an issue in which the 2320 SBR02 field (individual relationship code) was not transmitting or was transmitting with data from another field.
• Claims Manager
• 13135 – Corrected a filtering issue when sending secondary claims in which the application was not using a selected filter setting and would send all secondary claims instead of the filtered ones.
• 13212 – Corrected an issue with the application not holding the EDI file storage path for ERA files.
• GPNT Trailblazer
• 13355 – The application was modified to support MAC Jurisdiction 1 provider change to Palmetto GBA over GPNet for California, Hawaii, and Nevada. Early boarding began on May of 2008. The crosswalk, checklist, and manual were also updated. The new payor IDs are:
  
  

  State	Payor ID
  California	01192
  Hawaii	01202
  Nevada	01302



• FLCT
• 13487 – The checklist and manual was update to reflect a new requirement of Florida Medicare to have providers change their passwords every sixty days. Users can make this change using a web tool on the FCSO web site or within Medisoft from the EDI Receivers window ID tab in the Submitter Password II field. Providers will need to track when their password is due to expire or wait for the message from the carrier in a session log. If providers do not change their password in 60 day, they will be blocked from sending claims until they change their password in this field or use the web tool on the FCSO web site. Password must be eight characters in length (alphanumeric and uppercase only). The new password must be different from the old password by at least four characters. Passwords cannot match mailbox numbers and cannot repeat within ten changes.
• FLMC
• 12566 – The application was modified to support the new EDS claims processing system. The checklist, manual, and crosswalk were also updated to document new set up information for the FLMC module.
  
  Changes to NM1 09 in Loops 2010AA, 2010AB, 2310A, 2310C, 2310D, 2310E, 2420A, 2420B, and 2420E include noting the formatting exception for FLMC of: If the value in NM108 is equal to 24, the value sent in NM109 must follow the format of XX-XXXXXXX.
  
  Changes to REF 02 in Loops 2010AA, 2010AB, 2310A, 2310B, 2310C, 2310D, 2310E, 2420A, and 2420B include noting the formatting exception for FLMC of: If the value in REF01 is equal to EI, the value sent in REF02 must follow the format of XX-XXXXXXX.
• PABS
• 13356 – The checklist and manual was updated to support J12 Medicare provider change for Delaware, District of Columbia, Maryland, New Jersey, and Pennsylvania to Highmark through PABS in July of 2008. New payor IDs are:
  
  

  State	Payor ID
  Delaware	12102
  District of Columbia	12202
  Maryland	12302
  Pennsylvania	12501
  New Jersey	12401



• Phoenix and RelayHealth
• 13472 – Modified the application to create Loop 2000A Segment PRV to transmit the taxonomy code. For Florida Medicaid with payor ID 1478 (RelayHealth) the segment creates and with payor ID MC010 (Phoenix) the segment creates. The crosswalk was also updated to document the change.
• RelayHealth
• 13434 – Changed the data formatting for 2430 SVD05 and 2400 SV104. If there is a decimal value, the leading zeros in front of a decimal value are dropped.
• Version 14.04 5/23/2008
• All Modules
• 13078 and 13323 – The code was modified to now support transmitting NPI data only or NPI data and select legacy data. These options require you to set up a custom trigger to take advantage of the new features. The crosswalk was also updated to reflect the changes in the code.
  
  Some Insurance Carriers now require that submitted claims only contain NPI data. Other carriers require NPI data along with legacy data. Check with your carrier to verify before making any changes to your system settings.
  
  If your carrier requires NPI data only, you will need to enter a trigger in Medisoft on the Insurance Carrier Entry window, Address tab, Practice ID field. In this field enter NPI:. Also, if your carrier requires NPI only data on/after May 23, you will need to remove the pin number and qualifier and the group ID and qualifier from the PIN matrix on the Insurance Carrier window, PINs tab.
  
  If your carrier requires NPI data along with legacy data, you will need to enter the NPI: only trigger and leave the data in PIN matrix, Loop 2010AA Segment REF and Loop 2310B Segment REF now feature a new REF segment that will pull this data for claims directed to this carrier.
  
  Segments affected by these changes include: 2010AA Segment REF, 2010AB Segment REF, 2310A Segment REF, 2310B Segment REF, 2310C Segment REF, 2310D Segment REF, 2310E Segment REF, 2420A Segment REF, and 2420B Segment REF.
• Version 14.02 5/2/2008
• All Modules
• 13173 – The Insured Relationship 1, 2, and 3 fields are now replaced by the Insured Relationship Code 1, 2, and 3. The crosswalk was also updated.
• 13197 – The application code was modified to support transmitting test results in Loop 2400 MEA. If you need to transmit test results you will need to enter the data in Medisoft in Transaction window, Transaction Documentation window Documentation/Notes field. You will need to also select from the Type list EDI: Special Conditions.
  
  The format of this entry is composed of four parts. The first part of the entry is @MEA:.
  
  The second part of this entry is either one of the following values with an * after it:
  
  

  Entry	Definition
  OG	Original Starting Dosage
  TR	Test Results

  
  The third part of this entry is one of the following values with an * after it:
  
  

  Entry	Definition
  GRA	Gas Test Result
  HT	Height
  R1	Hemoglobin
  R2	Hematocrit
  R3	Epoetin Starting Dosage
  R4	Creatin
  ZO	Oxygen

  
  The fourth part of this entry is the actual measurement value.
  
  For instance a valid entry in the Documentation/Notes field to transmit test results could be: @MEA:TR*GRA*50.
• APN1
• 13206 – Modified the application code to only generate the second REF segment of 2010AA if the REF02 field has a value. This change corrects an issue with rejections due to the segment generating without a value in the REF02 field for certain legacy numbers for Medicare claims. The crosswalk was also updated.
• Version 14.01 4/4/08
• All Modules
• 13039 – Changes were made in the application code to correct an issue with data reporting in 997 reports. The reports now display the correct information.
• 13101 – Corrected a situation in which users received an error message when attempting to download ERA files. The error message reported that a remittance file could not be renamed, followed by a second error message that documented that a transmission error occurred due to an invalid file name. Made changes to correct an error in which the application was not storing the complete file path name. If you encountered this error, you will need to clear a registry entry. To do this: on the Windows taskbar click Start and select Run. On the Run window in the Open field, type in regedit. In the Registry Editor and from the directory list, go to HKEY_current_user folder, Software, Medisoft, Edi and delete all entries with a bad file path.
• AVAP
• 13069 – Corrected a situation in Loop 2010AB Segment REF 02 in which the PINs value and the Payee Number pulled instead of only the Payee Number. – Now is releasing in 14.02
• GPNT
• 12761 – Changes were made to the application to support the changes for MAC Jurisdiction 4 transition to Trailblazers. The crosswalk was updated to along with the GPNT checklist. The new payor IDs and dates are:



State	New Payor IDs	J4 MAC Effective Date
CO	04102	3-21-08
NM	04202	3-1-08
OK	04302	3-1-08



• Version 14.00 02/29/2008
• Initial Release

• Fixed an issue where the adsstamp utility would allow a serial number with spaces at the end to be pasted in to the dialog. The extra spaces could have a negative effect on the registration process.
• Fixed a memory leak if the ADO.NET provider was used to retrieve primary key or other index schema information.
• Fixed an issue where a restore of DBF tables would return a 5198 error if the table schema in the dictionary did not match the physical schema of the table in the backup image.
• Fixed an issue where a single error was returned (instead of a list of all errors and warnings) during a restore operation if an error was encountered when processing the last table in the backup image.
• Fixed an issue where the configuration value DISABLE_FREE_CONNECTIONS was not always respected.
• Fixed an issue where the CREATE DATABASE command could be run from non-ADSSYS user accounts.
• Fixed an issue where the CREATE DATABASE command did not parse correctly if run in an SQL script. It would return the error: "Unexpected token: XXXX -- Expecting semicolon".
• Fixed an issue where a specific combination of RI creation and trigger execution would cause the server to hang.
• Fixed an issue that could result in a server crash when invalid mailslot data was sent to the server during the discovery process.
• Fixed an issue where the Advantage NLM would still present a prompt to the user when unloaded via the command line, even if the SUPPRESS_MESSAGE_BOXES configuration parameter was set.
• Fixed an issue where the Advantage Configuration Utility (ads_cfg.exe) was enforcing a maximum number of work areas limit (255 per connection) that was lower than the actual limit (64k per connection).
• Fixed an issue where the server would return a 2228 error when executing a view that was created with an older version of Advantage, and ended with a semi-colon.
• The SQL optimizer now handles restrictions joined with the OR operator more accurately. It improves performance of some SQL queries that use this form of restriction.
• Fixed an issue in the SQL optimizer that may cause incorrect results to be returned in rare cases when a subquery or view is the child of a LEFT JOIN and there are restrictions applicable to the child query from the parent query.
• Fixed an issue that could lead to a server crash in rare cases when the SQL engine failed to read from an intermediate file. The likely scenarios for the read failure where when a virus scanner or backup software prevented Advantage from reading the file.
• Fixed an issue in the SQL optimizer that could cause a parameterized query to run slower the second time when the parameter value changed. The query optimizer failed to devise a new evaluation plan based on the new parameter value.
• Fixed an issue that could cause table corruption or other instability when the call to get the file length from OS failed. The reported case for this issue is when there are multiple cluster names on a Windows host and the Advantage server opened the file using both drive letter and a UNC path. The server will now returned an error if the file length cannot be obtained from the OS.
• Modified the cache subsystem to use the windows PSAPI to obtain more accurate Advantage memory usage information when adjusting the cache size. Previously, the memory used by Advantage Extended Procedures was not taken into consideration.
• Fixed an issue that may prevent errors that occur during startup of the Advantage Database Server for Linux from being logged properly.
• Modified the server to log the IP address of invalid TCP requests.
• Fixed an issue where the Advantage Local Server could get an access violation when attempting a connection on the Windows 98 operating system.
• Fixed an issue where the server would get an access violation if an invalid work area number was sent from the client on a record update operation.
• Fixed an issue that would cause a 9009 error when a user connection timed out.
• Fixed an issue that would result in a 9067 error when a computer had more than 2 IP addresses.

• System Requirements
• Medisoft Version 12 Service Pack 2 is now supported on the Microsoft Vista Business operating system.
• Reports
• The Billing/Payment Status report now offers an option to either include or exclude closed cases. The current report only excludes.
• The Practice Analysis report now displays the range included on the report at the top of the page, rather than the date the report was run.
• The Patient Collection Report totals value is now calculated correctly.
• The Production by Provider report did not show any amounts in the Actual Adjustment column. This has been corrected.
• Medisoft V12 would lock up after clicking [OK] in the printer setup for Patient Day Sheet.
• The Primary insurance aging report will now show 20 characters for the policy number.
• When printing Superbills, the Provider now functions properly.
• Errors
• Reset Accounting within MediUtils still causes the error “error: tblMemTransLoad: Type mismatch for field "Amount", expecting: BCD actual” in the communications manager tables. This has been corrected in SP2.
• Backing up while using Global Login no longer causes messages stating that the user is logged in on another computer.
• Random Access violations that were occurring in transaction entry have been corrected.
• The random Access Violations in Office Hours when appointments are moved have been corrected.
• Clicking the Find Next button in the Work Administrator no longer results in the error - qryMisc: Cannot perform this operation on a closed dataset.
• MediUtils now forces Medisoft to be closed before it will run.
• Claims Manager
• The Claims Manager Report now has time stamps.
• The Last Modified date is no longer incorrect after completing service enrollment.
• Program Workflow
• Added grid fields no longer disappear when clicking in the grid.
• Added grid fields no longer disappear in transaction entry when changing chart numbers.
• The guarantor quick ledger no longer displays transactions for the wrong patient when accessed from Transaction Entry.
• Documentation
• Box 17a on the Clickable CMS – 1500 has been updated.
• The 'Medical' practice type is now included in the Help files.
• Other
• Running a backup in MediUtils now creates the .mbk backup file.
• Box 24J in CMSFILE and CMS11 now prints 12 character PIN numbers.
• Box 33 in CMSFILE now prints Practice Information if the claim provider Entity Type field is set to Non-Person. It prints provider information if the claim provider Entity Type field is set to Person.
• Billing and Collections
• In the Collections List, if you save a tickler without selecting a chart number, the message has been changed to read “Field ‘Chart Number” must have a value”.
• If a claim is split in claim management, both claims will have a populated user code field. Previously, the user code field of the new claim was blank.
• If deleting a Collections List item, the default selected button will now be “No” instead of “Yes”.
• The apply payment window in Transaction Entry will now allow you to proceed using the enter key.
• Payments entered into Transaction Entry were not always being reflected in the Remainder Balance field within the Patient record. This caused the Remainder Balance in Office Hours Pro to show a different amount than the actual remainder balance. This has been corrected.
• Patient Statement slowness when printing has been corrected.
• CMS - 1500 with payment formats will be included in Add/Copy user reports screen.
• CMS - 1500 With Form formats will be included.
• Transaction notes now include a scroll bar so notes longer than six lines are visible.
• Deleting payments in Medisoft Original no longer results in a message referring to the deposit list.
• When applying a patient payment in the deposit list, you will now be able to advance to the next transaction using the enter/tab keys.
• “Not a valid integer” errors when searching for a Superbill have been corrected.
• If a payment has the complete box unchecked, a message will appear warning the user that statements in statement management may be affected by this change, and to go remove the transactions in question from their respective statements.
• Users can now delete rejection codes from the apply payment window.
• The error “you must close the popup window (Apply payments to charges) first” no longer occurs in transaction entry.
• When deleting an applied co-payment, the error “'Copayment_Amount Expected' not found,'“ no longer occurs.
• Electronic Claims and Remittance
• Medisoft Claim Manager Direct is included in Medisoft V12 SP1. Additionally, multiple fixes were made to existing Claim Manager components.
• A new menu item has been added to the tools menu if the Direct ERA module has been purchased and installed. This will allow Direct ERA to be utilized with ANY ANSI compliant remittance file.
• Installation
• If online updates are run when no updates are available, a message stating such will appear, rather than a cryptic error message.
• The Products Link under the Help menu is now correct.
• Final Draft
• Final Draft “Save As” now accepts more than eight characters.
• The Final Draft menu has been removed from Medisoft Original.
• Office Hours
• Appointment Lists in Office Hours were sometimes showing the incorrect Provider. This has been corrected.
• When printing a customized Appointment List from the Report Designer, the following error would occur “Error: MissingTablenameProperty.” This has been corrected.
• Negative Remainder Balances now show in Office Hours Pro Remainder fields.
• Office Hours now warns on invalid NPI numbers.
• Changing appointment status no longer removes the values from the case fields.
• Reports
• The option to include AR totals on reports will work properly (corrected in Bundle File).
• Reports no longer pull the practice name from the MWDBLIST.
• Patient List by Diagnosis codes now calculates the patient Age properly (corrected in Bundle File).
• Patient Day Sheet slowness has been corrected (corrected in Bundle File).
• Practice Analysis report now shows dollar amounts up to $99,999,999.
• Monthly and Daily Activity reports now print the correct AR amount (corrected in Bundle File).
• The Patient Day Sheet now pulls the provider from the Transaction line item, rather than the patient record (corrected in Bundle File).
• Aging reports were including some non-eligible transactions. This has been corrected, (corrected in Bundle File).
• The productivity by user report no longer freezes up (corrected in Bundle File).
• Patient Aging Reports were not including transactions that were on the first date of each bucket. This has been corrected.
• The Practice Analysis report no longer calculates deductibles as payments.
• Activity Reports now show totals up to $99,999,999.
• Patient Aging Reports were reflecting some charges twice (most often in cash cases). This has been corrected.
• Communication Manager
• Unprocessed Transactions screen now shows the correct title.
• Editing a case will now cause an update to be sent through the Communications Manager.
• Installation
• Error Field GL_Practice_ID not found when converting root data directories, no longer occurs.
• Users no longer have the option to install Crystal support files when installing Medisoft. They will always be installed.
• List Entry
• In previous versions, if you changed the patient flag, and went to another tab without saving, the flag reverted to the first flag on the list. Medisoft now remembers the flag setting when tabs are navigated.
• The error “Fixed row count must be less than row count” in the provider list has been corrected.
• Clearing the Middle Name for the patient now clears the middle initial.
• MediUtils
• The error “Cannot create file C:\MediData\Tutor\\_LpLock.lok,” occurring when backing up within MediUtils has been corrected.
• MediUtils now creates MWPRA tables with the correct structure.
• Copy data utility within MediUtils will now copy the MWPAT table.
• MediUtils Repair Practice will now repair issues with the MWTSK table.
• MediUtils Repair Practice will now create a valid MWPAT table if necessary. Previously it would leave out the Middle Name field causing errors when accessing the patient list within Medisoft.
• MediUtils Repair Practice will now repair issues with the MWTRG table.
• Error in Transaction Entry “‘tblclaim: Type mismatch for field ‘Amount’, expecting: BCD actual: Currency’" after resetting accounting in MediUtils no longer occurs.
• CMSFILE and CMS11
• CMSFILE and CMS11 now completes city names with spaces properly.
• CMS11 no longer adds lab charges to the totals in box 28.
• CMSFILE and CMS11 were only printing ten characters of the pin numbers. All twelve characters will now print.
• CMSFILE and CMS11 would not pull group IDs unless Group NPIs were entered. These will now pull the group from the pin matrix if the group is entered there. If you don’t want a group, don’t enter one.
• Other Items
• Data connection failures were resulting in deletion of data. These failures now produce an error message without deleting the data.
• The Quick Ledger will now remember sorting changes the next time opened.
• Data was being deleted if the Task Scheduler was running when data was restored. Medisoft will no longer allow you to restore data if the Task Scheduler is running. You will receive a message telling you to exit the task scheduler.
• Design custom data is now available in the demo.
• Unprocessed transactions have been removed from the demo.
• The Crystal Reports Designer no longer installs with Advanced Reports.
• Inactive patients no longer appear in Treatment Plan chart lists.
• Patient Recall list now hides inactive patients.
• When editing the grid within the Work Administrator, the Help button will now function as designed.

• The random Access Violations in Office Hours when appointments are moved have been corrected.
• Appointment Lists in Office Hours were sometimes showing the incorrect Provider. This has been corrected.
• When printing a customized Appointment List from the Report Designer, the following error would occur “Error: MissingTablenameProperty.” This has been corrected.
• Negative Remainder Balances now show in Office Hours Pro Remainder fields.
• Office Hours now warns on invalid NPI numbers.
• Changing appointment status no longer removes the values from the case fields.

• Version 12.17
• RelayHealth
• 14487 – Corrected an issue with a qualifier not populated in Loop 2310A REF01 segment and the state license number not populated in Loop 2310A REF02 segment for payor ID 1421 and 2426. The crosswalk was also updated to reflect the change.
• 14651 – Modified the code for Loop 2010BB Segment REF: Payer Secondary ID for BCBS South Carolina payer number 2410 to send 2U in the REF01 segment instead of FY. The crosswalk was also updated to reflect the change.
• AVAP, Claims Manager, GPNT, Phoenix, and RelayHealth
• 14625 – Corrected and issue with a payee number (Providers window, Default PINs tab, Payee Number) not populated in Loop 2010AB Segment REF: Pay-to-Provider Secondary ID REF02.
• Version 12.16
• Phoenix
• 13865 – Corrected an issue with claim status not being updated after successfully sending a primary/secondary claim. After transmitting the claim, the application was looking in the wrong folder for an REC file, which in turn caused the application not properly update claim status.
• All Modules
• 14809 – Corrected an issue with single and dual taxonomy data displaying in the correct segment(s). For the special case of dual taxonomy, you must submit the claim as a group (see below). Modified the crosswalk to reflect the change.
  
  Taxonomy information is transmitted in one of two segments or in some cases, if the Taxonomy utility is used to further customize the application, in both segments.
  
  If you are sending claims as a group (EDI Receivers window, ID tab, Group Practice box is selected) the taxonomy (Provider, Default PINs tab, Taxonomy Code field) is always sent in the Loop 2310B Segment PRV: Rendering Provider Specialty Info.
  
  If you are not sending claims as a group (EDI Receivers window, ID tab, Group Practice box is not selected) the taxonomy (Provider, Default PINs tab, Taxonomy Code field) is always sent in Loop 2000A Segment PRV: Billing/Pay-to-Provider Specialty.
  
  Some of your payers might require the taxonomy in both of these segments. If your payer requires this, you will need to use the Taxonomy utility. You also must submit the claim as a group (EDI Receivers window, ID tab, Group Practice box is selected).
  
  For more information on setting up the Taxonomy utility, search for the topic Taxonomy Utility in the crosswalk help file or download the instructions for using the utility from the KB.
• Version 12.15
• Claims Manager
• 13718 – Corrected an issue with the application not holding the EDI file storage path for ERA files.
• RelayHealth
• 14039 – Corrected a file formatting situation in which the delimiters used by RelayHealth were not creating a valid file format for reports. Added a new routine to the application code that translates various delimiters into a common format.
• 14192 – Corrected a delimiter formatting translation issue that was impacting ERA posting. Added a new routine to the application code that translates various delimiters into a common format.
• All Modules
• ation code to correct missing delimiters in Loop 2430 DTP.
• Version 12.14
• All Modules
• 13967 – Corrected an issue with using the new Taxonomy utility with Medisoft Network Pro. For more information on the Taxonomy utility, refer to the entry below in Version 12.13.
• Version 12.13 8/08/2008
• All Modules
  • 13771 – Modified the application to transmit taxonomy information in one of two segments or in some cases, if a new utility is used to further customize the application, in both segments. The crosswalk was also updated to reflect the change.
    
    If you are sending claims as a group (EDI Receivers window, ID tab, Group Practice box is selected) the taxonomy (Provider, Default PINs tab, Taxonomy Code field) is always sent in the Loop 2310B Segment PRV: Rendering Provider Specialty Info.
    
    If you are not sending claims as a group (EDI Receivers window, ID tab, Group Practice box is not selected) the taxonomy (Provider, Default PINs tab, Taxonomy Code field) is always sent in Loop 2000A Segment PRV: Billing/Pay-to-Provider Specialty.
    
    Some of your payers might require the taxonomy in both of these segments. If your payer requires this, you will need to use the Taxonomy utility. For more information on setting up the Taxonomy utility, search for the topic Taxonomy Utility in the crosswalk help file or download the instructions for using the utility from the KB.
• Version 12.12 7/31/08
• RelayHeath
• 13550 – Modified the application with a reworded error message to describe a situation that can occur with the RelayHealth module when transmitting claims if the EDI receiver has an invalid submitter ID.
• 13746 – Modified the application to support a URL change on 8-15-2008 by RelayHealth. On this date the application will use a new URL, https://mbox.collaborationcompass.com/EMFInfoExchange/jsp/login.jsp, for processing transactions. You do not have to make any changes to your setup other than installing the new EDI release.
• Phoenix
• 13608 – Corrected a build issue for the 12.11 Phoenix update which installed a beta version of 12.04 instead of the most current version.
• Version 12.11 6/27/08
• All Modules
• 13081 – Corrected an issue in Loop2430 SVD in which the application was transmitting the NDC code instead of the procedure code.
• RelayHealth
• 13433 – Changed the data formatting for 2430 SVD05 and 2400 SV104. If there is a decimal value, the leading zeros in front of a decimal value are dropped.
• Phoenix and RelayHealth
• 13463 –Modified the application to create Loop 2000A Segment PRV to transmit the taxonomy code. For Florida Medicaid with payor ID 1478 (RelayHealth) the segment creates and with payor ID MC010 (Phoenix) the segment creates. The crosswalk was also updated to document the change.
• Version 12.10 5/23/08
• All Modules
• 13075 and 13222 – The code was modified to now support transmitting NPI data only or NPI data and select legacy data. These options require you to set up a custom trigger to take advantage of the new features. The crosswalk was also updated to reflect the changes in the code.
  
  Some insurance carriers now require that submitted claims only contain NPI data. Other carriers require NPI data along with legacy data. Check with your carrier to verify before making any changes to your system settings.
  
  If your carrier requires NPI data only you will need to enter a trigger in Medisoft on the Insurance Carrier Entry window, Address tab, Practice ID field. In this field enter NPI:. Also, if your carrier requires NPI only data on/after May 23, you will need to remove the pin number and qualifier and the group ID and qualifier from the PIN matrix on the Insurance Carrier window, PINs tab
  
  If your carrier requires NPI data along with legacy data, you will need to enter the NPI: only trigger and leave the data in PIN matrix—Loop 2010AA Segment REF and Loop 2310B Segment REF now feature a new REF segment that will pull this data for claims directed to this carrier.
  
  Segments affected by these changes include: 2010AA Segment REF, 2010AB Segment REF, 2310A Segment REF, 2310B Segment REF, 2310C Segment REF, 2310D Segment REF, 2310E Segment REF, 2420A Segment REF, and 2420B Segment REF.
• Version 12.08 5/2/08
• All Modules
• 13089 – The application code was modified to support transmitting test results in Loop 2400 MEA. If you need to transmit test results you will need to enter the data in Medisoft in Transaction window, Transaction Documentation window Documentation/Notes field. You will need to also select from the Type list EDI: Special Conditions.
  
  The format of this entry is composed of four parts. The first part of the entry is @MEA:.
  
  The second part of this entry is either one of the following values with an * after it:
  
  

  Entry	Definition
  OG	Original Starting Dosage
  TR	Test Results

  
  The third part of this entry is one of the following values with an * after it:
  
  

  Entry	Definition
  GRA	Gas Test Result
  HT	Height
  R1	Hemoglobin
  R2	Hematocrit
  R3	Epoetin Starting Dosage
  R4	Creatin
  ZO	Oxygen

  
  The fourth part of this entry is the actual measurement value.
  
  For instance a valid entry in the Documentation/Notes field to transmit test results could be: @MEA:TR*GRA*50.
• APN1
• 13176 – Modified the application code to only generate the second REF segment of 2010AA if the REF02 field has a value. This change corrects an issue with rejections due to the segment generating without a value in the REF02 field for certain legacy numbers for Medicare claims. The crosswalk was also updated.
• Version 12.07 4/4/08
• All Modules
• 12720 – Changes were made in the application code to correct an issue with data reporting in 997 reports. The reports now display the correct information.
• 13095 – Corrected a situation in which users received an error message when attempting to download ERA files. The error message reported that a remittance file could not be renamed, followed by a second error message that documented that a transmission error occurred due to an invalid file name. Made changes to correct an error in which the application was not storing the complete file path name. If you encountered this error, you will need to clear a registry entry. To do this: on the Windows taskbar click Start and select Run. On the Run window in the Open field, type in regedit. In the Registry Editor and from the directory list, go to HKEY_current_user folder, Software, Medisoft, Edi and delete all entries with a bad file path.
• AVAP
• 13072 – Corrected a situation in Loop 2010AB Segment REF 02 in which the PINs value and the Payee Number pulled instead of only the Payee Number.
• Remittance
• 12844 – Changes were made to the ERA application and all the direct modules so that the applications use the same file path to the ERA data. Users will need to download the latest ERA and direct module updates.
• NYEB
• 12995 – Made changes to correct a claims rejection problem. NYEB commercial claims requires positions 4-7 of the NPI in Loop 2010AA. If there is not an NPI value, positions 3-6 of the PIN for NYEB. Crosswalk updated to document this change.
• WPS1
• 12939 – Corrected a communications issue with users not being able to receive reports when using the WPS1 module.
• Version 12.06 2/29/08
• All Modules
• 12720 - Changes were made in the application code to correct an issue with data reporting in 997 reports.
• 12429 - Changes were made to the ERA application and all the direct modules so that the applications use the same file path to the ERA data. Users will need to download the latest ERA and direct module updates.
• 12669 - Changes were made in the application code to correct a situation in which the CN1 segment was not creating in Loops 2300 or 2400 with secondary claims. The segment now creates.
• Claim Manager
• 11046 - Fixed an issue with default data path when selecting a path for saving data.
• 12058 - Changes were made in the application code to correct an issue with applying the Claim Created Date Data filter that produced an error.
• Remittance
• 12490 - Changes were made in the application code to correct an I/O Error 123 that users sometimes encountered when opening or downloading ERA files; the application now utilizes a new window for storing ERA data.
• AIM1
• 12067 - If the EDI Payor Number is MC021, the segment will create.
• GPNT
• 12736 - Changes were made to the application to support the changes for MAC Jurisdiction 4 transition to Trailblazers. The crosswalk was updated to along with the GPNT checklist. The new payor IDs and dates are:



State	New Payor IDs	J4 MAC Effective Date
CO	04102	3-21-08
NM	04202	3-1-08
OK	04302	3-1-08



• NYEB
• 12654 - The direct module now supports the M2 EDI Gateway. The application was updated to support the use of the new M2 trading partner ID, and the checklist for NYEB documents the fields in the application that use the M2 ID.
• WPS
• 12737 - The application now supports new WPS Payor IDS for MAC Jurisdiction 5. The new payor IDs and transition dates are:



State	New Payor IDs	Transition Date
Kansas	05202	3-1-08
Missouri (Western)	05302	3-1-08
Missouri (Eastern)	05392	6-1-08
Nebraska	05402	3-1-08



• Version 12.05 1/11/08
• All Modules
• 11722 - Modified code to address an issue with Claims Manager when creating and transmitting secondary claims after the primary was billed.
• 12028 - The application code for the Phoenix module was modified to generate Loop 2300 Segment REF CLIA Number for Michigan Medicaid (Payer ID MC035). Crosswalk also updated to reflect this change.
• 12076 - The method for selecting an EDI module to install has changed to now utilize a list box.
• 12160 - Modified the application to create Loop 2000A Segment PRV for Payer ID MC048 and Payer ID MC087 when sending as a group. Modified the Crosswalk to document this exception.
• 12396 - Updated the application code to not generate purchased service information when blood draws or specimen collections are performed by practitioners but then process at outside labs. The application applies new logic of if the code is 99000 or 36415 and the pos is 11 or 12, do not treat the entry as a purchased service to the following:
• Loop 2300 Segment AMT NE Qualifier with the logic applied to the transaction level and then to the total claim purchased service
• Loop 2400 Segment PS1 Purchased Service Info with the logic applied to the transaction level
• Loop 2400 REF Segment Referring CLIA Facility ID F4 Qualifier with the logic applied to the claim level and the transation level
• Loop 2420B logic applied to the entire loop at the claim level and at the transation level
• NHIC
• 12492 - Changed were made to the login script. Users will need to change the modem baud rate in the EDI Receiver window Modem tab to 57.6k.
• NYEB
• 11808 - Updated the application code for NYEB module to transmit in Loop 2012 AA Segment REF Eight REF 02 positions 4-8 for the provider number--change was required for NPI. Crosswalk also updated to reflect this change.
• AVAP
• 11861 - The application code for the AVAP module was changed to not send Loop 2000A Segment PRV segment when sending AVAP claims for a group. Crosswalk also updated to reflect this change.
• Phoenix
• 12263 - In certain instances mammography and purchased service claims were including facility information even though a facility was not assigned in the claim. The problem has been fixed.
• WPS1
• 12351 - Application code was changed to support the new bbs implementation by WPS1. The new WPS EDI BBS telephone number is 608-287-1581.
• Version 12.04 10/26/07
• All Modules
• 11360 - Loop 2300, Segment AMT was not always being created. The segment is now created if the following conditions are met:
• Insurance Carrier, Type is Medicare
• Provider, Medicare Participating is not checked
• Case, Assignment of Benefits/Accept Assignment is not checked
• 11667 - The fifth REF segment of Loop 2010AA was not sending when the calculated qualifier in REF01 was the same as the qualifier in the first REF segment even though the values in REF02 were different. The program now creates the fifth REF segment if the calculated qualifier in REF01 is the same as the qualifier in the first REF segment as long as the values in REF02 are different.
• 11689 - When present, Loop 2430, Segment CAS included trailing asterisks that would cause rejections. The asterisks have been removed.
• 11849 - The EDI data files are now located under the following default location: C:\Medidata\Practice Name\Module Name\EDI. If your practice name is Smith, and the module is AVAP, the EDI files will be in C:\Medidata\Smith\AVAP\EDI.
• CIGN
• 12001 - The payer is requiring the User Name to go in EDI Receiver, Submitter ID 1 and the File Name (without the .x12 extension) in EDI Receiver, Submitter Password 1. Then when you transmit claims, it will ask for the user name and password.
• Claims Manager
• 11499 - A progress window now appears when transmitting claims and receiving reports.
• Phoenix BB
• 11841 - When downloading reports, users on Vista were receiving an error, Getting Wrong Number of Arguments. The problem has been fixed.
• Version 12.03 09/07/07
• All Modules
• 11343 - Users who are on Windows Server 2003 were experiencing problems sending claims. They were getting the error "File Access Denied." The problem has been fixed.
• AVAP
• 11384 - Changed Loop 1000A NM109 to pull the value in Insurance Companies, EDI/Eligibility tab, Submitter ID field. If there is no value in that field, it pulls the value in EDI Receivers, ID tab, Submitter Password 1. The Submitter ID field is for Noridian Medicare customers who need to enter a unique clinic-level Submitter ID.
• 11645 - Users were unable to upload more than one claim file to Availity because the program names all the XMT files the same. Changed the program to name the XMT files dynamically so users can upload multiple claim files.
• AVAP, Claims Manager, GPNT, and Phoenix
• 11428 - Changed the REF segments of Loops 2010AA, 2010AB, and 2310B to pull the Payee Number field from the Providers, Default PINS tab when sending claims for Illinois Medicaid.
• Phoenix Dial-Up
• 11647 - the clearinghouse began storing ERA files in a new directory, so users were not getting their ERA files when they clicked Electronic Remittance in the Phoenix dial-up module. The program has been changed to access the new directory for ERA files at the clearinghouse.
• Remittance
• 7522 - If there is a crossover payer designated in the remittance file, the program will display the crossover payer name on on the remittance reports.
• Version 12.02 07/20/07
• All Modules
• 9612 - The Remittance Tracking window has been resized to fit the information in the window.
• 10468 - Some modules were posting blank reports, and the program failed when trying to convert them. The program has been modified to accept blank reports.
• 10606 and 10616 - There was a transmission error when downloading reports. It occurred when the program attempted to convert reports to a viewable format. The problem has been fixed.
• 11251 - Increased the number of stored reports from 10 to 50.
• Phoenix Broadband
• 10839 - A communication error, Error: File not sent, was occurring. The problem was fixed by MedAvant.
• Remittance
• 10408 - A 7057 error was occurring when posting an ERA file with takebacks. The problem has been fixed.
• 10712 - There was a problem when posting reversals items with no entry numbers. The problem has been fixed.
• 11113 - Changed the program to populate the adjustment and payment date fields in the Deposit List and Transaction Entry with the same date as the deposit from the 835 file.
• WPS1
• 10580 - There was an error in the scripting from WPS1 when downloading reports. The problem has been fixed.
• Version 12.01 06/13/07
• All Modules
• 10601 - For secondary claims, the program sends the Coordination of Benefits Payer Paid Amount AMT segment of Loop 2320 whenever a payment is applied. Previously the program would not send the segment when a zero dollar payment was applied. It now sends the segment as long as a payment has been applied.
• 10798 - For Medicare Secondary claims, the program sends nothing in 2000B SBR03.
• 10799 - For Medicare Secondary claims, the program sends 47 if the Case, EDI tab, Insurance Type Code field is a 0.
• 10815 - For group claims, the program sends only group NPI numbers in the applicable NM1 and REF segments of 2010AA and 2010AB.
• CIGN
• 10592 - The module was not uploading claims. The problem has been fixed.
• GPNT
• 10863 - If the program tries to create a second REF segment with the same value in REF02 in Loops 2010AA, 2010AB, 2310B, 2310C. 2310D, 2310E, 2420A, or 2420B, the identical REF segment will not be sent.
• INET
• 10797 - The program was having a problem connecting to the BBS. The problem has been fixed.
• Phoenix
• 10502 - Fixed the error “A matching REC file could not be found.”
• TNBB
• 9255 - The program no longer sends the taxonomy segment (PRV) in Loop 2000A for payer ID 00390. It still sends the PRV segment in Loop 2310B.
• UHIN
• 10402 - The program sends the CLIA number REF segment in Loop 2300 for payer ID HT000004-001.
• WMSC
• 9590 - The module can create a file for manual upload to new processing system.
• Version 12.00 04/02/2007
• Initial Release

The following issues were fixed in Office Hours Pro Version 11 Service Pack 4:

1.  Cancelled Appointments were printing on default Superbill format.

2.  Appointment list report in office hours displaying incorrect provider.

1 = Service Pack 1 Updates
2 = Service Pack 2 Updates

1          Enabled Office Hours conversion from V10 Stand alone to V11. 
1          Corrected Provider drop down error in Pro. 
1          Added document number to transaction entry from Office Hours Pro through copay entry. 
2         Demo installs to Medisoft directory instead of Medisoft DEMO directory.
2         Issue with canceling appointments in a template.
2         Cancel an appointment, confirm the cancellation, appointment is still showing up on the grid.
2         Error 7112 when printing appointment report.
2         Tries to open Medisoft twice when entering co-pay.
2         Audit generator shows the changes of level 3 user, but logged under the user startup.
2         Reports causing error “Invalid Stream Format”.
2         Audit trail does not keep track of proper scheduling individual.
2         The note wording for a rescheduled appointment is misleading.

• Version 11.18 1/11/08
• All Modules
• 12397 – Updated the application to not generate purchased service information when blood draws or specimen collections are performed by practitioners but then processed at outside labs. The application applies new logic of if the code is 99000 or 36415 and the pos is 11 or 12, do not treat the entry as a purchased service to the following:
• Loop 2300 Segment AMT NE Qualifier with the logic applied to the transaction level and then to the total claim purchased service
• Loop 2400 Segment PS1 Purchased Service Info with the logic applied to the transaction level
• Loop 2400 Segment REF Referring CLIA Facility ID F4 Qualifier with the logic applied to the claim level and the transaction level
• Loop 2420B logic applies to the entire loop at the claim level and at the transaction level
• Phoenix
• 12325 – In certain instances mammography and purchased service claims were including facility information even though a facility was not assigned in the claim. The problem has been fixed.
• NYEB
• 11808 – Updated the application code for NYEB module to transmit in Loop 2010 AA Segment REF Eighth REF 02 positions 4-8 for the provider number--change was required for NPI. Crosswalk also updated to reflect this change.
• Version 11.17 11/27/07
• All Modules
• 11360 – Loop 2300, Segment AMT was not always being created. The segment is now created if the following conditions are met:
• Insurance Carrier, Type is Medicare
• Provider, Medicare Participating is not checked
• Case, Assignment of Benefits/Accept Assignment is not checked
• 11667 – The fifth REF segment of Loop 2010AA was not sending when the calculated qualifier in REF01 was the same as the qualifier in the first REF segment even though the values in REF02 were different. The program now creates the fifth REF segment if the calculated qualifier in REF01 is the same as the qualifier in the first REF segment as long as the values in REF02 are different.
• 11689 – When present, Loop 2430, Segment CAS included trailing asterisks that would cause rejections. The asterisks have been removed.
• AVAP, GPNT, and NYMA
• 11712 – Loop 2010AB was not creating. The problem has been fixed.
• Version 11.16 09/07/07
• Phoenix Dial-Up
• 11647 – The clearinghouse began storing ERA files in a new directory, so users were not getting their ERA files when they clicked Electronic Remittance in the Phoenix dial-up module. The program has been changed to access the new directory for ERA files at the clearinghouse.
• AVAP, GPNT, and Phoenix
• 11428 – Changed the REF segments of Loops 2010AA, 2010AB, and 2310B to pull the Payee Number field from the Providers, Default PINS tab when sending claims for Illinois Medicaid.
• Version 11.15 07/20/07
• GAMS
• 11158 - The NPI was triggering multiple GS-GE functional sets when only one was required. The problem has been fixed.
• GPNT and AVAP
• 11154 - File was getting rejected because a 1000A PER segment had the incorrect separator in the phone number. The problem has been fixed.
• Version 11.14 06/13/07
• All Modules
• 10601 - For secondary claims, the program sends the Coordination of Benefits Payer Paid Amount AMT segment of Loop 2320 whenever a payment is applied. Previously the program would not send the segment when a zero dollar payment was applied. It now sends the segment as long as a payment has been applied.
• 10798 - For Medicare Secondary claims, the program sends nothing in 2000B SBR03.
• 10799 - For Medicare Secondary claims, the program sends 47 if the Case, EDI tab, Insurance Type Code field is a 0.
• 10815 - For group claims, the program sends only group NPI numbers in the applicable NM1 and REF segments of 2010AA and 2010AB.
• CIGN
• 10592 - The module was not uploading claims. The problem has been fixed.
• GPNT
• 10863 - If the program tries to create a second REF segment with the same value in REF02 in Loops 2010AA, 2010AB, 2310B, 2310C. 2310D, 2310E, 2420A, or 2420B, the identical REF segment will not be sent.
• Phoenix
• 10502 - Because MedAvant added a new line to the Daily Claims Verification Statement, users were getting the following error: Matching REC file could not be found. Made changes to how the program reads the report to fix the error.
• TNBB
• 9255 - The program no longer sends the taxonomy segment (PRV) in Loop 2000A for payer ID 00390. It still sends the PRV segment in Loop 2310B.
• UHIN
• 10402 - Made changes to create the X4 REF segment of Loop 2300 when EDI Receiver, EDI Payor Number is HT000004-001. The segment still requires that there be a CLIA number in the patient’s case.
• WMSC
• 9590 - The module can create a file for manual upload to new processing system.
• Version 11.12 03/23/07
• PHOENIX
• 10478 - When your password expires, the program verifies that the old password is valid. If the old password is not valid, it will pop up a window where you can reenter the password.
• Version 11.11 03/13/07
• GPNT
  • 10238 - This release accounts for two PIN entry methods for electronic claims. Updated GPNT Module populates the REF with the PIN Matrix qualifier (if present) and the PIN from the Default PIN field if the PIN Matrix has a qualifier without an associated PIN. Electronic claims created using the original rules and instructions for PIN Matrix data values remain and are unchanged by this additional functionality.
  • 10369 - This release accounts for 835 (Electronic Remittance Advise) transactions that come from a payer with unexpected CR/LF (Carriage Return/Line Feeds). The industry standard for ANSI transactions is one continuous line of data. This enhancement will remove the unexpected CR/LFs and format the transaction in the Medisoft expected format. Data integrity is not jeopardized and there are no changes made to the actual data received from the payer.
  • 10340 - This fix resolves the NM109 Medicare data mapping requirement. 1000A NM109 will pull from Submitter Password 2 when the Region field has WA or WAECC.
• Version 11.09 01/26/07
• All Modules
• 8095 - In the 2010AA REF segment, the program sends a 1D in REF 01 and the Medicaid PIN in REF 02 for payer ID 00824.
• 8898 - The program no longer adds trailing zeros to the fields in the CAS segments in loops 2320 and 2430.
• 8699 - When populating Loop 2310D, the program now pulls the facility from the claim instead of the case.
• 9674 - For all modules except GPNT, the program sends Loop 2300 segment DTP (Initial Treatment Date) if the Date of Manifestation has a value. The Date of Manifestation appears on the Miscellaneous tab of the Case when the Practice Type is set to Chiropractic.
• 9929 - If Purchased Services is not checked in the facility’s record, the program does not create the 2310C REF segment.
• CIGN
• 8908 - The program increments the number for each ST/SE grouping of the claims file.
• FLCT Availity
• 8102 - The program separates GS and GE segments by insurance company.
• GPNT
• 8674 - The program creates Loop 2010BA if the insurance type is Worker’s Comp and the EDI Receiver, Region is WA.
• 9704 - If 2310A Ref 02 is blank, then the program does not create the segment.
• 9733 - If 2400 SV106 has no value, the program no longer inserts 00 in the field.
• GPNT and AIM1
• 9732 - When no PINs are present in the facility, the program will not create Loop 2310D.
• PHOENIX Broadband
• 9639 - When viewing reports, an I/O error would appear. That error has been fixed.
• TNBB
• 9255 - If the Payor Number is 00390, the 200A PRV segment is not created.
• Version 11.07 06/22/06
• All Modules
• 7918 - Changed the CAS segments so that they do not include negative amounts.
• ARMB
• 7999 - Changed the program to send 2000A PRV when the EDI Receiver, Group Practice is not checked. Also, changed the program to send 2310B PRV when EDI Receiver, Group Practice is checked or EDI Receiver, Extra 1 includes 2310B:.
• CAMC
• 7816 - Changed the program so that only six lines are included per claim.
• NDMB
• 7912 - Changed the program to send Iowa Medicare’s new payer ID, 00826.
• Version 11.06 06/16/06
• GPNT
• 8022 - The program now sends the DTP 454 segment of Loop 2300 if the Case, Date First Consulted is valid and the Practice Type is Chiropractic.
• PABS
• 7957 - The program was freezing when receiving ERA files while downloading reports. ERA files are now downloaded when receiving reports from the carrier.
• Version 11.05 05/31/06
• GAMS
• 7878 - Lines of code that are important to GAMS were altered when changes were made to Phoenix. As a result, GAMS reports were not downloading properly. The information required for GAMS was added back in. The problem is now fixed.
• Version 11.04 05/09/06
• All Modules
• 7573 - Because the Claims data table did not have the facility field added to it, an error would appear when splitting claims. That has been fixed.
• 7821 - If sending a purchased services claim, the REF 1C segment of Loop 2310C creates.
• 7336 - Most modules can now send secondary claims. The following loops and segments have been affected by this change:
• 2320 CAS Claim Level Adjustment
• 2320 AMT Payer Amt Paid
• 2320 AMT Payer Allowed
• 2330B DTP Service Date
• 2400 AMT Payer Allowed
• 2430 CAS Line Adjustment
• Check the ANSI crosswalk in the help file for more detailed information about the changes to these segments.
• PHOENIX
• 7529 - There was an access violation when clicking the Print/Send button and then selecting the Phoenix module. That error has been fixed.
• 7806 - If the Payer ID is BS010, then the DTP 454 segment of Loop 2300 creates.
• ARMB
• 7873 - If the practice is a group, then the PRV segment of Loop 2310B creates. If the practice is a group and the insurance type is Medicare or BC/BS, then the PRV segment of Loop 2000A does not create.
• CIPA
• 7525 - Initial release of CIPA module.
• PABS
• 7142 - The AMT D segment of Loop 2320 now creates for claims with Medicare as the secondary.
• WMSC
• 7608 - If sending claims through other communication methods (i.e. ftp), enter NOTRANSFER in the EDI Receiver, Extension field.
• Version 11.03 04/19/06
• CAMC
• 7582 - The login script has been changed to wait for the VOLSER report from CAMC while sending claims. Also, the program has been changed so that you can send claims manually. Enter NOTRANSFER in the CAMC EDI Receiver settings, Modem tab, Dialing Suffix field. If you enter NOTRANSFER, the program will create the claim file and save it to a folder. Then you can send the claim file manually.
• Version 11.02 03/27/06
• All Modules
• 7025 - The program copies remittance files to an EOB folder and gives them an EOB extension. These files have segment separators instead of carriage return line feeds.
• PABS
• 7481 - The program no longer downloads e-SPR reports. It now downloads remittance files.
• Version 11.01 03/14/06
• All Modules
• 7400 - Loop 2400, Segment SV1 no longer sends the National Drug code. It sends the procedure code only.
• GPNT
• 5930 - If Insurance Carrier, Type is Medicare, the program sends the Transaction, Allowed Amount in AMT02 of Loop 2400, Segment AMT Approved Amount.
• 7049 - If Insurance Carrier, Type is Medicare, the program now sends the REF segment for Loop 2310C. It sends 1C as the qualifier in REF01 and the Facility ID in REF02.
• 7151 - Many secondary GPNT claims were getting rejected. The program now sends the correct primary payment and adjustment information with the claims.
• NYEB
• 5930 - For all insurance types, the program sends the Transaction, Allowed Amount in AMT02 of Loop 2400, Segment AMT Approved Amount.
• 7003 - If Claims Provider, NPI field is filled out, the program sends the NPI number in NM109 of Loops 2010AA and 2310B. It also sends the SSN or Tax ID in the REF segment of Loops 2010AA and 2310B.
• PABS
• 7142 - The program now sends Loop 2320, Segment AMT for Medicare secondary claims.
• Version 11.00 02/09/2006
• Initial Release

Medisoft Version 10 Service Pack 2 (With Hot Fix)

Office Hours Professional Version 10 Service Pack 2

Medisoft Version 9 Service Pack 2

Office Hours Professional Version 9 Service Pack 2

Medisoft Version 8 service pack 2