| Course | MHA FPX 5016 Introduction to Health Information Systems |
|---|---|
| Assessment | Assessment 1 |
| Paper type | Information systems map |
| 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 5016 Assessment 1
Mapping Information Systems by the Work They Support: The Referral-to-Surgery Pathway at an Orthopedic Practice
Student Name
Capella University
MHA FPX 5016: Introduction to Health Information Systems
Instructor Name
Month Day, Year
Organized by Work, Not Software
A list of software products says little about how information moves in a health care organization. This paper instead follows one pathway of work, from a patient's referral to the day of surgery, at a composite orthopedic practice, here called Summit Orthopedics, which has 11 surgeons in three clinics and operates at two hospitals. For each step, the paper identifies who does the work, which system they use, and how information moves to the next step.
The Pathway Step by Step
| Step | Work | Who | System used |
|---|---|---|---|
| 1 | Receive referral | Referral coordinator | Electronic fax inbox |
| 2 | Register patient and schedule visit | Scheduler | Practice management system |
| 3 | Obtain outside imaging | Medical assistant | Imaging exchange portal and CDs mailed by patients |
| 4 | Clinic visit and surgical decision | Surgeon | Practice's electronic health record |
| 5 | Obtain prior authorization | Authorization specialist | Payer web portals |
| 6 | Book surgery | Surgical scheduler | Hospital's scheduling system |
| 7 | Preoperative testing and clearance | Hospital preadmission nurse | Hospital's electronic health record |
| 8 | Day of surgery | Hospital surgical team | Hospital's electronic health record |
Seven different systems support eight steps, and only two of them, the practice management system and the practice's electronic health record, are connected to each other.
The Handoffs Marked
Each change of hands is a point where information can be lost or delayed. On this pathway there are seven handoffs, and four of them cross between systems that do not exchange data. The most important are from the fax inbox to the practice management system, from the surgeon's decision to the authorization specialist, and from the practice to the hospital when surgery is booked. At each of these, a person reads information in one system and acts on it in another. The handoff from the practice to the hospital is especially risky, because the hospital's preadmission nurse depends on information the practice sends by fax or through a separate portal, and missing information, such as a patient's anticoagulant use, can delay or cancel surgery. Marking handoffs rather than systems shows where information is most likely to be lost, which is where improvement should begin.
Rekeying Flagged as a Risk
At four points, staff retype information from one system into another: referral details from the fax into the practice management system, clinical details from the practice's record into payer portals for authorization, patient and procedure details into the hospital's scheduling system, and medication lists into the hospital's preadmission record. Ash et al. (2004) describe how patient care information systems can introduce new kinds of errors, including errors that arise when information must be transferred between systems that do not fit the way clinical work is done. Each retyping step is a chance for a transposed digit in a date of birth, a wrong side in a procedure description, or an outdated medication list. A spot check of 50 recent surgical bookings found three with a discrepancy between the practice's record and the hospital's booking, one involving the side of surgery, which was caught at the preoperative verification.
Data Ownership Named
For each key data element, the paper names the system and role that serve as the authoritative source.
| Data element | Authoritative source | Owner by role |
|---|---|---|
| Patient demographics and insurance | Practice management system | Front desk supervisor |
| Diagnosis and surgical plan | Practice's health record | Operating surgeon |
| Authorization status | Payer portal, recorded in practice system | Authorization specialist |
| Surgery date and time | Hospital scheduling system | Hospital surgical scheduler |
| Preoperative medication list | Hospital's health record after reconciliation | Preadmission nurse |
Naming an owner answers the question staff face when two systems disagree: which one is right, and who corrects the other?
What No System Holds
Some information needed for the pathway sits in no system. Whether the patient has someone to drive them home and help them for the first days after surgery is discussed at the clinic visit but not recorded in a structured way. The status of an authorization in progress, such as a payer's request for more records, is kept in the specialist's personal spreadsheet. Phone calls between the surgical scheduler and the hospital to find an open slot are not documented. Patients' questions about preparation, asked by phone, are handled but rarely recorded. Information that lives only in people's memory or personal files disappears when those people are absent, which makes the pathway fragile.
How the Pathway Looks to the Patient
From the patient's side, the fragmented systems appear as repeated questions and waiting. A patient referred for a knee replacement is asked for the same insurance details by the practice, the authorization specialist, and the hospital's preadmission office. They may carry imaging on a CD to the first visit because the outside radiology group is not connected to the practice's exchange portal. They wait for a call about their surgery date while the scheduler and the hospital trade phone messages. When preparation questions arise, they call the clinic, and the answer depends on who picks up. None of these experiences appears in any system's reports, but each is a result of the handoffs and rekeying described above. Mapping the pathway by work makes the patient's experience visible in a way a software inventory cannot, and it gives the practice a patient-centered reason to fix problems that staff have learned to live with.
Implications
The mapping suggests three priorities. First, reduce rekeying at the practice-to-hospital handoff by using the health information exchange connection both organizations already have, so that the surgical plan and medication list can be sent electronically. Second, move authorization tracking from a personal spreadsheet into a shared work queue in the practice management system. Third, add a structured field in the practice's record for discharge support, so that the hospital learns early which patients may need help. Each change targets a handoff or a gap identified in the map, and each can be tested on one surgeon's patients before it is extended to the whole practice.
Conclusion
Following the referral-to-surgery pathway shows how Summit's information systems support real work and where they fail it. The pathway uses seven systems with seven handoffs, retypes information at four points, needs clear data owners, and depends on information no system holds. Mapping by work rather than software points directly to the changes that would reduce risk.
References
Ash, J. S., Berg, M., & Coiera, E. (2004). Some unintended consequences of information technology in health care: The nature of patient care information system-related errors. Journal of the American Medical Informatics Association, 11(2), 104-112.
Reading the MHA-FPX5016 Assessment 1 instructions
The first assessment in MHA FPX 5016 asks you to map the information systems in a health care organization against the operations they support. You describe an operational process, identify the systems used at each step, show what data pass between them, mark manual steps and rekeying, identify data ownership and gaps, and explain the implications for managers. Organizing the map by work, rather than listing software, shows how systems affect operations. A diagram usually accompanies the written analysis. Sources include organizational documentation, observation and health information systems literature. Many students use a process they know well, such as scheduling, referral or billing, which makes gaps easier to see.
How this MHA FPX 5016 Assessment 1 example is built
Operations, systems, interfaces, ownership. The opening describes the operational flow the systems support, since a map organized by software rather than by work tells an administrator nothing about consequences. A systems block names each one and what it holds, in the vocabulary the organization uses rather than the vendor's. An interface block identifies what passes between systems, in what direction and by what mechanism, flagging anything that moves by rekeying rather than automatically. An ownership block names who is accountable for the accuracy of each data set. A gap block covers what no system currently holds, which is often what people complain about most. The closing states which interface would cause most damage if it failed. Claims about capability are sourced from the organization rather than from vendor material.
Where the marks sit in the MHA FPX 5016 Assessment 1 scoring guide
Capella's scoring guide rates the operational description, the systems identification, the interfaces, the data ownership and the implications. The description reaches Distinguished when the map follows the work step by step, from the referral arriving to the surgery date being set. Systems score higher when named with what they hold, in the organization's language. Interfaces earn credit when handoffs, rekeying and manual transfers are marked as risks, since those are where referrals get lost. Data ownership should be assigned to roles, not departments. Identifying what no system holds, such as a patient's preferred contact time, shows insight. Implications should connect to administrative decisions about staffing, training or system changes. APA references and clear writing are also scored.
MHA FPX 5016 Assessment 1 help from the desk
Students often list software products without showing how work moves between them. Another common mistake is copying vendor descriptions instead of describing how the organization actually uses each system. Rekeying and manual transfers are left out, though they are where errors happen, such as a surgery date typed twice into two calendars. Data ownership is assumed rather than assigned. Gaps are overlooked because the map only shows what systems contain. The patient's view of the process is rarely considered, even though delays are felt most by the patient waiting for a call. A clear diagram with arrows for data flow and marks for manual steps makes the analysis stronger than text alone. Date the map, since systems and interfaces change.
Get a MHA FPX 5016 Assessment 1 example written to your instructions
Send the Assessment 1 instructions and the scoring guide from your MHA FPX 5016 courseroom, plus the organization 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 mapping by operational flow rather than by software is the move 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 5016 papers and MHA samples
- MHA FPX 5016 Assessment 2: System Evaluation Against Workflow
- MHA FPX 5016 Assessment 3: Technology Direction Recommendation
- MHA FPX 5017 Assessment 1: Nursing Home Data Analysis
- MHA FPX 5014 Assessment 1: Measuring a Quality Problem Correctly
- MHA FPX 5020 Assessment 1: Capstone Project Framing
- MHA FPX 5012 Assessment 1: Governance and Leadership in a Nonprofit Community Hospital
MHA FPX 5016 Assessment 1 questions, answered
How detailed should the map be?
Detailed enough to show the handoffs and no more. An administrator needs to see where information crosses a boundary and what happens there. Screen level detail belongs to an analyst, and including it usually crowds out the interface analysis where this assessment concentrates its credit.
Should I use vendor documentation?
For what a system is capable of, yes, and clearly labeled. For what it actually does in this organization, ask or observe. The gap between advertised capability and configured reality is large in health IT, and a map built entirely from vendor material describes a system nobody is using.
Should I use vendor documentation for MHA FPX 5016 Assessment 1?
Only for technical facts, such as what a module does. Describe how your organization actually uses each system from observation and staff input, since configuration and workarounds matter more than the vendor's design.
Where can I find a free MHA FPX 5016 Assessment 1 sample paper?
This page contains the full referral-to-surgery systems map, with handoffs, rekeying risks, data ownership, gaps and the patient's view. A custom map of your own process is available free.
What if my organization uses one integrated system for MHA FPX 5016 Assessment 1?
Even integrated systems have modules, outside connections and manual steps, such as faxed referrals or payer portals. Map those, and show where data leave or enter the main system.