The Nursing Informatics DNP capstone sits at the intersection of clinical practice, information technology, and organisational systems, making it the most technically complex DNP track and the one most directly connected to the large-scale transformation of healthcare delivery driven by EHR mandates, clinical decision support systems, telehealth expansion, and artificial intelligence in clinical practice. Nursing informatics DNP projects address the unintended consequences of health information technology as much as the intended benefits: alert fatigue that causes clinicians to ignore 90% of CDS notifications, documentation burden that consumes 49% of a physician's time and is increasingly recognised as a nurse burnout driver, and patient portal adoption gaps that undermine the care coordination improvements that patient portals are designed to enable. Expert support is available for all nursing informatics DNP capstone components, all programme formats, and all health information technology settings.
What Makes the Nursing Informatics DNP Capstone Distinct
Nursing informatics DNP projects are distinguished by three features that set them apart from other DNP track projects. First, the intervention often involves modifying technology infrastructure, changing EHR alert logic, redesigning a documentation workflow, modifying a patient portal feature, or implementing a new clinical decision support tool, rather than changing a clinical protocol or staff behaviour directly. This means the informatics DNP student must work with the IT or informatics department, the EHR vendor (Epic, Cerner, Meditech), and often a clinical informatics governance committee in addition to the clinical stakeholders that other DNP projects require. Building these informatics-specific relationships early (before the proposal is finalised) is critical to project feasibility.
Second, the outcome measurement for informatics projects requires data extraction from EHR systems or health IT systems in ways that go beyond the standard quality report. Measuring alert fatigue requires pulling CDS alert response data (alert fire rate, alert override rate, alert type, time-to-response) from the EHR analytics module. Measuring documentation burden requires time-audit data or EHR time-in-chart logs. Measuring patient portal adoption requires extracting patient portal activation rates, message volumes, and MyChart/MyHealth login frequency from the EHR patient engagement module. These data extracts require the informatics team or the IT department to build custom queries, they are not standard quality reports that a unit manager or quality coordinator can run on request. Plan the data access pathway before the IRB submission, not after.
Third, nursing informatics projects often qualify as QI non-research because they modify existing clinical workflows and measure the impact on system performance metrics (alert rates, documentation time, portal adoption) rather than collecting data from individual patients as human subjects. However, if the project involves administering surveys to clinicians or patients, or if the intervention changes care delivery in ways that could affect patient outcomes, the IRB pathway determination must be made explicitly.
High-Value Nursing Informatics DNP Capstone Topic Areas
CDS Alert Fatigue Reduction: Clinical decision support alert fatigue (where clinicians override 90% to 96% of all EDS alerts) is one of the most documented patient safety and clinician burnout problems in health informatics. Nursing informatics DNP projects reducing alert fatigue typically use one of three intervention approaches: (1) alert deactivation or consolidation, identifying low-specificity alerts (alerts that fire frequently but rarely represent true actionable events) using alert analytics data, then working with the informatics governance committee to deactivate or consolidate; (2) alert tiering, modifying alert display to differentiate hard stops (must acknowledge before proceeding) from advisory notifications (informational only); (3) alert targeting, restricting specific alerts to the clinician role or patient context where the alert is most actionable, reducing noise for other roles. Primary outcome: alert override rate (percentage of alert firings where the clinician clicks "override" without taking the recommended action). Data source: EHR CDS alert analytics, Epic Reporting Workbench Alert Activity report or Cerner Discern Analytics alert override report. PICOT starter: "In [nurse practitioners / RNs / physicians] at [facility], does implementation of a nursing informatics-led CDS alert optimisation protocol targeting high-override-rate alerts compared to current unmodified alert configuration reduce the alert override rate..."
EHR Documentation Burden Reduction: Nursing documentation time is a significant contributor to nurse burnout, studies consistently show that nurses spend 25% to 35% of their shift on EHR documentation rather than direct patient care. Intervention options: flowsheet streamlining (removing redundant or rarely-used documentation fields); documentation template restructuring to pre-populate from prior entries; smart text expansion for common narrative entries; nursing order set optimisation to reduce redundant order entry clicks. Primary outcome: documentation time per patient encounter (minutes) measured by EHR time-in-chart log data. Secondary outcome: nurse satisfaction with EHR documentation (EHR satisfaction survey, Likert scale). Data source: Epic EHR Workload Report or Cerner time-in-chart log, requires IT extraction, not available through standard quality reports.
Patient Portal Adoption Programme: Patient portal adoption rates remain low, national average MyChart activation rates are 50% to 65% of eligible patients, with significant disparities by age, race, language, and health literacy. Nursing informatics-led patient portal adoption programme: structured nurse-led portal activation at discharge, bedside activation support during hospitalisation, or targeted outreach to non-activated patients. Primary outcome: patient portal activation rate (percentage of eligible patients with an activated portal account). Secondary outcomes: portal message volume (care team inbox messages from patients); portal-generated medication refill request rate; portal appointment scheduling rate. Data source: EHR patient engagement module activation rate report (Epic MyChart activation dashboard or Cerner HealtheLife portal analytics).
Telehealth Quality Improvement: Telehealth visits expanded dramatically during the COVID-19 pandemic and have partially sustained. Telehealth quality projects: patient satisfaction with telehealth visits (comparing telehealth to in-person visit satisfaction on standardised CAHPS survey items); no-show rate comparison for telehealth vs. in-person visits; technical failure rate and its impact on care delivery (failed video connections, audio-only downgrade rate). Data source: telehealth visit completion log; CAHPS telehealth patient satisfaction survey; EHR appointment status data for no-show comparison.
Nurse Handoff Communication Technology Implementation: Implementing a standardised electronic handoff tool (I-PASS, electronic SBAR, structured discharge summary template) within the EHR to reduce communication failures at care transitions. Outcomes: handoff tool completion rate; communication failure-related adverse events or near-misses; nurse perception of handoff quality (Safety Attitudes Questionnaire communication subscale). Data source: EHR documentation audit for handoff tool completion rate; voluntary event reporting system adverse event log.
Predictive Analytics / Early Warning System Implementation: Implementing a nurse-driven early warning score (National Early Warning Score 2, Modified Early Warning Score, or EHR-integrated sepsis predictive model) with a structured nursing response protocol for deteriorating patients. Outcomes: compliance with early warning score documentation; rapid response team activation rate; code blue rate outside ICU; time from early warning score elevation to first nursing intervention. Data source: EHR early warning score documentation audit; RRT activation log; code blue registry.
Frameworks for Nursing Informatics DNP Projects
Technology Acceptance Model (TAM): The most widely used theoretical framework for nursing informatics DNP projects. TAM (Davis, 1989) posits that two factors determine user adoption of technology: Perceived Usefulness (does the technology improve job performance?) and Perceived Ease of Use (how much effort does the technology require?). TAM provides both the theoretical framework for Chapter 2 and the measurement instrument for evaluating patient portal adoption, EHR documentation workflow adoption, or clinical decision support tool acceptance. The TAM is cited as: Davis, F. D. (1989). Perceived usefulness, perceived ease of use, and user acceptance of information technology. MIS Quarterly, 13(3), 319–340.
ANA Nursing Informatics: Scope and Standards of Practice (3rd edition, 2022): The ANA's Nursing Informatics Scope and Standards provides the professional competency framework for nursing informatics DNP projects, it defines the nursing informatics specialty practice competencies, the ethical standards for health information management, and the standards for clinical information system evaluation that ground the project within the specialty's professional standards. Cite as: American Nurses Association. (2022). Nursing informatics: Scope and standards of practice (3rd ed.). American Nurses Association.
HIMSS Nursing Informatics Workforce Survey Framework: For projects addressing the nursing informatics workforce, EHR satisfaction, or clinical informatics role development, the HIMSS Nursing Informatics Workforce Survey (conducted every 2 years) provides national benchmark data on nursing informatics workforce composition, EHR satisfaction, and informatics competency self-assessment, useful for framing the significance of the gap in Chapter 1.
Donabedian S-P-O Model (for informatics QI projects): Nursing informatics QI projects map cleanly to Donabedian Structure-Process-Outcome: Structure = the EHR system, alert configuration, or documentation template; Process = clinician alert response behaviour, documentation completion rate, portal activation workflow; Outcome = patient safety event rate, documentation time, portal adoption rate.
Iowa Model (for EBP informatics projects): When the informatics project is implementing an evidence-based health IT intervention (patient portal adoption programme, early warning score implementation, structured handoff tool), the Iowa Model provides the translation framework connecting the existing literature to the local implementation decision.
Which health IT problem are you targeting, alert fatigue, documentation burden, patient portal adoption, or telehealth quality?
Nursing informatics DNP capstone support covers EHR analytics data access planning (Epic Reporting Workbench, Cerner Discern Analytics), Technology Acceptance Model and Donabedian framework application, CDS alert optimisation protocol design, Chapter 3 methodology for informatics QI projects, and Results reporting for EHR time-in-chart and alert override data. Share your health system, EHR platform, the specific informatics problem, and the data source that documents the baseline gap.
Working with the EHR Informatics Team for DNP Capstone Data Access
The most common obstacle for nursing informatics DNP projects is data access, specifically, the student's inability to access the EHR analytics modules needed to document the baseline gap and measure post-implementation outcomes. EHR analytics access (Epic Reporting Workbench, Crystal Reports, Cerner Discern Analytics, Meditech) is typically restricted to the clinical informatics team, the IT department, and senior quality staff. To establish data access for a DNP capstone project: (1) Identify the clinical informatics analyst or application analyst responsible for the relevant EHR module (CDS, patient engagement, nursing documentation), this person is your primary technical stakeholder and will determine whether the data extraction is feasible and what the timeline will be; (2) Frame the data request as a quality improvement project extract, not a research data request, QI data extracts are processed through the informatics team without requiring data use agreements in most institutions; (3) Specify the exact data fields needed, the date range, and whether the data can be de-identified at the point of extraction, a precisely specified request gets a faster response than an open-ended request for "CDS alert data"; (4) Build the data access timeline into the project plan, data extraction requests at large health systems often take 4 to 8 weeks from submission to delivery, and this delay must be accounted for in the implementation timeline submitted to the capstone committee.
See also: DNP quality improvement project · Statistical methods for DNP · IRB protocol for DNP
Nursing Informatics DNP Capstone Help: Frequently Asked Questions
What is alert fatigue and how is it measured in a DNP capstone project?
Alert fatigue is the desensitisation of clinicians to clinical decision support (CDS) alerts caused by excessive alert volume, low alert specificity, and high false-positive rates. It is measured in DNP capstone projects using the alert override rate, the percentage of alert firings where the clinician clicks through or overrides the alert without taking the recommended action. A baseline alert override rate above 90% is the standard threshold used in the informatics literature to characterise an alert as suffering from alert fatigue. In Epic, the Alert Activity Report in Reporting Workbench provides override rate data by alert type, clinical role, and time period. In Cerner, the Discern Analytics alert performance report provides equivalent data. The informatics analyst assigned to the CDS module can pull this report for a specified date range and alert subset, request 12 months of data for the specific alerts targeted by the intervention to establish a valid baseline.
Can a nursing informatics DNP capstone be done without a clinical background in the specific EHR being studied?
Yes. Nursing informatics DNP projects are focused on the QI methodology, the change management process, and the outcome evaluation, not on independent configuration of the EHR system. The student does not need to be able to build or modify Epic or Cerner workflows directly; the informatics analyst or application analyst does the technical implementation under the student's direction based on the evidence-based protocol the student has developed. The student's role is to: define the clinical problem and the evidence-based solution; engage stakeholders and obtain governance committee approval for the informatics change; supervise and document the implementation process; and collect and analyse the outcome data. The clinical informatics team is the technical partner who executes the EHR modification. DNP students who are not from an informatics background should identify the clinical informatics analyst as their primary technical stakeholder and include this person in the stakeholder engagement plan from the proposal stage.
Is a nursing informatics DNP project exempt from IRB review?
It depends on the data sources and whether individual patients or clinicians are enrolled as study participants. Nursing informatics projects that use only existing EHR system performance data (alert override rates, documentation time logs, patient portal activation rates) without collecting any data directly from individual patients or clinicians generally qualify for QI non-research determination. Projects that administer surveys to nurses or physicians to measure technology acceptance (TAM instruments, EHR satisfaction surveys) may qualify for exempt review under 45 CFR 46.104(d)(2) if the survey data is collected anonymously and poses no more than minimal risk. Projects that randomise units or departments to receive different CDS configurations, or that involve patient contact for the purpose of portal adoption support, may require expedited review. The IRB determination letter must specifically describe the data sources, "EHR system performance analytics extracted de-identified from Epic Reporting Workbench" is a different risk category than "a survey administered to 50 nurses about their EHR documentation experience." Submit the determination request with a complete data collection protocol and let the IRB coordinator make the determination, do not self-determine exemption without a formal review.
Need expert help with your DNP capstone project?
Get Help NowCommon Questions
What is a DNP capstone project and how is it different from a PhD dissertation?
A DNP capstone project is a practice-focused doctoral scholarly project that applies evidence-based practice, quality improvement, or program evaluation methods to address a clinical problem. Unlike a PhD dissertation, which generates new knowledge through primary research, a DNP capstone translates existing evidence into practice change. It does not require original data collection in most cases and is evaluated on practice impact rather than research contribution.
Which DNP specialisation tracks do you support?
We support all 13 major DNP specialisation tracks: Family Nurse Practitioner (FNP), Adult-Gerontology Acute Care NP (AGACNP), Adult-Gerontology Primary Care NP (AGPCNP), Psychiatric-Mental Health NP (PMHNP), Pediatric NP (PNP), Neonatal NP (NNP), Women's Health NP (WHNP), Certified Nurse Midwife (CNM), Certified Registered Nurse Anesthetist (CRNA), Clinical Nurse Leader (CNL), Nurse Executive/Healthcare Leadership, Population Health, and Nursing Informatics.
Can you help with just one chapter of my DNP proposal or do I need the full project?
You can order help with any individual component: a single proposal chapter, just the PICOT question, just the IRB protocol, or just the data analysis section. You do not need to order the full project. Many students come to us mid-project needing targeted help with one specific deliverable.
Does my DNP capstone project need IRB approval?
Most DNP capstone projects are classified as quality improvement (QI) or program evaluation and do NOT require full IRB review under 45 CFR 46; they qualify for a QI determination or exempt status. However, the determination must be documented. We help you complete the QI determination checklist and, where needed, write the full IRB protocol for exempt or expedited review.