Written and maintained by CASRAI Editorial Board
Published
On this page
TrialMaster is an electronic data capture (EDC) system from Anju Software, used to collect and manage case report form data in Phase I to IV clinical trials and medical device studies. It is a web-based, cloud-hosted platform that sits inside Anju’s eClinical Suite. This guide is for sponsors, clinical operations staff, data managers and research offices who want a neutral description of what TrialMaster covers, what the vendor’s regulatory wording means, and which other systems do similar work. Every product statement below is attributed to Anju’s own pages (checked 2026-11-18); none is an independent test or a recommendation.
This page is general information about a software product. It is not procurement, regulatory or medical advice.
What is TrialMaster?
Anju’s FAQ describes TrialMaster as “an intuitive Electronic Data Capture (EDC) web-based solution designed to streamline Phase I-IV clinical trials” (Anju eClinical FAQ, checked 2026-11-18). Its product page adds that it serves medical device companies as well as drug and biologic sponsors, and that it supports decentralized trials (Anju TrialMaster page, checked 2026-11-18).
In plain terms, electronic data capture means that sites enter trial data directly into a validated web system instead of onto paper case report forms, and the system applies checks, keeps an audit trail and produces datasets for analysis. TrialMaster is one of several systems that do this job. It is a data-collection system, not a clinical trial management system: operational tracking of sites and milestones is a different category, covered in CASRAI’s guide to the clinical trial management system.
Who runs TrialMaster and what does it cover?
TrialMaster is published by Anju Software. Anju’s pages list offices in Lisle, Illinois, in Brussels and Antwerp, and in Pune, and present TrialMaster as part of the company’s eClinical Suite (Anju TrialMaster page, checked 2026-11-18). Third-party software directories name the vendor inconsistently, so Anju’s own pages are the authority for who currently publishes the product. Anju does not state user counts or the number of studies run on the platform on the pages read, so none is given here.
The vendor page describes these capabilities, which are mapped to the standards they refer to in the data table below the guide:
- TrialBuilder, the study-build tool. Anju describes a “user-friendly WYSIWYG” case report form designer with automatic edit-check generation and parameterized edit checks. Central laboratory reference ranges are also defined here, and out-of-range values prompt the user for a clinical significance assessment.
- ePRO and eConsent. Participant-reported data is entered directly in TrialMaster, with participant-facing text translated into the participant’s language, and eConsent runs “directly within the EDC system”.
- Source data verification (SDV). SDV is flexible: the monitoring level or a site risk rating determines which forms need verification, with a manual override and a task list for monitors.
- Risk-based quality management. Key risk indicators, dashboards and alerts are listed as part of the product.
- Data export. A custom export utility maps data to SAS datasets by drag and drop, and Anju states that “Standard templates are available by default for all SDTM domains.” Anju also lists export capabilities and APIs.
- AutoEncoder. Coding of medical terms against MedDRA and WHODrug Global, with the option to integrate with external EDC or safety systems.
- Safety Link. Serious adverse event reporting, where Anju says an E2B file is created.
- Access and usability. Single sign-on with a customer’s own identity provider, multi-language support, and screens that adapt to device size.
The product page does not describe a randomization module inside TrialMaster; randomization and trial supply management is handled by a separate Anju product, so a study that needs it should plan for a second system and an integration between them.
What do the standards behind these features mean?
CDISC SDTM
The Study Data Tabulation Model is a CDISC standard that, in CDISC’s words, “provides a standard for organizing and formatting data to streamline processes in collection, management, analysis” and reporting; CDISC lists it among the standards required for data submissions to the US FDA and Japan’s PMDA (CDISC SDTM page, checked 2026-11-18). Anju’s statement that SDTM templates exist for all domains therefore concerns how easily data can be exported into a submission-ready shape. It does not say how much programming a given study will still need. See the CASRAI entry for the Study Data Tabulation Model.
21 CFR Part 11
Anju’s FAQ says TrialMaster “Supports 21 CFR Part 11 and GCP standards for regulatory adherence” and lists user-level access controls and audit traceability. That is a vendor statement. The regulation itself, at 21 CFR 11.10 (Cornell Legal Information Institute, checked 2026-11-18), requires controls for closed systems including validation of systems to ensure accuracy, reliability, consistent intended performance and the ability to discern invalid or altered records (11.10(a)), and secure, computer-generated, time-stamped audit trails that record operator entries and actions (11.10(e)). Whether a particular installation meets those requirements depends on how it was validated and operated by the sponsor and the vendor. The Anju pages read do not describe a validation package, so a sponsor that needs one should request the validation documentation from the vendor in writing instead of relying on the word “supports”.
MedDRA, WHODrug and E2B
These are coding dictionaries and a safety-reporting message format that Anju names in connection with AutoEncoder and Safety Link. Naming them tells you which dictionaries the coding tool targets and which file format the safety module produces. It does not tell you which dictionary versions are loaded or how licensing of the dictionaries is handled, which are questions for the vendor.
How do you search or use TrialMaster?
TrialMaster is a licensed system, not a public database, so there is no open search. Access is provisioned per study by the organization running the trial, and Anju states that single sign-on with the customer’s own identity provider is supported. The vendor’s public pages do not publish step-by-step user documentation, so this guide does not reproduce interface instructions. To find the sign-in, use the Anju website or the link your study team gives you; do not enter credentials on any other page.
Strengths and limits
What the vendor pages support. TrialMaster combines study build, EDC, ePRO, eConsent, SDV management, coding, safety reporting and SDTM-oriented export in one suite, and the vendor states that it covers Phase I to IV and device studies and works on desktop, tablet and phone.
What the pages do not establish. They give no price, no user or study counts, no independent validation evidence, no statement on support or hosting service levels, and no randomization module. A decision to use any EDC system should rest on documents the vendor will sign or supply, such as a validation summary, an audit-trail description and a data export specification, not on feature lists alone.
How to read a vendor’s regulatory wording
Anju’s FAQ and Medidata’s EDC page illustrate a common difference in how EDC vendors present themselves. Anju’s FAQ states Part 11 and GCP support in so many words. The Medidata EDC page read for this guide does not mention Part 11, electronic records or signatures, or CDISC standards at all; it instead emphasizes study build, protocol amendments, site experience and scale, giving figures of 25+ years, 1.8M+ users and 38K+ studies (Medidata’s own claims, checked 2026-11-18). Neither page is a substitute for the other kind of evidence. A feature page is marketing; the evidence that matters is the validation documentation, the audit-trail output and the contract.
- Match each claim to the text it refers to. “Supports Part 11” corresponds to the 11.10 controls on validation, record protection, audit trails and access limits, and a sponsor still has to show those controls work in its own study.
- Separate collection from submission. EDC output becomes submission data only after mapping to SDTM, so ask whether mapping is done in the platform, by the vendor’s data services, or by the sponsor.
- Check what is a separate product. Randomization and trial supply management is separate in TrialMaster’s case; Medidata’s page lists RTSM, eConsent and eCOA as connected products. In both cases the integration is a project task.
- Plan the end of the study. Ask how data, metadata and the audit trail are exported and archived at close, because the sponsor must keep records for inspection long after the system contract ends.
Alternatives
EDC is a crowded category. The table lists systems whose own pages or CASRAI guides describe the same job. It is a description of what each source says, not a ranking.
| System | What its own materials say | Where to read more |
|---|---|---|
| Medidata Rave EDC | Described by Medidata as an EDC system for capturing, managing, cleaning and reporting trial data, with eCRF libraries, drag-and-drop study design, protocol amendments without downtime, and connections to eConsent, eCOA and RTSM. A Rave Lite variant targets Phase I, Phase IV and device post-market studies. | Medidata EDC page (checked 2026-11-18) |
| Medrio | EDC and clinical data management system aimed at small and scaling clinical teams, with eConsent, eCOA, RTSM, CTMS and eTMF listed. | CASRAI guide to Medrio |
| Castor EDC | Lightweight EDC, discussed for investigator-initiated trials. | CASRAI guide to Castor EDC |
Questions to put to any of these vendors, derived from the standards above, are: which validation documents will you provide for 21 CFR 11.10(a); how are audit trails exported (11.10(e)); which SDTM and dictionary versions are supported; and what happens to the data and audit trail at study close. For a market overview of trial intelligence rather than data capture, see CASRAI’s guide to Trialtrove.
Frequently asked questions
What is TrialMaster?
TrialMaster is a web-based electronic data capture system from Anju Software for Phase I to IV clinical trials and device studies, per Anju’s own FAQ (checked 2026-11-18).
Who makes TrialMaster?
Anju Software publishes it as part of its eClinical Suite. Third-party directories do not agree on the vendor, so Anju’s pages are the authority.
Is TrialMaster 21 CFR Part 11 compliant?
Anju states that it supports 21 CFR Part 11 and GCP standards. Part 11 compliance depends on validation and use in each study, so the statement is a vendor claim, not a certification. See the 11.10 discussion above.
Does TrialMaster support CDISC SDTM?
Anju says standard export templates are available by default for all SDTM domains, with drag-and-drop mapping to SAS datasets.
How much does TrialMaster cost?
Anju does not publish a price on the pages read, and third-party listings disagree on the billing unit, so no figure is given here. Ask Anju for a written quote.
Sources
- Anju Software, TrialMaster, read 2026-11-18
- Anju Software, eClinical frequently asked questions, read 2026-11-18
- 21 CFR 11.10 Controls for closed systems (Cornell LII), read 2026-11-18
- Medidata, EDC systems, read 2026-11-18
- CDISC, SDTM, read 2026-11-18
Data: TrialMaster capabilities as stated by Anju, mapped to the standard or requirement each refers to
Each row is a TrialMaster capability named on Anju Software's own product page or FAQ, paired with the external standard or regulation it refers to, taken from CDISC and 21 CFR 11.10. Compiled 2026-11-18 from vendor, CDISC and regulator pages; vendor statements are not independent verification.
Period covered: 2026.
| Capability | What Anju states | Related standard or requirement | What the sources do not say |
|---|---|---|---|
| Data export | Standard templates available by default for all SDTM domains; drag-and-drop mapping to SAS datasets | CDISC SDTM, required for FDA and PMDA submissions | How much programming remains per study |
| Regulatory support | Supports 21 CFR Part 11 and GCP; user-level access controls and audit traceability | 21 CFR 11.10(a) system validation; 11.10(e) time-stamped audit trails | Validation package or certification |
| Medical coding | AutoEncoder codes against MedDRA and WHODrug Global | MedDRA and WHODrug dictionaries | Dictionary versions loaded |
| Safety reporting | Safety Link for SAE reporting; an E2B file is created | E2B safety message format | Regulator-specific transmission details |
| Source data verification | Monitoring level or site risk rating sets which forms need SDV; manual override | Risk-based monitoring | Default thresholds |
| Study build | WYSIWYG CRF design with automatic and parameterized edit checks | Edit checks as data validation controls | Template library size |
Sources
- Anju Software, TrialMaster (accessed 2026-11-18)
- Anju Software, eClinical FAQ (accessed 2026-11-18)
- 21 CFR 11.10 (accessed 2026-11-18)
- CDISC SDTM (accessed 2026-11-18)
Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.
CASRAI runs an examined credential on this subject: Clinical Data Management certification, Foundation level (other levels are listed on its page).







