| Course | HIM FPX 2670 Strategic Management of Health Information Systems |
|---|---|
| Assessment | Assessment 2 |
| Paper type | System selection analysis |
| 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 2
Evaluating Options for Record Completion Tracking: Weights Fixed First, Alternatives at Equal Depth, and Scores With Evidence
Student Name
Capella University
HIM FPX 2670: Strategic Management of Health Information Systems
Instructor Name
Month Day, Year
Introduction
Medicare requires inpatient records to be completed within 30 days of discharge (Centers for Medicare & Medicaid Services, 2025). Maple Grove Hospital, a composite community hospital, found that its record completion process relies on a manual spreadsheet, produces inaccurate reminder lists, and has a delinquency rate of 8.2% against a target of under 3%. Seven requirements were traced to gaps in the current process. This paper evaluates three options against those requirements.
Criteria and Weights Fixed First
Criteria and weights were agreed by the health information director, a physician representative from the medical staff office, the chief financial officer's delegate, and an information technology analyst before any option was scored. Fixing them first prevents weights from being adjusted to favor a preferred option. The group recorded its agreement in the project file, with the date, so that any later change to the weights would have to be made openly and explained.
| Criterion | Weight | What it measures |
|---|---|---|
| Requirements coverage | 35% | How many of R1 to R7 the option meets fully |
| Physician experience | 20% | Whether physicians see an accurate list where they document |
| Five-year cost | 20% | Total cost over five years, all categories |
| Implementation risk | 15% | Likelihood of delay or disruption |
| Fit with existing systems | 10% | Need for interfaces and duplicate data |
Alternatives Described to Equal Depth
Each option is described at the same level of detail, so that none is favored by a fuller description. Option 1, configure the existing record's deficiency tracking module. The hospital's electronic health record includes a module for identifying and tracking deficiencies that has never been configured. It would use rules for required documents by encounter type, route deficiencies to clinicians' work lists, and update status when documents are signed. Configuration would require an information technology analyst and a health information analyst for about four months. Option 2, purchase a stand-alone deficiency management system. Several vendors offer systems that connect to the record through interfaces, identify deficiencies, and send reminders by email and text. Implementation would take about six months, including interface building and testing. Option 3, improve the manual process without new technology. The spreadsheet would be replaced by a shared report from the record listing unsigned documents, and analysts would continue to track missing documents manually. Weekly reminders would use the report.
Scores Shown With Their Evidence
Each score, from 1 to 5, is shown with its evidence.
| Criterion | Option 1 | Option 2 | Option 3 |
|---|---|---|---|
| Requirements coverage | 4 (meets R1-R5, R7 fully; R6 partly, per vendor documentation and a test build) | 4 (meets R1-R3, R5-R7 fully; R4 partly, since list is outside the record, per demonstration) | 2 (meets R3 partly, R5 partly; per analysis) |
| Physician experience | 5 (list in record work list, where physicians sign) | 3 (email and text; must switch to record to complete) | 2 (unchanged weekly emails) |
| Five-year cost | 4 (see cost table) | 2 (see cost table) | 5 (see cost table) |
| Implementation risk | 4 (configuration of existing system; peer hospital experience) | 3 (interfaces add risk) | 5 (little change) |
| Fit with existing systems | 5 (native) | 2 (interfaces, duplicate data) | 4 (uses record report) |
| Weighted score | 4.30 | 3.05 | 3.25 |
Showing the evidence behind each score lets reviewers challenge a specific judgment rather than the whole evaluation.
Cost Split Into Categories
| Cost over five years (dollars) | Option 1 | Option 2 | Option 3 |
|---|---|---|---|
| Software and licenses | 0 (included in current license) | 210,000 | 0 |
| Configuration or implementation | 85,000 (staff time) | 90,000 | 10,000 |
| Interfaces | 0 | 60,000 | 0 |
| Training | 15,000 | 20,000 | 5,000 |
| Ongoing support | 40,000 | 75,000 | 0 |
| Analyst time saved (negative) | -260,000 | -240,000 | -60,000 |
| Net five-year cost | -120,000 | 215,000 | -45,000 |
Splitting cost into categories shows that Option 1's cost is mostly internal staff time, that Option 2's includes ongoing license and interface costs, and that Options 1 and 3 save more analyst time than they cost. Analyst time saved assumes that about 20 of the current 26 weekly hours of manual tracking would be freed under Options 1 and 2, and about 5 hours under Option 3, valued at about 50 dollars an hour including benefits.
Reading the Results
The weighted scores separate the options clearly. Option 1 leads because it scores well on every criterion and best on the two that matter most to users, requirements coverage and physician experience. Option 2 meets most requirements but loses on cost and fit, since it duplicates data the record already holds and requires interfaces to keep the two systems in step. Option 3 scores lowest on the heaviest criterion; it would save little analyst time and would leave the inaccurate lists, the main source of physician frustration, largely in place. Its low cost and risk are attractive, but it does not solve the problem that started the project.
Recommendation
Option 1, configuring the existing record's module, has the highest weighted score, the best physician experience, and the lowest net cost. It is recommended, with a test build confirming missing-document rules as the first step before full configuration. The health information director would own the project, with the information technology analyst responsible for configuration and a physician champion from the medical staff office responsible for testing the physician work list.
What Would Change the Recommendation
The recommendation depends on assumptions that could change. If the module's rules cannot identify missing documents, which the test build has confirmed only for discharge summaries so far, Option 1's requirements coverage would fall and Option 2 might become preferable. If the information technology department cannot provide an analyst for four months because of other projects, implementation risk for Option 1 would rise. If physician leaders decide that text reminders are important, Option 2's physician experience score would rise. None of these changes would favor Option 3, which remains a fallback only if neither technology option can proceed. The evaluation team will report the result of the test build to the same group that set the weights before any configuration work is scheduled. Naming what would change the recommendation tells decision makers what to confirm before committing.
Conclusion
With criteria and weights fixed first, three options were described to equal depth and scored with evidence. Configuring the existing record's module scores highest and has the lowest net cost, provided the test build confirms that it can identify missing documents and staff are available.
References
Centers for Medicare & Medicaid Services. (2025). Condition of participation: Medical record services (42 C.F.R. ยง 482.24). U.S. Government Publishing Office.
The Capella HIM FPX 2670 Assessment 2 instructions
The instructions ask you to evaluate alternatives for meeting the information system requirements from Assessment 1 and recommend one. You convert requirements into weighted criteria, identify alternatives, which may include building on the existing electronic record, buying a module or changing the process without new technology, describe each at equal depth, score them with evidence, analyze costs by category and recommend an option. Weights should be set before scoring to avoid bias. Evidence can include vendor documentation, labeled as such, reference checks and published reviews. Total cost should include licenses, implementation, training and ongoing support.
Inside the HIM FPX 2670 Assessment 2 example
The example fixes the yardstick before it looks at anything. It opens by carrying forward the requirements established earlier and converting them into scored criteria with weights and definitions. The alternatives section then describes each option in the same categories and to the same depth, with the status quo among them. The scoring section applies every criterion to every option and shows the evidence behind each score rather than the score alone. A cost section works in categories over a stated period. The risk section treats implementation, interface and vendor risk separately, since they fail in different ways. The recommendation follows from the matrix, and a sensitivity paragraph states which weight would have to move for the answer to change. The example ends with the conditions that would justify revisiting the decision.
Reading the HIM FPX 2670 Assessment 2 scoring guide
Faculty score the criteria and weights, the alternatives, the scoring, the cost analysis and the recommendation. Criteria reach Distinguished when weighted and defined before any option is scored, for example physician ease of use at 25 percent and reporting at 20 percent. Alternatives score higher when described in the same categories and depth, including a non-purchase option such as better use of the existing record's deficiency module. Scores earn credit when each is supported by evidence rather than impression, such as a demonstration or a reference call. Cost should be split into one-time and recurring categories. The recommendation should follow from the weighted totals. Stating what would change the recommendation, such as a vendor failing a reference check, shows judgment and protects the organization.
HIM FPX 2670 Assessment 2 help: mistakes that cost marks
Students often set weights after scoring, which quietly lets the favored option win. Another common mistake is describing one alternative in detail and the others in a sentence each, which makes the comparison unfair. Scores are given without evidence, so readers cannot check them. Only the purchase price gets counted, with annual support, training and the interface to the record left off. The option of improving the current process, often the cheapest, is ignored. The recommendation does not follow from the scores. Vendor claims are treated as facts rather than as statements to verify. A scoring table with weights, scores and weighted totals, followed by a paragraph explaining the result and its sensitivity to the weights, makes the analysis easy to check and hard to dispute.
Get a HIM FPX 2670 Assessment 2 example written to your instructions
Send the Assessment 2 instructions and the scoring guide from your HIM FPX 2670 courseroom, along with the requirements or case your section supplied. We write a custom example against those criteria, with weighted scoring and cost worked in categories, 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 1: Needs Assessment
- HIM FPX 2670 Assessment 3: Implementation and Governance Plan
- HIM FPX 3620 Assessment 2: Retention and Release Policy
- HIM FPX 2660 Assessment 2: Privacy Incident Analysis
- HIM FPX 3640 Assessment 2: Downtime Procedure Plan
- HIM FPX 1610 Assessment 2: Clinical Report Interpretation
HIM FPX 2670 Assessment 2 questions, answered
Should the analysis use real products?
Follow your instructions. Where real systems are permitted, choose ones with published independent information so your scores have support beyond marketing pages. Where they are not, described option types work as long as capabilities are stated consistently. Either way the method carries the credit, and a well-scored comparison of generic options beats a lopsided review of named ones.
How do I score criteria I cannot measure?
Define the scale before you use it. Say what a high score on usability or vendor stability requires, in terms someone else could apply, then score against that definition and cite the evidence. Unmeasurable criteria are not the problem; undefined ones are, because a reader cannot tell whether a four means anything different from a three.
Is the recommendation graded on being correct?
Not usually. In current courserooms the criteria read for method, evidence and defensibility rather than for a right answer, and two sound analyses can reach different recommendations from different weights. What loses credit is a recommendation the matrix does not support, or one arriving with no statement of what the chosen option does worse than the alternatives.
Where can I find a free HIM FPX 2670 Assessment 2 sample paper?
This page contains the full selection analysis for record completion tracking, with fixed weights, equal-depth alternatives, evidenced scores, cost categories and the recommendation. A model analysis is available free.
Why set weights before scoring in HIM FPX 2670 Assessment 2?
Setting weights first prevents choosing weights that favor an option you already prefer. It makes the selection fair and easy to defend.