| Product Area |
CSR/Ticket/SCR |
Description |
Solution |
|
C:CSR T:Ticket S:SCR |
ENHANCEMENTS |
The following items are enhancements to the product |
| Billing |
C 3622 |
Cancelling a claim during the batch billing process (under the Ready To Bill tab of the New Claims screen) should not cancel the whole process. Instead, allow the user the ability to continue with the next order in line to be billed. |
When the user selects multiple patients and/or orders to be billed in a batch, if the user cancels one of the claims during the process, Ascend prompts the user with a message "There are more orders left to bill. Would you like to continue billing the remaining orders. Select No to cancel batch billing process?"When the user selects Yes, Ascend immediately presents the next order in a Claim screen. If the user selects NO, the entire batch billing process is cancelled. |
| Billing |
C 3989 |
The processing time to bill a TPN order is excessive. It is taking 5 or more minutes to bill TPN orders of a single patient when in the batch billing mode. |
The code behind the billing process was changed to significantly improve performance when performing batch billing where a TPN order is involved.Now, when a TPN Order with 8 ingredients is being batch billed (in the New Claims screen, under the Ready To Bill tab), it takes only 2 seconds for the claim screen to pop-up after clicking the Bill button. |
| Billing |
C 3996 |
Add the ability to bill by percentage of WAC.
The Wholesale Acquisition Cost (WAC) field appears for an inventory item near the bottom of the screen under the Price History tab in the Inventory screen.
Add "% of WAC" as an option in the "Price Structure" drop down controls in the Pricing Rule screen that is accessed via the Pricing Template screen. |
The option "% of WAC" has been added to the "Price Structure" drop down controls in the Pricing Rule screen. The user can now use the WAC pricing as the basis of the percentage calculation.
When the user adds or edits a Pricing Rule (by double-clicking the Pricing Rule listed on the Pricing Contracts screen), "% of WAC" appears as an option under the dropdown labeled "Price Structure" under the heading "Bill" and also under the heading "Allowable".
NOTE: This feature has NOT been added to the "Inventory Pricing Rules" screen (accessed by following the "Utilities->Inventory->Inventory Pricing" menu path from the Profile screen, and then editing an item listed in the "Inventory Pricing" screen). |
| Billing |
C 4009 |
After an order has been billed, if the user changes the Order from Billed=Y to Billed N, and then rebills the order to create a new claim, the item quantity in the new claim is a zero or negative value. |
This is the result of a change made to the way Ascend handles an order’s cancelled claims when calculating the item quantity in the new claim (when the same order is rebilled). Now …
If the user does not first cancel the original claim associated with the order before rebilling, the system will consider the order quantity billed, and will subtract that quantity upon rebilling of the order. This causes the claim to indicate a zero or negative quantity.
The user must first cancel the claim associated with the order, and then change the billed status of the order from Y to N. After these steps are accomplished, when the user rebills the order, the correct quantity is used in the new claim.
NOTE: The billing process in the Ascend-HI product does not take into account anything already billed for an order when that order is rebilled. Customers converting from Ascend-HI to Ascend should take note of this difference between the two products in this respect.
|
| Clinical |
C 3980 |
Make changes to the Synagis Tracking form and data views to meet the MedImmune 2010 specifications. |
Changes have been made to the Synagis form and its related data views per the MedImmune 2010 specifications. Now, the Synagis form has 24 questions, with the changes to the multiple-choice answers of questions 4, 5 and 9 as defined in the MedImmune requirements. |
| Doctors |
C 4011 |
The Facility ID number (Contract number) should appear with the facility name in any drop-down list where the user selects the Facility ID.
Example: When adding Doctors to Ascend while in All Facilities mode, the user must add the doctor, save the added record, then reopen to attach to a facility. At this time, since the Facility ID number is not displaying, and several sites can have the same name, the user must count down the names in the list to know which one to use when attaching the doctor record. It would be easier (and more exact) to have the Facility ID number display in front of the name so the user will know which facility to select.
|
All dropdown controls in Ascend that select the facility now have the Facility ID also displayed in front of the facility name. |
| Inventory |
C 3987 |
Add an additional filter of "All Facilities - All Unique Items" to the items listed in the “Facility” filter dropdown (under the General tab of the Inventory screen). |
The "All Facilities - All Unique Items" filter was added to the items listed in the “Facility” filter dropdown (under the General tab of the Inventory screen). When this filter option is selected, the user will only see one item listed in the Inventory window (rather than multiples of the same item) when that item is linked to multiple facilities. |
| Inventory |
C 3990 |
Add a facility assignment identifier that is visible from the General Tab of the Inventory screen.
Identify the facility to which the inventory item is linked. This will help avoid errors when adding, editing or deleting items in the inventory.
|
The facility to which the inventory item is assigned is now displayed at the bottom of the Inventory screen. |
| Inventory |
C 3995 |
Inventory items with the Inventory Type of Nursing are not listed in the Order Item selection screen. |
Modified the Inventory Item selection screen to include in the list those inventory items with an Inventory Type of Nursing. |
| Inventory |
C 4006 |
Inventory search with “All Facilities - All Unique Items” filter selected only displays and searches based on Description 1. Include the ability to search for Description 2 of an inventory item, and display the item in the list under its Description 2 value.
When logged into All Facilities, the user can search by "Description" with the “All Unique Items” filter selected. When the filtering is done, the list only includes the item for Description 1 of the drug, and does not list the drug under its Description 2 value. Additionally, when the user types the Description 2 name of the drug into the search field, the drug is not found.
|
When logged into All Facilities, in the Inventory screen, when the “All Facilities - All Unique Items” filter is selected, both drug descriptions are now included as separate items in the list. Now, when the user enters the Description 2 name of the item into the search field, the inventory item is found under its Description 2 name. |
| Inventory |
C 4022 |
When updating the Cost value in an Inventory record while logged into All Facilities, there is a potential for user error. After editing of the Cost field of an Inventory Item and saving the change, the user is prompted to select a facility. The Facilities screen pops up with the “All Facilities” selection highlighted. When the user clicks on another facility in the list, the “All Facilities” selection remains highlighted. This creates a risk of erroneous inventory data entry. |
The code behind the Facilities selection screen has been modified. Now …
The Facilities screen pops up with the “All Facilities” selection highlighted. When the user clicks on another facility in the list, the “All Facilities” selection is automatically deselected.
|
| Inventory |
C 4023 |
When copying an inventory item from one facility into another facility, the item duplicates itself in the original facility. |
The inventory copying function has been modified. Now …
When a user copies an inventory item from one facility into another facility, the item does not duplicate itself in the original facility.
|
| Order |
C 3986 |
Add the ability to edit an inpatient order, and change its category from “Inpatient Unit Dose” to “Inpatient IV”.
Add the ability for users to edit inpatient orders to change their order type from one category to another (say from a Unit Dose order type to an IV order type). Currently, once the order type has been set and the order entered, future edits to the order type are limited to order types of the same category as the order type currently assigned.
|
Now when editing the Order Type in an Inpatient Order, Ascend will display and allow the user to select an Order Type that is linked to either Inpatient Unit Dose or Inpatient IV Category. |
| Order |
C 4013 |
When refilling an order, calculate the Expiration Date as the number of days from the Mix date.
The Expiration date on the refill is currently based on the first fill expiration date.
The Expiration date on the refill should be based on the number of days between the Mix Date and Expiration Date of the previous fill, but calculated from fill start date of the refill order.
When the Mix date of an order is changed, the expiration date for that order must be updated, advancing or retarding the expiration date to maintain the same number of days between the two dates.
|
The logic that does the calculation of the Expiration Date of the order has been changed. Now ...
When a user refills an outpatient order that already has a mix date and expiration date filled in, the new refill order will have a default Mix Date of now (the current date/time). The Expiration Date on the refill is moved forward from the refill's Mix Date the same number of days as separated them in the order being refilled.
If the user edits the Mix Date of an order that already has an Expiration Date, the Expiration Date will be changed to maintain the same number of days separating the two dates.
Note that, this logic works the same whether the user manually types in a date, uses the "+" calendar function to select the date or changes the date by way of the "number interpretation" method (the user enters a number, such as 3, into the date field and then moves the focus outside the date field, and the program automatically calculates the date as that many days minus one from now).
|
| Order |
C 4014 |
When replacing an order with a quantity of 1, the warning message “This order would exceed authorized amount” is presented when it should not be. |
Changed the code that tests for exceeding the authorized amount. Now, when an order with a quantity of 1 is replaced, no warning message about the authorized amount is presented. |
| Order |
C 4017 |
Disable Replace functionality on Cancelled or Discontinued Orders
The Ascend product should not allow the user to "Replace" cancelled or discontinued orders.
|
The Ascend product no longer allows the user to Replace a cancelled or discontinued order. |
| Order |
C 4020 |
The user is unable to use the TPN calculator when entering the Infuse Over and IV Rate values.
An error message is generated when using the TPN Calculator. The user is unable to select QS mode. If the user enters Infuse over and IV rate on the General Tab or TPN Tab, the program will generate an error, and the TPN calculator won't work. Additionally, the IV rate is not saved when entering.
|
The TPN calculator code has been modified. The error is no longer generated when using the TPN calculator and entering the Infuse Over and IV Rate. |
| Order |
C 4021 |
The Copy/Paste function should update the Mix and Delivery Dates to the Start date on outpatient orders.
When using the order copy paste function for outpatient orders, the user is prompted to enter a start date. If the date is the current date, the fill start date, mix date and delivery date are populated with the current date. If the user changes the start date to a date in the future or past, the mix date and delivery date remain the same as current date, and only the fill start date is updated.
The dates in the mix/delivery date fields need to be the same based on the start date. A change to the entered start date should automatically update the mix and delivery date fields of the order.
|
Now, when copying and pasting an outpatient order, when the user changes the Start date to start in the past or future, the Fill Start date, mix date and delivery date are populated with the appropriate date based on what the user entered as Start date |
| Order |
C 4037 |
In Ascend version 6.1.53, when the user presses the ENTER key in an oupatient Order screen to jump from field to field, three of the date fields get skipped over.
In the Order Entry screen, the user can depress the ENTER key and the cursor will switch to the next field of the Order screen. However, when the ENTER key is depressed while moving through the fields, the FILL START DATE, MIX DATE, and NEXT FILL DATE fields get skipped (as soon as the focus is placed on the field, the focus jumps to the next field).
Because this occurs, in the case of a pharmacist who is accustomed to "10-keying" orders, it is very easy to enter erroneous data into the order without recognizing that it has happened.
|
Modified the code behind the outpatient Order screen. Now …
When the user presses the Enter key to exit one field and enter the next field of the outpatient Order screen, when the focus is placed on the any of the FILL START DATE, MIX DATE, or NEXT FILL DATE fields, the focus will remain on that field until the user takes an action to exit the field. The program no longer automatically "jumps" to the next field as soon as the focus is placed on a field.
|
| Order |
C 4044 |
Create an index in the database for ClaimsItems.OrderItemRef to improve the performance of queries that include this column. |
With this index added, the performance of these queries is noticeably improved. |
| Other Links |
C 3568 |
Enable users to double click on a document under the Other Links tab of the Patient Profile screen to open the selected document. |
Added the ability to double-click on a document under the Other Links tab to open the document. |
| Patient |
C 3084 |
Change Pregnancy/Lactation fields from Yes/No checkbox to a selection list. The following values are required:
Unknown
No
Yes
Not Applicable
When adding a new Patient record, default the Pregnancy/Lactation fields as “Not Applicable” for a Male, and “Unknown” for a Female. If Sex is not specified, then set these values to “Unknown”.
NOTE: Some ADT (admission) interfaces receive Pregnancy/Lactation data in a Z segment, with the code values specified as:
UNK or U = Unknown
N = No
Y = Yes
NA = Not applicable
|
The pregnancy status of a patient is displayed as a dropdown list control under the General tab of the Patient screen, and can be set to Yes, No, Unknown or N/A.
During the update to Ascend version 6.2.20 (or higher), ALL patients with a sex set to Male will have their pregnant and lactating columns both populated with a value of 3 (N/A). This is performed in by update sequence 20091235.
When the user selects a sex of Male, the screen immediately sets the values of the Pregnant and Lactating fields to N/A, and disables those two fields.
When the user selects a sex of Female, the screen immediately sets the values of the Pregnant and Lactating fields to Unknown, and enables those two fields. The user can then select any value from the dropdown for each field.
NOTE: If the user selects a value of N/A in the Pregnant and/or Lactating field for a patient identified as female, even though the screen allows this (and displays the selected value of N/A), when the patient's record is saved, that field is changed to have a value of Unknown (since the N/A value is invalid for a female patient). The next time the user opens the patient record for viewing/editing, the pregnancy and lactation values will display as Unknown.
If no sex is selected, there are 4 choices in the drop downs are. N/A, No, Unknown and Yes.
The database values are:
0=UNKNOWN
1=NO
2=YES
3=N/A
|
| Patient |
C 3496 |
On the Patient Profile screen, the patient weight is displayed along with (and immediately above) the ideal dosing weight (IDW) and ideal body weight (IBW). Having all of these weights displayed can be confusing to the eye during order entry, when looking for the patient weight. The Patient Weight should stand out from ideal dosing weight (IDW) and ideal body weight (IBW) as displayed on the Patient Profile screen. |
To highlight some of the important patient information on the Profile screen, the following patient fields have been bolded to stand out:
Name
Id
Admit Dt
Discharge Dt
DOB
Age
Sex
Ht
Wt
|
| Patient |
C 3978 |
As a customer converts to the Ascend product from Ascend-HI, some patient records have no admit date. This causes problems when searching for patients in Ascend, and creating patient admission records.
Currently an SQL command is manually issued (after the conversion is complete) to clean up this issue. For each patient, the command populates the AdmissionDate column of the PatientAdmissions table to be the “EnteredDate” of the earliest order that exists for the patient. If the patient has no orders, the AdmissionDate column of the PatientAdmissions table is left blank for that patient.
|
The SQL command that has been being manually issued has been added to the HI Clean routine. It is no longer necessary to run the SQL after the conversion is completed. |
| Patient |
C 3994 |
When selecting a patient from the "Select A Patient Admission" window, after typing in the “Search By” field, the user can use the down arrow to move the focus to the list of patients matching the search value. However, the focus is not on the first item in the list, and requires an extra up arrow key stroke to move the focus to the first item in the list of patients. |
Added code to set the focus to the first listed patient when the user clicks the down arrow after entering a name for the search. Now …
When selecting a patient from the "Select A Patient Admission" window, after typing in the “Search By” field, the user can use the down arrow to move the focus to the list of patients matching the search filters. The focus is on the first item in the list immediately after the user clicks the down arrow key, and no longer requires an extra up arrow key stroke to move the focus to the first item in the list.
|
| Patient |
C 4018 |
Add the ability via the Patient “right-click” menu to Switch Facilities, Log Out and Log Out + Exit.
Users frequently switch facilities, but Ascend does not have the option to switch facilities when using the right click menu on patient demographic area. The only way to access the option to switch facilities is to use the Patient dropdown menu. This is time consuming.
|
The menu for Patients (accessed by right-clicking on the patient demographic area of the Profile screen), now includes the option to switch facilities.
The user can already click the small red x at the top right of the Profile screen to logout and exit. The user can already click on the lock icon to log out.
|
| Patient |
C 4054 |
Add “NKFA” to the list of allergies available in the “Add Allergy” screen (NKFA = No Known Food Allergies).
When the user opens the Patient Admission Information screen, and then selects the Allergies/Diagnoses tab, the Allergies “Add” and “Edit” buttons are accessible. If the user adds or edits an allergy, the “Add Allergy” screen appears. The user can select from a list of allergies in this screen. However, “NKFA” is not available in the listed allergies. This limits compatibility with messages that arrive via some interfaces to Ascend.
|
The Lookups.XML file was updated to include the NKFA value in the list of allergies. Now …
When an update is applied, the program will extract the new value from the XML file and generate a row in the LookupValues table in the Ascend database. That will cause the NKFA value to be included and selectable in the allergy list of the Add Allergy screen.
|
| Reports |
C 3485 |
Add the option to the MAR to display the storage note as part of order data. While the user can currently type "REFRIGERATE" or the like into the Instructions or Comments fields, it would be convenient if the MAR displays the storage note for an order. |
A checkbox, labeled "Storage Note” is now found inside the "Include The Following Fields:" box under the MAR tab of the Options screen.
To access the new option, from the Profile screen, follow the menu path Utilities->Options. This will cause the Options screen to appear. Click on the MAR tab. The new checkbox, labeled "Storage Note”is seen in the "Include The Following Fields:" box.
If this checkbox is checked, after the change is saved (by closing the Options screen), the storage notes of an order are printed on the bottom line of the left-hand column of the order's area on the MAR report.
The list of options now found in the "Include The Following Fields:" box are:
AHFS Therapeutic Code
Comments
Mix Instructions
Nurse Instructions
Physician’s Orders
Storage Note |
| Reports |
C 3499 |
Users create extemporaneous label templates for medications where they commonly print extemporaneous labels. To print an extemporaneous label, they select a label template under Reports/Extemporaneous Labels, and then click on the Edit button. Next they make edits to the template; Lot #, Expiration Date, etc. When finished, they then click the Save button and then click Print, without reselecting the label just edited.
The result is that they get the wrong label because when clicking on Save, the focus or highlight is moved to the top of the list. This is counter-intuitive.
Request is that the focus remain on the label template last selected until the form is closed.
|
When the user saves an edited existing Extemporaneous Label record, or a new Extemporaneous Label record, the focus is set on the Name field and the item selected in the "Labels" list will be the record just edited/saved. |
| Reports |
C 3761 |
Add a new Accounts Receivable Report that excludes the patient portion from the accounts receivable balance due. The report must list the amount due by payer. The report must either exclude the patient portion (as an report option), or have a column to indicate patient portion.
This report is needed because some customers who enter the patient portion in a claim and bill a patient claim do not always create a co-pay claim to track the patient portion separately on the A/R.
|
A new version of the Accounts Receivables report has been created and included in the Ascend release package. This new version of the report includes a new column labeled “Patient $”. This new column is populated with the patient portion for each claim.
NOTE: The file date of the new version of the “Accounts Receivables.RPT” file is 9/2/2010 11:02 AM.
|
| Reports |
C 3979 |
The MAR option to NOT print times in a section is not working .
Setting the option to NOT “Show Times” for a Section of the MAR fails to cause the MAR to leave blank the columns with order doses.
To reproduce:
Under the MAR tab of the Options screen, Click the Add Section button under the list labeled “MAR Sections”.
When the popup question appears that asks “Do you want to show times for this section?”, click the No button.
Next, link an Order Type to the new MAR Section.
Add a scheduled order for the linked Order Type.
Print the MAR.
Look at the order in the new MAR Section of the MAR. The order dose times are still printed.
|
Modified the MAR.RPT file to correct this issue. Now, when the user runs the MAR report, the order dose times are NOT printed in a section that has the option to NOT “Show Times”. |
| Security |
C 4046 |
Add an “All Facilities” filter to User Security screen. This will simplify the setting of group permissions.
The user needs to be able to edit and assign security groups to those users who have access to all facilities. The user is currently unable to view a list of those users when logged into All Facilities. Currently, the user can only select one facility at a time.
|
An “All Facilities” filter has been added to User Security screen. |
| Security |
C 4050 |
Add options for Rx Counters in Security Groups.
Add the ability to limit users to specific Rx counters by using Security Groups.
|
A new tab (titled Order Counters) has been added to the Security Groups screen to enable/disable access to order types that use specific RX counters.
If a security group has any of the counter checkboxes checked under the "Order Counters" tab, then any user who inherits security attributes from that group will be limited in the order types that can be selected in an order.
This user, when editing an order, will only see, in the "Order Type" dropdown control under the General tab of the Order screen:
Those order types that are linked to the counters whose checkboxes are checked in the Security Groups screen for the group from which the user inherits their security attributes.
Those order types that do not have any RX counters (like inpatient orders).
If a security group has NONE of the checkboxes checked for the RX counters under the Order Counters tab of the Security Groups screen, for users whose attributes are inherited from that group, no filtering will be done on order types during the order entry process based on the Groups Security settings of the RX counters.
If a customer wants to prevent users from entering all outpatient or inpatient orders, then they should use the permissions and disable the menu options. This also will avoid breaking the order entry process for all current Ascend customers that do not limit by RX counters.
|
| Security |
C 4061 |
Add a new option to hide the Setup button on the Login Screen.Add a checkbox under the General tab of the Options screen (inside the "Workstation and Updates" frame) to turn on and off the display of the Setup button on the Ascend Login screen. Label the checkbox "Hide workstation setup button".
This new option is to be set once for all facilities. If the user logs into any facility, and then changes that setting, then it is to be changed for all of the other facilities at the same time.
|
Added a checkbox (labeled "Hide workstation setup button") under the General tab of the Options screen (inside the "Workstation and Updates" frame) to turn on and off the display of the Setup button on the Ascend Login screen.
To access the new option, from the Profile screen, follow the menu path Utilities->Options. This will cause the Options screen to appear, with the fields under the General tab displayed. The new checkbox is seen in the middle of the right side of the Options screen.
If this checkbox is checked, after the change is saved (by closing the Options screen), when a user starts the Ascend program and the Login screen is presented, the Setup button will not be visible on the Login screen.
This feature is not facility-specific. A single setting is shared by all facilities. If the user logs into any facility, and then changes and saves the "Hide workstation setup button" setting, then the new setting goes into affect immediately for that facility, as well as for all other facilities at the same time.
|
| System |
C 3985 |
Change Ascend to use the Ascend.INI file (instead of the Ascend-HI.INI file).
The Ascend product is often being evaluated or tested on the same server as is the Ascend-HI product (particularly for customers upgrading from Ascend-HI to Ascend).
This causes problems because both products use the same Ascend-HI.INI file.
The Ascend product should have its own configuration (INI) file that is separate from (and has a different file name than) the Ascend-HI.INI file.
|
When the Ascend program is started, it will now first look in the application folder for an Ascend.INI configuration file (instead of the Ascend-HI.INI file). The layout and content of the Ascend.INI file is identical to that of the Ascend-HI.INI file.
Having each product (Ascend and Ascend-HI) use its own configuration file prevents the Ascend product from writing to the Ascend-HI database, and also keeps the Ascend-HI product from writing to the Ascend database when the two products are being tested while installed on the same server.
If no Ascend.INI file exists, then Ascend will continue to look for the “Ascend-HI.INI” configuration file in the same location. This is done to insure that the change requires no action on the part of existing customers in order to have the product continue to act as it always has.
To get an Ascend.INI file into the application folder, copy the existing “Ascend-HI.INI” file, and paste it into the application folder as “Ascend.INI”. Leave the existing Ascend-HI.INI alone, so there will be no impact on the Ascend-HI product.
Once the Ascend.INI is in the application folder, Ascend will use that file for its configuration.
Some issues will still remain when running both Ascend and Ascend-HI on the same server machine when each is pointing to a different database. These issues involve printing and some of the fields that are printed on labels and forms. Most printing will work in most cases. However, there will be some cases, when printing from Ascend, where the allergies, diagnoses and some other data doesn't print on the form.
Once the Ascend-HI product has been removed from the machine, this will resolve itself, since the Crystal Reports engine will use the COM component in the Ascend application folder instead of Ascend-HI.
When operating Ascend and Ascend-HI in a Citrix environment:
It is strongly recommended that the user run Ascend on a different Citrix server than the one from which the Ascend-HI product is being run, but this is not always an option.
The customer must first copy the existing “Ascend-HI.INI” file, and paste it into the application folder as “Ascend.INI”. Then, the customer must put copies of the users' Ascend.INI files on the “M:\Document and Settings” folder of the Citrix server. If the users have Ascend.INI files in their “M:\Document and Settings” folder, but there is no Ascend.INI in the application folder, Ascend will continue to look for Ascend-HI.INI file.
After the latest Ascend client has been installed, it is recommended that the user re-register the AscendHI.DLL component in the Ascend-HI application folder using the “regsvr32” utility to make sure changes made using the Ascend-HI product are correctly stored in the Ascend-HI database (and not in the Ascend database).
Tests should be performed after this to verify that changes made using the Ascend product are correctly stored in the Ascend database (and not in the Ascend-HI database), and that changes made using the Ascend-HI product are correctly stored in the Ascend-HI database (and not in the Ascend database).
Again, if the user can have an Ascend Citrix server for testing that is a different server than one used as the Ascend-HI production server, that would be preferred, as this provides a wall between the two systems.
|
| System |
C 4031 |
Delete the CATHS table from database. This table is no longer used. |
The CATHS table was removed from the database. |
| System |
C 4032 |
Add a primary key to the PrintQueue table. This can be used to improve the speed at which printing can be accomplished. |
The PrintQueueRef field was added as a primary key for the PrintQueue table. |
| System |
C 4033 |
Add a primary key to the RNPTYPD0_NDC_PRICE_TYPE_DESC table. This can be used to improve the speed at which First Databank updates can be accomplished. |
The NPT_TYPE field was added as a primary key for the RNPTYPD0_NDC_PRICE_TYPE_DESC table. |
|
|
FIXES |
The following items are fixes to issues identified in the product |
| Billing |
C 3908 |
Question 9 of the DME 10.03 form does not display on the screen form. Additionally, the answer to the question is not being included in an electronically transmitted X12 claim. |
Now, the DME 10.03 form screen properly saves and displays the answer to Question 9. When print previewing the DME 10.03 form, the answer to Question 9 is correctly circled on the form. An ANSI X12 transmission for the claim includes Loop 2440 and its FRM segment (populated with the answer to question 9). |
| Billing |
C 3988 |
The Provider ID Qualifier and Prescriber ID fields display incorrectly in the Payer screen, under the E-Bill NCPDP tab.
The user can edit the payer record, assign values in each of these fields and save that change. Once the save operation is done, those fields appear blank on the Payer screen.
The data is stored correctly in the database record, just not displaying as expected .
|
This has been fixed. All existing Payer records now properly display the values in the Provider ID Qualifier and Prescriber ID fields as appropriate (if payer has been set up to bill NCPDP claims). |
| Billing |
C 3992 |
In the Pricing Contracts screen, the “Price Code” column is unpopulated for pricing rules that have “Inventory” selected in the “Price By” dropdown. |
The code that populates the list of pricing rules in the Pricing Contracts screen was fixed. Now the “Price Code” column is unpopulated for pricing rules that have “Inventory” selected in the “Price By” dropdown. |
| Billing |
C 3993 |
When performing NCPDP billing, the CY field of the NCPDP transaction does not contain the expected value.
The contents of the CY field of the NCPDP transaction is determined by the setting specified in the “Patient ID Field:” field (under the E-Bill NCPDP tab of the Payer screen) of the associated payer. The user has a choice of Patient ID, Social Security Number, Insured ID and Do Not Send.
When the CY field is set be populated from the Patient ID, the intent is that the ID is drawn from the patient admission record. Instead, it appears to be drawing the value from the patient record for this claim.
|
Now, when the Payer record NCPDP “Patient ID Field:” dropdown has Patient ID selected, the ID value included in the CY field of the NCPDP transmission is drawn from the current patient admission. |
| Billing |
C 3998 |
When Batch Locking claims, the user is unable to change the billed date.
Users frequently batch lock claims and change the billed date accordingly (maybe a prior date).
Ascend only allows the billed date to be the current date before batch-locking the claims.
|
The billed date of the claim has been enabled during the batch locking process, so the user is now able to edit the billed date on claims when performing the batch-locking task. |
| Billing |
C 4012 |
There are several issues related to DME items.
Claims processing is very fast unless the claims involve DME rentals. Claims with a DME rental item “time out” with a popup warning message that allows the user to proceed. After acknowledging the time out, the claim information is then displayed for editing and approval.
DME orders converted from Ascend HI do not have a “bill through” date in the Order record.
When attempting to open a DME order for viewing or editing (from under the Orders tab of the patient Profile screen), the query times out before displaying the order.
When billing and locking a new claim that has “From” and “To” dates for the DME item, the “billed through” date is not stored in the DME order item record.
|
Changed the SQL queries related to DME items. This eliminates time outs that would otherwise have occurred.
The creation of bill that have DME items in them is dramatically faster, taking less than five seconds.
DME orders converted from Ascend-HI now have the “bill through” date in the Order record.
When billing and locking a new claim that has “From” and “To” dates for the DME item, the “billed through” date is stored in the DME order item record.
|
| Billing |
C 4016 |
The filters for "Orders with a" are not working with date ranges on the New Claims screen.
In the New Claim screen, under the Ready To Bill tab, when the user selects the filter for "Order with a", and enters a date range, the orders that are displayed are not only for that date range. If a patient has a single order that falls in the filtered date range, all other unbilled orders for that patient are also being displayed.
|
Changed the code behind to New Claim screen filtering. Now …
In the New Claim screen, under the Ready To Bill tab, when the user selects the filter for "Order with a", and enters a date range, the orders that are displayed are only for that date range. If a patient has a single order that falls in the filtered date range, all other unbilled orders for that patient are not displayed.
|
| Billing |
C 4019 |
When billing DME orders, the quantity on the claim shows a negative amount.
DME items (like pumps) that are used by the patient for several months will usually be billed in 30-day increments. In Ascend, after billing the first 30 days (or whatever period of days), all subsequent billings show a negative amount in Quantity field on the claim, and that amount is the number of days previously billed. This amount can be edited, but the initial claim shows a negative Total amount and negative tax (if calculated). This needs to be changed to not show negative quantities in those fields.
|
DME items no longer show negative quantities in the Total Amount and Tax fields.
When the user bills a DME item for next 30 day period, the From date on the claim shows the correct start date for billing.
|
| Billing |
C 4026 |
In some cases, a DME order item is not found on the claim when that order is billed from “New Claims” screen, under the “Ready to Bill” tab.
Under the “Ready to Bill” tab of the “New Claims” screen, if the user selects a patient who has multiple DME orders, those DME orders are included in the list of orders on the right half of the screen.
If the user checks all of the listed patient orders, after clicking the Bill button, all of the DME orders show on the claim, as expected.
If the user un-checks an older (by Date Of Service) order, so it will not bill, after clicking the Bill button, the newer checked DME orders show on the claim, and the unchecked item is not shown, as expected.
However, if the user un-checks the newer DME item, and leaves the older items checked,
the claim still shows just the newer DME item, but not the (checked) older DME items.
|
The order inclusion logic of the billing process was changed. Now …
Under the “Ready to Bill” tab of the “New Claims” screen, if the user selects a patient who has multiple DME orders, those DME orders are included in the list of orders on the right half of the screen. If the user un-checks the newest DME item, and leaves the older items checked, the claim will not include the (un-checked) DME item, but will include all of the (checked) older DME items.
|
| Billing |
C 4027 |
Pricing Contracts – Pricing Rule sort order is not working as expected.
When generating claims based on pricing contract rules, the rules are not producing the same output in the Ascend product as is produced by the Ascend-HI product for the same input data.
|
The way the program determines which pricing rule to match now mimics how it is done in Ascend-HI.
The rules are first sorted by sort (the lower sort number are at the top of the list while the higher sort numbers will be at the bottom). If you want a price rule to be evaluated first in a contract, make it the lowest number. When pricing rules have the same sort number, the next field that controls how the rules are ordered is by the price by field. Again, the lower the number the higher the rule will appear when looking for a match:
Inventory = 1
NDC = 2
HCPC = 3
Charge Code = 4
Alternate Charge Code = 5
Revenue Code = 6
Order Type = 7
Therapy = 8
Everything = 9
|
| Billing |
C 4029 |
The Prior Authorization number is not displayed in Claim screen, under the Insurance tab.
If the user adds a Prior Authorization number on an order, and then bills that order, the Prior Authorization number from that order is expected to be displayed on the related Claim screen, under the Insurance tab, in the Prior Authorization field. However, under these conditions, the Prior Authorization field is currently displaying as blank.
Even if the user (in the Claim screen, under the Insurance tab) clicks on the Prior Authorization dropdown and re-selects the Prior Authorization number, and then clicks the Save button, the next time the claim is viewed, that field is still displayed as blank.
|
The Claim screen code was modified to properly save the Prior Authorization number value when the claim is saved (regardless of whether it is a new claim, or an edited existing claim).
NOTE: If the Prior Authorization number value is longer than 20 characters, then the value will NOT save to the claim record in the database.
|
| Billing |
C 4030 |
The HCFA 1500 (v1.3) form is printing the wrong Prior Authorization number in box 23.
After editing a claim and re-selecting the Prior Authorization number in the Claim screen, under the Insurance tab, when the user prints the HCFA 1500 (v1.3) form for the claim, an incorrect value prints on the form in box 23 (Prior Auth number field). The database reference number of the Prior Authorization record is printing, instead of the Prior Authorization number itself.
If the user creates a claim, and does not try to edit or re-select the Prior Authorization number under the Insurance tab of the claim), then the actual Prior Authorization number prints properly in box 23 of the HCFA 1500 (v1.3) form.
The correct number needs to print in box 23 under all circumstances
|
The HCFA-1500 (1.3) form now displays the correct Prior Authorization number value in box 23. |
| Billing |
C 4034 |
The Patient ID is not displaying for patients listed under the “New Claims” tab of the “New Claims” screen. |
Change the code behind the “New Claims” screen. Now, the Patient ID value displayed in the list under the “New Claims” tab will be sourced from the PatientAdmissions table, based on the patient admission record that is linked to the claim. |
| Clinical |
C 4038 |
An Error 9 is generated when entering an inpatient order for Percocet.
An error occurs when the Geriatric Precaution checking is done for a “combo” drug in an order (i.e., there is more than one drug in the item, and where two clinical alerts are expected for the order).
An error is generated when the user:
With the Geriatric clinical checking set to “On”.
Creates a new order for a patient whose age is greater than 60 years (61 years or higher).
Selects the inventory item Percocet 5/325MG Tablet with the NDC = 63481-0623-70.
Clicks the Save button on the Order screen.
The error that is generated is:
Error: 9
Description: Collection Index must be in the range 1 to the size of the collection.
Location: frmOrder – Save Order
If the user clicks OK on the error, they are prompted to charge, and then print.
Closing the order leaves a Clinical Checks window running – the window states: “checking for Custom Interactions”.
|
Modified the clinical checking code to prevent the Error 9 when performing clinical checking. |
| Clinical |
C 4059 |
In the Profile screen, when selecting “Clinical Documents” from the Clinical dropdown menu, the incorrect submenu is presented. The submenu for “New Financial Notes” is presented, instead of the expected "New Clinical Documents", "Edit Clinical Documents", etc. |
The menu code has been corrected to present the correct submenu when selecting “Clinical Documents” from the Clinical dropdown menu. The user now sees "New Clinical Documents", "Edit Clinical Documents", etc., as expected |
| Doctors |
C 3971 |
Unable to add/change/delete data in User-Defined 2 and User-Defined 3 fields under the “User Defined” tab of the Doctors screen. |
The Save routine for the Doctors screen has been modified. Now, when the user saves the Doctor record …
In the Doctors table, the MISC2 column is populated with what the user entered into the User-Defined 2 field of the Doctors screen.
In the Doctors table, the MISC3 column is populated with what the user entered into the User-Defined 3 field of the Doctors screen. |
| Doctors |
C 4010 |
The values for fields MISC2 and MISC3 of the Doctors table are not saved when the information in the Doctors screen is saved. |
The Save routine of the Doctors screen was modified. Now, when a doctor record is saved, the values entered into the user defined fields 2 and 3 are properly saved to the MISC2 and MISC3 of the Doctors table, respectively. |
| Inventory |
C 3999 |
In the Inventory screen, add the ability for the user to sort the list of facilities under the Facilities tab by the column headers. |
The Name and Id columns of the list of facilities under the Facilities tab of the Inventory screen can now be clicked upon to cause the list to sort by that value. |
| Inventory |
C 4000 |
While logged into All Facilities, when the user updates the Cost of an Inventory item, Ascend does not ask the user if they want to apply the change to all facilities. |
When logged into "All Facilities", when a user opens the Inventory screen, selects, then edits the Cost field and saves the changes to an inventory record, a popup message appears that asks the user whether they want to apply the cost change to other facilities. The popup message reads:
"Would you like to apply the new cost of $... to the other facilities?"
|
| Inventory |
C 4001 |
Improve the speed at which Inventory items are saved when adding or editing an item. |
Modified the log change routine. Minimized the time the routine takes when saving a new or changed inventory item in order to improve the speed of saving inventory items. |
| Inventory |
C 4008 |
While logged into All Facilities, when the user adds or edits an inventory record, Ascend allows the user to save the item even when no facility has been selected for the item (under the Facilities tab of the Inventory screen).
This causes the item to be saved into a "No Man's Land' in the system without a site assigned to it.
|
The code behind the Inventory screen has been modified, and will no longer allow saving an inventory without a facility selected under the Facilities tab. |
| Inventory |
C 4024 |
After adding an inventory item while logged into a single specific facility, the item is not listed when logged into All Facilities. The same is true if an inventory item is added while logged into All Facilities, and the user answers No when prompted to add the item to other facilities. |
Changed the logic related to adding inventory items to one or more facilities. Now …
After adding an inventory item while logged into a single specific facility, the item is listed when logged into All Facilities.
If an inventory item is added while logged into All Facilities, and the user answers No when prompted to add the item to other facilities, the added item is immediately visible in the list of inventory items in the Inventory screen. The new item is also visible in the single facility selected for the item under the Facilities tab of the Inventory screen.
Note that Ascend now requires that a facility (or “All Facilities”) be selected in the Facility dropdown under the Facilities tab of the Inventory screen before an inventory item can be saved.
|
| Inventory |
C 4025 |
When editing an inventory item while logged into All Facilities, even if the user cancels the edit, the change is saved in the inventory record for one facility. It appears to be the facility where the item was originally loaded in the database. |
Changed the code behind the Cancel button of the Inventory screen. Now …
When editing an inventory item while logged into All Facilities, if the user cancels the edit, the change is not saved to any inventory record.
|
| Labels-Forms |
C 4040 |
The incorrect “Unit Dose Label.RPT” file was packaged with Ascend versions 6.1.53 and 6.2.7. |
The Ascend release was repackaged with the correct “Unit Dose Label.RPT” file (dated 8/30/2010 1:09 PM). |
| Labels-Forms |
C 4058 |
The Delivery Receipt is not displaying the strength of the drug when the form option "Include all items on drug orders" is turned ON. |
The "Delivery Receipt.RPT" file has been modified to read the inventory print settings.
Print description and description 2 have been added to the delivery receipt record set delivered to the reporting engine by Ascend.
The Delivery Receipt now prints the strength of the drug when (in the Options screen, under the Printing tab) the "Include all items on drug orders" is turned ON (checked) for the Delivery Receipt.
|
| Labs |
C 4051 |
In the Labs screen, the Print and Print Preview functions are not working. |
Modified the Lab screen code. Now, the user can print and print preview selected labs. |
| Options |
C 3991 |
Several settings in the Options screen are not saving.
General Tab Fields: CURES Patient Id; CURES Prescriber Id
Admission Tab Fields: Patient Location
Order Entry Tab Fields: When No Allergy Date; When No Prior Authorization; Stop Date Grace Period
|
The Ascend program is now properly saving the Options screen information in question. |
| Options |
C 3997 |
Unable to access Options screen when logged into All Facilities.
When logged into All Facilities, when the user follows the menu path Utilities->Options, the program “locks up”.
|
The code behind the Options screen was modified to eliminate this condition. Now, when the user follows the menu path Utilities->Options, the Options screen is presented. |
| Order |
C 3813 |
When refilling of a confirmed order, the screen for the refill order displays confirmed date of the refilled order. Note that the confirmed date is NOT saved to the database for the refill order, but it is confusing to the user who is initially creating the refill. |
Now, when the user refills an order, the "Confirmed by" value is NOT displayed in the refill order screen. The value is also NOT saved to the refill order record |
| Order |
C 3916 |
When Start Date changed on an Inpatient order, the resulting Order Stop Date is incorrect.
On orders for medications that have an "auto stop days" setting that is different from the default of 30 days, if the user changes the order start time, the set auto stop days disappears, and the medication is scheduled for the default of 30 days.
|
Now, when the user creates a new inpatient order for a patient that is assigned to a Patient Care Area linked to the order item's "Auto-Stop Days" setting, and the inventory item has a stop days setting (set under the General tab of the Inventory screen) that is different than the default (set under the Order Entry tab of the Defaults screen), the order's Stop Date is initially set to the number of days after the Start Date defined in the INVENTORY ITEM's setting.
If the user changes the Start Date of the new order, then the Stop Date is still calculated as the number of days after the Start Date defined in the INVENTORY ITEM's setting.
Note that the change to the Stop Date display occurs immediately as the user is editing the Start Date of the order.
|
| Order |
C 3981 |
When a user rewrites an order that is a floor stock item with the floor stock list field populated, Ascend rewrites the order with the floor stock list attached. However, when the user completes the rewrite order and clicks the OK button, Ascend removes the floor stock list and prompts the user to print a label.
This is a particular problem with IV medications when those medications are actually in the Pyxis system. These orders are having labels printed inappropriately.
|
The code for rewriting an inpatient order has been updated to remember original floor stock list. If the order being rewritten has a floor stock list associated to the order, but the list no longer contains the items in the order, the new order will NOT contain the floor stock list. This is by default. Now, when saving the new order (even though the items are stocked in the floor stock list) the link to the floor stock list is not lost. |
| Order |
C 4003 |
Clicking OK to order item message when selecting an item for an order should not automatically add the item to the order.
When selecting an inventory item with a order entry message associated, the user receives the pop-up message. Next they select OK to the message, and the item is automatically selected for the order. The user does not have a way to cancel the item selection.
Do not automatically add the selected item to the order when the user clicks the OK button on the popup message.
|
Changed the popup message to include an OK and Cancel button. OK is the default, and continues adding the item. Cancel will cancel the item selection. |
| Order |
C 4015 |
When Copying and Pasting an order that has a prior authorization, Ascend is not saving the new order. This occurs even if the user selects a new prior authorization on the new order before attempting to save it. |
Modified the Save routine of the Order screen. The user can now successfully copy and paste an order, and save the new order when a prior authorization is linked from original order. |
| Order |
C 4028 |
Orders cannot be refilled from the Profile screen.
When the user attempt to refill an order from the Orders screen (by selecting the order under the Orders tab, and then following the Orders->Refill menu path), Ascend prompts the user with a message stating "Would you like to create a new order?". The user can, however, refill an order from within the order by clicking on the Refill button.
|
Modified the menu code for the Profile screen. Now …
When the user attempt to refill an order from the Orders screen (by selecting the order under the Orders tab, and then following the Orders->Refill menu path), Ascend proceeds to bill the selected order and present the Claim screen to the user.
|
| Order |
C 4036 |
When a user is creating orders based on common orders, in the Common Order selection (NewOrder) screen, the user can check multiple common orders to be filled back to back. When this is done, after the user saves the new common orders, with the exception of the first order, the Stop Date, Fill Stop Date and Next Fill Date are not saving in the new orders. If the user views the orders in the profile screen (under the Orders tab), or the user edits the orders, these fields are blank.
NOTE: This does NOT happen when a single common order is selected. In that case, these date fields save correctly.
|
Changed the logic behind the process of creating multiple Common Orders.
Now, when a user is creating orders based on Common Orders, in the Common Order selection screen, if the user selects (checks) multiple common orders, after the user saves the new common orders, the Stop Date, Fill Stop Date and Next Fill Date are saved correctly in all of the new orders.
|
| Order |
C 4041 |
The prompt to update the order description pops up even when creating a new order.
Ascend has an option to ask the user if they want to update the order description when an order item is changed. The option can be found in the Options screen ( follow the Utilities Menu->Options to open the Options screen). Under the Order Entry Tab, the dropdown list for "Order Description" contains:
Prompt to update with item change (ask me)
Always update with item change (do it, don't ask)
Do not update with item change (don't change and don't ask)
With the first choice selected, the Ascend program prompts the user (even when building a new order) with every order item selected, including the FIRST item.
Additionally, if the user changes the original dose (a case where the prompt is appropriate), the prompt does appear, but the prompt and new description are incorrect. They are both still displaying the original Inventory strength.
Example:
Tylenol 325 MG
Qty/Dose = 2, so the strength is 650 MG.
The prompt says:
Current Description: TYLENOL 325 MG
Proposed Description: TYLENOL 325 MG
The prompt should say:
Current Description: TYLENOL 325 MG
Proposed Description: TYLENOL 650
|
Modified the logic behind the handling of the Order Description Now …
With the Order Description for the facility set to "Prompt to update with item change" (in the Options screen, under the Order Entry tab):
The user can create a new order, and select an order item that has a strength value, and then change the quantity per dose value.
A prompt pops up allowing the user to change the order description. The values displayed in the popup prompt are correct for the original order description and the changed order description.
With the Order Description for the facility set to "Always update with item change" (in the Options screen, under the Order Entry tab):
The user can create a new order, and select an order item that has a strength value, and then change the quantity per dose value for the first item in the order.
No prompt pops up, and the order description is changed automatically.
With the Order Description for the facility set to "Do NOT update with item change" (in the Options screen, under the Order Entry tab):
The user can create a new order, and select an order item that has a strength value, and then change the quantity per dose value for the first item in the order.
No prompt pops up, and the order description is NOT changed automatically.
NOTE: All of these processes work regardless of the selections in the Order screen dropdowns under the list of order items.
|
| Order |
C 4048 |
The Therapy is not saving in the order entry screen when selected from the dropdown. |
Code was changed in the routine that saves the selected therapy for an order. Now …
When the user selects a therapy in the "Therapy:" field under the General tab of an OUTPATIENT Order screen, and then saves the order, the link to the selected therapy pointer is properly saved to the Order's record in the database. When the user re-opens the edited order, the new therapy selected is properly displayed in the "Therapy:" dropdown control.
|
| Patient |
C 3390 |
User is unable to delete a patient admission that has orders linked to it.
To delete one of the many admissions for a patient:
Open the Patient Admission Information screen for the patient and (under the Admission/Discharges Tab) select the admission. With the admission selected, click on the Delete button.
The admission appears to go away. Click on the Save button to save the changes to the patient record. After this is done, in the Profile screen, with the same patient selected, the admission is still displayed in the tree view of admissions in the upper right corner of the screen.
This is not just a screen refresh issue. Even if the patient is re-selected, the Admission is still present.
Instead of simply not deleting the admission, a message should be displayed that informs the user that the admission cannot be deleted due to linked orders.
|
Added a popup warning message when the user attempts to delete an admission that has other records linked to it.
If there ARE records linked to the admission, the program pops up a message stating that the admission cannot be deleted. The types of records linked to the Patient Admission record are:
Orders
Prior Authorizations
Patient Therapies
Clinical Reviews
Labs
Claims
NOTE: Clinical Documents, Other Links, Financial Notes and Nursing Visits are not currently linked to an admission.
If NO records are linked to the admission, the user is asked to confirm that they want to delete the admission record. If the user clicks on the "Yes" button, the admission immediately disappears from the Patient Admission Information screen. When the user clicks the Save button of the Patient Admission Information screen, the admission record is removed from the database. When the user re-opens the Patient Admission Information screen for the same patient, the admission is no longer displayed.
|
| Patient |
C 3713 |
The selected patient admission is changed after editing and saving a patient record.
To replicate this issue:
The user selects a patient whose two most recent admissions are NOT discharged.
The most recent admission for the patient is a Recurring Outpatient admit.
The second most recent admission for the patient is an Inpatient admit.
The user selects the Inpatient admission (second most recent), and edits at least one field in the Patient Admission Information screen.
When the user clicks the Save button, the focus is placed back onto the Patient Profile screen, with the edited patient selected and loaded into the screen. However, the most recent admission is selected, instead of the initially-selected admission. This change of admission selection is not very obvious to the user.
If the user does not notice the change, and proceeds to enter orders for the patient , those new orders are entered for the most recent admission, instead of the admission selected by the user at the start of the process.
When this isn't caught immediately, the medications are not included in batch dispense process (Fill List and IV Label printing). It also means that an MAR may not print, or if printed, may exclude some of the inpatient admission medications.
Note: This problem exists whether or not the admission is discharged. If the most recent admission is discharged, then Ascend warns the user when order entry is attempted.
|
Now, the selected admission continues to be selected after the user edits the Patient Admission Information screen and saves the change.
The exception to this is:
If a new admission is added from within the Patient Admission Information screen (under the Admissions/Discharges tab), when the user saves the change, the new added admission will be selected
|
| Patient |
C 3977 |
When first opened, the Workers Comp screen does not display the stored Employer State value.
On the Patient Admission Information screen, under the Insurances tab, the user can double-click an existing Workers Compensation record to edit the record (or select the record and click on the "Edit Comp" button) to open an edit screen (“PatientWorkersComp”) for the record.
When the “PatientWorkersComp” screen opens, the "Employer State" field dropdown control is empty (even though the correct data for the selected state is in the database.
|
Now, when the “PatientWorkersComp” screen initially opens and loads the values, the State drop down is preselected to the value stored in the database. |
| Patient |
C 4004 |
IBW and IDW are not displaying on the Patient Profile screen.
The Ideal Body Weight and Ideal Dosing Weight fields are not populating when the patient data is loaded into the patient profile form.
|
The Profile screen code was modifies so that the IDW and IBW now properly display on the Patient Profile screen. |
| Patient |
C 4049 |
The “Relation to insured” value under the Insurance Tab of the Patient Admission Information screen is not being saved with the patient insurance record. |
Changed the routine that handles saving the "Relation to Insured" value in the PatientInsurance table. Now ...
When editing a patient's record in the Patient Admission Information screen, under the Insurances tab, the user can edit a patient insurance record by double-clicking on the insurance row in the list of insurances in the box at the top of the screen. The user can select a value in the "Relation to Insured" dropdown control. This value is saved to the PatientInsurance table record after the user clicks OK to close the Patient Insurance screen, and then clicks the Save button to save the changes to the patient's record. When a user re-opens the Patient Insurance screen for the edited insurance of the patient, the "Relation to Insured" dropdown properly displays the new value.
|
| Reports |
C 4035 |
An error is generated when printing some saved reports. |
The WHERE clause of the SQL for the saved reports was not being parsed for replacements, as is done for the reports that are not saved versions. The code to replace SQL values has been modified to work when running saved reports |
| Security |
C 4007 |
Unable to add new User in the user Security screen. |
Modified the code behind the Security screen. Now, the user can successfully add new users to the Ascend database via the user Security screen. |
| Security |
C 4045 |
The Security screen is not working properly when setting the flag to force a user to reset their password.
When administrator populates the "Assign Password" field in the security record for a user (regardless of the status of the "reset upon log in" checkbox on the Security screen), when the record is saved, the program saves the record with the "reset upon log in" value set to "checked".
Once the "Change Password At Next Login" option has been turned on for a user, the administrator cannot turn it off until the user changed their password.
|
The Security screen code was changed so that the prompt can be turned on/off without requiring the user to change the password during the login. |
| Therapies |
C 4047 |
The Prior Authorization field in Therapy screen not displaying the saved value.
When adding/editing a therapy record and selecting the prior authorization for the therapy, the prior authorization is not displayed upon viewing the therapy record after saving.
|
Fixed the routine that controls the loading of the saved Prior Authorization value into the Therapy screen. Now ...
When the user opens a Therapy record, and then changes the selection in the "Prior Authorization:" dropdown control, the new value is saved when the user clicks the OK button on the Therapy screen. This value is saved as a pointer in the PatientTherapies table of the database. When the edited Therapy is re-opened in the Therapy screen, the newly selected prior authorization value is displayed in the "Prior Authorization:" dropdown control.
|