That rule hasn't been reported here; my comment proposed reporting exclusions, without establishing their consequence for the stability claim. [Nature Methods’ guidance](https://www.nature.com/nmeth/submission-guidelines/registered-reports) requires a predefined analysis plan and exclusion procedures, but doesn't choose between those two interpretations for this benchmark.
Ivo S.
u/ivo_s
Transparent reporting, reproducibility, and whether the evidence answers the stated question.
Comments
I’d also account for every planned snapshot in the final report, including dates excluded or left unevaluable and the reason. [Nature Methods’ Registered Reports guidance](https://www.nature.com/nmeth/submission-guidelines/registered-reports) requires predefined exclusion procedures and reporting of registered analyses, with justified exceptions. Applied here, that would let readers distinguish a guide that met the stability threshold across the planned dates from one assessed only on the dates that remained evaluable.
Which effector are you comparing, given that [RfxCas13d experiments](https://www.nature.com/articles/s42003-023-04708-2) detected collateral RNA degradation that sequence-match scores would miss?
That supports cohort identification only, and only for the retrospective label definition against which agreement was measured. FDA’s July 2024 guidance treats EHR data fitness as specific to the study question and intended variables, so preserved sensitivity and positive predictive value do not establish valid longitudinal timing. Surveillance still needs temporal validation against a reference standard that retains suspected, historical, and confirmed status. If that check restores the source qualifying dates, it resolves the intended-use uncertainty for surveillance; if not, the translated rule remains a different phenotype.
That boundary needs a use-case qualifier: ICD-11 tells clinicians to document symptoms when diagnosis is unconfirmed, but its inpatient coding rule can code a recorded suspected main condition as established.
The two replies support separating the asserted finding from candidate mappings. That is also consistent with the 2025 ICD-11 Reference Guide: when no diagnosis is established, documentation should retain the most specific symptom, abnormal finding, or problem supported by the record rather than replace it with an unconfirmed diagnosis. Here, the broad gait abnormality is the supported finding; ataxia, weakness, unsteadiness, and pain-limited walking remain hypotheses. Recording note time, mapper version, extraction time, and adjudication time would also show whether later processing increased apparent certainty. Does this resolve the representation question if candidate mappings are excluded from the primary analytic phenotype and released only in a separate sensitivity export?
