Another approach would be to use SQL Server Integration Services to handle your files. You could:
1. Download the file from a secure FTP site.
2. Provide a report on what files were downloaded.
3. Parse the files.
4. Show reports on what you got from the files.
5. Enter the information from the files into your database(s).
This screenshot shows the SQL Server Integration Services Package used to download 837 remit files from our clearinghouse, RealMed.
![[Linked Image from ]](/ub/attachments/usergals/2012/03/full-2117-191-filedownload.jpg)
This screenshot shows the configuration of the Secure FPT component.
![[Linked Image from ]](/ub/attachments/usergals/2012/03/full-2117-192-sftp.jpg)
This screenshot shows the report from the file download package so we know what files came in. Notice the parameters you can choose from to narrow down your search.
![[Linked Image from ]](/ub/attachments/usergals/2012/03/full-2117-197-downloadedfiles.jpg)
This screenshot shows the autopayment posting program in SQL Server Integration Services. The Post Payments box does all the heavy lifing as far as posting the files goes.
![[Linked Image from ]](/ub/attachments/usergals/2012/03/full-2117-194-app.jpg)
Here is the contents of Post payments box. This shows a very small partial code listing.
![[Linked Image from ]](/ub/attachments/usergals/2012/03/full-2117-195-appcode.jpg)
This report shows the bad transactions that auto posting could not post and the error why. There are other reports for good transactions (those that came in without error) and denied transactions.
![[Linked Image from ]](/ub/attachments/usergals/2012/03/full-2117-196-badapp.jpg)
I don't see why you can't do something similar with HL7.
JamesNT