| Course | MHA FPX 5064 Health Information Systems Analysis and Design for Administrators |
|---|---|
| Assessment | Assessment 1 |
| Paper type | Requirements definition |
| Length | About 1,070 words, 5 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | Master of Health Administration (MHA) |
| Updated | September 2026 |
Free sample paper for MHA FPX 5064 Assessment 1
Writing Requirements Before Choosing a Product: Referral Management for a Multi-Clinic Specialty Network
Student Name
Capella University
MHA FPX 5064: Health Information Systems Analysis and Design for Administrators
Instructor Name
Month Day, Year
Introduction
A composite specialty care network, here called Lakeshore Specialty Partners, operates 11 clinics in cardiology, orthopedics, gastroenterology, and neurology. It receives about 2,300 referrals a month from primary care practices, most by fax. Staff track referrals in spreadsheets, and a review of three months of referrals found that 17% were never scheduled, and that the median time from referral receipt to scheduled appointment was 19 days. Leadership has approved a search for a referral management system. This paper sets out the requirements before any product is examined.
Written Before Any Product
Writing requirements before looking at products prevents vendors' features from defining the organization's needs. The international standard for requirements engineering describes requirements as statements of what a system must do to meet stakeholders' needs, written so that they can be verified, without prescribing a particular design (International Organization for Standardization, 2018). No product is named in this document. Requirements written before any demonstration describe the organization's work; requirements written after a demonstration tend to describe the product.
Needs Identified
Requirements are traced to five needs identified through interviews with referral coordinators, schedulers, physicians, clinic managers, and three referring primary care practices. N1: Every referral received is tracked until it is scheduled, declined, or closed. N2: Referrals are reviewed for completeness and urgency quickly. N3: Referring practices know the status of their referrals without calling. N4: Managers can see volumes, delays, and outcomes by clinic and referral source. N5: Clinical information in referrals reaches the specialist before the visit.
Each One Testable
Each requirement is written so that a tester can determine whether a system meets it.
| ID | Requirement | Test | Need | Priority |
|---|---|---|---|---|
| R1 | Every referral received by fax, electronic referral, or health information exchange message creates a record with a unique identifier within 5 minutes of receipt | Send 20 test referrals by each channel; confirm records and timestamps | N1 | Essential |
| R2 | Each open referral displays its status, days since receipt, and assigned coordinator | Inspect 20 records | N1 | Essential |
| R3 | Referrals open more than 5 business days without a scheduled appointment appear on a work queue | Create test referrals and advance dates | N1 | Essential |
| R4 | Coordinators can mark a referral incomplete and send a request for missing items to the referring practice from within the system | Perform the task for 5 test referrals | N2 | Essential |
| R5 | Referring practices can view status of their referrals through a secure portal or electronic message | Log in as a test referring practice | N3 | Essential |
| R6 | Reports show referrals received, scheduled, declined, and never scheduled, by clinic and source, for any date range | Run report for test data and compare with known totals | N4 | Essential |
| R7 | Attached clinical documents are visible in the specialist's view of the patient before the visit | Attach document, check specialist view | N5 | Essential |
| R8 | The system suggests an urgency level based on diagnosis codes | Enter test referrals with urgent codes | N2 | Desirable |
| R9 | Referring practices receive automatic notification when the patient is seen | Complete a test visit | N3 | Desirable |
Essential Separated From Desirable
A requirement counts as essential when a system lacking it would leave the original problems unsolved. Desirable requirements add value but are not reasons to reject a product. The distinction matters because vendors often lead with desirable features, such as automated urgency scoring, which can distract from whether a product meets the basic tracking need. Seven requirements are essential and two are desirable. Any product that fails an essential requirement will be excluded, however attractive its other features.
Stakeholders Who Disagree
Stakeholders disagreed about two requirements. Physicians wanted every referral to be reviewed by a physician before scheduling, to catch inappropriate referrals. Referral coordinators and clinic managers argued that physician review would add days to every referral and that most referrals are routine. The requirements resolve this by making physician review a configurable step that can be applied to selected referral types, such as new cancer diagnoses, rather than to all. Referring practices wanted automatic notification when their patient is seen (R9), but some specialists were concerned that notifications would be sent before the specialist's note is complete. R9 is therefore desirable rather than essential, and any product will need to allow the timing of notifications to be set by clinic. Recording disagreements, and how they were resolved, shows vendors and future staff why the requirements look the way they do.
Traceable to a Need
Every requirement traces to at least one need, and every need has at least one essential requirement. This traceability serves two purposes. During vendor evaluation, it shows which needs a product gap would leave unmet. After implementation, it allows the network to check whether the system solved the original problems: whether the 17% of referrals never scheduled has fallen, whether the 19-day median has shortened, and whether referring practices call less often to ask about status.
How the Requirements Will Be Used
The requirements will be used in three stages. In the request for proposal, vendors will be asked to state, for each requirement, whether their product meets it now, will meet it in a named future release, or does not meet it. In scripted demonstrations, the evaluation team will run the tests listed for each essential requirement using Lakeshore's own test referrals rather than the vendor's prepared data. After implementation, the same tests will be repeated during acceptance testing before the network signs off on go-live. Using one set of requirements at all three stages keeps the evaluation consistent and prevents requirements from quietly changing to match whatever product is chosen.
Nonfunctional Requirements
The system must also meet requirements that are not tied to a specific task: it must protect patient information in accordance with federal privacy and security rules, support 60 concurrent users without delay, be available at least 99.5% of clinic hours, and export all data in a standard format if the network changes systems. Nonfunctional requirements are tested like the others, through security documentation, load testing, and a trial export.
Conclusion
Lakeshore's requirements for referral management were written before any product was considered. Each is testable, essential requirements are separated from desirable ones, disagreements among stakeholders are recorded and resolved, and every requirement traces to a need that can be measured after implementation.
References
International Organization for Standardization. (2018). Systems and software engineering: Life cycle processes: Requirements engineering (ISO/IEC/IEEE Standard No. 29148:2018).
What the MHA FPX 5064 Assessment 1 instructions ask for
The first assessment in MHA FPX 5064 asks you to define the needs and requirements for a health information system. You establish the operational need with evidence, identify stakeholders and what each needs, write requirements that can be tested, classify them as essential or desirable, trace each to a need and include nonfunctional requirements such as security, performance and interoperability. Requirements should describe what the system must do, not which product to buy. Stakeholders include clinicians, schedulers, billing staff and IT. Regulatory requirements, such as HIPAA security, belong in the list. The requirements carry into the workflow mapping and vendor evaluation later in the course.
Inside the MHA FPX 5064 Assessment 1 example
Need, stakeholders, requirements, priority. The opening establishes the operational need the system would serve, with evidence that it is real. A stakeholders block identifies whose requirements these are, since clinicians, administrators and billing staff want different things and a specification serving only one will be resisted by the others. A requirements block states each as a testable capability, grouped by function. A priority block separates essential from desirable with a reason for each classification. A constraints block covers what the environment imposes: existing systems, regulatory obligations, budget. A traceability block links each requirement to the need it came from. The closing states what is deliberately out of scope. Nothing names a product, and every requirement could be demonstrated or refused.
Where the marks sit in the MHA FPX 5064 Assessment 1 scoring guide
The scoring guide rates the needs, the stakeholders, the requirements, the prioritization and the traceability. Requirements reach Distinguished when each is testable, such as sends a referral status update to the referring office within one business day. Stakeholder analysis scores higher when disagreements are named and resolved, for example specialists wanting full records while front desk staff want a short intake form. Prioritization earns credit when essential requirements are separated from desirable ones with reasons, since the essential list will later eliminate vendors. Traceability rewards linking each requirement to a need, so nothing is on the list without a reason. Nonfunctional requirements, such as security, uptime and response time, show completeness. Writing the list before naming products prevents bias. Clear writing and APA references are graded as well.
MHA FPX 5064 Assessment 1 help from the desk
Students often start with a product and write requirements that describe its features, which quietly decides the selection before it starts. Another common mistake is writing requirements that cannot be tested, such as user friendly or efficient. Every requirement is marked essential, which makes selection impossible, since no product meets a list of fifty essentials. Stakeholder conflicts are ignored and resurface during implementation. Nonfunctional requirements, such as uptime, backup and data security, are left out. Requirements are not traced to needs, so some exist only because a vendor demo mentioned them. A numbered table with the requirement, its priority, its source need and how it would be tested is the format vendors and committees understand. Keep the list short enough to use.
Get a MHA FPX 5064 Assessment 1 example written to your instructions
Send the Assessment 1 instructions and the scoring guide from your MHA FPX 5064 courseroom, plus the need or scenario your version supplies. We write a custom example against those exact criteria and return it in 24 to 48 hours. The first custom sample is free, and writing requirements that could be demonstrated or refused is the discipline worth taking from it. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More MHA FPX 5064 papers and MHA samples
- MHA FPX 5064 Assessment 2: Current and Future State Workflow
- MHA FPX 5064 Assessment 3: Design or Selection Argument
- MHA FPX 5068 Assessment 1: Technology Evaluated Against Goals
- MHA FPX 5042 Assessment 1: Personal Leadership in a Health Care Setting
- MHA FPX 5001 Assessment 1: Profession and Scholarly Writing Orientation
- MHA FPX 5040 Assessment 1: Assessing Readiness for Change
MHA FPX 5064 Assessment 1 questions, answered
What makes a requirement testable?
You could watch somebody try it and say whether it worked. The system must produce the report within a stated time is testable; the system must be user friendly is not. If two people could disagree about whether a product satisfies it, the requirement needs rewriting rather than interpreting.
How do I handle stakeholders who want different things?
Record both and mark the conflict rather than resolving it silently. Clinicians wanting fewer clicks and billing wanting more captured fields is a genuine tension. Naming it lets whoever selects the system make the trade deliberately instead of discovering it after purchase. Deliberate trades beat discovered ones.
Should regulatory requirements be in the list?
Yes, as essential requirements with their source cited. A system that cannot meet a mandatory obligation is not a candidate, so treating compliance as a separate discussion risks a shortlist containing products that were never viable. Expressing it as a requirement keeps the selection honest.
Where can I find a free MHA FPX 5064 Assessment 1 sample paper?
This page contains the full referral management requirements, with testable requirements, essential and desirable priorities, stakeholders, traceability and nonfunctional needs. A custom list for your system is available free.
What makes a requirement testable in MHA FPX 5064 Assessment 1?
It states a specific behavior someone could check, with a measure where possible, such as the system alerts the scheduler when a referral is unscheduled after five days, rather than a vague quality.