| Course | HIM FPX 3640 Managing Electronic Health Records Systems |
|---|---|
| Assessment | Assessment 3 |
| Paper type | EHR optimization proposal |
| Length | About 1,100 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 3640 Assessment 3
One Change Specified to Build Level: Redesigning the Hospitalist Progress Note Template to Reduce Copy-Forward
Student Name
Capella University
HIM FPX 3640: Managing Electronic Health Records Systems
Instructor Name
Month Day, Year
Introduction
An audit of 200 hospitalist progress notes at Riverton Hospital, a composite community hospital, found long passages, 100 words or more, repeated verbatim from the prior day's assessment and plan in 41% of notes, that examinations were copied without a date in 49% of notes, and that most contradictions between notes and the rest of the record came from copied text. The main cause identified was the template, which copies the entire previous note by default. Tsou et al. (2017) recommended that organizations make copied text identifiable and design documentation tools that support accurate use. This paper specifies one change to the template.
One Change Specified to Build Level
The change replaces the current "copy previous note" default with a template that pulls structured data automatically and leaves narrative sections for new entry. It is specified at the level a build analyst needs. Template name: Hospitalist Progress Note, version 2. Trigger: selected by any user in the hospitalist provider group when creating a progress note for an inpatient encounter. Sections and their behavior: Subjective: blank free-text field with prompt text "Overnight events and patient report today." Prompt text disappears when the user types. Required: the note cannot be signed if the field is empty. Vital signs: auto-populated with the last 24 hours of vital signs from flowsheets, displayed as minimum, maximum, and most recent values. Read-only in the note. Examination: blank field with a button labeled "Insert yesterday's exam for editing." When used, the inserted text is marked with a gray background and the label "Carried forward from [date]; edit before signing." The label remains in the signed note if the text is not edited. Results: auto-populated with laboratory and imaging results filed in the last 24 hours. Read-only. Medications: auto-populated with active medications from the medication administration record. Read-only. Assessment and plan: pre-populated with the problem list; under each problem, a blank field. A button labeled "Insert yesterday's plan for this problem" inserts prior text with the same gray marking and label. Signing rule: if carried-forward text in the assessment and plan exceeds 60% of the section's words, a single prompt appears on signing: "Most of this plan is unchanged from yesterday. Sign as is or edit?" The prompt does not block signing. A specification at build level removes the interpretation that lets a change be built differently from what was intended.
Evidence Carried Forward, Not Rebuilt
The specification carries evidence forward from the audit rather than repeating the analysis. The subjective field is required because the audit found 26% of notes lacked day-specific subjective information. The examination and plan buttons with marking address the finding that copied examinations and plans were the main source of contradictions. Auto-populated results address the audit criterion on recent results, which 22% of notes failed. Every element of the specification can be traced to an audit finding.
Testing Beyond the Change Itself
Testing must cover the change and the systems it touches. Unit testing will confirm that each section behaves as specified. Integration testing will confirm that auto-populated data pull correctly from flowsheets, the laboratory interface, and the medication administration record, and that the gray marking and label display correctly when notes are printed, faxed, released through the patient portal, and exported through health information exchange. Regression testing will check that other note types used by hospitalists, such as admission and discharge notes, are unaffected, and that the change does not slow note loading beyond two seconds. Usability testing with four hospitalists, each writing notes for two test patients, will measure time to complete a note and identify confusion. Wang et al. (2017) found that most progress note text was copied or imported rather than typed, so the testing also checks that imported data remain readable and do not simply replace copied text with auto-populated bulk.
Alert Burden Treated as a Cost
The signing prompt is an alert, and every alert has a cost in attention. Hospitalists already see many alerts, and an additional one on every note would add to alert fatigue. The prompt is therefore designed to fire only when carried-forward text exceeds 60% of the plan, which the audit data suggest would occur in about 30% of notes at first and fewer as habits change. It does not block signing, and it will be reviewed after 60 days: if hospitalists override it more than 90% of the time without editing, it will be removed, since it would then be adding burden without changing behavior. Treating the alert as a cost means it must earn its place by changing behavior, or be removed.
Risks of the Change
The change carries risks that the testing is designed to catch. Hospitalists may find the new template slower at first, since they must type the subjective section and choose whether to insert prior text. Some may simply click the insert buttons for every section, reproducing the old behavior with a gray background. The measurement plan addresses this by tracking both the large identical block rate and how often the insert buttons are used; if button use is nearly universal and the block rate does not fall, the design will be reconsidered.
Training and Communication
Hospitalists will receive a two-page guide and a 15-minute demonstration at a group meeting. The hospitalist medical director will explain the reason for the change using the audit results, including the examples of contradictions caused by copied text.
Measured With the Same Criteria as Before
Six months after the change, the audit will be repeated using the same population definition, sample size, day 4 selection, criteria, and reviewers trained with the same definitions. Using the same method means that any change in results can be attributed to the template rather than to a different way of measuring. Targets are: day-specific subjective information in at least 95% of notes, examinations updated or dated in at least 85%, and large identical blocks in the assessment and plan in no more than 15%. Note completion time will also be measured, since a change that improves accuracy but greatly lengthens documentation time may not be sustained.
Conclusion
The template change is specified to build level, rests on evidence carried forward from the audit, is tested beyond the change itself, treats its one alert as a cost to be justified, and will be measured with the same criteria used in the original audit.
References
Tsou, A. Y., Lehmann, C. U., Michel, J., Solomon, R., Possanza, L., & Gandhi, T. (2017). Safe practices for copy and paste in the EHR: Systematic review, recommendations, and novel model for health IT collaboration. Applied Clinical Informatics, 8(1), 12-34.
Wang, M. D., Khanna, R., & Najafi, N. (2017). Characterizing the source of text in electronic health record progress notes. JAMA Internal Medicine, 177(8), 1212-1213. https://doi.org/10.1001/jamainternmed.2017.1548
Reading the HIM-FPX3640 Assessment 3 instructions
The final assessment asks you to propose an optimization to an electronic health record system based on your earlier audit. You state the finding that justifies the change, specify the change so it could be built, describe testing, consider effects on workflow and alert burden, identify risks, plan training and communication and set measures using the same criteria as the audit. One well-specified change is better than several vague ones, because it can be built, tested and measured within a single release cycle. Informatics and documentation integrity sources support the proposal. The audience includes the informatics team and clinical leaders who must approve the change, so the proposal should speak to both clinicians' time and data integrity.
Inside the HIM FPX 3640 Assessment 3 example
The example moves from evidence to build to proof. It opens with the finding that justifies the change, stated in one paragraph with its source, then specifies the change itself precisely enough to be configured. A design section covers what the entry looks like afterward from the user's side, including what is required, what is defaulted and what free text remains. The build and testing section sequences configuration, test scenarios, the workflow steps that must be retested and a limited pilot. Training follows, by role and in the format that fits the shift. The measurement section reuses the earlier audit definitions so the before and after are the same measurement. A risk section covers unintended effects, including workarounds, and states what would trigger reversing the change.
HIM FPX 3640 Assessment 3 scoring guide: what Distinguished looks like
The scoring guide rates the justification, the specification, the testing, the workflow effects, the risks, the training and the measures. The specification reaches Distinguished when precise enough to configure, such as which sections pull forward and which require fresh entry. Justification scores higher when drawn from the audit findings. Testing earns credit when it covers effects beyond the change, such as downstream reports. Treating alert burden as a cost shows informatics awareness. Measures should reuse the audit criteria, so improvement can be compared directly. Risks and training complete the proposal, and a short pilot on one unit before full rollout shows prudence.
Common HIM FPX 3640 Assessment 3 mistakes, and how to avoid them
Students often propose several changes at once, none specified well enough to build, which leaves the informatics team to guess what was meant. Another common mistake is a change not justified by the audit. Testing is limited to whether the template works, ignoring reports and billing that depend on it. Alert burden is added without considering clinician fatigue. Measures change from the audit, so improvement cannot be shown. Training is an email, though hospitalists need a short demonstration of the new template during their own meetings. Keeping to one change, specified precisely and measured the same way as before, makes the proposal convincing to informatics committees.
Get a HIM FPX 3640 Assessment 3 example written to your instructions
Send the Assessment 3 instructions and the scoring guide from your HIM FPX 3640 courseroom, plus the audit finding or scenario your change responds to. We write a custom example against those criteria, specified to build level with testing and measures attached, 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 3640 papers and BS in Health Information Management samples
- HIM FPX 3640 Assessment 1: Documentation Integrity Audit
- HIM FPX 3640 Assessment 2: Downtime Procedure Plan
- HIM FPX 4630 Assessment 3: Statistical Interpretation Paper
- HIM FPX 3620 Assessment 3: Department Functions Report
- HIM FPX 4650 Assessment 3: Decision Support Evaluation
- HIM FPX 2670 Assessment 3: Implementation and Governance Plan
HIM FPX 3640 Assessment 3 questions, answered
Can the proposal recommend a new system?
It can, but the criteria here read for a change to how an entry is made rather than for a procurement. A narrower change to a template, a field, a prompt or a workflow step is easier to specify, test, train and measure, and specification is where most of the credit sits. If your instructions require something larger, keep the same discipline and scope the testing honestly.
How do I show the change worked?
Measure the same thing before and after, using definitions written down first. If the problem was a copy-forward rate in a sample of notes, the proof is that audit run again on a comparable sample once the change has been live long enough to be normal practice. Name the period and state what else could explain a difference.
Should the proposal include cost?
In categories rather than as a figure. Build hours, testing time, training time and the temporary productivity loss during the first days are the real costs of a configuration change, and stating them as categories with assumptions is stronger than a number you cannot source. Where your scenario supplies rates, use those and cite them.
Where can I find a free HIM FPX 3640 Assessment 3 sample paper?
This page contains the full proposal to redesign the hospitalist progress note template, with build-level specification, testing, alert burden, risks, training and measures. A model proposal is available free.
Why use the audit criteria to measure results in HIM FPX 3640 Assessment 3?
So the before and after results are directly comparable. Changing the measure would make it impossible to show whether the template change reduced copy-forward.