IMPORTANT! AS/PC ® for Windows trial versions may be upgraded to production versions by calling DBC to get a special registration number that will be unique to your clinic, computer, and hard drive. Once you have registered your software, the trial expiration message will no longer appear when starting up the system. All DBC software and AS/PC ® systems are copyrighted by DB Consultants, Inc., © 1998-2008, all rights reserved. You may not sell this software or install this software on any computer except your own without the specific written consent of DB Consultants, Inc. You may not make copies of this software except for the purpose of backing up your data. Unauthorized duplication of this software is a violation of DBC's copyrights and is subject to severe penalties.
Electronic Claims Warning: Other than direct submissions to Medicare and submissions via Envoy/NEIC and Statlink, DBC does not support any third-party clearing houses. Users should be aware that attempting to submit claims by creating a text file from our paper claims selection in the main AS/PC system is not advisable, nor is it supported by DBC, Inc. Typically, local small clearing houses attempt to take a text version of your paper claims output and convert this to an acceptable ECS format. Don't do it! We do not support it, and every time we update our software, your third-party vendor's conversion program will fail and have to be rewritten!
Download: Computerizing Your Office
DBC's hard copy comprehensive tutorial on moving your practice into the 90's with Microsoft Windows is now available and shipping to all DBC licensed users. This document is required reading for all clinics, whether or not you are using DBC's practice management software. If you have Microsoft Word 2000/XP or a viewer that can read Word files, you can download the entire document here by clicking the title above. You should also download the latest version of the DBC Online Windows Help System. Computerizing Your Office interacts heavily with the help system.
Download the AS/PC ® for Windows Online Help System
The latest version of DBC's help system is available here. Please note that this is a Windows 98 formatted help file; and you must have Windows 98, 2000, XP Pro, or NT4 in order to use it.
Windows NT 4.0 Printer Setup Hints
1. You must name your generic text only printer driver so that its name puts it alphabetically at the end of your list of printers in the printer folder in the Control Panel. Simply name it "zgeneric" just to be safe. Once you do this, screen previews of all reports should work as desired.
2. Printing envelopes on HP lasers under NT 4.0 is the same as it is under Win 98. Via the Control Panel Printers folder, simply install another copy of your HP printer and name it "HP Envelope Printer". Right click its icon in the Printers folder and select "Document Defaults". Set paper size to "Envelope #10"; Orientation to "Landscape"; and Paper Source to "Manual Feed".
back to topSummer 2007 Upgrade
AS/PC for Windows -- Version 11.0
(Starts with Build # 360 -- 09/01/2006)
1. New CMS claim form (Builds ASPC-373, ASPCCLMS-075): We have added the new CMS-1500 claim form to ASPC; and it replaces the old HCFA 1500 in this system. ASPCCLMS will continue to have the ability to print the old form for as long as it's needed. Licensed users of ASPC will continue to be able to print the old HCFA 1500 by running an add-on program named HCFA1500.EXE. This program should only be used for printing the old HCFA form. All carriers are supposed to change to the CMS form shortly.
2. The new Box 11c has been added to the insurance carrier file (Build ASPC-373): This new field will print on the new CMS-1500 form in box 11 for "insurance plan name or program name" for those carriers which require something different than the name of the carrier printed at the top of the form. This box will not be used for printing the old HCFA1500 form which is being retired as of Spring, 2007.
3. Updates to the electronics claim program (DBW837X-083): Provider, clinic, and facility NPI's will be reported if included in the data files. Selection of either the legacy or the NPI may be made on a carrier-by-carrier basis. ANSI 4010A1 837 files are formatted for direct-to-Medicare and clearinghouse submission to Emdeon.
4. New UB-04 claim form (ASPCCLMS Build 076): The new claim form
was added for both laser and dot matrix printing.
5. Updated 837 electronic claims (DBW837X Build 091): Included in the
changes are: addition of a new carrier field F1500_NO option, change in
provider and facility NM1 segments, added new segments when reporting NPI,
changes for DMERC, output of all 8 diagnosis codes, NPI reporting in
facility data.
End of Version 11.0 Enhancements
back to topFall 2006 Release
AS/PC for Windows -- Version 10.0
(Starts with Build # 324 -- 04/01/2005)
1. 837 changes for billing Medicare demonstration project (DBW837X Build 069): We have added an option to create a new claim for each treating provider. The option is labeled "One claim per provider?". In addition, the program was changed to output the reference segment needed for billing the demonstration project.
2. New utilities for system files and revised data file update for all DBC systems (Builds ASPC-329, ASPCUTIL-113, DBAR-116, DBMAIL-212, DBCUTIL-033): We have added a utility that can append single/multiple additional records to DBDICT, DBREPORT, DBVIEWS, LABELER, PLIST and QUERIES data files. The new features are available via File/Import in the above systems. As a part of this enhancement, we have updated the installation/update software.
3. New System! ASPCPAY (Build 003): ASPCPAY processes payments automatically based on the 835 remittance advice file and user assigned options. The payments are processed from the main menu "Batch". During the process, the user will receive ASPCPAY Batch Report. If accepted, the system processes the payments and prints ASPCPAY Deposits Report.
Users are prompted to assign a unique batch description. The description is saved in payment files (ERABATCH field). ASPCPAY can regenerate the deposits report (Edit/Deposits Report menu selection) at later time as well. Each file processed is stamped by ASPCPAY to prevent users from processing the file more than once. The file may be reset (via Utilities menu) in the event it needs to be processed again. As in DBW837X, ASPCPAY can generate the three Remittance 835 Reports and FA997 Report.
4. Alternate phone number (ASPC Build 331): Added to the patient form (on INS2 tab) is an alternate phone number and extension fields.
5. New monthend closing report (ASPC Build 331): Added to the menu Monthly/Monthend is Claim Proc Check. This is a new report which that can be run prior to monthend close. It will show charges that can prevent the close process from completing successfully.
6. Several enhancements to charges and payments (ASPC Build 331): We have added default user defined transfer descriptions. Via charges/payments form menu: Options/Default Transfer Desc. Users can set the two transfer descriptions used for transfer to patient and transfer to insurance carrier. These descriptions are saved for all future entry sessions.
We have also added the names of the 3rd and 4th carriers to the Payments form. This allows the user to easily determine if additional carriers can be considered for claim payment prior to writing off or transferring any unpaid balances.
For charges, a new option setting default provider is available via menu: Options/Default Chgs Trt Provider. If used, this option sets default treating provider when entering new charges. This option is only active for the current charges entry session.
7. New ASPCPAY option (ASPCPAY Build 006): Added to user defined option sets is the ability to process multiple carriers from a single 835 remittance file. The option is located on tab 2. With this change, 837 was modified to transmit the data.
8. Stack Overflow Error Fixed in Charges and Payments Entry (ASPC Build 337): Due to a Windows XP issue with modal window forms, some users have experienced "Stack Overflow" error messages when entering large numbers of payment or charge transactions. To address this issue, we have redesigned the charges and payments entry portions of the system to do away with those modal windows that were causing the issue. Users who are experiencing stack overflow messages or instability during charges or payments entry will find that this update eliminates these.
Our test groups have entered as many as 12,000 charges and a similar number of payments in one session (via an automatic keystroke generator) without incurring any hint of instability or any stack overflow messages with this release.
Please note that this is an important and significant change. While we have tried to keep the external interface as consistent as possible with earlier versions of AS/PC, the elimination of modal data entry forms has required some changes in the user interface. Our beta clinics found these changes to be positive and easy to adapt to.
End of version 10.0 enhancements
back to topSpring 2005 Release
AS/PC ® for Windows -- Version 9.0
(Starts with Build #306) - January 6, 2004
1. A New Monthly Plus statement option has been added (ASPC Build 307): We
have added an option to print patients with cash balances on the Monthly Plus
Statements. Simply check the run-time option to "select patients with cash
balance only."
2. New payments form option (ASPC Build 307): On the deposits form, users may
define the description for write-off transactions (default is "Forgive"). The
new description is saved for future use. It can be changed from the
Charge/Payment Entry Window. From the secondary menu at the top of the window,
simply select Options, then "Default Write-Off Desc".
3. Expansion of the AS/PC Utilities renumber and duplicate functions (ASPCUtil
Build 104): The function which permits renumbering or elimination of duplicate
claim/invoice numbers has been enhanced to handle larger history files. This
function is available in the AS/PC Utilities program from the Claims/Charges
menu. The effected functions include Renumber Claims, Duplicate Claim #, and
Renumber Invoices. Users are advised that they must complete a backup prior to
running this function and that all users must be out of AS/PC and all associated
programs.
4. Support has been added for the UB-92 laser form (ASPCCLMS Build 057): We have
added the ability to print form #8 UB92 Medicare on laser forms using 10 point
Courier font. To run this form, simply change the custom claim option to select
Laser Claim Form.
5. HIPAA-Compliant Electronic Claims using the 837 V4010/4010A1 Format have been
enhanced. (DBW837X Build 051): Facility-related segments for claim and line
level data selection has been vastly expanded. Users can now select data from a
number of places as well as control the generation of facility segments via the
Options | EMC Options menu. Your selection includes the facility stored in the
patient file or the charge file, the provider stored in the patient or charge
file.
6. We have added new views in ASPC, dBar and dbMail (Builds ASPC-308,
ASPCUTIL-105, dBar-114, dbMail-210, dbcUtil-031): There are six new views for
ASPC containing various combinations of data files and relationships
including charges, payments, diagnosis and procedures. Similarly, four new views
for charges, payments and products were added to dBar and dbMail. These are
available for users in development of custom reports via the File | Open |
Lister option to provider more alternatives in reporting.
7. ASPC integrates with Spectrasoft Appointments via EDI (Builds ASPC -310,
ASPCUTIL-106): AS/PC patient data and Spectrasoft appointment data may exchange
information entered to reduce entry. To enable AS/PC for both imports and
exports, the user must select the option via Utilities/Enable Spectrasoft
Interface on patient form menu. This will
ensure that your data will be updated regularly.
ASPC exports similar patient fields to Spectrasoft. Exports occur whenever any
of these fields have changed or a patient is added in patient maintenance.
Single patient imports can occur whenever a patient or a charge is added or
edited. This works similar to the AutoBill function in charges. In addition,
user may batch import all appointments via ASPCUTIL (menu:
Patient/Appointments/SSoft Batch Import). This functions in similar fashion to
ASPCBill.
If exceptions are encountered during any import, an (optional) exceptions report
is available to print. All exceptions are stored in a database (SSOFTBAD.DBF)
and may be printed from ASPCUTIL (menu: Patient/Appointments/SSoft Exception
Report). SSOFTBAD file maintenance (menu: Patient/Appointments/SSoft Exception
Maintenance) deletes appointments data prior to the current date, eliminates
deleted records permanently and will reindex the file.
8. Capabilities for the #8 UB92 Medicare form have been enhanced. (ASPCCLMS
Build 060): We have updated box 23 revenue code to print four characters as
required. This enhancement will be transparent to the user.
9. UB92MC and 837 ANSI Part A Update for Multiple Disciplines (ASPCCLMS Version
3.0, Build 001 and DBW837X): The Part A claims have been updated to support OT,
PT, and ST charges on one claim. Prior to this update, the program created a
separate claim for each specialty. Now, all current therapy charges print on a
single claim per carrier specifications. Since visits have to be tracked
separately by therapy type (OT, ST, PT), the program will now recognize 3 new
visits counters in the MY file. In order to take advantage of this new
processing logic Multi-discipline Therapy users must create these 3 new fields
in their MY files before printing claims. The 3 fields must all be numeric type
of length 2; and their names must be VISITSPT, VISITSOT, and VISITSST. This can
be accomplished in the AS/PC Utilities program from The File menu. Users are
encouraged to contact their appropriate support organization for assistance in
creating these new fields and to have a complete backup before calling.
Important: When printing the UB92 claims for existing users, the visits
counter(s) are being updated via the new method.
For example: a PT only claim form reports visits by calculating the unique
occurrences from the claim form (plus what was already in my-visitspt). This
will mean that current users that used to have the visits counter coming from
patient->visits, will have to replace my->visitspt with the value in
patient->visits in order to be current.
10. As an aide in tracking how claims have been created, the Reset Batch
Function (Effects all systems) now creates a text file named REBATCH.TXT
whenever a RESET BATCH is performed by the user. The text file contains the
time, date, which claims were reset, and the terminal ID of the user who
performed the reset. The system retains several generations of REBATCH.TXT,
renaming it each time a new reset is performed. The older versions are named
REBATCH.001, REBATCH.002, and REBATCH.003. Anytime the user runs a new batch
after a reset, the system senses the presence of REBATCH.TXT and warns the user
that a reset has been performed. The user is given a view of the REBATCH.TXT
file and an opportunity to do a backup.
11. ASPCCLMS and DBW837X (ASPCCLMS Version 3.0, Build 001 and DBW837X) now both
have functions added to their menu to backup and restore the user's MY.DBF file.
It backs up the file to MY.001 if the user requests the backup function. This
feature is primarily for Part A users who may have to perform a rebatch. Use of
the backup and restore of the MY file feature will allow Part A users to
preserve their visits counters (in their MY file) if they rerun a batch
immediately after a reset, but before other claims have been processed. In the
unlikely event that a user needs to rerun a batch of claims, this function will
permit the user to "turn back" the visit counters in the MY.DBF file to their
original values.
12. We have added a new carrier PIN number database (ASPC Build 313): Similar to
the provider PIN database, we have added a new database RPIN_NO.DBF with the
associated maintenance and report to accommodate new reporting requirements for
referring provider IDs. The file stores the carrier, referring provider ID (up
to 25 characters for PIN
field) and the PIN qualifier. Use of this feature is optional and is accessible
from the File | Open | Referring Providers | PIN button.
13. Healthwire update (DBNSF Build 305): We have made a number of changes for Healthwire
claims. This also includes the use of the new referring provider PIN
database (described above). Users must be sure to activate this feature from the
main claims option menu "activate Provider referring PIN# from alternate file".
14. HCFA upgrade (Builds ASPC-314, ASPCCLMS-061): We have added the capability
to use the new referring provider personal ID database in processing HCFA
claims. Users must be sure to activate this feature from the main claims option
menu "activate Provider referring PIN# from alternate file".
15. The claim reprint function has been standardized throughout our claims
processing and now include electronic claims in DBW837X and DBNSF. This means
that users can now select from reprinting single claims, single patient multiple
claims and batch reprint current period. Both systems can also elect to includ
paid claims via these functions. Additionally, support for the referring
provider PIN feature has been added to electronic claims programs (Builds
DBW837X-064, DBNSF-306).
16. New Charge Fields (Builds ASPC-318, ASPCCLMS-062, ASPCUTIL-108, DBNSF-307,
DBW837X-066, ASPCBILL-125): We have added DATELAST and DATECONS fields to the
charges files (invget.dbf,billings.dbf, claims.dbf). During charge entry the
field values from the MY file DATELAST field and patient file DATECONS field are
automatically recorded with the charge. This retains the values for future use
(reprints and secondary claims). The values maybe changed by editing current
charges in ASPC or old charges via ASPCUtil.
The new fields use has been added to DBW837X, DBNSF and the HCFA claims. The new
charge fields are used if they contain data. Otherwise, the claim programs will
go back to my and patient file data as was done in the past.
17. New Labels (ASPC Build 320): Six patient labels ( Reports | Crystal Reports
| Labels ) have been added to handle
printer alignment issues. The labels start printing one line lower than other
labels. The new labels are: PAT25160, PAT25161, PAT2B160, PAT2B161, PAT2F160,
PAT2F161.
18. Social Security Numbers for Privacy (Builds: ASPC-320, ASPCCLMS-067): As a
direct result of the new HIPAA privacy rules, we have added the ability to
optionally suppress printing patient and provider social security numbers on
charges slips, super statements and itemized statements (an alternative to claim
forms). This feature is controlled by a check box available at print time.
19. YTD Report (ASPC Build 320): This report is available from Monthly | Year to
Date. It includes monthly dollar totals (total charges, total payments, etc. )
We have expanded the size of the charges column to accommodate larger dollar
amounts.
20. Proof of Timely Filing (Builds: ASPC-320, ASPCCLMS-065): A new report for
proof of timely filing is available from the ASPC and ASPC Claims main menu
(Insurance/Claims Registers/Proof of Timely Filing). Print the report for a
single patient selecting one or multiple claims.
21. Daysheet Reports (ASPC Build 320): Daysheets for daily, monthly, summary and
detail can be run on history (non-current month) data. The reports are located
on ASPC main menu under Daily / Daily/MTD Daysheets / History Daily/Month /
Detailed Daily/Month or Summary Daily/Month. The format is the detailed and
summary daysheets for the current month except no visit counts or totals are
included.
22. Monthly Log Report (Builds: ASPC-320, ASPCUTIL-109 and all DBC systems): The
monthly log report message that appears on the first day of each month has been
modified so it appears only once, instead each time the program is started.
To accomplish this a new zero byte file named "LOGRP001.TXT" (where 001 is the
terminal ID) is created in the users data directory. Erase this file to
re-activate the prompt and enable printing the report.
23. Monthend Statements (ASPC Build 320): We have added the ability to merge MY
and USR database records when printing a custom message on Monthly, Monthly
Plus, Short Form and Generic Envoy statements. Custom messages are defined in
the statement options message tab (Bill | Options).
24. ASPCUtil Mark Claim Paid (ASPCUTIL Build 110): The mark claims paid feature
in ASPCUTIL (Claims/Charges | Mark Claims Paid) has been modified to permit
marking a single or selected multiple claims paid by patient.
25. DBC Lister (Builds: ASPC-323, ASPCUTIL-111, DBAR-115, DBMAIL-211,
DBCUTIL-032): The AS/PC Field File List (File | Open | Field List) can now print
date fields with or without the century. Turn printing dates with century on and
off via the column definitions screen. When viewing a lister report, the current
setting is indicated in the upper right hand corner of the screen.
When you install the upgrade, existing lister reports are not effected. To turn
on printing century for these reports, you must check the "Print Dates with
Century" box in the column definitions screen. All lister reports created after
installing the upgrade, default to printing the century.
26. Exporting patient data (ASPCUTIL Build 112): (File | Export) We have added
the patients email address to the data exported to Microsoft Outlook.
End of version 9.0 enhancements
back to topWinter/Spring 2004 Release
AS/PC ® for Windows -- Version 8.0
(Starts with Build #271; Ends with Build 305) - January 6, 2004
1. Fix to patient and customer forms (Builds ASPC-271, DBAR-108, DBMAIL-204):
An error was discovered in patient form (ASPC) and customer form (DBAR/DBMAIL).
The error occurs when one user views
("sitting") on a customer record while another user edits that customers notes field.
When the "sitting" user navigates off the
record an error occurs. The error message maybe several different messages because the
application becomes unstable. A workaround was
implemented which eliminates the error.
2. Update NSF programs for North Dakota (Builds DBNSF-294, DOS DBECS-2.22): We
have updated the trailer record for special state
NDB and NDM to NSF V2.0 as the carrier has modified their software.
3. Upgrade to Functional Acknowledgement 997 listing and report in 837 systems
(Builds DBW837-165, DBW837A-161, DBW837B-031, DBW837X-009): We have added an 80
character file format conversion option to
FA997. WebMD currently provides FA997 in this format. Please note, the option will
appear as an additional prompt only if the 81st and
82nd characters of the file contain carriage return and line feed respectively.
4. New feature in patient maintenance form (Build 278): We have added zipcode
lookup to the patient form as it exists dBar/dBMail.
The lookup is available for patient, primary and secondary guarantor addresses.
Please note, there are other addresses within this form which contain city, state and zip
in one field. These fields do not perform the
lookup due to the single field.
5. ASPCCARE reports were updated (Build 159): We have updated all Summary Revenue
Reports and Clinic Receivable Reports for the new
stored Clinic ID field in charges and payments data files. In addition, Capitated Fees
Report for both DOS and Windows was updated
to count units as transactions.
6. New Monthly Plus Statement (Build 282): We have created a new statement that
allows intermixing charges and payments by invoice
number, claim number or date of service. The invoice and claim number sorts include
sub-totals for invoice/claim number. Requesting
date of service sort skips sub-totals. This is a great advantage
since some providers may prefer to reduce statement size by picking this sort.
7. New option for Daily Provider Spreadsheet (Build 282): An option was added to
eliminate the printing of zero dollar line items.
8. New options in charge entry (Build 282): We have added two options for
eliminating missing data warning message and diagnosis
warning message.
9. Modified multi-claim selection data (Build 282): Date of service or range
of DOS have been added to the multi-claim selector. This
function is used when reprinting claims.
10. Color coding financial classes (Build 282): We have modified display of
financial classes in charges and payments entry, patient
maintenance and carrier maintenance forms.
11. Reset monthly statements (ASPCUTIL Build 099): Previously you could not
batch run statements twice on the same day. Under
Patients/Reset Statements we have added the ability to reset all statements that
were run today.
12. Performance enhancements (ASPC Build 285): We have improved ASPC
performance for items that either require or optionally build a work file to
combine current and non-current charges and payments. This includes Super
Statement, new Monthly Plus Statement, Ledger and Transaction List.
13. Cash patients and warning messages (ASPC Build 285): We have further revised the charge entry (missing data) warning messages to be excluded for cash patients.
14. New Monthly Plus Statement (ASPC Build 285): The ability to print Monthly Plus statement directly from charges and payments maintenance was added. The request can be made from Reports icon or menu item.
15. Michigan Medicaid (Builds ASPC-285 and DOS ): HCFA 1500 was updated for Michigan Medicaid. Changes were made to boxes 24a and 24i.
16. Generic/Envoy statement option (Build 288): We have added the ability to print the optional monthend statement address (located on patient form INS3/4 tab) on the Envoy Statement.
17. HCFA 1500 Update (BUILDS ASPC-291, ASPCCLMS-049 and DOS): We have completed changes required by Medicaid in NC for secondary claims. This feature is optional and is available from: reprint claims from the line item payments screen, from Insurance | Secondary Claims | Single or Reprint - "Single Claim" and from Insurance | Reprint Claims - "Single Claim".
The choice for activating this feature is via prompt from the above menu items. The amount for box 29 is provided by the program but can be overridden in the prompt. Box 30 contains box 28 minus box 29.
18. Batch reprint current month claims (BUILDS ASPC-291, ASPCCLMS-049): You can now batch reprint current month claims without resetting the claims.
19. Logging insurance register (BUILDS ASPC-291, ASPCCLMS-049): Claim reprints (all paper claim forms) will no be logged in the insurance register. This was completed for the HCFA 1500 and will be completed for other paper claims.
20. New patient indexes (ASPC Build 294): We have added an index for patient nickname as a system index. In addition, PLAST tag index was modified to include middle initial at the end of the key.
21. EDI 835 Reports (DBW837X Build 36): We have completed 835 remittance reports including file listing, transaction listing and report. The functions are located in DBW837X from the edit main menu.
22. New option and info for Daysheets (ASPC Build 295): New option to include 0.00 charges in the transaction count and visits count. In addition, all detail Daysheets include sort order in header. Note: CPT Code Daysheet was not modified since it already contained the option.
23. New insurance tracer option (ASPC Build 295): You can now print multiple tracers for a single patient in one process.
24. Summary Lister report (BUILDS ASPC-294, ASPCUTIL-101, DBAR-113, DBMAIL-209, DBCUTIL-030): We have added the ability to print sub-totals and report total (only) in Lister generated reports.
25. Insurance Ledger changes (BUILDS ASPC-294, ASPCCLMS-050): We have added an option to include current month transactions, page breaks and printing DOB for each patient.
26. Reprint (all forms) paper claims (BUILDS ASPC-295, ASPCCLMS-050): The ability to batch reprint current month paper claims without unbatching is available.
27. Carrier Labels (ASPC Build 295): The ability to print a full sheet of 2 across laser labels for a given carrier was added. To run, select label icon/menu item from Carrier maintenance form.
28. DBNSF Healthwire+ (DBNSF Build 301): DBNSF was modified to handle WebMD's Healthwire+ (special state "HW") claims.
29. New paper claims and 837X batch limitation (BUILDS ASPC-300, ASPCLMS-056, DBW837X-043): We have added INSUR->MYFIELD limitation. User coding of limit or the field itself is not case sensitive for the comparison.
30. Print merge letter from patient form (ASPC Build 301): From within patient maintenance, you can now print a single merge letter. It is accessible from View/Print Merge Letter menu item.
31. Fee on transaction list (ASPC Build 301): As an option, users may elect to include fee on transaction listings.
32. More paper claim options (BUILDS ASPC-301, ASPCLMS-056): We have added the ability to reprint claims that are marked paid. If the user elects to include paid claims, the selection browse will include "PD" field column.
On batching new secondary claims, you may now elect to batch run a single patient carrier level (i.e. patient tertiary carrier only).
33. New sizes report (ASPCUTIL Build 102): We have created a new report
of ASPC data sizes on several of the most used files. This could be helpful in
troubleshooting technical issues. The report includes: PATIENT, INVGET, CLAIMS,
BILLINGS, DEPOSITS, OLDPAY and PAID files. The info has file name, number of
records, DBF and MDX file size in bytes, last modified date, lowest and highest
claim numbers (for INVGET and CLAIMS only). Access is from Utilities/Data
Analysis/ASPC Data Sizes.
End of version 8.0 enhancements
back to topSpring 2002 Release
AS/PC ® for Windows -- Version 7.0
(Starts with Build #242) - February 1, 2001
1. New carrier PIN and group numbers database with HCFA 1500 update (Builds ASPC-242,
ASPCCLMS-039): With the growing amount HMOs that
may assign provider group numbers and personal identification numbers, we have added a new
database PIN_NO.DBF with the associated maintenance and report to accommodate the growth.
This provides an open ended amount of this
type of data that can be stored and used.
The file stores the carrier and provider ID with up to 25 characters
for PIN and group number fields.
The use of this feature is optional. Activation is controlled via the claim option set
(master and/or other) on #3 tab. Even when
activated, this function will provide the old PIN or group numbers if the unique
provider/carrier record does not exist or does not
contain PIN or group data. Maintenance is provided via the provider edit form
(ASPCWIN:File/Open/Provider menu item). From this
form, press the PIN button at the bottom of the form. A report listing is also
accessible via the
provider form from its View menu.
This option is available with this build only for the HCFA 1500 form.
2. DBNSF PIN numbers (DBNSF build 281): We have updated DBNSF to use new PIN_NO database.
As in
HCFA 1500, it's use is optional. Activation is controlled from Main Options on tab #3.
3. DBNSF DOS and Windows Updates (Windows Build 284, DOS Ver. 2.12): We have updated
both platforms for the state of Illinois date of last
appointment/seen field (EA0 267-274) and for Champus provider number
(BA0 90-104). The Champus number is a new field in ECS Options named PROV_CHPS. It is located
on the options form/screen: Windows-tab 3
or DOS-page 2.
4. Edit and browse forms may now retrieve stored queries. (Builds ASPC-246, ASPCUTIL-087,
DBAR-103, DBMAIL-199, DBCUTIL-021): We have
added the ability to retrieve and use stored queries in most browse
and edit forms. The feature can be accessed from the query button or via the menu View/Queries
as was previously used for new queries
only. This is a global DBC software change affecting all systems.
5. Claims register for closed months. (Builds ASPC-248, ASPCCLMS-040): We added the
optional ability to process claims
register for closed months. The same options are available as when requesting the current
month register. It is also run via the same
menu option.
6. Update of claims rebatch process (Builds ASPC-248, ASPCCLMS-040, ASPCUTIL-089):
We have added an option to reset secondary claim flags
while processing primary claims rebatch utility. In addition to the
builds listed above, the same program is also used for all ECS systems (DBNSF, DBW837, DBW837A,
DBW837B).
7. Electronic statement submissions (BUILD 248): We have added the ability to
generate a text file for Electronic Statement Submission
using the generic Envoy statement form. To process, select the normal Envoy statement
from ASPC's main menu. Select (at minimum) the
following options: check-Batch print; check-Are forms preprinted?; uncheck-Are forms
preprinted with your address?. You will then be
presented an option to run ESS. Do not forget to select your other options (i.e. Query,
Transfers, etc.)
8. Deposits/Charges files updated with new fields (BUILD 255): We have added two
new fields to each charge -- Financial Class (FC) and
clinic ID (CLINIC). FC is being added for flexibility for user reporting purposes using
Lister, and it will not be visible or
available for edit. FC is per PATIENT file record. CLINIC may be edited from charges form:
main/edit entry screen, add charges screen
and charges confirmation screen (if the user has it turned on). Each location has an entry
field with a tool button for easy
lookup/selection.
Deposits files were updated with a user defined field (MYFIELD) and (based on charges transaction)
FC, CLINIC, DOS, CLM_CPT, HOSP, DIAG1,
AMOUNT. Excluding MYFIELD, none of these fields will be available for edit during deposits entry.
They are simply being copied to the
deposits files in order to allow users to reference them when using Lister for revenue (receipts)
reports. Note that they
will only be copied to the deposit record if the user elects to tie that deposit
to a specific charge. Otherwise, it is not possible to get this data.
MYFIELD is available for entry on both the regular deposits (tab) screen and from claim
payments screen. This is a 10 character field
upper/lower case entry containing whatever the user wants. Besides using MYFIELD for user
generated reports via Lister, please see item
#8 below for new A.R.M. report
9, New reports in A.R.M. (ASPCCARE BUILD 157): We have added two Payment Summary
reports. The first, will be a list of deposits by
Myfield contents. This will allow users to use this new field to statistically report on
deposits by any criteria that they choose.
The report is available for one patient or all patients, for the current month or for
both the current and all previous months, and
a query is allowed on the deposits (and oldpay) files. The report is sorted by the
contents of the myfield, and by date of deposit within
myfield. The report has separate columns for cash, insurance and adjustments, as well
as a totals column. It provides for DBF output
should the user wish to graph or otherwise use the data.
Similarly, the second report is by Hospital ID (sorted by deposit date within each HOSP
field). In both reports,
user can elect to skip payment records that do not contain MYFIELD or HOSP data (depending
on the report selected) without setting a query.
10. New system index and view. (Builds ASPC-256, ASPCUTIL-092): A new system index
on prior month charges (CLAIMS.DBF) and a new view for
user created reports (Field Lister) of prior month payments (by line
item) has been added to the system. Claims index is named INVTRN and its indexed expression
is invoice number plus transaction number to
allow lookups from payments files. The new view is named DEPCHGO. Prior month's payments
(OLDPAY.DBF) file is the parent database. It
is related to CLAIMS (INVN_MBR+TRANSNUM), PATIENT (ACCTNO), DOCTOR (DOCNO) and INSUR
(INS1).
To get an accurate line item report, user must set a minimal query that excludes OLDPAY
and CLAIMS file records that have no transaction
number (i.e. ".NOT. EMPTY(OLDPAY->TRANSNUM).AND..NOT. EMPTY(CLAIMS->
TRANSNUM)").
11. Referring Provider added to payment files (Build 256): As in item #7 above, we have
added RPHY. If line item charge is selected and the
charge contains a referring provider it is automatically recorded with the payment.
12. Update to ASPCBILL for new charge fields (Build 120): FC and CLINIC fields (see item #7
above) will
update during ASPCBILL batch processing. Financial Class is from the patient's data. Clinic ID is
entered based on the treating provider for the line item charge.
13. New class "G" procedure class in DOS and Windows platforms (Build 257 Windows):
The new class "G" code is based on class "F" except
that last appointment and visits counters are not updated. Class "F" code procedures do not
appear on claim forms, prevents the month-end
closing routine from purging a "no-charge" procedure and posts the charge as though the patient
has 0% insurance coverage.
The new "G" was not implemented in ASPCBill since this type of procedure will not occur.
14. Modification to new charge and payment CLINIC field (Builds ASPC-258, ASPCBILL - 121):
We have modified the recording of Master
Clinic in charges and payment files to ID = "00". This will allow users to differentiate between
old records which have no clinic ID
(because of the recent upgrade) and new records for Master Clinic. Other data files (i.e. DOCTOR.DBF)
will continue to record nothing
when the master clinic is desired.
15. Modified ECS chiro claims in CT (DBNSF Build 288 and DOS): We have made a modification to
segment EA0 position 242 for submissions
to Trailblazers of VA as they required.
16. Modified ECS claims in OH (DBNSF Build 290 and DOS): We have made a modification to segment
FA0 position 193. This position will print
"N" indicating that the provider is not a hospice doctor.
17. New HCFA claim options (DOS/Win) and revised (Win) claim option forms (Builds ASPC-262,
ASPCCLMS-041):
We have completely revised the appearance of (Windows) claim options form by sorting the options in
HCFA box number order. This affects ASPC, ASPC Claims and the master options for all ECS programs.
In addition, we added two new HCFA options. The first is for box 24e to print all diagnosis codes for
Medicare claims. Normally, we only
print the first one. The second option is for box 33. It allows group number to print to the right of the word PIN# (rather then printing
to the right of text Group#).
18. Global update to memo related utilities, DBC error system and memo related applications (Builds
ASPCUTIL-093, DBCUTIL-024, ASPC-263, DBAR-106, DBMAIL-202): Since memo fields always have a higher
vulnerability to corruption, we have made a number of changes to reduce and/or better handle fixing of
memo fields/files.
Most of the changes will be transparent to the user with the exception that corruption will be reduced.
There two things users should
notice. Memo bloat utility will automatically run the test/fix memo fields application prior to doing
there own task. This is to insure
the requested task is running on a good file. Otherwise, we may create additional problems.
Second, we have set a method for handling "Blob" errors. This error is a hard error and causes instability
in the application. Therefore,
we mark the record for deletion and have the application end. The user can then backup and rerun the app.
to eliminate the record
permanently by packing the file. Appropriate messages are displayed for this error.
19. Update to Memo Fix Utility (Builds ASPCUTIL-095, DBCUTIL-026): We have added additional tests
(optional) and correction of memo
field contents via the memo fix utility. Contaminated records may contain some uncommon low or high
ASCII characters. We now test/report and/or eliminate these characters.
In addition, we also test the first 6 characters (if all numeric) with the account number in the
database. Since our time stamp
function outputs the account number there, this may report contamination. Since this test is obviously
not precise, we can not
provide a programmatic record fix.
20. Update to DBCUtil (Builds DBCUTIL-027, DBAR-107. DBMAIL-203): We have added optional printer
output to Memo Fix Utility. In
addition, Emergency Recovery, Logon and all Change Data File items were added to Utilities in
DBCUtil.
21. Updates to electronic claim programs (Builds DBNSF-293, DBW837B-027): We have updated data
reported with regards to secondary
carriers in 837B claims for DOS and Windows. NSF Florida claims (DOS/Windows) were also updated to
accommodate their new
multi-carrier system.
22. Update ASPC for new Spectrasoft software (Build 269): With the new version of appointments
software, the program name has changed
to APPTS32.EXE from APPTS.EXE. We have modified ASPC options to allow either program as an acceptable
program name for selection and use.
The default dialogue will now show either or both file names if they exist in the selected directory.
Please note, it is possible to set program location and name from anywhere appointments is called to
run from (only if it was not
previously defined). You can always define this from the main menu Utilities/Options/Appointments.
This is where users of APPTS.EXE who
upgrade to APPTS32.EXE will have to go to change the setting.
23. Upgrade to ASPC and ASPCBILL adding UNITS, POS and TOS (Builds ASPC-270, ASPCBILL-123,
DOS-ASPCBILL):
We have added the ability to scan units, type and place of service codes with each line item
(CPT scan). In ASPC, this is done via AutoPay. The record layout is per the new ASPCBILL
specification document and overrides current data.
We continue to use PRCODES or default values when current data is not
available. Each entry is an override for that cpt code/line item only.
End of version 7.0 enhancements
back to topFall 2000 Release
AS/PC ® for Windows -- Version 6.0
(Starts with Build #207) - March 24, 2000
1. New warning message in monthend closing (Build 207): We have added one final warning message to allow users to abort the monthend closing.
2. DBC note archiving utility (Builds ASPC-208, ASPCUTIL-078, DBCUTIL-014, DBAR-086, DBMAIL-184):
We have added the ability to archive patient notes (customer notes in dBMail/dBar) to ASPCUTIL
for AS/PC and to DBCUTIL for dBMail/dBar. After the notes are archived to their new files, the system
compacts the original note
files. Users may view individual customer or patient archived notes
in the the Add/Edit Patient (Customer in dBMail/dBar) screens via new menu selections that have been
added to these screens. All archived
notes may also be viewed via File/Browse (and then select the archived note file you wish to browse).
Note: Archived note files are named by the system as NTmmddyy.DBF, where
mmddyy is the current month, day and year.
The new feature is available via Utilities|Memo File Maintenance in DBCUtil and ASPCUTIL. The feature allows you to archive (copy or move) notes from the dBMail MAILNOTE file (via DBCUtil) or the AS/PC PATNOTES file (via ASPCUTIL). You have the option of using a query on the note file and the master file (Patient or Mail) as a means of selecting which notes you which to archive. When you archive, you can either COPY or MOVE the notes. If you COPY the notes to the new archive file, the original notes are left in tact. If you MOVE the notes, the notes are deleted from the original note file after they are moved to the new archive file. When the notes are moved, the system performs some basic maintenance on the original file, packing it and clearing out any excess space (this wasted space is called memo file bloat).
The system always creates a backup of the original note file before the archiving process is begun. The user can ask the system to keep this temporary backup after the archiving process has been completed.
The note file data bases can become quite large over time. This feature allows users to periodically reduce the size of the main note files while keeping less current notes in separate archive files. Since you can set a filter using both the master file and the note file, the criteria by which you can select records to archive is very flexible. If the new archived files are left in the user's data directory, they will then be available from within the main systems for read-only viewing.
Note: Records in archived note files may not be edited. They may only be viewed.
3. New Minutes Field for Anesthesia Minutes in Charges Entry (Builds AS/PC - 209;
DBNSF - 269): We have added a new field to the charges
transaction files, MINUTES. This field is only to be used for NSF ECS tranmissions where
Anesthesia minutes must be reported in record
FA0, positions 87-89. The field shows up on the charges confirmation dialog during new
charges data entry. It also shows up on the charges
edit screen.
In DBNSF, the system checks the INVGET MINUTES field for each charge. If that field is
NOT EMPTY, then the system prints the contents of the
field in FA0, 87-89.
Important -- Users must not use the minutes field unless they want it to print in an
NSF submission!
4. New Date Functions for Queries (all systems, all builds after 04/30/2000):
DB550009.FNF is a special DBF file that contains descriptions of all valid dBase and DBC
developed functions that may be used in Queries,
merge fields, etc. DBC has expanded the normal list of dBase functions in this file over time
to add convenient functions that allow the user to
create better reports and queries.
The current addition contains 3 new functions for doing date comparisons. dBase queries are
limited to 255 characters; and when doing date comparisons,
the user must always check for the EMPTY condition of the date field in question. This can
take up quite a few of the allowed 255 query characters.
The purpose of the 3 new date comparison functions is to allow the user to do the comparison
and to check the EMPTY condition of a date field in one short
command which can easily fit into reports or queries.
The 3 new commands are:
I. IsDatLNE(dDate, dCompDate) -- Compares dDate to see if it is less than
dCompDate and is also not empty.
Usage.......: IsDatLNE(ANNIV, {07/21/2000})
Returns.....: Logical .T. if dDate < dCompdate and dDate is not empty.
Parameters..: dDate = date we are checking
dCompDate = date to compare dDate to.
II. IsDatGNE(dDate, dCompDate) -- Compares dDate to see if it is greater than
dCompDate and is it not empty.
Usage.......: IsDatGNE(ANNIV, {07/21/2000})
Returns.....: Logical .T. if dDate > dCompdate and dDate is not empty.
Parameters..: dDate = date we are checking
dCompDate = date to compare dDate to.
III. IsDatENE(dDate, dCompDate) -- Compares dDate to see if it equals
dCompDate and is also not empty.
Usage.......: IsDatENE(ANNIV, {07/21/2000})
Returns.....: Logical .T. if dDate = dCompdate and dDate is not empty.
Parameters..: dDate = date we are checking
dCompDate = date to compare dDate to.
Other Date Syntax Shortcuts -- dBase has a variety of allowable syntaxes when using date variables
and database date fields in queries and reports.
Here are some hints that will make your date functions more precise:
A. Use the bracket ({}) syntax to express real dates instead of the longer
CTOD() syntax. For example, {07/04/2000} is shorter and easier to read than
CTOD("07/04/2000"). In dBase 5 as used by DBC in its
Windows systems, the bracket syntax is quite acceptable and also executes much faster than
the conversion function CTOD().
B. The DBC EMPTY() function can be applied directly to a date variable or field. No other
conversion is required. For example,
EMPTY(ANNIV) works fine, and you do not have to use the longer, more
confusing, and slower EMPTY(DTOC(ANNIV)).
Examples of date queries using the new DBC functions:
A. IsDatGNE(ANNIV, {01/01/2000}) -- Will only select records where
the date field ANNIV is greater than 01/01/2000, and where ANNIV
is not an empty date field.
B. IsDatENE(LASTAPT, {04/01/2000}) -- Will only select patient records
where the last appointment date is equal to 04/01/2000, and where the
last appointment date is not empty.
5. Security enhancement to patient file (5/19/00, Build 211): We've added two new
fields to the patient file that will record the Shift
ID of the user who creates a patient record and the Shift ID of the last user to edit a
patient record. This enhancement allows the user
to trace who originally entered the patient as well as the last person who changed that
patient's data.
6. New audit report sort (5/19/00, Build 211): We've added the ability to print
the Audit Report in natural order. To access this
option, go to Daily|Daily Audit, and you will given the option to print the report in natural order.
7. Addressing super statement to patient/guarantor (05/19/00, Build 211): Until now,
the super statement has been addressed to the the
insurance carrier. With this upgrade, you have the option to address it to the patient or
guarantor instead. When generating a super
statement addressed to the patient, the name of the primary insurer will print under the
name of the patient's employer. For the
patient's super statement, the employer's name will print, but the address will not, as
in the following example:
EMPLOYER: DB Consultants, Inc.
INSURANCE: BC/BS of Pennsylvania
8. Custom descriptions for insurance payments (05/19/00, Build 211): When entering
an insurance payment that doesn't cover the entire
amount of the claim, you are given the following options for handling the balance: "write
off, transfer, or ignore." In the past, if you
selected "write off" AS/PC would automatically enter an insurance adjustment with the
description "FORGIVE." Now you can enter a brief
descriptor of your choice to replace "FORGIVE." Beneath the option to "write off, transfer,
ignore" the balance, there is a field
to enter your descriptor. "FORGIVE" will remain the default if no descriptor is entered by the user.
9. New user HCFA 1500 option for Box 27 -- Accept Assignment Box (05/19/00, Builds AS/PC - 211,
ASPCCLMS - 033, DBNSF - 270, DBW837 -
159, DBW837A - 155, DBW837B - 016): This box was active only for government (Medicare/Medicaid)
claims. Now you can activate this box
for any financial class. Note: The change primarily affects AS/PC. The remainder of DBC systems
listed were updated since they share the
same claim options form.
10. "Unpay Claims" (05/19/00, ASPCUTIL Build 079): We have added the ability to unmark a
claim as paid via the ASPCUTIL program. You can
access this option from the ASPCUTIL menu selection Claims/Charges|Unmark Paid Claims. A list of
all paid claims for the selected
patient is displayed. You then select the appropriate claim. After using this option, all
transactions on the claim will have the PD
field changed to F (false).
11. Patients Not Seen Report and Patients Without Payments Report (05/19/00, ASPCCARE Build 152):
Two more very useful reports added to
AS/PC ARM. The first report lists key data for all patients who have not had an appointment for a
period specified by the user in a query,
from one day to as long as you like. Similarly, the second report lists all patients who have not
made a payment for the period
specific in a query.
12. New Patient Retention Report (06/01/00 ASPCCARE Build 153): Report was modified to
include account number, first name
and middle initial in the patient referral column. Previously, the report listed the referral's
last name only.
13. dBar and dBMail help (07/07/00 Builds dBar-090, dBMail-188): dBar (and dBMail) help
was updated to context sensitive IDs.
14. New York Attending C4 Form (07/17/00 DBWNYAT Build 028 and DOS DBNYNEW): We have added
the ability to print C4 laser form in both
the DOS and Windows versions. We also modified the statements format to allow laser printing.
15. Yellow highlights in all active data entry fields (08/31/00 Builds ASPC -
220, ASPCBILL - 119, ASPCCARE - 154, ASPCCLMS - 035, ASPCUTIL - 081, DBAR - 091,
DBCUTIL - 016, DBMAIL - 189, DBNSF - 274, DBNYATPT - 010, DBOHBWC - 117, DBW837
- 161, DBW837A - 157, DBW837B - 018, DBWHIATT - 009, DBWNYAT - 029): When in
edit mode, the currently active field will show up as yellow to make it easier
for the user to locate the cursor.
16. Added the option to turn off bubble help in all DBC Windows Systems (08/31/00 same builds as above in #15 Yellow highlights...): This option may be set by each user from each systems' main menu Utilities/Options/Bubble Help Toggle. The setting is memorized by user ID for future sessions.
For users who like bubble help but may want to temporarily disable it in certain forms and/or at certain times, we have also added the ability to turn off bubble help temporarily for most DBC forms from the form's Utilities menu. This temporary switch expires when the user exits the form.
17. MYFIELD for patient and mail data files (08/31/00 Builds ASPC - 220, DBAR - 091): MYFIELD was added to AS/PC (DOS and Windows) and dBar as a user definable field (similar to the same field in our other files). The field may be edited from the 2nd tab/page in the Windows version, and from the first screen in the DOS version.
18. Insurance Payment Analysis Reports (09/13/00 ASPCCARE Build 155): We have
added a "Totals by Carrier" report to the eight current
reports. The menu selection is Payment Analysis/Insurance Payments/Summary Report by Carrier.
19. Total Payment Analysis Reports (09/13/00 ASPCCARE Build 155): We have added nine
reports similiar in format to Insurance Payment
Analysis Reports. These reports list all charges and payments. The menu selection is
Payment Analysis/Total Payments/...the specific
desired reports.
20. Merge Letters (09/15/00 Builds ASPC - 224, DBAR - 093, DBMAIL - 190, DBCUTIL - 017):
We have updated merge letters to allow sorted output when batch printing.
Users may select any system or user
created index.
21. Patient month-end statements optional address (10/11/00 ASPC Build 225): We
have added additional name and address fields to the
patient file for optional mailing address on month-end statements. This includes the
"Monthly" and "Short Form" statements. The fields
are located on the INS3/4 tab of the Patient Add/Edit/View form. The statements listed
already have an option to be addressed to the
Guarantor. This new option overrides the Guarantor address selection
should the user select both.
22. Detailed Daily Audit Report additional sorts and limits (10/11/00 ASPC Build 225
Windows and DOS platforms): Added to the
report was an option to sort each of the six sections by provider. In addition, the user
may limit the report to a single shift ID.
23. Viewing/selecting transactions when applying payments (10/11/00 ASPC Build 225):
We added an additional button labeled
"All Trns" on the payments tab of Bill/Charges/Payments form that will bring up all
charges/transactions (CLAIMS.DBF and INVGET.DBF) for the patient. The previous toolbutton
for selecting a
transaction from current charges remains. For possible performance issues, it is recommended
the user select the current charge tool
button.
24. Reprinting multiple claims (10/11/00 Builds ASPC 225 and ASPCCLMS 036): We added
the ability to reprint multiple unpaid claims
for a single patient. This option allows the user to select individually (by claim number)
all desired claims at one time via
DBC's Mover function.
25. Viewing patient comments field from charges form (10/11/00 ASPC Build 225): We
have added the display of PATIENT->COMM field and the
new MYFIELD from the charges and payments form. Due to screen limitations, this was
accomplished via a tool button/popup. It is
located towards the top right hand side of the form preceded with the text "Other Info".
Like most tool buttons, the popup is available
during entry (in edit mode) as well as when just viewing either
tab page of the form.
26. Transaction report button on payments screen (10/20/00 ASPC Build 226): We
have added a "Tran Rpt" button to Bill/Charges/Payments form
(payment tab). After pressing the button, the only prompt is for Output Setup. This is a
very quick way to run the report based on the
normal report's default responses.
27. New Copy To Feature on Edit Menu (12/07/00 Builds ASPC-237, dBar-098, dbMail-195):
We have added the ability to append single
records to a new file from the edit forms for patients, carriers,
providers, and referring providers. When in these forms, you can select Edit|Copy To, and
the system will copy the current record only
and append it to a new file. If the new file does not exist, it will be created. Otherwise,
the user is given the option of overwriting it
or adding to it with the current record. The same feature has been added to dBar and dBMail
for the master file and the Salesman file.
The name of the new file created by the system depends upon which form the user is in:
Edit Form
New DBF Filename
AS/PC:
Patient
TPATIENT
Carriers
TINSUR
Providers
TDOCTOR
Referring Providers TRDOCTOR
dBMail:
Mail
TMAIL
Salesman
TSALESMN
Note that this feature has numerous uses. Users can now quickly build a new file from selected records when a query is not feasible. This
new file can be used for labels, Excel, Word mail merges, etc. In dBMail, the file can be appended to a new MAIL.DBF file in a new
dBMail directory set up by the user.
28. Super Statement options (12/07/00 ASPC Build 238): We have added options to print
insurance payments only and cash payments only in the detailed line
items of Super Statements.
29. Custom Labels (01/02/01 Builds: ASPC-239, ASPCUTIL-086, DBAR-100, DBMAIL-196 and DBCUTIL-020):
We have added a dynamic Custom Labels
function to the above systems which uses Crystal Reports Engine to print a various Avery label formats.
Label data can be created based
on any DBC database file or view (up to 6 lines) in a similiar fashion to DBC's Field Lister
function. In addition, blank lines and fixed
literal lines (i.e. 'Happy New Year') can be defined by simply enclosing them in quotes. All
labels are named CRLnnnn.RPL with nnnn indicating
Avery label number. The function is called from the system's main menu File|Open|Custom Labels item.
Notes on using the new Custom Label feature:
a. Printing specific numbers of text labels -- Users may wish to create custom labels
that do not contain any database data, but are simply
literal text (e.g., "Copyright 2001 (c) Don Biresch"). The label printing
program will still cycle through the database/view and print one label for each record allowed
by the query (or one label for each record in
the file, if no query is selected). How then does one control the number of labels printed?
Simple! You can use the xBase RECNO() function in a
query. RECNO() provides the record number. Therefore, the query "RECNO() <= 50" will
allow only 50 records to be printed no matter
what database or view is selected by the user.
For example, suppose I want to print the above copyright text on a sheet of Avery labels
that hold 24 labels. I can set my view to any database
or view that contains at least 24 records. When I go to print, I will set a query to
"RECNO() <= 24", and the system will go ahead and print
out 24 labels with my text on each label.
b. Avery label form numbers -- there are many Avery label forms available.
However, many of these are physically the same dimensions and therefore can be printed by
DBC's software using one of the formats that we have
included. In fact, the custom label feature includes just about every Avery format
available. For example the popular Avery 5160 format
(which we have included) contains 30 labels per sheet. The 5160 is identical to the
Avery 5260, 5560, 5660, 5960, 5970, 5971, 5972, 5979,
5980, 6241, and 6460 formats.
End of version 6.0 enhancements
Spring 2000 Release
AS/PC ® for Windows -- Version 5.0
(Starts with Build #171) - July 1, 1999
1. Printing mailing labels for paper claim submission: We have added the capability to print unique carrier mailing labels based on a user specified query on the insurance register. From Reports/Crystal Reports/Labels, the user should select the predefined labels named CLB25160.RPL or CBL25161.RPL. When you click on the index selection button, a query may be entered and processed. Note that the normal query button does not work for these two predefined labels.
2. Report Text Preview Screen (7/15/99, Build 173): The DBC report preview screen
has a new RESIZE button that allows the
user to easily expand the size of the preview window on systems with resolutions higher
than 640 x 480. Click the new button
to display the maximum sized preview screen for your monitor.
3. Functional Acknowledgment 997: (7/15/99, Build 837B-10, 837A-149, 837-153) We
have added the ability to view/print a listing or a
report of FA997 file in 837 systems. The listing is simple listing of the file with
indentation per segment as well as an optional segment
counter. The report is a descriptive report of the acknowledgment which may eliminate
the need to have
FA997 documentation present for interpretation.
4. Sort Monthend Patient Statements(8/03/99, Build 181): Users may now request that
the monthend patient statements be sorted
by Zipcode, Social Security #, Last name (the default), or account #.
5. User Queries Listed in Smaller Font ((8/03/99, Build 181): Many of the reports in our
systems list the user defined query, if any, that was used to select the data to list on that report.
It is normally listed at the end of the report in the system's normal Courier font. This font
limits us to printing 79 characters
per line. We now list the user query using the Courier New 8 point font, and we can therefore now
list up to 132 characters per line.
6. ZIP2 Added to Carrier Address on HCFA Claim(08/06/99 Build 182): We have added the extended zip code to the optional carrier address printed at the top of HCFA paper forms.
7. Financial class added to clinic receivable aging report in AS/PC Care (08/18/99 Build 148):
Clinic receivale reports may now be run by
provider, patient or financial class. As in the two previous versions, financial class s
ort can be printed for each clinic or for
the entire practice.
8. Printing patient ledger from patient form (08/19/99 Build 183): We have added
the ability to print a single patient ledger from the
patient form. The selection is accessed via the forms Reports menu items. DBC standard
output selection form is used. The report can
be printed to screen, file or printer.
9. Printing patient aging from patient form (08/19/99 Build 183): We have
added the ability to print a single patient A/R aging from
the patient form. The selection is accessed via the forms Reports menu items.
DBC standard output selection form is used. The report
can be printed to screen, file or printer.
10. Audit function for deleting/recalling charges (09/07/99 Build 184):
AS/PC creates a "CHGAUDIT.DBF" data file (in the user's data
directory) the first time a charge transaction is deleted or recalled. All data
for the transaction is copied to this file. A
separate record is created for each deletion or recall.
Under Bill in the AS/PC main menu, "Charge Deletions" was added with 2 selections.
The report item prints a listing of CHGAUDIT.DBF. The
user may select a query to limit output. The Maintenance menu item allows
permanently deleting entries in CHGAUDIT.DBF as the file may
become large in size. Like the report, the maintenance item allows a query to
limit which records are permanently purged from the data
file.
In addition to copying the entire charge transaction, CHGAUDIT.DBF contains
"FLAGDEL" (logical) field. This field contains true if the record is
deleted or false if it was recalled. As in the charges
files, the "LEDIT" field contains the date the change occurred. This information
is important since the user may have a need to create a
custom report via DBC's Field Lister.
11. New payment type codes when applying carrier/patient payments (09/07/99 Build 184):
We have separated patient payments into 2 codes (PA for cash payments and
PK for check payments). In addition,
we have added an IE code for insurance EDI payments. The old IN code will
indicate carrier check payments. This was added for future AS/PC
development and DBC's new AutoPay 835 remittance advice automatic data entry program.
The Daily|Daily/MTD Daysheet|Summary report has been revised to report total
payments by PK (patient check), CC (credit card) and PA (Patient Cash) .
12. Precise file insert function in memo (note) fields (global change in
all DBC software 9/14/99, Build ASPC-184, ASPCUTIL-73,
dBar-74, dBMail-176): Memo (note) fields exist throughout DBC software.
They include: patient notes, daily notes, customer and user
notes. We have enhanced file insertion to be precise at whatever the user's
cursor position is. Previously, the file was added to the end
of the note.
13. Error log easy access (global change on 10/07/99; Build ASPC-187,
dBar-75, dBMail-177): Users may view/print any error logs that
may exist in their data directories via File|Open|Error Log. In dBar and AS/PC,
users can also view or print the monthend abort log
if one exists.
14. New York Medicaid Claims were updated (10/08/99, Build #29 ASPCCLMS):
Box 24H claim line item amount will now retrieve Medicare allowed amount
for secondary claims made to Medicaid when Medicare is the primary carrier.
The amount will come from PRCODES.DBF file in field
"MYFIELD".
15. Idapi Maximum File Handles Set Automatically (10/19/99 Build ASPC#189):
The system now checks the user's Idapi configuration to
ensure that the Maximum File Handles is set to at least 60. If it is not, the
system will set the value to 60. A file
named LMAXF.CFG is created in the user's program directory to indicate that
the Maximum File Handles setting has been updated.
Note that this effects all DBC systems, including dBMail.
16. Utility to update problem counters in AS/PC for Windows, dBar and dBMail
(Build# ASPC-190, dBar-76,
dBMail-178): We have added a utility to update problem counters. This
function is important since
we provide a problem indicator in the respective systems customer/patient forms.
The process requires exclusive use of patient or mail
databases. It resets all problem counters to zero and procedes to recount open
problems. Function access is from Patient/Customer main
menu selections under Update Problem Counters.
17. DOS and Windows HCFA 1500 Claim form update for Medicare (Build#ASPC for Windows-190,
ASPCCLMS-30): Due to Medicare requirements for several states, a new
procedure code field (PRCODES->BOX24E) has been
added to the file. Box 24e (diagnosis code) on the HCFA 1500 will now
print the contents of this field (if it contains data) for Medicare
patient claims only. To ignore this new feature, simply do not put anything
into this new field in the CPT code edit form.
18. DOS and Windows HCFA 1500 Claim form updte (Build# ASPC-191, ASPCCLMS-31): Box 24d for MA Worker's Comp. was updated to print CPT codes per the rev. requirement. Box 33 for WI Medicare was updated to print group number at PIN location.
19. dBar Packing List (Build# 77): We added a packing list form to dBar. The form resembles charge slips without any dollar information. The function can be accessed from Charges/Payments form by selecting the report menu item or button then selecting Packing List in the prompt that follows.
20. DOS and Windows NSF Electronic Claims Update (Build 265): Two state
codes were added. Code "NG" for processing claims by Noridian
Government Services and code "MP" for South Carolina Clearinghouse. In addition,
special state codes "KEY" and "RR" were modified for
recent changes.
21. DOS and Windows NSF Electronic Claims Update (Build 266): XRAY
date (exists) logic for Chiropractors was eliminated from the claims.
Checks for XRAY dates were also eliminated from Data Check Report in DBNSF
and Carrier Data Audit Report in AS/PC main system.
22. Windows systems NT 4.x Context Help With Generic Pop-up Dialog Boxes (Build 198):
We have added an update to all pop-up generic DBC
dialog boxes that allows us to provide context sensitive help with these dialog
boxes under NT 4.x, as well as Windows 95/98.
23. Improved AS/PC Windows trial systems security and extend trial expiration date (Build 199):
We have eliminated users ability to
run an AS/PC trial version on a system that is registered. In adddtion,
the trial expiration date was updated to 05/24/2000.
24. Problems with 0 amounts circumvented (Build 202): In some obscure cases and only on certain computers, we have noticed a bug that causes zero numeric amounts to evaluate to non-zero values. This causes numeric comparisons to provide incorrect results. Although this problem was not in our software and appears to be hardware related, we have rewritten sections of our programs to work around the problem.
25. Incremental searching on last, first (Build 203): We have modified
the last name index expression for MAIL.DBF, REPS.DBF, and SALESMAN,DBF in
dBMail/dBar and also for PATIENT.DBF and DOCTOR.DBF in AS/PC. The
reason for the change is so that users can now access an entry directly by
entering the last name and then a comma followed by some letters of
the first name.
For example, entering "SMITH,D" will take you directly to the first D. SMITH
on file. Note that you must not enter a space between the comma
and the first name. For this update to work, the new DBDICT.DBF file must be installed in
your data directory, and then you must reindex your files the next time you run AS/PC or dBar.
Note: The data dictionary, DBDICT.DBF, for dBar/dBMail and the one for ASPCWIN are not
interchangeable. Do not install one in the other program's data directory!
26. Yellow search control when in focus (Build 204): The DBC Seeker
search control that is on all forms that have a look-up capability
is now yellow whenever it is the active control (i.e., it has focus).