Three Requests, One NPD Practitioner: Scope, Competency, and Privacy Under Pressure

Test the request against role delineation, not against your willingness to help.

• NPD practice is organized around learning facilitation, change, mentorship, EBP/research, leadership, partnership, and advocacy. A stroke coordinator role carries program accountability, regulatory compliance (e.g., stroke certification data abstraction), and clinical practice decisions. That is an operational/quality role, not an NPD role - and holding it would compromise the neutrality you need when you later validate competency or evaluate education.
• Quantify the cost: 10 hours of a 40-hour week is 25% of capacity, with no backfill named. Ask who covers the education deliverables you drop and get the answer in writing.

Judgment call: decline the full absorption, offer a bounded partnership. For example: "I can commit 2 hours weekly to build and evaluate stroke education and sit on the stroke committee, but the coordinator accountabilities need a clinical owner." Offer a written scope with an exit date if leadership insists on temporary coverage.

Escalate with data, not emotion: bring a one-page list of current deliverables, hours, and the risk of dropping each. The discriminating question is whether this is a learning need (yours to solve) or a staffing/operational gap (leadership's to resource). Frame it that way and ask for a decision.

No - not as described. Competency validation means the nurse demonstrated a defined skill against explicit criteria, observed in the practice setting, with objective documentation. An hour of watching on a first shift is orientation, not validation, and signing it creates a false record that exposes patients, the nurses, and the organization.

What I would do:

1. Separate the day-1 safe set from the rest. Identify the minimum validated competencies required before independent practice (e.g., EHR/medication administration, pump programming, line care) versus those that can be completed within a defined onboarding window with a preceptor.
2. Use unit preceptors and a validated checklist, not the NPD practitioner alone for 14 nurses. Confirm what the agency's competency file already covers so we are not duplicating.
3. Never sign for a skill not observed. Document what was and was not validated.
4. Escalate the conflict to nursing operations. The real problem is a start date set before onboarding capacity existed; that is a staffing decision, and leadership must choose between a delayed start, a restricted assignment, or added preceptor hours.

What would change my answer: a documented, criteria-based validation process with adequate observer time and an approved restricted-practice plan. Convenience alone would not.

Use the minimum necessary standard and redesign the case.

• Remove names, MRNs, exact dates, and rare clinical or geographic details that could re-identify a patient. Verbatim incident narratives are especially high-risk because they often contain identifiers and staff opinions.
• Incident and peer-review material may carry additional legal protection and access restrictions beyond HIPAA depending on state law and organizational policy - check with risk management before circulating anything.
• If the teaching point genuinely requires a real case, either obtain documented permission or build a composite case: same clinical logic, altered details, no identifiers. This preserves learning value at near-zero privacy risk.
• Offer the quality department a written de-identification standard for future education requests so you are not litigating this each time.

Reasoning: the NPD practitioner is accountable for the integrity of the education product and for the ethical use of patient information; "it's just for internal teaching" does not create an exception. If a requester insists on identifiable data, the decision escalates to privacy/risk, not to the educator's discretion.