Creating EDI Transactions from the Database |
Top Previous Next |
|
The arguments above are concerned with the processing of incoming EDI files. But the export of EDI transactions can also be automated and run through the command line. The syntax is as follows:
Tip: The application window must be closed. Otherwise the CLI commands do not run.
ExampleThis example issues a SQL query and gives the file name for the 834 file: Select * from EDI_Enrollment where MemberFirstname='Frank', EDI, C:\Temp\file.834
The above command will create an 834 EDI file named "file.834" in the "C:\Temp\" directory using the results of the query "Select * from EDI_Enrollment where MemberFirstname = 'Frank'" and the last trading partner used to create an EDI file in the Create 834 window.
ExampleThis example issues a SQL query and specifies both a filename and Trading Partner ID to use: Select * from EDI_Enrollment where MemberFirstName='Frank', EDI, C:\Temp\file2.834, LOCAL
The above command will create an 834 EDI file named "file2.834" in the "C:\Temp\" directory using the results of the query "Select * from EDI_Enrollment where MemberFirstName = 'Frank'" and the Trading Partner with ID = 'LOCAL'.
TroubleshootingThe HIPAA Enrollment Master logs any use of the command line options and the reason for a missing or incorrect EDI file can be discovered through it. For example, if the query yielded no results, the log entry would look similar to the following:
A misspelled Trading Partner ID or a correct ID for an inactive Trading Partner will also log an error in creating a file.
|