ASCEND-HI -- CURRENT VERSION RELEASE NOTES

Version 2.14.94 (6/05/2008 )

View All Updates

The online help available for the Ascend-HI program is regularly updated to reflect changes in product features.  Please remember to use the help file as a more detailed reference than these release notes. 

Version 2.14.94 (06/05/2008) 

NOTE:  This version of the Ascend-HI program works with the following companion program versions:

AscendHI.DLL - Version 1.2.10 

UpdateHI.EXE - Version 1.1.827 (20080131 <-- This is the last sequential internal update performed by this version)

This version was repackaged 07/01/2008 2:26 PM with UpdateHI Version 1.1.830 (20080209 <-- This is the last sequential internal update performed by this version)

This version was repackaged 07/08/2008 9:36 AM with the latest First Databank files.

This version was repackaged 07/16/2008 2:27 PM with the correct version of the Medication Profile.rpt file (dated 7/16/2008 12:46 PM).

This version was repackaged 08/07/2008 10:28 AM with the latest First Databank files.

Here is a list of new database changes

        Each new update sequence in the UpdateHI.exe program is listed with a brief note about what it accomplishes.  Note that some sequence numbers are skipped.  

• Update20080120 ' Create and index the tables ReportDefaults and ReportDefaultsValues.
  Update20080121 ' Modify the stored SQL for the HCPC Codes report.
  Update20080122 ' Modify the stored SQL for the Fill List and Doses Dispensed reports. Delete NumberOfDaysToIncludeDCRecords default for the Fill List report.
  Update20080123 ' Add Column ReportCriteriaFields to LookupSQL table. Delete/re-add ReportCriteriaFields WHERE FieldTable='Inventory' AND FieldDescription='AHFS Code'.
  Update20080124 ' Add criteria for the ClinicalDocuments report. Add security objects for categories.
  Update20080125 ' Set security for menu items of the Patient Profile screen to secure 'patient access'.
  Update20080126 ' CSRs 1905/1961 -- Fix potential errors caused by Update20071216 and 20071218 (ClinicalDocuments table entries).
  Update20080127 ' Remove an unnecessary SecurityObject table entry.
  Update20080128 ' Add report SQL to SQLSources for Renal High Risk report. Add security object for report into SecurityObjects table.
  Update20080129 ' CSR: 1889 -- Change the report SQL in SQLSources for Patient Overview report.
  Update20080131 ' CSR: 1957 -- Refresh all the SQL Sources for reports.

• After 07/01/2008 2:26 PM Re-package with new UpdateHI.exe program:
  Update20080201 ' Add 5 new FDB tables and added Batch IV report.
  Update20080202 ' Add Lookup records for Payers screen UB-92 Box 4 list of values.
  Update20080203 ' CSR: 1950 -- Change the Lookup records for Payers screen HCFABox17a list of values.
  Update20080204 ' Updated the Order Labels SQL.
  Update20080205 ' Updated the Fill List and MAR WHERE.
  Update20080206 ' Updated the Fill List WHERE.
  Update20080207 ' Add changed RIPTBSC2_BASIC_DESCRIPTOR table.
  Update20080208 ' Add question and answer for Advanced Beneficiary Notice (ABN) form (Additional Information).
  Update20080209 ' Increase Inventory.PhysicalDescription to 80.

Here is a list of new report file changes

This release Includes the newest version of: 

• No new or changed report files.

Here is a list of new features and enhancements

• CSR: 1823 -- Request:  When the Batch Bill screen opens, an error is generated (number: "-2147217887", Description: "Multiple-step operation generated errors. Check each status value." Location: "frmNewClaims - LoadReadyToBill.").  Resolution:  This was caused by the length of a field was too large for a temporary recordset's structure.  The LoadReadyToBill routine was changed for the NewClaims screen of the Ascend-HI.exe program.  Now, the definition of the temporary recordset field (PatientName) that holds a patient's first and last name has been changed to hold up to 37 characters. This will accomodate a LastName of 20 characters, plus a FirstName of 15 characters, plus the comma and space that are inserted between them when populating the field.

Here is a list of things fixed

• CSR: 1972 -- Request:  Incorrect values are printing under the aging columns when running the Accounts Receivable report with the 'A/R Reports Based On:' field under the 'Additional Criteria/Format' tab of the Report screen set to 'Total Allowable'.  The report shows negative numbers when ther Amount Expected value is zero.  
  This is only happening in version 2.14.90.  Resolution:  This is occurring because the total allowable (Claims.AmountExpected field) from the claim is not being properly saved to the database Claim record when the claim is saved.  To cause the Claims.AmountExpected field to properly populate when the claim is saved, modified the 'PrepForIsNullNumber' function (in the Common module of the AscendHI.dll program) to properly return the numeric value if the value is not NULL.  Note that, after applying this update, when a user opens a non-locked existing claim record that incorrectly has a zero in the AmountExpected field, when the user clicks the 'OK' button on the claim screen, the AmountExpected field is repopulated correctly.

• CSR: 1965 -- Request:  The 30-1 report has three known issues:
  1. The Provider Zip Code field is too short, so it cuts off part of the last four digits (after the '-').
  2. The Metric Quantity (pre-decimal) value includes a comma if the value is greater than 999. The requirements state that NO commas should be in this field.
  3. The Metric Quantity (post-decimal) value is padded to 4 zeros (4 characters always print, even if just zeros). The requirements state that this field should only show 3 (three) characters.  Resolution:  The Crystal Reports file (30-1.rpt) for the 30-1 report has been modified as follows:
  1. The Provider Zip Code field is has been lengthened sufficiently to include all of the digits of the zip code, even if it includes the -nnnn (has 10 characters total).
  2. The Metric Quantity (pre-decimal) value now has any commas removed before it is printed.
  3. The Metric Quantity (post-decimal) value is now padded to only 3 zeros (3 characters always print, even if just zeros).

• CSR: 1961 -- Request:  When a client attempts to update from Ascend-HI versions of 2.14.79 or earlier up to versions of 2.14.80 through 2.14.90, if the ClinicalDocuments table in their database has reached ClinicalDocumentRef values greater than 32,767, then an 'Overflow' error occurs. In version 2.14.90, this causes the update to stop. This error occurs when the update program attempts to apply update sequence 20071216. The same error occurs when the update program attempts to apply update sequence 20071218. These sequences each use the Common.FindClinicalDocument function, which only stores values as integers. If the ClinicalDocumentRef of the document found is larger than 32,767, then the error occurs.  Resolution:  Modified the UpdateHI.exe Common routine "FindClinicalDocument" to return a value of the Long type, and internally handle ClinicalDocumentRef values as a type of Long (versus Integer). Changed the variable in Update20071216 to a type of Long to accomodate the results of calls to the FindClinicalDocument function.
  Also modified the following routines to handle database 'ref' values as a Long type to prevent potential future errors:
  Public Function FindClinicalDocument
  Public Sub AddClinicalDocumentQuestion
  Public Sub AddClinicalDocumentAnswer
  Public Sub AddReportDefault

• CSR: 1957 -- Request:  After running the update from Ascend-HI version 2.14.79 to Ascend-HI version 2.14.90, The message "There is no recordsource for the Accounts Receivable report." appears when opening the Reports screen.  This message is also presented when many of the other reports are selected.  It appears as though many of the Select statements for the stored reports SQL were not placed into the SQLSources table.  Resolution:  In some cases, the customer appears to have started with a database that does not have the SQLSources table populated properly to begin with. Since the code in the Update20071202 update sequence of the UpdateHI.exe program expects these tables to be in a specific condition before the update is applied, this is causing a failure to move the reports SQL to new rows of the database as intended. No error is generated, because the functions all work, but there is no SQL retrieved from the earlier rows of the SQLSources table, so the new rows are generated with NULL (empty) SQLSource values.
  A new subroutine ("AddOrUpdateSQLSource") has been added to the Update module of the Ascend-HI UpdateHI.exe program. This routine will properly repopulate the SQL for ALL reports.  Additionally, a single "cleanup" update sequence ("Update20080130") is now included to the UpdateHI.exe program that will remove unnecessary records from SQLSources table.

• CSR: 1905 -- Request:  Following an update to Ascend-HI version 2.14.90, when Adding a new Clinical Document, the 'Add' screen's list shows duplicates (2 entries) for all the standard HOS forms -- the ABN, the DME and the older CMN forms. The forms added by the user are listed only once.  Resolution:  Removed the hard-coded part of the Form.Load routine that adds the name of each CMN, DME and ABN document after the Lookups.ClinicalDocuments code has already been used to retrieve those names from the ClinicalDocuments table.
  While investigating this issue, another error was discovered and corrected. 
  Update20071218 erroneously causes an incorrect document name (‘CMN 484.03’) to be added to the ClinicalDocuments table, and 'fixes' two questions in that document instead of the ‘DME 484.03’ document. To fix the error that is implemented in Update20071218, an update sequence (Update20080126) was added to the UpdateHI.exe program. This update sequence removes the ‘CMN 484.03’ entries from both the ClinicalDocuments and ClinicalDocumentsQA tables. 

• CSR: 1889 -- Request:  For the Patient Overview report, the activated filters are not working properly.  A patient must be assigned to a location (on the Patient Admission Information screen, under the Patient Information tab) in order for that patient's data to be included in the report.  Attempting to use the <all locations> filter option does not include all patients. The Therapy filter is not working, and the date fields are confusing. The report is not pulling the catheter information as expected.  The filters for Patient, Patient Type and Patient status ARE working as expected.  Resolution:  The requirement of a patient to be assigned a location in order to be included in the Patient Overveiw report was resolved by changing the SQL for the report (in update sequence 20080129).
  To cause the 'Therapy' filter to work, changed the code in the Reports form, ReportCriteria subroutine to include the case for ‘Patient Overview’ when checking the condition of the Therapies filter.
  The catheter information is pulled from the Order. In the Order screen, the catheter must be selected. When this is done, then the catheter information appears on the report.
  Regarding the date fields, the report's SQL WHERE clause includes causes any patient who has a therapy with ANY therapy dates that fall into the report range to be included. This operates the way the report is designed.  Note that, while the 'Date Field:' dropdown for this report is active, and there are many selections available, this report's code ignores the value in this field.

• CSR: 1883 -- Request:  When using the Eligibility Verification process for Medicare Part D, Runtime Error 3265 (Item cannot be found in the collection corresponding to the requested name or ordinal.) is presented.  Resolution:  The AscendHI.dll program was modified to eliminate this error. In the NCPDP class, the CreateInsuranceSegment subroutine was attempting to use the Insured1EligibilityClarificationCode from a recordset created by the CreateTransaction subroutine. In the case where a claim is being billed via NCPDP, this field is in the SQL that generates the recordset used. However, when an Eligibility Verification transmission is generated by the program, the Insured1EligibilityClarificationCode is not inlcuded in the recordset (different SQL is used). To correct this issue, the CreateInsuranceSegment subroutine was changed to NOT include the Insured1EligibilityClarificationCode field unless a ClaimRef value greater than zero is available when the Insurance segment is being created. Note that, in the case of Eligibility Verification (an E1 formatted transmission), there is no claim selected, so the C9 field is not created. However, when a selected claim is being billed via NCPDP, the ClaimRef value is greater than zero, so the 309-C9 (Eligibility Clarification Code) field is created and included in the transmission. 

• CSR: 1827 -- Request:  Currently, the Ascend-HI update program (UpdateHI.exe) does not have subroutine-level error handling in the ServerChanges, ImportHCPCSFeeSchedule, ImportHCPCNDCCrosswalk, ImportNDDF and TruncateSQLLog routines.  Need to add local error handling to these routines to assist in troubleshooting when an error occurs during the update process. Also, when an error occurs during the updating of the database structure (in the sequential update routines), the update process needs report the error and stop the update that point(do not proceed to the next update sequence or go any further at all with the update process.  Resolution:  Added local error handling routines in these, and many other subroutines of the UpdateHI.exe program.  Additionally, progress messages are now being posted to the 'Error Log.txt' file (located in the 'Update' folder under the Ascend-HI folder).  This file will now contain line entries that report specific information about the update. This file is no longer overwritten, so the history of updates will now be visible by scanning this log file.  An example of the file contents is shown below. 

  6/5/2008 2:50:14 PM UpdateHI.exe - INFO: Starting Ascend-HI Server Update - Version 06/05/2008 Build: 1.1.827
  6/5/2008 2:50:20 PM Update lblUpdateNow.Click - INFO: Completed copying Update.exe file.
  6/5/2008 2:50:21 PM ServerChanges - INFO: Starting Database updates.
  6/5/2008 2:50:21 PM ServerChanges - INFO: LastUpdated sequence started as: 20080129
  6/5/2008 2:50:21 PM Updates2001 - INFO: Completed Updates2001 update sequences.
  6/5/2008 2:50:21 PM Updates2002 - INFO: Completed Updates2002 update sequences.
  6/5/2008 2:50:21 PM Updates2003 - INFO: Completed Updates2003 update sequences.
  6/5/2008 2:50:21 PM Updates2004 - INFO: Completed Updates2004 update sequences.
  6/5/2008 2:50:21 PM Updates2005 - INFO: Completed Updates2005 update sequences.
  6/5/2008 2:50:21 PM Updates2006 - INFO: Completed Updates2006 update sequences.
  6/5/2008 2:50:21 PM Updates2007 - INFO: Completed Updates2007 update sequences.
  6/5/2008 3:21:16 PM Updates2008 - INFO: Completed Updates2008 update sequences.
  6/5/2008 3:21:16 PM ServerChanges - INFO: Completed all database update sequences.
  6/5/2008 3:21:37 PM Update lblUpdateNow.Click - INFO: Completed updating reports.
  6/5/2008 3:21:37 PM Update lblUpdateNow.Click - INFO: Import HCPC subroutine finished.
  6/5/2008 3:21:37 PM Update lblUpdateNow.Click - INFO: Import HCPCSFeeSchedule subroutine finished.
  6/5/2008 3:21:37 PM Update lblUpdateNow.Click - INFO: Import HCPCNDCCrosswalk subroutine finished.
  6/5/2008 3:21:40 PM Update lblUpdateNow.Click - INFO: Import NDDF subroutine finished.
  6/5/2008 3:21:40 PM Update lblUpdateNow.Click - INFO: Truncate SQL Log subroutine finished.
  6/5/2008 3:21:40 PM Update lblUpdateNow.Click - INFO: SERVER UPDATE COMPLETED.

• CSR: 1822 -- Request:  After admitting a patient, the Admissions/Discharges tab of the Patient Admission Information screen is not listing the new admit.  Resolution:  In the LoadPatient routine of the Patient form, Modified a section at the top of the routine where the code checks for PatientRef=0. If the PatientRef=0, then this is a new admit. However, the Admissions.Item(1).Action was not set with an Admissions.Item(1).Action=”A” to add the Admissions record. This line has been added to the code so that the new admission is recorded now in the PatientAdmissions table as the new patient record is being saved. 

• CSR: 1817 -- Request:  When running the inventory pricing rule for the filter 'DRUG', nothing happens (no records are updated). When the user selects the filter of 'Factor', the system updates all other inventory records, including factor, supplies, solutions, enteral, etc.  It does not update the records with 'drug' type.  Resolution:  Modified the cmbo_Change routine of the InventoryPricingRule screen. Now, when the user selects an inventory type of 'R' (Respiratory) or 'F' (Factor), the code stores the Inventory Type selected into the InventoryPricing table record. 
  Also modified the LoadInventoryPriceRule routine of the InventoryPricingRule to check for the Inventory Types of 'R' (Respiratory) and 'F' (Factor) in the InventoryPricing record as it is loaded. Now, if one of these two inventory types is assigned, when the rule is loaded into the screen, the proper inventory type is populated into the Inventory Type field.
  Now, when the user applies the rule to change the pricing for the selected inventory type, only the inventory records with that type will have thier pricing updated. 

• CSR: 1662 -- Request:  Some facilities use NCPDP format to bill on behalf of other entities, each with a different NPI. Currently, only the NPI from the Facilities screen is what is being sent in the NCPCP transaction.  Resolution:  Changed the logic in the AscendHI.dll program to allow billing for a provider other than the billing facility itself. Now, when the user selects a value of '01' as the Provider ID Qualifier (on the Payer screen under the E-Bill NCPDP tab), the program expects that an NPI is being used for the 201-B1 (Service Provider ID) field. Now, (on the Claim screen under the HCFA tab) if the user selects a 'Pay To Provider', when the Transaction Header of the NCPDP transaction is built, it will contain the Pay-To-Provider's NPI, or if empty, the Provider ID (from the Payers screen under the E-Bill NCPDP tab), of if empty, the Facility NPI (from the Facility screen under the General tab), or if empty, the Facility NABP (from the Facility screen under the General tab). 

• CSR: 851 -- Request:  The option to have orders automatically discontinued after a preset number of days past the order stop date is not working.  Resolution:  In the Ascend-HI.exe program, Changed the Duty subroutine of the Profile form to properly filter the order records that need to be auto-discontinued. In the same subroutine, also changed the call to Order.Discontinue to have the correct number of parameters. Hard coded the UserRef in the parameters to zero, so when an order is automatically discontinued using this process, the log of changes will show no user name associated with these changes. 

First Databank Updates

• AWP/WAC Pricing Update - 07/31/2008
• Patient Education Monographs (English) - 07/31/2008
• Patient Education Monographs (Spanish) - 07/31/2008
• Drug-Drug Interactions - 07/31/2008
• Drug-Disease Contraindications - 07/31/2008
• Drug-Food Interactions - 07/31/2008
• Duplicate Therapy Checking - 07/31/2008
• Geriatric Precautions - 07/31/2008
• Lactation Precautions - 07/31/2008
• Min/Max Adult Daily Dose - 07/31/2008
• Pediatric Precautions - 07/31/2008
• Pregnancy Precautions - 07/31/2008

To determine the date of the First Databank files currently installed into your database, follow the steps of:

1. Click on the HELP option of the main menu of the Ascend-HI screen.  From the pull-down menu that appears, Select the 'About Ascend-HI' option to activate the ABOUT screen.
2. On the upper right-hand side of the ABOUT screen, the date is displayed as:  First Databank Current as of 07/31/2008

NOTE:  If a more current version of the First Databank files has been received by Hann's On Software since this release, you can go to the Hann's On Software website and perform a First Databank update that updates your Ascend-HI to the most current First Databank files.

HCPC Codes

• HCPC Codes - 11/01/2007