# Clinical workflows, connected to the clinic around them.

Bring patient context, prescribing, pathology and applicable Medicare claiming into one clinic platform. Keep medical and aesthetic care connected to the people and work around them.

Feature availability depends on your plan, enabled features and access permissions.

Canonical HTML: [https://dappleos.com.au/features/clinical-workflows](https://dappleos.com.au/features/clinical-workflows)

Feature group: [Clinical care](https://dappleos.com.au/features/clinical-care)

## At a glance

- **Start with the patient.** Keep notes, forms and images close to the clinical conversation.
- **Prescribe in context.** Prepare medication prescriptions and follow their electronic result.
- **Follow investigations through.** Connect requests, missing tests and reviewed results.
- **Keep claiming connected.** Follow applicable Medicare claims and their payment reports.
- **Record medication movements.** Keep product, patient, location and recorded use together.

## Start with the person. Keep the context.

A useful clinical record is more than a text box. Bring notes, forms, photos and treatment detail together, with the patient-home layout shaped around the information your team needs and is authorised to see.

- **The work behind the treatment room door:** Keep patient forms, photos, markings and product detail with the recorded treatment.
- **A view that fits the role:** Configured patient widgets and access permissions keep relevant information available to the right team members.
- **A record to return to:** Earlier notes, documents and dated patient information provide context for the next consultation. Configure patient fields around the information your clinic needs to record.
- **Consultation in context:** Where video consultation is enabled for your clinic, join the appointment’s call from the clinical note while keeping the patient context close. Calls without an appointment require separate setup; our team can confirm the consultation options available to your clinic.


## Carry the clinical context into the letter.

Prepare a patient letter from a reusable template, review its content and recipient, then finalise it before sending. Keep correspondence with the patient record, so your team can return to the letter and its recorded sending history.

- **A considered starting point:** Use templates and supported patient details to prepare the letter, then review and edit it for the person and purpose.
- **Keep professional contacts close:** Use the address book to find professional recipient details. Check the selected recipient before sharing patient information.
- **Review before sharing:** Authorised staff can generate a PDF or send a finalised letter by email. Letters access and sending permissions apply, and unresolved healthcare identifier alerts must be addressed before sending.


## Keep the patient record useful as it grows.

Keep documents and clinic-defined patient fields alongside the clinical history. When duplicate profiles need attention, authorised staff can review the source and destination records and choose the supported record types to consolidate.

- **Choose what moves:** Review the merge summary and selected data types before confirming. Record consolidation is a deliberate team action, not an automatic match between similar names.
- **Keep the action traceable:** A merge event records the source, destination and acting user. The scope depends on the supported record types and choices made for that merge.


## Different clinical jobs. Connected patient context.

A treatment-specific prescribing request, an electronic medication prescription and a stock movement each record something different. Give each job the detail it needs, with clear links back to the patient and the work performed.

- **Digital prescribing:** Select a medication, complete the prescription and follow the eRx result from the patient record.
- **Injectable scripting:** Connect the practitioner’s request with the clinic’s prescriber, consultation and review decision.
- **The digital drug book:** Track medication movements with product, barcode, patient, location and user context.


## Keep the request and the result in view.

See which tests have arrived, what is still outstanding and which results need review. Keep the patient, request and linked tests together, with review, portal release and notification as deliberate choices.

- **Follow partial results:** A request can remain incomplete while some tests have linked results and others are still pending.
- **Keep release clear:** The practitioner chooses what to share with the patient. Receiving a result does not automatically release it.


## Keep the claim beside the clinic’s billing work.

Support the applicable private and bulk-bill pathways with claim records, statuses and payment reports. Keep the service and provider context in view as the team prepares, reviews and follows up the claim.

- **Distinct claiming pathways:** A patient-paid service with a Medicare benefit and a bulk-billed service have different payment relationships.
- **A trail to reconcile:** Claim status and payment-report information help the team investigate the returned outcome.


## Know what needs a person’s attention.

Outstanding tests, a prescription error and a claim awaiting a response mean different things. Their own workspaces keep the detail available, so your team can return to the right record and follow up with context.

- **Clinical follow-up:** Use the investigation queue to find missing tests and results that have not been reviewed.
- **Prescribing exceptions:** An electronic creation error stays with the prescription for the prescriber to investigate.
- **Billing follow-through:** Use the claim record and returned information to understand the next claiming action.


## The right information. The right responsibility.

Bring clinical and operational work together while preserving access controls, practitioner judgement and the requirements of each connected service.

- **Role-based access:** Patient notes, prescribing and pathology have their own permission controls.
- **Configured connections:** eRx, pathology and Medicare workflows follow your clinic’s provider, organisation and integration setup.
- **Clinical responsibility:** Practitioners remain responsible for assessment, prescribing, interpretation and follow-up.
- **Clear claiming responsibility:** The clinic reviews eligibility, provider and service details for the claiming pathway it uses.


## FAQs

### Which clinical workflows can share the patient record?

Clinical notes, forms, photos, letters, medication prescriptions and pathology can share patient context in DappleOS. Applicable Medicare claiming and medication stock records connect with the clinic’s wider operational work. Each workflow retains its own permissions, configuration and responsible person.

### How is digital prescribing different from injectable scripting?

Digital prescribing prepares and maintains a medication prescription, including its electronic result. Injectable scripting connects a practitioner’s treatment-specific request with the prescriber’s consultation and decision. The dedicated pages show each workflow in detail.

### What does our clinic need for electronic prescribing?

The eRx pathway uses clinic and prescriber setup, required professional and healthcare identifiers, and complete patient information. A demo can review your prescribing model and the connection requirements that apply to your team.

### How do pathology review and patient release differ?

Receiving a result, reviewing and linking it, releasing it to the patient portal and triggering a notification are distinct actions. The request retains its tests and completion context, while the practitioner controls review and release.

### Which Medicare workflow fits our services?

DappleOS supports applicable private and bulk-bill claiming pathways. The right workflow depends on the service, provider setup, eligibility and payment relationship. Bring your current billing process to a demo so the team can demonstrate the relevant path.

### Can access vary across our team?

Yes. Clinical notes, pathology, prescribing and other patient information use role-based permission controls. The patient-home layout can be configured around the work and information a team member needs. Your clinic remains responsible for assigning suitable access.

### Can we prepare patient letters without a separate document workflow?

Yes. Use reusable templates and supported patient details to prepare a letter, then review its wording and professional recipient. Authorised staff can finalise it, generate a PDF and send it by email. Letters availability and permissions apply, and sending history does not confirm receipt.

### How can we keep duplicate patient records organised?

Authorised staff can review the source and destination profiles and select supported record types to consolidate. The merge summary helps the team check what will move, and the action has a recorded user and event. The scope depends on the records selected; it should not be treated as an automatic or universally reversible process.

## Related features

- [Digital prescribing](https://dappleos.com.au/features/digital-prescribing)
- [Pathology](https://dappleos.com.au/features/pathology)
- [Medicare and bulk billing](https://dappleos.com.au/features/medicare)
- [Injectable scripting](https://dappleos.com.au/features/real-time-scripting)
- [Digital drug book](https://dappleos.com.au/features/digital-drug-book)
- [Clinical notes and markings](https://dappleos.com.au/features/clinical-notes-markings)
- [Planning](https://dappleos.com.au/features/treatment-planning)
- [Clinic KPIs](https://dappleos.com.au/features/kpis)

## Next step

[Book a demo](https://dappleos.com.au/sales-call)