| Course | MHA FPX 5064 Health Information Systems Analysis and Design for Administrators |
|---|---|
| Assessment | Assessment 2 |
| Paper type | Current and future state workflow |
| Length | About 1,080 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 2
Mapping Prior Authorization Before and After an Electronic Change: Current and Future States at the Same Level of Detail
Student Name
Capella University
MHA FPX 5064: Health Information Systems Analysis and Design for Administrators
Instructor Name
Month Day, Year
Introduction
A composite orthopedic and imaging practice, here called Pinecrest Orthopedics, obtains about 1,100 prior authorizations a month for MRI, CT, surgery, and injections. The process is largely manual, using payer websites, phone calls, and faxes. Federal rules finalized in 2024 require many payers, including Medicare Advantage organizations, Medicaid and Children's Health Insurance Program agencies and managed care plans, and qualified health plans on the federal exchanges, to support electronic prior authorization through standard application programming interfaces and to meet decision time frames (Centers for Medicare & Medicaid Services, 2024). Pinecrest plans to connect its electronic health record to payers' electronic prior authorization services. This paper maps the process before and after the change.
Current State Mapped as Performed
The current state was mapped by observing four authorization specialists for two days each and reviewing 120 authorization records, not by reading the practice's written procedure. The written procedure has six steps; the observed process has eleven, because it includes steps staff have added over time, such as checking a shared spreadsheet of payer rules and calling payers to confirm faxes were received.
| Step | Current state (as performed) | Median time |
|---|---|---|
| 1 | Physician orders imaging or procedure in record | 1 min |
| 2 | Order appears on authorization work queue | Same day |
| 3 | Specialist checks payer rules spreadsheet to see if authorization is required | 3 min |
| 4 | Specialist gathers clinical notes, prior imaging, and therapy records from record | 9 min |
| 5 | Specialist logs into payer portal or prepares fax form | 6 min |
| 6 | Specialist enters clinical information, often retyping from notes | 11 min |
| 7 | Submission sent; confirmation saved | 2 min |
| 8 | Specialist calls payer if no response in 3 business days | 14 min, when needed |
| 9 | Payer requests more information; specialist asks physician or nurse | 2 days elapsed, when needed |
| 10 | Decision received; specialist records it in the record | 3 min |
| 11 | Scheduler notified to book patient | Same day |
Median staff time per authorization is about 34 minutes, and median elapsed time from order to decision is 6 business days. Mapping the process as performed revealed five steps that do not appear in the written procedure, including the spreadsheet check and the follow-up calls.
Future State at the Same Detail
The future state is mapped to the same level of detail, so that the two maps can be compared step by step. Mapping the future state more broadly, for example as "system submits authorization," would hide work that still has to be done.
| Step | Future state | Expected median time |
|---|---|---|
| 1 | Physician orders imaging or procedure in record | 1 min |
| 2 | Record queries payer to determine whether authorization is required | Automatic |
| 3 | If required, record displays payer's documentation requirements | Automatic |
| 4 | Specialist or clinical staff complete required questions, with data prefilled from the record | 8 min |
| 5 | Specialist reviews prefilled data for accuracy and attaches documents | 5 min |
| 6 | Submission sent electronically | 1 min |
| 7 | Decision returned to record, or request for more information | 1 to 7 days elapsed |
| 8 | If more information requested, routed to clinical staff | 1 day elapsed, when needed |
| 9 | Scheduler notified automatically when approved | Automatic |
Expected median staff time is about 15 minutes per authorization requiring submission.
Work That Moved, Not Vanished
Electronic prior authorization does not make all work disappear; some of it moves. Checking whether authorization is required moves from the specialist to the system, which is a true reduction. Entering clinical information partly moves to clinical staff, because payers' documentation questions are often clinical, such as the duration of conservative therapy or specific examination findings, and nurses or physicians can answer them more accurately than authorization specialists. Reviewing prefilled data is new work that did not exist before, since automatically pulled data may be outdated or incomplete. Showing where work moves prevents the organization from cutting staff in one area while creating unplanned work in another. The practice should expect about 3 minutes of added clinical staff time per authorization.
Timings on Both
Both maps show timings so that the change can be measured. Staff time is expected to fall from about 34 to about 15 minutes per authorization, saving about 350 hours a month across 1,100 authorizations, less about 55 hours of added clinical staff time. Elapsed time is expected to fall because submissions are immediate and payers must meet decision time frames: 72 hours for expedited requests and 7 calendar days for standard requests under the federal rule. The practice's current median of 6 business days is already within the new standard for many payers, so the main gain in elapsed time will come from fewer requests for more information.
Unverified Assumptions Flagged
Several assumptions in the future state have not been verified. The first is that all of Pinecrest's major payers will offer electronic prior authorization; the federal rule does not apply to traditional Medicare fee-for-service claims in the same way, or to many employer plans regulated under other laws. The second is that prefilled data will be accurate enough to require only a brief review; this depends on how consistently physicians document in structured fields. The third is that payers' documentation questions will be answerable from the record; some payers may still require documents that the record does not structure. Each assumption should be tested with the largest payers during a pilot before staffing decisions are made.
What the Maps Mean for Staffing
The maps suggest that Pinecrest should not reduce authorization staff until the pilot confirms the assumptions. If staff time falls as expected, the practice could redeploy about two specialists to other revenue cycle work, such as denial follow-up, rather than eliminating positions, while adding a small amount of nurse time for clinical questions. Making staffing decisions from verified timings, rather than from the vendor's projected savings, protects the practice from a shortfall if payer adoption is slower than expected.
Conclusion
The current-state map, built from observation, shows an 11-step process taking about 34 minutes of staff time. The future-state map, at the same level of detail, shows about 15 minutes of staff time, with some work moving to clinical staff and new review work added. Timings on both allow the change to be measured, and unverified assumptions are flagged for testing.
References
Centers for Medicare & Medicaid Services. (2024). Medicare and Medicaid programs; Patient Protection and Affordable Care Act; Advancing interoperability and improving prior authorization processes. Federal Register, 89(27), 8758.
Reading the MHA-FPX5064 Assessment 2 instructions
The instructions ask you to map a workflow as it is now and as it would be after a new or changed information system. You define the workflow and its boundaries, map the current state as performed, including workarounds and duplicate entry, map the future state at the same level of detail, compare the two with timings, identify work that moves to other people, flag assumptions and discuss implications for staffing and training. Maps should be diagrams with written analysis. Observation and interviews are the best sources for the current state. The future state should be realistic, not a vendor demonstration. The maps build on your requirements and lead to the selection argument.
How this MHA FPX 5064 Assessment 2 example is built
Current state, future state, difference, consequences. The opening states which workflow is being mapped and its boundaries. A current state block maps it as actually performed, including workarounds and duplicate entry, with timings. A future state block maps the same workflow as the system would enable, with the same level of detail so the two are comparable. A difference block works through what changed step by step: removed, added, or moved to somebody else. A consequences block names who gains time and who loses it, since a net saving frequently hides a transfer. A hazard block asks what the redesigned flow makes newly possible to get wrong. The closing states what the future state assumes about the system that has not yet been verified.
Reading the MHA FPX 5064 Assessment 2 scoring guide
Five rows carry the grade: both maps, the comparison between them, the analysis of what changed and the implications. The current state reaches Distinguished when it shows how work is actually done, including workarounds and duplicate entry. The future state scores higher when drawn at the same level of detail, so the comparison is fair. Comparison earns credit when timings are given for both. The analysis rewards identifying work that moved to another role rather than disappeared. Flagging unverified assumptions shows honesty. Staffing and training implications connect the maps to management. APA and writing count too.
MHA FPX 5064 Assessment 2 help from the desk
Students often map the current state from policy and the future state from a vendor demo, which exaggerates the benefit. Another common mistake is drawing the future state in less detail, hiding steps. Timings are missing, so savings cannot be judged. Work that shifts to clinicians or front desk staff is not noticed. Assumptions about payer portals or integrations are presented as facts. Implications for staffing are skipped, even when the future state would free hours in the authorization team or add work for medical assistants. Timing each step with a stopwatch on a few real cases gives numbers that leaders will trust. Walking through one real prior authorization from start to finish is the best way to capture the current state accurately.
Get a MHA FPX 5064 Assessment 2 example written to your instructions
Send the Assessment 2 instructions and your MHA FPX 5064 scoring guide, along with the requirements your first assessment produced. We write a custom example against those criteria and return it in 24 to 48 hours. The first custom sample is free, and mapping the current state as performed rather than as documented is the move that makes the comparison real. 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 3: Design or Selection Argument
- MHA FPX 5068 Assessment 2: Adoption Management Plan
- MHA FPX 5042 Assessment 2: Developing an Interprofessional Team
- MHA FPX 5001 Assessment 2: Evidence-based Issue Analysis
- MHA FPX 5040 Assessment 2: Leading a Change With Kotter's Steps Filled In
MHA FPX 5064 Assessment 2 questions, answered
How do I map a process I do not perform?
Watch it or ask the people who do, and say which. What actually happens differs from the documented procedure in almost every setting, and the difference is usually where the problems live. A map built from the policy manual describes an intention rather than a workflow.
Why include workarounds?
Because they are the most honest description available of what the current system gets wrong. A workaround exists because somebody needed to do something the system made difficult. Mapping them tells you what the future state actually has to solve, which the official process never would.
What if the future state moves work to another group?
Say so explicitly and name who. Redesigns frequently take steps from clinicians and give them to administrative staff or the reverse, and the receiving group is where resistance will come from. Identifying the transfer early is what allows it to be negotiated rather than discovered.
Where can I find a free MHA FPX 5064 Assessment 2 sample paper?
This page holds the full prior authorization workflow maps, with the current state as performed, the future state at equal detail, timings, moved work, flagged assumptions and staffing effects. A custom version is available free.
What if the future state moves work to another group in MHA FPX 5064 Assessment 2?
Show it on the map and discuss it. Moved work is a real cost, and the group receiving it needs training, time and a say in the design.