Navigation:  Automating > Using Command Line Arguments (CLI)

How to use EDI Exchange to automate processing?

EDI Exchange allows users to set different degrees of automation for file processing. There are two ways you can automate the application:

oFull Automation

oUsing Commands

 

See the details in the sections below.

 

Full Automation

To run EDI files automatically using EDI Exchange, the only argument needed is "Auto." The directory to look for new files and the processing options are defined in the setup screens for EDI Exchange. For more information on EDI Exchange automation, see Defining Auto-Processing Options.

 

 

Using Commands

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

 

The following is the list of command line arguments you may use. They must be separated by commas to work properly:

 

First Argument

Filename or the Directory Path — If not applicable, leave blank.

 

Note: Please ensure you have tested printing images before trying the command line mode.

 

Second Argument(s)

The second argument or combination of arguments contains the processing options.

oP — Print: If "P" is used as an argument, the claim will be printed.

 

 

oT — 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.)

 

 

oF — PDF File: If "F" is used as an argument, the claim will be saved as a PDF image.

 

oX — Export to database: If "X" is used as an argument, the claim file will be exported to the database.

 

oS — Send / Search: If "S" is used in connection with file creation, "QE" will send the file according to the Trading Partner settings. "S" could also be used as "search." See examples below.

 

oQ — Query against the database: See examples below.

 

oE — Create EDI: In conjunction with "Q," you can create an EDI file, either using the default command path or the database, depending on whether the EDI Exchange module is licensed.

 

Third Argument

The third command line argument is the image output filename or the EDI output filename when you create an 837 EDI file.

oIf your options specify a single file name, you will have a multi-page image file.

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

 

Fourth Argument

The fourth argument is your Query; you must have "Q" as the second argument. If you try to find one specific claim within an EDI file and create an image file for it and there are multiple matches, then the application will create an enumeration in the filename such as "Filename," "Filename_1," "Filename_2," and so on.

 

Fifth Argument

The fifth argument is the destination Trading Partner to whom you send an EDI file; this only works with the EDI Exchange module enabled.

 

Sixth Argument

In the sixth argument, you specify whether to use a Test (T) or Production (P) database connection should you have "Q" as the second argument.

 

How can I use multiple arguments?

You can combine the above arguments. Here is the sample syntax for the command line arguments:

oFirst argument: Filename to be processed.

oSecond argument: Command options (S for search, F for PDF).

oThird argument: Image file full path and filename.

oFourth argument: Search conditions in the form of Pipe (|) separated key-value pairs. (This is the backslash key in Shift mode).

 

Keys that can be searched at this time are:

oClaimNo — CLM_01 (you can look for several claim IDs at once, separating the IDs with '&' symbols)

oPatientID — NM1*QC_09

oPatientLast — NM1*QC_3

oSubcriberID — NM1*IL_09

oSubscriberLast — NM1*IL _03

oBillProvID — NM1*85_09

oSegment — A complete segment such as "HI*BF*3544"

 

What are some examples of CLI to use with the database?

 

Example 1

If you want to load data and create an image of an EDI file, you can use "XF" as the second option:

 

 

The "X" option will turn on the translator functionality and claims will be exported to the defined database. You can only do one imaging option, such as printing to a printer or an image file, at a time. "PF" is not valid.

 

Example 2

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

 

 

The above command has:

oThe first argument is blank because no file or directory is to be processed.

oThe second argument is 'QE,' meaning that an EDI file is to be created using the results from an SQL query.

oThe third argument is blank, meaning we use the default file naming convention.

oThe fourth argument lists the query.

oThe fifth argument specifies the ISA identifier of the destination Trading Partner. This only works with the EDI Exchange module enabled. If the fifth argument is blank and EDI Exchange disabled, then the last setting from the "Create 837" window is used as the Trading Partner identifier.

oThe sixth argument determines whether a production or test database connection is to be used.

 

Example 3

Here is an example for creating an image file from a query:

 

 

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

 

Example 4

Here is an example of using a database search to create a 277CA EDI file. This only works with the EDI Exchange module enabled:

 

 

oThe first argument is "277," meaning that a 277 EDI file is to be created using the results from a SQL query.

oThe second argument is Query text.

oThe third argument is Trading Partner ID.

oThe fourth argument is Optional 'T' and determines whether the production or test database connection is to be used. By default, the production connection is used.