Parchment + Pabau
Compliant Australian eScripts, launched straight from the client card.
Pabau connects to Parchment Health — Australia's ADHA-conformant ePrescribing platform — so prescribers send electronic scripts without retyping a thing. Patient details flow from Pabau, and finished scripts land back on the client record automatically.
- Patient details pre-filled from Pabau
- eScripts sent via Parchment in seconds
- Script activity synced back to the record
Compliant Australian eScripts, straight from the client card — in 33 seconds
Up and running in three steps
Link your Parchment organisation
Enter the organisation credentials Parchment provides into Pabau's ePrescription setup. Credentials are encrypted and validated on the spot.
Prescribe from the client card
Pabau creates or updates the patient in Parchment and hands you straight into Parchment's prescribing flow — no re-typing, no mismatched records.
Scripts flow back automatically
Created, ceased, cancelled or reissued — every script event arrives back on the Pabau client record via secure, signed webhooks.
Everything the integration handles
Launch from the client card
Open Parchment for the right patient in one click — Pabau passes the demographics so the script starts from clean data.
Automatic patient sync
Pabau creates and updates the Parchment patient for you, keeping both records aligned as details change.
Scripts on the record
Prescriptions and their lifecycle — created, ceased, cancelled, reissued — sync back to Pabau automatically.
ADHA-conformant eScripts
Parchment is conformant with the Australian Digital Health Agency's ePrescribing standards and works with the eRx Prescription Exchange.
Real-time prescription monitoring
Parchment connects prescribers to state RTPM systems — SafeScript, QScript and more — at the point of prescribing.
Secure by design
Organisation credentials are stored encrypted, every webhook is signature-verified, and each event is re-checked against your organisation before it touches a record.
ePrescribing without the double data entry
Your clinical record lives in Pabau; the script is written in Parchment. The integration keeps the two joined — patients flow out, finished scripts flow back, nothing is typed twice.
- Patient demographics pre-filled from Pabau
- Scripts and status changes land on the client record
- Works with electronic and paper scripts in Parchment
- No copy-paste between systems
Compliance that comes as standard
eScripts in Australia come with real obligations. Parchment handles conformance — ADHA standards, the eRx exchange, state RTPM checks — while Pabau keeps the audit trail on the client record.
- ADHA-conformant ePrescribing platform
- Real-time prescription monitoring built in
- MIMS medicines database at the point of prescribing
- Every sync event verified and logged
Frequently asked questions
Who is this integration for?
Australian clinics prescribing electronically — from aesthetics and skin clinics to GPs and telehealth. Prescribers use Parchment; the clinic record stays in Pabau.
Do I need a Parchment account?
Yes. You'll need a Parchment organisation — Pabau links to it with the credentials Parchment provides, entered once in your ePrescription setup.
What flows between the systems?
Pabau creates and updates the patient in Parchment when you launch a script, and Parchment sends prescription lifecycle events — created, ceased, cancelled, reissued — back onto the Pabau client record.
Is it compliant with Australian eScript standards?
Parchment is conformant with the Australian Digital Health Agency's ePrescribing standards, works with the eRx Prescription Exchange, and connects to state real-time prescription monitoring systems.
See Parchment + Pabau in action
Join thousands of clinics running bookings, records, billing and marketing on Pabau — with Parchment connected.
