Nursing informatics capstones operate at the intersection of clinical nursing, information technology, and organizational systems. Your project must demonstrate that you understand how data, information, and knowledge flow within healthcare systems — and how nurses can use technology to improve patient safety, care quality, and clinical workflow. The scholarly challenge is connecting the technical intervention (an EHR alert, a documentation redesign, a patient portal workflow) to meaningful clinical outcomes through a rigorous theoretical and evidence-based framework.
What makes informatics capstones distinct
Unlike clinical capstones that target a specific patient population's health outcome, informatics capstones typically target the information systems and workflows that support clinical care. Your intervention might be a change to how nurses document, how clinicians receive alerts, how patients access their records, or how data flows between systems. The outcome measures often reflect workflow efficiency, system adoption, error rates, or alert accuracy — not directly patient mortality or clinical lab values, though patient safety outcomes are the downstream goal.
This creates a specific challenge: your committee may include faculty from both nursing and health IT backgrounds. Your paper must be grounded in nursing theory and EBP methodology, but your technical description of the intervention must be accurate and specific enough to be credible to someone with informatics expertise. Strike the balance by using established informatics frameworks (described below) as your theoretical foundation and citing informatics-specific literature alongside clinical nursing sources.
Topic ideas for the nursing informatics capstone
EHR optimization and documentation
| Topic | Project angle | Primary outcome measure |
|---|---|---|
| Nursing documentation burden reduction | Redesign of the admission assessment flowsheet — eliminate redundant fields, restructure for clinical logic; nurse documentation time audit pre/post | Minutes per admission assessment; duplicate data entry rate |
| Sepsis bundle documentation compliance | Structured EHR template for SEP-1 bundle documentation; nurse completion rate and time-to-antibiotic documentation | SEP-1 bundle documentation compliance rate; time-to-antibiotic order entry |
| Nursing handoff structured note | SBAR-structured EHR handoff template vs. free-text narrative; completeness audit using validated checklist | Handoff note completeness score; post-handoff adverse events (shift-level) |
| Fall risk assessment documentation accuracy | EHR prompt linking Morse Fall Scale score to automatic care plan intervention; accuracy of care plan-to-score alignment | Percentage of high-risk patients with matching fall prevention care plan; fall rate per 1,000 patient days |
Clinical decision support (CDS)
| Topic | Project angle | Primary outcome measure |
|---|---|---|
| Sepsis early-warning alert effectiveness | Evaluation of CDS alert sensitivity/specificity using SIRS or qSOFA criteria; provider response time to alert; alert override rate | Alert positive predictive value; time from alert to treatment initiation |
| Medication alert fatigue reduction | Multi-disciplinary rationalization of duplicate drug-drug interaction alerts; tiered alert severity redesign; alert override rate pre/post | Alert override rate; clinically significant override rate (alert fired, patient had adverse event) |
| Pressure injury risk CDS integration | EHR-embedded CDS linking Braden Scale scores to automatic care plan orders; comparison to manual nursing judgment alone | Pressure injury incidence per 1,000 patient days; Braden reassessment compliance rate |
| Opioid prescribing CDS in primary care EHR | CDS alert requiring ORT score and PDMP check before opioid order; provider override rate and prescribing behavior change | High-dose opioid prescriptions per 100 encounters; ORT completion rate |
Patient-facing technology and engagement
| Topic | Project angle | Primary outcome measure |
|---|---|---|
| Patient portal activation in elderly patients | Nurse navigator–guided portal enrollment vs. passive invitation at discharge; 30-day activation rate by age group | Portal activation rate at 30 days; message volume (proxy for engagement) |
| Telehealth adoption for chronic disease management | Structured nurse-led telehealth onboarding vs. standard patient instructions; attendance rate and technology comfort score | Telehealth visit attendance rate; Patient Technology Comfort Survey scores |
| mHealth app for diabetes self-monitoring | FNP-prescribed glucose-tracking app vs. paper log; app usage rate and HbA1c at 3 months | Daily self-monitoring rate; HbA1c at 3 months |
| Discharge instruction comprehension — electronic vs. paper | Interactive electronic discharge instructions (with video and teach-back prompt) vs. printed paper; comprehension score at discharge | Discharge comprehension score (BHLS or similar); 30-day readmission rate |
Health information exchange and interoperability
| Topic | Project angle | Primary outcome measure |
|---|---|---|
| HIE alert for high-utilizer patients in the ED | Health information exchange alert notifying ED nurses of patients with ≥3 ED visits in 30 days; care coordination follow-up rate | Care management referral completion rate; 30-day repeat ED visit rate |
| Care transitions — medication reconciliation with HIE | Nurse use of HIE medication history at hospital admission vs. patient self-report only; medication discrepancy rate | Medication discrepancy rate per admission; time to completed reconciliation |
Nursing workflow and technology adoption
| Topic | Project angle | Primary outcome measure |
|---|---|---|
| Bar-code medication administration (BCMA) compliance | Re-education plus workflow adjustment vs. re-education alone; BCMA bypass rate pre/post at 60 days | BCMA scan compliance rate; near-miss medication events per 1,000 administrations |
| Nurse perceptions of EHR usability after upgrade | Pre/post EHR upgrade nurse usability survey (System Usability Scale); identify top workflow pain points for targeted redesign | System Usability Scale (SUS) score; number of help desk tickets per nurse FTE |
| Nurse informatics competency training | Structured informatics competency education (NI competency framework) vs. self-directed learning; pre/post knowledge scores | Nursing Informatics Competency Questionnaire (NICQ) scores; EHR use efficiency audit |
Theoretical frameworks for informatics capstones
Informatics capstones require frameworks that address technology adoption, information systems design, or knowledge management — not general clinical EBP frameworks alone. The most commonly used and accepted options:
| Framework | Best suited for | Core concept |
|---|---|---|
| Technology Acceptance Model (TAM) | Patient portal adoption, telehealth uptake, mHealth app use, EHR usability | Perceived usefulness + perceived ease of use → behavioral intention → actual use |
| Staggers & Bagley Smith Nursing Informatics Model | Any informatics capstone — purpose-built for the field | Data → Information → Knowledge → Wisdom; nurses as agents transforming data to wisdom at the bedside |
| DIKW Hierarchy (Data-Information-Knowledge-Wisdom) | EHR documentation, CDS design, data quality projects | Levels of information transformation; wisdom = knowing when to act on knowledge |
| Sociotechnical Systems Theory | EHR implementation, workflow redesign, alert rationalization — human-technology interaction | Technology and social systems co-evolve; technical changes have social consequences (and vice versa) |
| Diffusion of Innovations (Rogers) | New technology adoption, telehealth, patient portal, CDS rollout | Innovators → early adopters → early majority → late majority → laggards; adoption curve factors |
| Clinical Informatics Value Model (AMIA) | CDS evaluation, EHR optimization, system safety projects | Dimensions: patient safety, quality, efficiency, satisfaction — all measurable informatics outcomes |
Informatics capstone structure — section by section
Chapter 1: Introduction and problem statement
Ground the problem in health information technology data. Use statistics on EHR adoption rates, alert fatigue prevalence, medication error rates, or patient portal usage gaps from sources like the ONC (Office of the National Coordinator for Health IT), AHRQ, or HIMSS. Narrow from the national landscape to your specific setting, technology system, and population affected.
Chapter 2: Theoretical framework
Choose a framework appropriate to the informatics context (see table above). Apply it specifically — do not just describe the Technology Acceptance Model in the abstract. Show how perceived usefulness and perceived ease of use map to specific features of the technology your project addresses, and how you will assess each construct in your evaluation plan.
Chapter 3: Literature review
Draw from informatics-focused journals: Journal of the American Medical Informatics Association (JAMIA), Applied Clinical Informatics, CIN: Computers, Informatics, Nursing, Journal of Nursing Informatics, and Health Informatics Journal. Supplement with clinical nursing journals for patient outcome data. Aim for 15–25 peer-reviewed sources from the past 7 years.
Literature search strategy for informatics topics
Informatics literature is split across multiple databases. Search all of these:
- CINAHL: Best for nursing informatics, nursing-focused EHR studies, BCMA, clinical documentation
- PubMed/MEDLINE: Broad clinical informatics, CDS studies, sepsis alerts, medication errors
- Cochrane Library: Systematic reviews on CDS effectiveness, telehealth, mHealth
- IEEE Xplore / ACM Digital Library: Health information systems, interoperability, usability studies
Useful MeSH/CINAHL terms: "clinical decision support systems," "medical order entry systems," "electronic health records/utilization," "alert fatigue," "bar-code medication administration," "patient portal," "telemedicine/utilization," "nursing informatics."
Chapter 4: Project design and implementation plan
Informatics capstones require more technical specificity than other tracks. Your implementation plan should describe:
- Current state: How does the workflow or system currently function? What are the specific gaps (alert fire rate, documentation time, bypass rate)?
- Proposed state: What exactly will change? If proposing an EHR modification, describe the specific screen, flowsheet, or alert logic. If proposing a new technology, describe the platform, configuration, and integration requirements.
- Stakeholders: Who must be engaged? (CMO, CIO, CNO, nursing informatics team, IT, clinical unit champions, end users) What is the approval pathway for EHR changes at your institution?
- Change management approach: How will staff be trained? What is the communication plan? Who handles go-live support?
- Timeline: EHR changes require build time, testing, and validation before go-live. A realistic informatics implementation runs 8–16 weeks from approval to live rollout. Account for this in your timeline.
Chapter 5: Evaluation plan
Informatics evaluation typically uses a combination of system-generated data and user perception surveys:
| Outcome type | Common measures | Data source |
|---|---|---|
| System adoption | Login rate, feature utilization rate, portal activation rate | EHR analytics module; IT reporting dashboard |
| User experience | System Usability Scale (SUS); TAM perceived usefulness/ease-of-use survey | Post-implementation survey |
| Workflow efficiency | Documentation time (minutes/task), alert response time, BCMA scan rate | EHR time-stamp audit; workflow time-motion study |
| Safety outcomes | Medication error rate, near-miss rate, adverse drug event rate | Incident reporting system; pharmacy adverse drug event log |
| Clinical outcomes | CLABSI rate, sepsis bundle compliance, fall rate, 30-day readmission | Quality/infection control department; EMR data extract |
Common informatics capstone mistakes
- Proposing EHR changes without IT partnership: In most health systems, nurses cannot directly modify EHR flowsheets, alerts, or order sets — those changes require a formal IT request, build time, and governance approval. Your implementation plan must describe the IT partnership and governance pathway, not just the desired end state.
- Using only clinical frameworks: Applying the Iowa Model or Lewin's Change Theory to an informatics project is technically acceptable but misses the depth expected. Use an informatics-specific framework (TAM, Staggers-Smith, DIKW) as your primary foundation.
- Underestimating alert rationalization complexity: CDS alert projects that require physician and pharmacy buy-in to reduce alert categories involve political and clinical governance processes that can take 6–12 months. Scope your project realistically — a pre/post audit and recommendation proposal is more feasible than a full rationalization implementation.
- Conflating technical capability with clinical value: Just because a technology CAN do something does not mean it SHOULD. Your evaluation plan must measure clinical or operational outcomes — not just that the technology was implemented successfully or that staff completed training.
Need your nursing informatics capstone written?
Our writers understand EHR systems, CDS design, informatics frameworks, and nursing workflow — full capstone papers built around your program's rubric.
Start your capstone More MSN topicsRelated guides
Frequently asked questions
No — nursing informatics is a clinical and organizational discipline, not a software engineering one. Your capstone is evaluated on nursing science, EBP methodology, and informatics theory — not on your ability to write code or configure EHR systems. What you do need is enough understanding of how the technology works (at a functional level) to describe your intervention accurately, identify realistic stakeholders and workflows, and choose outcome measures that the system can actually generate. This comes from your informatics coursework, your workplace, and reading the implementation literature for your chosen technology.
Yes, but it requires more work in your implementation plan. If you are proposing a technology your site does not currently have, you must describe the procurement, implementation, and training pathway — not just the clinical protocol. This is feasible for an EBP proposal format but significantly more complex for a QI implementation project. Most informatics capstones are strongest when they address a real gap in a technology the student's site already uses (e.g., improving BCMA compliance, reducing alert fatigue in an existing Epic installation).
A nursing informatics capstone is grounded in nursing theory, nursing workflow, and the impact on nurses and patients. A health IT project might focus on technical architecture, data standards (HL7, FHIR), or software implementation without the clinical and human factors lens. Your capstone must demonstrate nursing knowledge — the theoretical framework chapter and literature review ground your work in nursing informatics science (Staggers-Smith, DIKW) rather than just IT project management. This is the distinction your committee will look for.
Not automatically — you must submit for a formal IRB exemption determination. De-identified data accessed for QI purposes is usually classified as exempt or as non-research, but that classification must come from your IRB office, not from your own judgment. Additionally, accessing de-identified data from an institution's EHR system requires a data use agreement with the facility's privacy officer or research administration office, separate from IRB review. Start both processes early — they run in parallel and both take time.