Generate Claim.Submission transactions
Once draft -claims are saved into the database, Claim.Submission transactions can be generated and uploaded to Post Office.
Step 1. Select Claims > Find Claims from the menu.
Find Claims form opens.
Step 2. Set a search value and click Search.
The search results grid appears.
Step 3. Mark several checkboxes and click Generate. Selection is possible for claims in Status = Ready for Submission or Submission Failed.
Two transactions are going to be generated on the screenshot below:
- 1st – two e-claims to payer A001;
- 2nd – one e-claim to payer A002.
After the generation has finished Upload Transactions dialog becomes available showing the generated transactions.
Step 4. Click Upload.
Generated files are sent one by one to Post Office. If the operation is successful, then the row is marked green, if sending fails, then it is marked red.
Step 5. Click Show errors in Error Report column for the failed transaction.
Validation Report dialog opens showing all errors returned for this transaction.
Step 6. Click Save report to save the error report to your PC.
A standard Windows selection dialog opens where you need to set a place for storing. The information dialog appears informing that the file is saved. Save report link changes to Open report one in Validation Report dialog in the background
Step 7. Click OK.
The information dialog closes.
Step 8. Click Open report.
The file explorer opens showing the report location. The error report is a zipped .csv file that can be opened in Excel.
Step 9. Click Close in both dialogs and check the status of processed claims.
For a sent claim Status = Submitted to Payer, for claims in the failed transaction Status = Submission Failed.
Note: A claim with Status = Submission Failed doesn't necessarily have validation errors. Most likely, there is some general error (like a mismatch of the submission date and the current date) or the transaction has errors in another claim that failed the whole uploading. In the second case, you can unselect the erroneous claim(s) on Find Claims and try to generate/upload transactions again skipping the said claim(s) (leaving for errors resolving).