| Course | MHA FPX 5064 Health Information Systems Analysis and Design for Administrators |
|---|---|
| Assessment | Assessment 3 |
| Paper type | Vendor selection argument |
| Length | About 1,090 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 3
Evaluating Referral Management Vendors: Screening on Essential Requirements, Admitting Gaps, and Costing Over Five Years
Student Name
Capella University
MHA FPX 5064: Health Information Systems Analysis and Design for Administrators
Instructor Name
Month Day, Year
Introduction
Lakeshore Specialty Partners, a composite network of 11 specialty clinics, wrote requirements for a referral management system before looking at any product. Seven were essential and two desirable. Four vendors responded to a request for proposal: Vendor A, a module offered by the network's electronic health record vendor; Vendors B and C, stand-alone referral management products; and Vendor D, a patient engagement platform with a referral feature. This paper evaluates them.
Essential Requirements Screen First
Each vendor was tested against the seven essential requirements in a scripted demonstration using Lakeshore's test referrals, not the vendor's own demonstration data. A vendor that failed any essential requirement was excluded before other factors were considered.
| Requirement | A | B | C | D |
|---|---|---|---|---|
| R1 Every referral creates a tracked record | Pass | Pass | Pass | Fail (fax referrals not captured) |
| R2 Status and days open visible | Pass | Pass | Pass | Pass |
| R3 Aging work queue | Pass | Pass | Pass | Pass |
| R4 Request missing items from referring practice | Partial | Pass | Pass | Pass |
| R5 Referring practice status view | Pass | Pass | Fail (portal in development) | Pass |
| R6 Volume and outcome reports | Pass | Pass | Pass | Partial |
| R7 Clinical documents in specialist view | Pass | Partial | Partial | Fail |
Vendors C and D failed at least one essential requirement and were excluded. Vendor A was rated partial on R4 because requests for missing items can be sent only by fax, not electronically; Vendor B was rated partial on R7 because documents appear in the specialist's view only after a manual step. Screening on essential requirements first stops attractive features from carrying a product that cannot do the basic job.
Gaps in the Preferred Option Admitted
Vendor A is the preferred option, mainly because it shares the electronic health record's patient data and would place referrals directly in the specialist's view. Its gaps must be stated honestly. It cannot send electronic requests for missing items, so coordinators would continue using fax for that step. Its reporting requires the record vendor's separate analytics tool for trend reports across clinics. It does not include either desirable requirement: automated urgency suggestions or automatic notification to referring practices when patients are seen. These gaps are not reasons to exclude Vendor A, but the network should not expect them to be solved by the purchase.
Cost Over a Period, Not a Price
Comparing quoted prices would favor the lowest license fee. Comparing cost over five years, including implementation, interfaces, training, and internal staff time, gives a truer picture.
| Cost over five years (dollars) | Vendor A | Vendor B |
|---|---|---|
| Licenses and subscription | 410,000 | 330,000 |
| Implementation services | 120,000 | 160,000 |
| Interfaces with electronic health record | 0 | 140,000 |
| Interface maintenance | 0 | 75,000 |
| Internal staff time for implementation | 95,000 | 150,000 |
| Training | 40,000 | 55,000 |
| Total | 665,000 | 910,000 |
Vendor B's license fees are lower, but it requires interfaces to and from the record, and more internal staff time, making it about 245,000 dollars more expensive over five years.
Vendor Claims Labeled
Several statements in vendor proposals could not be verified during the evaluation and are labeled as claims. Vendor A claimed that electronic requests for missing items would be available in a release scheduled within 12 months. Vendor B claimed that its customers reduced unscheduled referrals by 40% on average, but provided no data source or study. Both vendors claimed their systems support health information exchange referrals, which was tested for Vendor A but only described for Vendor B. Labeling claims keeps promises about future releases and customer results from being treated as facts in the decision.
Scoring the Remaining Vendors
After the essential requirements screen, Vendors A and B were compared on factors weighted in advance by the evaluation team: fit with daily workflow (30%), five-year cost (25%), integration with the electronic health record (20%), vendor stability and support (15%), and desirable requirements (10%). Coordinators and schedulers scored workflow fit after using each product for a half-day of simulated referrals. Vendor A scored higher on integration and cost, while Vendor B scored slightly higher on workflow fit because its work queues were easier to filter. The weighted totals favored Vendor A, 4.1 to 3.6 on a five-point scale. Fixing the weights before scoring prevented the team from adjusting them after seeing which vendor it preferred.
Risks of the Preferred Option
Choosing the record vendor's module has a risk that the evaluation should state: it deepens Lakeshore's dependence on one vendor, which may weaken its negotiating position at renewal and ties the referral system's future to that vendor's priorities. The risk is accepted because integration is the main source of value, but the contract should include price protection for renewal and the data export rights described below.
Recommendation
Lakeshore should select Vendor A. It passed every essential requirement except one, where its gap is partial and manageable, costs less over five years, and integrates directly with the record the specialists use. Its gaps should be addressed through process changes, such as a templated fax for missing items, and through contract terms. The referral coordinators, who will use the system most, supported the choice after the half-day trial, although they asked that their preference for Vendor B's work queue filters be passed to Vendor A as an enhancement request. That request, and the missing-item feature, should be tracked at every quarterly vendor meeting after go-live so that promised improvements are not forgotten once the contract is signed.
What to Verify Before Signing
Before signing, Lakeshore should verify five things. First, the contract should include the release date for electronic missing-item requests as a commitment, with a remedy if it is missed. Second, the network should speak with at least two current customers of similar size about implementation time and support. Third, the cost of the separate analytics tool for trend reports should be confirmed and added to the five-year cost if required. Fourth, the contract should specify that Lakeshore owns its referral data and can export it in a standard format. Fifth, the vendor should confirm in writing the staffing it will provide during implementation. The requirements document's standard for verifiable requirements applies equally to the contract (International Organization for Standardization, 2018).
Conclusion
Screening on essential requirements excluded two of four vendors. The preferred option, Vendor A, has admitted gaps, costs less over five years, and integrates with the record. Vendor claims are labeled as claims, and five items should be verified before signing.
References
International Organization for Standardization. (2018). Systems and software engineering: Life cycle processes: Requirements engineering (ISO/IEC/IEEE Standard No. 29148:2018).
The Capella MHA FPX 5064 Assessment 3 instructions
The final assessment asks you to argue for a system design or selection based on your requirements and workflow analysis. You identify candidate systems or designs, screen them against essential requirements, score the remaining ones against desirable requirements, estimate total cost of ownership over several years, assess risks, make a recommendation and list what must be verified before a contract. Vendor information should be labeled as claims unless independently confirmed. Reference calls, demonstrations and published reviews help. Cost should include licenses, implementation, interfaces, training and support. The argument should be traceable to the requirements from Assessment 1.
Inside the MHA FPX 5064 Assessment 3 example
Candidates, essential screen, desirable scoring, cost, decision. The opening names the options and where they came from. An essential block screens each against the mandatory requirements, eliminating anything that fails one and saying which. A scoring block assesses survivors against the desirable requirements with the evidence for each judgment. A gap block states where the preferred option falls short, together with how the organization would cope without that capability. A cost block totals purchase, implementation, interfaces, training and ongoing license over a stated period. A decision block commits, with the reasoning compressed beneath it. A risk block identifies where this particular choice could disappoint and how that would show. The closing states what the organization should verify before signing. Vendor claims are labeled as vendor claims throughout.
Reading the MHA FPX 5064 Assessment 3 scoring guide
The scoring guide rates the candidate identification, the screening, the scoring, the cost analysis, the risks and the recommendation. Screening reaches Distinguished when essential requirements eliminate candidates that fail any one, with the failed requirement named. Scoring scores higher when desirable requirements are weighted and applied consistently to every survivor. Cost earns credit when calculated over a period such as five years, including recurring license, support and interface costs. Admitting gaps in the preferred option shows honesty and prepares leaders for them. Labeling vendor claims, and saying which were confirmed by reference sites, shows rigor. The recommendation should follow from the screening and scoring. A pre-signing verification list shows practical judgment, and a clear table of scores makes the argument easy to follow. Writing and APA are graded.
MHA FPX 5064 Assessment 3 help from the desk
Students often compare vendors on price alone, which ignores what each product can actually do. Another common mistake is scoring every requirement equally, so a minor feature outweighs an essential one. Vendor marketing is treated as fact rather than as claims to verify. The preferred option's weaknesses are hidden, which leaves leaders surprised after signing. Five-year costs are missing, especially interface maintenance and annual support fees that often exceed the first-year license. Risks, such as vendor stability or a product being retired, are ignored. Reference calls with similar organizations are skipped. A verification list, covering reference sites, a demonstration with your own workflows and contract terms, protects the organization before it commits.
Get a MHA FPX 5064 Assessment 3 example written to your instructions
Send the Assessment 3 instructions and the MHA FPX 5064 scoring guide from your courseroom, with the requirements and workflow analysis your earlier assessments produced. We write a custom example against those exact criteria and return it in 24 to 48 hours. The first custom sample is free, and screening on essentials before scoring anything is what keeps a selection defensible. 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 1: Writing Requirements Before Choosing a Product
- MHA FPX 5064 Assessment 2: Current and Future State Workflow
- MHA FPX 5068 Assessment 3: Governance Training and Accountability
- MHA FPX 5042 Assessment 3: Personal Leadership Targets Drawn From the Team's Needs
- MHA FPX 5001 Assessment 3: Professional Development Plan
- MHA FPX 5040 Assessment 3: Sustaining a Change After the Launch
MHA FPX 5064 Assessment 3 questions, answered
How do I evaluate systems I cannot trial?
Use published documentation, reference sites and what comparable organizations report, and label each. Say what you could not verify and list it among the things to test before signing. An honest evaluation naming its own limits is stronger than a confident one built on marketing material.
What if no option meets every requirement?
That is the normal outcome. Screen on essentials, score the survivors, and state plainly where the winner falls short and what the organization will do instead. A selection acknowledging a gap and planning around it is far more useful than one that quietly relaxes a requirement.
How far ahead should cost be calculated?
Over the period the organization would realistically keep the system, which for clinical systems is often five to ten years. Purchase price is usually a minority of the total once implementation, interfaces, training and licensing are counted, and a comparison on price alone reliably picks the wrong system.
Where can I find a free MHA FPX 5064 Assessment 3 sample paper?
This page contains the full referral management vendor evaluation, with the essential screen, weighted scoring, five-year cost, admitted gaps, risks and verification list. A custom evaluation is available free.
What if no option meets every requirement in MHA FPX 5064 Assessment 3?
Revisit whether each failed requirement is truly essential, then recommend the option with the most manageable gap and state how the gap will be closed, such as a workaround or custom interface.