Using Command Line Arguments (CLI)

The HIPAA Claim Master can also accept command line arguments. This is a very important feature if you want to put the HIPAA Claim Master on a scheduler and automate the processing of files or directories. Refer to Running the Application via Scheduler.

The following is the list of the command line arguments, they must be separated by commas.


1. The first command line argument is the filename or the directory path. If not applicable, leave blank.
2. The second argument or a combination of arguments contains the processing options.
P — Print.

Using the "P" option as a Command Line Argument
T — TIFF File. If "T" is used as an argument, the claim will be saved as a TIFF image file. 

See Creating Image Files from EDI for details on how to set up the Image printing capabilities. 

Be sure that you have tested the Image printing, before trying the command line mode.

Using the "T" option as a Command Line Argument
F — PDF File. If "F" is used as an argument, the claim will be saved as a PDF image. ("P" could not be used again as it is already taken by print option). 

Again, be sure that you have tested the Image printing, before trying the command line mode.
X — Export to database
S — Search. See examples further.
Q — Query against database. See examples further.
E — Create EDI in conjunction with Q you can create an EDI file, either using the default settings from the last screen or the database depending whether the module EDI Exchange is licensed.
P — If a "P" is used as a second argument, the claim will be printed without ever being displayed.
3. The third command line argument is the image output filename or the EDI output filename when you create an 837 EDI file.

If your options specify single file name, then we will have a multi-page image file.

If your options specify one file per image, then passing the image filename in the command line really only makes sense in conjunction with a query.

Search condition when you try to find one specific claim within an EDI file and create the image for it. If there are multiple matches the program creates an enumeration in the filename such as "Filename," Filename_1, Filename_2 and so on.

A SQL query against the database where you expect a limited number of results (a single record preferably).
4. The fourth argument is your Query; you should have "Q" as second argument.
5. The fifth argument is the destination trading partner that you send an EDI file to. This works only with the EDI Exchange module enabled.


6. In the sixth argument you specify  whether to use "T" Test or "P" Production database connection if you have "Q" for query as the second argument.


Using Several Arguments

You can have a combination of the above arguments. For example, "XF" will export the data and create a pdf file.


If you want to export and image an EDI file, you can use "XF" as the second option.


Using the "XF" option for export and output as PDF file

The "X" option will turn on the translator functionality and claims will be exported to the defined data source. You can only do one imaging option such as printing or image file at a time.

"PF" is not valid.


Searching an EDI File

Here is the syntax for the command line arguments:

1. First: Filename to be processed.
2. Second: Command options: 

S for search

F for PDF
3. Third: Image file full path and filename.
4. Fourth: Search conditions in the form of Pipe (|) separated key-value pairs. (This is the back slash key in Shift mode).


Keys that can be searched at this time are:

ClaimNO — CLM_01 (you can look for several claim ID's at once separating the ID's with '&' symbols)
PatientID — NM1*QC_09
PatientLast — NM1*QC_3
SubcriberID — NM1*IL_09
SubscriberLast — NM1*IL _03
BillProvID — NM1*85_09
Segment — A complete segment such as "HI*BF*3544"



HIPAAClaimPrinter.exe I:\HIPAAsuiteCommDir\Inbox\837\HCFA_1,SF,C:\Temp\Test.pdf,ClaimNo= 6073123GWD|BillProvID=123414|SubscriberLast=SMITH


Working with the Database

Example 1

Here is an example of using a database search to create an 837 EDI file.


An example of using a SQL query to create an EDI file.

The above example has:

A blank first argument since no file or directory are to be processed.
The second argument is 'QE' meaning that an EDI file is to be created using the results from a SQL query.
Argument 3 is blank, meaning we use the default file naming convention
The fourth argument lists the query.
The fifth argument specifies the ISA identifier of the destination trading partner. This works only with the EDI Exchange module enabled. If the fifth argument is blank and EDI Exchange disabled then the last setting from the Create 837 screen is used as trading partner identifier.
The sixth argument determines whether the production or test database connection is to be used.


Example 2

Another example creating an image file from a query


Creating a PDF image file from the results of a query

The file C:\Temp\ImageFile1 will contain all the images from claims that fulfill the query.


Processing EDI Files with the EDI Exchange Module Enabled

The only argument you need in this case is "Auto". The directory to look for new files and the processing options are defined in the setup screens for EDI Exchange. No further arguments are needed.

No questions yet.

Publish modules to the "offcanvs" position.