The Substance Abuse Treatment to HIV Care II (SAT2HIV-II) Project: Complete Statistical Analysis

1. Trial at a Glance

This page covers the registry results for The Substance Abuse Treatment to HIV Care II (SAT2HIV-II) Project (NCT04687917), a randomized na study. The primary outcome is Staff-level Implementation Consistency.

2. Clinical Question

This is an implementation-strategy question: the primary measure concerns staff delivery of the brief intervention, not a direct measure of clients’ substance use. The registry record also lists client-related outcomes, including changes in days using the primary substance and in generalized anxiety symptoms. Numerical results for the primary and secondary outcomes are not reported in the registry record, so the direction and precision of any difference between strategies cannot be described from the record.

3. Trial Design

The Substance Abuse Treatment to HIV Care II (SAT2HIV-II) Project is registered as a randomized, parallel-group behavioral study. The registry describes it as cluster-randomized, so the assignment is at a cluster level rather than a simple assignment of each individual participant independently. The identities of the randomization clusters and the number of clusters are not reported in the registry record.

The comparison is between facilitation, training, feedback, and consultation (FTFC) and an enhanced strategy that adds incentivization (FTFCI). The registry summary describes the incentivization as monetary bonuses to staff tied to predefined performance targets. The record labels masking as single, but does not identify who was masked. The intervention period, the precise procedures used to deliver each strategy, and the allocation ratio are not reported in the registry record.

Enrollment is recorded as 428. This is the registry enrollment figure, not a reported count for each arm or a count of participants included in an outcome analysis. The study start date is 2021-01-14, and the primary completion date is 2023-04-30. The status is listed as active, not recruiting.

Cluster randomization matters when interpreting the design: participants within a cluster may have more similar outcomes than participants in different clusters. An analysis should account for that dependence to avoid treating correlated observations as independent. The registry record notes that a simple individual-level re-analysis would be misleading and that only the sponsor’s own analysis is shown. The statistical model and details of that sponsor analysis are not reported in the registry record.

4. Participant Flow and Accounting

The registry reports how participants moved through each stage of the study. All counts below are exactly as posted; missing counts are not inferred from other stages.

Overall Study

5. Baseline Characteristics

The table reproduces the baseline characteristics posted in the registry, which describe the participants analysed at baseline and help show whether the randomized groups were comparable.

Population: This study includes cluster-randomization of both staff participants and client participants. For each of the two implementation strategy conditions we have separated staff participants from client participants.

6. Primary Endpoint

The registry lists the primary outcome as Staff-level Implementation Consistency, measured over Assessed at the end of month 12.

The primary endpoint is staff-level implementation consistency. It is defined as the cumulative number of brief interventions that each HSO staff participant implemented with HSO client participants during the implementation phase. The measure is assessed at the end of month 12 and is summarized as a mean with standard deviation.

This endpoint is used to represent whether the implementation strategy is associated with staff delivery of the intervention in practice. It focuses on implementation activity, rather than measuring whether clients’ substance use or other health outcomes changed. The record describes the brief intervention as motivational interviewing-based and directed at substance use.

Because the endpoint is a count of interventions, its distribution may not follow the assumptions of methods designed for continuous measurements with symmetric, normally distributed errors. Counts can be concentrated at lower values, have a long upper tail, or show more variability than a basic model expects. These are general considerations, not claims about the observed endpoint distribution in this trial; distributional details are not reported in the registry record.

The registry record does not report the endpoint mean, standard deviation, between-strategy estimate, confidence interval, or p-value. Without those results, the size and precision of any difference in implementation consistency cannot be assessed.

7. Why No Re-analysis Is Shown

8. Statistical Interpretation

9. Statistical Methods Explained

Why does the cluster-randomized design matter?

In an individually randomized design, each participant is assigned independently. In a cluster-randomized design, groups of participants are assigned together. People within the same group may share staff, setting, or implementation conditions, so their outcomes may be more alike than outcomes from different groups. This dependence is called within-cluster correlation.

If correlated observations are analyzed as though they were independent, the analysis can overstate the amount of independent information and understate uncertainty. Appropriate methods account for the cluster structure, for example through a model or a cluster-level analysis. Which specific method was used for the sponsor’s analysis is not reported in the registry record. The cluster identities, number of clusters, and degree of within-cluster correlation are also not reported.

What does a mean and standard deviation describe?

The primary endpoint is specified as a mean with standard deviation. A mean describes the average outcome in a group. The standard deviation describes how spread out individual observations are around that average. These are descriptive summaries; they do not, by themselves, quantify the uncertainty in a comparison between strategies. A standard error or confidence interval for the comparison would address uncertainty in the estimated contrast, but these quantities are not reported in the registry record.

The endpoint is a cumulative count of brief interventions. General statistical considerations for count outcomes include whether the data have many low values, whether a small number of participants have high counts, and whether variability exceeds what a selected model assumes. Such features can affect model choice and uncertainty estimates. The observed distribution and the sponsor’s modeling choices are not reported in the registry record, so no particular distribution or model can be attributed to this study.

How should an estimated contrast be read?

A between-strategy contrast would quantify how the outcome differs between FTFCI and FTFC, according to the chosen coding and analysis. The estimate would describe the observed contrast under that analysis; a confidence interval would show its uncertainty. Whether a result is statistically distinguishable from a null value is not the same question as whether its size is important for implementation. Both the estimated magnitude and its uncertainty matter. No primary contrast or confidence interval is reported in the registry record.

For a cluster-randomized study, the validity of that uncertainty depends in part on recognizing the assignment structure. The registry notes that a simple individual-level re-analysis would be misleading and that only the sponsor’s own analysis is shown. The record does not report enough analytic detail to independently assess the model, assumptions, or handling of clustering.

What can planning calculations tell readers?

Sample-size planning asks how much information might be needed to detect an effect under stated assumptions. The planning approach described for this study uses a two-sided significance level of 0.05, equal allocation between the two arms, and a normal approximation; the effect to detect is framed as a stated fraction of the observed effect. These are planning assumptions, not a report of how the trial was actually designed. The registry record says the calculations are planning illustrations rather than the trial’s own design.

For a cluster-randomized study, planning also depends on the clustering structure and other assumptions about the outcome. The record does not report a sample-size justification for the trial, the assumptions used for its original design, or whether the planning illustration incorporates clustering. Any illustrated participants-per-arm values should therefore be read as scenario-based planning figures, not as observed sample sizes or evidence of observed power. Observed power is not a substitute for reporting the effect estimate and its uncertainty.

What does the absence of an analysis count imply?

The registry record reports zero analyses. This means the record does not provide a reported analysis entry to interpret; it does not establish that no analyses were conducted outside the registry. The statistical analysis plan, model specification, covariate adjustment, handling of the cluster structure, and inferential results are not reported in the registry record. Without these details and the outcome estimates, readers cannot assess the sponsor analysis beyond the design information recorded.

10. Confidence Intervals for Each Arm

No two-arm comparison is shown for this trial, but each arm's mean can be given with a t-based 95% confidence interval computed from the posted mean, spread and number of participants.

R code and output

arm <- c("Facilitation, Training, Feedback, and Consultation", "Facilitation, Training, Feedback, Consultation, an")
n   <- c(44, 43)
m   <- c(0.73, 2.35)
sp  <- c(1.55, 6.67)
sd  <- sp      # posted standard deviations
for (i in seq_along(n)) {
  se <- sd[i] / sqrt(n[i]); h <- qt(0.975, n[i] - 1) * se
  cat(sprintf("CARM|%s|%d|%.3f|%.3f|%.3f|%.3f\n", arm[i], n[i], m[i], sd[i], m[i] - h, m[i] + h))
}

CARM  Facilitation, Training, Feedback, and Consultation  44  0.730  1.550  0.259  1.201
CARM  Facilitation, Training, Feedback, Consultation, an  43  2.350  6.670  0.297  4.403

11. Multiplicity, Missing Data and Analysis Populations

The registry record lists four outcome measures. It identifies staff-level implementation consistency as the primary outcome and names secondary outcomes concerning client participants’ change in days using their primary substance and change in GAD-7 score. The record does not report the full analytic details for all listed outcomes or whether any correction or other strategy was used to address multiple comparisons.

Multiplicity is a general concern when several outcomes or contrasts are examined: the chance of at least one apparently unusual result can increase as the number of tests grows. A prespecified hierarchy, adjustment procedure, or clear separation of primary and exploratory analyses can help readers interpret results. The registry record does not report such a plan, so no claim about multiplicity control can be made.

Missing-data details are also not reported in the registry record. The record does not state how many participants contributed primary-outcome data, whether missingness differed by strategy, why observations might be missing, or how missing values were handled. These details matter because the analyzed participants may not represent all enrolled participants if outcome availability is related to intervention delivery or participant characteristics.

Analysis populations and the treatment of participants who did not follow the assigned strategy are not reported in the registry record. The record also does not specify whether analyses followed assignment regardless of adherence. These omissions limit assessment of how the analysis population was defined and how robust the findings would be to missing observations or deviations from assignment.

12. Safety Results

The registry reports serious adverse events as affected participants divided by participants at risk.

Deaths

Other (non-serious) adverse events

Participants with at least one non-serious event at or above the registry's 0% reporting threshold.

The registry reports serious adverse events and other adverse events separately for staff and client groups in each strategy. For FTFC staff, 44 were at risk and 0 serious events, 0 other events, and 0 deaths were recorded. For FTFC clients, 117 were at risk and the corresponding figures were 0, 0, and 0. For FTFCI staff, 43 were at risk and the corresponding figures were 0, 0, and 0. For FTFCI clients, 224 were at risk and the corresponding figures were 0, 0, and 0.

These are the event counts recorded for the listed groups; zero recorded events do not prove that the underlying risk is zero. The record does not report the adverse-event definitions, observation periods, completeness of event collection, or how the at-risk counts relate to the primary-outcome analysis population. Staff and client groups also represent different participant categories and should not be combined casually. These safety counts do not provide evidence about the primary implementation-consistency outcome.

13. What the Result Does, and Does Not, Mean

The registry record defines a randomized comparison of FTFC with FTFCI, an implementation strategy that adds incentivization, and identifies staff-level implementation consistency as the primary endpoint. It also gives the endpoint’s meaning and assessment time. Those design and measurement details clarify what the trial was intended to examine.

The record does not report numerical results for the primary endpoint. It therefore cannot show whether the mean number of brief interventions differed between strategies, how large any difference was, or how precisely it was estimated. It also cannot establish a result for the client-level secondary outcomes. The absence of reported numerical results is not evidence that the strategies had identical outcomes, nor does it establish that one strategy was better.

Even a reported difference in the primary endpoint would concern staff implementation consistency as defined in the record. It would not, by itself, demonstrate a change in clients’ substance use, anxiety symptoms, or other outcomes. Those questions require their own outcome estimates and uncertainty. No medical advice or conclusion about treatment effectiveness follows from the endpoint description alone.

Because the study is cluster-randomized, the analysis must reflect the cluster structure for uncertainty to be credible. The record flags the problem with a simple individual-level re-analysis but does not provide the statistical details needed to evaluate the sponsor analysis. Enrollment is 428, but the analyzed sample for any endpoint is not reported. Thus the design information does not resolve questions about outcome completeness or analytic precision.

The adverse-event entries record zero serious events, zero other events, and zero deaths in each listed group. These registry counts should be read as recorded observations, not as proof that events are impossible or that every participant was observed in the same way. Overall, the record supports description of the trial’s purpose, comparison, and endpoint, but not a conclusion about the numerical result.

14. Why This Trial Matters Statistically

This trial addresses a statistical distinction that is important in implementation research: the intervention being compared is a strategy for supporting staff delivery, and the primary outcome measures implementation activity. That distinction helps prevent a staff-level process measure from being mistaken for a direct client health outcome. The registry also lists client outcomes, but those require separate estimates and interpretation.

The cluster-randomized design is statistically consequential. When assignment occurs at the group level, the effective information depends not only on the number of individual participants but also on the cluster structure and similarity of outcomes within clusters. A conventional individual-level analysis that ignores clustering can give misleading uncertainty. The registry specifically flags that risk and directs attention to the sponsor’s own analysis, while leaving its details unreported.

The primary measure is a count of interventions, making the form and spread of the outcome relevant to model choice. Means and standard deviations describe average level and variation, but a comparison also needs an estimate of uncertainty that reflects both the outcome distribution and clustering. No numerical endpoint result or inferential measure is reported in the registry record, so these statistical considerations cannot be resolved from the recorded results.

Finally, transparent reporting of the analysis population, missing data, multiplicity handling, and model would help readers judge the strength and scope of any findings. These details are not reported in the registry record. The trial’s design is therefore informative about the question and structure of the comparison, while the lack of numerical results and analytic detail limits statistical interpretation.

15. Limitations

• The posted summary statistics are the only data these results rest on; patient-level data, full protocols and statistical analysis plans are not available.
• Recalculated results are simple, unadjusted calculations from posted summaries. They do not replace the sponsor's prespecified analysis.

The principal limitation for interpretation is that the registry record does not report numerical results for the primary endpoint. Group summaries, an estimated contrast, confidence interval, and p-value are not reported. The record also does not provide numerical findings for the listed secondary outcomes. Consequently, the magnitude, direction, and precision of the trial’s outcome comparisons cannot be assessed.

The cluster-randomized design raises an additional interpretive limitation because the cluster identities, number of clusters, and statistical handling of clustering are not reported. The registry warns that simple individual-level re-analysis would be misleading, but the sponsor analysis details are not reported. The randomization unit and allocation ratio are not specified.

Enrollment is recorded as 428, but the number analyzed for the primary endpoint, the distribution of participants across groups for analysis, and any exclusions are not reported. Missing-data methods, reasons for missing observations, analysis populations, and adherence to assigned strategies are also not reported. These gaps prevent assessment of attrition and of how the analyzed sample relates to enrollment.

The record identifies four outcome measures but does not report whether multiplicity was addressed or provide a complete analysis plan. It does not identify who was masked despite labeling the study single-masked. Further details about eligibility, intervention delivery, event definitions, and adverse-event observation are not reported in the registry record. These are reporting limitations; they should not be interpreted as evidence that the trial necessarily lacked such procedures.

16. Related Tutorials

17. Related Statistical Calculators

18. Sources

• ClinicalTrials.gov: The Substance Abuse Treatment to HIV Care II (SAT2HIV-II) Project — NCT04687917.
• Registry record last updated 2025-11-13; status last verified 2025-10.
• Results first posted 2025-05-14.
• Data retrieved from ClinicalTrials.gov on 2026-11-09.
• Group sizes, means, event counts and sponsor-reported p-values are reproduced as posted. Effect estimates, confidence intervals and p-values not attributed to the sponsor are independently calculated from the posted summary statistics.

19. Record Summary

The Substance Abuse Treatment to HIV Care II (SAT2HIV-II) Project is registered as NCT04687917 and sponsored by Ohio State University. It is a randomized, parallel-group behavioral study described as cluster-randomized. The record lists enrollment of 428 and status as active, not recruiting.

The comparison is between FTFC and FTFCI, which adds incentivization to facilitation, training, feedback, and consultation. The primary outcome is staff-level implementation consistency, measured as the cumulative number of brief interventions implemented with HSO client participants and assessed at the end of month 12.

The study start date is 2021-01-14, and the primary completion date is 2023-04-30. Numerical primary and secondary outcome results, the sponsor’s detailed statistical analysis, missing-data handling, and multiplicity procedures are not reported in the registry record.