• In January, 2018, the live, public version of the AACT database will be moving to a new server. The hostname/IP address you use to connect to it will change. The new IP address will be static so that those who need to, can add it to their organization's network whitelist. This AACT website will remain at the current url, so you will always be able to find information about how to connect to the current database here.
  • The live AACT database is temporarily unavailable because the daily update is running.

AACT Database Schema

The diagram below illustrates how the AACT database is structured and identifies all tables/columns. It presents tables, columns and relationships.

All tables include the unique study identifier: nct_id. This id provides a way to a) find all data for a particular study and b) facilitate query development that joins multiple tables.

AACT documentation may be downloaded from the following links:

Please refer to the National Library of Medicine's (NLM) documentation for authoritative definitions of the data elements:

The online data dictionary includes links to sections of this NLM documentation to provide documentation about specific data element.

Study-related Tables

Aact schema

What were the primary considerations when designing the database?

When designing the database, we tried to balance the following objectives:

  • Present data exactly as it exists in
  • Make the information as easy to understand & analyze as possible.
  • Use consistent names and structures throughout the database. Make it predictable; minimize uncertainty.
  • Provide value-added attributes, identify them as such, and keep them separate from the raw content. (The Calculated_Values table contains data elements that were derived from existing data.)

Naming Conventions

  • Table names are all plural. (ie. studies, facilities, interventions, etc.)
  • Column names are all singular. (ie. description, phase, name, etc.)
  • Table/column names derived from multiple words are delimited with underscores. (ie. mesh_term, first_received_date, number_of_groups, etc.)
  • Case (upper vs lower) is not relevant since PostgreSQL ignores case. Studies, STUDIES and studies all represent the same table and can be used interchangably.
  • Information about study design entered into during registration is stored in AACT tables prefixed with Design_ to distinguish it from the results data. For example, the Design_Groups table contains registry information about anticipated participant groups, whereas the Result_Groups table contains information that was entered after the study has completed to describe actual participant groups. Design_Outcomes contains information about the outcomes to be measured and Outcomes contains info about the actual outcomes reported when the study completed.
  • Where possible, tables & columns are given fully qualified names; abbreviations are avoided. (ie. description rather than desc; category rather than ctgry)
  • Unnecssary and duplicate verbiage is avoided. For example: Studies.source instead of Studies.study_source
  • Columns that end with _id represent foreign keys. The prefix to the _id suffix is always the singular name of the parent table to which the child table is related. These foreign keys always link to the id column of the parent table.

    Child_Table.parent_table_id =

    For example, a row in Facility_Contacts links to it’s facility through the facility_id column.

    Facility_Contacts.facility_id =

Structural Conventions

  • Every table has an nct_id column to link rows to its related study in the Studies table. All study-related data can be linked directly to the Studies table via the nct_id. (Note: The schema diagram omits several of the lines that represent relationships to Studies. This was done to avoid appearing complex and confusing. Relationships to the Studies table can be assumed since every table includes the NCT ID.)
  • Studies.nct_id = Outcomes.nct_id will link outcomes to their related study.

  • Every table has the primary key: id. (Studies is the one exception since it's primary key is the unique study identifier assigned by nct_id.)
  • Columns that end with _date contain date-type values.
  • Columns that contain month/year dates are saved as character strings in a column with a _month_year suffix. A date-type estimate of the value (using the 1st of the month as the 'day') is stored in an adjacent column with the _date suffix. (This applies to date values in the Studies table.)
  • Derived/calculated value are stored in the Calculated_Values table.

While we tried to rigorously adhere to these conventions, reality occassionally failed to cooperate, so compromises were made and exceptions to these rules exist. For example, to limit duplicate verbiage, we preferred the table name References over Study_References, however the word 'References' is a PostgreSQL reserved word and cannot be used as a table name, so Study_References it is.

How are arms/groups identified?

Considerable thought went into how to present arm and group information to facilitate analysis by simplifying naming and data structures while retaining data fidelity. NLM defines groups/arms this way:

  • Arm: A pre-specified group or subgroup of participant(s) in a clinical trial assigned to receive specific intervention(s) (or no intervention) according to a protocol.
  • Group: The predefined participant groups (cohorts) to be studied, corresponding to Number of Groups specified under Study Design (for single-group studies.

In short, observational studies use the term ‘groups’; interventional studies use ‘arms’, though for the purpose of analysis, they both refer to the same thing. Because 'group' is more intuitive to the general public, AACT standardized on the term 'group(s)' and does not use the term 'arms'.

Participant Groups: Registry vs Results

When a study is registered in, information is entered about how the study defines partipant groups. In AACT, this information is stored in the Design_Groups table, while info about actual groups that is entered after the study has completed is stored in the Result_Groups table. (AACT has not attempted to link data between these 2 tables.)

Result information, for the most part, is organized in by participant group. Result_Contacts & Result_Agreements are the only result tables not associated with groups. This section describes how AACT has structured group-related results data.

AACT provides four general categories of result information:

  • Participant Flow (Milestones & Drop/Withdrawals)
  • Baselines
  • Outcomes
  • Reported Events

The Result_Groups table represents an aggregate list of all groups associated with these result types. All result tables (Outcomes, Outcome_Counts, Baseline_Measures, Reported_Events, etc.) relate to Result_Groups via the foreign key result_group_id.

For example, Outcomes.result_group_id = assigns an identifier to each group/result that is unique within the study. The identifier includes a leading character that represents the type of result (B for Baseline, O for Outcomes, R for Reported Event, and P for Participant Flow) followed by a number that uniquely identifies the group in that context. To illustrate... Study NCT001 had 2 groups: experimental & control, and reported multiple baseline measures, outcome measures, reported events and milestone/drop-withdrawals for each group. The following table illustrates how the Result_Groups table organizes the group information received from in this case:

id nct_id result_type ctgov_group_code group title explanation
1 NCT001 Baseline B1 Experimental Group All Baseline_Measures associated with this study's experimental group link to this row.
2 NCT001 Baseline B2 Control Group All Baseline_Measures associated with this study's control group link to this row.
3 NCT001 Outcome O2 Experimental Group All Outcome_Measures associated with this study's experimental group link to this row.
4 NCT001 Outcome O1 Control Group All Outcome_Measures associated with this study's control group link to this row.
5 NCT001 Reported Event E1 Experimental Group All Reported_Events associated with this study's experimental group link to this row.
6 NCT001 Reported Event E2 Control Group All Reported_Events associated with this study's control group link to this row.
7 NCT001 Participant Flow P1 Experimental Group All Milestones & Drop_Withdrawals associated with this study's experimental group link to this row.
8 NCT001 Participant Flow P2 Control Group All Milestones & Drop_Withdrawals associated with this study's studies control group link to this row.

Notice that the integer in the code provided by (ctgov_group_code) is often the same for one group across the different result types, but this is not always the case. In the example above, B1, E1 & P1 all represent the 'experimental group', so you're tempted to think that '1' equates to to the 'experimental group' for this study, however for Outcomes, O1 represents the control group. In short, the number in the ctgov_group_code often links the same group across all result types in a study, but for about 25% of studies, this is not the case, so it can't be counted on to indicate this relationship. (We had hoped to use a single row in Result_Groups to uniquely represent a participant group in the study and link all related results data (from the various tables) to that one row, however this was not possible. Therefore, one group will typically be represented multiple times in the Result_Groups table: once for each type of result data.

Information about dates has historically provided the month/year (without day) for several date values including start date, completion date, primary completion date and verification date. Because the 'day' was not provided, AACT stored these dates in the Studies table as character-type rather than date-type values. Character-type dates are of limited utility in an analytic database because they can't be used to perform standard date calculations such as determining study duration or the average number of months for someone to report results or identifying studies registered before/after a certain date.

NLM recently reported that will start providing full date values (mm/dd/yy) for these date elements, however this only applies to new studies; pre-existing studies will continue to have only month/year date values. We considered various alternatives to handle dates given this issue. We decided to provide 2 columns in the Studies table for each date element: 1) a character-type column that displays the value exactly as it was received from & 2) a date-type column that can be used for date calculations. If the date received from has only month/year, in order to convert the string to a date, it is assigned the first day of the month. For example, a study with start date June, 2014 will have June, 2014 in the start_month_year column and 06/01/14 in the start_date column.

Information about trial sites (Facilities and Countries)

Information about organizations where the study is/was conducted (aka. facilities, trial sites) is stored in the Facilities table. This represents the facility information that was included in the study record on the date that information was downloaded from

The name and email/phone for the contact person (and optionally, a backup contact) at a facility is available if the facility status (Facilities.status) is ‘Recruiting’ or ‘Not yet recruiting’, and if the data provider has provided such information. This information is stored in AACT in the Facility_Contacts table, which is a ‘child’ of the Facilities table. Facility-level contact information is not required if a central contact has been provided. Contact information is removed from the publicly available content at (and therefore from AACT) when the facility is no longer recruiting, or when the overall study status (Studies.overall_status) changes to indicate that the study has completed recruitment.

Similarly, the names and roles of investigators at the facility are available if the facility status (Facilities.status) is ‘Recruiting’ or ‘Not yet recruiting’, and if the data provider has provided such information. This information is stored in AACT in the Facility_Investigators table, which is a ‘child’ of the Facilities table. Facility-level investigator information is optional. Facility-level investigator information is removed from the publicly available content at (and therefore from AACT) when the facility is no longer recruiting, or when the overall study status (Studies.overall_status) changes to indicate that the study has completed recruitment.

AACT includes a Countries table, which contains one record per unique country per study. The Countries table includes countries currently & previously associated with the study. The removed column identifies those countries that are no longer associated with the study. NLM uses facilities information to create a list of unique countries associated with the study. In some cases, data submitters subsequently remove facilities that were entered when the study was registered. Naturally these will not appear in AACT's Facilities table. If all of a country’s facilities have been removed from a study, NLM flags the country as ‘Removed’ which appears in AACT as Countries.removed = true.

The reasons facilities are removed are varied and unknown. A site may have been removed because it was never initiated or because it was entered with incorrect information. The recommended action for sites that have completed or have terminated enrollment is to change the enrollment status to “Completed” or “Terminated”; however, such sites are sometimes deleted from the study record by the responsible party. Data analysts may consider using Countries where removed is set to true to supplement the information about trial locations that is contained in Facilities, particularly for studies that have completed enrollment and have no records in Facilities.

Users who are interested in identifying countries where participants are being/were enrolled may use either the Facilities or Countries (where Countries.removed is not true) with equivalent results.

MeSH terms in Browse_Conditions and Browse_Interventions

When data submitters provide information to about a study, they’re encouraged to use Medical Subject Heading (MeSH) terminology for interventions, conditions, and keywords. The Browse_Conditions and Browse_Interventions tables contain MeSH terms generated by an algorithm run by NLM. The NLM algorithm is re-run nightly on all studies in the database, and sources the most up-to-date information in the study record, the latest version of the algorithm, and the version of the MeSH thesaurus in use at that time.

“Delayed Results” data elements are available in AACT

A responsible party of an applicable clinical trial may delay the deadline for submitting results information to for up to two additional years if one of the following two certification conditions applies to the trial:

  • Initial approval: trial completed before a drug, biologic or device studied in the trial is initially approved, licensed or cleared by the FDA for any use.
  • New use: the manufacturer of a drug, biologic or device is the sponsor of the trial and has filed or will file within one year, an application seeking FDA approval, licensure, or clearance of the new use studied in the trial. A responsible party may also request, for good cause, an extension of the deadline for the submission of results.

Studies for which a certification or extension request have been submitted include the date of the first certification or extension request in the data element: Studies.received_results_disposit_date.

In general, the content that is contained in the AACT database preserves the content in the source XML files that are downloaded from