User terms are not the entity agreement
A user click-through governs account use and acceptable behavior. It does not replace an entity-level BAA, MSA, or DPA signed by an authorized billing-company signatory before production PHI workflows.
Terms
Terms and acceptable use.
This page is the public posture for Medi account use. The signed customer agreement controls when there is a conflict, and attorney review is required before using final production contract language.
Boundary
What these terms do and do not authorize.
Medi is built for billing companies working across many client practices. That means user terms, entity agreements, and PHI processing authority are separate controls.
Human-reviewed billing work
Medi can guide, organize, and automate parts of revenue-cycle work, but billing decisions remain reviewable by the billing company and its authorized users. Guidance is evidence-backed, not a black-box coding directive.
No unauthorized PHI use
Production PHI use requires a signed business agreement and configured tenant access. Public pages and product terms do not authorize uploading PHI outside that contractual boundary.
Acceptable use
Operational rules.
Use Medi only for billing-company and practice workflows you are authorized to perform.
Do not upload PHI, payer credentials, or client data until the entity agreement and implementation boundary are complete.
Do not use Medi to create unsupported code uplift, false documentation, or payer submissions you cannot substantiate.
Keep user accounts individual. Shared accounts break auditability and may be disabled.