Common Genie and Gentu Problems — and How to Fix Them
8 July 2026 · 8 min read
Genie and Gentu are the two practice management systems most commonly used by specialist and GP clinics across Australia that want something beyond the Best Practice / MedicalDirector duopoly. They are capable platforms, but they come with their own set of recurring IT problems — and many of those problems surface at the worst possible times: when a pathology result won't import, when the system freezes mid-consult, or when an ePrescription won't go through for a patient waiting at the desk.
This article covers the issues we see most regularly in clinic environments running either platform, and what to do about each one.
Genie Desktop
Pathology results not importing
This is the most common Genie support call we receive. Results are arriving at the pathology gateway but not appearing in the patient record.
The usual culprit is a conflict in the import location settings. Genie has two checkboxes that control where pathology is processed:
- Allow Pathology Import on Server — processes results on the server
- Import Pathology Automatically on Client — processes results on each workstation
These two settings are mutually exclusive. If both are enabled simultaneously, Genie can enter a state where results are received but not imported anywhere — they sit in the HL7 queue and go nowhere. The fix is to pick one location and disable the other. For most multi-workstation practices, the server-side import is the right choice.
If fixing the setting doesn't resolve it immediately, also check the ACK folder. Genie uses an ACK (acknowledgement) folder to confirm that results have been processed. If that folder path is misconfigured or points to a location that doesn't exist, results will queue up rather than import.
Results arriving but sorted incorrectly
If pathology results are coming in but landing in the wrong patient record, or appearing under miscellaneous correspondence rather than the pathology tab, the issue is almost always the incoming modifier setting.
Genie uses modifiers to classify incoming HL7 messages and route them to the correct location. A modifier set to the wrong message type will cause results to be filed under correspondence, or to appear in the inbox but not associate correctly with a patient. This is a configuration setting your IT provider or Genie support can correct — it's not something to adjust manually unless you know exactly what each modifier maps to.
Freezing and slow performance
Genie desktop is a client-server application that puts meaningful demand on local hardware. When it freezes or becomes noticeably slow, the most common causes are:
Insufficient RAM — Genie's recommended minimum is modest, but when it's running alongside a full Windows environment, an antivirus scanner, and PDF software, 8 GB of RAM on a workstation is the practical floor. If you're on older machines with 4 GB, performance will degrade significantly as the database grows.
PDF engine conflicts — Genie renders documents using its own embedded PDF engine. If this engine is outdated or conflicts with a separately installed PDF reader, the application can freeze when opening any document. The fix is to update Genie's PDF components through the Genie installer update process, and in some cases to remove conflicting PDF software.
Temp file accumulation — Genie writes temporary files during normal operation. On a workstation that hasn't been maintained in some time, these can grow large enough to cause slowdowns. Clearing the Genie temp directory (with the application closed) is a quick fix that sometimes makes a noticeable difference.
Network latency — If your Genie server is on the same local network as your workstations, the application should be fast. If there's any routing through a VPN, a slow switch, or a Wi-Fi connection for the server, response times will suffer. Genie is not designed for high-latency environments.
Application crashes
Repeated crashes — especially on startup or when opening specific record types — usually point to one of two things: a corrupted installation or an outdated printer driver.
Printer drivers are a surprisingly frequent cause of Genie instability on Windows. When Genie tries to render a print job and the driver is incompatible with the current Windows version, it can crash the application rather than just failing the print. Updating or replacing the default printer driver resolves this in most cases.
If the crash is on startup and driver updates don't help, a clean reinstall of Genie (keeping the data and configuration intact) is the next step.
Gentu (Cloud)
ePrescribing errors
ePrescribing in Gentu is one of the most common sources of support calls, and most of the errors that come up fall into a small number of categories.
"Service Unavailable" / Status 500 errors — These indicate a problem reaching the ePrescribing integration service (usually through MIMS). The first thing to check is whether the practice's MIMS subscription is current. An expired or lapsed MIMS subscription will cause ePrescribing to fail silently in some configurations and throw a server error in others. If the subscription is active, clearing browser cache and cookies resolves a significant proportion of these errors — Gentu runs in the browser, and cached session state can cause API calls to fail.
Schema validation errors — These appear when a patient record contains data that doesn't match the format the ePrescribing system expects. The most common trigger is a non-numeric character in the patient's phone number field — spaces, dashes, or brackets that were entered manually rather than through a standardised format. Remove all non-numeric characters from the phone number field and retry.
Prescription not completing in Safari — Gentu recommends Chrome or Edge. Safari has known compatibility issues with certain Gentu modules including ePrescribing. If a prescriber is experiencing consistent failures on a Mac, switching browsers is the first thing to try.
Patient merging errors
Gentu allows duplicate patient records to be merged, but this operation is permanent and cannot be undone. When a merge is performed incorrectly — most often when two different patients are merged, or when a merge is triggered accidentally — the result is a corrupted record that can cause "Something Went Wrong" errors when opening appointments, generate orphaned entries in the appointment book, and produce incorrect clinical history displays.
This is not a fixable issue through normal IT support. The only resolution path is through Gentu's own support team, and recovery is not always possible. The practical advice is to treat the merge function with extreme caution, require explicit confirmation before any merge is performed, and if in doubt, contact Gentu support before proceeding rather than after.
Billing claim errors
Incorrect Bulk Bill and DVA claim batching is a recurring issue in Gentu, particularly for practices migrating from another system or after a Gentu software update.
The most common errors we see are:
- Claims batched with the wrong provider number (particularly in multi-provider practices)
- DVA claims submitted under a Bulk Bill service type or vice versa
- Claim batches failing to transmit because the Medicare software token has expired
Medicare Online claiming in Gentu requires a valid PRODA (Provider Digital Access) credential. These credentials expire and need to be renewed periodically. An expired PRODA token will cause claim transmissions to fail silently or return a generic error. Check the expiry date of your PRODA credential if claims are suddenly not transmitting.
Session timeouts and connection dropouts
Gentu is a cloud application, so its reliability is directly dependent on your internet connection. If clinicians are experiencing session timeouts, disconnections mid-consult, or slow screen loads, the investigation starts with the connection:
- Is the practice on a dedicated business-grade connection with a guaranteed SLA, or a residential NBN service?
- Is the router managed or consumer-grade?
- Is Gentu traffic competing with video calls, large file downloads, or clinical imaging software on the same connection?
Gentu does not have an offline mode. A flaky internet connection in a Gentu practice is a clinical risk, not just an inconvenience. If stability is a recurring issue, a secondary 4G/5G failover connection is worth considering.
When to call your IT provider versus Genie/Gentu support
A useful distinction: IT problems (network issues, workstation performance, Windows configuration, credentials, printer drivers) are your IT provider's domain. Application problems (data corruption, clinical record errors, billing logic, ePrescribing integration, merge operations) belong to Genie or Gentu support.
Where it gets complicated is in the middle — import settings, ACK folder configuration, HL7 routing, service account permissions. These require someone who understands both the IT layer and how the clinical application is built. That's where a specialist medical IT provider earns their keep.
If you are regularly dealing with any of the issues above and the fixes described here haven't resolved them, the underlying problem is usually a configuration that was set up incorrectly at some point and has been causing low-level issues ever since. A structured review of your Genie or Gentu configuration — ideally with someone who has seen these environments before — is usually more effective than fixing each symptom individually.
Not sure where your practice stands?
A Compliance Gap Assessment covers backup and DR posture, access controls, and compliance documentation — a written report with a prioritised roadmap.