Map who performs each step
For a superbill, record who creates the document, who verifies the service and codes, how the client receives it and what happens if it is corrected. For a claim, map payer enrolment, eligibility checks where used, submission format, clearinghouse or direct connection, acknowledgements, rejection handling, remittance and payment posting. Name the staff role responsible for every handoff. A polished PDF and a Submit button are not evidence that the full workflow is connected.
Compare the data and the evidence returned
Use one fictional visit to identify the provider, patient, service date, place of service, procedure and diagnosis information your workflow requires. Then ask what leaves the practice, which system receives it and what evidence comes back. CMS identifies the 837P as the standard electronic professional-claim format and CMS-1500 as the professional paper claim form used in allowed circumstances for Medicare. Other payers can have different enrolment, companion-guide and submission requirements.
Test exceptions before choosing a system
Run a missing field, rejected claim, corrected claim, duplicate, client-requested superbill correction and payer payment that differs from the billed amount. Confirm that staff can see the original event, the response or rejection, the next owner and the reconciled result. Where HIPAA applies, review access and disclosure policies for the specific billing workflow; HHS explains that covered entities generally must limit protected health information to the minimum necessary for the purpose, subject to stated exceptions.
Follow one visit through two different handoffs
Using fictional data, generate a client-facing superbill and separately walk through an electronic professional-claim submission. Record the recipient, file or transaction format, acknowledgement, rejection path, correction and reconciliation evidence for each. Do not accept a PDF preview as proof of payer connectivity, or a claim button as proof of enrolment and response handling.
| Check in the demonstration | Evidence to record |
|---|---|
| Superbill and claim responsibilities are separate | Describe the observed result using fictional data. |
| Submission acknowledgement and rejection evidence are visible | Record the role, exception and any manual work required. |
| Correction, remittance and posting can be reconciled | Agree on pass, follow-up or unavailable before rollout. |
Continue with practice billing and payment workflows and practice reporting and team visibility to test the connected steps. The interactive Flor demo provides fictional examples for the discussion.
Check the claim standard and privacy boundary
CMS identifies CMS-1500 as the professional paper claim form used in allowed circumstances, while its current professional-billing materials identify 837P as the electronic professional-claim format. HHS explains the HIPAA minimum-necessary standard and its exceptions. These federal sources frame a review; the practice still needs the exact payer, clearinghouse, state, discipline and contract requirements.
| Workflow | Destination | Evidence to request |
|---|---|---|
| Superbill | Client or authorised recipient | Reviewed document, delivery record, correction path and retained version. |
| Electronic claim | Payer, often through a clearinghouse | Enrolment, transaction format, acknowledgement, rejection and corrected submission. |
| Remittance | Practice billing workflow | Payer response, adjustment, payment posting and client-balance reconciliation. |
Questions for a US practice
Separate self-pay invoicing, superbills and electronic claims in your requirements. A working invoice does not establish payer connectivity. Ask for USD pricing, define staff and recipient access, and test the exact state, discipline and payer workflows relevant to your practice.
Where HIPAA applies, review the actual cloud services, responsibilities and agreements involved. HHS cloud-computing guidance is a starting point for those questions. A software label is not evidence that a particular clinic configuration satisfies its obligations.
A few common questions
Can software that prints a superbill also submit claims?
It might, but one capability does not prove the other. Ask for the exact payer, clearinghouse, enrolment and response workflow to be demonstrated.
Does this guide determine which codes a practice should use?
No. Coding and billing decisions require current payer rules and qualified professional review. Use fictional data when evaluating software.
Prepared for clinic owners in United States. Updated . These guides support product evaluation and do not replace professional or legal advice.