eRx integration
Create and manage electronic prescriptions through the rxConnect® middleware API.
rxConnect® by HITORI
Your platform. Connected.
Secure ePrescribing middleware for eRx, including hiConnect® for Services Australia Healthcare Identifiers Service integration—all exposed through focused APIs for your own healthcare software.
create-prescription.json
POST /eprescriptions/erx001/
Authorization: Bearer •••
{
"Patient": { … },
"Clinician": { … },
"PrescribedItem": { … }
}
200 { "scid": "…" }Fully owned infrastructure
One clean path to
electronic prescribing.
rxConnect® removes the specialised connectivity work while your application, workflows, user experience and data remain under your control.
HI Service included
Retrieve and verify patient IHIs through hiConnect®, the included Services Australia HI Service integration.
Your UI and workflows
The supplied React component and iFrame are optional. Adapt and style them, or build a completely custom interface using the API.
How it fits
A dependable boundary between
your product and the exchange.
Your healthcare applicationYour UI, workflows, architecture and data
—
rxConnect®REST API, mapping, certificates and lifecycle state
—
Australian digital healtheRx and Services Australia HI Service
rxConnect® + HI Service
ePrescribing and patient identity, connected.
The included HI Service integration, hiConnect®, resolves or verifies a patient’s IHI before that identifier is included in the rxConnect® erx001 prescription payload.
✓
Flexible IHI lookupSearch using Medicare, an existing IHI, DVA details, mobile or email with matching demographics.
✓
Environment separationDistinct staging and production endpoints and credentials.
✓
Conformance supportTechnical guidance through testing, evidence and required changes.
rxConnect® FAQs
Questions, answered.
The essentials for teams evaluating a direct ePrescribing integration.
What are the advantages of using rxConnect®?
You get the benefits of direct ePrescribing and HI Service integration without building and maintaining the specialised connection from scratch. Your application, workflows and data stay under your control.
Does rxConnect® include the HI Service?
Yes. The included HI Service integration is called hiConnect®. It retrieves and verifies patient IHIs through the Services Australia Healthcare Identifiers Service.
Where is it hosted, and are there usage limits?
rxConnect® can run in your own cloud environment or infrastructure. The perpetual licence has no per-prescriber, per-clinic or transaction-based limits.
Can it work with our existing healthcare platform?
Yes. It is designed for custom PMS, telehealth, clinical and healthcare software across web and mobile.
How long does integration take?
Technical integration typically takes 1–2 development days. Conformance testing and external approvals are separate and can take 3–12 months depending on readiness and review timelines.
Do we still need ePrescribing conformance?
Yes. rxConnect® and hiConnect® provide the underlying integrations, while your complete prescribing system and organisation must still meet the applicable workflow, security, audit and approval requirements.
Ready to own your integration?
New project? Talk with HITORI. Already integrating? Email our support team.