Compare clinical protocol amendments offline on Windows
Practice a source-linked amendment comparison with fictional study documents. Track changed text and exceptions without making patient or treatment decisions.
A protocol amendment review should identify changed wording, retain exceptions, and point the study team to the controlling source. Use AI only as a reading aid within an approved process. It must not determine patient eligibility, prescribe a dose, or replace clinical judgment.
The question this exercise answers
The BioVance pack is entirely fictional. Its thresholds, drug identifier, and schedules exist only to test text comparison. Do not apply any of them to a person or an actual study.
Download the fictional records
Download the separate records as a ZIP, extract it, and import the TXT files individually:
- Record 1: Clinical study protocol — protocol version 2.1
- Record 2: Clinical study protocol — protocol amendment 3.0
The combined reading copy remains available. Import either the separate files or the combined copy, not both. Question Scope selects whole imported Documents; headings such as “Record 1” inside a single TXT file cannot be selected independently. Use the separate files for this walkthrough.
These are fictional teaching records, including any future dates, statute references, and professional opinions. They are not authentic filings, standards, advice, or a benchmark of OriginPage’s answer quality.
Locate the passages before asking for a comparison
Create a separate Workspace for the exercise. Import the individual records and wait for each to show Ready. Open Document details and check the retained text. These TXT exercises do not demonstrate PDF layout extraction or OCR.
In Search, try ULN in Exact phrase mode, without adding quotation marks. Search each relevant file as well as the collection. If wording differs, try Keyword or Hybrid and inspect the returned passages. A missing result is a reason to check wording, scope, and extraction—not proof of absence.
Choose the records allowed to answer
Select record-01.txt and record-02.txt, the two independently imported protocol versions. In Chat, use Answering from → Selected documents. Search filters and Question Scope are separate controls; setting one does not set the other.
Try this focused question:
Compare section 4 in the two fictional protocol versions. List changed wording, units, exceptions, and the supporting passages. Do not assess a participant or give clinical advice.
Check the result against the source
The following is an editorial answer key derived from the fictional files, not a recorded model response. Answers may omit relevant evidence; use Direct Search and the original records to complete the review.
| Text-review check | Expected difference in the fictional files |
|---|---|
| Timing of laboratory documentation | Section 4.1 changes fourteen days to seven days. |
| Hepatic threshold wording | The general AST/ALT threshold changes, while record 2 retains a separate exception for documented hepatic metastases. Keep the exception attached. |
| Prior-therapy window | The written interval changes from 28 to 42 days. |
| Safety reporting | Section 7.3 changes the stated window and expands the described events and recipients. Compare all fields, not just the number. |
Search for ULN or for the spelled-out term separately: the two versions use different wording. An exact search for “AST and ALT” would not match every relevant occurrence in the baseline. Verify symbols, units, superscripts, and exceptions against the original document, especially after OCR.
Keep a review record
Prepare an amendment log with old text, new text, affected section, effective version, implementation question, and reviewer sign-off. Use the validated study-document process for final records. OriginPage is not presented here as a validated clinical decision system.
When a question needs two sides, open evidence from both. Check the filename, retained passage, surrounding conditions, and the original source where layout matters. A saved citation supports inspection; it does not certify the source or the conclusion.
Processing and professional boundaries
HIPAA does not require all processing to be local: HHS describes conditions for using cloud providers, including applicable business associate agreements and safeguards. Local use also needs an appropriate assessment of access, storage, and retention. HHS cloud guidance
OriginPage processes supported documents locally during ordinary use. The privacy statement explains the limits, including Windows services and local account access. For formats and supported behavior, see what OriginPage supports.
Method
Revised September 21, 2026. The two screenshots show the downloadable fictional records imported separately into the locally installed OriginPage 1.0.35.0 candidate. We ran the stated Exact phrase query, opened the shown source passage, and applied the illustrated Selected documents scope. These captures demonstrate retrieval and scope, not generated-answer quality or professional validation. The source inspector clips part of the main pane in this candidate; the screenshots preserve that observed layout. The exercise findings are an editorial answer key, not a captured model response.