Best iPhone Notes App for Biostatisticians

Biostatisticians make decisions that have consequences: which analysis population to use, how to handle missing data, what sensitivity analyses to pre-specify, when a data anomaly requires protocol deviation documentation. These decisions need to be documented, and they often happen in conversations — with clinical teams, with data management, with regulatory reviewers.

The Biostatistician's Documentation Challenge

Analytical decision trail. You decided to use the modified ITT population rather than strict ITT because of a specific unblinding risk in the full randomized set. That reasoning needs to survive to the clinical study report, which might be written 18 months later. Is it in the SAP? Maybe. But the conversation where you worked through the reasoning — with the medical monitor, the sponsor statistician, the data manager — that's where the real reasoning happened.

Data anomaly observations. During data review, you notice that Site 14 has systematically lower values on the primary endpoint vs. all other sites. It might be a site effect (real), a measurement artifact (data issue), or a protocol deviation (administrative). You flag it in your review notes. This observation is the starting point for an investigation that might change the analysis or generate a sensitivity analysis.

Meeting notes from statistical review calls. The sponsor's biostatistician said "we'll allow that imputation method if you add a sensitivity analysis using LOCF." That's a binding commitment. It needs to be in writing — and your personal notes plus a follow-up email confirmation create the documentation trail.

Pre-specification vs. post-hoc tracking. In regulatory submissions, the distinction between pre-specified and post-hoc analyses matters enormously. Your notes on when decisions were made and why are the evidence.

How Nemos Works for Biostatisticians

Statistical Analysis Decision Notes

When you make an analytical decision, document your reasoning:

``` ## SAP Decision — Primary Endpoint Analysis (Study XR-2025) Date: 2025-03-10. SAP version: 1.3.

Decision: Use MMRM rather than ANCOVA for primary endpoint analysis. Reasoning: Expected dropout pattern favors MMRM (MAR assumption more defensible than LOCF given mechanism of dropout — treatment-related nausea in early weeks). Discussed with Dr. Kim (medical monitor) on 2025-03-10 call — agreement to proceed. Sensitivity: add ANCOVA with LOCF as sensitivity per standard practice.

Pre-specified: Yes — incorporated in SAP v1.3, finalized before database lock. ```

Data Review Observation Notes

During data review:

"Site 14 observation (2025-03-12 data review): primary endpoint mean 4.2 units below grand mean (-22%). All other sites within ±8% of grand mean. Site 14 enrollment: 23 patients. Possible explanations: measurement technique variation, patient population difference, data entry issue. Flag for clinical team — request data management review of Site 14 measurement procedures."

Regulatory Interaction Notes

After FDA/EMA meetings or telecons:

"FDA Advisory Committee meeting prep call 2025-03-15: reviewer Dr. Liu asked about multiplicity adjustment for secondary endpoints. Team agreed to add Hochberg procedure in addition to Holm — pre-specified amendment to SAP required before this analysis runs. ACTION: draft SAP amendment by 2025-03-22."

Data Management Communication Notes

"DM call 2025-03-14: discussed handling of 47 missing primary endpoint values. DM confirms: 31 are site-level missing (no measurement taken), 16 are withdrawn before endpoint assessment. MAR assumption: reasonable for 31, questionable for 16 (systematic withdrawal). Incorporate MNAR sensitivity analysis."

Regulatory Context

Biostatisticians working on FDA/EMA regulatory submissions operate under ICH E9 and ICH E9(R1). Pre-specification and documentation of analytical decisions are regulatory requirements, not just professional standards. Your personal notes are part of the evidence trail.

FAQ

Q: Are my personal statistical notes part of the Trial Master File? A: Formal TMF documents (SAP, statistical output, programming specifications) are official TMF items. Personal working notes may be discoverable in litigation or regulatory inspection — write professionally.

Q: How do I document when I made a decision (pre-specification vs. post-hoc)? A: Date-stamp your notes (Nemos does this automatically) and follow up important decisions with a dated email to the team. The combination of personal notes + email confirmation creates a robust pre-specification trail.

Q: What about notes on software and programming decisions? A: Document your analytical software version, programming specifications, and key code decisions. "Primary endpoint analysis in SAS 9.4, PROC MIXED with unstructured covariance matrix — programming spec version 2.1" is a useful audit trail.

Q: Can I use Nemos for notes on interim analyses? A: Yes — but interim analysis notes require additional care around blinding. Do not document unblinded interim results in personal apps. Document process, methodology decisions, and administrative matters only.

Q: How do I handle notes when an analysis changes direction late in the project? A: Document the change, the reason, and the timing: "Post-hoc sensitivity analysis added 2025-03-20 per FDA reviewer request at pre-NDA meeting. Not pre-specified — will be labeled as exploratory in CSR."

Related Reading

• /blog/research-coordinator-notes-iphone
• /blog/lab-manager-notes-iphone
• /blog/clinical-researcher-notes-iphone
• /blog/data-scientist-notes-iphone

Sources

• ICH E9(R1) Statistical Principles for Clinical Trials (2019)
• FDA guidance for industry: Adaptive Design Clinical Trials
• American Statistical Association statistical practice guidelines