The evidence section of a translation project is not a literature review in the research sense, and writing it as one is the most common structural error at this stage. You are not establishing that a question is unanswered; you are establishing that an answer exists, that it is strong enough to act on, and that it applies to the specific population and setting where you intend to act. That means synthesis organized around the practice decision, guideline appraisal rather than study accumulation, and an explicit paragraph about transferability. 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 3 asks for
A student preparing a change to discharge teaching for residents leaving a subacute rehabilitation unit for home brought us a synthesis with twenty-two sources. It was thorough and it was unusable, because it was organized by source. Author, year, design, findings, repeated twenty-two times. Nobody reading it could tell what the evidence collectively said about the decision she had to make, which was whether teaching delivered by a nurse on the day of discharge works better than teaching distributed across the final three days. Reorganized around that question, the same twenty-two sources produced four paragraphs: what is established about timing, what is established about who delivers it, where the evidence is thin, and what the strongest guidance recommends. The literature had not changed. The organizing principle had.
That reorganization is the doctoral skill this stage examines. Evidence for a practice change is synthesized around decisions, and every decision your intervention embodies deserves a paragraph saying what the evidence supports and how strongly. Where you have chosen a delivery format, a frequency, a responsible role or a timing, that choice either follows from evidence or is a local adaptation, and both are acceptable as long as the document says which.
Deliverables at this depth usually sit inside your project documentation as an evidence or literature section, often with a synthesis or evidence table. Sections vary in whether they ask for a formal appraisal of levels or strength; where they do, use a published system and name it. If a discussion accompanies this stage, apply the same precision, because claims about what evidence shows are checkable and posts do not reopen once submitted in Canvas.
Guideline appraisal deserves particular attention in a 128-hour term because it is efficient. A well-constructed clinical practice guideline has already done the systematic work, and appraising two or three guidelines properly costs far fewer hours than assembling a synthesis from primary studies while producing a stronger foundation for a practice change. Appraisal means examining how the guideline was developed, who developed it, how recently, what strength it assigns its recommendations, and whether its population matches yours. Citing a guideline without appraising it, though, is an appeal to authority and reads as one.
The placement boundary, stated plainly
The written layer is where support belongs and where it stops. Your 128 practicum hours, hour logs, activity records, mentor and preceptor evaluations, site agreements and any verified signature are your own record, always, and are never drafted, reconstructed, estimated or filled in with assistance. Neither is any clinical activity performed or documented on your behalf. What is legitimately teachable is the scholarly writing that surrounds your real work: how to organize a synthesis around practice decisions, how to appraise a guideline systematically, how to build an evidence table that a committee can read, how to write a transferability paragraph that is honest about the gap between a study population and your own. Where anything in your writing draws on real residents, real transfers or real site documents, de-identify it fully, with no names, no dates of service, no unit identifiers and no detail that could narrow the field to a recognizable person.
The NR-705A Week 3 method, step by step
Six moves for building a synthesis that supports a practice change.
-
Reduce the rubric rows to verbs and check what appraisal system is expected
Synthesize, appraise and evaluate demand different work, and some sections require a named levels-of-evidence or strength system. Find out before you build the table, because retrofitting an appraisal scheme is slow.
-
Write out the decisions your intervention embodies
What is delivered, by whom, when, how often, to which subgroup, measured how. Each of those is a decision, and the list becomes the outline of your synthesis. Sources then get sorted into decisions rather than into chronological order.
-
Start with guidelines and syntheses, then descend
Search the synthesized layer first and only go to primary studies where the synthesized layer is silent or outdated. In a short term this ordering saves many hours and produces a stronger foundation than the reverse.
-
Appraise each guideline rather than citing it
Developing body, method, date, recommendation strength, conflicts declared, and the population it addresses. Two or three sentences per guideline, in the text, is enough to convert an appeal to authority into evidence.
-
Build the evidence table around your decisions, not the sources
Rows can be studies, but the columns should include which decision the source informs and what it supports. A table a reader can scan for the answer to one design question is worth three that summarize articles.
-
Write the transferability paragraph explicitly
Name the populations and settings the evidence came from, say where they differ from yours, and state what that difference does to the expected effect. This paragraph is where the practice-doctorate reasoning is most visible.
A layout and word budget for a translation evidence section
Our frame for the evidence section of a practice change project, sized for roughly 1,500 to 1,800 words plus a table. It is our own outline rather than anything the university issues, and your chair's guidance and your week's rubric outrank it wherever they disagree.
| Section | What belongs in it | Word target |
|---|---|---|
| Search account | Databases, terms, date limits, inclusion and exclusion rules, and the number of sources retained, written so it could be repeated. | 180 to 220 |
| Guideline appraisal | Two or three guidelines with developing body, method, currency, recommendation strength and target population. | 280 to 340 |
| Synthesis by decision | One passage per design decision, stating what the evidence collectively supports and how consistently. | 400 to 500 |
| Strength and gaps | Where the evidence is strong, where it thins, and which of your decisions rest on local judgment rather than literature. | 220 to 270 |
| Transferability | Source populations and settings against yours, with the direction and size of the expected discount named. | 230 to 280 |
| The change this supports | One paragraph stating precisely what the evidence justifies doing at your site, in operational terms. | 170 to 210 |
Evidence craft for a translation synthesis
Say what the body of evidence supports before naming any single study. Lead each passage with the collective claim and its consistency, then cite the sources behind it. A paragraph that opens with an author's name is describing an article; a paragraph that opens with a claim is synthesizing.
Keep verbs proportionate to design throughout. Associated with for observational findings, reduced only where an intervention was assigned and compared, and consistently reported across for a pattern spanning several studies of mixed quality. Doctoral readers check this and an overreaching verb undoes a well-built paragraph.
Give the guideline's recommendation strength, not only its content. Guidance bodies grade their recommendations, and the grade tells your reader how much confidence the developers themselves had. Quoting the recommendation while omitting the grade removes the most useful information in the document.
Name the date boundary and defend it. A search limited to recent years is a choice with consequences, especially where a foundational trial sits outside the window. State the limits, and where an older source is retained because nothing has superseded it, say that in the sentence rather than leaving the inconsistency visible.
Five mistakes that cost points in this week's territory
- Source-by-source organization. An annotated sequence of studies is a reading log, and it cannot tell a committee what the evidence collectively supports.
- Arguing a gap in the literature. That is the move of an original research proposal. A translation project argues that established evidence is not reliably delivered where you work.
- Guidelines cited without appraisal. Naming a body and a year without its method, currency and recommendation strength is authority rather than evidence.
- No transferability paragraph. Borrowing an effect from a different population and setting without discussing the difference leaves the central assumption of the project unexamined.
- Local adaptations presented as evidence-based. Where a choice comes from your setting rather than the literature, say so; a committee that finds an unsupported claim dressed as evidence discounts the whole section.
Before you submit
- The synthesis is organized by design decision rather than by source
- Each guideline carries its developing body, method, date and recommendation strength
- The search is described precisely enough to be repeated
- Every causal verb matches the design behind the claim
- A transferability passage names the gap between source populations and yours
- Decisions resting on local judgment are labelled as such
Building the NR-705A evidence section?
Send the rubric, your scope document and your source set out of Canvas. A premium original draft comes back in 24 to 48 hours organized by practice decision, with guidelines appraised properly and transferability argued. Revisions run until the grade lands, and your hours, logs and site documentation stay entirely yours.