| Course | MMHA 6600 Healthcare Informatics and Technology Management |
|---|---|
| Week | Week 4 |
| Paper type | Data quality memo |
| Length | About 820 words, 4 pages |
| Format | Memo, APA 7 citations |
| School | Walden University |
| Program | Master of Healthcare Administration (MHA) |
| Updated | October 2026 |
Free sample paper for MMHA 6600 Week 4
Memorandum
To: Chief Nursing Officer and Director of Pharmacy, Bramble Creek Hospital
From: Health Informatics Analyst (MMHA student)
Date: Month Day, Year
Re: Data quality of patient weight and its path to weight-based dose calculations
Summary
Patient weight is one of the most consequential numbers in our record because the order system uses it to calculate weight-based doses of heparin, enoxaparin, several antibiotics and most pediatric medications. A review of how weight enters the record found that it arrives by three routes, measured, stated by the patient or family, or estimated by staff, and that the record stores all three in the same field with no label. A fourth route, carrying forward a weight from a previous encounter, fills the field when nobody enters a new value. I recommend labeling the source of every weight and requiring a measured weight before the first weight-based dose wherever a scale is available.
How Weight Enters the Record
I traced weight entries on admission for one month across the emergency department and two inpatient units, interviewed triage and floor nurses, and reviewed the field's configuration with the build team. The figures below are illustrative values prepared for this sample memo.
Table 1
Source of the First Recorded Weight on Admission (Illustrative, One Month)
| Source | Who typically enters it | Share of admissions | Visible to prescriber as |
|---|---|---|---|
| Measured on a scale | Triage or floor nurse | 54% | Weight |
| Stated by patient or family | Triage nurse | 27% | Weight |
| Estimated by staff | Triage nurse, often for stretcher arrivals | 9% | Weight |
| Carried forward from a prior encounter | No one; system default | 10% | Weight |
Nearly half of first weights were not measured, and the prescriber sees all four sources as the same plain number.
Why the Source Matters
Data quality frameworks distinguish whether a value is present, whether it is plausible and whether it is correct for the purpose at hand (Weiskopf & Weng, 2013). A stated weight is present and usually plausible, but its correctness for dosing depends on how recently the patient was weighed and how well they remember. A staff estimate is quicker still and less accurate; in an emergency department study, both doctors' and nurses' visual estimates were often wrong by more than ten percent (Menon & Kelly, 2005). A carried-forward weight may be months old and may predate a large change, such as fluid overload in heart failure or weight loss during cancer treatment.
For many drugs, a ten percent error is clinically minor. For weight-based anticoagulants and some antibiotics with narrow margins, it is not. The same number can be fit for one use and unfit for another, which is the core idea in the consumer view of data quality: quality depends on the task the data serve (Wang & Strong, 1996).
The Path From Field to Dose
Once a weight is in the field, it flows without further review. The dose calculator in the order composer reads the most recent weight and displays a calculated dose; the prescriber sees the result, not the source. Pharmacy verification checks the calculation but has no way to see whether the weight was measured. The medication administration record shows the dose, not the weight. At no point after entry does anyone see a label saying stated, estimated or carried forward.
Two safety reports in the past year, both near misses, involved enoxaparin doses calculated from weights carried forward from encounters more than a year earlier. In each case a nurse noticed that the patient looked very different from the weight on file.
Recommendations
The policy change will need exceptions for emergencies, where a dose cannot wait for a scale. In those cases the label itself is the safeguard: a prescriber who sees estimated beside a weight knows to reweigh and recalculate once the patient is stable. The monthly audit uses a measure that data quality frameworks for secondary use already describe, the share of values that conform to a stated rule (Kahn et al., 2016).
Table 2
Recommended Changes, Owner and Timing
| Change | Owner | Timing |
|---|---|---|
| Add a required source label to the weight field: measured, stated, estimated | Record build team | Next configuration cycle |
| Stop carrying weight forward into new encounters; leave the field blank until entered | Record build team with pharmacy | Next configuration cycle |
| Show the weight, its source and its time beside every weight-based dose calculation | Pharmacy informatics | Within two cycles |
| Require a measured weight before the first weight-based dose of listed high-risk drugs where a bed or chair scale is available | Nursing practice council and pharmacy and therapeutics committee | Policy within one quarter |
| Audit the share of first weights that are measured each month | Quality department | Ongoing |
The first two changes cost almost nothing and remove the silent default; the third puts the source where the decision is made.
What I Need From You
I ask for two decisions: approval to place the labeling and carry-forward changes in the next configuration cycle, and your joint sponsorship as the measured-weight policy moves through both nursing and pharmacy committees. I will report the first month's audit to both of you.
References
Kahn, M. G., Callahan, T. J., Barnard, J., Bauck, A. E., Brown, J., Davidson, B. N., Estiri, H., Goerg, C., Holve, E., Johnson, S. G., Liaw, S.-T., Hamilton-Lopez, M., Meeker, D., Ong, T. C., Ryan, P., Shang, N., Weiskopf, N. G., Weng, C., Zozus, M. N., & Schilling, L. (2016). A harmonized data quality assessment terminology and framework for the secondary use of electronic health record data. eGEMs, 4(1), 1244. https://doi.org/10.13063/2327-9214.1244
Menon, S., & Kelly, A.-M. (2005). How accurate is weight estimation in the emergency department? Emergency Medicine Australasia, 17(2), 113-116. https://doi.org/10.1111/j.1742-6723.2005.00701.x
Wang, R. Y., & Strong, D. M. (1996). Beyond accuracy: What data quality means to data consumers. Journal of Management Information Systems, 12(4), 5-33. https://doi.org/10.1080/07421222.1996.11518099
Weiskopf, N. G., & Weng, C. (2013). Methods and dimensions of electronic health record data quality assessment: Enabling reuse for clinical research. Journal of the American Medical Informatics Association, 20(1), 144-151. https://doi.org/10.1136/amiajnl-2011-000681
What the MMHA 6600 Week 4 instructions ask for
Data quality memos ask you to pick one data element and show how its quality affects a decision. Choose something consequential, such as weight, allergies or code status. Trace how it enters the record, who enters it and how often each route is used. Apply a recognized data quality framework so your judgment rests on defined dimensions, not impressions. Follow the value downstream to the point where it changes care, and show whether anyone sees its source there. Include any safety reports or near misses. Recommend changes in order of cost, with an owner and timing for each. End by asking the recipients for specific decisions. Keep memo format: a clear subject line, short sections and no long introduction.
How this MMHA 6600 Week 4 example is built
The memo's summary states the problem, its cause and the fix in one paragraph. Table 1 shows four sources of the first recorded weight, who enters each and how prescribers see it. A section applies Weiskopf and Weng's dimensions, cites Menon and Kelly on visual estimates and uses Wang and Strong's fitness-for-use view to explain why the same value can be fine for one task and unsafe for another. A path section follows the weight through the dose calculator, pharmacy verification and the medication record, noting two near misses. Table 2 lists five changes with owners and timing. The close asks two executives for approval and sponsorship.
Reading the MMHA 6600 Week 4 rubric
Grading on this memo favors a clear line from data to decision. Showing where a value comes from, by route and by role, earns the first portion of credit. Using a published framework to describe quality, rather than calling data good or bad, is expected and rewarded. Tracing the value to the point of harm shows systems thinking. Including local evidence, such as near misses, strengthens the case. The plan section is rewarded for being specific, costed and owned, and when exceptions such as emergencies are handled. A memo that ends with a precise request shows professional judgment. Brevity counts on this assignment, and a reader should find the decision without searching, with sources cited where each claim is made.
Common MMHA 6600 Week 4 mistakes, and how to avoid them
Data quality memos often describe a problem without showing anyone why it matters. Pick a field that drives a decision, then follow it all the way there. Ask nurses and clerks how they really enter it; the answer often differs from policy. Count how often each route is used, even roughly. Use one framework and name it. Watch for silent defaults, such as values copied from old visits. Recommend the cheapest change first, and plan for emergencies where the ideal process is impossible. Ask for a decision at the end. We can help you trace a data element through your own organization's record and turn what you find into a short memo for leaders.
Get a MMHA 6600 Week 4 example written to your instructions
Say which data element your Week 4 prompt names, weight, allergy, race and ethnicity or another, and pair it with the rubric. A memo tracing that element arrives in 24-48h, free the first time. The hospital and its entry screens are invented, and the desk has no use for extracts from any record system you work in.
More MMHA 6600 papers and MHA samples
- MMHA 6600 Week 1: Admission Workflow Redesign
- MMHA 6600 Week 2: Copy-Forward Note Review
- MMHA 6600 Week 3: Pain Order Usability Review
- MMHA 6600 Week 5: Efficiency Dashboard Critique
- MMHA 6600 Week 6: Messaging Vendor Selection Memo
- MMHA 6600 Week 7: Allergy Alert Fatigue Case
- MMHA 6600 Week 8: Anticoagulant Registry Design
- MMHA 6600 Week 9: Anesthesia Record Go-Live
- MMHA 6600 Week 10: Downtime Drill Report
- MMHA 6600 Week 11: Handoff Tool Adoption Memo
- MMHA 6540 Week 4: Need Ranking Matrix
- MMHA 6530 Week 4: Care Model Comparison Memo
- MMHA 6520 Week 4: Denominator Specification
- MMHA 6501 Week 4: Change Management Memo
MMHA 6600 Week 4 questions, answered
Where can I find a free MMHA 6600 Week 4 sample paper?
The weight data quality memo, with both tables and its references, can be read on this page.
What four sources of weight does the MMHA 6600 Week 4 memo find?
Measured on a scale, stated by the patient or family, estimated by staff, and carried forward by the system from a prior encounter.
Why does the source of a weight matter for dosing?
Stated, estimated and old weights can be off by more than ten percent, which matters for weight-based anticoagulants and some antibiotics.
Which framework does the memo use?
Weiskopf and Weng's data quality dimensions, together with Wang and Strong's idea that quality depends on the use.
What is the first recommended change?
A required source label on every weight entry, which costs little and travels with the value to the dose calculator.