The preparedness stage of NR-586AT asks a leader to write continuity for a service rather than a general description of a hazard. The unit of analysis is the function your department performs: what has to keep happening, for whom, within what tolerance, when the building, the staff, the power or the supply chain is unavailable. Population health enters through the people who cannot absorb an interruption, and the writing is judged on specificity: named functions, stated tolerances, counted patients, real capacity. Your section may print this as NR 586AT or NR586AT; 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-586AT Week 7 asks for
What actually breaks when a department loses power for eleven hours? An outpatient chemotherapy and infusion unit finds out on a summer afternoon when a substation fault takes out three blocks. Refrigerated medication has a tolerance measured in hours and someone has to know what it is. Pumps run on battery for a while and then do not. The scheduling system is unreachable, so nobody can tell which of the day's remaining patients are the ones who cannot safely wait until Thursday. Twenty-two people are mid-treatment. The plan that matters here is not an evacuation plan; it is a continuity plan, and it is specific to functions this department performs and nobody else in the building performs.
That is the frame this stage rewards. Start from functions rather than from hazards, because the number of hazards is large and the number of ways a service actually fails is small: loss of building access, loss of power, loss of staffing, loss of information systems, loss of supply, and loss of the referring or receiving services you depend on. Almost every hazard produces some combination of those six. Writing to the failure modes gives you a plan that works for a flood, an outage and a staffing crisis at once, which is what a real continuity document has to do.
Each function needs a tolerance and a minimum acceptable level. How long can this stop before harm accrues, and what fraction of normal volume constitutes an acceptable degraded state? Those two numbers turn a plan into something that can be tested. A chemotherapy schedule and a routine wellness clinic have entirely different tolerances, and a plan that treats all department functions as equally urgent will fail at exactly the moment prioritization is needed.
The population health layer is where this stage connects to the rest of the session. Interruption does not distribute its harm evenly. Patients who depend on refrigerated medication, on powered equipment, on paratransit, on an interpreter, or on a caregiver who cannot take a second day off are the ones for whom a two-day closure becomes a clinical event. Identify those groups inside your own panel, estimate how many people they represent, and design the degraded-state plan around them. Deliverables at this depth run roughly 1,200 to 1,600 words; where a national preparedness framework is named in your prompt, use it as the spine and attribute it.
The NR-586AT Week 7 method, step by step
Six moves for a continuity plan that would survive an actual incident.
-
List your department's functions, not its hazards
Six to ten things the service does that somebody depends on. This list is the spine of the document and it is stable across hazard types.
-
Assign each function a tolerance and a minimum acceptable level
Hours or days before harm accrues, and the fraction of normal capacity that counts as degraded but acceptable. Both stated as numbers.
-
Identify the patients for whom interruption is a clinical event
Powered equipment, refrigerated medication, time-critical treatment, transport dependency, interpreter need. Count or estimate each group inside your own population.
-
Write the degraded-state operating plan
What you would run, where, with whom, in what order, and which patients are contacted first. Prioritization decided in advance is the whole value of the document.
-
Name dependencies outside your control
Pharmacy, laboratory, imaging, transport, the referring service, the supplier. A continuity plan that assumes everyone else is functioning has assumed the problem away.
-
Attach roles, triggers and a test
Which role activates what at which observable threshold, and how the plan will be exercised so that people have done it once before they have to do it.
A layout and word budget for a continuity plan
Our frame for this stage, sized for roughly 1,300 to 1,600 words. It is our own outline rather than anything the university issues, and your week's rubric outranks it wherever they disagree. If a function-and-tolerance table is permitted outside the count, build it and use the prose for the reasoning.
| Section | What belongs in it | Word target |
|---|---|---|
| Functions and tolerances | What the service does, how long each function can stop, and what a minimum acceptable level looks like. | 250 to 300 |
| Failure modes considered | Access, power, staffing, information systems, supply and upstream services, with local likelihood noted. | 200 to 250 |
| Patients at clinical risk from interruption | Each dependency group named, counted or estimated, with the tolerance specific to them. | 250 to 300 |
| Degraded-state operations | What runs, where, staffed by whom, in what priority order, and how patients are contacted without the usual systems. | 300 to 360 |
| External dependencies | The services and suppliers you rely on, what happens when each is unavailable, and any mutual aid arrangement. | 180 to 220 |
| Roles, triggers and testing | Who activates what at which threshold, and how and when the plan is exercised. | 170 to 210 |
Evidence craft for continuity writing
Use the organization's own hazard assessment where one exists. Health systems and jurisdictions produce hazard vulnerability analyses, and citing yours grounds the likelihood section in something other than intuition. Name the document and its year.
State tolerances as numbers, sourced where possible. Medication storage tolerances, equipment battery life and treatment interval limits are documented facts rather than estimates, and citing them is what makes a plan defensible to a pharmacy director or a clinical lead.
Count the dependency groups inside your own population. Roughly how many people on the panel use powered equipment or require refrigerated medication. An estimate with a shown derivation beats a category with no number.
Do not include patient identifiers or a callable list in a course document. Describe the categories and their sizes; the operational contact list belongs in your organization's systems and never in an assignment.
Keep any real incident account de-identified and systems-focused. If you lived through an outage, write what the plan assumed and where the assumption failed. No patient detail, no identifiable facility narrative.
Attribute preparedness frameworks and phases. Terminology drawn from national frameworks should carry a name and a year, since unattributed framework language reads as vocabulary rather than as structure.
Five mistakes that cost points in this week's territory
- A hazard essay instead of a continuity plan. Three paragraphs about the meteorology of an event and none about what the department does on Tuesday.
- Functions listed without tolerances. Without hours and minimum levels, nothing in the plan can be prioritized under pressure.
- Dependency groups named but never counted. Patients on home oxygen is a category; an estimated forty patients on home oxygen is a planning input.
- A plan that assumes the systems are up. If your contact strategy requires the scheduling platform, you have not planned for the most common failure.
- No triggers and no owner. Plans without an activation threshold and a named role activate late, which is the same as not existing.
Before you submit
- The document is organized by function rather than by hazard
- Each function carries a tolerance in hours or days and a minimum acceptable level
- Patients at clinical risk from interruption are grouped and counted
- The degraded-state plan states priority order and a contact method that survives system loss
- External dependencies are named with what happens when each fails
- Every trigger has an observable threshold and a named role attached
Writing the continuity plan?
Send the rubric and your service or unit out of Canvas. A premium original draft comes back in 24 to 48 hours organized by function, with tolerances stated, dependency groups counted and a degraded-state plan that names priority order and owners, with revisions until the grade lands.