| Course | HIM FPX 2670 Strategic Management of Health Information Systems |
|---|---|
| Assessment | Assessment 1 |
| Paper type | Information systems needs assessment |
| Length | About 1,080 words, 5 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | BS in Health Information Management |
| Updated | September 2026 |
Free sample paper for HIM FPX 2670 Assessment 1
Mapping the Record Completion Process as It Runs: A Countable Problem, Distinct Stakeholders, and Requirements Traced to Gaps
Student Name
Capella University
HIM FPX 2670: Strategic Management of Health Information Systems
Instructor Name
Month Day, Year
Introduction
Hospital medical records must be completed promptly after discharge. The Medicare Conditions of Participation require that inpatient records be completed within 30 days following discharge (Centers for Medicare & Medicaid Services, 2025). At Maple Grove Hospital, a composite community hospital with 220 beds, the health information management department tracks incomplete records, called deficiencies, such as unsigned orders, missing discharge summaries, and unauthenticated operative reports. The department's director believes the process needs a better information system. This paper maps the current state and derives requirements, without naming or assuming any product.
Current State Mapped as It Runs
The process was mapped by observing the two deficiency analysts for three days, reviewing the department's tracking spreadsheet, and interviewing physicians and the medical staff office. 1. After discharge, the record appears on a daily discharge list in the health information system. 2. An analyst opens each record and checks it against a paper checklist of required documents. 3. Missing or unsigned items are entered in a spreadsheet by physician, with the date found. 4. The electronic health record automatically routes unsigned documents to physicians' inboxes, but missing documents, such as an absent discharge summary, are not routed; the analyst sends a message. 5. Each week, the analyst emails each physician a list of their open deficiencies from the spreadsheet. 6. When a physician completes an item, the analyst must notice it in the record and update the spreadsheet by hand. 7. At day 21, the analyst sends a warning letter; at day 30, the record is counted as delinquent and reported to the medical staff office, which can suspend admitting privileges under the medical staff bylaws. Steps 3, 5, and 6 are manual and duplicate information already in the record. Mapping the process as it runs shows the manual work and duplicate tracking that the official description omits.
The Problem Shown in Something Countable
The problem is shown in measures that can be counted and tracked. Over the last quarter, Maple Grove discharged about 3,300 inpatients. On average, 410 records were incomplete at any time. The delinquency rate, the share of records not completed within 30 days, averaged 8.2%, against the department's target of under 3%. Analysts spend about 26 hours a week maintaining the spreadsheet and sending reminders. In a spot check of 50 spreadsheet entries, 7 were out of date, listing items that physicians had already completed, which led to physicians receiving incorrect reminders and losing trust in the lists.
Stakeholder Groups Kept Distinct
Different groups experience the process differently and need different things from it. Physicians want one accurate list of what they need to complete, available where they work, and fewer reminders about items already done. Deficiency analysts want to stop duplicating the record in a spreadsheet and to see completion automatically. The medical staff office wants reliable delinquency reports for enforcing bylaws, since suspending privileges on the basis of an inaccurate list would damage relationships with physicians. Coders want complete records sooner, since a missing discharge summary delays final coding and billing. The chief financial officer wants fewer records held from billing, measured as discharged-not-final-billed days. Keeping these groups distinct prevents the analysis from treating the problem as only a health information department concern. It also shows that any solution will be judged differently by each group, so the evaluation that follows must reflect all of their needs rather than the department's alone.
Requirements Traced to Gaps
Each requirement traces to a gap identified in the current state, and no requirement describes a product or vendor feature. R1 (gap: manual spreadsheet): The system must identify deficiencies from the record automatically, based on rules for required documents by encounter type. R2 (gap: missing documents not routed): The system must route missing documents, not only unsigned ones, to the responsible clinician's work list. R3 (gap: manual update on completion): Completion of a deficiency in the record must update its status automatically, without analyst action. R4 (gap: inaccurate reminder lists): Clinicians must be able to see their own current deficiencies at any time in the place they complete documentation. R5 (gap: delinquency reporting): The system must produce delinquency reports by clinician and department that match the record in real time. R6 (gap: coding delays): Coders must be able to see which records are held for deficiencies that affect coding. R7 (gap: analyst workload): The system must allow analysts to manage exceptions, such as reassigning a deficiency when a physician leaves, without recreating records.
Why the Current Process Persists
The spreadsheet was created eight years ago, when the hospital moved from paper to an electronic record and needed a quick way to track deficiencies during the transition. It was meant to be temporary. It persisted because it worked well enough, because analysts became skilled at maintaining it, and because no one owned the question of whether the record itself could do the job. Understanding why a workaround persists matters, because the same forces, familiarity and the lack of an owner, could keep the spreadsheet alive alongside any new system unless the transition explicitly retires it.
What the Current State Costs
The current state has costs beyond analyst time. Each delinquent record is a compliance risk in accreditation and Medicare surveys, which review record completion. Missing discharge summaries delay coding and billing: the finance department estimates that deficiency holds account for about 1.4 days of the hospital's discharged-not-final-billed total. Inaccurate reminders erode physicians' trust, which makes them less responsive to accurate ones.
No Product Named Anywhere
This analysis names no product. Naming a product at this stage would shape the requirements around that product's features and could exclude better solutions, including configuring tools already available in the hospital's existing electronic health record.
Conclusion
The current record completion process at Maple Grove relies on a manual spreadsheet that duplicates the record, produces inaccurate lists, and contributes to a delinquency rate of 8.2%. Stakeholder groups have distinct needs, and seven requirements are traced to specific gaps. The next step is to evaluate options against these requirements, including configuring tools the hospital already owns, with weights agreed before any option is scored. The measures above, the delinquency rate, analyst hours, and the accuracy of reminder lists, will serve as the baseline for judging whichever option is chosen.
References
Centers for Medicare & Medicaid Services. (2025). Condition of participation: Medical record services (42 C.F.R. ยง 482.24). U.S. Government Publishing Office.
Reading the HIM-FPX2670 Assessment 1 instructions
The first assessment in HIM FPX 2670 asks you to assess the information system needs of a health information management process. You define the scope, map the current process as it actually works, measure the problem with data, identify stakeholders and their distinct needs, derive requirements from the gaps and explain the costs of the current state. The assessment should stay at the level of needs and requirements; product selection comes in Assessment 2. Record completion, release of information and coding workflows are common topics. Data such as the number of delinquent records, their age and the effect on billing make the problem concrete. Sources include AHIMA practice briefs and systems analysis texts.
Inside the HIM FPX 2670 Assessment 1 example
The example works from evidence toward requirements and stops there. It opens with scope: the department, the process and the boundary of the assessment. The current state follows, mapped as work actually happens rather than as policy describes it, with the handoffs and the workarounds visible. The third section presents problem evidence, each figure with its source and its period, so the need is demonstrated rather than claimed. The fourth section covers stakeholder input by group, keeping clinical, registration, coding and leadership perspectives distinct. The fifth section derives requirements directly from the gaps identified, each one traceable back to a documented problem. A constraints section names budget category, interface obligations and staffing reality. The example closes without recommending anything, because recommending belongs to the next assessment.
HIM FPX 2670 Assessment 1 scoring guide: what Distinguished looks like
The scoring guide looks at the scope, the current state map, the measurement, the stakeholder analysis, the requirements and the costs. The map reaches Distinguished when it shows how work actually happens, including workarounds such as email reminders to physicians. Measurement scores higher when the problem is expressed in countable terms, such as delinquent records over thirty days. Stakeholders earn credit when their needs are kept distinct, since physicians want fewer clicks and HIM staff want reliable tracking. Requirements should each trace to a gap in the current state. Costs, such as delayed billing and accreditation risk, show why the problem matters. Keeping product names out shows discipline.
HIM FPX 2670 Assessment 1 help from the desk
Students often name a product in the needs assessment, which turns the analysis into a sales pitch. Another common mistake is mapping the process from policy rather than observation. The problem is described in words, such as records are late, without counts. Stakeholders are treated as one group with shared needs. Requirements appear without a link to any gap. The cost of the current state is left out, though delayed record completion can hold up billing and threaten accreditation. A countable problem, a real process map and requirements traced to gaps give the selection analysis in Assessment 2 a solid foundation.
Get a HIM FPX 2670 Assessment 1 example written to your instructions
Send the Assessment 1 instructions and the scoring guide from your HIM FPX 2670 courseroom, plus the department and process your assessment covers. We write a custom example against those criteria, with the current state mapped and requirements traced to evidence, and return it in 24 to 48 hours. The first custom sample is free. 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 HIM FPX 2670 papers and BS in Health Information Management samples
- HIM FPX 2670 Assessment 2: System Selection Analysis
- HIM FPX 2670 Assessment 3: Implementation and Governance Plan
- HIM FPX 3620 Assessment 1: Records Lifecycle Analysis
- HIM FPX 2660 Assessment 1: Ethics Case Analysis
- HIM FPX 3640 Assessment 1: Documentation Integrity Audit
- HIM FPX 1610 Assessment 1: Terminology Breakdown
HIM FPX 2670 Assessment 1 questions, answered
Do I need real data for the current state?
You need stated figures with stated sources, which can come from a supplied scenario, published benchmarks or clearly labeled assumptions. What weakens the document is a number with nothing behind it. If your section provides a case, use its figures exactly. If you build your own, say what you assumed and keep that assumption visible wherever the figure is used.
How many requirements should the assessment produce?
Fewer than a product brochure contains. Each requirement has to trace back to a documented gap, so the count follows from the evidence rather than from ambition. Sorting them into mandatory and desirable matters more than the total, because the next assessment scores alternatives against them and an undifferentiated list makes every option look equally acceptable.
Can I name a vendor in this assessment?
Keep products out of it unless your instructions say otherwise. The purpose is to establish need independently, so that selection later has an honest standard to measure against. Naming a system this early tends to bend the requirements toward that system, and a scoring guide reading for objective analysis notices the shape of the resulting list.
Where can I find a free HIM FPX 2670 Assessment 1 sample paper?
This page holds the full needs assessment for record completion, with the process as it runs, countable problem, distinct stakeholders and traced requirements. A model needs assessment for your process is available free.
Should I name a system in HIM FPX 2670 Assessment 1?
No. The needs assessment describes what the organization needs, not which product to buy. Product selection belongs in Assessment 2, where options are compared against these requirements.