MHA FPX 5064 guide: systems analysis and design workload

MHA FPX 5064 at a glance: requirements, workflow, vendors

The course follows the early stages of a system project. The requirements assessment defines what a system must do, written before any product is considered. The workflow assessment maps how work happens now and how it should happen with the new system. The vendor assessment compares referral management products against the requirements.

Referral management is a strong example because referrals cross organizational boundaries, involve many roles and often fail: lost faxes, missing information and patients who never complete the specialist visit.

Plan 35 to 40 hours, with workflow mapping taking the longest.

MHA FPX 5064 Assessment 1: writing requirements before choosing a product

The requirements assessment asks you to define what a system must do. Separate functional requirements, such as sending referrals electronically, tracking status and notifying the referring provider of results, from non-functional requirements, such as security, usability, uptime and integration with the electronic health record.

Write each requirement as a clear, testable statement, and rank them as must-have, should-have or nice-to-have. Involve stakeholders: referring physicians, specialists, schedulers, patients and IT.

Points slip when requirements describe a particular product's features. Faculty want needs stated independently, so they can later be used to judge any product.

MHA FPX 5064 Assessment 2: current and future state workflow

The workflow assessment maps the referral process as it works now and as it should work. Use swim-lane diagrams showing each role, step, handoff and decision.

For the current state, mark delays, rework, missing information and points where patients drop out. Gather data where you can, such as referral completion rates or average days to appointment.

For the future state, show how the new system and process changes remove those problems. Explain what changes for each role. A future-state map that only adds technology to a broken process misses the purpose of the assessment.

MHA FPX 5064 Assessment 3: evaluating referral management vendors

The vendor assessment compares products against your requirements. Build a weighted scoring matrix: list requirements, assign weights by priority and score each vendor.

Gather information from vendor materials, independent reviews, analyst reports and references from other organizations. Consider total cost of ownership, including licenses, implementation, training, interfaces and ongoing support.

Recommend a vendor or a short list for demonstrations, and explain the reasoning. Faculty reward evaluations that are transparent about criteria and honest about uncertainty, since public information on products is often incomplete.

MHA FPX 5064 and the systems development life cycle

The course covers early stages of the systems development life cycle: planning, analysis and design, before selection and implementation. Understanding the full cycle helps you explain why careful requirements and workflow work matter.

Mistakes made early, such as missing a requirement for EHR integration, become expensive later. Studies of failed health IT projects often trace problems to poor requirements and weak stakeholder involvement.

Mentioning the life cycle and where each assessment fits shows faculty that you see the project as a whole.

MHA FPX 5064 stakeholder involvement

Systems succeed when users shape them. Referral management affects primary care physicians, specialists, nurses, front-desk staff, schedulers, patients and IT teams, each with different needs.

Describe how you would involve them: interviews, observation, workshops to review workflow maps and user testing during vendor demonstrations.

Address conflicts between groups. Specialists may want detailed clinical information before scheduling, while referring offices want a simple process. Showing how requirements balance these needs demonstrates administrative judgment.

Record who you would consult for each requirement.

Where MHA FPX 5064 papers fall short

Common weaknesses include requirements written as product features, workflow maps too general to show problems, future states that simply digitize the current process and vendor evaluations without weighted criteria or cost analysis.

Another frequent gap is ignoring interoperability. A referral system that does not connect to the EHR and to outside practices will force staff to re-enter data.

Faculty also reward measurable goals. Stating that the new process should raise referral completion from a baseline to a target gives the project a clear purpose.

Sources for MHA FPX 5064

Useful sources include ONC for interoperability and health IT standards, AHRQ for health IT and care coordination research and HIMSS for systems analysis and selection guidance.

Peer-reviewed studies on referral loop closure and electronic referral systems provide evidence on what works. Research on electronic consultation programs offers additional examples.

Vendor websites and analyst reports, such as KLAS research, can inform the vendor assessment, but treat marketing claims with caution and note their source.

Date every vendor claim you cite, since products change with each release.

Pacing MHA FPX 5064

On FlexPath, a common rhythm is a week and a half for requirements, two weeks for workflow mapping and a week and a half for vendor evaluation.

On GuidedPath, the quarter's due dates apply, so begin observing or researching the referral process during the first week.

Keep a single requirements list and update it as workflow mapping reveals new needs. The vendor evaluation will use the final version.

Save each version of your workflow maps; the change from current to future state is itself useful evidence in the second paper.

Getting help with MHA FPX 5064

Requirements writing and workflow mapping take practice. A health administration writer with health IT experience can draft the requirements, the workflow maps and the vendor evaluation for you to review and submit.

If you work with referrals, share how the process runs in your setting, in general terms. Real detail makes the maps and requirements far more convincing, and the final choices are yours.

Help can also cover only the workflow maps, which take the most time, while you write the requirements and vendor evaluation yourself.

Measuring referral success in MHA FPX 5064

A new referral system should be judged by results. Key measures include referral loop closure, meaning the share of referrals where the specialist visit happens and results return to the referring provider; days from referral to appointment; the percentage of referrals with complete information; and patient no-show rates for specialist visits.

Set baselines from current data or published studies, then targets for the future state.

Including measures in the workflow and vendor assessments shows faculty that the project aims at better care, not just new software, and gives leaders a way to judge the investment.