Skip to main content
QuickIntell

Workflow planning · English

Plan specialist correspondence in Australia

Follow a referral into the practice and a reviewed letter back to its intended recipient. Clinical record, practice administration, secure delivery and claiming are separate parts of that journey.

Planning, not a product promise

A correspondence-planning worksheet. It does not establish software compatibility, delivery authority or Medicare claiming capability.

Before you start

  • Record the actual clinical and practice-management products. Genie and Gentu must be scoped separately; distinguish MedicalDirector Clinical from Pracsoft, Helix and Bluechip.
  • Identify the approved referral channels, recipient directory and source of patient identity. Do not assume that an appointment entry supplies everything needed for clinical correspondence.
  • Agree the template, authorised drafting inputs, clinician approval and permitted delivery method. Check deployment, privacy and support with the responsible owners before using patient information.

Map the workflow and its human review

Use the following as an assessment structure, then adapt it with the people who own the real process. No step below asserts that QuickIntell currently performs it.

01Review the referral and intended recipient

Have staff confirm the patient, referring practitioner and referral attachments through the practice’s existing process. Preserve uncertain information for review.

Expected output
A checked correspondence context.
Human reviewer
Practice administration, with clinical questions escalated.
Exception path
Missing recipient details or conflicting patient identity stops automated delivery.

02Prepare a clearly marked draft

Use the agreed document structure and authorised inputs. Keep unsupported facts, uncertain transcription and unanswered questions visible rather than completing them by inference.

Expected output
An unapproved draft letter in the agreed template.
Human reviewer
The responsible clinician.
Exception path
A draft is not a signed clinical document and cannot be sent as one.

03Approve content and destination separately

Require the clinician’s content review and the practice’s recipient check. Identify whether transfer to the installed software is manual or an authorised interface operation.

Expected output
Approved content with an approved recipient and destination.
Human reviewer
Clinician for content; authorised staff for delivery details.
Exception path
A destination mismatch or unsupported operation returns the item to staff.

04Reconcile delivery and filing

Track both the delivery acknowledgement and the copy in the clinical record. A prepared PDF, a sent message and a filed record are three different completion states.

Expected output
A reconciled correspondence status.
Human reviewer
Practice correspondence owner.
Exception path
Undelivered or unfiled items remain open; retrying must not produce duplicate letters.

Agree acceptance checks before a pilot

Begin with synthetic or appropriately authorised test data. Name the assessor, method and target before testing; publish results only when approved and genuinely measured.

Review before sending
An unapproved synthetic draft cannot reach a delivery action.
Correct recipient
Changed and ambiguous recipient details force a staff check.
Complete acknowledgement
Tests distinguish preparation, transmission, receipt and record filing.
Measured improvement
Compare clinician editing time, staff handling time and unresolved correspondence with a baseline; report rework as well as speed.

What this does not establish

  • Medicare Online or ECLIPSE access implied by letter generation.
  • My Health Record connectivity implied by practice-software access.
  • Clinical decisions or signatures generated without the responsible clinician’s approval.

Primary sources and limits

These sources establish local product or infrastructure context. The workflow checklist is an editorial planning framework, not an official implementation specification, legal opinion or statement of QuickIntell compatibility. Verify the current requirements with the responsible organisation.

Content updated 2026-10-02. This is not a clinical, legal or product approval date.

Bring a specific workflow to the discussion

Share your operating country, care setting, system name and review requirements. Do not send patient records, credentials or identifiable clinical information.

Australian Specialist Correspondence Workflow Checklist | QuickIntell