Minimum necessary access
Practice and billing-company scope is enforced server-side. Users only reach workflows their role and client-practice access allow.
Privacy
Privacy posture.
Medi handles medical billing data for billing companies and the practices they serve. Privacy starts with scoped access, audit logging, and a signed production agreement before PHI work begins.
Controls
How customer data is treated.
Operational records remain tenant-scoped. Any de-identified data use is tracked separately from live billing operations and is not a shortcut around the signed agreement.
Auditability
PHI-sensitive activity is logged with user, tenant, action, and timing evidence so access can be reviewed later.
De-identified data is gated
Medi separates operational PHI from de-identified data. Benchmark or network use requires explicit rights, de-identification controls, and suppression gates before customer-visible use.
Requests
Reviewable privacy workflows.
Customer account closure and retained-record explanation
Patient privacy request support for amendment, restriction, access, or disclosure accounting workflows
Processor and subprocessor review during implementation
Incident, audit-log, and support-access review when a security event is suspected