Every order is original, expert-done, and screened for AI — full report on request.See how it works

Assignment questions
Health Information ManagementPresentationHealth informatics

HCI 670 internal presentation benchmark: a planning guide

The audience is executive leadership, which changes everything — the deck has to justify the work rather than describe it, and the human factors slide is the one that separates informatics from IT.

Editorial process

Last reviewed · August 10, 2026

01

What does an executive audience change about this deck?

The audience specification is the assignment's most important line and the one that decides whether the deck works. This is designed for executive leadership, which means the people watching did not build the form, do not remember the gap analysis, and will not read the notes. They need to know what problem existed, what was done, whether it worked, and how you will know. Everything else is supporting detail. A deck built as a chronological account of your coursework — here is what I did in topic 2, then topic 3 — describes the process to an audience that only wants the argument. Assume every slide will be read in about fifteen seconds and that any question will be about cost, risk or evidence.

Structure the ten to fifteen slides against the six required elements rather than against the timeline. The gap or need is the opening and it should be quantified from the case study wherever the case supplies numbers, because an executive audience reads a stated problem as a claim on resources. The electronic form and the future state workflow are the intervention, and the useful framing is what changed rather than what was built: the navigator previously did X in Y steps across two systems, and now does it in one place at the point of care. Screenshots or a workflow diagram carry that far better than prose. A before-and-after pair of workflow diagrams on adjacent slides is the single most effective thing you can put in this deck, because it makes the change visible without anyone reading a word.

The human factors and user interface slide is the one that distinguishes an informatics presentation from an IT status update, and it is where most decks go thin. Human factors engineering is a discipline with specific principles you can name and apply: designing to the task and its interruptions rather than to the data model, minimising memory load, making errors visible and recoverable, keeping the number of steps and screens down, and using consistency so the interface is predictable. Say which principle drove which design decision. "We made it user-friendly" is not an application of anything, whereas "required fields were reduced from eleven to four because the remaining seven were unavailable at the moment of entry" demonstrates the discipline the course is teaching. Implementation belongs on that slide too, since the brief says design and implementation: training, phasing, and what you did to reduce the burden on people whose workflow changed.

The last two elements are separate and are commonly merged. The evaluation measures are what you will count — completion time, error rate, referrals appearing in the receiving queue, user satisfaction, abandonment. The process for evaluating success is how and when you will count it: baseline before go-live, measurement points afterwards, who collects the data, what threshold counts as success, and what happens if the measure moves the wrong way. An executive audience is used to that distinction, and a deck that gives measures without a process invites the obvious question of who is actually going to check. Include at least one measure that could show the solution failing; a set of metrics that can only improve is not an evaluation.

Slide craft matters here more than in a written assignment, because the notes are explicitly required and that tells you what belongs where. Claims and evidence go on the slide, kept to what can be read at a glance; the reasoning, the caveats and the citations go in the presenter's notes. Three to five credible sources are required and they should be attached to the design and evaluation decisions rather than assembled on the reference slide alone. Usability validation methods for health records and implementation reviews are the natural sources — cite them where you justify a choice, and the deck stops being an assertion about your own work. Keep the reference slide to the same three to five sources rather than padding it, since the cap is part of the specification.

One judgement call worth making deliberately: what to do about limitations. Presenting a completed solution to leadership without any risks or open questions reads as sales rather than analysis, and this is a benchmark being marked by someone who knows the case study. Name what you could not test, what the evaluation will not show, and what would have to be true for the solution to hold at scale. One honest slide near the end will do more for the assessment than another slide of features. It is also what executives are trained to look for, so the deck reads as more credible rather than less.

Likely learning objectives

Inferred from the brief — check these against your own rubric.

  • 01
    Adapt a technical account for an audience that did not do the work.
  • 02
    Justify design decisions by naming the human factors principle behind each.
  • 03
    Distinguish an evaluation measure from an evaluation process.
  • 04
    Use presenter's notes as the place where reasoning and citation live.
Assignment instructionsQuoted verbatim

Read the full question

Review every instruction before using the planning guidance that follows.

The purpose of this assignment is to present the steps taken to identify and solve an EHR problem. This PowerPoint presentation is designed for executive leadership and explains the work done to solve the identified problem in the case study. Create a 10-15 slide PowerPoint presentation overviewing the informatics solution to the identified problems in the \”Integrated Case Study\” resource. Include the following information: Describe the gap/need identified. Describe the electronic form created to assist the oncology RN navigator Describe the future state workflow created to meet the needs of the EHR. Explain how principles of human factor engineering and user interface were integrated into the design and implementation of the informatics solution. Outline the evaluation measures for the informatics solution. Describe the process for evaluating the success of the informatics solution. Include cover slide, reference slide, and presenter\’s notes. Include three to five credible resources to support your findings Overview: Throughout this course, you will use this case study to demonstrate knowledge of the following course content: Clinical decision support Assessing user needs Analyzing and documenting workflow Designing and customizing fields, forms, and templates User testing Evaluation metrics Designing user documentation and training In a series of assignments, you will use this case study to integrate user interface design (including usability/human factor principles) into a design document, analyze and develop workflows, evaluate users’ needs (including their involvement in user testing), develop evaluation metrics, and design end user training materials. The case study, which will be used throughout the course, will focus on various components of the course topics. It focuses specifically on the unique needs of oncology patients and the health care needs of oncology navigators and prior authorization/financial coordinators. The Case: Universal Health is a large not-for-profit health care system with 12 hospitals in three states and two large oncology programs in Arizona. One of the oncology programs is affiliated with Academic Hospital and the other with a larger national oncology health care system. Although both oncology locations are part of Universal Health, there are significant differences in how each of the locations operates due to a recent merger/acquisition of the Academic Hospital oncology program (Oncology South) and the affiliation of the other oncology program (Oncology North) with a national oncology health care system. To compound these operational issues, Oncology North had been part of Universal Health for 8 years, so its Electronic Health Record (EHR) was Chrystal, which was the EHR platform for Universal Health and became the model used to convert Oncology South off its EHR to align with the rest of the organization. Management of oncology patients is quite complex and there was significant concern from Oncology South about the EHR conversion, as well as changes that would affect its operating model. Previously, both oncology programs worked relatively independently with IT to create custom solutions, but now would need to work together to create a standardized oncology solution for Universal Health. If a merger/acquisition of a large academic hospital and its oncology program was not complex enough, adding the conversion of an EHR certainly made the situation more difficult. Also compounding the issue, Oncology North—although it had been on the EHR Chrystal for almost 8 years—had significant issues with the current build and felt that there were several gaps related to functionality for oncology clinicians to service its unique population. Since Universal Health was in the process of converting the EHR at Academic Hospital and Oncology program, the EHR vendor, Chrystal, was actively involving its alignment specialists to assist in the conversion. One of the key first steps of the Chrystal alignment specialists was to do a gap analysis and prioritization of EHR functionality for oncology as well as throughout Universal Health. The gap analysis done by Chrystal found that the oncology build for Universal Health overall did not align to its recommendation for oncology specialties in several areas within the EHR. As a result, a focused team (including a project manager, nursing informatics, Universal Health IT resources, Chrystal oncology alignment specialists, and Chrystal oncology IT experts) was created to systematically address the recommendations from the Chrystal oncology gap analysis. Although there were recommendations globally related to Universal Health’s overall EHR build, there were some specific recommendations related to the build of the oncology platform within Chrystal. Some of the initial focus was related to concerns related to prior authorization/financial gaps and the functionally/workflow of all the oncology providers/clinicians, but also the oncology navigators who really did not have any oncology functionality within Chrystal. Servicing an oncology population is a significant part of the patient demographics of any large health care organization. Oncology patients have unique needs due to the frequency of their visits and the length of their treatments and follow-up, which can last a lifetime. A cancer diagnosis is life changing and can cause great emotional, physical, and financial stress. Oncology navigators exist to assess and assist patients and their families during their cancer treatment and hopefully into remission/survivorship. Unfortunately, cancer treatment can be costly, and dealing with insurance companies for prior authorization is an unfortunate reality in the current health care system. For health care providers, there is great financial responsibility in providing cancer treatment, so obtaining authorization from insurance companies and ensuring that patients are aware of their own financial responsibility are essential for both the patient and the organization. After a patient receives a cancer diagnosis, the next step is usually a referral to an oncology specialist/program like Oncology North or Oncology South. That referral can come from a patient calling an oncology specialist/program directly or from the diagnosing physician contacting an oncology specialist/program. Oncology South and Oncology North both have dedicated intake referral specialists who work directly with patients, families, and referring physicians to get patients scheduled with an oncology specialist based on their diagnosis. Before the patient sees the oncology specialist for the first time, many documents need to be sent to the prior authorization team for review to ensure that the appropriate prior authorization is obtained from the insurance company, as well as making sure that the patient will be seen by the most appropriate oncology specialist for the specifically diagnosed cancer. These documents vary from pathology reports, diagnostic results, and referring physician notes that can be sent to the prior authorization specialist at different times for different patients. It is essential to have a standard workflow and expectation of standard documentation in a certain place in the EHR, so that everyone involved in the initial authorization and clinical care knows what steps have been taken and what actions are pending. While these financial steps are occurring behind the scenes and are important details that need to be secured before a patient’s first appointment, it is worth noting that at this juncture patients have just received some of the worst news in their life and they just want to get treatment as soon as possible. Benchmark – Internal Presentation Paper HCI670 Oncology navigators are nurses that specialize in assisting patients navigate their cancer journey from diagnosis through treatment and into survivorship. After the first contact with the oncology intake specialists, oncology navigators are the next foundational step in the patient’s journey towards treatment and recovery. After the initial documentation is completed by the intake specialist who provides some basic information, including name of person calling, contact information, referral sources, provider information, and diagnosis information, such as type of cancer. Based upon the type of cancer on the intake documentation, an oncology navigator who specializes in that cancer type is notified of the new patient and contacts the patient to initiate a custom navigation plan based upon assessment of needs. The oncology navigator role is an extremely important part of the oncology team. However, oncology navigators were identified as being significantly underdeveloped within Universal Health EHR based upon Chrystal’s gap analysis, so there needed to be focused attention on this group within the organization. As a result, a dedicated team needed to be formed to include individuals from nursing informatics from Universal Health, Chrystal oncology alignment and IT specialists, Chrystal IT staff, and oncology navigators from both Oncology North and Oncology South. This team would be responsible documenting workflow, assessing end user needs, and submitting a final design recommendation (including training materials) to the Universal Health IT build team. The completion deadline for the design document is 8 weeks. Assessing current state and understanding end user needs must be one of the first goals of this dedicated team. Two days were dedicated for onsite observations of oncology navigators at Oncology South and Oncology North, during which it was discovered from the observations that even though the oncology navigators at both locations performed the same role, they had some significant differences that needed to be overcome to be able to collaborate and create a single oncology navigator solution. The grid below outlines some of the differences. Operations Differences Oncology South Oncology North Initial Contact With Patient Phone interview within 3 days Initial physician clinic visit Patient Oversight All oncology patients Only oncology patients that have identified needs Documentation Paper form: See document: Nav Assessment 2018 Paper form: See document: Oncology North Although each location has operational differences, they also have several similarities in how they used some of the tools in the EHR, as well as their need for data and the ability to track/trend the outcomes of their patients. One key request was to make it easier for all oncology clinicians to be able to see their documentation within Chrystal. These foundational similarities aligned to what Chrystal oncology specialists had implemented at other institutions, having already created an Oncology Navigator Recommended Design Document that could be used at Universal Health. The table below provides some similarities between Oncology North and Oncology South. Operations Similarities Oncology North and Oncology South Position Navigator/Coordinator RN Data Request Wanted discrete data for reports Electronic Documentation Used same two electronic methods to chart: 1. Electronic forms shared by all types of navigators (e.g., ortho, pulmonary) 2. Free-text note also shared by same navigators above Electronic Documentation Wanted it to be easier to find specific oncology navigator documentation Health care is all about data. In addition to using EHR for recording documentation, it is used to extract data to evaluate outcomes. Data in the EHR can come from discrete data from ICD10/ICD9 used by providers/coders, SNOMED, IMO codes used clinicians, but also directly from forms and flowsheets from discrete data fields. Understanding the unique data requirements of the oncology navigators, as well the initial prior authorization team, is foundational to creating the appropriate discrete fields or using existing data fields like ICD10 to help sort and organize data. Benchmark – Internal Presentation Paper HCI670.
02

The six required elements and the slide rules

  1. 01
    A 10–15 slide PowerPoint presentation for executive leadership.
  2. 02
    A description of the gap or need identified.
  3. 03
    A description of the electronic form created to assist the oncology RN navigator.
  4. 04
    A description of the future state workflow created to meet the needs of the EHR.
  5. 05
    An explanation of how human factor engineering and user interface principles were integrated into the design and implementation.
  6. 06
    The evaluation measures for the informatics solution.
  7. 07
    The process for evaluating the success of the solution.
  8. 08
    Cover slide, reference slide and presenter's notes, with three to five credible resources.
03

Gap, solution, design rationale, evaluation

01

The gap and why it mattered

State the identified need with a figure from the case study and the consequence of leaving it unaddressed.

02

The form and the future state workflow

Show what the navigator does now versus what they did before, using a diagram rather than prose.

03

Human factors and interface design

Name the principles applied and the specific design decision each one produced.

04

Evaluation measures and process

List what will be counted, then set out when, by whom, against what threshold, and what happens on failure.

04

Where the human factors evidence sits

Recommended databases

  • The Integrated Case Study resource
  • NIST publications on EHR usability
  • PubMed Central and JMIR Human Factors
  • ONC HealthIT.gov

Search sequence

  1. 1.
    Pull every number the case study gives about the gap before designing a slide; an executive deck without a figure on the problem slide is arguing from assertion.
  2. 2.
    Search human factors engineering in health IT for named principles, then match each to a decision you actually made.
  3. 3.
    Search EHR implementation evaluation for the measures other organisations used, which is faster than inventing your own and easier to defend.
  4. 4.
    Keep three to five sources and no more; the brief caps them, and a deck with a dozen citations is not an executive presentation.
05

Sources for usability and implementation claims

These are authoritative starting points, not a ready-made bibliography. A qualified reviewer must confirm that each source fits the assignment and supports the claim beside which it is cited.

Nothing here is cleared for citation until you have read it.

  1. 01

    Technical Evaluation, Testing, and Validation of the Usability of Electronic Health Records: Empirically Based Use Cases for Validating Safety-Enhanced Usability and Guidelines for Standardization

    National Institute of Standards and Technology · 2012

    The standard method for validating EHR usability with safety in view. Cite it on the human factors slide, where it converts a design claim into an application of an established protocol.

  2. 02

    Human factors in healthcare IT: Management considerations and trends

    Journal of Hospital Management and Health Policy · 2023

    Frames usability and human factors as management concerns rather than technical ones, which is exactly the register an executive audience needs. Useful for the slide that explains why design decisions belong on a leadership agenda.

  3. 03

    Mind the Gap: A systematic review to identify usability and safety challenges and practices during electronic health record implementation

    Applied Clinical Informatics · 2016

    Six recurring implementation gaps including workflow analysis, customisation and training. Good support for the evaluation process slide and for the limitations you acknowledge near the end.

  4. 04

    SAFER Guides

    Office of the National Coordinator for Health Information Technology · 2025

    Self-assessment guides for safe health IT use. A source for at least one safety-oriented evaluation measure, which most decks omit and which an executive audience will expect to see.

06

Before you submit the deck

Common mistakes

  • Presenting the coursework chronologically rather than presenting the argument.
  • Stating the gap without any figure from the case study to size it.
  • Describing what was built rather than what changed for the navigator.
  • Claiming the design is user-friendly instead of naming the human factors principle applied.
  • Merging evaluation measures with the evaluation process, so nobody is accountable for measuring.
  • Putting the full argument on the slides and leaving the presenter's notes empty.
  • Attaching the three to five sources only to the reference slide rather than to the decisions they support.
  • Presenting a solution with no limitations, which reads as sales rather than analysis.

Submission checklist

  • Slide count is 10–15 excluding cover and reference slides.
  • The gap is quantified from the case study.
  • The form and the workflow are described in terms of what changed.
  • At least three human factors or interface principles are named and tied to specific decisions.
  • Evaluation measures are listed as countable quantities.
  • The evaluation process names timing, owner and success threshold.
  • Every slide has presenter's notes carrying the reasoning and citations.
  • Three to five credible sources are cited at the decisions they support.
  • At least one limitation or open risk is acknowledged.

Use this guide to plan and review your own work. Follow your institution's rules and read our academic-integrity policy.

Written by

Aaron Bishop

MA, Education

assignment interpretation and research-methods coaching across disciplines

Aaron leads the EssayCrackers editorial desk. He works on how assignment briefs are read — what a rubric is actually asking for, and where students most often answer a different question than the one set.

Reviewed by

Dr. Nathan Cole

PhD, Rhetoric & Composition

Argumentation and thesis development

Nathan teaches first-year composition and directs a university writing center. He reviews EssayCrackers guides for argumentative soundness and citation accuracy.

Want feedback on your plan before you draft?

Get help interpreting the brief, checking your evidence strategy, and strengthening your outline while keeping the work your own.

Get assignment guidance
Start your order