Biometrics partner for sponsors and CROs

Health authority questions: a programming playbook for answering fast without breaking anything

During a review, regulators send health authority questions (HAQs), also called information requests. Some are simple clarifications. Others ask for new analyses: an extra subgroup, a different handling of missing data, a pooled look across studies. Those land on the programming team, usually with a deadline set by the agency in the request itself.

Why the timing matters

Under PDUFA VII, FDA aims to act on new molecular entity applications within ten months of the 60-day filing date for a standard review, or six months for priority review. A substantial new analysis submitted late can be treated as a major amendment and extend the goal date by three months. Fast, clean answers protect the timeline.

Before the first question arrives

  • Freeze and archive the exact environment that produced the submission: data, programs, macro or package versions, and the operating system.
  • Keep the ADaM specifications and derivation logic current, so a new analysis can reuse existing variables instead of rebuilding them.
  • Agree in advance who signs off a response: statistician, programming lead and the regulatory contact.

When it lands

  • Read the question with the statistician first. Most delays come from answering the wrong question well.
  • Add new derivations to ADaM in a controlled way, with the same traceability as the original datasets, rather than in a one-off program.
  • Double-program the key numbers. A response is part of the regulatory record; errors in it are expensive.
  • Update define.xml and the ADRG if datasets or variables change, and say clearly in the response what is new.

After it is answered

Keep every HAQ program and output alongside the submission archive. Similar questions often come back from another agency, at an advisory committee, or in a later submission, and reusing a validated answer is far faster than recreating it.

HAQ and ad-hoc support is a large part of our programming work. If you have a review coming up, it is worth agreeing the plan before the first question arrives.

Have a study that needs statistical support?

Tell us about the study and what you need. A statistician will get back to you.