List of Features

Top  Previous  Next

 

List of Features

 

Files

Command

Description

most files

lmargin=x

causes the left margin to be moved right x columns.

most files

prtsetup=xxxxxx

used mostly for laser printers. This gives codes7 to be sent to the printer prior to printing

most files

prtreset=xxxxxx

used mostly for laser printers. This gives codes to be sent to the printer after printing

most files

rptlength=66

used mostly for laser printers. This changes the length of the text in the file.

M6R1885.CTL

ignoreopenitem=yes

will cause the transaction deletion program to delete transactions as though the account is not open item

M6R4.CTL

2-up=yes

will cause the right side of the statement to print giving a "2-up" statement. Report width=130

M6R4.CTL

alternating=yes

similar to 2-up=yes except that the "insurance" side will print on the next form; allows using the 1-up statements

M6R4.CTL

amtdueinbox=yes

suppresses printing the patient balance in boxes and instead prints amount due

M6R4.CTL

amountduenow=yes

will print "Patient amount due now" on open item statement

M6R4.CTL

printdx=no

suppresses diagnoses printing on statements

M6R4.CTL

prtpvbottom=yes

will cause the provider name to print at the bottom of the statement

M6R4.CTL

prtpvtrxline=yes

will cause the provider lookup code to print on the statement transaction line. Optionally use with prtrefdr so the provider name is at the bottom of the statement

M6R4.CTL

prtrefdr=yes

will cause the referring doctor name to print on the statement

M6R4.CTL

rejectpaper=no

will cause the form to be created even if there are errors like missing name &/or address. An audit is created

M6R4.CTL

rptskipdays=x

causes x days to be skipped before printing a transaction on a statement. If a patient came in every x days they would never get a statement

M6R4.CTL

stopsmtaging=yes

suppresses printing aging on statements

M6R4.CTL

stopsmtbalance=yes

suppresses printing the patient balance on statements

M6R4.CTL

smpaoic=0

0=use common setting, yes or no override the common setting

M6R4.CTL

doopenitm=yes

process open item accounts on regular statement run (401)

M6R401.CTL

doopenitm=yes

process open item accounts on regular statement run (401)

M6R401.CTL

alternating=yes

like '2-up' above but works with 80 column printer: prints next statement with charges only, for insurance billing

M6R401.CTL

docontrolcode=1

will cause the 401 stmt program to only look at patients with data control code=1; if you put 12 then it will look at patients with code=1 or 2

M6R401.CTL

doopenitm=yes

will cause the 401 stmt program to print open-item patients

M6R431.CTL

prtchgifnoins=yes

print charges without regard to activity if no insurance is registered for patient

M6R5.CTL

amountdecimal=yes

causes decimals to print on the  CMSforms. Default is no

M6R5.CTL

barcode=xxx

xxx=yes causes the ins co name to start printing at position 45 (avoids the bar code). if xxx is a number (15-55), the ins co name will start printing at that position

M6R5.CTL

Bx19keyedclaimtype=xx

xx=value to be put in CMS 1500 box 19 for "keyed claim type" XE "Keyed claim type"

M6R5.CTL

carriernumber=xxxxx

the Medicare carrier number, taken from the federal register. (ex: 951=WPS in Wisconsin)

M6R5xx.CTL

clearinghouse=xxx

the clearinghouse/carrier which will receive your transmission. ex: xxx=carevu,ets, and others which are predefined by Stratford

 

m6r5xx.ctl:

At this time we continue to support many special forms for different carriers, specialties and state requirements. We believe there is a trend away from many different forms and possibly in the future every insurance company will accept the CMS 1500 form for medical and the ADA form for dental. There will continue to be different requirements for completing the form and the codes in this file are the way that the Stratford program will know how to print the form for you. The Stratford program can print almost any type of claim at this time using the numbered series: 511-519 and 561-569. These programs are matched to the integrated EDI programs 911-919 and 961-969. The EDI programs in the 911-919 and 961-969 series are programmed to transmit in either the National Standard Format (NSF) or the ANSI 837 format. You may only transmit the dental forms using ANSI 837. At this time we believe the ANSI 837 format (or its successor) will eventually replace all other formats. We are not doing any NSF updates except for those carriers that will not accept the ANSI 837.

 

m6r1885.ctl:

ignoreopenitem=yes

This is for the transaction deletion program.

Description: ordinarily no transactions are deleted unless the charge has a zero balance. If the balance is zero, the charge and its associated payments, adjustments and memos are deleted.

 

If this switch is used, all transactions will be deleted as though the account is not open item. If the deleted transactions do not total zero, a new transaction will be placed in the account to keep the patient's balance and the accounts receivable from changing. If the deleted transactions total a minus amount, a zero charge will be placed in the account and a payment will be associated with that charge to keep the minus amount.

m6r673.ctl:

bucket1=3

bucket2=4

bucket3=5

 

The 'buckets' refer to the 3 columns in this report. Please refer to a copy of the report to help you understand this discussion. The first column labeled 30-59 days is controlled by bucket number 1. The second column labeled 60-89 days is controlled by bucket number 2. The third and last column labeled >=90 days is controlled by bucket number 3. The defaults for the buckets are written above. When bucket1 is equal to 3, then the first column will show amounts that are at least 30 days past due. When bucket2 is equal to 4, then the second column will show amounts that are at least 60 days past due. When bucket3 is equal to 5, then the third column will show amounts that are at least 90 days past due. Calculate it this way:  decide the aging intervals you want, divide by 30 and then add 2. This seems complicated but most people are happy with the 30/60/90 breakdown and we are discussing this for those people who want a custom printout. Those people want to be able to control the program and to do that you must work a little. This really does not qualify as 'high math' anyway. For example you want all the people who are 1 year past due to sort to the top of each financial class. Ok, let's figure this out. 1 year is about 360 days, right?  Using the formula above we divide by 30 and we get?  (answer=12). Now we add 2 (answer=14). The final answer to the problem is 14. We did not explain it very clearly above but this report sorts bucket 3 to the top. Bucket 2 is next, and bucket1 is last. Of course, after bucket1 are the people who are current. The current people appear on this report because most accountants want the aged account listing to show all accounts who do not have zero balances. The sorting is to help you with collections. Back to the problem:  You want the people who are 1 year past due to sort to the top. To do this put the following line in your control file:  bucket3=14. This will not make sense to many of you, but if you try it and then print the report (or view it on your screen) you will see what the program is doing. If you think we are describing what you want, but you do not understand this discussion, please fax. We are ready to help you. We do not care if you learn to program the reports or not, but we do want you to get the reports you need and so we will set up the control file for you.

m6r681.ctl:

do685with681=yes

do687with681=yes

Most clients are set up so they get the 685 (financial summary production report) and the 687 (CPT production report) at the same time that they get the 680 (month end or periodic closing report). There is another report we call the 681. The 681 is exactly like the 680 except that it does not set any flags in the data files. This means it is a 'trial' 680, that is, you can create it repeatedly and see the same transactions over and over. The 680 does set flags so when you create it, the transactions are marked so they will never appear on a 680 again. This makes the 680 a true 'audit'. Some offices like to create a 681 to see if there are any obvious errors that must be corrected (like posting charges to the wrong provider in a group) before they create the month end report for accounting purposes. The switches above allow you to also get the financial summary report at the same time. By using both switches you cannot tell the difference between a 680 and a 681 except for the number in the upper left of the report.