Private prescriptions requiring Approval Number
Identified - We are currently experiencing an issue where Private prescriptions are requiring users to enter an approval number when one isn't normally required.

We are looking into this issue currently. In the meantime, you can enter any value into the approval number field to work around the problem and finalise the prescription.
Jun 16, 2026 - 12:50 AEST
Uptime over the past 90 days. View historical uptime.
Admissions Operational
MediRecords Operational
90 days ago
100.0 % uptime
Today
Activities - Clinical Actions, Tasks, and Work Lists Operational
Appointment Book Operational
Appointment Widget Operational
ConnectAPI Operational
90 days ago
100.0 % uptime
Today
Correspondence Operational
Waiting Room Operational
Engage Operational
ePrescribing and Prescribing Operational
Invoicing Operational
Secure Messaging Operational
SMS Operational
Patient Mobile App Operational
Third Party Components Operational
MediRecords Support Channel Operational
Twilio SMS Services Operational
Medications - Medispan Interactions Service Operational
Medications - Real-Time Prescription Monitoring Operational
Snomed Operational
Coviu Operational
Stripe Operational
Azure Web Services Operational
Heidi AI Operational
Australian Digital Health Agency Services Operational
My Health Record Operational
Health Identifier Service (IHI Validator) Operational
ePrescribing - eRx Script Exchange Operational
Claiming Services Operational
Medicare Operational
Australian Immunisation Register (AIR) Operational
Secure Messaging Services Operational
Healthlink Operational
Medical Objects Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

System Metrics Month Week Day
Apdex ?
Fetching
Server Response Time
Fetching
Jun 17, 2026

No incidents reported today.

Jun 16, 2026

Unresolved incident: Private prescriptions requiring Approval Number.

Jun 15, 2026
MediRecords Degraded Performance - Unable to Send SMS
Resolved - This incident has been resolved.
Jun 15, 20:48 AEST
Update - We are continuing to investigate this issue.
Jun 15, 15:44 AEST
Investigating - MediRecords is currently experiencing degraded performance with SMS on Demand, resulting in an inability to send SMS's. Our investigations has led us to an issue on our vendor/SMS carrier service, and our MR team are working with the vendor to restore services. We will provide updates on our status page as soon as they are available.
Jun 15, 13:53 AEST
Medicare claiming issue only impacting AIR
Resolved - This incident has been resolved.
Jun 15, 20:22 AEST
Investigating - We are currently experiencing a claiming issue impacting AIR claims only, no other claiming types are impacted. This issue started at 15:46 Sydney Time.

We have logged a support call with OTS. We will provide updates accordingly.
Jun 12, 17:25 AEST
Jun 14, 2026

No incidents reported.

Jun 13, 2026

No incidents reported.

Jun 12, 2026
Jun 11, 2026

No incidents reported.

Jun 10, 2026
RDS (Relational Database Service) Scheduled Maintenance
Completed - The scheduled maintenance has been completed.
Jun 10, 23:15 AEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 10, 23:00 AEST
Scheduled - As part of our commitment to continued platform improvements and currency, MediRecords will be undertaking a minor upgrade of our RDS (Relational Database Service). This minor upgrade is being scheduled to further enhance security of our databases and apply appropriate bug fixes as required.

What does this mean for our customers?
During the minor upgrade, MediRecords will be unavailable for 15 minutes.

When: 11pm (AEST), June 10, 2026
Duration: 11:00PM – 11:15PM AEDT outage
Component Impacted: Medirecords
May 27, 15:22 AEST
eRx Maintenance (NASH Certificate) for the eRx Script Service
Completed - The scheduled maintenance has been completed.
Jun 10, 19:30 AEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 10, 19:00 AEST
Scheduled - A software upgrade (NASH Certificate) for the eRx Script Service has been planned for 7pm (AEST) June 10, with an outage of 30mins to electronic prescribing services. Users will not be able to re-prescribe or generate new electronic prescriptions for patients during the down time.

When: 7pm (AEST), June 10, 2026
Duration: 30mins (7-7:30pm down time)
Component Impacted: ePrescribing

____________________________________________________________________________________________________

1️⃣ What will happen when a user clicks ePrescribe during the outage duration?
Note: Expected downtime is brief (minutes, not hours).

When a user completes the prescribing flow and clicks ePrescribe (or ePrescribe & Print), the system will attempt to connect to eRx and fail. The user will see this error:
"MediRecords is unable to generate Paperless Prescription for this script. E00000 - The eRx Gateway is not available. Please contact MediRecords support at support@medirecords.com if this issue persists."
The system will then automatically attempt to fall back:
- Paperless fails → attempts Paperscript (paper barcode)
- Paperscript also fails (likely) → falls back to Manual prescription

While electronic prescriptions will not work during this update, paper prescriptions will still be generated as normal and can be offered while the upgrade is completed.

2️⃣ What are the user's options?
✅ Option A — Let it fall back (recommended)
Click ePrescribe as normal. Accept the error. The system auto-converts to a Manual/Paper script. Patient receives a paper prescription (no token sent to phone/email).
✅ Option B — Prescribe as Paper intentionally
Use Prescribe & Print (or Prescribe (Paper)) instead of ePrescribe. This skips eRx entirely — no error shown.
✅ Option C — Save as Draft and send later
See section 3 below. Best option for telehealth prescribers who can't hand a paper script to a patient.

3️⃣ If they MUST send via ePrescribe — the Draft option
Users can save the script as a Draft and send it electronically once eRx is back up:
During the outage:
1. Complete the prescribing flow as normal
2. Click Save Draft (eRx)
3. No submission to eRx occurs — no SCID generated, no error triggered
4. If prompted "Some items have been selected for printing" when finishing the consult, choose Store

After the outage (once eRx is confirmed back up):
1. Go to the patient's Current Rx grid
2. Select the Draft prescription
3. Click the Print icon in the grid toolbar
4. The system will submit to eRx and send the token to the patient

⚠️ Things to be aware of:
- The Draft workflow does not show the recipient confirmation modal — it auto-sends to the patient's default contact method (known issue MED-81004). If they need a different recipient, update the patient's contact preference before printing the draft.
- A Draft created via ePrescribe cannot be converted to a Manual script — the prescribe type is locked to the original selection.
Jun 5, 16:11 AEST
Jun 9, 2026

No incidents reported.

Jun 8, 2026

No incidents reported.

Jun 7, 2026

No incidents reported.

Jun 6, 2026

No incidents reported.

Jun 5, 2026

No incidents reported.

Jun 4, 2026
Heidi AI Experiencing Degraded Performance
Resolved - Heidi are no longer reporting issues via their Service Status page.
Jun 4, 13:42 AEST
Monitoring - Heidi AI is currently experiencing degraded performance. We are aware of errors occurring when using the Heidi AI transcription service within MediRecords.

We’ve identified that this issue originates from our third-party supplier, Heidi AI. While the root cause lies outside of our systems, we are working closely continuing to monitor the situation to ensure timely resolution.

Updated will be provided via the Heidi AI Service Status page: https://status.heidihealth.com/
Jun 4, 12:10 AEST
Jun 3, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage