Run your own PV on HAROM OnePV, run many clients behind one address, or take a dedicated instance — provisioned, governed and audited from one control office.
CRO model · Direct tenant · Single instance
HAROM control office
Every client in every model, the CROs and their people, and who changed what.
CROs
3
3 active
Clients
14
6 direct · 7 CRO · 1 single
CRO people
12
11 active
MultiPV users
4
4 active · 19 sign-ins this week
Clients by model
How each client runs
Changes over the last 30 days
8 this week · 23 in 30 days · every change by a Super Admin, with a reason
One control office
Every client, every model
Every model runs the same HAROM OnePV applications with the same controls. What changes is who signs in where, and how your data is kept.
CRO modelFor CROs and PV service providers
Your team signs in once and works across every client with the same role. Each client keeps its own segregated database, users and audit trail.
Direct tenantFor Mid-size pharma and MAHs
Your users, your data and every OnePV application, ready quickly and kept current by HAROM.
Single instanceFor Top-tier pharma and groups
For organisations that require isolation: a dedicated server and databases, with the same applications and controls as every other model.
HAROM provisions every client, in every model, from one control office. Nothing changes without a Super Admin, a written reason and an audit entry.
Provision a client in any model
Direct, CRO or single instance, from one place.
Review, then run set-up
Nothing is created until a HAROM Super Admin has reviewed it.
CRO people and permissions
Who works for which CRO, with which role, across which clients.
Who changed what
Every change needs a written reason and is kept in an append-only record.
HAROM control office
Every client in every model, the CROs and their people, and who changed what.
CROs
3
3 active
Clients
14
6 direct · 7 CRO · 1 single
CRO people
12
11 active
MultiPV users
4
4 active · 19 sign-ins this week
Clients by model
How each client runs
Changes over the last 30 days
8 this week · 23 in 30 days · every change by a Super Admin, with a reason
A CRO signs in once and sees the whole book of work: what is open, what is due, what went out on time and where an acknowledgement needs attention.
Every client at a glance
Open, overdue, due today and due in seven days, across all clients or one.
Submission compliance
Reports sent on time over the last 90 days, with late ones and acknowledgement problems called out.
Cases in, reports out
Cases received against reports submitted, week by week.
One click to any client
Switch client, keep your role, keep your context.
Active clients
4Client A
2 open
Client B
0 open
Client C
1 open
Client D
3 open
Open cases
6
being processed now
Overdue
0
past the regulatory due date
Due today
1
in the client's time zone
Due in 7 days
4
plan the week
Submitted this month
18
reports sent
On time, 90 days
98%
41 on time · 1 late
ACK problems, 30 days
0
failed or rejected
Active users, 30 days
9
signed in
Submission compliance
Reports sent on or before their due date
41 on time · 1 late · 0 ACK problems
Cases received and reports submitted
Cases by clock start · reports by date sent · last 12 weeks
Safety Vault, IntakeIQ, GatewayPRO, AggregatePRO and SignalIQ, in every model.
E2B(R3) to EMA, FDA, MHRA, Health Canada and WHO PIDM from every model.
MedDRA and reference data kept current centrally for every client.
The same roles and permissions everywhere, so audits read the same.
Releases applied by HAROM across models, with change control.
Every action in every client and in the control office is recorded.
| CRO model | Direct tenant | Single instance | |
|---|---|---|---|
| Best for | CROs and PV service providers | Mid-size pharma and MAHs | Top-tier pharma and groups |
| Address | One address for the CRO | Your own address | Your own address |
| Data | A segregated database per client | Your own database | Dedicated server and databases |
| Users | Your team, same role across clients; Microsoft sign-in | Your users, your roles | Your users, your roles |
| Onboarding | HAROM provisions each client; open to your team immediately | Provisioned by HAROM, ready quickly | Set up and reviewed by HAROM |
| Upgrades | Applied by HAROM | Applied by HAROM | Pushed by HAROM |
A short conversation on how you operate today and where you are going.
Client, address, users, products and reference data, reviewed before set-up runs.
Role-based training with assessed competency, then your first cases.
Platform support included; PV services added whenever you need capacity.
Designed to support 21 CFR Part 11 and EU Annex 11 controls.
Role-based access
Everyone sees exactly what their role allows.
Audit trail on every action
Who, what and when — always on record.
MFA or one-time code, enforced
Every sign-in verified twice.
Strict password policy
Strong, rotated, enforced.
Controlled workflows
Nothing skips a step.
Offer pharmacovigilance to your clients behind your own address, without building a platform.
Your own tenant on a platform that already runs multi-market submissions.
A dedicated instance with the isolation your security and residency policies require.
Next step
A HAROM PV expert walks you through the control office, the CRO dashboard and the applications on your own workflow.
