Insights Digital health and workflow engineering
What ScriptStream taught us about reliable workflow software
Reliable workflow software makes responsibility clear through every step, including the ones that fail. Twin Global's work developing ScriptStream for BOP Plus shows why approvals, status and recovery deserve attention from the start of a project.
ScriptStream is an Australian electronic prescribing platform owned by BOP Plus and developed by Twin Global. Its workflow separates preparation and review from the authorised prescriber's final approval, while connecting the product to external Australian digital health services.
That creates an engineering problem familiar beyond healthcare. Several people can contribute to a piece of work, while only a particular person has authority to complete it. The software has to preserve that responsibility as records move between users and systems.
Make authority part of the workflow
A business process needs clear rules about who can prepare information, change it and approve the final action. Those rules should be reflected in the system's permissions and behaviour.
For a workflow design review, ask what happens if a preparer tries to perform an approval, or if information changes after someone has reviewed it. Identify whether the change requires another check and how that need becomes visible.
The appropriate answer will depend on the process. The important work is resolving it before the interface makes an action appear complete.
This applies to a payment approval or a property handover as well as a health workflow. The relevant authority needs to remain clear when the task crosses a team boundary.
Use status to explain the next action
A single complete label can conceal several different events. A record may have been prepared, submitted to another service or accepted by that service. Each state can require a different response from the user.
The workflow should identify what has happened and who needs to act next. Pending work needs to remain visible when the person who started it is away or another team takes over.
Review the status language with the people operating the process. Technical terms that make sense to developers may not tell a user whether to wait, correct a record or contact someone.
Clear status also supports reporting. Managers need to distinguish work awaiting a business decision from work delayed by an external system.
Plan for an incomplete external step
ScriptStream's delivered integration work includes handling failures, corrections and status visibility around external services. These are part of making an integration usable in an operating environment.
For any connected workflow, test situations where a response is delayed, a record is rejected or the outcome of a request is uncertain. Establish what users can see and what they should do while the issue is resolved.
A repeated submission also needs deliberate treatment. The design should establish whether the original request succeeded before an action is repeated where duplication would matter.
Define a recovery route that preserves enough history for support staff to understand the event. The user should be able to continue safely without reconstructing the process from unrelated messages.
Treat release as part of the engineering work
ScriptStream has been released and is in early production, with real prescribers using the platform. Prescriber onboarding and further development continue. Full PRODA integration remains underway.
The ScriptStream customer story describes the integration scope, conformance milestones and the platform's release.
For another business planning workflow software, the practical lesson is to test a complete operating scenario before release. Include the permissions, handovers and external responses that determine whether a person can finish the task.
Then test how the process behaves when one of those steps fails. That is where a project team can find the missing decision, unclear status or recovery action that a successful demonstration might never expose.