What ScriptStream taught us about reliable workflow software
Use the ScriptStream example to review authority, status, external failures and release responsibilities in a connected business workflow.
Reliable workflow software keeps responsibility clear through every step, including the ones that fail. Twin Global’s work developing ScriptStream for Wesley Pharmacy Group shows why permissions, status and recovery deserve attention from the start.
ScriptStream is an Australian electronic prescribing platform developed by Twin Global for Wesley Pharmacy Group. It separates preparation and review from the authorised prescriber's approval while connecting the product to external health services.
That creates an engineering problem familiar beyond healthcare. Several people may contribute to a task, while only a particular role has authority to complete it. The software needs to preserve that distinction when records move between users and systems.
Make authority part of the workflow
Define who can prepare information, change it and approve the final action. Reflect those rules in permissions and tested behaviour, not only in instructions for users.
During design review, ask what happens if a preparer attempts an approval. Then change information after review and check whether another approval is needed. Resolve the appropriate answer before the interface makes an action appear complete.
This applies to payment approvals, property handovers and other controlled work as well as healthcare. The authority depends on the process, but it should remain clear when the task crosses a team boundary.
Use status to explain the next action
A “complete” label can hide several events. A record may be prepared, submitted to another service or accepted by that service. Each state can require a different response from the user.
Review the status language with the people operating the process. It should help them decide whether to wait, correct information or contact someone. Pending work needs to remain visible when the original user is away.
Clear status also supports management reporting. Work awaiting a business decision should be distinguishable from work delayed by an external system.
Plan for an incomplete external step
The delivered integration scope includes failure handling, corrections and status visibility. Test delayed responses, rejected records and requests whose outcome is uncertain.
Establish what users can see and what they should do while the issue is investigated. Before repeating a consequential action, determine whether the original request may already have succeeded. Safe recovery needs more than a generic retry button.
Keep enough linked history for support staff to understand the event without reconstructing it from unrelated messages. Limit access to the information needed for the support task.
Separate public milestones from wider readiness
The ADHA Electronic Prescribing Conformance Register lists Script Stream under BOP Plus Pty Ltd, version 1.0, as a Prescribing System with profile 3.0.1 and registration from 6 November 2025.
That entry establishes a particular registration milestone. The customer story describes Twin's wider engineering and integration scope. ScriptStream is in early production, with prescriber onboarding and further development continuing. Full PRODA integration remains in progress.
Do not use one milestone to imply every service dependency or future feature is complete. A release record should identify both the behaviour available and the conditions that remain open.
Test a whole operating scenario before release
For another workflow project, follow a representative task through permissions, handovers, external responses and final confirmation. Then introduce an interruption at the step most likely to expose an unclear responsibility.
Check whether the next user can understand what happened and continue through an agreed recovery path. That exercise can reveal a missing decision or status that a successful demonstration never exposes.
Use the electronic prescribing conformance guide for the assessment process. This article addresses the workflow design that makes the product understandable in daily use.