Digital health

Choosing a health software development partner

Assess a health software partner through workflow evidence, privacy controls, relevant conformance, regulatory scope and responsibilities after release.

Choosing a health software vendor starts with how well they understand your workflow, not their feature list.

Ask a proposed supplier to show you the evidence for the work you want them to do. Start with a complete scenario and the product or version it represents. Then use these six questions to compare the evidence you receive.

AreaAsk the supplier to show you
WorkflowWho prepares and approves this record? Show a routine case and one that must stop for review.
Health informationWho can access the record in each environment, from where and for what purpose? Show the access and retention arrangements.
External servicesWhich connection and product version does your evidence cover? Show an exchange that is rejected or delayed.
Regulatory scopeWho will check intended purpose and applicable requirements? Show the evidence and exclusions relevant to this release.
AcceptanceWhich test will show this workflow is ready? Show what the buyer can review and who signs off.
SupportWho takes the first call when the exchange fails? Show the incident route, recovery instructions and handover materials.

Ask for evidence against the proposed work

A relevant example should identify the product, the partner's role, the delivered scope and the status reached. A prototype, an integration test and a production release are different forms of evidence. Each can be useful when it is described accurately.

Ask the supplier to demonstrate an external exchange that times out after submission. Watch who receives the alert, how they establish whether the provider received the request and what they can safely correct or retry. Ask which parts of that demonstration belong to the proposed product and version.

Establish privacy and access responsibilities

The OAIC's health privacy guidance explains that health information receives particular protection under the Privacy Act. Confirm how that framework applies to your organisation and product, alongside any relevant state or territory requirements.

Ask who can access production information, from where and for what purpose. Include support staff, administrators and subcontractors. Australian hosting alone does not answer those questions.

Set rules for development and test data before records are copied. Use synthetic or appropriately de-identified information where it can support the test. Where real information is necessary, agree access, protection and disposal controls for every environment.

A role-based workflow model illustrates how access can follow the task and stage of work. The applicable controls still need to be designed and tested for the product.

Check the scope of regulatory claims

An organisation-wide statement that a vendor is “ADHA approved” is too broad to assess. Ask which product, version, service and conformance profile the evidence covers, then check the relevant official record.

Software's TGA regulatory position also needs to be assessed for its intended purpose and applicable exclusions or exemptions. Not every application used in healthcare is regulated in the same way. Record the assessment and revisit it when the product's purpose changes.

Keep responsibility clear. The client and its advisers confirm the applicable legal, clinical and regulatory obligations. The development team needs to translate agreed requirements into product behaviour, tests and evidence. Neither side should leave that translation to an assumption in a proposal.

Walk through an incident before signing

Ask how the team would investigate an unexpected disclosure, incorrect record change or unavailable external service. Establish who contains the issue, preserves evidence, contacts the client and authorises recovery. Confirm notification duties with the organisation's privacy and legal advisers.

Request evidence of access control, patching, backup recovery and the removal of access when people leave. A policy is useful, but a demonstrated control gives the buyer a firmer basis for judging the proposed service.

ScriptStream's dashboard. The published story identifies the engineering scope and current release status.

Distinguish delivery proof from a promise

Twin Global developed ScriptStream for Wesley Pharmacy Group, including workflow engineering, Australian health-system integrations and conformance support. The October 2026 project record shows early production, with onboarding and development continuing and full PRODA integration still underway.

Ask what is delivered, what remains open and who owns the next decision. Review Twin’s approach to access and continuity, then request the evidence and responsibilities relevant to your proposed engagement.

Discuss your health software requirements