Frequently asked
questions

MEDIQCODE reads clinical documentation and produces a complete first-pass code set for every episode in ICD-10-AM, ACHI, and AR-DRG, with the Australian Coding Standards and your local policies indexed alongside. Every proposed code is shown with the source text behind it, so coders review evidence rather than guesses. Around that sits the operational layer: routing, turnaround SLAs, clinician queries, audit, and reporting.

It helps them. MEDIQCODE assists coders with explainable suggestions, and coders remain accountable for the final coded output. The AI clears the routine work and flags the complex cases, so your team spends its time on judgement calls, audit, education, and documentation quality rather than on retyping what the record already says.

Accuracy is something you can check, not something you take on trust. Every code carries its justification, so a reviewer sees immediately why it was proposed. MEDIQCODE consistently surfaces documented diagnoses and procedures that manual coding misses under time pressure, and it codes the same documentation the same way every time. Before go-live we validate accuracy on your own closed charts in a retrospective test, so the number you see is measured on your case mix.

MEDIQCODE works natively in ICD-10-AM, ACHI, and AR-DRG, with ACS and your organisation's coding policies applied inside the workspace. It is built for international markets rather than US-payer specifics, and currency, units, and language reflect your tenant. Support for other classifications should be confirmed for your deployment.

Revenue comes from three places: diagnoses and procedures that were documented but never coded, DRG groupings that move once the full picture is captured, and fewer denials because every code carries its justification. The size of the uplift depends on your case mix and current coding quality, which is why we start with a retrospective test on your own charts and measure the difference before you commit.

MEDIQCODE is designed around privacy by design. Sensitive patient details are reduced and de-identified before AI processing begins, either in your environment or in a dedicated secure instance agreed with your IT team. Data is encrypted in transit and at rest, processed in isolated environments with full audit trails, and only the minimum necessary information is used. Hosting location, retention, and controls are scoped with your security team as part of deployment.

Certification status must be confirmed with current evidence during your assessment rather than taken from a marketing page. Our team will provide the security documentation, contractual requirements, hosting location, and controls that apply to your deployment. See the Security & trust page for the principles the platform is built on.

Yes. Every suggestion shows the source text and the standard it rests on. Submissions are versioned, every recode carries a categorised reason from your audit catalog, and the full chain of changes is retained. When a case is questioned, the evidence is already attached to it.

Access is role-based. What is visible and what is permitted changes by role: Administrator, Coder, Auditor, CDI Specialist, and Clinician each get a tailored view. Trainee coders can be placed under a policy that requires manager review before work is finalised.

No. MEDIQCODE runs where your episodes already are. Episodes flow in automatically from your HIS/EMR, MEDIQCODE creates and routes them under your rules, and finalised coding returns to your systems. Coders can also upload discharge letters directly, which is common in smaller teams and during evaluation.

It depends on the integration path. A direct-upload evaluation can start almost immediately. A full HIS/EMR integration is scoped with your IT and security teams, and our team handles connectivity, configuration of your coding policies and rules, and coder onboarding. We will give you a timeline once we have seen your environment rather than quoting a number up front.

Discharge summaries and letters, clinical notes, operative reports, pathology and radiology reports, and other episode documentation. Both structured and unstructured text are handled, whether it arrives through the integration or as an uploaded file.

Yes. Organisation-specific coding policies and custom AI rules are configured to your organisation and surfaced inside the coding workspace, so coders see why a rule fired rather than discovering it in an audit later.

We start with a retrospective test on a set of your own closed charts. MEDIQCODE codes them blind, and we compare the results against what was billed: codes captured, codes missed, DRG movement, and revenue impact. You see the difference on your own case mix before committing to anything.

An independent quality check for clinically coded data. Upload a single episode or a full extract, and Lens checks the coding against the classification, the coding standards and, where it's provided, the clinical record. Every finding comes with its reason and evidence. See MEDIQCODE Lens.

Insurers and health funds use it to check the coding on the hospital claims they pay. Hospitals and health centers use it to measure their own coding quality and find where it slips. See Lens for insurers and health funds.

Audit in Coding is part of a hospital's own workflow: reviewers check and change codes before an episode is final. Lens is separate and independent. It assesses coding done anywhere, by anyone, one case or a whole extract at a time.

Pricing depends on episode volume, the integration path, and the modules you use. We scope it during the evaluation once we understand your case mix and workflow, so the quote reflects your operation rather than a generic tier. Ask for a quote and we will walk you through it.

Usually the coding manager or HIM lead, someone from revenue or finance who owns the DRG outcome, and a representative from IT or security if integration is on the table. A first walkthrough is a short working session with your questions, not a slide deck.