Skip to main content

Product requirements

  • November 13, 2025
  • 0 replies
  • 3 views

Before initiating deployment, please ensure the product requirements document is completed and reviewed. This document provides the foundation for configuring the Sandbox environment and aligning the Consent Suite setup with the customer’s clinical and operational needs. The Sandbox environment will be used throughout the integration and consent workflow testing phases.

 

You will be provided with a Product requirement document as part of the implementation.

 

The product requirements document is a living document and will evolve throughout the project lifecycle. These initial details are needed to streamline the build process, reduce rework, and support a smooth go-live:

 

  • Full name and address of the Trust or Hospital
  • Primary admin user details
  • Product modules to be enabled (e.g. PDF, Article, Consent)
  • Agreed procedure list
  • Required consent forms (e.g. CF1, CF2, CF3, CF4)
  • Patient data configuration (which demographic data points are needed)
  • Customised content requirements – agreeing these early helps with training and visual alignment
  • User permissions and data retention periods
  • Security settings, including two-factor authentication (2FA)