OpenClinica positions itself as a modular eClinical platform for sponsors, CROs, academic teams, and sites. Marketing material from the vendor describes electronic data capture as the core product, with optional connections to Recruit, eCOA, Randomization, eConsent, EHR-to-EDC, and Reporting & Analytics. The documentation defines the software through its data import and API functions rather than through a formal product tier list. This profile focuses on workflows that the public documents describe, distinguishing vendor claims from technical specifications. [2][3][7]
Study Design and Data Entry Workflows
The vendor markets study design tools that include a drag-and-drop form builder, pre-built CDASH templates, and templated case report forms. Marketing copy states that teams can send a protocol and receive a validated study build in days, or build a study themselves in hours. The vendor also markets a free expert-managed study build as an included feature. These statements are commercial claims rather than independently verified service commitments. [2][3]
For sites entering data, the user documentation describes a participant matrix that shows data entry status, automatic saving during entry, conditional display of relevant fields, automatic calculations, edit checks, and query creation. Forms collect data for events, and the reference guide distinguishes visit-based events from common events such as adverse events, concomitant medications, and early termination. Common events can repeat or occur only once per participant. [5]
The documentation does not specify which study types or therapeutic areas the data entry behavior was tested against. The event configuration description applies to the documented OC4 workflow, and the reference guide does not state whether earlier versions behaved identically. [5]
Clinical Data Import and API Access
The Clinicaldata endpoint imports or retrieves participant clinical data in JSON or CDISC ODM XML format through the OpenClinica API. Authentication is required before calling the service, and access depends on the user's assigned role and study permissions. The documentation specifies a two-step import process: create a job with an ODM XML file, then download results after the job completes. Each import is logged separately in the audit log, even when the same XML and ZIP file is re-imported. [1][4]
File attachments can only be uploaded through the XML Import API, not through the Study Runner import screen or the Tabular Import API. Attachments require an XML import file, a ZIP containing the referenced files, and an item Value set to the matching file name. The ZIP must contain all referenced files, standard file formats are supported, and the default maximum size is approximately 2 GB. The documentation warns that OpenClinica does not validate whether an uploaded file matches the item type, so any file type can be uploaded, consistent with user interface behavior. [1][4]
API Responses and Access Scope
Retrieval of clinical data returns CDISC ODM XML or JSON according to the user's access level. A user with only site A access receives metadata and clinical data only for site A study, users, and participants. The documentation specifies required parameters for retrieving data: StudyOID or SiteOID depending on user level, ParticipantOID, with an asterisk as a wildcard for all participants, and EventOID, with an asterisk for all events. Asterisks and wildcards can be used in place of OIDs and Participant ID in request parameters. [4]
ODM XML Representation and Validation
OpenClinica provides and consumes CDISC ODM XML representations through its Extract Data and Import Data modules. The documentation specifies CDISC ODM XML version 1.3 with OpenClinica Extensions as implemented in OpenClinica 3.1 and later releases, noting that OpenClinica's ODM representation changed iteratively since version 2.5 and that a custom extension was introduced with OpenClinica 3.0. [1][6]
On extract, OpenClinica escapes the five basic XML entities using XML Entity notation and preserves whitespace literally, including line breaks and tabs in ItemData values. The documentation states that tabs and carriage returns are limited on the data entry side of the application. Not all CDISC item data types are supported: definitions exist for text and date mapping but not for time, timedate, string, boolean, double, hexBinary, base64Float, partialTime, partialDatetime, durationDatetime, intervalDatetime, incompleteDatetime, or URI. [6]
Bulk Event Data and Authentication Limits
A bulk endpoint accepts multipart form data for study event information and requires a CSV file with exactly one column headed ParticipantID containing participant IDs, plus a StudyEventOID column. The sample cURL request in the documentation uses a customer-specific server URL and a bearer authentication token. The request parameters description is tied to that documented endpoint and does not indicate whether all studies support the same columns. [1]
For token retrieval, the documentation instructs teams to stagger initial token retrieval when multiple processes need tokens so the rate limit is not exceeded when the process starts. Excessive calls to the authentication API are blocked with a 429 status code. Scripts should wait 30 seconds to one minute before retrying. These design constraints come from the API documentation rather than from an observed network test. [1]
Reporting, Alerts, and EHR-to-EDC Integration
OpenClinica Insight is described as a reporting and visualization module for interactive dashboards and reports. Users can create a report, called a Question, that polls specific item data on a schedule and sends an email when the query returns results. The documentation gives an example of hourly and daily SAE reports, noting that notification can support timely assessment and follow-up on critical safety events without manual monitoring. This is presented as a configuration example rather than a guaranteed clinical monitoring outcome. [8]
Separately, OpenClinica markets OpenClinica Unite as an EHR-to-EDC integration product. Vendor claims include transfer from any EHR to any sponsor system, compatibility with eSource-enabled EHRs, regulatory-grade data transfer, site activation in 90 minutes after health-system-level mapping, and application across all trial phases and therapeutic areas. The vendor states it has helped sponsors and research sites with EHR-to-EDC integration since 2021. These are marketing claims and should be treated as such. [7]