Castor EDC is positioned by its vendor as a clinical trial data capture system for research teams that need to build studies, collect eCRF data, and connect trial information across systems. The vendor's public materials emphasize short deployment timelines, API access, and a modular set of adjacent tools such as ePRO and eConsent. This profile examines documented product functions, integration mechanics, implementation boundaries, and areas where the available sources leave operational details unspecified. [1][2][3][4]

Study Build and Data Capture

Castor's marketing pages describe an EDC intended for researchers to create electronic case report forms and capture study data. The vendor states that low-complexity studies can be deployed in as little as 3–4 weeks and that build times can be reduced by up to 63%. One page also claims that more than 90% of studies are deployed within the first four weeks. These are vendor performance statements rather than independently verified benchmarks. [1][2][4]

The documented build workflow includes pre-built eCRF templates, multiple field types, conditional logic, and the ability to clone or reuse forms across studies. Vendor text says users can set up studies without training, though this claim appears in promotional material rather than a formal usability evaluation. The platform also describes real-time data saving, field-level encryption, two-factor authentication, and long-term retention as part of its data storage approach. [1][2][4][6]

Integration and API Access

Castor promotes an API-driven EDC that can integrate data from EHR, eCRF, ePRO/eCOA, laboratory systems, wearables, and other devices. The vendor describes an open API and an extensible integration framework intended to reduce data silos and manual reconciliation. These integration capabilities are presented as product features, but the sources do not document specific third-party systems that have been connected in production. [1][2][4]

The API documentation provides technical detail on authentication and access. Castor EDC uses OAuth 2, with full support for the Client Credentials flow and conditional support for the Authorization Code flow. The documentation lists three OAuth scopes: default, study_statistics, and record. Endpoints are generally rate-limited to 600 requests in 10 minutes unless a resource specifies otherwise. Basic HTTP authentication was removed on August 13, 2019. [3]

The developer policy adds operational constraints for API consumers. Integrations must not negatively affect application performance or end-user experience, and Castor may request changes or deny access if problems are detected. The policy also states that when exporting data from Castor systems, 21 CFR Part 11 and Annex 11 require validation that the exported data is accurate. This is a vendor policy statement about regulatory expectations, not a certification of any specific customer workflow. [5]

API Authentication and Rate Limits

The Castor EDC API uses OAuth 2 Client Credentials as the primary authentication flow. A user generates a Client ID and Client Secret from the Castor EDC profile, then requests an access token from the /oauth/token endpoint with grant_type=client_credentials. The Authorization Code flow is supported but requires contacting Castor. Endpoints are generally limited to 600 requests per 10 minutes, and rate limits are communicated through the X-RateLimit HTTP response header where automatic limiting applies. [3][5]

A hypothetical integration demonstration could show a study team using the Client Credentials flow to retrieve study statistics for a test study, then checking the X-RateLimit header to confirm remaining request capacity. The demonstration would not promise specific performance outcomes, but would illustrate the documented authentication sequence and rate-limit visibility without implying that any particular third-party system has been validated with Castor.

Monitoring, Compliance, and Data Governance

Castor's materials describe live dashboards for enrollment, data entry status, queries, and source data verification. The vendor claims more than 99.9% platform uptime and 100% data integrity, but these figures are marketing statements without an accompanying audit methodology in the cited pages. The platform also describes audit trails, test environments for amendments, and validation-friendly change management. [1][2][6]

The vendor lists compliance with FDA 21 CFR Part 11, ICH GCP, GDPR, HIPAA, ISO 27001, and ISO 9001, along with alignment to HL7 FHIR. These are vendor claims about the platform's regulatory posture. The sources do not include certificates, audit reports, or independent confirmation of compliance status. Teams evaluating Castor for regulated studies would need to verify the current certifications and their applicability to a specific protocol and jurisdiction. [1][2][4][6]

Catalyst AI Extraction Workflow

Castor Catalyst is described as an AI clinical data extraction service that sits between source documents and the EDC. The documented workflow includes intake through a Source Gateway, redaction, AI extraction, and human review. Source documents are stored in a study-isolated, encrypted gateway, and the vendor states that no large language models or other subprocessors are used during the redaction stage. [7][8]

The review policy currently sends every value to a Castor reviewer, described as 100% review. Risk-based review is listed as coming soon. Vendor benchmarking reports a manual time of 39 minutes per chart versus 6 minutes for Catalyst, and manual cost of $48.75 versus $9.75 for Catalyst. The vendor notes that these figures are internal benchmarks, production telemetry, or anonymized case results, not peer-reviewed data. The manual error rate is attributed to a 2025 meta-analysis, while Catalyst error rate is described as after review. [7]

Catalyst offers two documented workflows. Site Upload works globally and accepts source documents in any language. Direct-to-Patient retrieval uses HIPAA releases and Patient Right of Access to pull EHR data via FHIR APIs or TEFCA, and is currently available only in the US. Both workflows use the same AI pipeline and produce the same audit trail. Source documents are stored in a logically segregated Source Vault and purged 30 days after study close. [7][8]

Organizational Settings and Implementation Scope

The vendor's materials target sponsors, CROs, and research sites, with references to decentralized trials, real-world evidence programs, and post-market surveillance. Customer quotes describe use by clinical study managers, clinical affairs directors, and early-stage companies, but these testimonials are promotional and do not constitute independent case documentation. The sources do not provide a formal list of supported organization types or study phases. [2][4][6][7]

Implementation boundaries are documented in several places. Direct-to-Patient Catalyst retrieval is US-only, while Site Upload is global. The API has rate limits and OAuth scope restrictions. The developer policy permits Castor to deny access for noncompliance. The sources do not specify minimum study size, maximum site count, or formal training requirements, so those operational parameters remain unknown from the cited documents. [3][5][7][8]