Every doctoral project passes through a review process that decides how it is classified and what protections apply, and this stage is about writing the documentation that process needs. Two things matter above all. Write factually about what has been submitted, to whom and when, and predict no outcome whatsoever: not that approval is expected, not that a determination will be routine, not that the work is exempt. And write the protection layer properly, covering how the people affected by your project are safeguarded, how data is de-identified, stored and eventually disposed of, and how the ethical obligations of a practice change are met even where formal research protections do not apply. Your section may print this as NR 705A or NR705A; it is the same course. Chamberlain publishes no syllabi outside Canvas. The placement here is our teaching judgment from the course's catalog arc; your section's rubric decides what your week actually asks.
What NR-705A Week 7 asks for
The distinction that organizes this whole stage is between generating new generalizable knowledge and improving care at a particular site. A DNP project translates evidence that already exists into a practice change at one setting, which is a different activity from research and is usually classified differently by review bodies. But the classification is theirs to make, not yours, and the single most common error in this section is a student writing a determination into their own documentation. You describe the project accurately and completely; the review body decides what it is.
That does not mean protections are optional. A change to how residents are handed over between settings affects real people who did not volunteer for anything, staff whose work is altered, and information that is confidential regardless of how the project is classified. Ethical obligation attaches to the activity rather than to its administrative label, and a doctoral document that treats a non-research determination as the end of the ethics discussion has misunderstood the point. Write the protections as though they matter, because they do.
The written deliverable at this depth usually consists of the documentation your program's process requires, plus a protection or ethical considerations section inside your project documentation. Requirements vary by program and by site, and where they conflict you satisfy both rather than choosing. If a discussion accompanies this stage, treat it as final copy, since posts do not reopen once submitted in Canvas.
One more thing belongs here that students frequently omit: the dual-role question. Most DNP students carry out projects where they work, which means the person asking a nursing assistant to add a step to her routine is also, on other days, her colleague or her supervisor. That is a real influence relationship and the honest move is to name it and say how it is managed, in a short paragraph. Disclosure is ordinary scholarly practice and reads as maturity; silence about an obvious dual role reads as something else.
The placement boundary, stated plainly
This is the stage where the boundary is least negotiable. Your 128 practicum hours, the hour log, activity and encounter records, mentor and preceptor evaluations, site agreements, attestations and every signature the facility or the university verifies are your own record. They are never drafted, reconstructed, estimated, back-dated or completed with help from anyone, and any submission to a review body is written and submitted by you, in your own account, describing what is actually true. There is no version of this work in which someone else supplies it. What can legitimately be taught is the written layer around it: how to structure a protection section, how to describe a review process factually, how to write about de-identification and data handling precisely, and how to disclose a dual role in professional language. Every clinical illustration in your writing must be de-identified beyond recognition, with no names, no dates of service, no unit or room identifiers.
The NR-705A Week 7 method, step by step
Six moves for writing protection and review documentation cleanly.
-
Establish both sets of requirements before writing anything
Your program has a process and your site may have its own, and they are not always the same. Find out what each requires, in what order, and satisfy both. Sequencing errors here cost weeks that a 128-hour term does not have.
-
Describe the project in the vocabulary of a practice change
Site, population served, evidence being translated, process being altered, measures drawn from existing data. Accurate description is what allows a review body to classify correctly, and research vocabulary applied loosely invites the wrong reading.
-
Write status factually and stop
What was submitted, to which body, on what date, and what stage it is at. No expectations, no anticipated outcomes, no characterization of what the determination will be. One or two sentences.
-
Identify everyone the change touches and what each is exposed to
Residents and families, staff whose work changes, the organization itself. For each, name the burden or risk, however modest, and the protection that addresses it. Minimal risk is a conclusion, not a substitute for the analysis.
-
Specify de-identification and data handling concretely
Which identifiers are removed and at what point, where files live, who has access, whether anything is stored on a personal device, and what happens at the end. Specificity here is quick to write and conspicuous when missing.
-
Disclose the dual role and say how it is managed
Where you work in the setting, name the relationship and describe the management: voluntary participation in anything optional, no evaluative consequence attached, feedback routed through someone without authority over the staff involved where that is possible.
A layout and word budget for a protections and review section
Our frame for an ethical considerations and data stewardship section, sized for roughly 1,300 to 1,600 words. It is our own outline rather than anything the university issues, and your chair's guidance, your program's process and your site's requirements all outrank it.
| Section | What belongs in it | Word target |
|---|---|---|
| Project described for review | Setting, population served, the evidence translated, the process altered, and the data the measures draw on. | 200 to 250 |
| Review status | What was submitted, to which bodies, when, and the current stage, with no predicted outcome anywhere. | 100 to 140 |
| Who is affected | Residents and families, staff, the organization, each with the burden or risk the change places on them. | 230 to 280 |
| Protections | The safeguard matched to each identified burden, including anything voluntary and how that voluntariness is preserved. | 250 to 300 |
| Data stewardship | Identifiers removed and when, storage location and security, access list, retention period and disposal. | 240 to 290 |
| Dual role and conflicts | Your position in the setting, the influence it creates, and the concrete steps that manage it. | 180 to 220 |
Evidence craft for protection writing
Cite the ethical framework you are working within. Professional codes and published ethical guidance for quality improvement exist and are citable. Naming one anchors your protection reasoning in something external rather than in your own sense of what is reasonable.
Use the language of your own governance documents. Where your program or site uses specific terms for determinations, categories or submissions, use those terms exactly. Approximating official vocabulary in a document that goes to a review body creates ambiguity nobody benefits from.
Never characterize a review outcome, including in the past tense loosely. Report what a body actually issued, in its own words, with its date. Paraphrasing a determination generously is a factual error in a document whose whole purpose is accuracy.
Write de-identification as a process with a moment. Say at which point identifiers are removed rather than stating that data will be de-identified. The distinction between abstracting identifiable information and then stripping it, and never recording it at all, is exactly what a reviewer is reading for.
Five mistakes that cost points in this week's territory
- Writing your own determination. Stating that the project is exempt or non-research pre-empts a decision that belongs to a review body and is the fastest way to have documentation returned.
- Predicting approval. Anticipated, expected and should be routine have no place in a document describing a pending review.
- Minimal risk asserted without analysis. The conclusion may well be right, but it has to follow from an identification of who is affected and how.
- Data handling left vague. Data will be kept secure names no location, no access list, no retention period and no disposal, and reviewers read the absence as thoughtlessness.
- Dual role unmentioned. Conducting a project where you work is common and acceptable; failing to disclose the influence it creates is neither.
Before you submit
- No sentence states or implies a determination or predicts a review outcome
- Both program and site requirements are identified and addressed
- Everyone affected by the change is named with their specific burden
- Each burden has a protection matched to it
- De-identification names the identifiers and the moment they are removed
- Storage, access, retention and disposal are all specified
- Any dual role is disclosed with concrete management steps
Writing NR-705A protections documentation?
Send the rubric and your project documentation out of Canvas. A premium original draft comes back in 24 to 48 hours with the protection layer built properly and review status written factually. Revisions run until the grade lands. Submissions, signatures, hours and logs remain entirely yours to complete.