This manual is for MHA-FPX5064 Assessment 2, start to submission. The middle deliverable is specification and selection: requirements written so a tester could pass or fail them, interfaces named as costed pieces of work rather than as settings, and options scored on weights fixed before any vendor presented. Your scoring guide decides whether it arrives as a requirements document, a recommendation or a presentation to a decision making committee, and the graded skill holds across all three, which is whether the specification could survive being written into a contract. Below is the order our tutors build it in, a criterion-keyed structure, and an annotated sample excerpt. Want it done with backup? A premium original sample returns inside 24 to 48 hours, revised free for as long as the criteria need it. Your courseroom may print this as MHA FPX 5064 Assessment 2 or MHA5064 Assessment 2; it is the same deliverable, and MHA-FPX5064 Assessment 2 is what this manual walks through.
One honesty note before the manual: Capella revises courses and scoring guides over time, so always write to the exact scoring guide attached to your assessment in the courseroom. The course identity above is verified on capella.edu; the method and structure below are our tutors' approach to it, not Capella's official rubric text.
How MHA-FPX5064 Assessment 2 is scored
Four levels per criterion, and on a requirements and evaluation deliverable they sort by enforceability:
| Level | What it means on a requirements and vendor evaluation deliverable |
|---|---|
| Distinguished | Every requirement is testable and ranked before demonstrations, non-functional thresholds are stated, each interface is named with its message standard and version, and the scoring weights are stress tested with the decisive priority identified. |
| Proficient | Requirements are specific and the options are compared on stated criteria. Thresholds are missing and the matrix is presented as though it produced an objective answer. |
| Basic | Requirements written as product feature names, interfaces mentioned in passing, and a comparison table with scores nobody can trace to a rule. |
| Non-performance | No evaluation criteria at all, or a recommendation with no requirements behind it. The criterion has nothing to grade. |
The order of operations is itself being marked. Rank the requirements before anybody demonstrates anything, because ranking afterwards means the product you enjoyed watching has quietly become the specification.
The MHA-FPX5064 Assessment 2 method, step by step
-
Write each requirement with four parts
An actor, an action, a condition and a measurable threshold, so a tester could pass or fail it without asking what you meant. The system shall return a completed problem list for a patient identifier in under two seconds at 400 concurrent users is a requirement; modern intuitive interface is a wish.
-
Separate functional from non-functional and write both
What the system does belongs in one list. How fast, how available, how auditable, how recoverable belongs in another, and the second list is where implementations fail and where students write nothing at all. Availability targets, recovery time and audit logging deserve numbers.
-
Rank mandatory, important and desirable before any demonstration
Date the ranking in the document. A specification with a date on it is evidence that the requirements shaped the selection rather than the other way round, and evaluators who have run a procurement will look for exactly that.
-
List every interface with its standard and version
Each interface is a project with a cost, a build, a test cycle and an owner, not a checkbox in a configuration screen. Name the sending system, the receiving system, the message type and the version, and put a price next to each one.
-
Fix the weights, then break them on purpose
Set the criteria and their weights before scoring, then rerun the matrix with a plausible alternative weighting and report what happens. Naming which priority decided the outcome is stronger than presenting a total, and it is much harder for a committee to dismiss.
-
Read every requirement as a vendor would, then self-score
Take one pass looking for any line you could technically satisfy while leaving the organisation unhappy. Tighten those. Then grade yourself criterion by criterion and submit early in the week, since the evaluation window can run to two business days.
A structure that maps to the criteria
Planning ranges our tutors use on a specification deliverable; expand any section your own guide leans on.
| Section | What it must do | Guide |
|---|---|---|
| Need and scope | The problem carried forward from the analysis, sized, with what the system must and must not cover. | ~200 words |
| Functional requirements | Testable statements with actor, action, condition and threshold, each ranked and dated. | ~350 words |
| Non-functional requirements | Performance, availability, recovery, auditability and security thresholds, stated as numbers. | ~250 words |
| Data and interfaces | Elements and definitions, the interface inventory with standards, versions, owners and prices. | ~300 words |
| Options and scoring | Build, buy or configure, the candidates, the pre-set weights, the scores, and the sensitivity run. | ~300 words |
| Recommendation and references | The call, the condition it depends on, standards cited by version, current APA both ways. | as needed |
Annotated sample excerpt
Original model work from our writers, showing how a weighted evaluation reads when its author expects to be cross-examined at a committee.
The weights were fixed by the selection committee on 3 February, before either candidate presented: functional fit 30, interoperability 25, cost of ownership 20, implementation risk 15, vendor viability 10.1 On those weights the incumbent's upgrade path scores 340 and the specialist surgical vendor scores 385, and the gap is carried almost entirely by interoperability, because the incumbent cannot deliver a discrete anaesthesia record to the enterprise data warehouse without a middleware layer it prices separately.2 Rerunning the matrix with interoperability at 15 and implementation risk at 25, which is how the chief nursing officer would weight it, narrows the gap to nine points without reversing it, so the recommendation survives the priority most likely to be contested in the room.3
- 1Dates the weighting and places it before the demonstrations, which is the procedural fact the selection criterion is actually testing.
- 2Identifies the criterion carrying the result instead of quoting a total, and names the technical reason behind it.
- 3Runs an alternative weighting drawn from a real stakeholder's priorities and reports the outcome. A matrix that has tested itself is hard to dismiss.
The full premium sample for your exact assessment, written fresh to your scoring guide and issue, is free to request. Study it, revise it into your own voice, and submit work you understand.
The five mistakes that cost Distinguished
- Feature names as requirements. Statements that cannot be tested and cannot be enforced, which leaves the organisation with nothing to hold anyone to.
- Only the functional half. Performance, availability, recovery and audit thresholds omitted, which is precisely where implementations come apart.
- Interfaces as an afterthought. A proposed system that quietly assumes data will arrive by itself, with no standard, version, owner or price named.
- Weights set after the demonstrations. Criteria that turn out to describe the product the committee already liked, which any experienced reader will notice.
- The matrix as an oracle. A total presented as an objective answer, with no test of what a different priority ordering would do to it.
Pre-submission checklist
- Every requirement carrying an actor, an action, a condition and a threshold
- Non-functional requirements written as numbers, including recovery and availability
- Requirements ranked mandatory, important or desirable, with the ranking dated
- An interface inventory with sending system, receiving system, standard, version and price
- Weights fixed before scoring, then rerun under an alternative weighting
- The decisive criterion named rather than the total, self-scored D, submitted early in the week
Requirements or vendor analysis due?
Send the scenario together with the scoring guide. Our eight-person pipeline returns a premium original sample in 24 to 48 hours with a weighted matrix whose weights come before the scores, an interface list with prices, and one review pass spent only on whether each requirement is genuinely testable.