Introduction

Top  Previous  Next

As mentioned earlier, The HIPAA Eligibility Responder can autoprocess Eligibility Requests and Functional Acknowledgments without the need to launch the program's User Interface. To do this, the HIPAA Eligibility Responder can accept command line arguments. The following is a list of the command line arguments; they must be separated by commas.

 

1.First Argument - mode
a.“auto” will process a 270 file. If no other arguments are included, all 270 files in the EDI Exchange Inbox directory will be processed.  Any other files in the Inbox directory will be ignored. If the filepath is included as a second argument, that file will be processed individually.
b.“soap” will process a specific 270 or 999 file. A second and third argument containing the file directory (including filename) and PayloadID are necessary.
c.If a filepath is used instead, only one more argument is necessary.

 

2.Second Argument – full filepath (auto, optional / soap)
a.Not necessary for “auto” process mode. If included will only autoprocess that file.
b.Necessary for “soap” mode.
c.If a filepath was used as a first argument, the following processing options may be used:
       X - Import file to database.

 

3.Third Argument – PayloadID (soap only)
a.SOAP/MIME PayloadID tied to request/response transaction. Necessary to identify request, response, and acknowledgements associated with a single transaction.

 

4.Fourth Argument – FileType (soap only, optional)
a.Used to differentiate between a request file and an acknowledgment file. If omitted, file will be processed as a 270 request.

 

The HIPAA RealTime Server can also be used to run the Eligibility Responder without the need for user interaction. It can accept 270 EDI Eligibility Request transactions, draw eligibility data stored in the Eligibility tables, and send a 271 Eligibility Response in under 10 seconds.