Every client practice.
One platform.
Praventa is multi-tenant by construction. Add a client practice without standing up an instance, with isolation enforced at the database layer.
Growth breaks the tooling before it breaks the clinical model.
Usually around practice number four.
The care model scales. The operating layer underneath it does not. Three things give out first.
One instance per client
- Every new practice means another environment to configure, patch and monitor
- Staff hold separate logins and re-authenticate to move between clients
- A platform change has to be rolled out N times and verified N times
Isolation held together by queries
- Separation depends on every developer remembering a WHERE clause
- One missing filter in one report exposes another client's panel
- The control you describe in a security questionnaire is a convention, not a constraint
Reporting assembled by hand
- Client reporting is exported, filtered and reassembled in a spreadsheet each month
- Nobody can see caseload across the book of business without stitching sources together
- Questions about a specific practice's performance take days to answer
How is one client's data kept separate from another's?
At the database layer, not in application code. Every clinical row carries a tenant key, and access policies are enforced by the database on every read and write. A query that omits the tenant returns nothing rather than returning another practice's patients. Separation does not depend on a developer remembering a filter.
Enforced, not conventional
- Row-level policies. The tenant boundary is a database constraint that application code cannot bypass.
- Scoped sessions. A user's active practice sets the tenant context for the whole session, including background jobs and reports.
- Auditable by design. Cross-tenant access attempts are logged, not silently filtered.
- Answerable in a questionnaire. You can describe the control as a mechanism rather than a policy.
Configured per practice
- Programs. Enable CCM for one client and the full eight for another.
- Billing. Each practice carries its own TIN, rendering NPIs, place of service and fee schedule.
- Care protocols. Call guides, thresholds and escalation paths differ by client without forking anything.
- Branding and templates. Patient-facing documents carry the practice's identity, not yours.
Can one coordinator work across several practices?
Yes. A staff member holds one account with an explicit role in each practice they serve, and switches between them in a click without re-authenticating. Their time is attributed to the practice they were working in at that moment, so minutes never cross a client boundary in billing.
One-click practice switching
A single sign-on and a practice picker. Switching resets the tenant context for everything on screen: the panel, the queue, the calendar, the reports.
Caseload management
Assign patients to coordinators, see who is carrying what across every client, and rebalance when a caseload runs hot or somebody is out.
Bulk onboarding
Import a practice's panel, enable its programs, configure billing and invite its users as one setup pass rather than a per-patient chore.
What can we show a client at the end of the month?
Per-client reporting scoped to that practice: enrolled patients by program, minutes delivered and by whom, codes that qualified and codes that fell short, and the documentation behind each. You can hand a client their own numbers without exporting and reassembling them.
What the practice sees
- Their patients, their minutes, their qualified codes, and nothing from any other practice
- Which patients are short of a threshold while the month is still open
- The signed note, consent record and time detail behind every claim
What you see
- Program performance across the whole book of business, and per practice within it
- Coordinator caseload and throughput across clients
- Where documentation is incomplete before it becomes an audit finding
Is this a different product from the practice platform?
No. It is the same platform with the multi-practice control surface turned on. Every capability on the care management software page applies to every practice you operate: automatic time tracking, CPT qualification across 23 codes, AI-drafted notes your clinician signs, in-browser calling and texting, cellular RPM devices, EHR integration and audit-grade logging.
Questions care management companies ask
Does each client practice need its own instance of the software?
No. One platform serves every practice you operate. Adding a client is a configuration step, not a deployment: enable their programs, load their billing identifiers, import their panel and invite their users. There is no separate environment to patch, monitor or upgrade per client.
How is one client's patient data isolated from another's?
Every clinical record carries a tenant key and access is enforced by database-level policies rather than application filters. A query without a tenant context returns nothing. Isolation is a constraint the code cannot route around, which is what makes it defensible in a security review.
Can one staff member work across multiple practices?
Yes. A staff member holds one account with an explicit role in each practice they serve and switches between them in a click. Their minutes are attributed to whichever practice they were working in, so time never crosses a client boundary in billing or reporting.
Who bills Medicare, us or the practice?
The practice does, under its own TIN and rendering NPI, with its billing practitioner supervising the work. Praventa is software and does not bill on anyone's behalf. Each practice's billing configuration is held separately, so claims are generated against the right identifiers automatically.
Can programs and protocols differ between our clients?
Yes. Program enablement, call guides, RPM thresholds, escalation paths, document templates and branding are all per-practice. One client can run chronic care management only while another runs all eight programs, without forking configuration or maintaining parallel setups.
What happens when a patient moves between practices?
Transfer is a built-in operation with an audit trail recording who moved the patient, when, and between which practices. The receiving practice inherits a complete record instead of re-entering one, and the sending practice keeps its history intact for its own audit position.
Can we report to each client separately?
Yes. Reporting is scoped per practice for client-facing delivery and rolled up across the book of business for your own operations. A practice sees only its own enrollment, minutes, qualified codes and documentation, with no possibility of another client's data appearing in it.
See it run across your book of business
Bring us the practice that is hardest to operate today. We will walk through how it would be configured, how its staff would work alongside your other clients, and what its month-end reporting would look like.