Platform Specification for Platform Services (Medical AI)

Version: v1.0 May 2026

PLATFORM SPECIFICATION

FOR

PLATFORM SERVICES

(MEDICAL AI)

1. PRELIMINARIES

This Platform Specification:

• forms part of the Agreement (as described in the Platform GTCs);

• describes the technical and functional specification of the Platform; and

• may be updated and amended by the Supplier from time to time in accordance with clause 13 (Product Roadmap) of the Platform GTCs.

Defined words and phrases used in this Platform Specification but not defined here shall have their respective meanings given in the Platform GTCs.

2. PLATFORM OVERVIEW

The Platform is the Supplier's software platform known as "Medical AI", an AI-native execution layer for the review, indexing, summarisation and chronological organisation of medical records and associated medico-legal documents. The Platform delivers a set of claim-type-specific and medical AI products (paragraphs 4.7 to 4.11) on top of common platform modules for authentication, user, matter, contact and file management (paragraphs 4.1 to 4.6).

The Platform is delivered as a multi-tenanted, cloud-hosted application accessed via web browser. The Platform is hosted on Amazon Web Services in region eu-west-2 (London) as described in the Data Processing Terms.

The Platform comprises the functional modules described in paragraph 4 (Functional Modules).

3. TECHNICAL SPECIFICATION

3.1 Hosting and infrastructure

Hosting provider	Amazon Web Services (AWS)
Primary region	eu-west-2 (London)
Tenancy model	Multi-tenant with logical tenant isolation
Availability	High-availability architecture utilising multiple AWS availability zones
Backups	Encrypted backups at least every twenty-four (24) hours, with periodic restoration testing

3.2 Access and client requirements

• Access via current versions of supported modern web browsers (Chrome, Edge, Safari, Firefox);

• Stable broadband internet connection;

• No client-side installation required;

• Customer is responsible for its network connections and telecommunications links from the Customer's System to the Supplier's Cloud.

3.3 Security

The Platform is delivered in accordance with the Security Controls as described in the Data Processing Terms, including:

• encryption of data in transit (TLS 1.2 or higher) and at rest (AES-256 or stronger);

• role-based access control on a least-privilege basis;

• audit logging of security-relevant events and Authorised User actions;

• centralised security monitoring and alerting;

• multi-factor authentication for administrative access;

• annual independent penetration testing;

• Certifications and Controls: SOC 2 Type I and Cyber Essentials Plus.

3.4 AI infrastructure

AI Features are powered by Amazon Bedrock operated within the Supplier's virtual private connection (AWS PrivateLink), under zero-retention terms. Further information is set out in the AI AUP.

4. FUNCTIONAL MODULES

The Platform comprises the following functional modules. Modules 4.1 to 4.7 are platform-wide capabilities. Modules 4.8 to 4.12 are AI products that may be enabled for the Customer through the Order. Each module is provided as part of the Platform Services subject to the Agreement (including the AI AUP, the Data Processing Terms and the Fees Policy).

4.1 Authentication — Login (federated access)

Purpose	Authenticate Authorised Users into the Platform via federated identity providers and supported sign-in methods.
Multi-factor authentication	Supported via the Customer's federated identity provider; available natively where SSO is not deployed
Session security	Configurable session timeout; account lockout following a reasonable number of consecutive failed authentication attempts; alignment with current NCSC and NIST guidance
Regional dashboards	Separate authentication endpoints for UK, US and Australia regional dashboards

4.2 Logout

Purpose

Terminate the Authorised User's authenticated session and invalidate associated session tokens.

Capabilities

Manual logout from any screen within the Platform;

Automatic logout on session timeout;

Single Logout (SLO) via the federated identity provider where supported;

Forced session termination by Customer administrators via the User Management module.

4.3 User Management

Purpose

Enable the Customer to manage Authorised Users, their roles and their permissions within the Platform.

Capabilities

Invite, create, suspend and deactivate Authorised Users;

Assign role-based permissions (e.g. administrator, fee-earner, paralegal, read-only, expert);

View and manage active sessions, including forced logout;

Configure SSO and identity provider settings;

Configure default permissions and access scopes;

View audit logs of user actions.

4.4 Contact (data subject) creation and management

Purpose

Create and manage records relating to data subjects connected to a matter (e.g. claimants, defendants, witnesses, treating clinicians, experts) as determined with the Customer

Capabilities

Create, view, edit and archive contact records;

Capture identifying information (name, date of birth, contact details, role in matter);

Link contacts to one or more matters;

Manage relationships between contacts (e.g. claimant ↔ treating clinician);

Search and filter contacts across the Customer's tenant.

4.5 Matter creation and management

Purpose

Create and manage the matters (cases) in respect of which the Platform Services are used.

Capabilities

Create, view, edit, archive and close matters;

Capture matter metadata (reference, type, jurisdiction, key dates, fee-earner assignment);

Link contacts (data subjects) and files to a matter;

Assign Authorised Users to a matter on a role basis;

Track matter status and progress;

Search and filter matters across the Customer's tenant.

4.6 File management

Purpose

Upload, organise, view and manage source documents (medical records and associated medico-legal documents) within a matter.

Capabilities

Upload single files and bulk file uploads;

Organise files within a matter (tags);

Preview files within the Platform;

Download original source files;

Delete files;

View processing status of files (queued, processing, complete, failed).

4.7 Expert profile

Purpose

Enable an Expert User to maintain a profile describing their expertise, credentials and availability, for the purpose of being viewed by Firm Users considering or having appointed them.

Capabilities

Create, view, edit and archive the Expert User's profile;

Capture relevant experience (areas of practice, types of matter handled, jurisdictions, language(s) spoken);

Capture practising address(es), correspondence details and availability for new instructions;

Indicate fee guidance, turnaround times and any other commercial or professional qualifications or standards information the Expert User chooses to publish to Firm Users;

Preview the profile as it appears to Firm Users.

Visibility

The Expert User's profile is visible to Firm Users in accordance with clauses 11.1.1 and 11.1.2 of the Platform GTCs. The Expert User remains responsible for the accuracy and currency of all information published in the profile (clause 11.1.2.2).

4.8 Medical Summary for Personal Injury

Purpose	Produce a structured medical summary tailored to personal injury (PI) claims (including road traffic accidents, slips and trips, workplace and public liability matters), focusing on mechanism of injury, treatment received, recovery progression and prognostically relevant facts to support quantum and causation analysis by the instructed fee-earner.
Inputs	Claimant medical records (e.g. GP, hospital, allied health), accident-related records, letters of claim, or claim notification forms and any source files uploaded to the relevant matter; user-specified parameters (e.g. summary scope, date range, focus areas)
Outputs	Structured medical summary aligned to PI requirements with references back to the source records
Fees	Charged per Fees Policy

4.9 Military Hearing Loss Evidence Review

Purpose	Produce a structured review of the medical evidence in military noise-induced hearing loss (NIHL) claims, supporting the instructed fee-earner's preparation of the matter and the engagement of expert opinion.
Inputs	Service medical records, audiometry reports, occupational and noise-exposure records, deployment and posting history, and any other source files uploaded to the relevant matter; user-specified parameters
Outputs	Structured evidence review covering noise-exposure history, audiometric progression, clinical and treatment history, and opinion-relevant facts, in each case with references back to the source records. The Platform does not produce expert opinion; opinion remains the responsibility of a suitably qualified instructed expert.
Fees	Charged per Fees Policy

4.10 Indexed and Paginated Bundle for Personal Injury

Purpose	Produce an indexed, paginated and chronologically ordered bundle of the medical and associated records held within a personal injury (PI) matter.
Inputs	Source files uploaded to the relevant PI matter (typically GP, hospital, allied health, accident-related and insurer-disclosed records)
Outputs	Paginated PDF bundle (or equivalent) of the source records; Index of the bundle organised by healthcare setting and date, and displaying document type and other information. Chronological ordering of records within the bundle.
Fees	Charged per Fees Policy

4.11 Indexed and Paginated Bundle with Chronology for Medical Negligence

Purpose	Produce an indexed, paginated and chronologically ordered bundle of the medical and associated records held within a clinical / medical negligence matter, accompanied by a structured chronology of events, treatments, investigations and clinician entries.
Inputs	Source files uploaded to the relevant medical negligence matter (typically GP records, hospital records, imaging, pathology and allied health records)
Outputs	Paginated PDF bundle (or equivalent) of the source records; Index of the bundle organised by date, document type or other selected criteria; Chronological ordering of records within the bundle; Structured chronology document presenting events, treatments, investigations and clinician entries in chronological order.
Fees	Charged per Fees Policy

4.12 Other AI products

Additional AI products may be made available by the Supplier from time to time and shall be enabled for the Customer through the Order. Where enabled, each such product is subject to the general framework set out in this paragraph 4 (purpose, AI techniques, inputs, outputs, per-instruction processing, limitations, audit and fees), the AI AUP and the Platform GTCs.

5. LIMITATIONS AND DISCLAIMERS

The functional modules described in paragraph 4 are subject to:

• the limitations and disclaimers set out in the Platform GTCs (including clauses 7 (Supplier's Obligations) and 9 (Exclusions and Disclaimers));

• the limitations and disclaimers set out in the AI AUP (including paragraphs 2.1.4 (Limitations of the AI Features) and 5 (Limitations and Disclaimers)); and

• the Customer's obligations regarding human oversight, review and verification of Outputs.

The Outputs of the AI Features are administrative and assistive in nature. They are produced to support — not replace — the legal and clinical judgement of the qualified fee-earner or expert instructed on the matter.

6. SERVICE AVAILABILITY AND SUPPORT

Service Levels and Support are described in the Support Specification.

7. AMENDMENT

The Supplier may amend this Platform Specification from time to time in accordance with clause 13 (Product Roadmap) of the Platform GTCs.