ASCEND-HI -- VERSION RELEASE NOTES

Version 2.14.43 (05/25/2007 )

View All Updates

NOTE:  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. 

NOTE:  Each customer service request (CSR) addressed by this update is listed separately below along with its resolution information. 

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

AscendHI.DLL - Version 1.1.1369

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

Here is a list of new features and enhancements

• CSR: 935 -- Request:  On the new HCFA-1500 (v1.3)/(CMS1500) form, column 24E, Diagnosis Pointer, is wider in the template used by Ascend-HI than it is on the pre-printed forms, so the diagnosis pointer value is printing outside the diagnosis pointer column on pre-printed forms. Also, some clients have requested the ability to print up to 5 digits in column 24G (Days or Units column).  Resolution:  The Crystal Reports file for the HCFA-1500 (v1.3) has been modified. The width of column 24D has been widened, and the corresponding 'sub-boxes' within column 24D have also been widened to accommodate the new alignment of the box. This causes column 24E to be narrower, and start further to the right side of the page, thus better aligning it with pre-printed forms. Column 24E now also has its text right-justified. The alignment of the text in column 24G has been adjusted to the left. This causes the first digit of the value displayed in column 24G to start just the right of the box's left margin. While the specification says that only 3 characters are permitted in box 24G, the version printed by the Ascend program will allow up to 4 characters (using a Courier New (Western) size 10 Bold font).

• CSR: 860 -- Request:  Wherever a non-NPI identifier is printed on the new HCFA1500 form, an ID qualifier is supposed to be printed also. The fields affected are 17a, 19 (if used), 24-I, 32b and 33b.  Resolution:  Changes were made to the Crystal Reports file for the HCFA-1500 (v1.3) report. 
  
  Regarding Box 17a, the menu dropdown for Box 17a on the Payers screen (under the HCFA-1500/UB92 tab) has been reduced to only offering the options that have known qualifiers and are available from the database. These include:
  UPIN (qualifier 1G)
  Medicaid Number (qualifier 1D)
  State ID (qualifier 0B) 
  Now, when the user selects the type of ID being placed into Box 17a, the matching qualifier is placed in the box just to the left of the ID itself.
  
  Regarding Box 19, the value is drawn from the individual Claim screen in the field labeled 'Reserved for local use:', which is a 65-character field into which the user can enter any text. However, to be compatible with the new HCFA-1500 specifications, if the user places an entity (doctor, facility, etc.) in this field, the user must also prefix the appropriate qualifier before any the identifier text (with NO SPACED between the qualifier characters and the identifier text). According to the specifications, more than one identifier can be placed into Box 19, and there is not a specific restriction to entity identifiers being used in this box.
  
  Regarding Boxes 24i and 24j, please refer to the solution provided in related CSR: 522.
  
  Regarding Boxes 32b and 33b, there is a new set of text boxes available now on the Payers screen, one for each of these boxes. Since these values rarely change for a single payer, the user can now directly enter up to 20 characters that will be used to populate the box. It is important to note that when the user enters this text, they must first prefix the text with the appropriate qualifier according to the HCFA-1500 specifications. A note to this effect has been added as tool tip text for each of these boxes.

• CSR: 886 -- Request:  The Payers screen currently has the single 'Electronic Billing' tab that contains the NCPDP, X12 and NSF settings for the payer. Since it is anticipated that many more possible settings could be required for each of these formats, the settings for each needs to be moved to its own tab to allow more screen real estate for each format's settings.  Resolution:  The Payers screen has been modified. The single 'Electronic Billing' tab that contains the NCPDP, X12 and NSF settings for the payer has been removed, and the settings for each electronic billing format has been moved to its own tab.

• CSR: 856 -- Request:  The DME 10.03 form has quantity fields that are not required.  Resolution:  Changed the form to not display the unnecessary quantity fields.

• CSR: 826 -- Request: Need To Add RDOSED2_DOSE_DESC table from First Databank. Resolution:  This table is now added to the First Databank and Standard Full Update packages.

• CSR: 812 -- Request:  Currently, the "Doctor" drop-down field in the Claim screen is used as the Referring doctor in the printed HCFA-1500 and  HCFA 1500 (v1.3) (CMS 1500)  forms.  It needs to be more obvious to the user that this drop-down field is used as the source for the Referring Doctor information in used boxes 17 and 17a on the older HCFA 1500 form and boxes 17, 17a and 17b for the newest HCFA-1500 (v1.3)  form (CMS 1500). Resolution:  Modified the Claim form to re-label the pull-down menu object from 'Doctor:' to 'Referring Doctor:'.  Additionally, added ToolTip text to the pull-down menu object that states: 'This Referring Doctor field is used to populate boxes 17, 17a & 17b of the CMS 1500 (v1.3) form, as well as boxes 17 and 17a of the older HCFA form.'  (this occurs when the mouse hovers over the object on the screen).

• CSR: 807 -- Request:  Need the ability to send NPI numbers in X12 batch files.  Resolution:  In order to allow users to select which ID type is sent in the NM109 field for each of the X12 transmission loops (2010AA 2310A 2310B 2420A-F), added lookup tables to the database (PayerDefaults, PayerDefaultTypes, PayerDefaultTypeLookups) along with associated selection dropdown menus on the Payers screen.  Also added the 'NPICompatible' flag in the ElectronicReceivers table and Electronic Receivers screen. 
  For each X12 loop, the user can select (at the Payer level) from a list of ID types (i.e., NPI, EIN) that will be used.  Based on the which ID type is being sent, the program now automatically sets the proper Qualifier (NM108 field) that will be used with the ID.  
  In the update that populates the initial lookup tables, the ID type is set with a blank for all of the X12 fields for all of the Payers.  When a setting for a field is left blank, the Federal Tax ID is sent for the provider unless the NPICompatible box is checked in the Electronic Receivers screen, in which case the NPI for the provider is sent instead. Whenever a specific value is set in the Payers screen (E-Bill X12 tab), the ID associated with that selection is sent (regardless of the settings in the Electronic Receivers screen).
  When a payer notifies the user that the NPI values are now being accepted by that payer, the user can then edit that payer's record to select the correct NPI value to send in the appropriate loops for that payer.  
  NOTE: The additional screen input fields required that the electronic billing settings be reorganized under new tabs ('E-Bill NCPDP', 'E-Bill X12' and 'E-Bill NSF') in the Payers screen. These settings were previously all included in the single 'Electronic Billing' tab.

• CSR: 794 -- Request:  Prevent Blank SIG Codes from being added. Resolution:  Modified the program to not allow a blank SIG code to be added to the SIG codes list.
• CSR: 790 -- Request:  Set patient status to Discharged when patient is discharged.  Resolution:  Previously, when the a patient was discharged, the status could still be Active.  Now when the patient is discharged, the AscendHI.dll program will now scan for a status of Discharged and, if found, set the status to Discharged.
• CSR: 789 -- Request:  Need to import the Route during the Inventory Synchronization process.  Resolution:  Modified the AscendHI.dll code to import the Route during an Inventory Synchronize operation. See related CSR: 830.
• CSR: 788 -- Request: Add RROUTED3_ROUTE_DESC table for Routes from First Databank.  Resolution:  Added RROUTED3_ROUTE_DESC table for Routes from First Databank.
• CSR: 787 -- Request:  Delete Description field from the Routes table.  Resolution:  The UpdateHI.exe program has been modified to delete the Description field to the Routes table.
• CSR: 786 -- Request:  Add RouteCode to the Routes table.  Resolution:  The UpdateHI.exe program has been modified to add the RouteCode field to the Routes table.
• CSR: 771 -- Request:  The user should be able to have a SIG code NOT interpreted (expanded) when entered into an order field.  Resolution:  The user can now cause a SIG code to remain uninterpreted by surrounding the text with parentheses. For example, "BID" will find a matching SIG code and be expanded automatically, but "(BID)" will be left alone (not expanded). 
• CSR: 768 -- Request:  Create Physician Orders field in the Inventory table.  Resolution:  The UpdateHI.exe program has been modified to add the PhysicianOrders field to the Inventory table. 
• CSR: 767 -- Request:  Create MARPainEffectiveness and MARDoseText to the Inventory table.  Resolution:  The UpdateHI.exe program has been modified to now add the MARPainEffectiveness and MARDoseText fields to the Inventory table. 
• CSR: 762 -- Request:  Add PriorityRef Field to Sig Codes table.  Resolution: Update sequence # 20061005 has been added to the UpdateHI.exe program to add the PriorityRef column to the SigCodes table.  
• CSR: 697 -- Request:  The product allows different items with duplicate charge codes to be added to the inventory. When logged in as a multi-facility user, changing an inventory item that has the same charge code as others causes a message to appear. 'Would you like to apply this add/edit to multiple facilities?" Answering YES to this message allows the user to select from a list which facilities will have the items with the same charge code updated along with the change. When the user selects all of the facilities for update, all items with the same charge code are updated. This process allows the user to unknowingly incorrectly change items in inventory.  The system should not allow the user to proceed with the addition until the charge code is corrected to a unique code. A “Uniqueness” check should included for charge codes.  Resolution:  It is not an error that the (multi-facility) user can perform this operation. In fact, using the same charge code for multiple items in inventory is a common beneficial practice. This 'batch update' based on charge code feature is intended to allow simpler updating of inventory where the same item exists in multiple facilities, and a batch update of all like items is desired. The user can answer NO to the message that asks about applying the edit to multiple facilities. This will prevent the batch update from occurring. A new warning message has been added to alert the user that the charge code is duplicated in other records (listing the records with a duplicate value). Also, the popup message that asks the user about applying the change to multiple facilities has been made more specific, informing the user of the consequence of answering YES to the question. 
• CSR: 690 -- Request:  Need to create PARLevel in the SigCodes table.  Resolution:  PARLevel column has been added to the SigCodes table. 
• CSR: 647 -- Request:  Need a field to store the default par level for inventory records that can be used to set the par level during order entry.  Resolution:  The UpdateHI.exe program now creates a field to store the default par level in the inventory table records.
• CSR: 646 -- Request:  Need to create a field to store the default fill method for inventory records that can be used to set the fill method during order entry.  Resolution:  The UpdateHI.exe program now creates a field to store the default fill method in the inventory table records.
• CSR: 645 -- Request:  Need to create a field to store the default order type for inventory records that can be used to set the order type during order entry.  Resolution:  The UpdateHI.exe program now creates a field to store the default order type in the order table records.
• CSR: 632 -- Request:  Compile new Crystal Reports custom DLL with the file name of CRUFLNET.DLL. Keep the existing CRUFLAHI.DLL file. Resolution:  Recompiled the Crystal Reports custom DLL with the file name of CRUFLNET.DLL. Kept the existing CRUFLAHI.DLL file.  Added code to the UpdateHI.EXE program (in the frmWorkstationUpdate module) that causes this driver to be registered when the Update is run.  This new DLL file will be included in this and future update packages.
• CSR: 630 -- Request:  Add the ability to create a rs.ttx file from the SQL shown on reports screen (in the SQL tab). This will allow the user to easily type or paste SQL into the box and then create a TTX file to use when developing new reports.  Resolution:  Added a button to the SQL tab of the Reports screen that allows the user to automatically create a rs.ttx file from the SQL contained in the text box on the same tab of the screen.
• CSR: 620 -- Request:  When a user is already logged into the Ascend-HI program, and then clicks on the 'lock' icon to log off, the Password screen appears.  If the user clicks on the 'x' button (top right corner of screen) to close the screen, the screen closes, but the Ascend-HI program continues to run.  The same is true if the user clicks the upper left corner of the Password screen and then selects the 'Close' option to close the window.  If the user attempts to log back in (clicks the lock icon), an Error 91 message appears. Some users want to use this method to allow minimizing of the Ascend-HI program screen after logging out to secure the program.  Resolution:  A change was made to the code to cause the 'x' button to act like the cancel button. Now, when the user clicks the 'x' button, the entire application closes. Additionally, a minimize button is now included in the title bar, so the user can click that button and it will cause the entire application to minimize. NOTE: When the application is restored on the screen after this, the Password screen will still be minimized within the application's screen. 
  One other way to minimize the Ascend-HI program window after a log off occurs is to simply simultaneously click on the 'START' (Windows icon) key and the 'D' key of the terminal keyboard. This will immediately put the user at their desktop (with the Ascend-HI program minimized). When the user re-accesses the program, the Password screen will still be visible.
• CSR: 613 -- Request: Client needs 10 characters in the Zip code field (nnnnn-nnnn) in the Providers screen to accommodate a full 9-number Zip code since the Post Office states there must be a dash or space between the 5/4 numbers.  Resolution: The Ascend-HI.exe program was modified.  The Zip code text box on the Providers screen now accommodates 10 characters (nnnnn-nnnn) instead of 9. Also increased the Zip field size to 10 in the Suppliers ('Providers') table.
• CSR: 590 -- Request:  Program does not populate the 32B and 33B boxes of the HCFA 1500 (v1.3) form. Resolution: Code has been added to the program that allows the user to hand-enter data on the Payer screen (under the HCFA-1500/UB92 tab) for each of these boxes.  NOTE:  The user must remember to prefix the non-NPI ID with the appropriate qualifier code (with no spaces between the qualifier and the ID).

• CSR: 546 -- Request:  This is essentially a duplicate of CSR: 460.  Resolution:  See resolution for CSR: 460 below.

• CSR: 541 -- Request:  Add additional inpatient order type categories for Ascend (.NET) functionality.  Resolution:  The additional inpatient order types were added.
• CSR: 529 -- Request:  Remove SQL from reports source code and add source code statements to retrieve SQL for each report from the database (see related CSR: 514).  Resolution:   The ReportRecordSource subroutine was changed to retrieve the report SQL from the database for all but one of the reports ... they now use a routine to retrieve the report's core SQL from the database (Note that this does not include the 'WHERE' clause). NOTE: The Patient Account Statement report was not modified under this CSR, but instead is tracked separately in CSR: 576.
• CSR: 528 -- Request:  Modify Server Update Logic To Work With Vista Operating System.  Resolution:  Modified the server update logic to work with Vista. The ConnectionString value was not able to be read from the ADO connection so the code was changed to read it from the workstation settings. This change was necessary for checking if a table exists or if a field exists.

• CSR: 522 -- Request:  The new HCFA-1500(v1.3) form does not properly populate boxes 24i and 24j (NPI and non-NPI IDs and their qualifiers).  Also, there is no user choice as to the entity to identify in these boxes, nor which type of non-NPI ID to send.  Resolution:  Made changes to the HCFA-1500 (v1.3) Crystal Reports file and code changes in the Ascend-HI and DLL programs to allow the user to select which entity is identified in Box24j.  The NPI (if available) for that entity is placed into the white area at the bottom half of the box.  The non-NPI ID (if used) of that entity is placed in the gray area at the top half of the box.  If a non-NPI ID is used, its qualifier is placed into the 24i box just to the left of the non-NPI ID.
  
  On the Payers screen (under the HCFA1500/UB92 tab) the user selections for which entity is identified in Box24j include:
  - None (Do not populate Box 24j)
  - Ordering Dr. (from the order)
  - Referring Dr. (from the claim)
  - Facility (from the facility to which the patient is assigned)
      
  If a doctor is selected as the entity to identify in Box 24j, then the following non-NPI ID types are available on the Payers screen:
  - None (No qualifier is printed into Box 24i and no ID is placed into Box 24j)
  - Federal Tax Id (qualifier EI)
  - State Id (qualifier 0B)
  - Medicaid Number (qualifier 1D)
  - Upin (qualifier 1G)
  
  If the facility is selected as the entity to identify in Box 24j, then the following non-NPI ID types are available on the Payers screen:
  - None (No qualifier is printed into Box 24i and no ID is placed into Box 24j)
  - Federal Tax Id (qualifier EI)
  - State License (qualifier 0B)
  - Facility ID (qualifier G2)

• CSR: 514 -- Request:  For compatibility with Ascend (.NET), the SQL for the Ascend-HI reports needs to be added into the new SQL storage tables (SQLSources, SQLSourceTypes and SQLSourceLinks). This will also make it possible for report SQL to be modified without re-compiling the Ascend-HI executable program.  Resolution:   The UpdateHI.exe program now adds the SQL for each of the reports to the SQL tables of the Ascend-HI database.  See related CSR: 529.
• CSR: 513 -- Request: When calculating the creatinine clearance (ClCr) for a patient, the program should include all three variations of Cockroft-Gault equations.  The “standard” Cockroft-Gault equation used in Ascend-HI is based on ideal body weight among other data. However, the equation should also include the two additional variations in the Cockroft-Gault equations (to handle unusually high and low weights).  Resolution: Equations to handle unusually high and low weights have been added to the Ascend-HI creatinine clearance calculations.
• CSR: 460 -- Request:  The new DME forms (09.03, 10.03, 484.03) are not printing the NPI for the physician and supplier.  Also, a portion of the text 'SUPPLIER NAME' is printing slightly over the revision date.  Resolution:  The Crystal Reports files for the new DME forms have been modified (along with changes to the program) so that the NPI is now able to be printed for the physician and supplier.  The 'SUPPLIER NAME' text block has been moved down slightly to prevent it from printing over the revision date.

Here is a list of things fixed

• CSR: NONE -- Request:  When Adding an inventory item, and using the 'Search' function to select an item, if the NDC code for the item is 00677-1699-10, then the returned Strength and 'Per' values are incorrect (there should be no 'Per' value returned, just Strength).  Resolution:  The Inventory class in the AscendHI.dll program has been corrected to not return the 'Per' value.

• CSR: 932 -- Request:  The 'Other' tab on the Claim screen is now blank. The data entry field objects no longer appear when the tab is selected.  Resolution:  During an edit of the Claim screen, the frame that contains the missing controls was accidentally left 'behind' the screen's tab control. This caused the controls in that frame to be hidden by the tab control when the 'Other' tab was clicked. The frame has been placed 'in front of' the screen's tab control, so now the field controls appear when the 'Other' tab is clicked.

•  CSR: 924 -- Request:  In the Options screen, under the Printing tab, when the user selects the TPN label to view options for that label, the final check box in that options list is labeled simply "Include".  The final check box should be labeled "Include item volume".  Resolution:  The LoadOptions subroutine has been corrected to place the complete text 'Include item volume' onto the screen next to the last checkbox of the TPN Label settings under the Printing tab of the Options form.

• CSR: 898 -- Request:  In some cases, after a SIG code is entered into the Doctor Instructions or Patient Instructions field of an order, when the user exits the field on the screen, it can take several minutes before the program is once again responsive.  Resolution:  The code that automatically schedules doses according the interpretation of the SIG code has been 'commented out'. This code is currently only used for the Ascend (.NET) product.

•  CSR: 893 -- Request:  When performing an Ascend-HI update, if the Ascend-HI.INI file has a server path name that does not end with a backslash, the update generates errors related to not being able to access the path. This occurs when a user has the Server Path as a hidden shared network directory (i.e., "Path=\\Some Server Name\Ascend-HI$").  Resolution:  The UpdateHI.exe program has been modified to test whether the Ascend-HI.INI file's Server Path parameter has a backslash at the end of the pathname. If it does not, the INI file entry is left as is, but the variable to which it is assigned in the UpdateHI.exe program has the backslash suffixed so that the program can properly locate and access the hidden shared directory.

• CSR: 849 -- Request:  When a user chooses to Un-Discontinue an order, the inventory counts for the items in that order are being decremented. The inventory counts should be left alone in this case, since the items in the DC'd order are assumed to have been dispensed, and were already decremented in the inventory counts when the order was first made active. Also, when an order is Discontinued from within the Order screen, the inventory items are returned to inventory. This is NOT the case when an order is discontinued by right-clicking the order in the orders list of the profile screen, and then selecting the 'Discontinue (F6)' option in the dropdown menu. The correct action is to leave the inventory item quantities alone. Resolution:  Changed the code in the AscendHI.dll program to detect a change of state in an order from Discontinued to Active. When this case is detected, the inventory counts are left alone. Also changed the code to NOT return items to inventory quantities when an order is Discontinued from within the Order screen. 
• CSR: 843 -- Request:  When a user edits the Referral Description in the Referrals screen (Utilities->Referrals menu), and then clicks the 'Save' button, the changed description is not saved.  Resolution:  Changed the AscendHI.dll program to properly save the changes made to the Referral Description when the user clicks the 'Save' button.
• CSR: 830 -- Request:  When saving an Inventory record that has invalid characters in the HCPC field, an error appears. The error states: Unclosed quotation mark after the character string ''.  The reporting module-function is Common-ExecuteSQL.  Resolution:  In this case, there were invalid characters present in the HCPC value for the inventory item. When the save routine attempted to save the invalid characters to the database, the error occurred.  Modified the Common module's PrepSQLString function in the AscendHI.DLL to test for invalid characters in a string before returning the string to the calling routine. The PrepSQLString function is called by the ExecuteSQL function whenever a string must be prepared for insertion into a database field. In this case, the inventory record was being saved, and when the ExecuteSQL function attempted to save the invalid characters into the HCPC field of the database table, the error occurred.  See related CSR: 789.
• CSR: 796 -- Request:  When an e-bill is generated with a DME 09.03 form 'attached', the stored answers to questions 1-4 are not being parsed properly, and therefore incorrect information is being placed into the e-billing file. Resolution:  The AscendHI.dll code was changed to properly parse the DME 09.03 data for placement into the e-billing file.
• CSR: 792 -- Request:  The FacilityRef field must be added to the Routes table.  Resolution:  The UpdateHI.exe program has been modified to add the FacilityRef field to the Routes table. 
• CSR: 785 -- Request:  When a user enters a time into an order's schedule, an error occurs if the user incorrectly enters a time with a space character included. Additionally, if the format of the time is 'HH:m' (where the last character of the minutes is left off), the program stores the time that way.  Resolution:  The error-checking routine (lost_focus) for the time entry fields of the Order form's Schedule tab has been enhanced to prevent the user from incorrectly entering a time. 
• CSR: 783 -- Request: When canceling a refilled order, the program asks whether the user wants to re-activate the last refill.  If the user clicks YES, the program does not cancel the refilled order, nor does it re-activate the last refill.  Resolution:  The SaveOrder routine of the Order form was modified to save the Cancelled refill record, preserving its new Cancelled status. Then the routine Un-discontinues the most recently discontinued order that has the same RX number. This would be the original order, or the most recent refill of the same order. 
• CSR: 781 -- Request:  When using SIG codes in new orders, editing of orders, refills and adding common orders, the system presents
  an error message (Error 380 - "Invalid Property Value").  The user can click 'OK' on the error screen, and the system will then populate instructions with the related SIG code description.  This only occurs if the selected SIG code has a time entry in the schedule fields of the setup screen for the SIG code.  Resolution:  Fixed the program to properly handle the case where schedule times are entered into the SIG code setup. The program now properly uses the schedule times from SIG code setup and posts them to the order's schedule (seen under the Schedule tab of the Order screen).
• CSR: 780 -- Request:  The DME 484.03 form has incorrect wording for question 2 in Section B.  Resolution:  In the Crystal Reports file, the wording for question 2 in Section B of the DME 484.03 form has been corrected to read: "2. Was the test in Question 1 performed (1) with the patient in a chronic stable state as an outpatient, (2) within two days prior to discharge from an inpatient facility to home, or (3) under other circumstances?"  The DME 09.03 screen form's wording has also been corrected. 
• CSR: 714 -- Request:  The old address of Hann's On Software is being displayed on the Help->About Ascend-HI screen in the 'For Information Contact' frame.  Resolution: Changed the form text to now display the correct (new) address. 
• CSR: 704 -- Request:  There are unnecessary entries in the OrderChanges table due to an error in the order change logging code. These need to be cleaned out of the table. Resolution:  Modified the UpdateHI.exe program to remove the records where the only difference is the format of the date stored in a field. This cleanup is a one-time occurrence.
• CSR: 703 -- Request:  When changing the status from Active to Discontinued or Discontinued back to Active, the AscendHI.DLL is not logging the OrderRef number in the OrderChanges table.  Resolution:  Changed AscendHI.DLL code to insure that the OrderRef value is always saved in OrderChanges table entries. 
• CSR: 691 -- Request: When an internally-handled error message is generated by the Ascend-HI application, the version of the running application should be displayed in the error window for ease of troubleshooting. This way, when a user captures a screen shot of the error, the Hann's On Software support team will know immediately which version of the product is encountering the issue.  Resolution:  The RecordError function in the Common module of the software was modified to always display the product and version in the title bar of the error message window. 
• CSR: 673 -- Request:  The Fill Stop Date is displaying in the Fill Start Date column on the Confirm tab in the Verify orders screen.  Resolution:  Code change has been made to the VerifyOrders form in the Ascend-HI project.
• CSR: 639 -- Request: When working in a common order, an Error 5 occurs when the user presses the Enter key while the cursor is on a blank line in the comments text box.  Resolution:  The common order has its 'Therapies' dropdown control disabled. A special routine handles the case in the comments text box when the user presses the Enter key while the cursor is on a blank line. This routine was attempting to force the focus to the Therapies dropdown control, but since this control was disabled, an Error 5 occurs. This special routine no longer attempts to force the focus to the Therapies dropdown control. Instead, it now 'tabs' to the next available control. 
• CSR: 609 -- Request:  Previously in the Security screen, if a Technician's option setting for 'Orders need to be Verified' and 'New orders will be inactive' were checked, the Tech was still able to refill orders, and those 'refill' orders would be created with an ACTIVE status.  Now any orders refilled by a technician (with these security options set) are created with a status of INACTIVE.  The program needs to create all refills with an ACTIVE status when created, even by a technician.  Resolution:  The refill action has been changed back to forcing the status of the new refill order to be 'Active'. 

• CSR: 591 -- Request:  Discovered that a change made for CSR: 529 on 3/1/2007 (released INTERNALLY with Ascend-HI version 2.14.25 and released to BETA in versions 2.14.31 and 2.14.35) forced the report SQL to upper case for some reports, thereby causing the facility filter-type determination algorithm to fail to match on any table name.  This 'un-fixed' the solution previously applied under this CSR (591).  Resolution:  This was corrected by forcing both comparison values to upper case prior to the comparison. See related CSR: 444.

• CSR: 540 -- Request:  When an 'On Hold' order is released from Hold and changed to Active, the release is not being flagged in Pyxis.  Resolution:  Corrected this so that now, when an order is released from 'Hold' status, the event information is being passed to the Pyxis system.

• CSR: 532 -- Request:  Inventory and Lot quantity on hand (QOH) values are not being correctly updated when an order changes status.  Resolution:  See resolution for related CSR: 319. 

• CSR: 444 -- Request:   Many reports (in particular, the On Call Patient List report) are no longer properly filtering by facility.  Resolution:  Discovered that a change made for CSR: 529 on 3/1/2007 (released INTERNALLY with Ascend-HI version 2.14.25 and released to BETA in versions 2.14.31 and 2.14.35) forced the report SQL to upper case for some reports, thereby causing the facility filter-type determination algorithm to fail to match on any table name. This was corrected by forcing both comparison values to upper case prior to the comparison.  See related CSR: 591.

• CSR: 375 -- Request:  When making a change to date fields in an order, the changes are not being recorded as changes in the Order Log (OrderChanges table) for the order.  Resolution:  Modified LogChanges routine in the Order class object to properly distinguish the same date in different forms when comparing order records and determining whether a change should be logged. 

• CSR: 319 -- Request:  Inventory and Lot quantity on hand (QOH) values are not being correctly updated when an order changes status.  Resolution:
  A change was made to the AscendHI.DLL that addresses this issue. Now a matrix of inventory quantity actions determines whether the inventory and Lot QOH values are incremented or decremented, depending on the initial and final status of the order when edited. The new algorithm uses the following Logic:
  Each order status has one of two possible inventory actions associated with it (Decrement inventory and Increment inventory).
  1. If an order status changes from a decrementing to a non-decrementing status, Items in the order are returned to inventory.
  2. If an order status changes from a non-decrementing to a decrementing status, Items in the order are removed from inventory.
  3. If an order status starts and remains in a decrementing status, Items in the order are returned to inventory (based on the pre-edited values stored in the database for the order), and then removed again from inventory (based on the changed order's data).
  4. If an order status starts and remains in a non-decrementing status, the inventory item quantities are NOT changed.
  5. If an order is Replaced, the replaced items have their inventory quantities decremented.
  The statuses below show whether they are 'Decrementing' or 'Incrementing' states.

  Active	D
  Inactive	D
  Hold	I
  Pending	I
  Cancelled	I
  Replaced (auto-created by ‘Replacing’ an existing order)	D
  Discontinued	I

  This CSR is essentially duplicated in related CSR:532. 
  
  

First Databank Updates

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

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 right-hand side of the ABOUT screen, the date is displayed as:  First Databank Current as of 04/26/2007

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 - 01/15/2007