PSP Data Quality Checks for Saudi Pharma Teams: Six Tests Before You Trust the Dashboard

Short answer: Before a pharma team trusts a patient support programme (PSP) dashboard in Saudi Arabia, it should test six things: duplicate patients, missing consent, undefined denominators, stale statuses, unreconciled events and unclear ownership. A vendor report is only as reliable as the checks behind it, and these can be written into the contract.

Why the dashboard is not the starting point

A PSP report that shows "enrolled patients" and "adherence" looks authoritative. But every number depends on decisions made much earlier: what counts as an enrolled patient, who can enter data, what happens when two records describe one person, and who corrects errors. When those decisions are implicit, two teams can read the same dashboard and reach different conclusions.

International PSP practitioners have been consistent on this. A 2024 PSP Leaders Forum resource from 20Sense (Canada) frames data quality as something to plan from the start, with defined roles, trained data collectors, vendor management and continuous monitoring through scheduled control reports (20Sense, January 2024). It is a Canadian, non-regulatory document, so use it as a practical framework rather than a Saudi requirement. The six checks below are our own proposed working checklist built on those themes.

Check 1: duplicate and merged patients

The same patient can enter a PSP through a physician referral, a pharmacist call and a self-registration form. If each creates a record, enrolment looks higher than reality and follow-up contacts double. Ask your vendor how matches are detected, who approves a merge, and whether a merge is reversible and logged. Report the number of suspected duplicates found and resolved each month.

Check 2: consent status on every active record

For a programme handling health data, consent is not a one-time form. Check that every active record has a recorded consent, a date, the purposes it covers and a withdrawal route. Records without valid consent should be visible in a control report, not hidden. The principles are discussed in our guide to PDPL-compliant PSPs in KSA; confirm the legal position with your own counsel .

Check 3: denominators written down

Many disputes in PSP reporting are denominator disputes. "Adherence rate" can mean patients with a refill on time divided by all enrolled patients, or divided by patients who were due a refill. "Drop-out" can start at enrolment or at first dispensing. Before launch, write the numerator, denominator and time window of each reported KPI in a one-page definition sheet, and require the vendor to use it. Our article on PSP KPIs for pharmaceutical companies lists the metrics; this check makes sure each one is defined the same way every month.

Check 4: status age

A case marked "active" for ten months with no contact is a data quality issue, not an engaged patient. Set a maximum age per status and report cases beyond it. For example, "awaiting first call" should rarely last more than a few working days; your medical and operations teams should agree the thresholds.

Check 5: reconciliation of events

Adverse event, product complaint and refill-related events should reconcile between the PSP system and the safety or quality process of the marketing authorisation holder. Define how events are captured, who forwards them and how often the two lists are compared. Regulatory expectations for reporting in Saudi Arabia belong to your pharmacovigilance team , and any change in who reviews events during a vendor change should follow the controlled handover in our PSP vendor transition guide.

Check 6: ownership and access

The 20Sense resource notes the value of assigning data roles: one party responsible for access, governance and consent, another for testing and monitoring. Apply the same idea locally. Name the data controller on the pharma side, the vendor's data lead, who may export identifiable data, and who signs off a monthly control report. Review who has access every quarter.

What to put in the vendor agreement

Convert the checks into terms the vendor can meet:

• A data quality plan delivered before go-live.
• A one-page KPI definition sheet that is part of the contract.
• A monthly control report covering the six checks, with open items and owners.
• Training records for staff who enter data, refreshed on a schedule.
• A service level for correcting errors, with an escalation path.
• Audit rights and a clear process for data return at contract end.

An illustrative scenario

This is a planning scenario, not a customer case. A pharma medical affairs lead in Riyadh reviews a quarterly PSP report showing 1,200 enrolled patients. The control report shows 90 suspected duplicate records, 40 active cases without a recorded consent date, and 150 cases in "awaiting first call" for more than two weeks. None of this means the programme is failing. It means the headline number needs adjusting before it is quoted in an internal review, and the vendor has a clear list of items to fix by next month. Without the control report, the 1,200 would have gone forward unchallenged.

From operations data to evidence

Clean operational data is the foundation for any later evidence work, but it does not turn into evidence automatically. Using PSP data for outcomes, publications or promotional statements requires methodological and medical review . Our article on PROMs and real-world evidence in PSPs explains the distinction.

PSP Connect is CareSync's product for pharma patient support programmes; which of these controls are available in your configuration should be confirmed in a scoped demonstration .

FAQ

What are PSP data quality checks?

They are routine tests that confirm programme data is complete, unique, consented, consistently defined and current. Typical checks cover duplicate patients, consent status, denominators, status age, event reconciliation and access.

How do you audit a patient support programme vendor's data?

Ask for a monthly control report, review a sample of records against source documents, check the KPI definition sheet, and confirm training and access logs. The contract should give you audit rights.

Why do PSP adherence numbers differ between reports?

Usually because the denominator or time window changed. Writing each KPI's numerator, denominator and period in a fixed definition sheet prevents this.

Who should own PSP data quality, the pharma company or the vendor?

Both, with defined roles. The pharma company typically sets standards and oversight; the vendor operates the checks and corrects errors. Write the split into the agreement.

Can PSP data be used for outcomes claims?

Not directly. Operational data needs methodological and medical review before it supports any clinical or promotional statement.

---