Using Data for Decision Making: MHA-FPX5064 Assessment 2
Interview subjects will tell you which report they want, not which decision they are trying to make — and the second is the one that determines the data need.
Editorial process
Last reviewed · August 9, 2026
What people ask for is not what they need
The deliverable is an *executive summary*, and treating that as a synonym for 'short report' is the first and most expensive mistake available here. An executive summary is written for someone who will act on it without reading anything underneath it, so it leads with the recommendation rather than building to it, states what it will cost and what it will change, and puts the supporting detail after the ask rather than before. Five to six pages is generous for the genre, which means the marker expects the structure as well as the length: a statement of the problem, what you found, what you recommend, and what happens next. If your document only reveals its recommendation in the final paragraph, it is a report with the wrong label on it, and the assessment is partly about knowing the difference.
Your evidence comes from interviews, and interviews have a characteristic failure mode you should plan around. When you ask professionals at St. Anthony Medical Center what data they need, most will answer with the *report* they want rather than the *decision* they are trying to make. Those are different things, and the second is what actually determines the system requirement. A nurse manager asking for a daily census report may really be trying to predict staffing two shifts ahead, which is a forecasting need rather than a reporting one. So record what each person asked for, but write up what each person is trying to decide, and note where the two diverge. Doing that visibly is the single clearest way to show analysis rather than transcription. Ask the follow-up question in the simulation wherever it is offered, because the second answer is almost always closer to the decision than the first and the interview content is the only evidence base this assessment gives you.
Group the needs before you present them, because a summary organised person by person forces the reader to do the synthesis you were paid to do. Grouping by stakeholder type — clinical, operational, financial, quality and compliance, executive — works well and maps onto how the organisation is actually governed. Grouping by data lifecycle — capture, storage, retrieval, analysis, reporting — works too and has the advantage of pointing directly at where the system gaps sit. Whichever you pick, the pattern you are looking for is the need that appears in more than one group, because a requirement three departments share is both the strongest business case and the cheapest thing to fix. Say which needs are shared and which are local. Say how many people raised each need as well, since a count turns an impression into a finding and gives the executive reading your summary a basis for deciding which requests to fund first.
The brief gives you the organisational context and it should shape the recommendation: Vila Health plans to use *existing* data to develop a strategy for improving and ensuring communication and continuity within its *growing* system. Two words there do a lot of work. Existing data means the answer is unlikely to be a new collection instrument; it is more likely to be about access, integration, standardisation and trust in what is already held. Growing means whatever you recommend has to survive the addition of sites that are not yet in the system, so a solution built precisely around today's departments will be obsolete on arrival. Recommendations that acknowledge both constraints read as though written by someone who read the case rather than someone who knows about data warehouses. Watch for needs that conflict with one another too, because stakeholders who want broader access and stakeholders who want tighter control are both in this hospital and a strategy has to reconcile them rather than pick a side silently.
Remember which department you are writing from. The brief places you in health information management, which means your recommendations carry HIM-specific obligations that a general management answer will miss: data governance and stewardship, master patient index integrity, data quality and completeness standards, retention schedules, release-of-information processes, and the privacy and security constraints that decide who may see what. Stakeholders will ask for things that cannot lawfully be given to them in the form they want, and saying so — with the alternative you would offer instead — is exactly the professional judgement the role implies. It also protects the recommendation, because a data strategy that ignores minimum necessary access will not survive its first compliance review. Name who owns each dataset as well, because a recommendation that does not say whose decision it is to grant or refuse access has left out the step where such strategies usually stall.
Finish by making the recommendation actionable, since that is what an executive summary is for. Name what should be done first and why it is first — usually the shared need with the lowest implementation cost, because early visible value buys the credibility that later work needs. Say roughly what each recommendation requires in people, systems and time, even if only in orders of magnitude, since a recommendation with no cost attached cannot actually be decided on. Say how you would know it worked, which means naming a measure. And follow the APA template the brief supplies rather than a format of your own, because in a course where every assessment builds on the last, consistency of presentation is part of what is being taught. Keep the appendices for the interview detail, since the body of an executive summary should stay readable at speed while the evidence remains available to anyone who wants to check the reasoning behind a recommendation.
What a stakeholder says | What they are usually deciding | The data need underneath |
|---|---|---|
'I need a daily census report' | How to staff the next shift | Short-horizon forecasting |
'I want access to the whole record' | Whether this patient was seen elsewhere | Cross-site continuity, not full access |
'Our numbers do not match finance' | Which figure to trust | A single agreed definition |
'It takes a week to get a report' | Whether to act now or wait | Self-service retrieval |
'We cannot see the referral outcome' | Whether the referral worked | Closed-loop tracking |
'I need it in a spreadsheet' | How to do their own analysis | Export and tooling, not a new report |
'Quality keeps asking for the same data' | How to stop duplicating work | Shared definitions and one source |
'I do not trust that figure' | Whether to use it at all | Data quality and provenance |
Likely learning objectives
Inferred from the brief — check these against your own rubric.
- 01Write in the executive summary genre rather than as a short report.
- 02Distinguish a requested report from the decision that generated the request.
- 03Synthesise interview findings into grouped organisational needs.
- 04Apply health information management obligations to a data strategy.
Read the full question
Review every instruction before using the planning guidance that follows.
What the executive summary must contain
- 01An executive summary of 5-6 pages on the APA template.
- 02The data needs identified through the simulation interviews.
- 03Those needs grouped and synthesised rather than listed by person.
- 04Recommended strategies for meeting them using existing data.
- 05A sequenced first step with a stated reason for its priority.
- 06Governance, quality and privacy constraints addressed.
- 07A measure by which success would be judged.
From interviews to a sequenced recommendation
The recommendation, stated first
Open with what should be done and what it will change.
What the interviews found
Report the needs elicited, separating requests from underlying decisions.
The needs, grouped
Synthesise across stakeholders and identify what is shared.
How existing data can meet them
Propose access, integration and standardisation rather than new collection.
Governance, privacy and sequencing
Set the HIM constraints and name what happens first.
Run the simulation before reading the literature
Recommended databases
- The Vila Health simulation transcripts
- PubMed Central
- AHIMA and HIMSS practice literature
- Capella library health administration databases
Search sequence
- 1.Work the simulation first and take verbatim notes, because the assessment is graded on what you elicited rather than on what the literature says organisations generally need.
- 2.Read on how hospitals actually move data internally, since the brief's concern is communication and continuity within one growing system rather than exchange with outsiders.
- 3.Look for evidence on governance, because that is what turns a list of requests into a defensible strategy and it is the HIM contribution the role implies.
- 4.Find at least one source on measuring the value of a health IT investment, so your recommendations can be justified rather than merely asserted.
Internal exchange, governance and investment value
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.
- 01
Hospitals' adoption of intra-system information exchange is negatively associated with inter-system information exchange
Journal of the American Medical Informatics Association · 2018
Directly on the brief's situation — continuity within a growing multi-site system — and it carries a warning worth citing: solving internal exchange well can make external exchange harder. Useful for the scalability argument.
- 02
Valuing hospital investment in information technology: does governance make a difference?
Health Care Financing Review · 2006
Evidence that governance arrangements change what an IT investment returns, which is how you justify treating data governance as a recommendation rather than as administrative background.
- 03
Successes and Barriers of Health Information Exchange Participation Across Hospitals in South Carolina From 2014 to 2020
JMIR Medical Informatics · 2023
A longitudinal account of what actually blocks data sharing between facilities, which gives your recommendations realistic obstacles to address rather than an idealised implementation path.
- 04
Hospital Investment Decisions in Healthcare 4.0 Technologies: Scoping Review and Framework for Exploring Adoption Determinants
Journal of Medical Internet Research · 2021
Supplies a framework for the determinants behind an adoption decision, which is what an executive summary needs if its recommendation is to be actionable rather than aspirational.
Before the Assessment 2 summary is submitted
Common mistakes
- Writing a report that withholds its recommendation until the end.
- Transcribing interviews person by person instead of synthesising them.
- Recording the report each stakeholder asked for and stopping there.
- Recommending new data collection when the brief specifies existing data.
- Designing around today's departments in a system the brief says is growing.
- Ignoring that you are writing from health information management.
- Omitting data governance, stewardship and master patient index integrity.
- Promising stakeholders access that privacy rules would not permit.
- Making recommendations with no indication of cost or effort.
- Naming no measure of success.
- Substituting your own formatting for the supplied APA template.
Submission checklist
- The recommendation appears early, as the genre requires.
- Needs are grouped by a stated scheme, not by interviewee.
- Shared needs are distinguished from local ones.
- Each need is traced to the decision it supports.
- Recommendations work with existing data.
- Scalability to new sites is addressed.
- HIM obligations — governance, quality, privacy — are covered.
- Any request that cannot lawfully be met has an alternative offered.
- A first action is named and its priority justified.
- Resource implications are stated at least in magnitude.
- The document is 5-6 pages on the supplied APA template.
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.