From waiting to in progress.
Assignment makes responsibility visible. In-app notifications reach eligible prescribers; SMS is available for prescribers with it configured.
Injectable scripting for aesthetic and cosmetic clinics
Injectable scripting, connected to the patient.
Bring your clinicians and prescribers into one connected workflow. Start with the treatment context, review the patient record and keep the prescribing decision in view.
At a glance
A clearer connection between clinician and prescriber.
Keep the request, the information behind it and the person responsible together. Your clinic brings its own prescribers. DappleOS connects the workflow.
Start from the note.
Carry relevant treatment, product and anatomical context into an editable request.
Review the whole picture.
Keep medical history, notes, photos and forms beside the request.
Connect the people.
Bring queue ownership, request messages and video consultation together.
Keep the decision clear.
Separate requesting, reviewing and issuing, with the outcome recorded.
Understand the queue.
See waiting requests, recent waiting time and configured prescriber availability.
Start with the treatment context
Carry the detail forward. Keep the request editable.
When a treatment needs a script, start the request from the clinical note. Relevant scanned Schedule 4 products and recognised anatomical areas can carry across, ready for the clinician to check and the prescriber to review.
Explore clinical notes and markings
- Connected to what was recorded.
Bring relevant treatment and product context from the note into the request. Existing valid coverage is excluded from the gaps being requested.
- A starting point for review.
Products, quantities, repeats and anatomical areas remain editable. Carried-forward information is not a prescribing decision.
One patient. Connected context.
The clinical note starts the request. The prescriber reviews and decides. The recorded script can then inform the next clinical check.
Clinical noteScript requestPrescriber review
Patient context, in the review
See the person behind the request.
Review medical history, past notes, photos and completed forms alongside the request. Keep the clinic, requesting clinician and treatment detail in view while the prescriber considers what is appropriate.
- Medical history and previous notes
Review the recorded patient context without piecing it together from a separate message thread.
- Photos and completed forms
Bring the relevant patient imagery and form responses into the same review workspace.
- Product and anatomical scope
Check the requested products, quantities, instructions and anatomical areas before making a decision.
A clear place to pick up the request
Know who is reviewing. Keep the conversation connected.
Eligible prescribers see the live queue and can take ownership of a request. Bring the patient and clinician into a connected video consultation, with request messages alongside it.
Join the consultation in context.
For a request attached to an active video appointment, the assigned prescriber joins the same room as the patient and clinician.
The decision stays with the prescriber
Review deliberately. Record what was decided.
The authorised prescriber can amend the requested scope, decline the request or proceed to issue. Issuing captures the signature and validity period, with the completed record available in the patient’s scripting history.
- A distinct issuing action.
Taking a request or joining a call does not approve it. The prescriber reviews the information and completes the issuing action, using their configured profile signature or drawing a signature in the supported workflow.
- Keep current coverage in view.
Return to the clinical workflow with the recorded script status and treatment scope. Prescribing, treatment use and stock movements remain separate records.
“The prescriber’s judgement is central. A request should bring the patient’s context and the proposed treatment into view, with room to ask questions and a clear record of the decision that follows.”
Visibility for the working day
See the queue before the next request.
See how many scripts are waiting, the recent average waiting time and prescribers available according to their configured schedules. Use that context to coordinate the clinic’s next conversation.
Waiting is different from being reviewed.
The queue separates pending requests from work already in progress. Completed requests have their own view.
Context, not a promised response time.
Average waiting time comes from recorded assignment times. Prescriber availability reflects configured schedules, not a guarantee of immediate acceptance.
Less work to piece together.
Keep the request, patient context, consultation and decision together, so the team can return to the same record.
Explore connected treatment planningTrust and compliance
Your prescribers. Clear responsibilities.
Keep clinical responsibility with the authorised practitioner, supported by patient context, assignment and deliberate review.
Feature availability depends on your plan, enabled features and access permissions.
- Hosted in Australia
- Encrypted storage
- Your own prescribers
- Your clinic engages and configures its authorised doctors and nurse practitioners. DappleOS provides the workflow, not a prescriber service.
- Assignment and access
- The assigned prescriber reviews the request in the correct clinic context. Patient information and decision controls follow the user’s role and assignment.
- Configured review requirements
- Anatomical-area and consent requirements can inform the request and approval controls. Where the consultation requirement applies, a recorded real-time consultation is needed before approval.
- A recorded clinical decision
- The prescriber determines the appropriate scope and validity and completes the signature. Clinical judgement and treatment responsibilities remain with your practitioners.
Supporting your Australian clinical obligations
Ahpra and National Boards
Consent and patient information
Keep consent and patient information available for review. Your practitioners apply the cosmetic procedure guidance relevant to their profession.
Read practitioner guidanceMedical Board of Australia
Clear clinical records
Retain the patient context and the prescriber’s recorded decision to support clear clinical record keeping.
Read the code of conductYour clinic applies the guidance relevant to each practitioner and treatment. Clinical decisions and compliance remain with your team. DappleOS is not endorsed by these regulators.
Before you start
FAQs
How injectable scripting fits your prescriber relationships and the way your clinic works.
Can we use our own prescribers?
Yes. Your clinic works with its own authorised doctors and nurse practitioners, with request routing and availability configured around those relationships. DappleOS provides the software workflow; it does not supply prescribers or guarantee response times.
How does this reduce the back-and-forth around a request?
A clinician can start a request from the clinical note with relevant treatment, scanned Schedule 4 product and recognised anatomical detail carried forward. The prescriber reviews the patient’s medical history, notes, photos and completed forms in the request workspace, with messages and video consultation available alongside it.
Can the clinician or prescriber change the requested scope?
Yes. Carried-forward products, quantities, repeats and anatomical areas are an editable starting point. The authorised prescriber reviews the scope and can amend it before making their decision. Nothing is approved simply because it appeared in the note.
Can the prescriber join a patient’s video consultation?
Yes. A request attached to an active video appointment can connect the assigned prescriber to the patient and clinician in the same room. The request retains its patient context and messages. Where the recorded consultation requirement applies, it must be satisfied before approval.
How will our prescribers know a request is waiting?
The live queue shows waiting and in-progress requests. Eligible prescribers receive in-app notifications, and SMS notifications can be configured for individual prescribers. Once assigned, notifications for that request are directed to the assigned prescriber.
What remains visible after a script is issued?
The completed request retains its recorded prescribing scope, prescriber, completion date and validity. The supported issuing workflow uses the prescriber’s configured profile signature or a signature drawn for that script. The clinical workflow can then show relevant script coverage. Issuing a script is separate from recording treatment use, updating stock or billing the patient.
What needs to be configured before we start?
Your clinic sets up its prescriber relationships, access, availability, treatments and products, and relevant consent and anatomical requirements. A demo can map those choices to your current workflow and show the request, review and issuing stages together.
Does the software decide whether treatment is appropriate?
No. DappleOS organises the information and workflow around the prescribing decision. The authorised practitioner assesses the patient, decides what is appropriate and remains responsible for the clinical decision and applicable obligations.
Ask DappleOS
Talk through your prescribing workflow.
Bring a question about your clinicians, prescribers or clinic setup.