A records project feels like the safe one. Nobody is recruited, nothing is done to a patient, and the numbers already exist. That is exactly why it stalls: the chart is not yours. It is held by the facility, about a patient, under rules the facility answers for — and the fact that you may open it every shift as part of your job says nothing about whether you may open it as an investigator.
A records project is human-subjects work whenever identity can be worked out from what you hold. Chamberlain rules on how your file describes the data; the practicum site rules on whether an extract leaves its systems at all, and by which route.
Start with custody, because everything else follows from it. A medical record is held by the facility as custodian and describes a patient who never agreed to be in your project. You may have credentialed access for treatment, and you may have written in that chart yourself. None of that is access for a project: the role you occupy when you open it changes what the record legally is, and a login issued for care is not a licence to abstract.
So a records project has two doors. Chamberlain rules on your file — what you take, from where, who handles identifiers, and whether that account holds together. The practicum site rules on the record room: its board or nursing-research council, with whatever office it keeps for privacy, decides whether an extract reaches you at all and in what form. No school determination opens a facility’s data warehouse.
The Common Rule never asks whether you met anyone. It reaches any living individual about whom an investigator obtains or analyses identifiable private information (45 CFR 46.102). Private information covers what someone shared for a particular purpose and reasonably expects to stay out of public view — a description a chart fits precisely. It becomes identifiable private information once who the person is can readily be worked out by the investigator, or is already attached to the data.
The test is reachability of identity, not contact. Open a chart, read the name, record what you find under a code you assign, and identity is plainly reachable. Have someone else abstract, keep the link behind, and hand you a file you cannot trace back, and no human subject may be involved at all. The Office for Human Research Protections has long treated coded information that way where the analyst genuinely cannot ascertain identity — for instance where key-holder and analyst have a written agreement barring its release. That guidance is pointed about who decides: not you.
On the Chamberlain side, the first document is not the application at all. The current DNP Project & Practicum Handbook routes a project through a Prescreening Review Form filed inside the project and practicum course sequence, stating that “most DNP projects will meet prescreening criteria” for a finding that the project does not constitute human subjects research. A records project is where that expectation gets tested: prescreening turns on identifiable information, not on how quiet the method feels. The handbook also makes you identify whether an IRB is required at the practicum site, and holds that implementation waits on both. Which forms apply, and how they are submitted, is set by Chamberlain’s current handbook or IRB portal, not by what a colleague filed before. Where the label itself is in play, classification and the review path it decides is the companion read.
Chamberlain protects a project it will put its name to. The site protects a record system it answers for long after you finish.
A Chamberlain determination is not a key to the record room, and a data-use agreement is not a project file. Both must exist, and both must describe the same extract.
Both boards will settle this from your file whether or not you settle it first, so settle it first. Claim one row below and describe another, and the file returns.
| How the extract reaches you | What the site controls | What the Chamberlain file must show |
|---|---|---|
| You query and abstract yourself, under your own credentials | Whether you may at all, and by which privacy route | Why identity is needed, who else reaches the key, when it is destroyed |
| A facility analyst abstracts; the link stays behind under written agreement | Who that person is, what may be released, and the agreement’s wording | That you will never receive, request, or reconstruct the link — stated, not implied |
| You receive a limited data set: direct identifiers stripped, dates retained | The data-use agreement, and who may sign for the facility | That the file calls it a limited data set, not de-identified, everywhere |
| You receive an extract with every listed identifier removed | Who removed them, and by which method | That no fine-grained date, unit label, or free-text note survived the strip |
One row trips more files than the rest. A spreadsheet with names deleted but admission dates and a unit name intact is not de-identified, and calling it that in front of a privacy office is the fastest way to lose the room.
Most practicum sites are covered entities, and the Privacy Rule gives a facility a short, closed list of lawful ways to let a project use its records. Your file does not choose among them; the facility’s privacy office does. Your file names the chosen route and describes it consistently.
Neither board administers the Privacy Rule for the other. Each asks whether your account of the data is coherent — and a file calling itself de-identified on one page while linking readmissions by record number on the next has described two projects.
Records projects drift most quietly. Keep these consistent, word for word:
Chamberlain’s board says of itself that it does not advise on study design or create required documents such as consent forms. That is the gap a desk like ours fills: we settle the classification and the data plan before a page is drafted, build the school’s file, prepare the site’s packet in its own vocabulary, draft the agreement for the office that can sign it, and carry every reply until both approvals are in writing. We are independent consultants, not affiliated with Chamberlain University; each board decides for itself. How it works lays out the route; the FAQ covers what arrives first.
Send the variable list and the facility holding the records. We will tell you free of charge which privacy route your pull needs, whose signature it requires, and whether the site will read it as improvement work or as research. Request the free application review. For the sequence, the process step by step puts both tracks in order; site permission versus the site’s IRB covers the distinction records projects trip over most.
35% off the whole process when you start this season, and the application review is free.
Fixed fee, quoted in writing after the free review. No hourly billing, no add-ons. The review is free either way.