HACT CTMS · Clinical Trial Management System
Clinical trial management, built for better research operations
HACT CTMS brings study setup, site and investigator coordination, participant registration, monitoring, data management and reporting into one secure, permission-controlled environment - so a trial’s operating record lives in one place instead of nine.
- Single sign-on through your identity provider
- Permissions resolved server-side from your assigned roles
- Access tokens never exposed to browser JavaScript
Site activation
Enrolment against plan
Enrolment trend
Placeholder
Monitoring
Data quality
Platform
One connected record, from protocol to report
A clinical trial is a sequence, not a set of independent screens. HACT CTMS is structured so each stage hands the next one a record instead of a report, which is what makes an operational question answerable.
- 1
Study setup
Protocol, study and project configuration are captured once, in a controlled version rather than in a spreadsheet per team.
- 2
Site activation
Investigational sites, study teams and investigator records are managed against the study they belong to.
- 3
Participant operations
Screening, eligibility and registration, recorded as they happen so the operating record matches the trial.
- 4
Clinical monitoring
Monitoring visits, findings and corrective actions are tracked to closure against the site that owns them.
- 5
Data management
Data capture, review and query resolution share the same study structure, so a change is visible in one place.
- 6
Regulatory and reporting
Submissions, approvals and operational reporting read from the same records the study was run on.
Capabilities
Modules that share one foundation
Each capability is an independent module, so a deployment can be configured to match how an organisation actually runs its studies - without losing the single record underneath.
Study management
Protocols, studies and project configuration in one controlled place.
Site management
Investigational sites, study teams and investigator records.
Participant operations
Screening, enrolment and registration with full traceability.
Clinical monitoring
Monitoring visits, findings and corrective actions to closure.
Data management
Data capture, review and cleaning workflows.
Regulatory operations
Submissions, approvals and compliance records.
Reporting
Operational and regulatory reporting across every module.
Document management
Controlled documents and versions attached to the study record.
Module scope is delivered in phases. The capability areas above describe the platform architecture; each module is released only once it is implemented and verified.
Workspace
Inside HACT CTMS
The workspace is organised around the trial lifecycle: the navigation, the summaries and the actions all follow the study rather than the other way round.
HACT CTMS workspace
Study summary
Key figures for the selected study
Active studies
Investigational sites
Participants registered
Monitoring visits due
Enrolment by site
Placeholder
Recent activity
- Monitoring visit recorded
- Data query resolved
- Role assignment updated
Illustrative preview of the planned workspace. Values shown are placeholders - the screen is not connected to live study data.
Security
Trusted by design, not by assertion
Clinical data is sensitive, and the controls around it should be checkable. Each statement below describes something implemented in the platform today.
Standards-based authentication
Sign-in uses the OpenID Connect authorization code flow with PKCE against Keycloak. HACT CTMS never receives, stores or validates a password.
Role and permission based access
Access is granted by assigning a reusable role. Roles carry permissions, and both live in PostgreSQL - so revoking access takes effect immediately, independently of any token.
Authorisation decided on the server
Every API request is authenticated and authorised server-side on each call. Hiding a screen or a menu entry is a usability measure; the server refuses the request either way.
Credentials kept out of the browser
Access tokens are held in an httpOnly, same-site cookie and are never exposed to page scripts or browser storage, so an injected script cannot read them.
Auditable by design
Auditable activity is written to a dedicated audit table capturing the actor, the action, the outcome and the originating request. Coverage grows as each module is delivered.
Deny by default
Authentication is enforced globally across the API: a new endpoint is protected unless it is explicitly marked public, so an omission fails closed rather than open.
About
About HACT CTMS
HACT CTMS is a configurable clinical trial management platform. It is built as one system with one permission model, and it is delivered in phases: each capability is added to the same foundation rather than beside it.
The platform is designed for organisations that run studies across several sites and several teams, where the difficulty is rarely any single task and almost always keeping one operating record that everyone can rely on.
- Identity
- Keycloak, using OpenID Connect. Accounts, sessions and credentials belong to the identity provider; the application holds none of them.
- Records
- PostgreSQL, with a single schema and migrations applied by version. Authorisation data lives beside the records it protects.
- Application
- A NestJS API and a Next.js interface in one repository, so a contract change is a reviewable change rather than a cross-team negotiation.
- Interface contract
- A versioned REST API documented with OpenAPI, validated at both ends, so a caller cannot silently drift from the contract.
- Background work
- Redis-backed queues for work that should not block a request, and object storage for documents and files.
- Deployment
- Containers behind a single reverse proxy, which is also where transport security headers and rate limits are applied.
Sign in to the HACT CTMS workspace
Access is granted by role, so an administrator decides exactly which parts of a study you can see. If you have an account with your organisation, you can start now.