|
Free Service Packs for Medisoft
Medisoft Version 14 Service Pack 1
Office Hours Professional Version 14 Service Pack 1
Medisoft Version 14 EDI Modules (V14.11)
Advantage Database Server Version 8.1
Medisoft Version 12 Service Pack 2
Office Hours Professional Version 12 Service Pack 2
Medisoft Version 12 EDI Modules (V12.15)
Medisoft Version 11 Service Pack 4
Office Hours Professional Version 11 Service Pack 4
Medisoft Version 11 EDI Modules (V11.18)
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
The items listed in the box to the left explain what things the service pack has either fixed or enhanced. Once you download and install, all of the “fixes” listed will go into your Medisoft program.
| File Description |
(click for install) |
The release includes corrections to issues in the following parts of the software:
- 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
For a complete list of the key defects resolved in this service pack, please visit the following website:
http://www.medisoft.com/download/V14/Medisoft V14 SP1 Release Notes.doc
|
|
- 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
|
|
IMPORTANT: If you use the Phoenix Broadband module, you should not download this module. Phoenix Broadband customers that download this module, will receive an I/O error.
Version History for V14 ANSI Modules
- 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
|
|
Please note that all Medisoft Network Professional and Office Hours Professional for Networks users must update to Advantage Database Server Version 8.1 before applying Medisoft Version 12 Service Pack 2 or Office Hours Professional Version 12 Service Pack 2
- 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.
|
|
Please note that all Medisoft Network Professional and Office Hours Professional for Networks users must update to Advantage Database Server Version 8.1 before applying Medisoft Version 12 Service Pack 2 or Office Hours Professional Version 12 Service Pack 2
The following items were corrected in Medisoft Version 12 Service Pack 2:
- 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 History for V12 ANSI Modules
- 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
|
|
The following items were corrected in Medisoft Version 11 service pack 4 (Posted 6/20//07):
Fixes the slow patient statement issues.
1.
Electronic Statement Summary Reports would not print.
2.
Error: “Field The_Count not found” when
converting data to Version 11.
3.
Ambulance fields would not save in Medisoft Advanced.
Custom case data will now save in advanced, but you do not
have the ability to design custom case data.
The design is still Network Professional only.
4.
CMSFILE and CMS11 print image formats were added.
5.
Group NPI Number was added to the Provider Class screen.
6.
Work Administrator security flaw.
(Displayed user names and passwords in certain circumstances.)
7.
NPI Number Validation was added.
8.
Quick Statements would not print unless the statement
number range was manually removed.
9.
Previously released version of File Maintenance was
included in SP3.
10.
Claim forms pulled Case Facility instead of Transaction
Facility. Now pull Transaction Facility.
11.
Cancelled Appointments were printing on default Superbill
format.
12.
Procedure/Staff List contained 2 date stamps.
13.
Quick Ledger would not open properly from within
Transaction Entry.
14.
Appointment list report in office hours displaying
incorrect provider.
15.
Invalid Credit Card Authorization message within
Transaction Entry.
16.
Provider Class and User Entry added to Medisoft Basic.
1
= Service Pack 1 Updates
2 = Service Pack 2 Updates
Advanced
Reports
1
Corrected
repeatable parameters to redisplay with entered data.
1
Corrected
report import to move reports to the proper tree structure.
2
Corrected code to
fix Export Error - The instruction at “0x7c910455”
referenced memory at “0x05810586” - the memory could not be
“read”/ click on OK to terminate the program.
2
Made changes to
correct system error code 3 - can’t find path specified.
Audit
1
Added
Registration information to bottom of Audit Report.
1
Updated
all audits to use new MWAUDD and MWAUDM tables.
Backup
2
Auto backup data
not converting properly.
Collection
List
2
Name of Work List
changed to Collection List.
2
Made change to
allow edit of item: Ticklers.
2
Is not a valid time
stamp.
2
Tab order of the
Add Items button changed.
2
Cannot add or edit
notes in collection list for patients that have a status marked as
OPEN.
2
Refresh Balances is
caught in a loop within Collection List, due to timer activation
issues.
2
Add functionality
to remove deleted items from history.
2
“qryTempWL:
Error 7200: AQE Error: State=42000; NativeError=2117;[Extended
System][Advantage SQL Engine] Unexpected token: SAN000:” : found
extra tokens after expected end of statement.
2
Access Violation
when adding ticklers.
2
Window does not
open when Medisoft is running in maximized window mode.
2
Giving wrong
message with “Show Deleted Only” isn’t marked.
Communications
Manager
1
Enhanced
HL 7 error log messaging.
1
Corrected
HL 7 enabling and disabling confusion.
1
Tightened
registration requirements for HL 7.
1
Enhanced
security for initial setup limited to level 1 users.
2
Installation is
slow even when .NET Framework is already installed.
2
Needs more user
friendly error messages.
2
Installation wizard
freezes on selecting the installation type - when HL7
application is running.
2
Incorrect window
title.
2
Transfer errors
listed as ‘Unknown Errors’.
2
Errors reading the
configuration file.
2
Disable and Enable
Communications Manager causes the Database Configuration screen to
flash and disappear.
2
Errors transferring
data (chart numbers) with apostrophes and single quotes.
2
Tab order in the InstantDX
connection configuration window reordered.
2
Once the database
is configured user cannot change data path.
Conversion
1
Modified
conversion to properly populate facility on converted
claims.
1
Updated
conversion to create indexes for deposit, obj,
and pax.
2
Allowed Amount
Conversion corrected.
2
Ambulance data
fields did not move to the case from the patient information.
2
Receive message:
‘conversion process did not complete successfully.’, then
Medisoft shuts down.
2
Old task scheduler
data doesn't convert properly to V11.
2
Errors in
converting V9 OH data to V11.
2
Converting V9 or
older data generates an error that PatientResponsible
field already exists.
2
Log reports
“Could not rebuild MWALL index file”.
2
Log reports “all
items Failed” when converting from SP1.
2
Auto backup data
not converting properly.
2
Electronic
Prescribing
2
Login doesn’t
pull up the login screen.
Electronic
Remittance
2
Allow posting of
adjustments based on CAS amounts.
2
Reason code entry
requires an extra ‘;’ at end.
2
ERA module not
creating the Posted folder in the ERA directory.
2
Getting an unknown
file format error when trying to open an EOB file.
2
Added process to
move the ERA files to EOB folder upon file open for use with MREP.
Eligibility
Verification
1
Corrected
initialization error for Eligibility Verification.
1
Modified
connection process to eliminate socket error 10054.
2
Error message reads
“42P”.
2
Update always
applies at startup even when no update is necessary.
Encoder
Pro
1
Resolves
installation difficulty when doing first time installation.
Help
File
1
Enhanced
help file to better explain that only Advance Reports can be
scheduled.
2
Change help ID’s
for backup and restore of root data.
2
Menu web links in
OH, OHPro and Medisoft are broken.
2
Patient Day Sheet
does not show takeback totals though
the help files say it should.
2
Help files appear
to imply that Encoder Pro is a feature instead of a purchased
module.
2
Help not working in
OH Pro File Maintenance.
2
Procedure/Payment/Adjustment
window linked to wrong help topic.
2
Work Administrator
help not functioning.
2
Help for Patient
Day Sheet changed to correctly depict handling of takebacks.
Installation
2
Advantage installed
to non “C:” drive causes an error pertaining to ADSOLEDB.DLL.
2
Copy Medisoft
Client during install does not show a progress bar.
2
Add Tutorials is
copying extra BAK files into the MediData
Tutor directory.
Medical
Connect
2
Loaded under NCDMedisoft
directory instead of Medisoft directory.
2
Error 7057 the key
value not unique error on adding a duplicate provider class.
2
Program file in the
start menu has a capital ‘S’.
2
Account Alert
settings in Program Options, General not clearing out properly.
2
Work areas not
clearing in V11 Single User and Net Pro.
2
Data causes work
areas exceeded error.
2
Cancel after adding
tutorials causes Error 5159.
2
Create new practice
causes error: ‘Could not create the tables.’
2
Small balance write
off window not sized to show all fields.
2
Running audit
report for current day only states that there is nothing to print.
2
Autotask
icon recovered.
2
Hotkey - Tools
menu is missing and contains duplicate hotkeys
2
Hotkey -
File menu is missing hotkeys for “Backup Root
Directory” and “Restore Root Directory”.
2
tlbReceiver:
Error 5147 Constraint Violation while updating column GroupPractice.
2
Add Tutorials is
copying BAK files into the MediData
Tutor directory.
Mediutil
1
Modified
Mediutils to create both local and
remote connections.
Office
Hours
1
Corrected
Provider drop down error in Pro.
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.
Program
Options
1
Removed
Enable Communications Manager check box.
Quick
Ledger
1
Updated
to correct “QueryTransGrid”
error.
1
Corrected
slowness when entering guarantor chart number.
2
Added back into the
system the original Quick Ledger that only had the chart number
and did not have any lookup by Guarantor. Both types are now
available and the practice is now given the option to use either
format. Both contain the new functionality that was added for V11.
2
Date of last
payment and last patient payment date set to 12/30/1899 when
deleting entry.
2
Chart does not auto
populate when Guarantor is searched.
2
Typing fast in the
‘Guarantor’ field drops characters during the lookup.
2
User can only pull
information from the guarantor field but not the chart number
field.
2
Family total
figures are not being populated when the user selects a chart
number.
2
If the account
totals are less than or equal to 0.00 the family totals do not
appear.
2
Closing “Patient
Flag Legend” (color legend) color codes the Guarantor label.
2
Color code is not
consistent between keyboard entry and mouse selection.
2
First patient in
the patient list is displayed in chart label when using keyboard
entry.
2
Payment detail
screen not refreshing the changed chart number values.
2
Previous, next
arrow keys not functional.
2
Inconsistency with
flag colors and account alerts.
2
Re-selecting the
guarantor does not reload the Chart field.
2
F9 to edit
guarantor pulls up patient instead of guarantor for edit.
2
Guarantor Ledger
menu item is shown in original when not available in that product.
2
Guarantor Ledger
clears the previous patient and never gains focus.
Registration
1
Resolved
"Invalid serial number." Issue.
2
“Upgrade
From” field not updating.
Reporting
1
Corrected
totals in Standard Statement.
1
Corrected
totals in Production by Procedure.
1
Added
registration information to bottom of Patient Collection
Letter.
2
The quick reports
say they do not exist when they are set as defaults.
2
Report Designer
cannot open any reports.
2
AuditGen
- running report for today only returns a nothing to print
message.
2
Statement Manager
2
Using F9 (edit key)
will not pull up the highlighted patient selected.
2
Statements of more
than 1 page totaled only the last page.
2
Receiving
“Invalid Stream Format” when trying to print Patient
Statements and Remainder Statements.
2
Transaction Entry:
Entry of a write off
causes the error: “Facility or the diagnosis code changed, if
you continue you will create a new claim”.
2
Credit Card
“Received Settings” screen displayed when creating an item in
the payment section.
2
Changing chart
number causes error: “Access violation at address 0087f42D8 in
module ‘MAPA.EXE’.”.
2
Payment grid order
has changed from previous versions.
2
Payments must be
applied message pops even after all payments have been applied.
2
Work Administrator:
Launch Work Administrator
fro | |