# Audit Logging Source: https://docs.aitriumos.com/aitrium-admin/audit-logging View, filter, and export a complete audit trail of system activity across your organization For: Organization admins at trial organizations and site organizations ## Overview Audit Logging is accessed at **Dashboard → Audit Logs**. It provides a tamper-evident audit trail of all user actions and system events across your organization — from both the **Aitrium Portal** (web application) and **AitriumOS Desktop** (native application). Audit logs support: * **Compliance reporting** — Exportable records with reason-for-change tracking * **Security monitoring** — Visibility into authentication events, access changes, and credential operations * **Operational traceability** — End-to-end tracking of data workflows, submissions, and integration activity *** ## Audit Log Table The log table displays events in reverse chronological order (newest first): | Column | Description | | - | - | | **Timestamp** | When the event occurred, displayed in your local timezone | | **Action** | Human-readable description of what was done | | **Category** | Color-coded badge indicating the event domain (see [Event Taxonomy](#event-taxonomy)) | | **Resource** | Type of resource affected (e.g., User, Site, Integration) | | **User** | Display name and email of the actor who performed the action | | **Source** | Where the action originated (see [Source Applications](#source-applications)) | All columns are sortable — click a column header to toggle sort direction. Results are paginated at 50 per page. ![Audit log table showing timestamped events with category badges](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/admin/audit-logging/audit-log-table.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=643445aae78cd5e04d64d5d8a795853b) *** ## Source Applications Every audit event records **where** the action originated. The **Source** column shows one of two values: | Source | Application | Description | | - | - | - | | **aitrium-web** | Aitrium Portal | Actions performed in the web application — user management, project configuration, credential management, and authentication | | **aitrium-desktop** | AitriumOS Desktop | Actions performed in the desktop application — clinical data tool execution, data transfers, QA submissions, and local credential management | *** ## Event Taxonomy Audit events are classified by **category** (the domain of the action) and **action** (the specific operation performed). The system enforces strict validation — each action is only valid within its designated category or categories. ### Categories and Actions > **AUTH — Authentication** > > Authentication lifecycle events from both Portal and Desktop. > > | Action | Description | Source | > | - | - | - | > | `LOGIN` | Successful user login | Portal, Desktop | > | `LOGOUT` | User logout or session end | Portal, Desktop | > | `LOGIN_FAILED` | Failed login attempt | Portal, Desktop | > | `SSO_INITIATED` | Single sign-on flow started | Portal, Desktop | > | `SSO_COMPLETED` | SSO authentication completed successfully | Desktop | > | `SSO_FAILED` | SSO authentication failed | Portal, Desktop | > | `PASSWORD_RESET_REQUEST` | Password reset email requested | Portal, Desktop | > | `PASSWORD_RESET_COMPLETE` | Password reset completed successfully | Portal | > | `PASSWORD_RESET_FAILED` | Password reset attempt failed | Portal, Desktop | > | `EMAIL_VERIFICATION_SENT` | Email verification link sent during registration | Portal | > | `EMAIL_VERIFICATION_COMPLETE` | Email address verified | Portal | > **IDENTITY\_ACCESS — User & Access Management** > > User lifecycle and permission management events, primarily from the Portal. > > | Action | Description | Source | > | - | - | - | > | `REGISTER` | New user account created (via invitation or self-service) | Portal | > | `REGISTER_FAILED` | User registration failed | Portal | > | `UPDATE_PROFILE` | User profile updated (role, site, or status change) | Portal | > | `DEACTIVATE` | User account deactivated | Portal | > | `REACTIVATE` | Previously deactivated user account restored | Portal | > | `INVITATION_SENT` | User invitation sent or refreshed | Portal | > | `INVITATION_FAILED` | User invitation failed to send | Portal | > | `INVITATION_VERIFIED` | Invitation link verified during registration | Portal | > | `INVITATION_VERIFICATION_FAILED` | Invitation verification failed (expired or invalid) | Portal | > | `GRANT_ACCESS` | Access granted to a user (role or site assignment) | Portal | > | `REVOKE_ACCESS` | Access revoked from a user (invitation revoked or permission removed) | Portal | > **CLINICAL\_DATA — Clinical Data Operations** > > Clinical data access and processing events. Portal handles project/protocol-level actions; Desktop handles data tool execution. > > | Action | Description | Source | > | - | - | - | > | `CREATE` | Clinical resource created (e.g., project, dataset) | Portal | > | `READ` | Clinical data accessed or viewed (e.g., DICOM dataset analysis) | Desktop | > | `UPDATE` | Clinical resource updated | Portal | > | `DELETE` | Clinical resource deleted | Portal | > | `EXPORT` | Clinical data exported | Portal | > | `IMPORT` | Clinical data imported | Portal | > | `PUBLISH` | Protocol or clinical resource published | Portal | > | `UNPUBLISH` | Protocol or clinical resource unpublished | Portal | > | `SHARE` | Clinical data shared | Portal | > | `ARCHIVE` | Clinical data archived | Portal | > | `RESTORE` | Archived clinical data restored | Portal | > | `ANONYMIZE` | DICOM data de-identified (severity: Critical) | Desktop | > | `VALIDATE` | Data validated against policy or DICOM standards (severity: Medium) | Desktop | > | `TOKENIZE` | Patient identifiers tokenized (severity: High) | Desktop | > | `REDACT` | Sensitive data redacted from documents (severity: High) | Desktop | > **SUBMISSION — Data Transfers & QA** > > Data transfer and quality assurance events from the Desktop application's contribution workflows. > > | Action | Description | Source | > | - | - | - | > | `QA_SUBMIT` | QA metrics submitted for a contribution | Desktop | > | `QA_EVALUATE` | QA evaluation triggered against a policy | Desktop | > | `TRANSFER_COMPLETE` | Data transfer workflow completed successfully | Desktop | > | `TRANSFER_FAILED` | Data transfer workflow failed | Desktop | > | `DATA_TRANSFER_COMPLETED` | Integration-level data transfer completed (e.g., SFTP upload) | Desktop | > | `DATA_TRANSFER_FAILED` | Integration-level data transfer failed | Desktop | > **INTEGRATION — Integration Operations** > > Integration synchronization and execution events. > > | Action | Description | Source | > | - | - | - | > | `API_CALL` | External API call made | Portal | > | `WEBHOOK_TRIGGERED` | Webhook event triggered | Portal | > | `SYNC_COMPLETED` | Integration sync completed (e.g., platform contribution sync) | Desktop | > **CREDENTIAL — Credential Management** > > Credential and integration access management from both Portal and Desktop. > > | Action | Description | Source | > | - | - | - | > | `ACCESS` | Credential accessed | Portal | > | `CREATE` | Credential group created, or users added to credential group | Portal | > | `UPDATE` | Credentials updated (SFTP config, connection status, etc.) | Portal, Desktop | > | `DELETE` | Credential group deleted, or user removed from credential group | Portal, Desktop | > | `ROTATE` | Credentials rotated | Portal | > | `TEST_CONNECTION` | Integration connection test performed | Desktop | > **POLICY\_COMPLIANCE — Policy & Compliance** > > Policy management and compliance-related events. > > | Action | Description | Source | > | - | - | - | > | `UPDATE_CHECK` | Policy update check performed | Portal | > | `DOWNLOAD` | Policy downloaded to Desktop for local evaluation | Desktop | > | `VALIDATE` | Policy validation performed | Portal | > | `EXPORT` | Policy or compliance report exported | Portal | > **CONFIGURATION — System Configuration** > > Configuration changes to system settings, sites, and integration infrastructure. > > | Action | Description | Source | > | - | - | - | > | `CONFIG_UPDATE` | System configuration changed | Portal | > | `SYSTEM_UPDATE` | System-level update applied | Portal | > | `MAINTENANCE` | Maintenance operation performed | Portal | > | `INTEGRATION_ENABLED` | Integration enabled for organization | Portal | > | `INTEGRATION_DISABLED` | Integration disabled for organization | Portal | > | `API_KEY_GENERATED` | API key generated | Portal | > | `API_KEY_REVOKED` | API key revoked | Portal | > | `WEBHOOK_CONFIGURED` | Webhook endpoint configured | Portal | > | `UPDATE` | Configuration resource updated (e.g., site external ID, label mapping) | Portal, Desktop | > **SYSTEM — System Events** > > System-level events and application lifecycle. > > | Action | Description | Source | > | - | - | - | > | `DOWNLOAD_APPLICATION` | AitriumOS Desktop application downloaded | Portal | > | `HEALTH_CHECK` | System health check performed | Portal | ### Resource Types Each audit event references the type of resource affected: | Resource Type | Description | | - | - | | **User** | User accounts and profiles | | **Site** | Research sites | | **Project** | Clinical research projects | | **Protocol** | Clinical protocols | | **Integration** | External system integrations | | **Credential Group** | Integration credential groups | | **Data Policy** | Data compliance policies | | **Role** | User role assignments | | **Organization** | Organization records | | **Site Contribution** | Data submissions to a project from a site | | **Data Tool Run** | Execution of a clinical data tool (Desktop) | | **Document** | Files and documents | | **Audit Log** | Audit log export records | *** ## Filtering Audit Logs ### Filter Presets Quick-access presets surface common views with one click: | Preset | What It Shows | | - | - | | **Auth Failures** | Failed login and SSO attempts (`LOGIN_FAILED`, `SSO_FAILED`) | | **Identity Access** | User management and permission changes (all `IDENTITY_ACCESS` events) | | **Clinical Data** | Data access and modification events (all `CLINICAL_DATA` events) | | **Integration Access** | Integration execution and credential events (`INTEGRATION` and `CREDENTIAL` categories) | | **Policy Compliance** | Policy-related actions (all `POLICY_COMPLIANCE` events) | ![Filter preset buttons for quick access to common audit views](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/admin/audit-logging/filter-presets.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=bfc6a80f88b5e8cd047a806973352720) ### Quick Date Filters * **Today** — Events from the current day * **Last 7 Days** — Events from the past week ### Advanced Filters Click **More Options** to access the full set of filters: | Filter | Description | | - | - | | **Action Categories** | Multi-select from the 9 event categories | | **Event Types** | Filter by specific actions (e.g., `LOGIN_FAILED`, `INVITATION_SENT`, `ANONYMIZE`) | | **Resource Types** | Filter by affected resource type | | **Integration Operations** | Filter by specific integration operation names | | **Date Range** | Custom from/to date picker | | **Search** | Full-text search across action, category, resource, email, and event details | Active filters display as badges with a total count indicator. Click **Reset** to clear all filters. ![Advanced filter panel with multi-select dropdowns and date range picker](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/admin/audit-logging/advanced-filters.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=d94935add1ce415c3f59899183d82500) *** ## Viewing Log Details Click **View Details** on any row to open the detail dialog, which displays: * **Actor** — Who performed the action (display name and email) * **Action Details** — Structured grid of event properties as label/value pairs * **Request Information** — Source application, timestamp, and request context * **Additional Metadata** — Full event context in JSON format (scrollable for large entries) ![Audit log detail dialog showing actor, action details, and metadata](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/admin/audit-logging/log-detail-dialog.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=94f0011abab9d2c2ce1629588134b868) *** ## Exporting Audit Logs Export filtered audit logs as a CSV file for compliance reporting or offline analysis. 1. Apply your desired filters (presets, date range, or advanced filters) 2. Click **Export** 3. Review the export dialog, which shows: * **Total rows** that will be exported * **Active filters** applied to the export 4. Confirm to download the CSV file ![Export dialog showing row count and active filter summary](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/admin/audit-logging/export-dialog.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=228cae154d1b8e377bef422ed3223f5f) ### Export Details | Property | Value | | - | - | | **Format** | CSV | | **File name** | `audit-logs-export-{timestamp}.csv` | | **Row limit** | 50,000 rows per export | | **Included columns** | Event time (UTC), recorded time (UTC), actor email and display name, action, category, outcome, target resource type and display name, target user (if applicable), source app, authentication method, reason for change, change reference, details summary | | **Excluded data** | IP addresses, authentication tokens, raw internal IDs, API keys, passwords, and other sensitive fields are automatically excluded | > [!NOTE] > > If your filtered results exceed 50,000 rows, narrow your filters (e.g., reduce the date range or add category filters) and export in batches. # Integrations Source: https://docs.aitriumos.com/aitrium-admin/integrations Configure data transfer integrations, manage credential groups, and control trial-level access For: Trial organization admins ## Overview The Integrations page allows organization administrators to manage data transfer integrations, credentials, and user permissions. Integrations are accessed at **Dashboard → Integrations**. Integrations are configured by the **trial organization** that receives the data. Participating sites do not enter or manage transfer credentials. The IT team that operates your SFTP server should read [SFTP server compatibility](/security/aitrium-os/sftp-compatibility). Each integration card displays: * Integration name * Credential type (**Cloud Credentials** or **Local Config**) * Number of sites using the integration Click on any integration card to manage its settings. ![Integrations page showing list of configured integrations](https://mintcdn.com/aitrium/Oz3RPd1teRou2Jhk/images/integrations/integrations_page.png?fit=max\&auto=format\&n=Oz3RPd1teRou2Jhk\&q=85\&s=61b802aaf9fc8560689a801914869b26) ### What if I don't see any integrations? If no integrations appear, your organization hasn't been set up with any data transfer integrations yet. Contact support at [contact@aitriumos.com](mailto:contact@aitriumos.com) to request integration setup. *** ## Credential Groups Credential groups allow you to manage different sets of credentials within the same integration. This is useful when: * Different sites require different connection endpoints or credentials * You want to segregate credentials for security or organizational reasons * Different trials need to route data through different systems ![Integration details page showing credential groups in the left sidebar](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/integrations/integration_details_page_credential_groups.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=8b7a8cdaa1f56cd04c136809d03fad81) ### Key Features * **Multiple Groups**: Create multiple credential groups per integration * **Independent Credentials**: Each group has its own connection configuration * **Trial Linking**: Link trials to a credential group to control which credentials are used for data transfers * **Per-Site User Access**: Control which users at each site can access the integration, per trial ### Creating a Credential Group 1. Open an integration from the main Integrations page 2. Navigate to the **Credential Groups** tab 3. Click **Create New Group** in the left sidebar 4. Provide: * **Group Name**: A descriptive name for the credential group * **Description** (optional): Additional context about the group's purpose 5. Click **Create** to save the new group ![Create new credential group dialog](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/integrations/new_credential_group.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=06937af2530888973f97bdf6a9222d19) ### Editing a Credential Group 1. Select the credential group from the left sidebar 2. Click the **Edit** button (pencil icon) 3. Update the group name or description 4. Click **Save** to apply changes ### Deleting a Credential Group 1. Select the credential group to delete 2. Click the **Delete** button (trash icon) 3. Confirm the deletion in the dialog > [!NOTE] > > You must have at least one credential group per integration. The last group cannot be deleted. *** ## Managing Credentials Each credential group has a **Credentials** tab where you configure the connection details for that group. ### Viewing Current Credentials 1. Select a credential group from the left sidebar 2. The **Credentials** tab displays all configuration fields 3. Sensitive fields (passwords, private keys) display a **"Stored securely"** badge — values are never shown in plain text ### Updating Credentials 1. Select a credential group 2. Click **Edit** to enter edit mode 3. Modify the credential fields as needed: * **Text fields**: Enter alphanumeric values * **Number fields**: Enter numeric values only * **Boolean fields**: Toggle on/off * **Secret fields**: Enter passwords (masked on input) * **File fields**: Upload key files or certificates 4. Click **Save** to publish changes 5. Click **Cancel** to discard unsaved changes ### How Credential Updates Propagate When you update credentials: * Changes are automatically published to all sites assigned to the credential group * Credentials are re-encrypted with each site's encryption key before distribution * The system tracks all credential updates in the [Audit Log](/aitrium-admin/audit-logging) > [!WARNING] > > Credential updates affect all trials and users linked to this credential group. Ensure credentials are correct before saving. *** ## SFTP Configuration When an integration uses SFTP for data transfer, credential groups contain the following configuration fields: | Field | Required | Description | | - | - | - | | **Host** | Yes | SFTP server hostname or IP address | | **Port** | Yes | SFTP server port (typically 22) | | **SFTP Username** | Yes | Authentication username | | **SFTP Password** | Yes | Authentication password | | **Root Directory** | No | Base directory path on the SFTP server. If omitted, the default directory is used. | | **Private Key (RSA)** | No | RSA private key for key-based authentication. PEM format (`-----BEGIN RSA PRIVATE KEY-----`) is recommended and works on every workstation. OpenSSH format (`-----BEGIN OPENSSH PRIVATE KEY-----`) is also accepted, but Windows workstations then need the Windows **OpenSSH Client** feature installed. ECDSA and Ed25519 keys and PuTTY `.ppk` files are not supported. | | **Private Key Password** | No | Passphrase for the private key, if the key is encrypted. | > [!NOTE] > > When both password and private key are provided, key-based authentication takes precedence. The SFTP server must allow sign-in with a password or a public key; keyboard-interactive and multi-factor sign-in are not supported. Sites connect directly from their own network, so a server that restricts IP addresses must allow each site's public egress IP address. For supported SSH algorithms and the traffic your server will see, share [SFTP server compatibility](/security/aitrium-os/sftp-compatibility) with the server's IT team. ### Upload destination reachability From AitriumOS 2.2.6, each installation checks whether it can reach its trials' SFTP servers and reports the latest result to Aitrium. The check is a handshake only: it never signs in or transfers data. Site users can run it from **Settings → Network → Upload destinations → Check now**; see [Upload connection troubleshooting](/aitrium-os/connection-troubleshooting). The results feed site readiness in Aitrium Web: * **Organizations that own a site** see, under **Dashboard → Sites** → the site → **Readiness**, an **Upload destinations** section listing each trial's destination (host and port) with its latest check: **Reachable**, **Blocked**, **Check failed**, **Not yet tested** or **Not yet reported**. Installations older than AitriumOS 2.2.6 don't report. The same tab offers an IT checklist download. * **Trial organizations** see an **Upload server** status in each site's readiness for the trial, showing whether the site's upload connection is working or blocked. Only the destination, the result and when it was checked are reported, with the negotiated encryption algorithms and the server's host key fingerprint after a successful check. Credentials, patient data and workstation IP addresses are never reported. *** ## Credential Encryption All integration credentials are encrypted at rest using organization-level encryption keys managed through a Key Management Service (KMS). ### Owning Organization Your organization owns the credential group and its encryption keys. Credentials are encrypted with your organization's KMS key before storage — they are never stored in plaintext. ### External Participating Sites When external provider sites are assigned to a credential group through trial linking: * Credentials are re-encrypted with site-level keys for secure distribution * Each site receives only the credentials relevant to their assignment * Credential transport uses session-derived encryption for additional security This ensures that credentials are never transmitted in plaintext, and each participant only has access to the credentials they need. *** ## Managing Trial Access Integration permissions are managed at the trial level. Each credential group has a **Trials** tab where you link trials and control per-site user access. ### Permission Hierarchy Permissions follow a trial-scoped hierarchy: **Integration → Credential Group → Trial → Site → Users** * An integration has one or more **credential groups**, each with its own connection configuration * Each credential group can be linked to one or more **trials** * Different trials can use different credential groups — even for the same site. This means a site can have separate credentials for each trial it participates in. * At each site, you control which **users** have access — either all site users or a selected subset ### Linking a Trial to a Credential Group 1. Select a credential group from the left sidebar 2. Navigate to the **Trials** tab 3. Click **Add Trial** 4. Search for and select the trial from the list > [!NOTE] > > Trials already linked to this credential group are excluded from the search results. Credentials must be configured before you can add trials. ### Per-Trial Credential Groups Different trials can be linked to different credential groups, even when they share the same sites. This allows you to: * Route data for Trial A through one SFTP endpoint and Trial B through another * Use separate credentials for different sponsors or data destinations * Isolate trial data flows without creating duplicate sites When the same site participates in multiple trials with different credential groups, each trial's data transfers use the credentials from its linked credential group. ### Trial Overview Once trials are linked, the Trials tab displays each trial as a collapsible row: * **Trial name** with site count and active/inactive status * **Readiness indicators**: * Green dot — Site is transfer-ready (credentials and users configured) * Red dot — Site is blocked (missing credentials or user configuration) * Summary: "N sites not ready" when blocked sites exist * **Header metrics**: Number of trials linked and total access patterns configured Expand a trial to see all sites and their access configuration. ![Credential group Trials tab showing linked trials with site readiness indicators](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/integrations/credential-group-trials-tab.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=ae1031ff563493570a94fca330ceb9ce) ### Managing Site Access Click **Manage access** on any site within a trial to configure user permissions: **Access Modes:** | Mode | Description | | - | - | | **All site users** | Every user at the site automatically has access to the integration for this trial. New users added to the site will inherit access. | | **Selected users** | Only explicitly chosen users have access. You must add users individually. | **In "Selected users" mode:** * Search for users by name * Click **Add** to grant a user access * Click **Remove** to revoke a user's access * The drawer shows users split into "Has Access" and "No Access" sections ![Site access management drawer showing access mode selection and user list](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/integrations/manage-site-access-drawer.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=1f5ab6199addd7dbc662c56f0ffd2e7e) ### Removing a Trial 1. Expand or hover over the trial in the Trials tab 2. Click the dropdown menu on the trial header 3. Select **Remove Trial** 4. Confirm the removal Removing a trial from a credential group revokes all associated user access for that trial. *** ## Managing Access from Trials In addition to the Integrations page, admins can manage integration access directly from a trial's detail page. This is useful when you're working within a trial and want to configure site access without navigating to the Integrations section. 1. Navigate to **Dashboard → Projects → \[Trial Name]** 2. Switch to the **Sites** tab 3. Each site row displays an **Access** column: * Shows the number of users with access (e.g., "3 Users") * Or **"Set Access"** if no permissions are configured yet 4. Click the access count or select **Manage Access** from the row's dropdown menu 5. The site access drawer opens — the same interface described in [Managing Site Access](#managing-site-access) above ![Trial sites tab showing the Access column with user counts and Manage Access action](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/integrations/project-sites-access-column.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=488a90039e4e9202056b483fc5d9525b) > [!NOTE] > > Both entry points — the Integrations page and the Trial sites tab — manage the same underlying permissions. Changes made in one location are immediately reflected in the other. *** ## Integration Logs The Integration Logs tab provides execution logs showing when the integration has run and whether it succeeded or failed. This is useful for monitoring integration health and debugging issues. ### Log Analytics The **Overview** tab provides a visual summary of integration execution history, including: * Time series chart of success, warning, and failure events * Recent activity list (last 10 events) * Summary metrics: total events, success rate, error count, warning count The **Errors** tab breaks down failures by category: * **Authentication** — credential or permission issues * **Connection** — network or timeout failures * **Configuration** — setup or path issues * **Transfer** — upload/download failures * **Validation** — format or schema errors ![Integration log analytics showing execution metrics and error breakdown](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/integrations/integration-log-analytics.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=b713d432833a34b4f5d515eb823d6cbb) ### Execution Details The **Details** tab shows a chronological table of all integration executions: | Column | Description | | - | - | | **Timestamp** | When the execution occurred | | **Action** | What the integration performed | | **Status** | Success or failure | | **Details** | Additional context about the execution | The table is searchable and sortable by timestamp (default: newest first). Use the time range filter (1 day, 7 days, 30 days) to narrow results. ### Troubleshooting with Logs * Identify when an integration last ran successfully * Diagnose technical failures or connection issues * Monitor integration performance and reliability * Debug data transfer problems *** ## Common Tasks ### Granting a User Access to a Trial's Integration 1. Navigate to **Integrations** → Select the integration 2. Select the **Credential Group** linked to the trial 3. Go to the **Trials** tab and expand the trial 4. Click **Manage access** on the relevant site 5. Set the access mode to **Selected users** (if not already) 6. Find and **Add** the user Alternatively, navigate to **Projects → \[Trial] → Sites** tab and click **Manage Access** on the site row. ### Rotating Integration Credentials 1. Navigate to **Integrations** → Select the integration 2. Select the **Credential Group** to update 3. Go to the **Credentials** tab and click **Edit** 4. Update the credential fields with new values 5. Click **Save** 6. Verify the update in the [Audit Logs](/aitrium-admin/audit-logging) page ### Connecting a New Trial to a Credential Group 1. Navigate to **Integrations** → Select the integration 2. Select the **Credential Group** (or create a new one) 3. Ensure credentials are configured on the **Credentials** tab 4. Go to the **Trials** tab and click **Add Trial** 5. Search for and select the trial 6. Expand the trial and configure site access for each site ### Restricting Access to Specific Users at a Site 1. Navigate to the credential group's **Trials** tab 2. Expand the trial containing the site 3. Click **Manage access** on the site 4. Change the access mode from **All site users** to **Selected users** 5. Add only the users who should have access 6. Users not explicitly added will lose access *** ## Troubleshooting ### Problem: Can't See Any Integrations **Solution**: Your organization may not have integrations configured. Contact support at [contact@aitriumos.com](mailto:contact@aitriumos.com) to set up integrations. ### Problem: Can't Update Credentials **Possible Causes**: * Required fields are missing * Invalid values entered (e.g., text in a number field) * Insufficient permissions **Solution**: Check that all required fields are filled and valid. Ensure you have administrator permissions. ### Problem: Can't Add a Trial to a Credential Group **Possible Causes**: * Credentials have not been configured yet for the group * The trial is already linked to this credential group **Solution**: Configure credentials on the **Credentials** tab first. Check whether the trial is already linked. ### Problem: Site Shows as "Blocked" (Red Dot) **Possible Causes**: * Credentials are missing or incomplete for the credential group * No users have been granted access at the site **Solution**: Verify credentials are configured on the **Credentials** tab. Click **Manage access** on the blocked site and ensure at least one user has access. ### Problem: Credential Updates Not Taking Effect **Solution**: * Verify the update was successful in the [Audit Logs](/aitrium-admin/audit-logging) page * Ensure the trial's sites are assigned to the correct credential group * Contact support if the issue persists ### Problem: Integration Execution Failures **Solution**: * Check the **Logs** tab on the integration detail page for error messages * Review recent credential changes in [Audit Logs](/aitrium-admin/audit-logging) that might have caused issues * Verify network connectivity to the integration endpoint * Contact support with the error details from the Integration Logs For audit log questions, see [Audit Logging](/aitrium-admin/audit-logging). *** ## Getting Help If you need assistance with integration management: * **Email**: [contact@aitriumos.com](mailto:contact@aitriumos.com) * **Subject Line**: Integration Management Support * **Include**: * Your organization name * Integration name * Description of the issue * Screenshots (if applicable) # Network Management Source: https://docs.aitriumos.com/aitrium-admin/network-management Create and manage internal sites, view external sites, and configure site identifiers for data transfers For: Organization admins at trial organizations and site organizations ## Overview Network Management is accessed at **Dashboard → Network**. It provides a unified view of your organization's sites, for trial organizations and site organizations alike: * **Internal sites** — Sites your organization creates and manages directly * **External sites** — Sites created by Aitrium and connected to your organization for cross-organizational workflows (e.g., multi-site clinical trials) *** ## Network Dashboard The Network page displays statistics and a searchable site table. ### Statistics * **My Sites** — Number of internal sites your organization manages * **External Sites** — Number of connected external sites * **Total Sites** — Combined count * **Organizations** — Number of organizations in your network (including your own) ### Site Table | Column | Description | | - | - | | **Site Name** | Name of the site | | **Organization** | Owning organization, with an **Internal** or **External** badge | | **Type** | Internal Site or External Site | | **Site External ID** | External identifier for data transfer file naming (editable) | | **Org External ID** | External organization identifier (editable for external entries) | Use the filter toggle (**All / Internal / External**) to narrow the view, or search by organization or site name. ![Network management dashboard showing site statistics and table](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/admin/network-management/network-overview.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=05d5883e3ecd62b5c243336af2d62f41) *** ## Internal Sites ### Creating an Internal Site 1. Navigate to **Dashboard → Network** 2. Click **Create Site** 3. Enter the **Site Name** 4. Optionally enter a **Site External ID** — this is used in file naming conventions for data transfers (see [External IDs](#external-ids) below) 5. Optionally check **Invite a user to this site** to send an invitation during site creation: * Enter the user's email address * Select a role 6. Click **Create** ![Create internal site dialog with name, external ID, and optional user invite fields](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/admin/network-management/create-internal-site.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=debebfac9d3912fbae7e52eb0ebcc463) Internal sites belong to your organization and can have users assigned to them through [User Management](/aitrium-admin/user-management). *** ## External Sites ### How External Sites Work External sites are created by Aitrium and connected to your organization to enable cross-organizational data workflows. You **cannot** create external sites yourself — they appear in your network automatically once Aitrium connects them to your organization. External sites display: * The site name and the external organization they belong to * An **External** badge to distinguish them from your internal sites * External ID fields for integration mapping If you need an external site added to your network, contact Aitrium support at [support@aitriumos.com](mailto:support@aitriumos.com). *** ## External IDs ### Purpose External IDs map your internal site and organization identifiers to the naming conventions expected by integration partners. When a **Site External ID** is set, it is used in the file naming convention for transferred patient datasets — ensuring files are named according to the receiving system's expectations. ### Setting a Site External ID 1. Find the site in the Network table 2. Click the **Site External ID** cell to enter inline edit mode 3. Enter the external identifier 4. Click the **checkmark** (✓) to confirm, or **X** to cancel ![Inline editing of a site external ID in the network table](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/admin/network-management/external-id-editing.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=34190a20ae103c51a5707ca049928e94) > [!NOTE] > > Org External IDs follow the same inline editing pattern and are available on external organization entries. They map your organization's identity to the external system's naming convention. # Organization administration Source: https://docs.aitriumos.com/aitrium-admin/overview Overview of Aitrium's administration capabilities for managing users, networks, audit logs, and integrations For: Organization admins at trial organizations and site organizations ## Overview Aitrium's administration features give organization administrators centralized control over users, sites, integrations, and compliance. Admin features are available to users with the **Admin** role and are accessed from the **Admin** section in the Aitrium Portal sidebar. Every organization on Aitrium has its own administrators, whether it runs trials (a **trial organization**) or contributes data from its sites (a **site organization**). Most admin pages apply to both; data transfer integrations are configured by the trial organization. *** ## Which pages apply to your organization | Page | Trial organizations | Site organizations | | - | - | - | | [User Management](/aitrium-admin/user-management) | Yes | Yes | | [Network Management](/aitrium-admin/network-management) | Yes — internal sites, plus external sites that Aitrium connects for multi-site trials | Yes — your internal sites | | [Audit Logging](/aitrium-admin/audit-logging) | Yes | Yes | | [Integrations](/aitrium-admin/integrations) | Yes — SFTP credentials and which sites and users may transfer data for each trial | No — transfer credentials are set by the trial organization. Upload destination results appear in your site's readiness ([details](/aitrium-admin/integrations#upload-destination-reachability)). | *** ## Admin pages > **[User Management](/aitrium-admin/user-management)** > > All organizations. Invite users, manage roles, assign sites, and control access across your organization. > **[Network Management](/aitrium-admin/network-management)** > > All organizations. Create internal sites, view external sites, and configure site identifiers for data transfers. > **[Audit Logging](/aitrium-admin/audit-logging)** > > All organizations. View, filter, and export a complete audit trail of system activity across your organization. > **[Integrations](/aitrium-admin/integrations)** > > Trial organizations. Configure credential groups, manage trial-level access, and monitor integration execution. *** ## Roles & Permissions Aitrium uses two customer-facing roles that determine what a user can access: | Role | Scope | Admin Features | | - | - | - | | **Admin** | Organization-wide | Full access to all admin features — user management, network, audit logs, and integrations. Not restricted to specific sites. | | **User** | Site-specific | Standard access to workflows and data associated with their assigned site(s). No access to admin features. | Admin users can manage all users and sites within their organization. User-role members only see data and workflows for the sites they've been assigned to. # User Management Source: https://docs.aitriumos.com/aitrium-admin/user-management Invite users, manage roles, assign sites, and control access across your organization For: Organization admins at trial organizations and site organizations ## Overview User Management is accessed at **Dashboard → Users**. Admins can invite new users, manage existing user roles and site assignments, and track invitation status. This works the same way for trial organizations and site organizations: each organization's admins manage only their own organization's users. Aitrium has two customer-facing roles: * **Admin** — Organization-wide access to all features, including administration * **User** — Access scoped to an assigned site *** ## Users Dashboard The Users page provides an at-a-glance summary of your organization's user base along with a detailed table for management. ### Statistics * **Total Users** — Count of active and inactive users * **Administrators** — Number of users with the Admin role * **Pending Invitations** — Invitations awaiting acceptance * **Invitation Status** — Breakdown of accepted vs. expired invitations ### User Table The table displays all users and invitations with the following columns: | Column | Description | | - | - | | **Email** | User's email address | | **Status** | Active, Inactive, Pending, or Expired | | **Role** | Admin or User | | **Site** | Organization-wide (for Admins) or the assigned site name | | **Last Activity** | Most recent activity or creation date | You can toggle between a **unified view** (users and invitations in a single list) or a **tabbed view** (separate tabs for each). Use the status and site filters to narrow the list, or search by name or email. ![Users dashboard showing statistics cards and user table](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/admin/user-management/users-dashboard.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=7084aaeec6f71b3a5618c283fa34a48f) *** ## Inviting Users > [!NOTE] > > Invitations are always limited to your own organization. Users invited with the **User** role can only access data and workflows for their assigned site. ### Inviting an Admin User 1. Navigate to **Dashboard → Users** 2. Click **Invite User** 3. Enter the user's email address 4. Select the **Admin** role 5. Click **Send Invitation** Admin users have organization-wide access — no site assignment is needed. ### Inviting a User with Site Assignment 1. Navigate to **Dashboard → Users** 2. Click **Invite User** 3. Enter the user's email address 4. Select the **User** role 5. Select a **Site** from the dropdown 6. Click **Send Invitation** User-role invitations require a site assignment. The user will only have access to data and workflows associated with that site. ![Invite user dialog with role and site selection](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/admin/user-management/invite-user-dialog.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=637f1b706d46af95e00ddccc3326480e) ### Invitation Lifecycle * Invitations are valid for **7 days** from creation * Status flow: **Pending** → **Accepted** (user completes registration) or **Expired** (7 days elapsed) * Only one active invitation can exist per email address * If a previously deactivated user is re-invited, the system handles it as a **reactivation** — their existing account is restored with the new role and site assignment *** ## Managing Invitations ### Refreshing an Invitation Refreshing extends the invitation expiration by 7 days from the current time: 1. Find the pending or expired invitation in the Users table 2. Click the actions menu (⋮) → **Resend Invitation** 3. The invitation link is refreshed and re-sent to the user's email ### Revoking an Invitation Revoking permanently removes a pending invitation: 1. Find the invitation in the Users table 2. Click the actions menu (⋮) → **Remove Invitation** 3. Confirm the removal > [!NOTE] > > Revoking an invitation permanently deletes it. If you need to re-invite the user, you'll need to create a new invitation. *** ## Managing Existing Users ### Changing a User's Role 1. Find the user in the Users table 2. Click the actions menu (⋮) → **Edit User** 3. Change the **Role** (Admin or User) 4. If changing to User, select a site assignment 5. Save changes ![Edit user dialog showing role and site fields](https://mintcdn.com/aitrium/3WnG7yixUbGSLasn/images/admin/user-management/edit-user-dialog.png?fit=max\&auto=format\&n=3WnG7yixUbGSLasn\&q=85\&s=fc55c52e41cd74fea1b12a9549c92de7) ### Adding or Changing User Sites 1. Find the user in the Users table 2. Click the actions menu (⋮) → **Edit User** 3. Update the **Site** assignment 4. Save changes > [!NOTE] > > Admin-role users have organization-wide access and are not restricted to specific sites. Site assignment only applies to the User role. ### Deactivating a User 1. Find the user in the Users table 2. Click the actions menu (⋮) → **Deactivate User** 3. Confirm deactivation Deactivated users immediately lose access to the platform. Their account status changes to **Inactive** and their organization association is removed. They can be re-invited later, which triggers a reactivation flow that restores their account with the new role and site assignment. # Upload connection troubleshooting Source: https://docs.aitriumos.com/aitrium-os/connection-troubleshooting Check whether AitriumOS can reach a trial's SFTP server, and what each upload connection message means. For: Site users · Site IT ## How uploads connect For trials that transfer data over SFTP, AitriumOS sends the prepared, de-identified dataset **directly from the workstation** to the trial's SFTP server. It connects on the port the trial organization configured, usually TCP 22. * **This connection does not use a web (HTTP) proxy.** A corporate proxy handles AitriumOS's HTTPS traffic to Aitrium only. The workstation must be allowed to open the SFTP connection itself. * **It is separate from the "Can't reach Aitrium" check.** AitriumOS can connect to Aitrium normally while the trial's SFTP server is still blocked, so check both. * **The trial's SFTP server sees the site's public IP address**, not Aitrium's. Some trial organizations only accept connections from addresses they have approved. See [If the trial's server restricts IP addresses](#if-the-trials-server-restricts-ip-addresses). ## Check an upload destination Open **Settings → Network** in AitriumOS. The **Upload destinations** list shows each SFTP server your trials send data to, with its host and port, the latest result and when it was checked. Select **Check now** to test a destination immediately. You can check again 10 seconds after the previous check finishes. > [!NOTE] > > A destination appears once you have access to a trial that sends data by SFTP. Until then the list shows **No upload destinations yet**. ### What a check does A check is a **handshake only**. AitriumOS looks up the server's address, opens a connection, confirms the server answers as an SSH server and agrees on encryption with it, then disconnects. A check **never signs in, never uses the trial's credentials and never transfers data**. On the trial organization's server it appears as a short connection that normally ends with the disconnect reason `AitriumOS reachability check`. ### Automatic checks From AitriumOS 2.2.6, destinations are also checked automatically: * **Daily.** While AitriumOS is open, each destination is checked at most once a day per workstation, at a randomized time. The daily check is skipped when an upload or a connection test to that destination succeeded in the last 24 hours, because that already proved the connection works. * **Before a first submission.** When you open a submission to a destination this workstation has never uploaded to, AitriumOS checks it, unless it was checked in the last hour. * **No automatic retries.** A failed automatic check is not repeated until the next day. Select **Check now** after IT makes a change. Aitrium can pause automatic checks. **Check now** always runs. ### Who else sees the result AitriumOS reports the latest result for each destination to Aitrium. The report includes the destination's host and port, the result and when it was checked, plus the negotiated encryption algorithms and the server's host key fingerprint after a successful check. It never includes credentials, patient data, file names, the workstation's IP address or proxy details. These results appear in site readiness, so your organization's administrators, the trial organization and Aitrium support can see when a destination is blocked. See [Upload destination reachability](/aitrium-admin/integrations#upload-destination-reachability). ### Transfer status on the trial dashboard The trial dashboard header shows the trial's data transfer status: **Transfer connected**, **Transfer failed** or **Not checked yet**. This is a full connection test: unlike a reachability check, it signs in with the trial's credentials, but it transfers no data. Hover over the status to see the message and when it was checked, and select it to test again. ## What the messages mean ### Upload destinations list The examples below use `sftp.example.org` and port `22`; AitriumOS shows your destination's host and port. On macOS, messages name **AitriumOS** instead of **AitriumOS (NewLeaf.exe)**. | Message | What it means | Who acts | | - | - | - | | **Reachable** | The server answered and the handshake completed. | No action needed. | | **Not yet checked** | No check has run on this workstation yet. | Select **Check now**. | | **Blocked by a firewall — ask IT to allow outbound TCP 22 to sftp.example.org for AitriumOS (NewLeaf.exe)** | The computer refused to let AitriumOS open the connection. A firewall or endpoint-security rule on the workstation or its network is blocking this program. | Site IT: allow the connection for the program. See [Allowing the connection](#for-site-it-allowing-the-connection). | | **No response from sftp.example.org:22 — ask IT to allow outbound TCP 22 to sftp.example.org for AitriumOS (NewLeaf.exe)** | Nothing answered. Usually a firewall is silently dropping the traffic, either the site's outbound firewall or the trial server's IP restrictions. | Site IT first. If the site's firewall allows the connection, the trial organization must approve the site's [public IP address](#if-the-trials-server-restricts-ip-addresses). | | **Unreachable — sftp.example.org:22 refused the connection** | The server, or a device in front of it, actively refused the connection. Typically nothing is listening on that port, or the server's firewall rejects the site's address. | Trial organization: confirm the host and port, and approve the site's public IP address if they restrict addresses. | | **Can't connect to sftp.example.org:22 — ask IT to allow outbound TCP 22 to sftp.example.org for AitriumOS (NewLeaf.exe)** | The connection failed for another network reason, for example no route to the server. | Site IT. | | **Unreachable — sftp.example.org could not be found** | The server's name could not be resolved. | Site IT: confirm the workstation can resolve external names. If the name itself is wrong, the trial organization corrects it. | | **No SFTP response — ask IT to allow outbound sftp.example.org:22** | The connection opened, but no SSH server answered. Something between the workstation and the server accepted the connection instead, such as a proxy, a TLS-inspection device or an application-aware firewall that only allows web traffic, or the port is not an SFTP port. | Site IT. If nothing on the site's network intercepts the traffic, the trial organization confirms the port. | | **Secure connection could not be set up — contact Aitrium support** | The server answered as an SSH server, but AitriumOS and the server could not agree on security settings. | Contact [Aitrium support](mailto:support@aitriumos.com). The trial organization can compare its server settings with [SFTP server compatibility](/security/aitrium-os/sftp-compatibility). | | **Check did not complete** | The check stopped because of a local error. | Select **Check now** again. If it persists, contact support. | | **Blocked — ask IT to allow outbound sftp.example.org:22** | Network blocked. AitriumOS 2.2.6 shows this for both firewall blocks and unanswered connections. | Site IT, as for the two messages above. | > [!NOTE] > > AitriumOS 2.2.7 separates results that 2.2.6 grouped together. In 2.2.6, a firewall block and an unanswered connection both show **Blocked — ask IT to allow outbound …**, and any connection failure other than a missing name shows **Unreachable — … refused the connection**. ### Upload and connection test messages These appear when an upload fails and in the trial dashboard's transfer status. The transfer status shows the full message right after a test, and a one-line summary for a stored result, for example *The server could not be reached from this workstation.* > **Blocked from connecting to sftp.example.org:22 … Ask IT to allow outbound TCP 22 to sftp.example.org for AitriumOS (NewLeaf.exe).** > > **From AitriumOS 2.2.7.** The workstation, or security software on it, refused to let AitriumOS open the connection. Another program on the same computer may still be allowed. Site IT should allow outbound TCP to that host and port **for the AitriumOS program**, not only for the port. See [Allowing the connection](#for-site-it-allowing-the-connection). > **No response from sftp.example.org:22 within 20s (TCP connect) …** > > Nothing answered the connection within 20 seconds. The message continues: the host never answered, which usually means a firewall or network policy is blocking the outbound port. Check the site's outbound firewall first, then ask the trial organization whether their server only accepts approved IP addresses. > **No response from sftp.example.org:22 within 30s (SSH handshake) …** > > The connection opened, but the secure handshake and sign-in did not finish within 30 seconds. A device between the workstation and the server may be holding the connection open without passing SSH traffic, or the server may be very slow to respond. Site IT should check for proxies or inspection devices on the path. If there are none, contact the trial organization. > **Unable to connect to the SFTP server: the connection was refused or could not be made. Verify the host, port, and network access.** > > The connection could not be opened: the server refused it, or the network could not reach the server. Use **Settings → Network → Upload destinations → Check now** for a more specific result. > **The SFTP server's security settings aren't supported by this version of AitriumOS. Please update AitriumOS or contact Aitrium support.** > > **From AitriumOS 2.2.7.** The server answered, but it and AitriumOS have no SSH algorithms in common. The host, port and network are working. Update AitriumOS if an update is available, and contact [Aitrium support](mailto:support@aitriumos.com). The trial organization can check its server against [SFTP server compatibility](/security/aitrium-os/sftp-compatibility). > > Earlier versions show the generic message *Unable to connect to the SFTP server. Verify the host, port, and network access.* for this case. > **Authentication failed. Verify the configured username and credentials.** > > The server did not accept the account. Your site does not hold these credentials: the trial organization configures them, so ask them to check the account. The trial dashboard summarizes this as *The server did not accept the account.* After a rejected sign-in, AitriumOS does not retry automatically; select the transfer status to test again once the trial organization has fixed the account. > **Failed to fetch site integration credentials … / Transfer credentials are not available yet.** > > AitriumOS could not obtain the trial's transfer credentials, so no SFTP server was contacted. Usually your access to the trial or a required training has not been confirmed yet. Open the trial from [Trial Participation](https://app.aitriumos.com/dashboard/participation) in the Aitrium portal to check what is still outstanding, and confirm any training shown there. If access or setup is still pending, or the cause is unclear, contact the trial organization. > **OpenSSH format detected but ssh-keygen is not available for conversion.** > > **Windows, key-based sign-in only.** The trial uses a private key in OpenSSH format, which AitriumOS converts on Windows with the `ssh-keygen` tool from Windows' **OpenSSH Client** optional feature. Site IT can add **OpenSSH Client** under **Optional features** in Windows Settings, or the trial organization can supply the key in PEM format. > **PuTTY PPK format is not supported …** > > The trial's private key is in PuTTY's `.ppk` format. The trial organization must export it in OpenSSH format with PuTTYgen and update the credentials. > [!NOTE] > > During an upload, AitriumOS tries to connect up to three times, 2 and then 4 seconds apart, before the upload fails. The final message then ends with *(failed after 3 connection attempts)*. A rejected sign-in or unsupported security settings fail immediately, because retrying cannot change the result. ## For site IT: allowing the connection This section covers the SFTP upload only. For the rest of the workstation setup, including the HTTPS allowlist and proxy, see the [IT setup checklist](/aitrium-os/it-setup). If you operate the trial's SFTP server rather than the site's network, see [SFTP server compatibility](/security/aitrium-os/sftp-compatibility). * **Allow outbound TCP to the host and port** shown in **Upload destinations**. The connection goes directly from the workstation. It cannot go through a web (HTTP) proxy. * **Allow the program, not just the port.** Endpoint-security products and per-application firewall rules often block one program while allowing another. Allow the AitriumOS executable: * Windows, per-machine (MSI) install: `C:\Program Files\AitriumOS\NewLeaf.exe` * Windows, per-user (Standard) install: `%LOCALAPPDATA%\AitriumOS\NewLeaf.exe` * macOS: the **AitriumOS** application * **If the host name has several addresses,** such as an IPv6 and an IPv4 address, AitriumOS 2.2.7 tries each in turn within one time budget. A blocked IPv6 address therefore no longer stops an upload when the IPv4 address works. Allow every address you intend the workstation to use. * **Confirm with AitriumOS itself.** Run **Settings → Network → Upload destinations → Check now** on the workstation after each change. > [!WARNING] > > **Testing from another program does not prove AitriumOS can connect.** A successful `ssh`, `sftp` or `Test-NetConnection` from the same computer shows the port is open for *that* program. Security software can still block AitriumOS, or intercept the connection, on the same port. Use **Check now** to test the path AitriumOS actually uses. ### If the trial's server restricts IP addresses Some trial organizations only accept SFTP connections from IP addresses they have approved. The trial's server sees your site's **public egress IP address**: the address your network's traffic leaves from, often shared by many workstations. It does not see the workstation's internal address, and there is no Aitrium relay address to approve. Ask your network team for the public egress IP address, or addresses, used by the workstations running AitriumOS, and send them to the trial organization. A **No response** or **refused the connection** result that persists after your own firewall allows the connection usually means the address has not been approved yet. ## Getting help Contact [support@aitriumos.com](mailto:support@aitriumos.com) with: * The exact message, and the result of **Check now** * Your AitriumOS version, shown in the application header * What IT has already allowed, for example the program, the host and port, and whether the trial organization has approved your public IP address Do not send passwords, private keys or unredacted logs by email. # IT setup checklist Source: https://docs.aitriumos.com/aitrium-os/it-setup What a site's IT team needs to install, allow, and validate so clinical staff can submit trial data with AitriumOS. For: Site IT AitriumOS is the desktop application that clinical staff at your site use to prepare and submit patient data to clinical trials. Validation, standardization, and **de-identification** run on the workstation; the prepared dataset is then sent directly to the trial's destination. This page is the starting point for the IT team that installs and supports AitriumOS. Work through the steps below for each workstation, then confirm the result from inside the application. **1. Install AitriumOS** AitriumOS runs on Windows 10/11 (64-bit) and macOS. On Windows, choose between the **MSI** installer (per-machine, for IT-deployed fleets) and the **Standard** installer (per-user, no administrator rights). Install only one type per workstation. * IT facts — requirements, installer options, and how updates are delivered: [Deployment & updates](/security/aitrium-os/deployment) * User walkthrough with screenshots: [Installing AitriumOS](/aitrium-os/overview#installing-aitriumos) and [Switching Windows installer types](/aitrium-os/overview#switching-windows-installer-types) **2. Allow outbound HTTPS to Aitrium** Permit outbound HTTPS (TCP 443) to the destinations in the [firewall allowlist](/security/aitrium-os/data-flows#firewall-allowlist). The most important is `api.aitriumos.com`: without it, users can sign in but no trials load and no data can be submitted. **3. Configure your corporate proxy, if you use one** AitriumOS reaches its HTTPS services through a corporate HTTP proxy, including proxies that use Windows Integrated Authentication or Basic authentication. See [Corporate HTTP proxy](/security/aitrium-os/proxy-configuration). **4. Allow the direct SFTP upload** For trials that transfer data over SFTP, the upload goes directly from the workstation to the trial's server and **cannot go through a web proxy**. Allow the program `NewLeaf.exe`, not just the port, and send your site's public egress IP address to the trial organization if its server restricts addresses. See [For site IT: allowing the connection](/aitrium-os/connection-troubleshooting#for-site-it-allowing-the-connection). **5. Check endpoint protection** AitriumOS is code-signed and runs in the user's context. If your EDR or antivirus needs an exception, allow it by publisher, install path, or executable. See [Build integrity & validation](/security/aitrium-os/validation). **6. Validate from inside AitriumOS** Browser and command-line tests do not prove the application can connect. On the workstation, open **Settings → Network**: it lists each Aitrium service with its status, and **Upload destinations → Check now** tests each trial's SFTP server without signing in or sending data. For what each message means, see [Upload connection troubleshooting](/aitrium-os/connection-troubleshooting). ## Related > **[Security review](/security/aitrium-os/overview)** > > Architecture, data flows and residency, and access management for your Information Security team. > **[Getting started (for users)](/aitrium-os/overview)** > > The page clinical staff follow to install AitriumOS and sign in. > [!NOTE] > > Operate the SFTP server that receives a trial's data? That is the trial organization's IT team: see [SFTP server compatibility](/security/aitrium-os/sftp-compatibility). For help, contact [support@aitriumos.com](mailto:support@aitriumos.com). # EORTC Data Submission Source: https://docs.aitriumos.com/aitrium-os/no-protocol-submissions Step-by-step guide for submitting clinical trial data using the EORTC submission workflow in AitriumOS. For: Site users ## Overview > [!NOTE] > > **This guide is for EORTC trials.** For all other trials, follow [RTQA Data Submission](/aitrium-os/protocol-submissions) instead. This guide walks through submitting clinical trial data with AitriumOS for EORTC trials, which use a per-patient dataset checklist. The submission process ensures your data meets all trial requirements while maintaining patient privacy through standardization and de-identification. ## Step-by-Step Walkthrough [https://supercut.video/embed/aitrium/K8ppUTUdCx8K6rN6sc62GN?embed=full](https://supercut.video/embed/aitrium/K8ppUTUdCx8K6rN6sc62GN?embed=full) ## Adding a Patient Before you can submit data for a patient, the patient must be added to the trial: 1. Open the trial in AitriumOS and select **Add Patient**. 2. Enter the patient's **Trial Patient ID** exactly as assigned by the trial. 3. The patient appears in the **Submit a Patient Dataset** table, ready for submission. > [!WARNING] > > The Trial Patient ID is the de-identified ID the trial team uses to track this patient — double-check it before saving. Never enter a medical record number or other identifying value. ## Submission Process The clinical trial data submission protocol consists of five key steps: ### 1. Trial Dataset Validation The first step validates your patient dataset against a clinical trial's specific dataset file requirements: * Verifies presence of required patient data files * Identifies missing or invalid data elements * Validates DICOM headers against a trial's requirements * Provides detailed feedback for any validation issues ### 2. Structure Standardization For trials requiring RT Structure Set file submission, this step: * Labels organ and target volumes according to the trial specific nomenclature * Maps local naming conventions to the trial specific nomenclature * Ensures adherence to trial-specific structure requirements ### 3. DICOM Metadata Validation & De-identification This critical step protects patient privacy by: * Analyzing all DICOM headers for potentially identifying information. * Applying the clinical trial's de-identification policy to the DICOM file metadata. This step will run automatically and only require action if there is a failure. > [!CAUTION] > > **Aitrium currently does not remove burned-in pixels from DICOM image data or de-identify non-DICOM files. Please ensure images and other supplementary files are anonymized prior to submission.** ### 4. Final Review Before submission, the user can: * Review dataset completeness. * Approve data for submission. ### 5. Upload to Trial The final step packages the approved dataset as a zip file named according to the clinical trial requirements, then completes the submission in two parts: 1. **Data Transfer** — the dataset is uploaded to the trial's data destination, with a progress bar tracking the transfer. 2. **Aitrium Sync** — the submission is registered with Aitrium, which records it for the trial and notifies the trial team. Both parts run automatically, and the transfer progress card shows which one is underway. When both finish, AitriumOS shows the **Submission complete** screen. ![Upload progress bar mid-transfer in AitriumOS](https://mintcdn.com/aitrium/G4cxhD6ZKGPc1CDc/images/trial_submissions/upload-in-progress.png?fit=max\&auto=format\&n=G4cxhD6ZKGPc1CDc\&q=85\&s=baa96ce8ea07904cc0edbaca14d9e5c3) *While the upload is in progress, keep AitriumOS open.* ![Submission complete screen shown after the submission finishes](https://mintcdn.com/aitrium/G4cxhD6ZKGPc1CDc/images/trial_submissions/upload-complete-confirmation.png?fit=max\&auto=format\&n=G4cxhD6ZKGPc1CDc\&q=85\&s=a2c211345b7c3c55ec47847287ea4578) *The Submission complete screen. A progress bar at 100% is not this screen — the submission is still finishing.* > [!WARNING] > > **Keep AitriumOS open until the Submission complete screen appears, then verify the submission.** Closing the application while the upload is finishing can leave a submission unregistered — the trial team receives the files but gets no notification, and the dataset will not appear as submitted. After every upload, confirm the dataset shows as submitted on the trial page (see [Monitoring Submission Status](#monitoring-submission-status)). If it doesn't, see [Troubleshooting](#troubleshooting-common-issues). ## Monitoring Submission Status Verifying the submission is the final step of every upload — don't skip it: 1. Navigate to the trial homepage in AitriumOS. 2. Find the patient in the **Submit a Patient Dataset** table and confirm the submission registered: the patient's **Last Sent** time reflects your upload, and the dataset's status no longer shows **Submit Dataset**. ![Submit a Patient Dataset table showing a just-submitted patient with an updated Last Sent time and a Complete status](https://mintcdn.com/aitrium/G4cxhD6ZKGPc1CDc/images/trial_submissions/dataset-table-submitted.png?fit=max\&auto=format\&n=G4cxhD6ZKGPc1CDc\&q=85\&s=4cf178073aa3c87af5084a1e5753e382) If the **Last Sent** time has not updated after you saw the **Submission complete** screen, the submission did not finish registering — see [Troubleshooting](#troubleshooting-common-issues). ## Resubmitting a Dataset A submission may need to be repeated — for example, when a dataset was incomplete, an upload failed partway through, or the trial team requests a corrected dataset. 1. Navigate to the trial homepage in AitriumOS and locate the patient in the **Submit a Patient Dataset** table. 2. The dataset's action button reflects what is needed: * **Complete Required Items** — the dataset is missing required items; provide them to finish the original submission. * **Resubmit Dataset** — the dataset should be submitted again; selecting it restarts the submission flow for that patient. 3. Prepare the corrected dataset and proceed through the same validation, standardization, de-identification, and review steps as the original submission. > [!NOTE] > > **Do not add the patient again.** Resubmit from the patient's existing row — never re-enter the Trial Patient ID as a new patient. The resubmission becomes the active dataset the trial team reviews; earlier submissions stay recorded for traceability but are no longer the dataset under review. ## Best Practices > **Prepare Your Data** > > * Ensure that all supplementary non-DICOM files have been pseudonymized. > * Ensure that DICOM images do not have burned-in pixels with personally-identifiable information. > * Ensure all trial required DICOM data is available for submission > **Review Validation Results** > > * Review the completeness status and address data omissions or errors before proceeding. ## Troubleshooting Common Issues ### Validation Failures If dataset validation fails: * Check the Analysis Result's Data Errors tab. The DICOM data provided may be corrupted. * Check that all trial specific required DICOM data and series are present in the selected folder for upload ### Structure Standardization Issues For RT structure problems: * Confirm RTSTRUCT files are properly linked to image series * Check that structure names can be mapped to trial standards * Review the standardization mapping table ### Upload Errors If uploads fail: * Verify your internet connection stability * Confirm your institution's firewall permits the outbound transfer connection — see [Before You Begin](/aitrium-os/overview#before-you-begin) * Check available disk space * Ensure you have proper trial permissions * Contact support if issues persist ### Upload finished but the dataset doesn't show as submitted If the upload completed but the patient's row on the trial page doesn't reflect it — the **Last Sent** time has not updated, or the dataset still shows **Submit Dataset** — the application was most likely closed before the submission finished registering. The trial team received the files, but no notification was sent and the submission was not recorded. To resolve: * Run the submission again for that patient from the **Submit a Patient Dataset** table, exactly as you did the first time. The trial team can disregard the duplicate file. * If the dataset still does not show as submitted, contact [support@aitriumos.com](mailto:support@aitriumos.com) with your trial ID and patient ID. Verifying every submission on the trial page right after uploading (see [Monitoring Submission Status](#monitoring-submission-status)) catches this immediately instead of weeks later. ## Need Help? If you encounter any issues during the submission process: * Review the error messages carefully * Consult the trial-specific requirements documentation * Contact support at [support@aitriumos.com](mailto:support@aitriumos.com) # Getting started Source: https://docs.aitriumos.com/aitrium-os/overview Overview and installation guide for AitriumOS For: Site users (with a checklist to forward to Site IT) ## Overview Welcome to Aitrium. We developed AitriumOS to streamline trial participation for contributors by making it easier to standardize, validate, and upload data to investigators. This document is intended to guide first-time users of AitriumOS through the initial set-up and installation. ### The Two Parts of Aitrium You'll use Aitrium in two places, with one sign-in for both: * **Aitrium Web** ([app.aitriumos.com](https://app.aitriumos.com)) — sign in from any browser to download AitriumOS, view your submissions, and manage users. * **AitriumOS desktop app** — installed on your workstation; where you prepare and submit patient datasets. All submission work happens here. ### Before You Begin There are two quick checks before installing AitriumOS — one you can do yourself, and one for your site's IT team. **1. Check that you can sign in** * You should have received an Aitrium account invitation for your site. If you have not, contact your trial coordinator. * Verify you can sign in at [https://app.aitriumos.com](https://app.aitriumos.com). The desktop application uses this same sign-in. **2. Forward the requirements below to your IT team** Most hospital networks restrict which applications can be installed and which network connections are allowed. You do not need to understand or check these items yourself — send this page to your IT team and ask them to confirm each item for the computer you will use. The full IT guide is the [IT setup checklist](/aitrium-os/it-setup). > [!NOTE] > > **For IT staff — requirements for AitriumOS (clinical trial data submission application):** > > * **Installation** — AitriumOS is a desktop application for Windows 10/11 (64-bit; 32-bit available for older releases) or macOS (Apple Silicon or Intel). The user needs it installed on their workstation. > * **Disk space** — during a submission, the application creates a temporary de-identified working copy of the patient imaging dataset, so the workstation needs transient free space roughly equal to the dataset being submitted. Working copies are deleted automatically when the submission completes or is cancelled (leftovers from interrupted sessions are removed the next time the application starts), so storage utilization does not accumulate over time. > * **Web access** — outbound HTTPS (port 443) from the workstation to `app.aitriumos.com` and Aitrium service endpoints. > * **Data upload** — for trials that transfer data over SFTP, outbound SFTP/SSH (TCP, usually port 22) from the workstation directly to the trial's SFTP server. This connection **cannot go through a web (HTTP) proxy**, so outbound firewall rules must permit it. Allow the **program** `NewLeaf.exe` (`C:\Program Files\AitriumOS\` for the MSI installer, `%LOCALAPPDATA%\AitriumOS\` for the standard installer), not just the port. The host and port are listed in AitriumOS under **Settings → Network → Upload destinations**. > * **Trial SFTP servers that restrict IP addresses** — the trial's server sees the site's **public egress IP address**. If the trial organization only accepts approved addresses, send them that address. > > Details: [IT setup checklist](/aitrium-os/it-setup) and [Upload connection troubleshooting](/aitrium-os/connection-troubleshooting). #### How you'll know: "Can't reach Aitrium" You do not need to test the network requirements yourself — AitriumOS checks its own connection every time it runs. **If you can sign in and don't see either of the warnings below, the workstation's network is configured correctly and no IT involvement is needed.** If the network does block Aitrium, the application tells you in two places: * **Right after sign-in** — a full-screen message: ![Can't reach Aitrium screen shown after sign-in, with a link to the network configuration guide and a Try again button](https://mintcdn.com/aitrium/G4cxhD6ZKGPc1CDc/images/networking/cant-reach-aitrium-signin.png?fit=max\&auto=format\&n=G4cxhD6ZKGPc1CDc\&q=85\&s=757d5f5b8d7a82f5de8ae25bcc8fb35f) * **While signed in** — a red **Connection issue** indicator in the header; select it for details: ![Connection issue indicator in the AitriumOS header with the Can't reach Aitrium details panel open](https://mintcdn.com/aitrium/G4cxhD6ZKGPc1CDc/images/networking/connection-issue-header.png?fit=max\&auto=format\&n=G4cxhD6ZKGPc1CDc\&q=85\&s=4924c35b80c6f95a797eac316aa2b0a7) Both mean the same thing: the workstation cannot connect to Aitrium's servers (the **Web access** requirement above), so trials and submissions won't work until the connection is restored. **Your account and data are fine** — this is a network or firewall setting on the workstation, not a problem with Aitrium or your sign-in. Local tools remain available in the meantime. To resolve it: 1. Use the in-app link to send the **network configuration guide** to your IT team — it lists exactly which addresses to allow (the same information as the [firewall allowlist](/security/aitrium-os/data-flows#firewall-allowlist)). If your site routes traffic through a corporate proxy, IT should also see [Corporate HTTP proxy](/security/aitrium-os/proxy-configuration). 2. Once IT has made the change, select **Try again**. 3. If the message persists after IT's change, contact [support@aitriumos.com](mailto:support@aitriumos.com). > [!NOTE] > > Sign in on the workstation well before your first submission is due — not the day data is due — so any network change has time to be made. The **Data upload** (SFTP) connection is separate from this check. To test it, open **Settings → Network → Upload destinations** and select **Check now** next to your trial's server: a check confirms the server can be reached without signing in or sending data. If it doesn't show **Reachable**, see [Upload connection troubleshooting](/aitrium-os/connection-troubleshooting) for what the message means and who needs to act. ### Installing AitriumOS [https://supercut.video/embed/aitrium/vMhNRfTBePqFIAStExvsyT?embed=full](https://supercut.video/embed/aitrium/vMhNRfTBePqFIAStExvsyT?embed=full) 1. **Log in to Aitrium**: Access your account at [https://app.aitriumos.com](https://app.aitriumos.com) using your provided username and password. 2. **Download the Application**: * Navigate to 'Downloads' on the lefthand navigation bar — open the page **on the computer you want to install AitriumOS on**, and it will recommend the right download for that computer * For **Windows**, there are two installers that do the same thing but install differently: * **Standard installer** — installs for your account only and does **not** need administrator rights. This is the right choice for almost everyone installing on their own workstation. * **MSI installer** — installs machine-wide for all accounts and **requires administrator rights**. Only choose this if your IT department deploys software this way (they will usually know). * For **Mac**: select based on your CPU (Apple Silicon or Intel) * Check by clicking the Apple icon -> About This Mac > [!WARNING] > > **Install only one Windows installer type.** The two types don't detect each other, so installing both puts two separate copies of AitriumOS on the computer — two identical icons that can run different versions, which is very confusing. If you're not sure whether AitriumOS is already installed, check **Windows Settings → Installed apps** first: if an AitriumOS entry is already there, update or uninstall that copy instead of installing a second one. The Downloads page will also warn you if you're about to download a different type than you used before. 3. **Install the Application**: Follow your operating system's standard installation process. #### Switching Windows installer types If you want to move from one Windows installer type to the other — for example, switching to the Standard installer so future updates never need an administrator — switch cleanly rather than installing the second type alongside the first: 1. **Check what is installed now**: open **Windows Settings → Installed apps** and search for AitriumOS. If more than one AitriumOS entry is listed, you already have duplicate copies — remove all of them in the steps below, then install fresh. 2. **Uninstall the existing copy**: * An **MSI copy** was installed machine-wide, so removing it **requires administrator rights one last time** — if you don't have them, ask IT to uninstall it. After that, the Standard installer installs and updates without ever needing an administrator again. * A **Standard copy** uninstalls without administrator rights. 3. **Install the new type**: return to the Downloads page and download the type you want. (The page will show a warning because your previous downloads were the other type — that warning exists to prevent *accidental* switches; when you're switching on purpose, continue.) 4. **Your data is safe either way**: submitted trial data lives in Aitrium, not on the workstation, and your local sign-in and settings are kept through an uninstall/reinstall. ### Using AitriumOS [https://supercut.video/embed/aitrium/44Ne6pBxkRxHuSnYoQFoW7?embed=full](https://supercut.video/embed/aitrium/44Ne6pBxkRxHuSnYoQFoW7?embed=full) After installation, launch AitriumOS and log in with your username and password. If you see a **"Can't reach Aitrium"** message instead of your trials, the workstation's network is blocking the connection — see [the section above](#how-you’ll-know-“can’t-reach-aitrium”). ### App Updates If an update is available for AitriumOS, you will see the version button in the header turn blue: ![](https://mintcdn.com/aitrium/qAL7O0ERlC__-H2b/images/update-new-version.png?fit=max\&auto=format\&n=qAL7O0ERlC__-H2b\&q=85\&s=4c21f0b853203780ae8c922d138befe7) To install the update: * Click "Update Now" to start downloading the version * Once the download succeeds, the application will automatically close to apply the update * After the update completes, the application will re-open. ## Need Help? If you run into problems during set-up: * Contact support at [support@aitriumos.com](mailto:support@aitriumos.com) * Include your operating system version and, for connection issues, the error message shown in the app # RTQA Data Submission Source: https://docs.aitriumos.com/aitrium-os/protocol-submissions Step-by-step guide for submitting patient data using the RTQA submission workflow in AitriumOS, including regimen setup, the trial data submission schedule, and QA evaluation. For: Site users ## Overview > [!NOTE] > > **Submitting to an EORTC trial?** Follow [EORTC Data Submission](/aitrium-os/no-protocol-submissions) instead. This guide covers all other trials. RTQA trials arrive in AitriumOS pre-configured with study arms, regimens, data collection schedules, and QA policies. The submission process is guided — each patient's required data submissions are scheduled automatically based on the trial's configuration. This guide covers the complete workflow: configuring a patient's treatment regimen, reviewing the trial data submission schedule, and submitting data through the five-step submission flow. ## Step-by-Step Walkthrough [https://supercut.ai/embed/aitrium/Cqc4SUbRKvKIYYKbayulnc?embed=full](https://supercut.ai/embed/aitrium/Cqc4SUbRKvKIYYKbayulnc?embed=full) ## Add Patient Regimen Before submitting data, each patient must be configured with their treatment details. Open the **Patient Configuration** modal from the trial's patient list. ### Setup Checklist The modal presents three required fields: 1. **Randomization Date** — When the patient was enrolled in the trial 2. **Study Arm** — Which treatment arm the patient is assigned to 3. **Patient Regimens** — One or more treatment regimens with start dates > [!NOTE] > > Status indicators show configuration progress: green = complete, amber = required field missing, lock icon = managed by trial manager (read-only). [https://supercut.ai/embed/aitrium/ehp-ci8c9NevC6EOyx98dd?embed=full](https://supercut.ai/embed/aitrium/ehp-ci8c9NevC6EOyx98dd?embed=full) ### Adding a Regimen 1. Select a **Study Arm** from the dropdown — this filters the available regimens 2. Choose a regimen from the searchable dropdown, which displays: * Regimen name * Number of fractions * Dose range (min–max Gy or single target dose) 3. Enter a **Treatment Start Date** (required), and optionally a Treatment End Date 4. To add multiple regimens, queue them and click **Save N Regimens** to save in batch > [!NOTE] > > Regimens already assigned to the patient are disabled in the dropdown to prevent duplicates. After saving, the system automatically schedules the patient's data submissions based on the trial's data collection events, anchored to the patient's dates (randomization, regimen start, etc.). ## Submit Scheduled Datasets The **Patient Submission Queue** in the **Trial Data Submission Schedule** displays all pending data submissions for the trial: * **Site-level submissions** appear at the top of the queue * **Patient-level submissions** are grouped by patient below Each row shows: * **Status badge** — OVERDUE, SCHEDULED, or COMPLETED * **Due date** — When the data is expected * **Event name** — The data collection event (e.g., "Baseline CT", "Fraction 1") * **Associated datasets** — What data types are required ![Trial patient submission schedules](https://mintcdn.com/aitrium/XixA6cHGss3Xencl/images/trial_submissions/patient_schedules.png?fit=max\&auto=format\&n=XixA6cHGss3Xencl\&q=85\&s=83c02c9d57c70dec16f68f24e5713061) To begin a submission, click **Submit** on the desired row in the queue. This opens the guided submission flow. ## Submission Flow The submission flow consists of five sequential steps. Each step must complete successfully before proceeding to the next. ### 1. Dataset Analysis Select the local directory containing the patient's DICOM data. The **Dataset Analyzer** scans the directory and produces: * **DICOM file inventory** — Patient, Study, and Series structure * **Modality breakdown** — CT, MR, RTSTRUCT, RTPLAN, RTDOSE, and other modalities detected * **Protocol validation** — Checks data against the trial's specific requirements * **Missing data warnings** — Color-coded indicators for gaps: * Red: required data missing * Amber: optional data missing Review the analysis results and address any data gaps before proceeding. ![Trial patient submission schedules](https://mintcdn.com/aitrium/XixA6cHGss3Xencl/images/trial_submissions/dataset_analyzer_results.png?fit=max\&auto=format\&n=XixA6cHGss3Xencl\&q=85\&s=f203268354113cc34d9ad70abf0c7571) ### 2. RT Structure Standardization > [!NOTE] > > This step runs automatically when RTSTRUCT files are present in the dataset. If no RT structures exist, this step is skipped. The standardizer maps your local structure names to TG-263 standard nomenclature and the trial's specific structure requirements. Review the mapping table: * **Left column** — Your original structure names * **Right column** — Standardized / trial-required names (editable via searchable dropdown) Protocol-required structures are highlighted to ensure all necessary mappings are confirmed before proceeding. ![Trial patient submission schedules](https://mintcdn.com/aitrium/XixA6cHGss3Xencl/images/trial_submissions/map_target_structures.png?fit=max\&auto=format\&n=XixA6cHGss3Xencl\&q=85\&s=7f3a165c01d4708ddea064096d731aad) ![Trial patient submission schedules](https://mintcdn.com/aitrium/XixA6cHGss3Xencl/images/trial_submissions/map_oar_structures.png?fit=max\&auto=format\&n=XixA6cHGss3Xencl\&q=85\&s=d58a8ec30b443d1c02ff9d28a36554a9) ### 3. DICOM Metadata De-identification This step protects patient privacy by removing or replacing personally identifiable information (PII) from DICOM metadata according to the trial's assigned de-identification policy. The process has three sub-phases: 1. **Pre-anonymization validation** — Checks whether the data already meets the trial's de-identification policy requirements 2. **De-identification** — Removes or replaces PII fields (patient name, patient ID, dates, and other identifying metadata) per the trial's policy. A progress bar tracks the operation. 3. **Post-anonymization validation** — Confirms the anonymized files meet all policy requirements before proceeding > [!WARNING] > > If errors occur during de-identification (e.g., corrupt files, insufficient disk space), the system provides specific guidance and a retry option. You can also select a new source directory to start over. ### 4. QA Policy Evaluation > [!NOTE] > > This step only appears if the protocol has a QA policy assigned. If no QA policy is configured, the flow proceeds directly to Data Transfer. QA policy evaluation assesses the dosimetric and structural quality of the submitted dataset: 1. **Extract QA Facts** — The system identifies the best RT study pair (RTSTRUCT + RTDOSE), computes DVH metrics, and evaluates them against the protocol's policy constraints. A progress bar is shown with status updates. 2. **Review QA Metrics** — A table displays the extracted metrics (e.g., D95, D5, Dmean, Dmax, Dmin, V100%) with color-coded results: * **Green** — Within acceptable range (Per Protocol) * **Amber** — Acceptable variation * **Red** — Unacceptable deviation 3. Click **Continue** ![Trial patient submission schedules](https://mintcdn.com/aitrium/XixA6cHGss3Xencl/images/trial_submissions/qa_metrics_review.png?fit=max\&auto=format\&n=XixA6cHGss3Xencl\&q=85\&s=402f2a89a956d8f0210ccd882f25fdc2) ### 5. Data Transfer The final step uploads the processed dataset to the trial's configured destination. 1. **Pre-submission review** — Verify the summary of what will be submitted: * Patient ID and Site ID * Number of DICOM series grouped by modality * Integration destination * Anonymization status confirmation * QA status confirmation (if applicable) 2. **Upload** — The upload runs in two parts, shown on the transfer progress card: **Data Transfer** uploads the files to the trial's configured destination with real-time progress tracking, then **Aitrium Sync** registers the submission with Aitrium — recording it for the trial and notifying the trial team 3. **Success** — The **Submission complete** screen displays transfer details and provides the option to submit another patient dataset ![Upload progress bar mid-transfer in AitriumOS](https://mintcdn.com/aitrium/G4cxhD6ZKGPc1CDc/images/trial_submissions/upload-in-progress.png?fit=max\&auto=format\&n=G4cxhD6ZKGPc1CDc\&q=85\&s=baa96ce8ea07904cc0edbaca14d9e5c3) *While the upload is in progress, keep AitriumOS open.* ![Submission complete screen shown after the submission finishes](https://mintcdn.com/aitrium/G4cxhD6ZKGPc1CDc/images/trial_submissions/upload-complete-confirmation.png?fit=max\&auto=format\&n=G4cxhD6ZKGPc1CDc\&q=85\&s=a2c211345b7c3c55ec47847287ea4578) *The Submission complete screen. A progress bar at 100% is not this screen — the submission is still finishing.* > [!WARNING] > > **Keep AitriumOS open until the Submission complete screen appears, then verify the submission.** Closing the application while the upload is finishing can leave a submission unregistered — the trial team receives the files but gets no notification, and the event will not move to **Completed**. After every upload, confirm the event shows **Completed** in the Patient Submission Queue (see [Monitoring Submission Status](#monitoring-submission-status)). If it doesn't, see [Troubleshooting](#troubleshooting-common-issues). ## Monitoring Submission Status Verifying the submission is the final step of every upload — don't skip it: 1. Navigate to the trial in AitriumOS 2. Find the patient's event in the **Patient Submission Queue** and confirm its status shows **Completed** ![Patient Submission Queue showing the just-submitted event as Completed](https://mintcdn.com/aitrium/G4cxhD6ZKGPc1CDc/images/trial_submissions/submission-queue-completed.png?fit=max\&auto=format\&n=G4cxhD6ZKGPc1CDc\&q=85\&s=b9b4de397208223796f86748f13a0dce) If the event has not moved to **Completed** after you saw the **Submission complete** screen, the submission did not finish registering — see [Troubleshooting](#troubleshooting-common-issues). The queue provides real-time status per patient and event. Submission statuses progress through: * **Pending Dates** — Waiting for anchor dates (e.g., randomization date not yet set) * **Scheduled** — Dates calculated, awaiting data submission * **In Progress** — Submission started * **Completed** — Data successfully submitted * **Overdue** — Past the collection window end date ## Resubmitting a Dataset A submission may need to be repeated — for example, when a dataset was incomplete, an upload failed partway through, or the trial team requests a corrected dataset. 1. Navigate to the trial in AitriumOS and locate the patient's event in the **Patient Submission Queue**. 2. The submission's action button reflects what is needed: * **Complete Required Items** — the dataset is missing required items; provide them to finish the original submission. * **Re-submit** — the dataset should be submitted again; selecting it restarts the submission flow for that event. 3. Prepare the corrected dataset and proceed through the same analysis, standardization, de-identification, QA evaluation, and transfer steps as the original submission. A resubmission will transfer a new dataset to the recipient for that patient event; earlier submissions remain recorded for traceability. ## Best Practices > **Prepare Your Data** > > * Ensure all trial-required DICOM data is available in a single directory for submission > * Verify that supplementary non-DICOM files have been pseudonymized > * Confirm that DICOM images do not contain burned-in pixels with personally identifiable information > **Configure Patients Early** > > * Set randomization dates and regimen start dates promptly after enrollment > * This ensures scheduled submissions are generated with correct due dates > * Review the Patient Submission Queue to confirm expected events appear > **Review QA Results Carefully** > > * Address any unacceptable deviations (red indicators) before acknowledging > * Contact the trial coordinator if you are unsure whether a variation is acceptable > * Use manual entry to supplement metrics the system could not extract automatically ## Troubleshooting Common Issues ### Dataset Analysis Failures If dataset analysis fails: * Check the Data Errors tab for details — the DICOM data may be corrupted * Verify all trial-required DICOM data and series are present in the selected directory * Ensure the directory is accessible and not locked by another application ### RT Structure Standardization Issues For RT structure mapping problems: * Confirm RTSTRUCT files are properly linked to their image series * Check that structure names can be mapped to the trial's required nomenclature * Use the searchable dropdown to manually assign mappings for unrecognized names ### De-identification Errors If de-identification fails: * Check available disk space — the process creates anonymized copies of all files * Verify file permissions on the source directory * Use the **Retry** button to attempt again, or **Select New Directory** to start over ### QA Metric Extraction Issues If QA facts cannot be extracted: * Verify that both RTSTRUCT and RTDOSE files are present and properly linked * Check that structure names have been correctly standardized in the previous step * Use manual entry to provide metrics that could not be computed automatically ### Upload Errors If data transfer fails: * Verify your internet connection stability * Confirm your institution's firewall permits the outbound transfer connection — see [Before You Begin](/aitrium-os/overview#before-you-begin) * Check that the trial's integration is properly configured (contact your trial administrator) * Ensure you have proper trial upload permissions * Contact support if issues persist ### Upload finished but the event doesn't show as Completed If the upload completed but the patient's event still has not moved to **Completed** in the Patient Submission Queue, the application was most likely closed before the submission finished registering. The trial team received the files, but no notification was sent and the submission was not recorded. To resolve: * Run the submission again for that event from the **Patient Submission Queue**, exactly as you did the first time. The trial team can disregard the duplicate file. * If the event still does not show as **Completed**, contact [support@aitriumos.com](mailto:support@aitriumos.com) with your trial ID and patient ID. Verifying every submission in the queue right after uploading (see [Monitoring Submission Status](#monitoring-submission-status)) catches this immediately instead of weeks later. ## Need Help? If you encounter any issues during the submission process: * Review the error messages carefully for specific guidance * Consult the trial-specific requirements documentation * Contact support at [support@aitriumos.com](mailto:support@aitriumos.com) # Get Nomenclature Standard Labels Source: https://docs.aitriumos.com/api-reference/rt-structures/get-nomenclature-standard-labels /openapi.yaml get /structures/standard-labels/{nomenclature_id} Retrieves the list of standard labels for a given nomenclature ID. Requires a valid Bearer token. Access might be restricted based on client's organization or if the ID corresponds to the public template. # Standardize RT Structure Names Source: https://docs.aitriumos.com/api-reference/rt-structures/standardize-rt-structure-names /openapi.yaml post /structures/standardize Standardizes a list of Radiation Therapy structure names using Aitrium's RT Plan Standardizer. # Get Trial Details Source: https://docs.aitriumos.com/api-reference/trials/get-trial-details /openapi.yaml get /trials/{trial_id} Retrieve details for a specific trial. Requires a valid Bearer token. # Get Trials Source: https://docs.aitriumos.com/api-reference/trials/get-trials /openapi.yaml get /trials/ Retrieve a list of trials associated with your organization. Requires a valid Bearer token. # Welcome to Aitrium Source: https://docs.aitriumos.com/introduction Find the documentation for your role, and learn how to get access to Aitrium. For: Everyone — choose your role below ## I am a… > **[Site user](/aitrium-os/overview)** > > I submit patient data to a trial from my hospital or clinic using AitriumOS. > **[Site IT](/aitrium-os/it-setup)** > > I install and support AitriumOS and manage my site's network and security software. > **[Trial organization admin](/trial-accelerator/overview)** > > I set up trials, sites, users, and data transfer in Aitrium Web. > **[Trial organization IT](/security/aitrium-os/sftp-compatibility)** > > I operate the SFTP server that receives a trial's data from participating sites. Reviewing Aitrium for security or compliance? Start with [Trust & Security](/security/overview). Managing users at a site organization? See [Organization administration](/aitrium-admin/overview). ## Introduction Aitrium makes it simple for physician scientists around the world to share standardized data with research partners. For research organizations sourcing data, Aitrium offers a web application that allows you to: * Create and manage Trials * Set de-identification and dataset requirement policies * Configure a data transfer integration * View dataset contributions * Manage participation For organizations contributing data to research projects, Aitrium offers AitriumOS for Windows and Mac that supports the de-identification, standardization, and transfer of medical imagery datasets (DICOM) and supplementary files to Trials. ## Setup Your Account ### Access and Requirements > **Request an Invite** > > Aitrium is currently invite-only. In order to set up your account, reach > out to \[[contact@aitriumos.com](mailto:contact@aitriumos.com)]\(mailto:[contact@aitriumos.com](mailto:contact@aitriumos.com)) for > access. > **Sign Up for Aitrium** > > Once you've received an invite and have created your Aitrium account, you > can log in to our Aitrium Dashboard. This is where you'll be able to create > and manage Trials, set data policies, and configure how data flows into > your Trials. ### Contribute Data > **AitriumOS (Windows & Mac)** > > If you're contributing data to a research project, download and install > AitriumOS. You can use it to de-identify, standardize, > and securely transfer your DICOM images (and other supplementary files) to > any active Trials you're participating in. # Access Management Source: https://docs.aitriumos.com/security/aitrium-os/access-management Organization roles, trial-level permissioning, and authentication. For: Security and compliance reviewers Access is governed by the Aitrium platform and is **self-service within your organization** — you do not depend on Aitrium to add or remove your own users (Aitrium assists only with initial organization setup and your first administrator). For step-by-step administration, see [User Management](/aitrium-admin/user-management). ## Organization roles | Role | Scope | | - | - | | **Admin** | Organization-wide access, including administration: inviting and managing users, managing Sites, and granting users access to authorized trials. | | **User** | Operational access limited to an **assigned Site** (and to the trials that user is authorized for — see below). | An **Admin** invites users by email. Invitations are valid for a limited period and move from **Pending** to **Accepted** or **Expired**; Admins can resend or revoke invitations and reassign a user's role or Site. A **User invitation requires a Site assignment** — that user can only access data and workflows for their assigned Site. > [!NOTE] > > The credentials used to transfer data to an investigator are configured by the investigator/sponsor organization, not by your Site's Admin. See [Transfer credentials](/security/aitrium-os/data-flows#transfer-credentials). ## Trial-level permissioning Access to a trial is scoped, not global. A user only ever sees the trials they are explicitly authorized for: **1. User → Site** A user is associated with one or more Sites in your organization (set at invitation). **2. Site → Trial** The investigator determines which Sites participate in a given trial. A Site that is not participating in a trial is invisible to that Site's users. **3. User → Trial** For a participating Site, a user is granted access to the specific trial, with fine-grained rights — for example, **viewing** a trial versus **transferring/submitting data** to it. In the application, AitriumOS only ever displays the trials, policies, and actions the signed-in user is authorized for. Authorization is **enforced on the server for every request** — the application cannot surface or act on anything the user has not been granted. ## Authentication Users sign in individually through Aitrium's managed identity service. The application presents the signed-in user's token on every request, and the server authorizes access according to the rules above. # Architecture Source: https://docs.aitriumos.com/security/aitrium-os/architecture The local and cloud components of AitriumOS, and how they fit together. For: Security and compliance reviewers AitriumOS is a native desktop application. The user interface runs in the operating system's WebView; the application core runs as a compiled native process. It is an outbound client — there is no customer-hosted server, database, or inbound network service. ## On the workstation * A single native desktop application ("AitriumOS"). * A user-interface layer rendered in the Microsoft Edge **WebView2** runtime (included with Windows 11). * A small local database and working folders in the per-user application-data directory, holding application state and in-progress dataset processing — not a copy of your imaging archive. * Bundled helper components for imaging tasks (e.g., DICOM de-identification and dose-volume-histogram computation) that run as ordinary, user-level processes and require no special privileges. ## In Aitrium's cloud (managed by Aitrium) You install nothing server-side. The cloud platform comprises: * An authenticated API the application calls for trial definitions, policies, and dataset-completeness records. * A managed database and object storage (platform data and application-update artifacts). * A managed identity service for sign-in. > [!NOTE] > > There is no customer-hosted database, no inbound network service, and nothing to operate on your side beyond the desktop application itself. ## System diagram [View on Eraser\ ![](https://app.eraser.io/workspace/sBxvYQgwaUKl1rtLxLY0/preview?figure=LK1SRZoqtHYv5bX9im85S\&type=embed)](https://app.eraser.io/workspace/sBxvYQgwaUKl1rtLxLY0?figure=LK1SRZoqtHYv5bX9im85S) ```mermaid theme={null} flowchart TB subgraph CLOUD["Aitrium Cloud — managed by Aitrium"] API["Aitrium API"] DB[("Managed database")] IDP["Identity service"] STORE[("Object storage
(updates, platform data)")] API <--> DB API <--> IDP API <--> STORE end subgraph WS["Site workstation — inside your network"] subgraph OS["AitriumOS desktop application"] UI["WebView2 user interface"] CORE["Native application core"] HELP["De-identification & QA helpers
(user-level processes)"] LOCAL[("Local store
app state & operation logs")] CORE --- UI CORE --- HELP CORE --- LOCAL end end INV[["Investigator destination
SFTP / FTP"]] OS -- "HTTPS 443 (outbound)" --> API OS -- "Prepared dataset — direct, not via Aitrium" --> INV ``` > **[Interactive version](https://app.eraser.io/workspace/sBxvYQgwaUKl1rtLxLY0?origin=share)** > > Open the full, interactive system architecture diagram. # Data Flows & Residency Source: https://docs.aitriumos.com/security/aitrium-os/data-flows Network destinations, ports, firewall allowlist, where patient data lives, and how transfer credentials are handled. For: Security and compliance reviewers · Site IT (firewall allowlist) All communication between AitriumOS and Aitrium/Google cloud services is **HTTPS/TLS over port 443**, always initiated outbound by the application. The only non-443 traffic is the transfer of the prepared dataset to the investigator's endpoint (typically SFTP over TCP 22), whose destination is defined by the investigator — not by your Site. ## Submission sequence ```mermaid theme={null} sequenceDiagram autonumber participant TM as Trial Manager participant AC as Aitrium Cloud participant SU as Site User participant OS as AitriumOS (local) participant INV as Investigator destination TM->>AC: Create trial with policies (de-identification, protocol, sites) SU->>AC: Sign in and request active trials AC-->>SU: Return authorized trials SU->>AC: Select trial and request policies AC-->>SU: Return trial policies SU->>OS: Select local patient dataset Note over OS: Validate, standardize, and
de-identify — all on the workstation OS->>INV: Transfer standardized, de-identified dataset (direct) OS->>AC: Send sanitized QA results & dataset structure (no imaging) AC->>TM: Notify of new submission ``` > **[Interactive version](https://app.eraser.io/workspace/2rQ6SX5mAbjJC7Q1xAKd?origin=share)** > > Open the full, interactive submission data-flow diagram. ## Firewall allowlist Permit outbound **HTTPS (TCP 443)** to the following destinations: | Destination | Purpose | If blocked | | - | - | - | | `api.aitriumos.com` | Core Aitrium API (trials, policies, dataset records) | **Submissions blocked** — trials and patient data will not load | | `app.aitriumos.com` | Web sign-in and installer downloads | Sign-in and installer downloads blocked | | `*.googleapis.com`, `*.firebaseapp.com`, `oauth2.googleapis.com` | User authentication (Google Firebase Authentication) | **Sign-in blocked** | | `rt-plan-standardizer-api-336813653216.us-central1.run.app` | Radiotherapy structure standardization — maps a dataset's structure names onto the trial's required structures | **Submissions containing RT structures fail partway through**, at the structure-mapping step. Sign-in and trial loading are unaffected, so a site that allows only the API will not notice until a submission is already under way. | | `audit-logging-microservice-336813653216.us-central1.run.app` | Regulatory audit trail of user and system actions | Audit events queue locally and are retried; they are not lost, but they do not reach Aitrium's audit store until the host is reachable. Submissions are unaffected. | | `storage.googleapis.com` | Application updates (and any Google Cloud Storage transfer you configure) | App updates unavailable — submissions unaffected | > [!NOTE] > > The most important address to allow is `api.aitriumos.com`: if it is blocked, users can sign in but trials and patient data will not load, and no data can be submitted. AitriumOS shows an in-app "Can't reach Aitrium" message in this state pointing the user to this guide. `storage.googleapis.com` only affects automatic app updates and never blocks a submission. > [!WARNING] > > **Testing these addresses in a browser does not validate the application.** A browser (and AitriumOS's own sign-in window) follows the machine's proxy configuration, while AitriumOS's background connections use their own route — so a destination can open fine in a browser and still be blocked for the application, or the reverse. Validate from inside the application: **Settings → Network** lists each Aitrium service with its status and names the route AitriumOS used. > [!NOTE] > > The structure-standardization and audit-logging destinations are Aitrium-operated services on Google Cloud Run (HTTPS/443). If your release uses different endpoints, your IT team is told which ones: [support@aitriumos.com](mailto:support@aitriumos.com). **Settings → Network** in AitriumOS also lists each service with its status. > [!TIP] > > Prefer to route this traffic through a corporate HTTP proxy instead of allowing direct egress? See [Corporate HTTP proxy](/security/aitrium-os/proxy-configuration). ### Transfer to the investigator | Destination | Purpose | Notes | | - | - | - | | Investigator's SFTP/FTP endpoint | Transfer of the prepared dataset | Host, port (typically TCP 22), and credentials are set by the investigator's organization — not entered or stored by your Site. The transfer connects directly from the workstation to the investigator and does not route through Aitrium. AitriumOS shows the host and port under **Settings → Network → Upload destinations**. | Allowing this connection differs from the HTTPS destinations above: * **No proxy.** The SFTP transfer always connects directly from the workstation. It cannot be routed through a web (HTTP) proxy, so the workstation's firewall must permit outbound TCP to the investigator's host and port. * **Allow the program, not just the port.** Endpoint-security and per-application firewall rules can block AitriumOS while allowing other programs on the same port. Allow the executable `NewLeaf.exe`: `C:\Program Files\AitriumOS\NewLeaf.exe` for the per-machine (MSI) installer, or `%LOCALAPPDATA%\AitriumOS\NewLeaf.exe` for the per-user installer. * **Validate from AitriumOS.** A successful `ssh`, `sftp` or `Test-NetConnection` from the same workstation only shows that the port is open for that program. Use **Settings → Network → Upload destinations → Check now**, which tests the connection AitriumOS itself uses without signing in or transferring data. > [!NOTE] > > The transfer originates from the **site's public egress IP address**. If the investigator's SFTP server restricts sources by IP, give the investigator's organization that address — there is no fixed Aitrium relay address. See [Upload connection troubleshooting](/aitrium-os/connection-troubleshooting) for what each connection message means, and [SFTP server compatibility](/security/aitrium-os/sftp-compatibility) for the SSH algorithms and authentication methods AitriumOS supports. ## Data residency — where patient data lives * **Raw patient DICOM (pixel data) is processed entirely on the local workstation and is never uploaded to Aitrium's cloud.** * Patient files leave the workstation **only** via the transfer to the investigator's destination, connecting directly from the workstation. No patient imaging is routed through Aitrium-controlled infrastructure. * Aitrium's cloud stores only non-sensitive metadata and metrics that AitriumOS extracts or computes from the local dataset — never the original images: * **Dataset structure / metadata** — the DICOM hierarchy (studies, series, modalities, instance counts) and references to supplementary files, used to confirm a submission is complete against the protocol. * **Derived quality metrics** — for radiotherapy, dose-volume-histogram curves (computed summaries, not original images). * **Platform configuration** — trial definitions, policies, automations, and integration settings. In short: structure and derived metrics go to Aitrium; the imaging itself goes only to the investigator's destination. ## Transfer credentials Your Site does **not** enter, hold, or manage the credentials used to transfer data to the investigator. The recipient (investigator/sponsor) organization configures and permits the transfer integration at the user level. Credentials are stored **encrypted at rest using Google Cloud KMS keys** — scoped to the owning recipient organization and to each participating site — and those keys never leave Aitrium's servers. When an authorized Site user performs a transfer, Aitrium decrypts the credentials server-side and re-encrypts them for delivery using a **short-lived session key tied to that user's authenticated session**, transmitted over TLS. AitriumOS then decrypts them **in memory**, uses them only for that transfer, and **discards them** — they are never written to the workstation's local storage. Which users may transfer data for a given trial is controlled by a per-user permission (see [Access management](/security/aitrium-os/access-management)). # Deployment & Updates Source: https://docs.aitriumos.com/security/aitrium-os/deployment System requirements, installer options, and how AitriumOS updates. For: Site IT For installation, sign-in, and update walkthroughs with screenshots, see [Getting started with AitriumOS](/aitrium-os/overview). This page summarizes the IT-relevant facts; for the full set of IT steps, start with the [IT setup checklist](/aitrium-os/it-setup). ## System requirements * **Windows 11** (and Windows 10), **64-bit (x64)**. * Microsoft Edge **WebView2** runtime — included with Windows 11; otherwise provisioned automatically, per-user, during setup. * **Normal operation requires no local administrator rights** under either installer below. ## Installer options | Installer | Scope | Administrator rights | Best for | | - | - | - | - | | **MSI** (default) | Per-machine | Typically required to **install** (e.g., when deployed centrally by IT); the application still **runs** in the user's context with no elevation. | Centrally-managed / IT-deployed fleets. | | **NSIS** | Per-user | **None** — installs into the user's profile and runs entirely in the user's context. | Self-service install where users cannot elevate. | > [!TIP] > > To satisfy a strict "no administrator privileges" requirement for self-installation, use the per-user NSIS installer. Aitrium can also set NSIS as the default for your sites — contact [support@aitriumos.com](mailto:support@aitriumos.com). Download the current release after signing in at [app.aitriumos.com](https://app.aitriumos.com) → **Downloads**. (Specific version binaries and their hashes can be provided for change-control purposes — see [Build integrity & validation](/security/aitrium-os/validation).) ## Firewall and endpoint-security rules Where endpoint-security products or per-application firewall rules control which programs may connect, allow the AitriumOS executable, `NewLeaf.exe`: | Installer | Executable | | - | - | | **MSI** (per-machine) | `C:\Program Files\AitriumOS\NewLeaf.exe` | | **NSIS** (per-user) | `%LOCALAPPDATA%\AitriumOS\NewLeaf.exe` | This matters most for the SFTP transfer to the investigator. It connects directly from the workstation and cannot use a web proxy, so a rule that blocks the program blocks the transfer even when the port is open. AitriumOS reports this case as **Blocked by a firewall** or **Blocked from connecting**. See [Data flows & residency](/security/aitrium-os/data-flows#transfer-to-the-investigator) for the destinations and [Upload connection troubleshooting](/aitrium-os/connection-troubleshooting) for how to validate the connection. ## Updates * **Integrity.** Every update package is **cryptographically signed and verified before it is applied**; a package that fails verification is rejected. Windows binaries are code-signed; macOS binaries are signed and notarized. * **Distribution.** Updates are delivered over HTTPS from Google Cloud Storage. * **Delivery depends on how the application was installed:** * **Per-user (NSIS):** the user is notified in-app when a new version is available and applies the update in their own context. * **Per-machine (MSI), centrally deployed:** version management is handled by your IT team through your deployment tooling. * **Scope.** Updates deliver fixes, improvements, and features; they do not change the security posture described in this section. # AitriumOS Security Overview Source: https://docs.aitriumos.com/security/aitrium-os/overview Security reference for AitriumOS — the desktop application installed at Sites — for IT and Information Security teams. For: Security and compliance reviewers · Site IT AitriumOS is the desktop application that **Sites** install on a workstation inside their own network. It receives a clinical trial's data-handling policy and runs validation, standardization, and **de-identification** on the Site's *local* patient DICOM data so the dataset conforms to that policy — before the prepared dataset is transferred directly to the investigator. > [!NOTE] > > AitriumOS is one component of the broader Aitrium platform. This section is the IT/security reference for the **AitriumOS desktop application** specifically; additional platform areas are documented elsewhere in this Trust & Security center over time. ## Security posture at a glance > **Patient data stays local** > > Raw patient imaging is processed on the workstation and is never uploaded to Aitrium's cloud. It leaves only via a transfer to the investigator's destination. > **Outbound client only** > > The application initiates outbound HTTPS connections, plus the direct SFTP transfer to the investigator; nothing connects to the workstation. There is no inbound listener and no server software to host. > **No administrator rights** > > Normal operation requires no elevation, and a per-user installer installs without administrator rights. > **Signed & scanned builds** > > Installers are code-signed via Microsoft Trusted Signing and verified clean by multi-engine scanning; updates are cryptographically verified before they apply. ## Security reference > **[Architecture](/security/aitrium-os/architecture)** > > Local and cloud components, with system and data-flow diagrams. > **[Data flows & residency](/security/aitrium-os/data-flows)** > > Network destinations, ports, firewall allowlist, and where patient data lives. > **[Access management](/security/aitrium-os/access-management)** > > Roles, trial-level permissioning, and authentication. > **[Build integrity & validation](/security/aitrium-os/validation)** > > Code signing, hashes, multi-engine scan results, and endpoint-protection guidance. ## Guides for IT teams > **[Site IT: setup checklist](/aitrium-os/it-setup)** > > Install, allow network access, configure a proxy, and validate AitriumOS at your site. > **[Site IT: deployment & updates](/security/aitrium-os/deployment)** > > System requirements, installers, and the update mechanism. > **[Site IT: corporate HTTP proxy](/security/aitrium-os/proxy-configuration)** > > Proxy configuration, authentication, and the acceptance test. > **[Trial organization IT: SFTP server compatibility](/security/aitrium-os/sftp-compatibility)** > > Supported SSH algorithms and sign-in methods, and the traffic an investigator's SFTP server will see. > [!NOTE] > > For a detailed IT/security review or to request environment-specific information (e.g., a complete firewall endpoint list), contact [support@aitriumos.com](mailto:support@aitriumos.com). # Corporate HTTP proxy Source: https://docs.aitriumos.com/security/aitrium-os/proxy-configuration Configure and validate AitriumOS with a corporate HTTP proxy, including Windows Integrated Authentication, NTLMv2, and Basic authentication. For: Site IT AitriumOS connects through your organization's HTTP proxy to reach its HTTPS services. It supports proxies with no authentication, Windows Integrated Authentication (NTLMv2/Negotiate), and Basic authentication. > [!NOTE] > > **Version covered: AitriumOS 2.2.5 for Windows.** If you use an earlier version, update before following this guide. Start with [Configure the proxy](#configure-the-proxy), then run the [Acceptance Test](#acceptance-test). For screenshots and sign-in help, see [What users will see](#what-users-will-see). ## Configure the proxy Select the setup that matches your Windows configuration: | Your configuration | What to do | | - | - | | **Enabled Windows manual proxy** | AitriumOS detects it automatically. No proxy environment variable is required. Follow [Windows manual proxy](#windows-manual-proxy). | | **PAC setup script or WPAD automatic discovery** | AitriumOS 2.2.5 and later follows the policy automatically. No proxy environment variable is required. Follow [PAC or WPAD](#pac-or-wpad). | | **PAC selects multiple proxies or requires automatic failover** | AitriumOS uses the first usable proxy the script returns and does not fail over to the alternatives. If your policy depends on failover, configure an explicit address as described in [PAC or WPAD](#pac-or-wpad), or contact [support](#contact-support). | ### Windows manual proxy 1. In **Windows Settings → Network & internet → Proxy → Manual proxy setup**, enable your approved proxy address and port. If already configured, leave it in place. 2. Fully exit AitriumOS, including any tray process, and launch it again. 3. Open **Settings → Network** in AitriumOS. Confirm **Connection: Hospital network** and the expected **Detected network**, then select **Test connection**. AitriumOS reads the proxy settings for the Windows user running the application. Configure the policy for each user on a shared workstation. There is no separate proxy-address field inside AitriumOS. > [!NOTE] > > Existing `HTTPS_PROXY` or `ALL_PROXY` environment variables can override detection of the Windows manual proxy. Review any previous test or deployment overrides if the detected address is unexpected. ### PAC or WPAD **From AitriumOS 2.2.5, automatic proxy configuration is honoured by background connections.** Earlier versions applied the PAC/WPAD policy only to the Windows sign-in component (WebView2) and sent every background connection direct, which could bypass the proxy without any visible error. AitriumOS now asks Windows itself — the same WinHTTP resolver the operating system uses — which proxy applies to each Aitrium destination. It reads `AutoConfigURL` and the **Automatically detect settings** policy for the Windows user running the application, evaluates your own PAC script, and honours a `DIRECT` result per destination. 1. Keep the Windows PAC/WPAD policy enabled. No proxy environment variable is required. 2. Confirm the script returns an approved proxy (or a deliberate `DIRECT`) for every required Aitrium HTTPS destination. See the [destination allowlist](/security/aitrium-os/data-flows#firewall-allowlist). 3. Fully exit AitriumOS, including any tray process, and launch it again. The policy is read at startup. 4. Open **Settings → Network** in AitriumOS. **Detected network** names both the proxy address and how it was discovered — `PAC url` or `WPAD auto-detect`. Then select **Test connection**. If **Detected network** is absent while Windows does have a proxy policy, AitriumOS reports that its background connections are not using your proxy. Treat that as a configuration problem to resolve before submissions, not a cosmetic warning. **Automatically detect settings** being switched on, as it is by default on Windows, does not count as a proxy policy on its own. If no WPAD configuration is found on the network, AitriumOS connects direct and shows no warning. > [!NOTE] > > AitriumOS re-checks the destination's proxy every few minutes, so a PAC change takes effect without a restart. If the script was unreachable when AitriumOS started, **Try again** or **Test connection** re-reads it immediately once it is back. Changing between *having* and *not having* a policy at all does require a restart. #### When an explicit address is still recommended Automatic discovery removes the need for an environment variable in most deployments. Configure an explicit `HTTPS_PROXY` instead when any of the following apply: * **Your PAC script returns several proxies with failover semantics.** AitriumOS uses the first usable entry the script returns and does not fail over to the alternatives, so a deployment that depends on failover should name the proxy you want explicitly. * **The proxy policy is applied per machine by a tool the user session cannot read** — for example a group policy or management agent that configures the service account or the machine store rather than the signed-in user's Internet Settings. AitriumOS reads the policy for the Windows user running the application, so a policy that account cannot see will not be discovered. * **Your site requires all traffic pinned to one audited proxy.** An explicit address fixes the route for every background connection regardless of what the script returns or how the network changes, which is easier to evidence in a security review. * **You are troubleshooting an absent Detected network.** If **Settings → Network** shows no **Detected network** while Windows does have a proxy policy, setting the address explicitly confirms whether the problem is discovery or the proxy itself — and restores correct routing immediately while you investigate. * **The PAC script is hosted on a slow or intermittently reachable server.** While the script cannot be evaluated, AitriumOS sends its background connections direct, shows a **Proxy configuration unavailable** notice, and retries automatically. On a network that blocks direct traffic, those connections fail until the script is reachable again. An explicit address removes that dependency. To do that, deploy a machine-level environment variable with your normal IT tooling: ```text theme={null} HTTPS_PROXY=http://proxy.example.org:8080 ``` Sign out of Windows and back in, or restart the workstation, so newly launched applications inherit the setting. Use your actual proxy host and port. Do not include credentials in the variable. An explicit address takes precedence over both the Windows manual proxy and automatic discovery, and pins every background connection to that one proxy. > **Using an existing managed HTTPS\_PROXY setting** > > You can retain an approved `HTTPS_PROXY` deployment. It takes precedence over Windows manual-proxy detection for background connections. Keep the Windows system proxy policy configured for WebView2 sign-in traffic as well. > > Use a machine-level setting for shared workstations; a per-user setting applies only to that account. After changing it, sign out and back in before launching AitriumOS. ### Network access requirements * Permit the required HTTPS destinations through the proxy. See the [destination allowlist](/security/aitrium-os/data-flows#firewall-allowlist). * If your proxy performs TLS inspection, install your organization's inspection CA in the Windows certificate store according to your policy. * Permit trial-specific SFTP/FTP connections separately. See [SFTP transfers bypass the proxy](#sftp-transfers-bypass-the-proxy). Configuring a proxy does not enforce a workstation-wide ban on direct traffic. Keep your firewall policy in place and verify routing during the Acceptance Test. ### SFTP transfers bypass the proxy > [!WARNING] > > **The proxy applies to AitriumOS's HTTPS traffic only.** The SFTP transfer of the prepared dataset to the trial's server always connects **directly** from the workstation, on the trial's configured port (usually TCP 22). It cannot be sent through an HTTP proxy, and a proxy or PAC setting has no effect on it. On a network that blocks direct outbound traffic, add a firewall exception for the trial's SFTP host and port, and allow the AitriumOS program `NewLeaf.exe` rather than only the port. The host and port are listed in **Settings → Network → Upload destinations**, where **Check now** confirms the connection. See [transfer destinations](/security/aitrium-os/data-flows#transfer-to-the-investigator) and [Upload connection troubleshooting](/aitrium-os/connection-troubleshooting). ## Authentication and credential protection AitriumOS first tries the proxy without credentials. If authentication is required, it attempts Windows sign-in, then a saved network credential. If neither succeeds, it presents the network sign-in form. | Proxy authentication | Expected behavior | | - | - | | **None** | Connects without a network sign-in prompt. | | **NTLMv2 / Negotiate** | Uses Windows SSPI to attempt authentication with the signed-in Windows session. Kerberos selection depends on your domain and proxy configuration and requires validation in your environment. | | **Basic** | Uses a saved proxy credential or asks the user to sign in. | Network credentials are separate from the user's Aitrium account. NTLMv1 has not been validated and is not recommended. When Windows sign-in succeeds, AitriumOS stores no additional network password. User-entered passwords are protected at rest with Windows DPAPI in the current user's context and are excluded from application logs and support bundles. **Forget sign-in** removes the saved credential. A rejected saved password is marked invalid so AitriumOS does not repeatedly retry it. ## What users will see Which screens appear depends on your network configuration. These Windows screenshots use a local test proxy; `127.0.0.1:8888` is an example, not an address to configure at your site. ### Automatic connection If the proxy accepts the current Windows sign-in, AitriumOS connects without asking for another password. The header displays **Hospital network**, and **Settings → Network** shows **Sign-in: Windows sign-in**. A proxy that does not require authentication also connects without a sign-in form. Check **Connection** and **Detected network** in Network settings to see the configured route; the authenticated **Hospital network** header indicator may not appear for this connection. ### Hospital-network sign-in requested **When it appears:** The proxy requires credentials and automatic authentication has not completed successfully. The screen is titled **Connect through your hospital network** and explains why another sign-in is needed. Enter the hospital-network username and password specified by your IT team, then select **Connect to Aitrium**. These may differ from your Aitrium account credentials. You can select **Continue with local tools** while your IT team helps resolve access. ![AitriumOS network sign-in screen with username and password fields, Connect to Aitrium, and Continue with local tools](https://mintcdn.com/aitrium/5cpnVag9RGVyF6q7/public/images/networking/hospital-network-sign-in.png?fit=max\&auto=format\&n=5cpnVag9RGVyF6q7\&q=85\&s=b30e7d7b9dbba2dbb3dc65fd90e23670) Hospital-network sign-in. The footer has an outdated version label; check the application header for the installed version. ### Credentials rejected or no longer accepted **When it appears:** A connection attempt using the entered credentials did not succeed. The form displays **We couldn’t verify these details** and allows another attempt. If a saved credential has been rejected, the title changes to **Update your hospital network sign-in**, with an **Update and reconnect** button. Enter your current work password or ask IT to confirm your account's proxy access. This message alone does not establish that a password has expired. ### Continuing with local tools **When it appears:** You choose to continue while network sign-in remains unresolved. The application opens with **Network sign-in needed** in the header and a persistent **Hospital network sign-in needed** banner. Local tools remain available. Previously loaded project information may still be visible, but live refreshes and submissions may fail until you reconnect. ![Trial dashboard with Network sign-in needed in the header and a hospital-network warning banner containing a Sign in button](https://mintcdn.com/aitrium/5cpnVag9RGVyF6q7/public/images/networking/network-local-tools.png?fit=max\&auto=format\&n=5cpnVag9RGVyF6q7\&q=85\&s=bfa5850d6841a4ea184477adb89b17b7) The network warning remains visible while previously loaded project information is on screen. A separate data-transfer status does not confirm access to Aitrium services. > [!NOTE] > > Use **Settings → Network → Test connection** to check live connectivity. Previously loaded data and separate transfer connections can remain visible while access to Aitrium services is unavailable. ### Reconnecting from the current page Select **Sign in** on the banner to open the hospital-network sign-in dialog without leaving the page. You can also select the header's **Network sign-in needed** indicator and choose **Sign in** or **Network settings**. ![Hospital-network sign-in dialog displayed over the current trial dashboard](https://mintcdn.com/aitrium/5cpnVag9RGVyF6q7/public/images/networking/network-reconnect-dialog.png?fit=max\&auto=format\&n=5cpnVag9RGVyF6q7\&q=85\&s=74ea97c3c0cd9ec74cf356b4db908d9c) Sign in to reconnect without leaving the current page. After successful sign-in, AitriumOS clears the resolved warning and refreshes project and integration information without reloading the application. Check the status of any previously failed submission before retrying it. ### Reviewing or removing a saved sign-in Open **Settings → Network** to review the connection: ![Network settings showing Network sign-in needed, detected proxy 127.0.0.1:8888, Test connection, and Add sign-in](https://mintcdn.com/aitrium/5cpnVag9RGVyF6q7/public/images/networking/network-settings-sign-in-needed.png?fit=max\&auto=format\&n=5cpnVag9RGVyF6q7\&q=85\&s=6c3b7b9ce739362af99ec2c3b273d8c4) Network settings shows the detected proxy and an Add sign-in action when authentication is needed. | Field or action | What it tells you or does | | - | - | | **Connection: Hospital network** | AitriumOS detected a configured proxy route. | | **Detected network** | Shows the proxy host and port; this field is informational. | | **Sign-in: Windows sign-in** | The current Windows session authenticated the connection. | | **Signed in as** | Identifies the separately saved network account, when present. | | **Test connection** | Checks whether AitriumOS can reach its services. | | **Add sign-in / Change sign-in** | Opens the network credential form when available. | | **Forget sign-in** | Removes AitriumOS's saved network credential after confirmation. | Removing a saved sign-in does not sign you out of Aitrium or Windows, and does not change the workstation's proxy configuration. Windows may still authenticate automatically, or existing proxy sessions may remain usable. If another sign-in is required, AitriumOS presents the same recovery flow described above. ### Other connection messages | Message | What to do | | - | - | | **Can't reach Aitrium** | Check the workstation connection. IT may need to check the proxy and permitted destinations. Select **Try again** once connectivity is restored. This message does not necessarily mean credentials are needed. | | **Updates unavailable** | The update check failed while the Aitrium API remained reachable. Ask IT to check access to the update service. This warning alone does not block other workflows; their destinations must still be reachable. | Windows may also display a proxy sign-in prompt alongside the AitriumOS form. Follow your IT team's guidance for the expected proxy. After correcting a connection issue, use **Try again** or **Test connection** to recheck it. If IT changes the proxy address or configuration, fully exit and reopen AitriumOS to pick up the new route. ## Acceptance Test Follow these steps on a managed Windows workstation using your organization's intended proxy policy. **1. Confirm the route** Configure the proxy, fully exit AitriumOS, and reopen it. Sign in to your Aitrium account. **2. Authenticate if requested** If **Connect through your hospital network** appears, sign in with an account approved by your IT team for testing. **3. Check Network settings** Open **Settings → Network** and confirm: * **Connection** is **Hospital network**. * **Detected network** shows the expected proxy host and port. * **Test connection** reports success. **4. Check online features** Confirm that projects and integration status refresh and the application update check succeeds. In **Settings → Network → Upload destinations**, select **Check now** for each trial's SFTP server and confirm it shows **Reachable**; then confirm a test submission reaches its configured destination. **5. Verify network policy** With your intended firewall restrictions active, confirm in proxy or firewall logs that Aitrium HTTPS traffic uses the approved proxy. If a temporary direct-HTTPS exception was granted, disable it for this test while retaining required SFTP/FTP access. **6. Test removal and recovery** If a separate credential was saved, select **Forget sign-in** and reconnect when prompted. Confirm that warnings clear and project and integration information refresh. Windows authentication or an existing proxy session may keep the connection working after the saved credential is removed. **7. Check sign-in after restarting** Fully exit and reopen AitriumOS. Confirm that Windows authentication or the saved network sign-in restores connectivity as expected. ## Troubleshooting ### Network settings shows `Connection: Direct` * Confirm the proxy was enabled before AitriumOS started. * Fully exit AitriumOS, including any background or tray process, and reopen it. * Confirm the proxy is configured for the same Windows user running AitriumOS. * For **Use setup script** or **Automatically detect settings**, follow [PAC or WPAD](#pac-or-wpad). ### The connection fails without showing network sign-in The proxy may be unreachable, may be closing the connection without a standard `407` response, or may be advertising an unsupported authentication scheme. Check the response in your proxy logs for the status code and authentication scheme names. You do not need to share raw authentication headers for initial troubleshooting. ### A saved password stopped working Open **Settings → Network → Change sign-in** and enter the user's current network password. AitriumOS deliberately avoids repeated attempts with a rejected saved password to reduce the risk of account lockout. ### TLS or certificate errors occur If your organization performs TLS inspection, ensure its root CA is installed in the Windows certificate store according to your workstation policy. ## Contact support Contact [support@aitriumos.com](mailto:support@aitriumos.com) with: * Your AitriumOS version and Windows domain/join status * The proxy configuration method: manual, PAC, or WPAD; whether one fixed proxy can be used * The proxy product, authentication method, and whether TLS inspection is enabled, if known * Which Acceptance Test steps passed or failed and any redacted application error message Please do not send passwords, authentication tokens, internal proxy addresses, PAC files, or unredacted logs by email. Your IT team can verify routing in its own logs and report the outcome. If further technical information is needed, we can coordinate through your organization's approved support channel. # SFTP Server Compatibility Source: https://docs.aitriumos.com/security/aitrium-os/sftp-compatibility SSH algorithms, authentication methods and connection behavior of AitriumOS as an SFTP client, for IT teams operating a trial's SFTP server. For: Trial organization IT This page is for the IT team that operates a trial's SFTP server. It lists what AitriumOS supports as an SFTP client and the traffic your server will see from participating sites. Site IT teams should start with [Upload connection troubleshooting](/aitrium-os/connection-troubleshooting). > [!NOTE] > > **Version covered: AitriumOS 2.2.7.** AitriumOS uses the libssh2 1.11 SSH library. On Windows it uses the Windows cryptography API (CNG); on macOS it uses OpenSSL. The two platforms support different algorithm sets, so check both columns below. ## How sites connect * AitriumOS is an SSH-2 SFTP client. Each site's workstation connects **directly** to the host and port configured in the trial's integration. Traffic does not pass through Aitrium, and it cannot go through a web (HTTP) proxy. * Connections come from each **site's public egress IP address**. There is no fixed Aitrium address to allowlist. If your server restricts source addresses, each site must send you its egress addresses. * If your host name resolves to several addresses, such as IPv6 and IPv4, AitriumOS 2.2.7 tries them one after another, in the order the site's resolver returns them. ## Supported algorithms SSH uses the first algorithm in the client's list that the server also supports. AitriumOS offers the algorithms below in this order of preference. | Category | Windows | macOS | | - | - | - | | **Key exchange** | `diffie-hellman-group-exchange-sha256`, `diffie-hellman-group16-sha512`, `diffie-hellman-group18-sha512`, `diffie-hellman-group14-sha256` | `curve25519-sha256`, `curve25519-sha256@libssh.org`, `ecdh-sha2-nistp256`, `ecdh-sha2-nistp384`, `ecdh-sha2-nistp521`, then the same Diffie-Hellman methods as Windows | | **Host key** | `rsa-sha2-512`, `rsa-sha2-256`, then legacy `ssh-rsa` | `ecdsa-sha2-nistp256`, `ecdsa-sha2-nistp384`, `ecdsa-sha2-nistp521`, `ssh-ed25519`, `rsa-sha2-512`, `rsa-sha2-256`, then legacy `ssh-rsa` | | **Cipher** | `chacha20-poly1305@openssh.com`, `aes256-ctr`, `aes128-ctr` | `chacha20-poly1305@openssh.com`, `aes256-gcm@openssh.com`, `aes256-ctr`, `aes128-gcm@openssh.com`, `aes128-ctr` | | **MAC** | `hmac-sha2-256`, `hmac-sha2-256-etm@openssh.com`, `hmac-sha2-512`, `hmac-sha2-512-etm@openssh.com` | Same as Windows | * **Integrated ciphers.** `chacha20-poly1305@openssh.com` and the AES-GCM ciphers include their own integrity protection, so no separate MAC is negotiated with them. * **Strict key exchange.** AitriumOS 2.2.7 supports the OpenSSH strict key exchange extension (`kex-strict-c-v00@openssh.com`), which mitigates the Terrapin attack. * **Not supported:** post-quantum hybrid key exchange (such as `sntrup761x25519-sha512` or `mlkem768x25519-sha256`) and DSA host keys. Servers that offer post-quantum methods alongside the classic ones above are unaffected. * **Older algorithms**, such as SHA-1-based key exchange and MACs and CBC-mode ciphers, are still offered at the lowest preference so older servers keep working. A server that disables them is unaffected. ### Recommended server settings > [!NOTE] > > **Servers that work with AitriumOS today need no changes for 2.2.7.** AitriumOS 2.2.7 only adds algorithms and reorders its preferences; everything earlier versions could negotiate, including legacy `ssh-rsa` host keys and SHA-1 key exchange and MACs, is still accepted. The settings below are guidance for **new servers or when hardening** an existing one. When hardening, keep at least one algorithm from each row enabled so that **both Windows and macOS** workstations can connect: | Category | Keep at least one of | | - | - | | Key exchange | `diffie-hellman-group-exchange-sha256`, `diffie-hellman-group16-sha512`, `diffie-hellman-group18-sha512`, `diffie-hellman-group14-sha256` | | Host key | An **RSA host key**, preferably offered as `rsa-sha2-256` or `rsa-sha2-512` (legacy `ssh-rsa` is still accepted) | | Cipher | `chacha20-poly1305@openssh.com`, `aes256-ctr` or `aes128-ctr` | | MAC | `hmac-sha2-256` or `hmac-sha2-512`, with or without `-etm@openssh.com` (not needed if only `chacha20-poly1305@openssh.com` is offered) | > [!WARNING] > > **Windows workstations need an RSA host key and an AES-CTR or ChaCha20 cipher.** A server with only an Ed25519 or ECDSA host key, only elliptic-curve key exchange, or only AES-GCM ciphers accepts macOS workstations but not Windows workstations. Windows workstations then report *The SFTP server's security settings aren't supported by this version of AitriumOS*. ### Changes in AitriumOS 2.2.7 | | AitriumOS 2.2.6 | AitriumOS 2.2.7 | | - | - | - | | Encrypt-then-MAC (`hmac-sha2-256-etm@openssh.com`, `hmac-sha2-512-etm@openssh.com`) | Not supported | Supported | | `chacha20-poly1305@openssh.com` | Not supported | Supported | | AES-GCM | Not supported | Supported on macOS | | Preferred cipher | `aes256-ctr`, then `aes128-ctr` | `chacha20-poly1305@openssh.com`, `aes256-gcm@openssh.com`, `aes256-ctr`, `aes128-gcm@openssh.com`, `aes128-ctr`, where supported | | No algorithm in common | Generic connection error | *The SFTP server's security settings aren't supported by this version of AitriumOS* | A server that accepts **only** encrypt-then-MAC MACs requires AitriumOS 2.2.7 or later. ## Authentication | Method | Support | | - | - | | **Password** | Supported (SSH `password` method). | | **Private key** | Supported (SSH `publickey` method) with an **RSA** key, optionally protected by a passphrase. If both a key and a password are configured, the key is used. | | **Keyboard-interactive** | Not supported. A server that offers only `keyboard-interactive`, as some PAM-based setups do, rejects AitriumOS. Enable `password` or `publickey` for the trial's account. | | **Multi-factor sign-in** | Not supported. The trial's account must be able to sign in with a single password or key. | **RSA key signatures.** AitriumOS signs RSA key logins with `rsa-sha2-512` or `rsa-sha2-256`. A server that accepts **only** the legacy `ssh-rsa` signature for key logins works if it advertises that restriction to clients (OpenSSH 9.7 or later does); on older servers, also accept `rsa-sha2-256` or `rsa-sha2-512` in `PubkeyAcceptedAlgorithms`. **Private key formats.** PEM (`-----BEGIN RSA PRIVATE KEY-----`) works on every platform and is the recommended format. OpenSSH format (`-----BEGIN OPENSSH PRIVATE KEY-----`) is also accepted. On Windows, AitriumOS converts an OpenSSH-format key with the `ssh-keygen` tool from Windows' **OpenSSH Client** feature, so each site's workstation needs that feature installed. PuTTY `.ppk` keys are not accepted; export them in OpenSSH format with PuTTYgen first. Credentials are configured by the trial organization and delivered encrypted to authorized site users. Sites do not enter or hold them. See [Transfer credentials](/security/aitrium-os/data-flows#transfer-credentials). ## Traffic your server will see | Traffic | What happens | How often | | - | - | - | | **Upload** | Sign-in, then SFTP transfer of the prepared, de-identified dataset. | Each submission. On a network failure, AitriumOS tries to connect up to three times, 2 and then 4 seconds apart. A rejected sign-in is not retried. | | **Delivery check** | After each upload, AitriumOS reads the uploaded file's size on the server to confirm delivery. A full read-back with a SHA-256 comparison can be enabled per integration on request. | Each upload. | | **Reachability check** (from 2.2.6) | Connection, SSH identification and key exchange only, then disconnect with the reason `AitriumOS reachability check`. **No sign-in, no SFTP session, no data.** | At most once a day per workstation and destination, at a randomized time, and skipped after a successful upload or connection test in the last 24 hours. Also before a workstation's first submission to your server (at most once an hour), and when a site user selects **Check now**. | | **Connection test** | Sign-in with the trial's credentials, without transferring data. | Automatically when a site user opens the trial, at most 4 times per 24 hours per workstation and destination. A success is reused for 24 hours. After a rejected sign-in there are no automatic retries. Site users can also start a test. | > [!NOTE] > > Many workstations at one hospital can share a single public IP address. The limits above apply per workstation, so intrusion-prevention or ban rules (for example fail2ban) should allow for several workstations connecting from one address. The delivery check needs the trial's account to be able to read the attributes of files it has uploaded. The full read-back also needs read access to those files. ## Troubleshooting from the server side * **Connection closes after the key exchange, before sign-in, with the reason `AitriumOS reachability check`:** this is the handshake-only check working as designed. * **"No matching" key exchange, host key, cipher or MAC in your server log:** compare your server's enabled algorithms with [Recommended server settings](#recommended-server-settings). Tell sites to update to AitriumOS 2.2.7 if your server accepts only encrypt-then-MAC MACs or only ChaCha20. * **No connection attempt in your log while a site reports "No response" or "refused the connection":** the traffic is blocked before it reaches your server, by the site's outbound firewall or your own address restrictions. For compatibility questions, contact [support@aitriumos.com](mailto:support@aitriumos.com). # Build Integrity & Validation Source: https://docs.aitriumos.com/security/aitrium-os/validation Code signing, integrity hashes, multi-engine scan results, endpoint-protection guidance, and privileges. For: Site IT · Security and compliance reviewers AitriumOS installers are code-signed and independently verifiable. This page documents the integrity controls and the validation performed on a release. ## Endpoint protection (EDR / antivirus) compatibility There are no known incompatibilities with endpoint-protection (EDR / antivirus) products. AitriumOS is a code-signed application that runs in the user's context. As with many clinical/imaging desktop tools, an endpoint-protection product may apply heuristics to a few legitimate behaviors; if needed, the cleanest approach is to allow the application by: * **Code-signing publisher** — the installers are signed via **Microsoft Trusted Signing**; the publisher is shown in the file's **Properties → Digital Signatures** tab. * **Install path** — by default, the per-machine (MSI) installer installs under `C:\Program Files\` (e.g., `C:\Program Files\AitriumOS\`), and the per-user (NSIS) installer installs under `%LOCALAPPDATA%` (e.g., `%LOCALAPPDATA%\AitriumOS\`). The application executable is `NewLeaf.exe`; allow it in per-application network rules so the direct SFTP transfer is not blocked (see [Deployment & updates](/security/aitrium-os/deployment#firewall-and-endpoint-security-rules)). * **Application data directory** — `%APPDATA%\newleaf.ai\` (Windows *roaming* app-data; this is the runtime data folder, distinct from the install path above). For awareness, behaviors an EDR may flag heuristically: the bundled imaging helper executables, the spawning of these helpers as child processes, and the in-app updater downloading and launching a signed update. > [!NOTE] > > Endpoint-protection results are policy-dependent, so a behavioral pass in your own EDR environment is the authoritative test. Aitrium can support a validation pass on request. ## Privileges & OS compatibility * **No local administrator privileges** are required for normal operation under either installer; the per-user (NSIS) installer also installs without admin rights. * **Windows 11** (64-bit / x64) is supported; WebView2 is included with Windows 11. ## Validation performed The following checks are run against each release. Results below are for **v2.2.7 (x64)**, recorded 2026-09-30. | Validation | Result | | - | - | | **Authenticode code-signature verification** (both installers) | ✅ Valid — signature verifies, the signing certificate is not revoked (CRL checked), chains to the Microsoft Identity Verification Root CA 2020, and is RFC-3161 timestamped by the Microsoft Public RSA Time Stamping Authority. Confirms the binaries are signed by the stated publisher and unaltered since signing. | | **Cryptographic integrity (hash manifest)** | ✅ Recorded — see below; lets your team confirm a downloaded file matches the published build. | | **Multi-engine static scan** (incl. major EDR/AV vendors, via VirusTotal) | ✅ Clean — 0 detections on both installers (0/62 MSI, 0/71 NSIS). | | **EDR behavioral validation** (install + full submission workflow on an EDR-enrolled Windows 11 endpoint) | Available on request — run against an evaluation tenant or supported under your own policy. | ### v2.2.7 hash manifest (SHA-256) | Installer | SHA-256 | | - | - | | `AitriumOS_2.2.7_x64_en-US.msi` (MSI) | `b12abf3566c7e265a62292a3e1f054239e77beb9758d1c842a0fd803c860027d` | | `AitriumOS_2.2.7_x64-setup.exe` (NSIS) | `6004fdc6aec9d2253311ca8257c87bbe91a9f8ce063b2746efe19db2315c6714` | **Independent verification (VirusTotal, scanned 2026-09-30):** * [MSI installer report (0/62)](https://www.virustotal.com/gui/file/b12abf3566c7e265a62292a3e1f054239e77beb9758d1c842a0fd803c860027d) * [NSIS installer report (0/71)](https://www.virustotal.com/gui/file/6004fdc6aec9d2253311ca8257c87bbe91a9f8ce063b2746efe19db2315c6714) # Trust & Security Source: https://docs.aitriumos.com/security/overview Security, privacy, and compliance information for the Aitrium platform. For: Security and compliance reviewers at sites and trial organizations This Trust & Security center documents how Aitrium products handle data, networking, access, and software integrity. It is written for security and compliance reviewers evaluating Aitrium, at sites and at trial organizations. The Aitrium platform spans several products. Security documentation is being expanded across the platform; coverage available today is below. ## Available now > **[AitriumOS — Desktop App for Sites](/security/aitrium-os/overview)** > > The IT & security reference for the desktop application that Sites install to validate, de-identify, and transfer clinical trial data — architecture, data flows, access management, deployment, and build integrity. ## Deploying or operating Aitrium? The step-by-step IT guides live with each audience's documentation: > **[Site IT](/aitrium-os/it-setup)** > > Install AitriumOS, allow its network connections, configure a proxy, and validate the setup. > **[Trial organization IT](/security/aitrium-os/sftp-compatibility)** > > Prepare the SFTP server that receives a trial's data from participating sites. > [!NOTE] > > Additional platform areas (for example, the Aitrium web platform) will be documented here over time. For a specific request, contact [support@aitriumos.com](mailto:support@aitriumos.com). # EORTC Submission Training Source: https://docs.aitriumos.com/training/basic-submission Training curriculum for clinical site staff submitting patient datasets to trials using the basic submission workflow in AitriumOS. For: Site users ## Who this training is for Clinical site staff — for example radiotherapy technologists, medical physicists, or trial data managers — responsible for submitting patient imaging data to a clinical trial through Aitrium. You will normally arrive at this page from a link in the Aitrium portal or AitriumOS, or from your trial coordinator, identifying it as the training for your trial. If you are unsure whether this is the right curriculum for your trial, ask your trial coordinator. ## What you will learn * How to download and set up AitriumOS, including what your IT team needs to confirm before you start * How the submission process protects patient privacy through validation, standardization, and de-identification * How to submit a patient dataset, monitor its status, and resubmit when needed * Where to get help if something goes wrong ## Curriculum Review the following materials in order: **1. Getting Started** Read [Getting Started](/aitrium-os/overview), including the **Before You Begin** section — forward its IT requirements to your IT team if you have not already. Watch the installation and first-use videos on that page. *(\~10 minutes)* **2. EORTC Data Submission** Read [EORTC Data Submission](/aitrium-os/no-protocol-submissions) and watch the step-by-step walkthrough video at the top of the page. Pay particular attention to the de-identification review step and the **Resubmitting a Dataset** section. *(\~20 minutes)* > [!WARNING] > > **Critical behaviors.** Keep AitriumOS open until the **Submission complete** screen appears at the end of every upload, and always confirm the dataset shows as submitted on the trial page before you finish. Closing the application too early can leave a submission unregistered — the [EORTC Data Submission](/aitrium-os/no-protocol-submissions#5-upload-to-trial) guide covers both behaviors. > [!NOTE] > > **Trial-specific instructions.** Some trials display additional instructions from the trial team in AitriumOS after you complete a submission. These supplement this training with requirements unique to your trial — review and follow them each time they appear. ## Confirming your training After reviewing the materials above, confirm completion in the Aitrium web portal. You must confirm before you can upload patient data to the trial. **1. Open your trials** Sign in to [Trial Participation](https://app.aitriumos.com/dashboard/participation) in the Aitrium portal. It lists the trials your site has been added to, and flags any trial waiting on your training. Select that trial. You can also click **Confirm training** on the **Confirm your training** card on your portal dashboard. **2. Review and confirm** In the **Complete the trial training** section, open the training curriculum if you haven't already, read the statement, tick the confirmation box, and click **Confirm training**. One confirmation covers every trial that requires this training. Your confirmation — including the training version you reviewed and the date — is recorded for the trial organization's compliance records. If the training materials are materially updated (for example, after a significant software change), you will be asked to review and confirm again before your next upload. ## Questions? Contact your trial coordinator for trial-specific questions, or [support@aitriumos.com](mailto:support@aitriumos.com) for help with AitriumOS itself. # RTQA Submission Training Source: https://docs.aitriumos.com/training/rtqa-submission Training curriculum for clinical site staff submitting patient data to trials using the RTQA submission workflow in AitriumOS. For: Site users ## Who this training is for Clinical site staff — for example radiotherapy technologists, medical physicists, or trial data managers — responsible for submitting patient imaging data to a clinical trial through AitriumOS, where the trial page shows a **Trial Data Submission Schedule** with a **Patient Submission Queue** of each patient's study arm, regimens, and submission status. You will normally arrive at this page from a link in the Aitrium portal or AitriumOS, or from your trial coordinator, identifying it as the training for your trial. If you are unsure whether this is the right curriculum for your trial, ask your trial coordinator. ## What you will learn * How to set up AitriumOS, including what your IT team needs to confirm before you start * How to configure a patient's treatment regimen so their data submissions are scheduled correctly * How the submission process protects patient privacy through validation, standardization, and de-identification * How QA policy evaluation works and how to respond to deviations * How to submit each patient's scheduled datasets, monitor their status, and resubmit when needed * Where to get help if something goes wrong ## Curriculum Review the following materials in order: **1. Getting Started** Read [Getting Started](/aitrium-os/overview), including the **Before You Begin** section — forward its IT requirements to your IT team if you have not already. Watch the installation and first-use videos on that page. *(\~10 minutes)* **2. RTQA Data Submission** Read [RTQA Data Submission](/aitrium-os/protocol-submissions) and watch the step-by-step walkthrough video at the top of the page. The guide covers patient regimen setup, the trial data submission schedule, QA policy evaluation, and the **Resubmitting a Dataset** section. Pay particular attention to the de-identification review step. *(\~30 minutes)* > [!WARNING] > > **Critical behaviors.** Keep AitriumOS open until the **Submission complete** screen appears at the end of every upload, and always confirm the event shows **Completed** in the Patient Submission Queue before you finish. Closing the application too early can leave a submission unregistered — the [RTQA Data Submission](/aitrium-os/protocol-submissions#5-data-transfer) guide covers both behaviors. > [!NOTE] > > **Trial-specific instructions.** Some trials display additional instructions from the trial team in AitriumOS after you complete a submission. These supplement this training with requirements unique to your trial — review and follow them each time they appear. ## Confirming your training After reviewing the materials above, confirm completion in the Aitrium web portal. You must confirm before you can upload patient data to the trial. **1. Open your trials** Sign in to [Trial Participation](https://app.aitriumos.com/dashboard/participation) in the Aitrium portal. It lists the trials your site has been added to, and flags any trial waiting on your training. Select that trial. You can also click **Confirm training** on the **Confirm your training** card on your portal dashboard. **2. Review and confirm** In the **Complete the trial training** section, open the training curriculum if you haven't already, read the statement, tick the confirmation box, and click **Confirm training**. One confirmation covers every trial that requires this training. Your confirmation — including the training version you reviewed and the date — is recorded for the trial organization's compliance records. If the training materials are materially updated (for example, after a significant software change), you will be asked to review and confirm again before your next upload. ## Questions? Contact your trial coordinator for trial-specific questions, or [support@aitriumos.com](mailto:support@aitriumos.com) for help with AitriumOS itself. # Advanced Trial Configuration Source: https://docs.aitriumos.com/trial-accelerator/advanced-configuration Advanced features for configuring dose constraints and data collection schedules in Trial Accelerator For: Trial organization admins # Advanced Trial Configuration Once a protocol-driven trial is live, you have a suite of configuration tools to refine the setup. These features let you tailor arms/regimens, enforce dose constraints, shape the data collection timeline, and set up site-events for ongoing quality and compliance. *** ## 1. Manually Create or Edit Study Arms & Regimens You can fine-tune the treatment structure of your trial beyond automatic extraction: * Use the **Arms & Regimens editor** to add new arms (e.g., "Adaptive", "Hypofractionated") or deactivate existing ones * Define each regimen's dose, fractionation, and modality (e.g., 60 Gy in 30 fx, IMRT) * Reassign patients to updated arms when needed * All changes are logged and version-controlled ### Key Features * Add unlimited study arms to accommodate trial complexity * Configure treatment parameters specific to each arm * Maintain audit trail of all modifications * Update active trials without disrupting ongoing data collection *** ## 2. Add Dose Constraints to Treatment Regimens Each regimen can have one or more ROI-specific dose constraints: ### Example Constraints * **Spinal Cord**: Dmax \< 45 Gy * **Heart**: V20Gy \< 10% * **Lung**: Mean \< 12 Gy ### Constraint Types * **Hard constraints**: Must-pass requirements that block submission if violated * **Soft constraints**: Advisory warnings that flag potential issues Constraints are used in QA review and scorecard generation to ensure protocol compliance across all participating sites. *** ## 3. Advanced Data Collection Schedules The schedule of expected data submissions can be customized beyond the protocol-extracted defaults: ### Customization Options * **Add/edit events** such as "Week 3 Mid-Tx" or "Follow-up Month 6" * **Specify required file types** (e.g., CT, RTSTRUCT, MRI, RTDOSE) * **Configure timing logic** (e.g., every 3 months, ±5 days) * **Apply globally or to specific arms** for arm-specific data requirements ### Event Types * **Patient-level events**: Tied to individual patient timelines (treatment start, follow-ups) * **Site-level events**: Apply to the entire site (training, credentialing, audits) *** ## 4. Configure Site-Level Events To enforce standards and facilitate site onboarding: ### Site-Level Events Configure critical milestones for each participating site: * **Investigator training windows**: Schedule and track required training sessions * **Credentialing deadlines**: Ensure sites meet qualification requirements * **Interim QA audits**: Schedule periodic quality assessments These events appear on the trial dashboard for each site, providing visibility into trial readiness and ongoing compliance. *** ## Best Practices ### Version Control * Always review draft versions before publishing. Onced published, the changes to your protocol will automatically take affect. * Review the version history to track trial evolution ### Testing * Test data collection schedules with sample submissions * Verify dose constraints with representative treatment plans *** ## Related Resources * [Creating Protocol-Driven Trials](/trial-accelerator/creating-protocol-trials) - Complete setup workflow * [Trial Accelerator Overview](/trial-accelerator/overview) - Product introduction and key features * [Data Tools](/aitrium-os/data-tools) - De-identification and data processing tools * [Integrations](/aitrium-admin/integrations) - Data transfer configuration # Creating Protocol-Driven Trials Source: https://docs.aitriumos.com/trial-accelerator/creating-protocol-trials Step-by-step guide for creating a protocol-driven trial using Advanced Mode in Trial Accelerator For: Trial organization admins # Creating a Protocol-Driven Trial This guide outlines the step-by-step process for creating a protocol-driven trial using the Advanced Mode in Trial Accelerator. This mode supports automatic ingestion of trial protocols, digitization of study arms and regimens, and configuration of downstream data workflows for designated hospital sites. *** ## Trial Setup Workflow ### Step 1 – Create a Trial ![Create new trial button in Trial Dashboard](https://mintcdn.com/aitrium/Oz3RPd1teRou2Jhk/images/trial_accelerator_images/%5Bimage1%5D.png?fit=max\&auto=format\&n=Oz3RPd1teRou2Jhk\&q=85\&s=fa75c6ab409ba2893a125a1c175caf9f) Begin by navigating to the Trial Dashboard and selecting **Create New Trial**. Enter the following: * Trial Name * Start Date * Description (optional) Click **Next** to proceed. Then, select **Protocol Driven Trial** to begin. ![Protocol Driven Trial selection screen](https://mintcdn.com/aitrium/Oz3RPd1teRou2Jhk/images/trial_accelerator_images/%5Bimage2%5D.png?fit=max\&auto=format\&n=Oz3RPd1teRou2Jhk\&q=85\&s=1704ef316d8ecdb2db351225c4500cb3) *** ### Step 2 – Upload Protocol Document First, select your protocol method. We recommend creating a draft from PDF. ![Protocol upload method selection](https://mintcdn.com/aitrium/Oz3RPd1teRou2Jhk/images/trial_accelerator_images/%5Bimage3%5D.png?fit=max\&auto=format\&n=Oz3RPd1teRou2Jhk\&q=85\&s=8f95c56abce3789a718baed8acc57bdd) Upload the trial protocol in supported formats (PDF or DOCX). The system will extract: * Study arms and treatment regimens * Dose and fractionation schedules * Inclusion/exclusion criteria (informational only) * Submission event timelines You will see something similar to the following example. ![Extracted study arms and regimens display](https://mintcdn.com/aitrium/Oz3RPd1teRou2Jhk/images/trial_accelerator_images/%5Bimage4%5D.png?fit=max\&auto=format\&n=Oz3RPd1teRou2Jhk\&q=85\&s=aae4a93647e7ed10cd193447032226b9) Each of the study arms and regimens can be explored, confirmed, and edited here. *** ### Step 3 – Confirm Study Arms and Regimens Review the proposed arms and associated regimens. You can: * Rename or remove arms * Adjust dose, fractionation, and modality settings * Add new arms or regimens manually When the configuration matches your protocol, click **Publish Version** in the top right. *** ### Step 4 – Verify Data Collection Schedule Next, navigate to **Data Collection Schedule** to confirm and edit the system's parsed submission events. ![Data Collection Schedule interface](https://mintcdn.com/aitrium/Oz3RPd1teRou2Jhk/images/trial_accelerator_images/%5Bimage5%5D.png?fit=max\&auto=format\&n=Oz3RPd1teRou2Jhk\&q=85\&s=e05ed37ea6f487cb23dc81be9c9e365c) For each event: * Review the name, anticipated event information, and due date information ![Event details configuration](https://mintcdn.com/aitrium/Oz3RPd1teRou2Jhk/images/trial_accelerator_images/%5Bimage6%5D.png?fit=max\&auto=format\&n=Oz3RPd1teRou2Jhk\&q=85\&s=30ddbb49b533b372cfc2078544cdcfc1) * Adjust timing windows (e.g., ±3 days) or anchor dates By selecting **Add Data Collection Event**, fully customizable patient/site level events can be added as well: ![Add custom data collection event](https://mintcdn.com/aitrium/Oz3RPd1teRou2Jhk/images/trial_accelerator_images/%5Bimage7%5D.png?fit=max\&auto=format\&n=Oz3RPd1teRou2Jhk\&q=85\&s=751e40e64bfc3141c88c7415f073868d) Click **Continue** when ready. *** ### Step 5 – Assign De-Identification Policy Using either the activation checklist modal or navigating to **Settings**, add a DICOM anonymization policy to your trial. ![De-identification policy assignment interface](https://mintcdn.com/aitrium/Oz3RPd1teRou2Jhk/images/trial_accelerator_images/%5Bimage10%5D.png?fit=max\&auto=format\&n=Oz3RPd1teRou2Jhk\&q=85\&s=ff272d4cb0faf4e12d061edb00c3a816) You will be prompted to one of the following: * **Create new policy**: Define a new DICOM de-identification policy based on an Aitrium template or from scratch.. * **Use existing**: Leverage an existing de-identification policy which you've used for other projects. Once you've selected your policy, click **Publish Latest** to assign the policy to the trial. *** ### Step 6 – Enroll Trial Sites In the top-level navigation, select **Sites** to view your enrolled sites. To add a site, select **Add Sites** in the top right. Adding a site will prompt you to select an existing Aitrium Network site: ![Add sites from Aitrium Network](https://mintcdn.com/aitrium/Oz3RPd1teRou2Jhk/images/trial_accelerator_images/%5Bimage8%5D.png?fit=max\&auto=format\&n=Oz3RPd1teRou2Jhk\&q=85\&s=a8847199aa19916296b2b6e32e1710ba) If a site you're looking to add does not exist, send an email to [contact@aitriumos.com](mailto:contact@aitriumos.com) with the following information to begin the onboarding process: * Site Name * Site City, Country, State/Province * Site trial POC (First + Last name, Email Address) Multiple sites may be added at any time. Click **Add X Sites** to add them to the trial. *** ### Step 7 – Assign Designated Site Users Once a site has been added, you will also have the ability to authorize site users' upload permissions: ![Authorize site users interface](https://mintcdn.com/aitrium/Oz3RPd1teRou2Jhk/images/trial_accelerator_images/%5Bimage9%5D.png?fit=max\&auto=format\&n=Oz3RPd1teRou2Jhk\&q=85\&s=86c44fb0d0e3557c3e2996723b9ae080) These users will access a guided upload interface tailored to the arm, regimen, and event schedule. At this time, all users authorized to a trial will have the ability to upload patient data. *** ### Step 8 – Configure Data Transfer Integration The Aitrium team will configure a data transfer integration for your organization. If you do not have an integration present in the Integrations page, reach out to [contact@aitriumos.com](mailto:contact@aitriumos.com) *** ## Trial Activation and Propagation Once all setup steps are complete: * The trial is automatically deployed to all assigned sites * Designated users will see the trial in the AitriumOS desktop application * Upload workflows will be pre-configured based on: * Assigned study arms and regimens + resulting data requirements * Data collection schedules * De-identification policy * Structure nomenclature Finally, click **Publish Version** in the upper-right hand corner to propagate your trial to all participating sites. Your trial is now live. *** ## Next Steps Now that your trial is live, you can explore [Advanced Configuration](/trial-accelerator/advanced-configuration) options to further customize your trial setup with dose constraints, benchmark cases, and more. # Getting Started Source: https://docs.aitriumos.com/trial-accelerator/overview Introduction to creating and managing protocol-driven clinical trials with Trial Accelerator For: Trial organization admins # Trial Accelerator Overview Trial Accelerator enables you to create and manage protocol-driven clinical trials with automated configuration and streamlined site deployment. This platform is ideal for trials with structured protocols and well-defined data requirements. ## What is a Protocol-Driven Trial? The Advanced Trial Creation workflow minimizes manual setup by: * **Automatically extracting study configurations** from protocol documents * **Digitizing study arms and regimens** with dose and fractionation schedules * **Configuring downstream data workflows** for designated hospital sites * **Automating site-level experiences** including curated regimens and data collection schedules ## Key Features ### Automated Protocol Ingestion Upload trial protocols in PDF format and let the system extract: * Study arms and treatment regimens * Dose and fractionation schedules * Inclusion/exclusion criteria (informational) * Submission event timelines ### Site Management * Enroll multiple hospital sites from the Aitrium Network * Assign designated users with upload permissions * Deploy trial configurations automatically to all sites ### Data Collection * Configure custom data collection schedules * Set timing windows and anchor dates for submissions * Define patient-level and site-level events ### Quality Assurance * Apply DICOM de-identification policies * Configure data transfer integrations (SFTP) * Monitor trial progress across all sites ## Getting Started To create your first protocol-driven trial, follow the [Creating Protocol-Driven Trials](/trial-accelerator/creating-protocol-trials) guide, which walks through the complete setup process from trial creation to site deployment. For advanced features like dose constraints and benchmark cases, see [Advanced Configuration](/trial-accelerator/advanced-configuration). *** ## Troubleshooting & Support For additional help: * Contact support at [support@aitriumos.com](mailto:support@aitriumos.com) * For site onboarding requests, email [contact@aitriumos.com](mailto:contact@aitriumos.com)