Introduction

Top Previous Next

The HIPAA Claim Status Responder can autoprocess Claim Status Requests and Functional Acknowledgments without the need to launch the program User Interface. To do this, the HIPAA Claim Status 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 276 file. If no other arguments are included, all 276 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 276 or 999 file. A second and third argument containing the file directory (including filename) and PayloadID are 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.

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 276 request.

The HIPAA RealTime Server can also be used to run the Claim Status Responder without the need for user interaction. With the addition of HIPAA Claim Master, it can accept 276 EDI Claim Status Request transactions, draw data from claims stored in the Claim Master, store the relevant Claim Status request/response(s) in the HIPAA Claim Status Responder, and send a 277 Claim Status Response in under 10 seconds.