Two registers, one trial
Use secondary IDs to avoid counting two independent observations.
In-depth practical guides
Connect protocol, history, posted results and publications without counting one trial twice.
Updated :

AI-generated illustration
A register describes a study and updates. It may list objectives and recruitment without reporting results. ICTRP gathers registers: an aggregate and its original register may describe one trial.
Record the original registry ID, secondary IDs and sponsor. A similar title is insufficient as a key; inspect links between registrations.
Separate registration, planned or actual start and completion, and last update. When history exists, compare primary outcomes and planned enrolment across versions.
Locate protocol, posted results and article separately. Link the article through the trial ID and check population, intervention and period before attributing its results.
Reading workshop
Fictional file DEMO-T18 compares protocol versions without a medical conclusion.
Fictional data and records for learning: none of these results comes from a live service query.
v1 is dated 1 March; v2, 15 July. Recorded start is 20 June. The history shows a change but does not by itself establish its reason.
If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.
| Step | Evidence or value | Reading | Decision |
|---|---|---|---|
| Study identity | DEMO-T18 in both versions | One tracked study file. | Retain identifier and v1/v2 documents. |
| Eligibility criterion | v1: ages 18–65; v2: 30–65 | Declared eligible population changes. | Record the date and seek the protocol explaining the amendment. |
| Primary endpoint | Score S at 8 weeks, then 12 weeks | Measurement timing differs. | Cite definition and timing with version; do not treat it as unchanged. |
| Available results | No score S value in the file | No effect direction established. | Seek posted results and linked publications without inventing conclusions. |
Open each proposition to compare its diagnosis. More checks may still be needed.
No: absence in this file does not establish result direction.
No: a scheduled time is not an observed value.
Appropriate. Read protocol and results without a treatment recommendation.
File: DEMO-T18; invented identifier v1: 1 March; ages 18–65; score S at 8 weeks Recorded start: 20 June v2: 15 July; ages 30–65; score S at 12 weeks Amendment reason and effect: to document Score results: absent from supplied documents Conclusion: protocol change, not a result
Attach version, population and measurement timing when citing the endpoint. Separate start date, amendment date and results consultation date.
Use secondary IDs to avoid counting two independent observations.
Describe displayed status and available results; do not infer positive or negative outcomes from missing results.
Worked exercise
Fictional example: the values and documents teach the method and do not describe a real organisation.
All information concerns the same fictional record. Determine what can be calculated and what remains unknown.
If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.
| Field | Observed information |
|---|---|
| Planned participants | 80 |
| Enrolled participants | 60 |
| Recruitment status | Finished |
| Primary-outcome result | Unavailable in the records consulted |
Enrolled participants represent 75% of the stated target. This measures recruitment, not intervention effectiveness. Recruitment status and unavailable results establish neither clinical benefit nor clinical failure.
For results published elsewhere, check trial ID, protocol, analysed population and version before linking them.
Keep IDs, qualified counts, status, outcomes, versions and actually consulted results.
Documentation reference : WHO — Trial Registration Data Set · Consulted on
No: return to the original register and look for results documents and linked publications.
It describes study progress, not conclusions or the presence of an article.
To identify the changes of information useful in reading. Differences must be described and contextualized, without automatically concluding their cause or effect on the results.
TOOLS / REGISTERS
Locate protocol, posted results and article separately. Link the article through the trial ID and check population, intervention and period before attributing its results.
DOCUMENTED REFERENCE
These ClinicalTrials.gov API fields belong to identificationModule and statusModule inside protocolSection. They distinguish identification, study conduct and publication; not all describe a medical event.
| Reference | Value or form | What it identifies |
|---|---|---|
| nctId | NCT + 8 | NCT followed by eight digits: the registry identifier, distinct from the sponsor’s internal number. |
| studyFirstPostDateStruct | date | First record availability after NLM quality review; not the study start. |
| primaryCompletionDateStruct | date + type | Completion of data collection for primary outcomes, with estimated or actual type. Precision may be month-only. |
| resultsFirstPostDateStruct | date | First availability of summary results after quality review; some may appear earlier with QC comments. |
| lastUpdatePostDateStruct | date | Latest publication of record changes, different from their submission date. |
Keep field names, version and precision. Do not invent a day for a month-only date. Quality review and an NCT do not establish efficacy, safety or treatment approval.
No. Completion of collection, results submission and publication are separate events. Check the results posting field and any QC comments. The last update may concern another part of the record.
Documentation consulted on .
DEEPER READING / PRACTICE
A register describes a study and its protocol. Reading focuses on what is recorded, the available versions and the possible results published, without transforming the recording into a demonstration of effectiveness.
Updated on .
Release identifier, title, promoter, calendar, status and criteria indicated. Compare the version consulted with the documents or results to which it references.
An announced protocol does not prove the completion of the study or its outcome. Dates and statutes can describe different steps and require careful reading.
The reading sheet indicates version, dates, status, announced elements and links to the available results. The conclusions remain limited to the documentation actually consulted.