ASCEND-HI -- CURRENT VERSION RELEASE NOTES
Version 2.14.107 (11/14/2008 )
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.2.94
UpdateHI.EXE - Version 1.1.838 (20080414 <-- This is the last sequential internal update performed by this version)
This version was repackaged 12/08/2008 1:36 PM with the latest First Databank files.
Here is a list of new database changes
Each new update sequence in the UpdateHI.exe program is listed with a brief note about what it accomplishes. Note that some sequence numbers are skipped.
Update20080309 '
Add NDCQuantity to Inventory
Update20080310 '
Change SQL for OrderWithDeliveryPatientAddress, OrderWithDeliveryPatientAddress, Unbilled Orders, Charges.
Update20080311 ' CSR: 2381 -- Change report SQL for the Patient Account Status report.
Update20080312 '
Update the Charges report to include NDC Quantity and Billing Units
Update20080313 '
Database Lab Changes.
Update20080314 '
Update MAR for AHFS Code and Physician Orders
Update20080315 ' Remove unnecessary fields from OrdersItems table and add new fields
Update20080316 ' Add column TimesDefinedDuringOrderEntry (Bit) to SigCodes table.
Update20080317 ' Add report Mar Section criteria.
Update20080318 ' Set facility default 'Print Nurse Instructions' to "1" for MAR report.
Update20080319 ' CREATE TABLE LabOrdersItems. Add LabOrderNumber column (Varchar(20) to LabOrders table.
Update20080320 ' Update Inventory Adjustments and Transfers report
Update20080321 ' Create new Outpatient Oral Prescription category
Update20080324 ' CSR: 2446
-- Add 'Synagis Tracking' Clinical Document with Qs&As.
Update20080325 ' Add Patients.StateId field
Update20080326 ' Add QuantityOnHand criteria for "Inventory" report filtering.
Update20080327 ' Add Column "FacilityRef" to PatientAddresses table. Added ShippingAddresses criteria for OptionsAdmissionTables SQL.
Update20080328 ' CREATE TABLE OrdersScheduleTimesNotes. Change OrdersScheduleTimes "Quantity" column type to "REAL". Add Column "FacilityRef" to LookupValues table.
Update20080329 ' CSR: 1445
-- Remove Claims.UB04Box4 column; Remove Payers.UB04Box4 column; Add Claims.BillFrequency, Suppliers.ANSI837TypeOfFacility and Suppliers.ANSI837BillClassification columns.
Update20080330 ' CSR: 1445
-- Add entries to LookupTables and LookupValues tables for "BillFrequency", "ANSI837BillClassification", "ANSI837TypeOfFacility" value lists.
Update20080401 ' Add USPS Customer Id for new Shipping Label
Update20080402
' Add lookup values for the Food/Drug Severity Levels. Add defaults for the Inpatient IV Label.
Update20080403 ' Change lookup values for the NCPDP Reason For Service and NCPDP Professional Service.
Update20080404 ' Change the SELECT SQL for the Patient Account Status, undoing changes of Update20080311.
Update20080405 ' Update SQL source for "Batch IV" and "Charges".
Update20080406 ' CSR: 2491 -- Add ProductCode and ProductQualifier columns to the InventoryPayerUnits table.
Update20080407 ' Change SQL for Prescription Log reports. Add Report Criteria for "OrderTypes" and "ClinicalDocuments".
Update20080408 ' CSR: 2520 -- Add new 'Place of Service?' Q & A (Home, Office) for Synagis Tracking clinical document.
Update20080409 ' CSR: 2545 -- Delete the Inpatient IV Label report file from the Crystal\Orders folder. This Report is only for Ascend.
Update20080410 ' CSR: 2539 -- Add Taxonomy and TaxonomyQualifier columns to the Doctors table.
Update20080411
' CSR: 2539 -- Add Taxonomy and TaxonomyQualifier columns to the Doctors table.
Update20080412 ' Added column "NDCAddDateToInsuredId" as "BIT" to the "Payers" table.
Update20080413 ' CSR: 2522 -- Update the SELECT SQL for ReportName = "ClaimLineItem" (used by the 30-1 report).
Update20080414 ' CSR: 2545 -- Delete the Inpatient IV Label report file from the Crystal\Orders folder. This Report is only for Ascend.
Here is a list of new report file changes
This release Includes the newest version of:
Clinical Document.rpt -- File
date is 10/23/2008
3:44 PM (See CSRs 2395 and 2546).
Factor
Label.rpt -- File
date is 11/06/2008 9:51 AM (See CSR 2582).
HCFA 1500 (v1.3).rpt -- File date is 10/31/2008
4:46 PM (See CSR: 2416).
Order Label.rpt
Patient Account Status.rpt
Shipping Label.rpt -- New.
Syringe
Label.rpt -- File
date is 11/12/2008 4:53 PM (See CSR 2589).
TPN
Label.rpt -- File date is 10/23/2008 10:22AM (See CSR:
2428).
UB-04.rpt -- File date is 10/28/2008 10:15 AM (See
CSR 2459).
REMOVED: Inpatient IV Label.rpt
-- This is not a valid report for Ascend-HI.
Here is a list of new features and enhancements
CSR: 2540 -- Request: RI Medical Assistance requires the Group Name to be populated in Box 61 of the UB04 form. The requirements definition from the RI Medical Assistance requirements document for Box 61 of the UB-04 form state:"Enter the name of insured's other group health coverage, if applicable." Resolution: Box 61 of the UB-04 form is populated with the value found in the 'Insurance Plan' field of the Claim screen under the 'Primary Insurance', Secondary Insurance' or 'Tertiary Insurance' tab (depending on whether the entry is being made on row a, b or c, respectively, under the Box 61 column header).
CSR:
2539 -- Request: RI
Medicaid requires Box 81cc to be populated with a qualifier of
"B3" and taxonomy code when there is an NPI entered in Box 76-79.
Following is the requirement definition from the RI Medicaid requirements
document for Box 81cc the UB-04 form:
"Enter B3 in the qualifier if locations 76-79 contain an NPI. Enter the
corresponding provider taxonomy of provider NPI’s entered in locations
76a – 81CCa
77b – 81CCb
78c – 81CCc
79d – 81CCd"
Resolution:
Modified the UB-04.RPT Crystal Reports file to populate Box 81cc with the Taxonomy Code of the Referring doctor (from the claim record) whose NPI appears in Box 76. If the Taxonomy Code is not blank, then the qualifier "B3" is printed in the small box to the left of the Taxonomy
Code.
In the UpdateHI.exe program, added Update Sequence 20080410 to add the TaxonomyCode column (10 characters) and TaxonomyCodeQualifier (3 characters) to the Doctors table. In the Doctors screen, added text boxes for allowing the user to view/edit the new fields. In the AscendHI.DLL program, modified the Doctor class to include these two new fields.
CSR:
2538 -- Request: RI
Medicaid requires Box 57 of the UB-04 form to have the Taxonomy Code
populated if there is an NPI in Box 56.
Following
is the requirement
definition from the RI Medicaid requirements document for Box 57 of the
UB-04 form: "Taxonomy
must be entered if NPI is entered in
location 56. This id must be entered in line A,B,C that corresponds to the
line in which the “RI Medicaid” payer information is entered in locator
50."
Resolution:
The UB-04 populates Box 57 with the Taxonomy Code of the facility to which the patient is assigned. When a taxonomy code is present in the facility record, this works. In the Facilities screen, added the ability for the user to view and change the facility's taxonomy code. Also changed the Facilities class in the AscendHI.dll program to add the ability to get and set the Taxonomy Code
attribute.
CSR:
2527 -- Request: For both a
Clinical Document or Financial Note on any patient profile, when the
document is locked, the user is still able to access the locked Document and
click on Edit, Paste (or use the ctrl-v or Shift-Ins) to paste into the
document whatever is in the PC's clipboard.
When a clinical document or Financial note is locked, the "Paste"
option under the Edit menu of the document should be grayed-out (disabled),
and the ability to use standard Windows functions to paste into the document
should also be disabled.
Resolution:
When a Clinical
Document/Financial Note is locked, the Paste option on the Edit menu of the Clinical Document/Financial
Note screen is now disabled to prevent pasting into the document. This change was made in the ClinicalDocument form, in the LoadChart routine. The
change also disables standard Windows functions for pasting content into the
document.
CSR: 2524 -- Request: The Shipping Label needs to apply the label margins that are set in the Options screen under the 'Printing' tab. Resolution: The Printer Defaults class of the Ascend-HI.exe program was changed. Added the Shipping Label to the list of labels that apply the margins set for labels in the Options screen. Now, the Shipping Label does apply those default label margins.
CSR: 2516 -- Request: Need utility to parse ANSI X12 transmission batch text. Resolution: In the AscendHI.dll program, changed the X12N module. Added a routine (ParseX12Transmission) to parse the text of an ANSI X12 text from a transmit batch. In the Ascend-HI.exe program, changed the Profile screen's menu path (Financials->E-Bill->837P) to (Financials->E-Bill->View Parsed 837P) and this menu item now calls the new routine in the DLL that parses the text before it is displayed in the MS Notepad program.
CSR:
2498 -- Request: Additional
fields are needed for the Narcotics Data Export functionality to accommodate
the state of Louisiana narcotics reporting (per the specifications of the
Louisiana Board of Pharmacy for Narcotics reporting).
The three additional fields are:
Customer License Number - positions 26-45
Zip-Code - Positions 46-48
Birth-Date - Positions 46-56
Resolution:
Date of birth is already being sent.
The Zip code data was added for the state of LA.
Customer License Number ("State Id") has been added to the database and to the patient edit screen. The StateId field is now used to populate the Customer
License Number (positions 26-45) of the export when the state of the issuing facility is Louisiana.
CSR: 2445 -- Request: Change the
design of how the UB-04 form's Box 4 data is stored and edited.
The character-mapped UB04Box4 column of the Claims table needs to be
removed, and replaced with a new column in the Claims table 'BillFrequency'
as a Varchar(1) that contains only the 4th digit ('Frequency') of the UB-04
form's Box 4 value. All code referencing the 4th character of the
removed UB04Box4 column must be changed to reference the new
Claims.BillFrequency column.
A new column '837TypeOfFacility' as a Varchar(1) also needs to be added to
the Suppliers (providers) table to hold the 2nd digit ('Type of Facility')
of the UB-04 form's Box 4 value. All code referencing the 2nd character of
the removed UB04Box4 column must be changed to reference the new
Suppliers.837TypeOfFacility column.
Additionally, a new column '837BillClassification' as a Varchar(1) needs to
be added to the Suppliers (providers) table to hold the 3rd digit ('Type of
Facility') of the UB-04 form's Box 4 value. All code referencing the 3rd
character of the removed UB04Box4 column must be changed to reference the
new Suppliers.837BillClassification column.
The design of the Payers screen of the Ascend-HI.exe program needs to be
changed to remove (under the UB-04/UB-92 tab) the Box 4 default controls.
The Claim class of the AscendHI.DLL program must also be changed to accommodate
the removal of the UB04Box4 column from, and the addition of the
BillFrequency column to, the Claims table.
The design of the Providers screen of the Ascend-HI.exe program also needs
to be changed to add the two new controls. The first control will be for
viewing/editing the Suppliers.837TypeOfFacility column. The second control
will be for viewing/editing the Suppliers.837BillClassification column. The
Supplier class of the AscendHI.dll program must be changed to accommodate these two new database fields.
Resolution: The Payers.UB04Box4 column
was removed.
Added a new column 'BillFrequency' to the Claims table. This new
column contains only the 4th digit ('Frequency') of the UB-04 form's Box 4
value. The Claim class of the AscendHI.DLL program was changed to accommodate
the removal of the UB04Box4 column from, and the addition of the
BillFrequency column to, the Claims table.
On the Claim screen, under the ‘Other’ tab, the 1st, 2nd and 3rd digits
of UB-04 Box 4 are not displayed. Only the 4th digit (Frequency) is displayed
and editable. Under the line item-level tab, the value of the UB-04
Box 4 content is not displayed.
Added ’ANSI837TypeOfFacility’ column to Suppliers table.
Added ‘ANSI837BillClassification’ column to Suppliers table.
All code referencing the removed UB04Box4 column was changed to instead
reference the new ‘BillFrequency’, Suppliers.ANSI837TypeOfFacility and
Suppliers.ANSI837BillClassification columns.
Now, when a claim is initially created, only the 4th digit of the UB-04 Box
4 field will be stored in the claim record, and populated with a default of
“1”. After the claim is initially created, the user can
view/change the 4th digit (‘Frequency’) of UB-04 Box 4 at the claim
level (under the 'Other' tab of the Claim screen).
The Payers screen of the Ascend-HI.exe program was modified. Removed
the Box 4 default controls (under the UB-04/UB-92 tab).
The Payers class in the AscendHI.dll program was modified to remove
references to the UB04Box4 column of the Payers table. Removed the
UB04Box4 attribute from the Payers class.
Changed the SQL in frmPrintOuts for the UB-04 report in the Labels.frm
(frmPrintOuts)/ReportRecordSource routine. The new SQL passes the new claims
and Suppliers columns to the Crystal Reports engine (and no longer includes
the UB04Box4 field).
Changed the UB-04.rpt Crystal Reports file. Now, when a claim’s UB-04 form
is being generated:
The 2nd digit of the UB-04 Box 4 field will be derived from the provider
record’s ANSI837TypeOfFacility column.
The 3rd digit of the UB-04 Box 4 field will be derived from the provider
record’s ANSI837BillClassification column.
The 4th digit of the UB-04 Box 4 field will be derived from the claim
record’s BillFrequency column.
The X12N Module of AscendHI.dll program was modified. The CLM segment
of the 2300 loop no longer references the UB04Box4 column for the 5th field
in the segment. Now, this data is retrieved from the Claims.BillFrequency
column. Added X12 batch warnings for Medicare resubmission information
(see also CSR: 2405). Now, if HCFAMedicaidOriginal is NOT blank, and the claim’s BillFrequency is not
7, then the error is "CLM05.03 Frequency code <> 7”. If
HCFAMedicaidOriginal is blank, and the claim’s BillFrequency is 7, then
the error is "Original Claim ICN/DCN for resubmission".
The values used in the option lists presented for each of the digits of the
UB-04 Box 4 value are now stored in the LookupTables and LookupTableValues
tables as follows:
ANSI837TypeOfFacility (for UB-04 Form, Box 4, Digit 2)
"1 - Hospital"
"2 - Skilled Nursing"
"3 - Home health agency"
"7 - Clinic (RHC, FQHC, RDC)”
"8 - Special facility"
ANSI837BillClassification (for UB-04 Form, Box 4, Digit 3)
"1 - Inpatient (including Medicare Part A)”
"2 - Inpatient (Medicare Part B only)”
"3 - Outpatient"
"4 - Other (for hospital-referenced diagnostic services, for example,
laboratories and X-rays)”
"7 - Intermediate care"
"1 - Rural health (for Clinics/Special Facilities only)"
"2 - Hospital-based or independent RDC (for Clinics/Special Facilities
only)"
"3 - Free standing (for Clinics/Special Facilities only)"
"5 - Comprehensive outpatient rehabilitation facility (CORF) (for
Clinics/Special Facilities only)"
BillFrequency (for UB-04 Form, Box 4, Digit 4; ANSI X12 Loop 2300, CLM
segment)
"0 - Nonpayment/zero claim"
"1 - Admit through discharge"
"2 - Interim–first claim"
"3 - Interim–continuing claim"
"4 - Interim–last claim"
"5 - Late charges–only claim"
"6 - Adjustment of prior claim"
"7 - Replacement of prior claim"
Added Lookups for “BillFrequency”, “ANSI837TypeOfFacility” and
“ANSI837BillClassification” in the DisconnectedRecordsets module/
FillComboBox routine. These lookups now each indicate that the list
values are stored in the LookupValues table. These lookups are now used when
populating dropdown controls for:
BillFrequency – on Claim screen, under the ‘Other’ tab.
Facility Type – on the Providers screen.
Bill Classification – on the Providers screen.
CSR: 2439 -- Request: In the AscendHI.dll program, the ANSI X12 AddClaim subroutine currently contains the code that generates non-837P format text (in HCFA-1500 format). This code is run only if the Electronic Receiver's format setting is not ANSI X12 Professional. This non-837P code needs to removed from the AddClaim subroutine and moved into its own routine, and the new routine should be called by the AddClaim subroutine. This makes the code easier to read, and keeps the AddClaim subroutine down to a reasonable size. Resolution: In the AscendHI.dll program, the ANSI X12 AddClaim subroutine no longer contains the code that generates non-837P format text (in HCFA-1500 format). This non-837P code has been removed from the AddClaim subroutine and moved into its own routine (AddHCFA1500ClaimText), and the new routine is now called by the AddClaim subroutine if the Electronic Receiver's format (version) setting is HCFA-1500.
CSR: 2436 -- Request: In the Patient screen, under the Insurance tab, when the user double-clicks on an insurance list item, the screen for editing the selected patient insurance record should pop up and allow the user to edit the record. Resolution: In the Ascend-HI.exe program, the patient screen code has been modified so that, under the Insurance tab, when the user double-clicks on an insurance list item, the screen for editing the selected patient insurance record pops up and allows the user to edit the record. Note that this resolution also applies to the Workers Compensation list (just below the insurance list under the Insurance tab of the Patient Admission screen). Now double-clicking an item in the Workers Compensation list will cause the edit screen to appear for that Workers Compensation entry.
CSR:
2381 -- Request: The
Patient Account Status report has detail rows for each claim listed. The
order of the detail rows should be according to the date of the payment,
receipt or adjustment (with the oldest detail item printed first, and the
oldest item printed last). Currently, some detail rows are not in 'date
order' per this requirement.
Resolution:
Modified the ReportRecordSource routine in the Ascend-HI.exe program's Reports screen. The change adds the following 'Order By' Clause after the addition of the 'Where' clause to make the detail rows print in date order: 'Order by Claims.ClaimNumber, Claims.ClaimRef'.
Added update sequence Update20080404 to change the stored SQL for the Patient Account Status
report.
CSR: 422 -- Request: The facility ID number (Contract number) should appear in any drop-down list where the user selects the facility ID. Resolution: Modified the Doctors (Physicians) form to populate each row in the list of the facilities selection dropdown with the ID of the facility, followed by its name (just as is done in the facility selection dropdown when logging into a multi-facility environment).
Here is a list of things fixed
CSR: 2602 -- Request: An error was discovered in the GetNextRXNumber routine of the DLL. In the case where the Defaults table does not contain a RX Number prefix value for the RX counter in question, the previously seen prefix remains in memory, and is incorrectly used when searching for the next RX number. Resolution: Added a line of code in the GetNextRXNumber routine of the DLL. The new line clears out the memory-stored RX Number prefix before searching for the prefix in the Defaults table.
CSR: 2589 -- Request: Storage Notes field on Syringe Label is too short. The Syringe Label was changed after version Ascend-HI version 2.14.97, and now the field for Storage Note is not sufficiently wide to allow for the longest potential value. Quantity, an optional field, shares the line with Storage Note and Quantity is now wider than on the previous Syringe Label format. Please modify the Syringe label by widening Storage Note and shortening Quantity fields. Resolution: Placed a new version of the 'Syringe Label.RPT' file into the Ascend-HI distribution directory so it will be distributed with Ascend-HI version 2.14.107 and higher.
CSR: 2582 -- Request: In
Ascend-HI versions 2.14.97 through 2.14.105, the Factor Label incorrectly
prints the ordering doctor name in the Patient name field.
In Ascend-HI versions 2.14.94 and earlier, the Factor label prints the
patient name in the patient field correctly.
The label was changed to work with custom label fonts after Ascend-HI
version 2.14.94. Resolution: Replaced the Factor Label report file in the Ascend-HI distribution folder with the corrected version of the file.
CSR: 2558 -- Request: Even when patients and orders are configured to be eligible for SHP Outcomes export, when the user selects Strategic Outcomes for exporting, no patients show in the Export Outcomes screen unless the user is logged into the facility with a FacilityRef value of 1. Resolution: The SQL that populates the list of patients in the ListPatients (Export Outcomes) screen for exporting strategic outcomes was modified to no longer filter to only FacilityRef=1. Now the screen is filtered to patients whose facilityref is the one into which the user is currently logged. This causes the correct list of patients to appear.
CSR: 2557 -- Request: When editing a manufacturer in the Inventory->Manufacturers screen, an error is generated (Error 13: Type mismatch) when the user attempts to enter a non-numeric value into the Labeler Code field on the screen. Clicking OK to this error causes the Ascend-HI program to terminate. Resolution: In the Manufacturers screen, changed input control of the 'Labeler Code' field from a text box to a masked text box, setting the mask to accept up to 10 numeric digits. The masked box does not accept non-numeric characters from the user, so this eliminates the type mismatch error. Added a check to verify that the value of the Labeler Code does not exceed 2147483647 (the maximum value storable in a 'Long' type). If the number exceeds this value, then the user is warned with a popup message and returned to the field after clicking on the OK button.
CSR: 2546 -- Request: When a user creates a clinical document, the physician defaults to the primary physician on the profile. If the user changes the physician in the clinical document to another physcian, and then saves and prints or print previews the document, the primary doctor's name still prints in the report, but the address is for the physician that the user selected to at the time the document was created. Resolution: The Crystal Reports file 'Clinical Document.rpt' was modified to correctly print the name, address and phone number of only the doctor selected in the Clinical Document screen.
CSR:
2545 -- Request: The
Crystal Reports file 'Inpatient IV Label.RPT' has been distributed with the
Ascend-HI Update package, beginning with Ascend-HI version 2.14.94 (third
repackaging). The third repackaging of Ascend-HI version 2.14.94 was first
released to the BETA folder on 7/2/2008 10:06 AM.
This report file should not be distributed to Ascend-HI customers, and needs
to be removed from the Ascend-HI machines and associated share directories.
Resolution:
Starting with Ascend-HI version 2.14.105, this report has been removed from the package. In the UpdateHI.exe program, added Update Sequence 20080414 that removes the 'Inpatient IV Label.RPT' file from the user's ~\Crystal\Orders folder (including from a shared server folder, if used).
NOTE: The attempt to delete this file in
Ascend-HI version 2.14.105 (sequence 20080409) failed. The new
sequence 20080414 directly deletes the files.
CSR: 2525 -- Request: When a user applies a payment to a claim, they are prompted to create a copay (to which they answer Yes), after which they are asked to add an adjustment to the original claim (to which they answer Yes), and are then prompted to designate the adjustment as a Payer or Patient adjustment (to which they answer Payer). Instead of posting a credit to the primary payer of the original (parent) claim (as would be expected), the secondary payer receives the credit of the adjustment. Resolution: In the Common module of the Ascend-HI.exe program, changed the code in the CheckForCopay routine. Now, in the copay process, when the user is asked to post an adjustment to the original claim, and the user selects the Payer as the creditee, the amount remaining due on the PARENT claim is credited back the original PRIMARY payer of the parent claim.
CSR: 2521 -- Request: Running a custom version of the Unit dose label generates an error in Ascend-HI versions 2.14.97 through 2.14.104. The error is "This field name is not known", field is CopayAmount. Resolution: Changed the code in the ReportRecordSource routine of the PrintOuts (Labels) form in the Ascend-HI.EXE program. The SQL for the "Order" type of label was changed. This SQL had been modified in version 2.14.96, and the Orders.CopayAmount field was removed from the query. This field has been added back to the query, so the custom Unit Dose Label that uses this field will once again function properly.
CSR: 2474 -- Request: When a
user accidentally double clicks on an order item's 'Edit' button in the
Order screen, the order item selected is automatically changed to whatever
item ends up under the mouse pointer when the inventory item list is popped
up. Following the process below, this can be observed.
1. open an active order, and double click on an item for the order.
2. On the next screen, (Inventory Item screen) the item that appears under
where the mouse was double clicked is selected in the inventory list.
3. Click the 'Cancel' button on the Inventory Item screen.
4. Now, the user is returned to the order screen (note that the listed item
on the order screen has not changed). If the user double clicks on that same
order item again, to select it, when the Inventory Item screen appears
again, the item selected in the inventory list is NOT what was displayed on
the order as the item.
This is confusing to the user if they go back to the order item and the program brings up the incorrect item. It also allows for a drug error in the order if the user is not paying attention to what they click on in the Inventory screen.
Resolution: In the APIs module of the Ascend-HI.exe program,
added the line:
Public Declare Function BlockInput Lib "user32" (ByVal fBlock As
Long) As Long
Added the 'BlockInput (True)' at the beginning of the cmdEditItem_Click()
routine of the Order screen. This prevents the second click of the
accidental double-click of the Edit button. Added the 'BlockInput
(False)' to the cmdEditItem_Click() routine to turn capture of keyboard and
mouse input back on after the routine has finished its work.
CSR: 2463 -- Request: UB-04 Form: Box 76 second box needs to be widened to be able to print 10 digits. Resolution: The UB-04.rpt Crystal Reports file has been modified. The Other ID field (second box) for Box 76 is now wide enough to contain 10 characters.
CSR: 2459 -- Request: On the UB-04 form, the NDC number of an item is required in location 43 when a 'J-code' (HCPC) is printed in location 44. The UB-04 form Box 43 specification states: "Enter a brief description that corresponds to the Revenue Code in column 42. List applicable NDC if location 44 is a J code." Resolution: Modified the UB-04.rpt Crystal Reports file to now populate the Box 43 contents depending on the 'Box 44' setting for the Payer under the 'UB-04/UB-92' tab of the Payers screen. If the setting is to include the NDC in Box 44, then the 'Description' field is used to populate Box 43. If the setting is to include the HCPC (J code) in Box 44, then the NDC is used to populate Box 43.
CSR: 2449 -- Request: When
IMPORTING a FDB record into inventory (where the item did not previously exist), the AWP price is copying the last price record in history
(regardless of if the record is AWP or not). The import function need
to ONLY look at AWP price type when importing into a blank record in the
database.
The workaround for Ascend-HI users is to run a FDB synchronize after they
import any items from the FirstDatabank master file. Resolution:
Changed the SQL in the 'Find' routine of the CDP.cls class in the Ascend-HI.exe program. The new SQL filters the returned data to only look at the AWP price type. Also added a second SQL to retrieve the Last Updated value and the Average Wholesale Unit
Price.
CSR: 2428 -- Request: On the TPN label, the intrinsics are printing the source name and strength on top of each other on the left hand side of the label. Resolution: Modified the TPN Label.RPT Crystal Reports file so that does not print the source name and strength on top of each other.
CSR: 2424 -- Request: The AddClaim subroutine in the X12N module of the AscendHI.dll program is generating a 'Routine too large' error in the VB6 development environment when the software attempts to run the routine (create an X12 batch). The AddClaim subroutine needs to be broken down into subroutines, one for each ANSI X12 loop, and the AddClaim routine should call these subroutines. This not only corrects the error, it makes the code easier to read and maintain. Resolution: The AddClaim subroutine in the X12N module of the AscendHI.dll program was broken down into subroutines, one for each ANSI X12 loop, and the AddClaim routine now calls these subroutines.
CSR:
2416 -- Request: The
HCFA-1500 (v1.3) form is printing the main
facility's
NPI in Box 24J, and not the NPI
of the provider that dispensed the items.
Resolution:
Modified the HCFA-1500 (v 1.3) Crystal Reports file. Changed the way Box 24J is populated.
Now, when a Billing Provider is selected for a claim (under the claim-level 'HCFA' tab of the Claim screen), and the claim's Payer's settings for the source of an ID for Box 24j is 'Facility' (under the 'HCFA-1500' tab of the Payers screen), then the HCFA 1500 (v 1.3) form will
print the NPI of the Billing Provider in the NPI portion of Box 24J.
Note that, if the selected Billing Provider’s NPI is equal to the Facility NPI, then (if configured in the Payers screen to do so) the Facility’s non-NPI ID and its qualifier are used to populate the non-NPI portion of Box 24J. If a Billing Provider is selected for the claim, and the Billing Provider’s NPI is NOT equal to the Facility NPI, then the non-NPI ID and related qualifier portion of Box 24J is NOT populated.
If a Billing Provider is NOT selected for the claim, then Box 24J is populated with the NPI of the facility, and (if configured in the Payers screen to do so), the non-NPI ID and related qualifier will also be drawn from the facility record.
CSR: 2415 -- Request: version 2.14.102, a modified Ascend-HI 'Order Label' was inadvertently packaged with the program. There are numerous differences that are not appropriate for Ascend-HI users. The original report needs to be put into the release packages in the future. Resolution: The earlier version of the Order Label.rpt file was retrieved, and minor corrections were made to the field layout to prevent the mix date field from cutting off the last digit of the year. Also, the date format was returned to the original use of '/' instead of '-' as the separator (2/2/2000 vs. 2-2-2000).
CSR: 2404 -- Request: Before
version 2.14.102 of Ascend-HI, if the SQL Server user did not have access to
the share directory to bulk insert the FDB files into the database, the
update process would present a message that it would take more time to
complete the update, and then would continue inserting FDB records at a row
level after the user clicked the 'OK' button. In the update to version
2.14.102 of Ascend-HI, this changed. Now, if there are no permissions to the
share from the bulk insert, then the program presents an error that says
that the user does not have permissions to do bulk inserts and stops the
update process and then presents additional messages for every table that it
tries to bulk insert, instead to inserting into the database on a row by row
level.
If the user does not have bulk insert permissions, then the program should
fall back to inserting records at a row by row level and NOT stop the update
process.
Resolution: In the UpdateHI.exe program, FirstDatabank module, ImportNDDFFile routine, added an error trap for the word 'BULK' as a catch-all in case the SQL Server error message is not an exact match to known bulk insert errors (as was the case here). It appears that different specific versions of SQL Server have slightly varying messages for the same error.
CSR: 2395 -- Request: In Ascend-HI version 2.14.102, the patient phone number was removed from the patient address information on the upper left hand side of the printed Clinical Documents form. Additionally, the doctor's phone number is getting cut-off in the Doctor's address information on the upper right hand side of the printed form. The Patient's Home Phone needs to be included on the form. Resolution: The Crystal Reports file 'Clinical Document.rpt' was modified to correctly print the name, address and phone number of patient for whom the Clinical Document was created. Additionally, the form was modified so that the doctor's phone number will not be cut-off. Finally, vertical room was rearranged in the heading to make room for a second patient address line (without cutting off the patient phone number or causing it to overlap the line below it).
CSR: 2375 -- Request: The UB-04 form has a 'Page n of n' entry (just left of the 'CREATION DATE' label). The number of total pages is correct, but when more than one page is used for a single claim, the individual page number is always '1', even for pages 2 and higher. This field should represent the actual page number of the specific page of the claim on which it is printed. Resolution: Modified the UB-04.RPT Crystal Reports file to use an internal Crystal Reports function to properly identify and print the page and total number of pages. The report now prints the correct page number and total number of pages in their respective fields on the page.
CSR: 2354 -- Request: If pharmacy staff does not visually see that a medication was just filled that day, they can accidentally refill an order on the same date as the original fill (as long as there are refills left on the order). Currently, some customers are refilling an order, billing for the drug, and are then having the claim rejected by the payer because the prescription was refilled too soon. The user has to then go back to the refilled order and cancel it, and then go into the Claims screen and put the correct Claim in a Canceled Status. There should be a default setting, that (when set) causes this 'too soon to refill' warning to appear if an order is being refilled earlier than a specified # days before it is due. Currently, the software does not present such a message. Resolution: Added "Always check refill Start date" as an option to the Options screen under the 'Order Entry' tab. Now, the ValidOrder routine of the Order screen code checks the condition (true/false) of the "Always check refill Start date" value to determine whether to run the overlapping dates test between the refill and the original order. If the value is True, then the software ignores whether the user changed a fill date on the refill, and checks the dates anyway. Otherwise, the date comparison is only run if the user changes a fill date on the refill order before saving it.
CSR:
2122 -- Request: When
Help->Online Help is selected by the user, the Help window is displayed
along with the topics, but none of the actual help information is displayed
in the box on the right side of the window.
Resolution:
In the Ascend-HI.exe program, the OpenHelpTopic routine in the Common module
was modified. The line:
HtmlHelp 0, strAppPath & "Ascend-HI Manual.CHM",
HH_SAFE_DISPLAY_TOPIC, ByVal Value
was replaced with:
Shell "HH.EXE " & Chr(34) & strAppPath &
"Ascend-HI Manual.CHM" & Chr(34), vbNormalFocus.
This change causes the help file to open and the contents to display
properly.
CSR: 2017 -- Request: Since errors can occur in the update process, the ReportCriteriaFields table can become mispopulated. To repair the table and its data is a time-consuming, manual process. To eliminate the need to hand-populate the table in the future, there needs to be a routine in the update that drops, re-creates, and then properly re-populates the ReportCriteriaFields table. This routine can be called by future update sequences whenever this is necessary. Also, this routine is where all future changes to the contents of the ReportCriteriaFields table will occur. Note that this was already done for the SQLSources table (see CSR: 1957). Resolution: Modified the UpdateHI.exe program. In the Update.vb module, added the AddOrDeleteReportCriteria subroutine. In this new routine, ALL of the information for each row in the ReportCriteriaFields table is kept. Now, when an update sequence calls this routine to add or delete criteria, the parameters can be set to clear and repopulate the ReportCriteriaFields table (based on the statements in the new subroutine) by passing all blank parameters and setting the DeleteRecord parameter value to True. Alternately, an individual entry in the ReportCriteriaFields table can be deleted from the table by passing the entire set of parameters and setting the DeleteRecord parameter value to True. Additionally, an individual entry can be added to the table by calling the routine with all valid parameters and having the DeleteRecord parameter value to False. In this case, the routine checks to see if that entry already exists, and if not, adds the entry.
CSR: 1270 -- Request: In Clinical review screen, there is a link to the related monograph for the issue (states "Click here to review the related monograph"). For Drug-Food interactions, clicking on the link brings up the actual monograph. For Drug-Drug interactions, however, clicking on the link brings up a blank Monograph screen. Resolution: In the Ascend-HI.exe program, the frmClinicalReview and frmMonographs code was changed. The parameters used in a call from the frmClinicalReview.lblMonograph_Click subroutine to the frmMonographs.LoadADIM routine were changed to properly cause frmMonographs to load the correct drug-drug interactions.
CSR: 606 -- Request: On very rare occasions, duplicate Rx's #'s are being assigned to different drugs, different patients. Need to improve the method for preventing duplicate Rx #'s being assigned. Resolution: In order to improve the ability to avoid collisions that cause the same RX number to be assigned to different prescriptions, (in the GetNextRXNumber function in the Order class of the AscendHI.dll program) moved the line of code that Writes the RX number to the Defaults table to an even earlier execution point. This avoids the delay that occurs when the code searches the existing orders for a duplicate. Once the number is posted to the Defaults table, the search is commenced to identify duplicates. If one is found, the RX number is incremented and the loop is rerun. This occurs until a valid unused RX number is found. During this time, the number that was posted immediately to the Defaults table is found by any other workstations attempting to generate a different order at the same time. Additionally, in this routine, replaced the calls to the ReadDefault function with direct SQL to speed up the process of getting the last used RX number.
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
11/25/2008
NOTE: If a more current version of the First Databank files has been received by Hann's On Software since this release, you can go to the Hann's On Software website and perform a First Databank update that updates your Ascend-HI to the most current First Databank files.
HCPC Codes