Keeping Study Design and Protocol Authoring in Step at CDISC US Interchange
At CDISC US Interchange 2026, AlphaLife Sciences explored how structured study design can carry protocol decisions into data collection and review.

A protocol describes the study a team intends to run. Its decisions also shape the visit schedule and the data the study needs to collect. At CDISC US Interchange, held October 5–6 in Denver, sessions on the Unified Study Definitions Model (USDM) and digital study design examined how structured definitions can carry that intent across systems. At Booth 19, AlphaLife Sciences focused on the authoring side of the same handoff. View the conference program and our event page.
The CDISC 360i plenary used progression-free survival to illustrate how one endpoint can connect study design, data collection, analysis, and submission. The program showed how a structured schedule of activities can link visits and assessments to the data definitions a downstream team receives. That example gave the authoring discussion a concrete starting point. A protocol section can explain a decision in language that study teams can act on, and a structured definition can help other systems carry the same decision forward.
Start with the design decision
Consider a team that revises when it will measure a primary endpoint. The change may affect the endpoint description, the schedule of activities, and the data collection instructions. Giving the decision a consistent definition makes it easier to identify where those materials refer to it and check whether they still agree.
For example, if an assessment moves to a different visit, the protocol author can update the schedule and identify any passages that describe the timing in prose. The data collection team can use the same revised definition to check the visit and the associated form. The study team can then confirm which changes apply and document anything that needs further review, such as an assessment window or an instruction for a missed visit.
That is where AI can help with protocol authoring. An author can use agreed study inputs to draft relevant sections and flag passages that may need review when an input changes. Study and data experts still decide what the change means for the protocol and the work that follows.
Check what survives the handoff
One way to evaluate a standards-aware workflow is to follow a single protocol amendment. Can a reviewer trace the amendment back to the design decision, identify the affected materials, and check that each team is working from the same definition? Those checks show where structured study information is already doing its job and where the handoff still depends on someone copying or interpreting it.
Follow the amendment into data collection
Give the protocol and data teams the same approved amendment and ask each team to show where it took effect. For the writer, that may be the endpoint description and the schedule of activities. For the data team, it may be a revised form specification or a change to the expected visit. Comparing those outputs can reveal an ambiguity while there is still time to resolve it.
Record the version each team used, the materials that needed revision, and the decisions reviewers made about exceptions. The resulting record gives the next person a way to check how the design was translated into operational instructions. It also gives the team a practical test for any authoring tool that claims to support a connected workflow.
Thank you to CDISC and the clinical research community for convening the discussion in Denver. Talk with AlphaLife Sciences about connecting study design and protocol authoring in your workflow.


