ASCEND-HI -- CURRENT VERSION RELEASE NOTES
Version 2.14.122 (05/18/2009 )
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: References are provided that show each CSR (CSR = Customer Service Request) related to a released version.
NOTE: This version of the Ascend-HI program works with the following companion program versions:
AscendHI.DLL - Version 1.3.3
UpdateHI.EXE
- version 1.1.851 (20080621 <-- This is the last
sequential internal update performed by this version)
This Ascend-HI CURRENT release was repackaged with the latest First Databank files 06/02/2009 3:30 PM.
This Ascend-HI CURRENT release was re-packaged with the newest FDB files on 7/6/2009 10:43 AM.
This Ascend-HI CURRENT release was re-packaged with the newest FDB files on 8/6/2009 12:22 PM.
This Ascend-HI CURRENT release was re-packaged with the newest FDB files on 8/31/2009 3:47 PM.
This Ascend-HI CURRENT release was re-packaged with a newer product expiration date on 9/8/2009 9:30 AM.
UpdateHI.EXE
- version 1.1.859 (20080621 <-- This is STILL the last
sequential internal update performed by this version)
This Ascend-HI CURRENT release was re-packaged with the newest FDB files on 9/29/2009 11:26 AM.
This Ascend-HI CURRENT release was re-packaged with the newest FDB files on 11/03/2009 11:26 AM.
This Ascend-HI CURRENT release was re-packaged with a new product expiration date on 11/03/2009 11:26 AM.
This Ascend-HI CURRENT release was re-packaged with a new product expiration date on 12/14/2009 3:23 PM.
This Ascend-HI CURRENT release was repackaged with the latest FDB files on 1/04/2009 11:04 AM.
This Ascend-HI CURRENT release was repackaged with the latest FDB files (with data date: 01/28/2010) on 2/02/2010 01:50 PM.
UpdateHI.EXE
- version 1.1.865 (20080621 <-- This is STILL the last
sequential internal update performed by this version)
This Ascend-HI CURRENT release was repackaged with the latest FDB files (with data date: 02/25/2010) on 3/01/2010 05:12 PM.
This Ascend-HI CURRENT release was repackaged with the latest FDB files (with data date: 04/01/2010) on 4/08/2010 09:06 AM.
UpdateHI.EXE
- version 1.1.868 (20080621 <-- This is STILL the last
sequential internal update performed by this version)
This Ascend-HI CURRENT release was repackaged on 5/10/2010 09:37 AM with the latest FDB files (with data date: 04/29/2010).
This Ascend-HI CURRENT release was repackaged on 6/07/2010 03:24 PM with the latest FDB files (with data date: 05/27/2010).
UpdateHI.EXE
- version 1.1.870 (20080621 <-- This is STILL the last
sequential internal update performed by this version)
This Ascend-HI CURRENT release was repackaged on 8/04/2010 12:26 PM with the latest FDB files (with data date: 07/29/2010).
This Ascend-HI CURRENT release was repackaged on 8/30/2010 5:07 PM with the latest FDB files (with data date: 08/26/2010).
This Ascend-HI CURRENT release was repackaged on 10/04/2010 4:52 PM with the latest FDB files (with data date: 09/30/2010).
This Ascend-HI CURRENT release was repackaged on 12/10/2010 1:04 PM with a new product expiration date.
UpdateHI.EXE - Version 1.1.872 (20080621 <-- This is STILL the last sequential internal update performed by this version).
Here is a list of new database changes
Each new update sequence in the UpdateHI.exe program is listed with a brief note about what it accomplishes. Note that some sequence numbers are skipped.
Update20080424 ' Delete selected records from the ReportCriteriaFields table. Change the SQL for the Charges report.
Update20080425 ' CSR: 2659 -- Add lookup values for Narcotics Reporting ASAP versions.
Update20080426 ' CSR: 2671 -- Change the WHERE clause SQL for the Unbilled Orders report (changed the SQL in the AddOrUpdateSQLSource routine).
Update20080427 ' Add PatientRef to the Charges report for grouping.
Update20080428 ' Add "DR2_RT" column to the Routes table. Run Common.UpdateRoutes routine to update the routes.
Update20080429 ' Change the "Allergy" column to a VARCHAR(50) type in the "PatientAllergies" table.
Update the "Routes" report's SQL SELECT statement in the SQLSources table.
Update20080501 ' Add Lookup values for the Lookup Table "DEACodes".
Update20080502 ' Add "SystemRecord" field to the "ClinicalReviewTypes" table.
Add "EnteredByRef","EnteredDate" fields to the "ClinicalReviews" table. Add Lookup
values for Lookup Table "OptionsOrderTables". Run the Common.
UpdateClinicalReviewTypes routine to update the types.
Update20080503
' Add ClinicalReviewLookups.SystemRecord column. Update Clinical Review Types. Update Clinical Review Problems.
Update20080504 ' Add Claims.OwnerClaimRef column. Copy Claims.OriginalClaimRef into Claims.OwnerClaimRef for all Claims records. Add report defaults for Patient
Account Statement.
Update20080505 ' Add Security Objects to Profile form.
Update20080506 ' Change SQL for reports (Inventory Usage Based On Order Changes,Inventory Usage Based On Orders,Prescription Log. DeleteSecurityObject
(CrystalReports.Physicians License Expiration). AddReportCriteria(Doctors.LicenseExpirationDate). Remove Claims.OwnerClaimRef column. Add
Claims.PrimaryClaimRef Column. Copy Claims.OriginalClaimRef into Claims.PrimaryClaimRef for all Claims records. AddReportCriteria (Inventory. AHFS
Description).
Update20080507 ' CSR: 2293 -- Delete the Physicians License Expiration report file. This report was erroneously reintroduced to the Ascend-HI release package.
Update20080509 ' Delete non-custom 'SELECT' rows from SQLSources table. Refresh all SQL in the SQLSources table.
Update20080510 ' Add lookup values for NCPDPCompoundQuantity.
Update20080511 ' Create Table: RSTR1_STRNGTH_DESC.
Update20080512 ' Add MSP lookup rows (CASCodes, ClaimAdjustmentGroupCodes, ContractTypes),payer defaults ('X12 2000B Loop: MSP PayerType') and fields
(Claims.ClaimAdjustmentGroupCode, Claims.X12Loop2320CAS, Claims.X12Loop2300NTE02, ClaimsItems.ClaimAdjustmentGroupCode,
ClaimsItems.X12Loop2430CAS, PricingTemplates.ContractTypeCode).
Update20080513 ' DROP RSTR1_STRNGTH_DESC TABLE. Add ClinicalReveiw columns CompletedByRef, CompletedDate. Add report criteria for ClinicalReviews.
Update20080514 ' Add SQL to SQLsources for Program, ASAP (Narcotics reporting).
Update20080515 ' Change stored SQL for 'AHFS Codes' and 'Food Drug Interactions'. Set the Default date field for Food Drug Interactions.
Update20080516 ' Add SQL to SQLsources for Program, OrderLabelWithDoses. Add/change report defaults for "Inventory By AHFS", Inventory By First Databank Code"
reports, "Inpatient IV Label" and "Stop Order Notices". Add/change security objects, criteria and SQL for "Clinical Reviews" report. Drop Column
"ReviewedByRef" from "ClinicalReviews" table.
Update20080517 ' Add report criteria for First Databank reports. Add/Update stored SQL for "Inventory By First Databank Class" report.
Update20080518 ' Add/Update stored SQL for "Inventory By First Databank Class" report.
Update20080519 ' Delete and Add Report Criteria for "AHFS Description". Add/update stored SQL for "Clinical Reviews" report.
Update20080520 ' Add/update stored SQL for "OrderWithDeliveryPatientAddress", "OrderWithDeliveryShippingAddress", "PatientLabel" and "Food Drug Interactions".
Update20080521 ' Delete and Add Report Criteria for "First Databank Class ID", "First Databank Class Description".
Update20080522 ' Delete security object for "Inventory By First Databank Code" report. Add security object and defaults for "Inventory By First Databank Class" report.
Update20080523 ' Move three report defaults.
Update20080524 ' Add Column "SQLSources" to the "Options" table. Add/Update stored SQL for "MAR 31 Day" report.
Update20080525 ' Change ClinicalReviewTypes lookup values. Add/update stored SQL for "MAR" report WHERE clause. Set facility default to True in the Defaults table
row "ORDER ENTRY", "INVALID NDC WARNINGS". Add lookup value for "NCPDPPatientIdField".
Update20080527 ' Add "09 Other" lookup value for ContractTypes lookup. Add ClaimOTAF column to Claims table.
Update20080528 ' Add report criteria for Prior Authorizations. Change SQL in SQLSources for the 'Program' 'ASAP' query.
Update20080529
' Change the SQL in the SQLSources table for the SELECT clause of the Patient Label. Add Archived column to AdjustmentTypes table.
Update20080530 ' Remove SQLSources rows that might have non custom SELECT or WHERE statements that are linked to a facility.
Update20080601 ' Set the default date field to 'A/R' for Accounts Receivables reports. Add Program/OrderLabel SQL to SQLSources table.
Update20080602 ' Remove the SQLSources.Options column. Add the DisplayShortcut column to the SQLSources table.
Update20080603 '
Remove the Outpatient Label report file from Ascend-HI customers' machines.
Update20080604 ' Clean up LookupValues entries for 'OptionsAdmissionTables'.
Update20080607 ' Update Fill List and Drug Utilization sql.
Update20080608 ' Create indexes on dosage range table.
Update20080610 ' Change the Select SQL stored in SQLSources table for "Floor Stock Lists". Add security object for "Floor Stock Lists".
Update20080611 ' Add lookup values for 'InventoryDescriptionField'. Add column "ClinicalReviews.PatientAdmissionRef" and index on the column. Add column
"SecurityPreferences.SecurityGroupRef".
Update20080612 ' CSR: 2872 --
Delete the Outpatient Label report file from Ascend-HI customers' machines.
Update20080613 ' Add DosageCheck column to the Inventory table.
Update20080614 ' Add PatientAdmissionRef to Charges and Fill List
SQL.
Update20080615 ' CSR: 2872 --
Delete the Outpatient Label report file from Ascend-HI customers' machines
using updated DeleteReportFile rotuine.
Update20080616
' Add report defaults for Fill List. Add Report Default Value options.
Update20080617
' Add report criteria and Report Default for Floor Stock Lists. Change SQL for OrderWithDeliveryPatientAddress and OrderWithDeliveryShippingAddress.
Update20080618
' Update ReportDefaultsValues (change 'Sort By' to 'Sort'). Update SQL for several reports. Add Report Default for MAR. Add ReportDefaultValueOptions.
Update20080619
' Add PatientRef column to ElectronicClaims table. Drop PatientRefRef column from ElectronicClaims table. Delete ReportDefaultValues for Inpatient IV
Label.
Update20080620
' Add ShowIncompleteClinicalReviewReminders column to both Security and SecurityGroups tables (option for clinical review reminders on/off).
Update20080621
' Update Orders table, SET InventoryAreaRef=-1 WHERE Common Order has a ChargeMethod = 'Schedule'.
Here is a list of new report file changes
This release Includes the newest version of:
30-1.RPT file
-- File
date is 5/1/2009 11:50 AM.
Claim
Tax Summary.rpt file -- File
date is 12/29/2008 3:52 PM (See CSR: 238).
Return Receipt.rpt file -- File
date is 01/05/2008 1:35 PM (See CSR: 2668).
Shipping Label.RPT file -- File
date is 5/5/2009 2:56 PM.
Supply
Label.RPT file -- File
date is 5/6/2009 2:27 PM (See CSR: 480).
TPN
Label.RPTfile -- File
date is 4/28/2009 2:45 PM (See CSR:2850 and 2851).
Here is a list of new features and enhancements
CSR: 3076 -- Request: The Shipping Label needs to use 9102 as the shipping prefix for USPS. Resolution: The Shipping Label.RPT Crystal Reports file was modified. Now the new value is being used for the shipping prefix for USPS. In order for the new Shipping Label.rpt file to work correctly, the newest CRUFLNET.DLL file (dated 2/17/2009 5:41 PM) has been included in the release package, as well as the new font file (IDAutomationC128L.ttf). The new font will automatically be installed on each machine at the customer site during the workstation update.
CSR: 3056 -- Request: In related CSR: 3051, the NCPDP output was modified to not send the CX/CY fields if the NDCPatientID field of the related payer record has a value of 3. An additional 'do not send' item needs to be added to the dropdown option for the 'Patient ID' field under the 'E-Bill NCPDP' tab of the Payer screen. Selecting this new option should place a value of 3 into the Payer record's NDCPatientID column. This will allow Ascend-HI customers to more conveniently take advantage of this change. Resolution: Changed the Ascend-HI.exe program. In the Form_Load routine, added the 'Do Not Send' option (value of 3) to the 'Patient ID' field. This complements related CSR: 3051. Now, when a user edits a payer record, the 'Do Not Send' option is included as a dropdown option for the 'Patient ID' field under the 'E-Bill NCPDP' tab. When this value is selected for a payer, when a NCPDP eligibility transmission is made to that payer, the CX and CY fields are NOT included in the transmission.
CSR: 3015 -- Request: To provide NCPDP enhanced E1 support for Medicare Part D, the Processor Control Number in the NCPDP transmission needs to be changed from TROOPELIG to 2222222222. Resolution: Changed the AscendHI.DLL program. Modified the routine of the NCPDP class. Changed the hard-coded PCN from TROOPELIG to 2222222222.
CSR: 3004 -- Request: Clinical
Interventions information, stored in the Clinical Reviews table, does not
include who entered that information (EnteredByRef) nor when the record was
added to the database (EnterDate). For audit purposes, this
information needs to be added to the database and those fields should be
populated. Resolution:
Modified the Ascend-HI.exe program. Changed the Order screen code (SaveOrder routine) to pass the User’s SecurityRef to each of the
clinical Intervention functions. Also, changed the Other Medications screen code to include the user's ID in calls to the Order class' clinical check routines.
Now, when a clinical review record is created, the user's ID and date/time are recorded in the record.
CSR: 2940 -- Request: When a Clinical Document is locked, the Cut option (under the Edit drop-down Menu at the top of the Clinical Document) should be disabled or "grayed-out" the next time the document is opened. Currently, the user is still allowed to cut text out of the Clinical Document and save the document without the cut text in the document. This should not be allowed. Resolution: Changed the code in the Ascend-HI.exe program. In the ClinicalDocuments form's LoadChart routine, added an instruction to disable the 'Cut' item in the Edit menu when a clinical document is locked. This prevents users from cutting (deleting) any of the contents of the locked document.
CSR: 2874 -- Request: The state of California has changed its processor of electronic electronic Narcotics Export reports. The new processor company (Infinite Solutions) requires that the PHA segment contain the Address1, City and Zip values (currently, these fields are being left blank in the segment). Resolution: Modified the Ascend-HI.exe program. In the NarcoticsExport class, changed the PHA segment code to now include the Address1, State and Zip values. Note that this change applies ONLY if the state for which the report is being generated is California.
CSR:
2384 -- Request:
Add the loops, segments and fields to ANSI X12 Professional claims generated
for Medicare, when Medicare is the secondary payer (MSP). Resolution:
This resolution includes changes to the X12N class of AscendHI.DLL program, as well as adding the following columns to tables:
Claims.ClaimAdjustmentGroupCode
Claims.X12Loop2320CAS
Claims.X12Loop2300NTE02
Claims.ClaimOTAF
ClaimsItems.ClaimAdjustmentGroupCode
ClaimsItems.X12Loop2430CAS
PricingTemplates.ContractTypeCode
In the DLL, the X12N module code was changed to include/exclude the MSP-related loops, segments and fields of the ANSI X12 Professional output. In order for the new MSP-related items to be included in the X12 output,
a row must exist in the Defaults table with the values:
FacilityRef = 0
Section = X12
Field = AccessCOBLogic
DefaultValue = 1
If this row does NOT exist, then the claim is defaulted to NOT being a MSP claim, and therefore none of the MSP items are included in the X12 output.
Here is a list of things fixed
CSR: 3167 -- Request: When editing existing users, the change appears to be made when the user clicks Save. After closing and re-opening the Security screen, the change are not reflected on the screen. When adding a new user, the user appears to be added when the user clicks Save. After closing and re-opening the Security screen, the new user is not there. Also, when attempting to edit Security/Groups, the user gets runtime error 3265 "Item cannot be found in the collection corresponding to the requested name or ordinal." Resolution: Added Update20080620 to the UpdateHI.EXE program. This new update sequence adds the ShowIncompleteClinicalReviewReminders column to both the Security and SecurityGroups tables. This eliminates the 3265 error in the case where the user attempts to edit the Security Groups screen. It also eliminates the issue of the changes and additions to the users.
CSR: 3051 -- Request: New Mexico Medicaid specifications for NCPDP claim state that fields CY (patient ID) and CX (Patient ID Qualifier) are 'NA'. If this payer receives a claim with those fields included in the NCPDP transaction, the claim is rejected. Need an option or process whereby the user can select to not build these fields in the transaction record. Resolution: The AscendHI.DLL program was changed. Now, if CY does not contain a value, then CX will not be created. If the NDCPatientID column of the Payers table record for the payer of the claim has a value of 3 (three), then the CX and CY segment are not created. Please see related CSR: 3056 and related CSR: 2859.
CSR: 3120 -- Request: When the option "Only user who verified the order can make changes" is checked in the Options screen (under the Order Entry tab), and a pharmacist opens the Verify Orders window, If the pharmacist is not recorded as the 'Verified By' user, then the pharmacist will not be allowed to change or verify that order. Resolution: This CSR was resolved with the changes made in CSR: 3118.
CSR: 3118 -- Request: When refilling orders, the "Verified By" field is being populated with the last filled order's "verified by" user. The program should NOT enter in a verified by field value if the user that is refilling the order has the option set in Security that states "Orders must be verified". Resolution: The code has been changed in the Order screen (refillOrder routine) to no longer allow the refill to automatically allow a verified order to carry its verifier over to the refill. The refill is given a status according to the user’s security settings (option: ‘New orders will be inactive prior to verification’).
CSR: 3116 -- Request: For a MSP claim (where Medicare is the secondary payer), in Loop 2000B/segment SBR01, the Payer is being designated as the Primary Payer (with a value of 'P'). This is incorrect. The 2000B loop is used "To record information specific to the primary insured and the insurance carrier." The insured would be the patient and the carrier the payer. The the SBR01 field of the the SBR segment in the 2000B Loop should be populated with a "S" and not a "P" when the claim is a MSP claim. Resolution: Modified the AscendHI.DLL program. In the X12N class, changed the Add2000BLoop routine to place an 'S' (Secondary payer) into the SBR01 field of the SBR segment when the claim is a MSP claim. Now, when a MSP claim is generated, the SBR01 field will always have a value of 'S'. If the claim is NOT a MSP claim, the value of 'P' (Primary payer) is still placed into the SBR01 field.
CSR: 3115 -- Request: When
creating a X12 batch, the 2330A Loop (Other Subscriber Name) is required
when the 2320 Loop (Other Subscriber
Information) is used. Otherwise, the 2330A Loop is not used. Resolution:
Changed the AscendHI.DLL program. In the X12N module, added the Add2330ALoop
routine for Medicare as Secondary Payer when the 2320 Loop is
included. Now, when the X12 output is being generated, if the claim
being billed is a Medicare as Secondary Payer type, and the 2320 Loop is
included, the 2330A loop will also be included in the output. If the
claim being billed is NOT a Medicare as Secondary Payer type, the 2320 Loop
will NOT be included, and the 2330A loop will also NOT be included in the
output.
CSR: 3114 -- Request: The
X12/837P specifications for Loop 2300 CLM02 states "CLM02 is the total
amount of all submitted charges of service segments for this claim."
The software is currently populating this segement with the BilledAmount
field from the Claims table (which is the total amount of the service lines
MINUS any reciepts and adjustments made to the claim). According to the
specifications, the software needs to sum only charged lines
(ClaimsItems.TotalPrice) and populate this value into the CLM02 field of the
CLM segment of the 2300 Loop. Resolution: Changed the
AscendHI.DLL program. In the Add2300Loop routine, added code to sum the
TotalPrice value of all of the 'charged' items of the order. If the total is
zero (or a blank value), then a 'potential problem' ("Total of Line
item prices equals zero.") is added to the list of potential problems.
CSR: 3104 -- Request: When more than one intrinsic is found in an order, the TPN Label prints only the first amount field on the first column of the intrinsics information. Resolution: The TPN Label.RPT Crystal Reports file was modified. The "Can Grow" option for the field in the report file is now 'checked' for field Intrinsics1Amount, so the amount will print on the label for all of the intrinsics.
CSR: 3075 -- Request: Currently the Prior Authorization number prints in the 'TAR Control No.' field on the 30-1 claim form only when the NCPDP Product Qualifier is NDC (value 03). Most supplies do not have NDC numbers, but when the supply order has a prior authorization assigned to it, that Prior Authorization number must print in the 'TAR Control No.' field on the 30-1 form. Need to allow printing of Prior Auth number in the 'TAR Control No.' field regardless of the value in Product Qualifier field. Resolution: Modified the 30-1.RPT Crystal Reports file. Changed the of the Insured1PriorAuthorization field ('Tar Control No.' field). Additional code was added to the 'Suppress' (Object Visibility) property of the field. Now, the prior authorization value will print when the NCPDP Product Qualifier = 3 OR the NCPDP Product Qualifier = 0 (0 is the qualifier used for supplies). In this way, when a supply item or an item with an NDC is indicated by the qualifier value, the Insured1PriorAuthorization field will be populated.
CSR: 3020 -- Request: In the Financial Notes tab; When Right-Clicking on a Financial Note and selecting Print, the program brings up a Printer selection window to pick the printer to which the user would like the Financial Note to print. If the user selects a printer other than the Windows OS default printer, the Financial Note prints to that printer, but this also changes the Windows OS default printer to the selected printer. The selected printer should not be automatically set as the Windows OS default printer. Resolution: Changed the Ascend-HI.exe program. In the Profile screen's mnuFinancialNotes_Click routine, added code to reset the default printer to what it was before the user selected another printer for the print job. NOTE: If the user selected a printer different than the Windows default printer for the print job, there is an additional delay of several seconds while the Windows default printer is reset to its original value after the print job has been sent to the printer.
CSR: 2995 -- Request: The following error is generated four times by the UpdateHI.AddReportDefault function when updating from Ascend-HI version 2.14.111 to 2.14.113: "Object variable or With block variable not set." Resolution: Changed the UpdateHI.exe program. In the Common.AddReportDefault subroutine, changed the ParameterNameValue parameter type to a String from a Variant. This eliminates the errors that were generated when Updates2008.Update20080504 called this routine with a 'Nothing' value. Also changed all other calls to this routine that used 'Nothing', so they now call the routine with "" instead of 'Nothing'.
CSR: 2943 -- Request: When
Admitting a new patient, there are rare cases where the new patient record
does not have a Patient ID number assigned. This is true even if the
software is setup to automatically populate the Patient ID (Patient ID
number in the Options, Admissions tab is populated with a valid
value). Resolution: Changed the SavePatient routine of
the Patient screen of the Ascend-HI.exe program.
Now, when a user ‘admits’ a new patient (Patients->New Patient menu
path):
If there IS a valid entry in the Defaults table for the PatientIdCounter (a
numeric value), then a Patient ID is generated as expected, and the
data entry box for Patient ID displays the Patient ID, but is disabled,
thereby NOT allowing the user to add/edit the value.
If there is a prefix value, then the new Patient ID will start with the
prefix, followed by the ID number.
If there is a suffix value, then the new ID number is also followed by the
suffix value.
If there are no entries or all blank entries in the Defaults table for the
PatientIdCounter, PatientIdPrefix and PatientIdSuffix, then a blank Patient
ID is generated as expected, and the data entry box for Patient ID is
enabled, allowing the user to add/edit the value.
If the PatientIdCounter value IS blank, and the entries in the Defaults
table for the PatientIdPrefix or PatientIdSuffix are NOT blank, then a
Patient ID is generated (made up of the Prefix and/or suffix), and the
data entry box for Patient ID is enabled, allowing the user to add/edit the
value.
If there IS a valid entry in the PatientIdCounter and/or PatientIdPrefix
and/or PatientIdSuffix values in the Defaults table, and after the new
patient record is saved there is still no Patient ID, an error is
logged into the Errors table, for example:
"Module:
frmPatient; Procedure: SavePatient New Patient record was saved without a
Patient ID. PatientRef: 74 3/31/2009 11:39:00 AM"
Also, the user is
warned in a popup message that the Patient ID was not created for the new
patient record.
In this initial popup message, the user is provided the opportunity to retry
auto-generating a new Patient ID.
A series of popup messages follows the initial message, depending on the
user’s response to this message and the success of the retry (if requested
by the user).
If the user selects ‘Retry’, and the Patient ID is STILL not generated,
then a message appears stating so, and reminding the user to manually enter
the new patient’s unique Patient ID value.
If the user selects ‘retry’ to the first message, and the Patient ID is
successfully generated, then a message appears stating so.
If the user selects ‘Cancel’ to the first message instead of retry, and
Patient ID not generated then a message appears reminding the user to
manually enter the new patient’s unique Patient ID value.
CSR: 2924 -- Request: When a user
is editing a discontinued Other Medication type order, an error 5 (Invalid
Procedure Call) may occur in certain conditions, and is reported by the
rmProfile_mnuOrders.Click routine. Resolution: In an
attempt to narrow down the routine that is actually generating this error,
error checking was added to certain routines of the Ascend-HI.exe program,
these routines include:
Common module – PickItem
Common module – MaskDate
frmOtherMedicationOrder – LoadOrder
frmOtherMedicationOrder – LoadDrugList
Now, when a customer experiences an error when attempting to view a
discontinued Other Medication order, the error should more precicely point
out the routine that is generating the error. This information will
allow improved troubleshooting results.
CSR: 2918 -- Request: The "County" field in the Patient Admission Information screen has a list of the counties listed per state when entering or editing patients. For the state of LA, the parish of "Vermon" is misspelled. It should be "Vernon". Resolution: Corrected the spelling of "Vernon" parish for Louisiana (LA) in the Counties routine of the Lookups.bas module of the Ascend-HI.exe program.
CSR: 2890 -- Request: When printing Clinical Documents, Ascend-HI fails to send the print job to the selected printer, always using the default printer in the Print window instead. Resolution: Changed the Ascend-HI.exe program's Profile screen code. In the mnuClinicalDocuments_Click routine, added code that remembers the Windows printer default setting (before presenting the printer selection dialog to the user) so the software can temporarily use the clsPrinterDefaults.WindowsDefaultPrinter value to set the printer selection using the 'cmdlg' object. After using the clsPrinterDefaults.WindowsDefaultPrinter value as the selected printer, the default value is reset to its original setting. Note that this reset only occurs if the user had selected a printer other than the default. Since the reset process takes up to 15 seconds, this saves time for the user.
CSR: 2872 -- Request: The 'Outpatient Label' was added to Ascend via CSR 1973. This label is showing up in the list of Labels/Forms for an order. This label is not intended to work in Ascend-HI. Remove this report file from the AscendHI update release package. Also delete any instances of the file on the Ascend-HI customer workstations and the server's 'share' directory. Resolution: Removed the Outpatient label Crystal Reports file from the Ascend-HI distribution directory. This prevents the report file from being redistributed. Added the update sequence 20080612 to cause the file to be removed from the customer machines in case it has been introduced. Finally, In the UpdateHI.exe program, modified the Common module's DeleteReportFile routine. Added code to handle 'labels' as well as reports.
CSR: 2863 -- Request: When performing a TPN Calculation, if the total nitrogen instrinsic value / 1000 is less than 1, then a division by zero error will occur. Resolution: Changed the Ascend-HI.exe program. In the LoadTPNOrder routine of the Order screen, changed the calculation to eliminate the possibility of a division by zero occurring.
CSR: 2859 -- Request: New Mexico Medicaid specs for NCPDP claim states that fields CY (patient ID) and CX (Patient ID Qualifier) are 'NA'. Claims transmitted with those fields in the NCPDP transaction are rejected. An option or process is needed whereby the user can select to not build these fields in the transaction record. Resolution: The AscendHI.DLL program was changed. Now, if CY does not contain a value, then CX will not be created. If the NDCPatientID column of the Payers table record for the payer of the claim has a value of 3 (three), then the CX and CY segment are not created. Please see related CSR: 3051 and 3056.
CSR: 2851 -- Request: The TPN Data Sheet is not rounding correctly on the 'Per' field. The field is currently rounding to the first decimal place instead of the second. The report currently displays two decimal places. The 'Per' value on the TPN Data Sheet should be rounded to the second decimal place. Resolution: In the 'TPN Data Sheet.rpt' file, changed the way that the 'Per' value (@ItemVolume field) is displayed. Now, the value is rounded to two decimal places. If there are trailing zeroes past the first decimal place, then those zeroes are not displayed. For example, if the value is 3.4450, and the rounding results in 3.4500, the number will be displayed as '3.45'. However, if the value is 1.0 after rounding, then the number will be displayed as '1.0'.
CSR: 2850 -- Request: The TPN Label is not rounding correctly on the 'Per' field. The field is currently rounding to the first decimal place instead of the second. The report currently displays two decimal places. The 'Per' value on the label should be rounded to the second decimal place. Resolution: In the 'TPN Label.rpt' file, changed the way that the 'Per' value (@Per field) is displayed. Now, the value is rounded to two decimal places. If there are trailing zeroes past the first decimal place, then those zeroes are not displayed. For example, if the value is 3.4450, and the rounding results in 3.4500, the number will be displayed as '3.45'. However, if the value is 1.0 after rounding, then the number will be displayed as '1.0'.
CSR: 2827 -- Request: When
updating to Ascend-HI version 2.14.111, during the updating of the database
the following error is generated.
"UpdateRoutes - Either BOF or EOF is True, or the current record has
been deleted. Requested operation requires a current record."
After clicking on the error, the update continued without issue and the user
is able to get into Ascend-HI and work with no problems. Resolution:
Changed the UpdateRoutes subroutine in the Common module of the UpdateHI.exe program. To avoid EOF()/BOF() errors, added an IF construct, and changed Do constructs to 'Do While Not EOF()' instead of 'Do Until EOF()'.
CSR: 2825 -- Request: Since update to version 2.14.110, there is a problem with the edit or refill of an order that started as a Common Order. If the user alters the sequence of items in the Order Item list of the order screen and saves the order, when the order is next edited or refilled, the sequence of items in Order Item list is changed in the display from what the user had set. This affects sequence in which the order items are printed on the Labels and forms printed for the order. Resolution: Modified the Ascend-HI.exe program. In the Order screen code, changed the lvwItems control to no longer be alphabetically sorted. Now, when a user creates or edits an order, the items in the order are displayed according to the OrdersItems.Rank value of each item. When the user manually changes the rank by clicking on the UP or DOWN buttons to rearrange the items in the order, the new rank is properly saved. Future access to the order's screen will always show the items in order of their 'rank'. This is also true for the labels/forms generated for the order (the items are printed in order of their rank), with the one exception being the Invoice. The invoice prints the order items in the sequence in which they appear in the database.
CSR: 2786 -- Request: When performing an update to Ascend-HI version 2.14.111, an error occurs (Invalid Use of NULL). The location where the error is occuring is in the Common.UpdateClinicalReviewTypes routine of the UpdateHI.exe program. Resolution: Changed the Common.UpdateClinicalReviewTypes routine of the UpdateHI.exe program. Changed the call to the Common.GetClinicalReviewTypeRef routine to pass a blank string if a null value is returned from the database query used to gather the Types of ClinicalReviews found in the ClinicalReviews table. Thereby, the 'Invalid Use of NULL' error should no longer occur.
CSR: 2783 -- Request: When
calculating a TPN order on a refilled TPN (when clicking
"Calculate" on the TPN tab in the order), some line items in the
TPN are being incorrectly incremented. The calculator rounds the 'Per'
value, and then uses the rounded value instead of the original ordered value
in the calculation. Resolution: Changed the LoadTPNOrder
subroutine of the Ascend-HI.exe program's Order screen. Removed the
statement:
xDoseQty.Per = RoundUp(xDoseQty.Per, 2)
Also changed calculations performed in the LoadOrderItem routine of the Item
screen.
With these changes, the rounded value is not included in the calculation.
CSR: 2737 -- Request: When parsing an X12 transmission file, the parsing code mis-identifies the 1000A Loop as the 1000B Loop, and also mis-identifies the 1000B Loop as the 1000A Loop. Resolution: Modified the code in the AscendHI.dll program. In the ParseX12Transmission function of the X12N class, changed the identifying values of the 1000A and 1000B loops so that they are now properly identified in parsed output document.
CSR: 2728 -- Request: The order save process querys the Order table unnecessarily on new orders. The Order.Save routine calls the InventoryQuantityAction function before a new order is saved. In the case of a not-yet-saved new order, the OrderRef value is still zero. When the InventoryQuantityAction function is called, it wastes time querying the Orders table looking for a record that does not yet exist. To reduce the number of database transactions, the InventoryQuantityAction function needs to skip the query against the Orders table when a new order (OrderRef = 0) is being saved. Resolution: Changed the Order class in the AscendHI.DLL program. The Order.Save routine is now calling the InventoryQuantityAction function with the OrderRef value. If the OrderRef value is zero, then the Orders table is not queried during the InventoryQuantityAction function's operation.
CSR: 2701 -- Request: The
Unbilled Orders report is including both 'Other Medication' type orders and
orders with a status of 'On Hold'. Orders of this type or status are not
billable, and therefore should not be on the report. Resolution:
Changed the report SQL stored in the SQLSources table for the Unbilled Orders report. The new SQL filters out Order Types with a Category of 6 (Other Medications). Also, it now filters out orders that have a status of "H" (On Hold).
This required changes to the AddOrUpdateSQLSource routine for the SELECT and WHERE clauses of the Unbilled Orders report. It also required adding Update Sequence 20080422 to call the AddOrUpdateSQLSource routine to make the changes.
Finally, for Ascend-HI, the new 'WHERE' clause of the SQL (that filters out
the unwanted records) was included in the Reports screen's ReportCriteria
function.
CSR: 2668 -- Request: The header field on the Return Receipt form is of insufficient "height" to print the phone number(s)for the facility on a 2nd line in the header area. Resolution: The Crystal Report file was changed to expand the area in which the 2nd line of the Facility information can print. Now, this 2nd line is no longer cut off. Also, limited to 30 the number of lines to which the Shipping Notes can grow.
CSR: 2623 -- Request: On a co-pay claim where credits have been applied to the original claim, if the co- pay claim has an allowable balance, the balance, in some cases, does not show correctly in the lower right side of the claims edit screen. Resolution: In the Ascend-HI.exe program Changed the code in the claim screen to properly display the correct balance if the co-pay claim has a balance. Removed the receipts and adjustments values from the co-pay claim as it is being created. These values were picked up because the co-pay claim is a duplicate of the original, and there is at least one receipt posted against the original claim when a copay claim is created. Also, now the totals display to correctly includes the 'Credits posted to claim ...' row in the calculations.
CSR: 2384 -- Request: When sending ANSI X12 Professional claims to Medicare, when Medicare is the Secondary payer (MSP), The Contract Type Code is only one digit long in the CN1 segment (CN101 element) in both the 2300 and 2400 loops. The ANSI specifications state that this must be a 2-digit code. Also, the AMT01 value for the Primary Payer Allowed Amount in the 2320 loop should be a 'B6' as stated in the ANSI specification, instead of 'AAE', as is currently incorrectly being used. Resolution: Modified the AscendHI.DLL program. In the X12N class, changed the code that passes the Contract Type Code value to the routine that builds the CN1 segment. Now, if the stored value is only one digit, a leading zero is prefixed to the number so that it is 2-digits long (i.e., 6 becomes 06). Additionally, changed the AMT01 value for the Primary Payer Allowed Amount in the 2320 loop to a 'B6' as specified, instead of 'AAE'.
CSR: 2293 -- Request: An error 3704 is generated when attempting to run the Physicians License Expiration report. Resolution: The Physician License Expiration report was removed from the Ascend-HI update packages August of 2006. The report file was accidentally re-introduced to the package with the release of Ascend-HI version 2.14.98. Once again, the report was removed from the distribution directory for the Ascend-HI product and later accidentally reintroduced to the directory. A new update sequence (20080507) has been added to the UpdateHI.exe program to remove the 'Physician License Expiration.rpt' file from the customer machines.
CSR: 1477 -- Request: Technicians
whose orders must be verified are allowed to refill orders and have those
refills marked as Active. However, if they cancel a refill and answer
"Yes" to question about reactivating the previous fill, that
(previous) fill is marked Inactive, not Active, and shows back up in the
Verification screen. Change the process so that fills reactivated via the
Cancel process are set to Active status,and not the Inactive. Resolution:
Changed the Ascend.EXE program. Added Order screen code in the RefillOrder routine. Added an IF construct to see if the previous fill had already been verified. If so, and the current user must have orders verified and made Inactive, then set the status of the refill to Active. If there is not a verifier on the original order, and the current user must have orders verified and made Inactive, then set the status of the refill to Inactive.
Also changed the AscendHI.DLL program to act this way when an order is Un-discontinued.
CSR: 609 -- Request: Need a general Order Entry option under the 'Orders' tab of the Options screen that makes refills NOT need to be re-verified. Resolution: Please see related CSR: 3118.
CSR: 480 -- Request: Supply Label should suppress printing of any items with zero quantity. If an item has a zero quantity (essentially not being sent with this current fill of supply items), do not display this item on the Supply Label. Resolution: Modified the 'Supply Label.RPT' Crystal Reports file. Changed the item detail suppression logic to suppress printing the item if the item quantity is not greater than zero.
CSR: 238 -- Request: The 'Grand
Total' line on the Claim Tax Summary report does not sum all Payer
totals. Resolution: The Crystal Reports file for the
Claim Tax Summary report was modified. Now, the totals rows properly sum the
values in each column.
NOTE: While this report now properly displays the
totals and tax amounts based on the ClaimsItems table values, it is possible
that, after a tax rate is changed, or a new tax rate is added for a state or
zip code (using the Options screen), the individual claim item rows will
print the new tax rate, but the tax amount column will contain the tax value
initially stored in the claim item's record, even if there was a different
tax rate in effect when the claim was created. This is because, when
the claim is initially created, the tax rates in effect at that time
dictated what tax value was stored in the claim item's row in the
ClaimsItems table. When a tax rate is changed or added, the software
does not propagate the change backwards into older claims.
First Databank Updates
To determine the date of the First Databank files currently installed into your database, follow the steps of:
1. Click on the HELP option of
the main menu of the Ascend-HI screen. From the pull-down menu that
appears, Select the 'About Ascend-HI' option to activate the ABOUT screen.
2. On the upper right-hand side of the
ABOUT screen, the date is displayed as: First Databank
Current as
of 04-01-2010
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