This page provides an independent statistical analysis and educational interpretation of publicly reported results. ClinicalTrials.gov provides the official trial registry record. Numerical trial results on this page are restricted to the results posted in the ClinicalTrials.gov record; calculations added by Clinical Biostats are labelled as such.
1. Trial at a Glance
This page covers the registry results for RPS InflammaDry Detector™ to Determine MMP-9 Levels in Tears (NCT01313351), a registered phase not stated study. The primary outcome is Sensitivity and Specificity of InflammaDry Detector Compared to Clinical Assessment at Confirming a Diagnosis of Dry Eyes..
| Feature | Registry value |
|---|---|
| ClinicalTrials.gov identifier | NCT01313351 |
| Phase | Phase not stated |
| Condition | Dry Eye |
| Allocation | Not Stated |
| Design model | Not Stated |
| Masking | Not Stated |
| Enrollment | 206 |
| Arms in the primary outcome | n/a |
| Lead sponsor | Rapid Pathogen Screening |
| Results posted | Yes |
2. Clinical Question
Population
The record concerns patients assessed for signs and symptoms of Dry Eye. Enrollment was 206. The primary-outcome description names OSDI (Ocular Surface Disease Index), TBUT (Fluorescein Tear Break-up Time), corneal fluorescein staining and Schirmer Tear Test as components of the clinical assessment. The registry record does not report further eligibility details or a fuller description of the population used for the primary assessment.
Intervention
The device was the RPS InflammaDry Detector™. The brief summary describes its intended use as detecting elevated MMP-9 in human tears to aid diagnosis alongside other methods of clinical evaluation. The arm description says tears were collected from subjects for application to the detector and that subjects were clinically evaluated. The record does not report additional procedural details.
Comparator
The comparison was the clinical assessment for dry eye, rather than a separate randomized control group. The listed clinical methods were OSDI, TBUT, corneal fluorescein staining and Schirmer Tear Test. The registry record does not report how results from those methods were combined to define the clinical assessment or whether a particular threshold determined a positive or negative clinical classification.
Primary question
The primary question was how well the detector's results agreed with clinical assessment when confirming a diagnosis of dry eyes, described through sensitivity and specificity. Sensitivity is defined in the record as the percentage of true positive cases correctly identified by the test compared with clinical assessment. Specificity is the percentage of true negative cases correctly identified. The outcome timeframe was 15 minutes. The registry record does not report the estimated sensitivity or specificity, their confidence intervals, or the underlying counts.
3. Trial Design
This completed clinical evaluation is listed under the title “RPS InflammaDry Detector™ to Determine MMP-9 Levels in Tears.” Its official title describes evaluating the detector's sensitivity and specificity compared with clinical diagnosis for confirming dry eyes. The sponsor was Rapid Pathogen Screening. The record lists the study start as 2010-11 and primary completion as 2011-10, with status COMPLETED.
The intervention was a device, the RPS InflammaDry Detector™. The arm description is “Device testing”: tears were collected from subjects for application to the detector, and subjects were clinically evaluated. The primary measure compared detector results with clinical assessment, which included OSDI, TBUT, corneal fluorescein staining and Schirmer Tear Test. The specified timeframe was 15 minutes.
The record explicitly indicates that this was not a randomized comparison and that allocation was not stated. It also cautions that the arms are not a like-for-like control comparison. The design should therefore be read as an evaluation of diagnostic classification against clinical assessment, not as a randomized treatment-effect comparison. The registry record does not report a separate control arm, allocation procedure, masking, test order, or whether clinical assessors were unaware of device results.
Enrollment was 206, but the registry record does not report how many participants contributed usable results to the primary measure or whether all enrolled subjects received both assessments. It lists one outcome measure and no analysis records. The protocol's sample-size justification, any planned interim analyses, and a fuller statistical analysis plan are not reported in the registry record. Those omissions limit assessment of how enrollment and the analysis were planned.
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
| Stage | Device Testing |
|---|---|
| STARTED | 206 |
| COMPLETED | 206 |
| NOT COMPLETED | 0 |
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.
| Characteristic | Unit | InflammaDry Test |
|---|---|---|
| Participants analysed | 206 | |
| Age, Continuous | years | 53 (18 to 88) |
| Sex: Female, Male: Female | Participants | 152 |
| Sex: Female, Male: Male | Participants | 54 |
| Race/Ethnicity, Customized: Race – White | Participants | 136 |
| Race/Ethnicity, Customized: Race – Black | Participants | 11 |
| Race/Ethnicity, Customized: Race – Hispanic | Participants | 49 |
| Race/Ethnicity, Customized: Race – Asian | Participants | 9 |
| Race/Ethnicity, Customized: Race – Other | Participants | 1 |
| Region of Enrollment: United States | participants | 206 |
6. Primary Endpoint
The registry lists the primary outcome as Sensitivity and Specificity of InflammaDry Detector Compared to Clinical Assessment at Confirming a Diagnosis of Dry Eyes., measured over 15 minutes.
| Element | Registry entry |
|---|---|
| Result type | Number |
| Measure of spread | 95% Confidence Interval |
| Unit | percentage of cases |
| Endpoint classification | not reduced to a single comparison |
The primary endpoint concerns sensitivity and specificity of the RPS InflammaDry Detector™ compared with clinical assessment for confirming a diagnosis of dry eyes. The clinical assessment named in the record used OSDI, TBUT, corneal fluorescein staining and Schirmer Tear Test. The stated timeframe was 15 minutes.
Sensitivity describes the proportion, expressed in the record as a percentage, of cases classified as true positive by the clinical assessment that the detector correctly identifies. Specificity describes the percentage of true negative cases correctly identified by the detector. These measures address different kinds of classification: sensitivity concerns recognition among cases deemed positive by the comparator, while specificity concerns correct negative classification among cases deemed negative. A test can perform differently on these two dimensions, so reporting both is informative.
These measures depend on the comparator's definitions. The registry record names the clinical assessment methods but does not report a detailed rule for combining their findings, thresholds for positive classification, or the clinical reference definition used for the calculations. It also does not report the actual sensitivity, specificity, confidence intervals, or counts of positive and negative classifications. Consequently, the endpoint's intended meaning is clear, but its empirical precision and observed classification performance cannot be evaluated from the registry record.
7. Why No Re-analysis Is Shown
8. Statistical Interpretation
The registry record describes a diagnostic evaluation, not a randomized comparison of treatments. Its central statistical question is whether device classifications correspond to classifications from clinical assessment. The primary measure was sensitivity and specificity, with clinical assessment serving as the stated comparator. The listed clinical methods were OSDI, TBUT, corneal fluorescein staining and Schirmer Tear Test.
The registry record does not report numerical sensitivity or specificity estimates. It names a 95% Confidence Interval as the dispersion measure, but no interval limits are reported. It also does not provide the classification counts needed to see how many results fell into true-positive, false-positive, true-negative or false-negative categories. Without estimates, intervals and counts, the degree of agreement and its precision cannot be judged. No direction or magnitude of diagnostic performance should be inferred from the study title or the fact that the study is marked completed.
In general, a confidence interval expresses uncertainty around an estimate under the analysis assumptions. A narrow interval indicates greater statistical precision than a wide interval, although precision alone does not establish that a measure is clinically meaningful. Here, the interval is part of the endpoint description, but the registry record does not report its calculated limits. The stated confidence-interval format therefore does not itself reveal how precise either measure was.
Interpretation also depends on how clinical assessment defined the reference-positive and reference-negative groups. The record lists several assessment methods but does not report their thresholds, combination rule, or handling of conflicting findings. If classification depends on such rules, a different rule can change which cases count as positive or negative and thereby affect sensitivity and specificity. This is a general feature of diagnostic-accuracy analysis, not a reported finding about this evaluation.
The record lists enrollment of 206, but this does not establish how many observations entered either endpoint calculation. The registry does not give the analysis population, the number of missing or uninterpretable results, or the denominators for sensitivity and specificity. A study's enrollment and the number contributing to a particular calculation can differ; the relevant endpoint denominators are not reported in the registry record.
The record lists no analysis records. That absence means the posted registry information does not show the statistical results or describe the analysis in detail. It does not establish that no analysis was conducted. The study status is COMPLETED, but completion status is not a substitute for outcome estimates. The appropriate interpretation is limited to the planned comparison and the endpoint definitions that are documented, while recognizing that the numerical evidence needed to judge accuracy and uncertainty is not reported in the registry record.
9. Statistical Methods Explained
The endpoint uses two diagnostic-accuracy measures: sensitivity and specificity. In general, each compares a test's classification with a reference classification. For this evaluation, the record identifies clinical assessment as the comparator and the RPS InflammaDry Detector™ as the test under evaluation. The clinical methods listed are OSDI, TBUT, corneal fluorescein staining and Schirmer Tear Test.
What sensitivity describes
In general, sensitivity is the share of reference-positive cases that the test also classifies as positive. It addresses detection among cases considered positive by the reference assessment. If sensitivity is lower, more reference-positive cases have test results that do not identify them as positive. The registry record defines sensitivity as the percentage of true positive cases correctly identified by the test compared with clinical assessment. No sensitivity estimate or classification count is reported, so the measure's observed level cannot be described.
What specificity describes
In general, specificity is the share of reference-negative cases that the test also classifies as negative. It addresses correct negative classification among cases considered negative by the reference assessment. The registry record defines specificity as the percentage of true negative cases correctly identified compared with clinical assessment. No specificity estimate or count of reference-negative cases is reported. The endpoint title's inclusion of both measures signals that the evaluation considered positive and negative classification, but does not disclose the resulting performance.
Why the comparator definition matters
Diagnostic-accuracy measures rely on a clear reference definition. Here, clinical assessment is the comparator, and the description names four assessment methods. The registry record does not explain whether those methods were combined into a single rule, whether each contributed separately, or what thresholds were used. It also does not describe how disagreements among clinical findings were handled. In general, changing the reference definition can change the classification groups against which sensitivity and specificity are calculated. This is important when interpreting any diagnostic evaluation, because these values characterize agreement with the selected reference rather than an independent, error-free truth.
The registry record does not report masking or the order in which the detector and clinical assessments were performed. These are relevant design details in general: knowledge of one result can potentially influence another assessment, and order can matter when procedures or assessments are not independent. Their absence from the registry record means their role cannot be assessed for this evaluation.
Confidence intervals and precision
The endpoint description identifies a 95% Confidence Interval. In general, a confidence interval conveys statistical uncertainty around an estimate, reflecting that the estimate is based on a finite set of observations. The width of an interval helps readers assess precision: a wider interval represents more uncertainty about the estimate than a narrower interval. The interval does not by itself correct for bias in the comparator, missing data, or limitations in the study design.
Although the record names the confidence-interval format, it does not report the interval limits or the point estimates for sensitivity and specificity. It does not report the numbers of positive and negative reference classifications or the corresponding detector classifications. These omissions prevent a reader from checking the estimates, understanding their precision, or examining the pattern of misclassification. The endpoint timeframe is 15 minutes, but the registry record does not give additional details about timing beyond that designation.
Over-dispersion and diagnostic counts
In general, over-dispersion refers to greater variability in data than a chosen statistical model expects. It can matter for count or clustered data because methods that assume less variability may produce uncertainty estimates that are too small. The primary measure in this record is described as percentages of cases with confidence intervals; the registry does not describe an over-dispersion adjustment or any count model. There is no basis in the registry record to infer that an over-dispersion method was used or was needed.
Diagnostic classification can also be affected by dependence among observations or by repeated assessments. General methods account for the structure of data when it is relevant, but the registry record does not report whether there were repeated measurements, clustering, or a specific model. It is therefore not possible to evaluate those methodological choices.
Analysis plan and planning calculations
The record lists one outcome measure and no analysis records. It does not report a statistical analysis plan, estimator, confidence-interval method, missing-data procedure, or prespecified subgroup analysis. The protocol's sample-size justification is also not reported in the registry record. Any planning illustration associated with the study should be understood as a planning exercise, not as observed power or as evidence that a particular effect was detected. Such calculations cannot replace the unreported endpoint estimates and intervals.
In general, a statistical analysis plan clarifies how outcomes will be defined and analyzed before results are examined. For diagnostic endpoints, details can include the reference classification rule, handling of indeterminate results, endpoint denominators, and methods for interval estimation. Because these items are not reported, the calculation process cannot be reproduced from the registry record. The documented details support a description of the intended diagnostic comparison, but not a numerical judgment of accuracy or precision.
10. Multiplicity, Missing Data and Analysis Populations
The registry record lists one outcome measure, whose title covers sensitivity and specificity. Those are two related but distinct diagnostic-accuracy summaries. The record does not report whether each was treated as a separate primary analysis, whether one was prioritized, or whether any multiplicity procedure was planned. The statistical analysis plan is not reported in the registry record, so the handling of multiple endpoints or additional analyses cannot be assessed.
Missing-data information is also not reported. The record does not state how many primary-outcome results were unavailable, uninterpretable, or excluded, nor how such results were handled. It does not provide the endpoint denominators. Enrollment was 206, but enrollment alone does not show how many observations contributed to each calculation. The registry record does not describe whether participants with incomplete clinical assessments or device results were included in any analysis.
The analysis population is not reported in the registry record. There is no description of eligibility for the primary analysis, exclusions after enrollment, or whether the analysis used all enrolled subjects with available results. No interim analyses, analysis-population rules, or missing-data assumptions should be inferred from the completed status. These omissions matter because endpoint estimates and their precision depend on which results are included and how unavailable or indeterminate classifications are treated.
11. Safety Results
The registry reports serious adverse events as affected participants divided by participants at risk.
| Arm | Participants with serious adverse events | Participants at risk | Percentage |
|---|---|---|---|
| Device Testing | 0 | 206 | 0.0% |
Other (non-serious) adverse events
Participants with at least one non-serious event at or above the registry's 0% reporting threshold.
| Arm | Participants affected of at risk |
|---|---|
| Device Testing | 0 of 206 |
The registry lists the Device Testing group with 206 at risk for serious adverse events and 0 affected. For other adverse events, it likewise lists 206 at risk and 0 affected. Deaths are not reported in the registry record. These figures describe the adverse-event entries as recorded; they do not provide event descriptions or further details about monitoring.
A zero count in a registry entry means that no affected cases are recorded in that entry. It should not be interpreted as proof that no adverse experiences occurred, that every possible event was assessed, or that the device has no safety risks. The registry record does not provide definitions, collection procedures, severity grading, follow-up detail, or a narrative safety summary. It also does not explain whether all enrolled subjects contributed to each safety denominator. The safety figures should therefore be read narrowly as the reported counts, rather than as a complete account of safety or as a comparison with another group.
12. What the Result Does, and Does Not, Mean
The documented study question is whether the RPS InflammaDry Detector™ identifies cases in a way that corresponds to clinical assessment for dry eye. Its intended role, as described in the brief summary, is to detect elevated MMP-9 in tears and aid diagnosis alongside other clinical evaluation methods. The endpoint was sensitivity and specificity compared with clinical assessment, with a stated timeframe of 15 minutes.
The registry record does not report numerical endpoint results. It does not provide sensitivity, specificity, confidence-interval limits, or the classification counts needed to interpret those measures. As a result, no conclusion about the level or precision of diagnostic agreement can be drawn from the reported information. The study's COMPLETED status does not supply the missing outcome estimates.
Even when diagnostic-accuracy estimates are available, they describe performance relative to a defined comparator. Here, the record names OSDI, TBUT, corneal fluorescein staining and Schirmer Tear Test, but does not explain the rule used to derive the clinical classification. General interpretation of sensitivity and specificity therefore depends on details that are not reported. These measures are not, by themselves, proof of diagnostic benefit or evidence about outcomes beyond classification against the chosen reference.
The design is not described as randomized, and the record cautions that its arms are not a like-for-like control comparison. The data therefore should not be interpreted as a randomized estimate of a treatment effect. The registry record also does not report detailed analysis populations, missing results, or the analysis plan. Those gaps constrain what can be concluded even about the diagnostic comparison.
The record supports a description of the device's intended use and the planned comparison, but not a claim that the device does or does not work. It does not establish how the detector performs in other populations or settings, and it does not report evidence on clinical outcomes. Those questions cannot be answered from the registry record.
13. Why This Trial Matters Statistically
This study is statistically useful to consider because diagnostic evaluation asks a different question from a trial that compares treatments. Rather than estimating a difference in clinical outcomes between randomized groups, the stated aim is to compare test classifications with clinical assessment. Sensitivity and specificity capture different aspects of that classification, and presenting both is relevant because correct detection of reference-positive cases and correct rejection of reference-negative cases are not interchangeable properties.
The evaluation also illustrates why a comparator's definition is central. The record names OSDI, TBUT, corneal fluorescein staining and Schirmer Tear Test but does not report how those methods formed a clinical reference classification. Without that rule, readers cannot fully understand which cases defined the sensitivity and specificity denominators. This is a general issue in diagnostic research: accuracy estimates are conditional on how reference status is established.
Precision is another important part of interpretation. The endpoint description specifies a 95% Confidence Interval, but the registry record does not report the estimates or interval limits. A named uncertainty measure cannot communicate precision when its numerical results are unavailable. The absence of classification counts also prevents independent checking of the diagnostic summaries.
Finally, enrollment, completion status and safety entries do not substitute for a statistical results record. Enrollment was 206, while the endpoint denominators and analysis population are not reported; the study is marked COMPLETED, while no analysis records are listed. These distinctions help readers separate study conduct information from the evidence needed to assess a diagnostic endpoint. The registry record documents the question, but it does not provide the numerical results needed to answer it.
14. 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 main limitation for interpretation is that the registry record does not report primary-outcome estimates or confidence intervals. Although sensitivity and specificity are named and a 95% Confidence Interval is specified, neither estimates nor interval limits are present. The underlying classification counts and endpoint denominators are also not reported. Consequently, neither diagnostic performance nor its precision can be assessed.
The comparator is described through OSDI, TBUT, corneal fluorescein staining and Schirmer Tear Test, but the record does not report how these methods were combined, what thresholds defined positive and negative clinical assessments, or how discordant findings were resolved. Those details are important to interpreting accuracy measures because they define the comparison standard.
Enrollment was 206, but the registry record does not state the analysis population, the number with evaluable results, or how missing and uninterpretable findings were handled. It does not report test order, masking, or other procedural details that could inform assessment of bias. Allocation was not stated, and the record notes that the arms are not a like-for-like control comparison. The study should therefore not be read as a randomized comparison.
The statistical analysis plan, sample-size justification, and any interim analyses are not reported in the registry record. No analysis records are listed. Safety entries report zero affected for serious and other adverse events, but deaths and further safety procedures are not reported. Together, these omissions leave the documented study question clearer than the evidence needed to evaluate its answer.
15. Related Tutorials
16. Related Statistical Calculators
17. Sources
- ClinicalTrials.gov: RPS InflammaDry Detector™ to Determine MMP-9 Levels in Tears — NCT01313351.
- Registry record last updated 2022-12-12; status last verified 2022-11.
- Results first posted 2022-03-16.
- 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.
Continue through the Clinical Biostats statistical pathway
Use this trial's endpoint as a starting point for deeper study of effect measures, confidence intervals, and sample-size planning.
18. Record Summary
The record describes a completed device evaluation of the RPS InflammaDry Detector™ for detecting elevated MMP-9 in tears. The sponsor was Rapid Pathogen Screening; the listed condition was Dry Eye. Enrollment was 206, with a start of 2010-11 and primary completion of 2011-10.
The primary measure compared sensitivity and specificity with clinical assessment using OSDI, TBUT, corneal fluorescein staining and Schirmer Tear Test. Its timeframe was 15 minutes. The study was not randomized, allocation was not stated, and the record cautions that the arms are not a like-for-like control comparison.
The registry record does not report the sensitivity or specificity estimates, confidence-interval limits, analysis population, endpoint denominators, or statistical analysis plan. It lists no analysis records. Safety entries show 0 affected for serious and other adverse events; deaths are not reported in the registry record.