Quality improvement or research? At Aspen you file either way — the board writes the determination
The question people bring us is “does my project need IRB review?” At Aspen that is very nearly the wrong question, because Aspen’s own material answers it before you ask: whatever kind of activity you are proposing, you submit materials and the board issues a determination. It makes that call; you do not. The real question is what your design is telling the board about itself — and a design that argues with the label on the form is the single most expensive finding in this whole process.
Charlotte Devereux, MSN, RN · 2026-08-23
In short. You file regardless. Aspen asks every doctoral candidate to submit; the board then decides whether the work is research, whether human participants are involved, and at what level it is read. What settles that is intent behind the design: not the label, not publication plans.
Does an Aspen capstone or DNP project need IRB review at all?
Assume a submission is required, and let the board tell you otherwise in writing. Aspen’s published guidance is explicit that a candidate does not self-certify: you send materials, an administrator applies a formal process built on the Common Rule, and a determination comes back. Aspen even makes the point about activities most people would swear are exempt from the whole business, a systematic review of the literature among them — you still submit, and the level of oversight follows from what the activity turns out to be.
That is a kinder arrangement than it first sounds. If the answer is that your work is not research, you receive a letter saying so, and that letter is a document with weight: it is the thing that protects you later, when a committee member or a journal asks under what authority the data were collected. An assumption protects nobody. A determination is evidence.
Master’s capstone work sits in a different place. Aspen’s current MSN Handbook frames the capstone as a written account of a practicum project and does not carry an IRB chapter, while the IRB Handbook addresses itself to doctoral candidates. If your capstone starts to look outward — surveying colleagues, interviewing patients, drawing identifiable records — put the question to your capstone instructor, and to whatever Aspen’s current handbook or IRB portal now says, instead of reasoning from that silence.
What actually makes an activity research?
Two things together, and both have to be present. The Common Rule defines research as a systematic investigation built to develop or contribute to generalizable knowledge, and Aspen breaks that into the two tests an administrator applies: is this a systematic investigation, and is it built to produce knowledge that reaches past the place it was gathered?
Almost every doctoral project clears the first test. A prospective plan, data collected, data analysed, a question answered — that is systematic by any reading. So the weight falls entirely on the second, and Aspen is candid that there is no regulatory definition of generalizability to lean on. What Aspen offers instead is the operative test: whether the investigator intended to contribute to a body of knowledge. Results that stay in the building and serve administration are commonly treated as quality improvement; findings meant to apply beyond the unit, the setting or the population you studied are behaving like research.
Does intending to publish decide it?
No, and both Aspen and the federal guidance say so in the same breath. Aspen states plainly that it is neither publication nor the intent to publish that matters, but the intent of the project. The Office for Human Research Protections puts it the other way round for emphasis: planning to publish an account of a quality improvement project does not make it research, and a project can be research with no plan to publish at all.
This one causes real damage, because it cuts both ways. People add “for internal use only” to a protocol hoping it buys them a lighter reading, and people delete a dissemination plan for the same reason. Neither move changes what the design does. Boards read the design.
Which design features actually decide it?
Six, and you can inspect all six today, in your own proposal, before anybody official reads it.
| Feature | Reads as quality improvement | Reads as research |
|---|---|---|
| Purpose | Improve care in this unit, against a standard already accepted here. | Establish whether something works, as evidence for others. |
| Who the finding serves | This organisation, for clinical or administrative use. | A field, a population, or practice beyond this setting. |
| The intervention | A practice already known to work, being put into use. | Something untested here, adopted in order to see what it does. |
| Sampling | Everyone the change touches; no allocation, no arms. | A drawn sample, a comparison group, a control condition. |
| The question | Are we doing what we already agreed to do? | A hypothesis, tested for significance. |
| Reach of the claim | Conclusions stop at the unit’s door. | Conclusions are offered as transferable. |
The federal guidance draws the same line with a worked example: implementing a practice known to reduce prescription errors and auditing charts to see whether it took hold is not research, while introducing an untested clinical intervention partly in order to build scientific evidence about its effect may well be. Aspen’s own approval questions run alongside this — the board asks whether the design is sound enough to answer the question it poses, which is a hard thing to say yes to when the file has not decided what kind of question it is asking.
Why does Aspen expect more than an in-house improvement project?
Because the doctoral work is meant to reach further. Aspen’s handbook says it directly: while quality-focused work may not always fit the legal definition of research, dissertations and projects inside Aspen programmes are required to go beyond simple in-house quality initiatives.
Sit with that for a moment, because it is the tension at the centre of most Aspen files. The programme pushes the work outward, toward something that contributes; the quality-improvement framing pulls it inward, toward something that only serves one unit. A file written with one foot in each is the file that bounces, because every later answer — the consent question, the sampling question, the data question — was drafted to whichever framing happened to be in mind at that moment. Settle the category from the design first, then write every document to it. That order is the whole of how we work a file.
If it really is quality improvement, what still applies?
More than people expect, and one thing less.
- Site permission still applies. Aspen’s handbook is emphatic here: a project run at a clinic needs written permission from the appropriate person at that clinic, whatever the work is called. This is the finding least forgiving of delay, because you cannot cure it on your own schedule.
- A consent form often does not. Aspen gives the worked case: assessing nurses’ understanding of an established evidence-based protocol and then reviewing charts to see what the initiative changed would not, in Aspen’s account, require a consent form from those nurses — though the site permission letter is still required. Unless your site demands one, quality improvement work frequently proceeds without it.
- Privacy law does not care what you call it. Aspen ties the authorisation form to a factual trigger: if medical records are touched at any point, that requirement is live.
- Nothing starts early. No recruitment, no data access, no collection, no implementation before the letter arrives. The category makes no difference to that rule.
So the practical answer to “is my project quality improvement?” is rarely a lighter file. It is a differently shaped one, and knowing the shape before you build it is what saves the cycle. Which level that shape earns is taken up in the piece on Aspen’s review levels; the road the file then travels is drawn in the process, in order.
What to do next
Uncertain which side of this line your project sits on? That uncertainty is diagnosable today, from documents you already hold. Ask us for the free application review through the contact desk: we read the design as the board will, then write down which category it earns and the features that earn it, with the evidence a reviewer would see and the correction beside each finding. There is no cost and nothing follows it — sometimes the report simply says the claim already holds. Where it does not, the whole process can pass to us: the category settled, every document rebuilt to match it, the submission prepared and filed alongside you, and each reply carried until an answer comes. What we never touch is the work itself. Your project, its data and its conclusions stay yours, and the board’s determination is its own. Our FAQ covers the adjacent questions.