Investigational Product Management System for Clinical Trials Pharmacy

The IPMS software is to be delivered and made accessible across the HSPs to enable accessibility by multiple users located in multiple sites.

The Contractor must ensure accessibility on a 24/7 – 365 days per year basis through a software license / subscription arrangement.

The access and use of the IPMS software must be accompanied by a 24/7 support service available by direct telephone call or email that is responded to within specified hours of an issue being logged (see Schedule 8 – Service Level Agreement).

The Contractor will provide all relevant user training, training documentation and user manuals to ensure the proficient and knowledgeable use of the IPMS by WA Health’s authorised users.

The Contractor will develop a project plan (Schedule 7) for the IPMS software implementation and submit a copy with the response. The Project Plan will include a program for routine reports and updates, stating frequency, format and delivery to a nominated email address.

The Contractor must include configuration of the SaaS solution required to meet the Business Requirements (Schedule 16, HSS202515196 - Attachment 1 Functional and Non-Functional Requirements) as agreed with the Customer’s Representative. Furthermore, the Respondent is required to provide details of their proposed cloud by completing Attachment 6 – Cloud Service Assessment Vendor Form.

The Contractor is required to:

a) Fully configure, develop and test the solution and provide support on initial go-live operation prior to final review, UAT, and acceptance by the Customer. The final review will include, but will not be limited to successful completion of:

(i) solution testing and UAT (as per Schedule 13);

(ii) training; and

(iii) technical handover and documentation.

b) Ensure that all off-site resources are available to support the implementation process during business hours from 8.00am to 5.00pm (AWST);

c) State any known issues or risks (and how they are managed or mitigated);

d) Commit to completing the implementation within the agreed timeframe by using all planned resources;

e) Conduct a pre-implementation review to identify possible gaps between HSS functional and non-functional requirements, the system’s existing functionality, and develop a treatment plan in cooperation with HSS; and

f) Supply the following project and technical documentation as part of the implementation process:

(i) System and technical configuration;

(ii) Application Programming Interfaces (APIs), connectors or integrations;

(iii) Software version and license details;

(iv) Implementation Plans; and

(v) Handover documentation and signed checklists to meet HSS’ governance requirements.

g) Provide a detailed estimated timeline of completion of the Software solution to ‘Go Live’ ready for the initial site from the contract commencement.

Online Briefing

An online briefing session will be held on 9 Oct, 2025 8:00 AM.

Respondents to register their attendance no later than 3:00PM, Wednesday 8 October, (AWST) by emailing Thomas Hunter, contact details are in the Request. Invites will then be sent via Microsoft Teams.