That's correct. I had created a dummy billing payload a while back for my own testing, but it could be done through an API.
Jeff
Is there a way of testing the billing functionality end-to-end without entering real information about a physician, patient, insurance company/policy, etc.? I imagine this would require a dummy insurance API portal that would respond to billing requests with dummy info about physician and patient for testing purpose.
--
You received this message because you are subscribed to the Google Groups "FreeMED Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to freemed-suppo...@googlegroups.com.
To post to this group, send email to freemed...@googlegroups.com.
Visit this group at http://groups.google.com/group/freemed-support.
For more options, visit https://groups.google.com/d/optout.
Is there a way of testing the billing functionality end-to-end without entering real information about a physician, patient, insurance company/policy, etc.? I imagine this would require a dummy insurance API portal that would respond to billing requests with dummy info about physician and patient for testing purpose.
The REMITT transport modules add support for pushing batches to clearinghouses. I explicitly implemented support for a few of them, as well as a generic SFTP transport.
Jeff
The REMITT transport modules add support for pushing batches to clearinghouses. I explicitly implemented support for a few of them, as well as a generic SFTP transport.
Jeff