| Course | DDHA 8303 Research Methods for Healthcare Administrators |
|---|---|
| Week | Week 2 |
| Paper type | Researchable problem statement |
| Length | About 550 words, 4 pages |
| Format | APA 7 student paper |
| School | Walden University |
| Program | Doctor of Healthcare Administration (DHA) |
| Updated | October 2026 |
Free sample paper for DDHA 8303 Week 2
From "The Remote Coders Are Rushing" to a Problem a Study Can Address: Inpatient Coding Accuracy Before and After a Move to Remote Work at a Five-Hospital System
Student Name
Walden University
DDHA 8303: Research Methods for Healthcare Administrators
Instructor Name
Month Day, Year
From "The Remote Coders Are Rushing" to a Problem a Study Can Address: Inpatient Coding Accuracy Before and After a Move to Remote Work at a Five-Hospital System
The Complaint
At a revenue cycle meeting, the director of health information management at Halvorsen Health, a composite five-hospital system, said that payer DRG downgrades had risen since coding went home and that she believed remote coders were rushing.
Background
Inpatient coding sets the diagnosis-related group on which most inpatient payment rests, so errors carry financial and compliance consequences in both directions: undercoding loses revenue and overcoding invites recovery and penalties. Coding accuracy also matters beyond payment, because coded data feed quality measures, research and population health reporting. O'Malley et al. (2005), reviewing sources of error in ICD coding, describe how errors arise at several points between the patient encounter and the final code, including documentation, coder training and experience, and the coder's own judgment. A change in where coders work could plausibly affect some of those points, for example by reducing informal consultation with colleagues or with clinical documentation specialists, and leave others untouched.
The wider evidence on remote work does not settle the question. Gajendran and Harrison (2007), in a meta-analysis of telecommuting studies, found small positive associations between telecommuting and supervisor-rated performance, alongside evidence that high-intensity telecommuting harmed relationships with coworkers. Allen et al. (2015) concluded that results differ by occupation and by how many days people spend away from the office. Neither review isolates rule-based clinical documentation work of the kind coders do, and neither measures accuracy against an audit standard. Halvorsen moved 41 of its 64 inpatient coders to fully remote work in two waves, in January and September 2024, while 23 coders stayed onsite or hybrid. That staggered move, together with the system's routine monthly coding audits, creates an opportunity to examine the question with the organization's own records.
Problem Statement
Among inpatient coders at a five-hospital health system, it is not known whether the transition to fully remote work in 2024 was followed by a change in coding accuracy, measured as the rate of agreement between the coder's assigned DRG and the DRG assigned by internal auditors, relative to coders who did not move.
Purpose
This study aims to estimate whether, and by how much, DRG agreement rates changed for coders who moved to remote work compared with coders who did not, and to describe how coders in both groups account for any differences in their work practices.
Boundaries
The study will not evaluate whether remote work should continue, which is a management decision involving recruitment, retention and cost. It will not attempt to measure coder productivity, which is tracked separately and would require a different design. It will not examine outpatient or professional fee coding, which use different classification systems and audit processes. Payer downgrades will be described as context but will not serve as the outcome, because they reflect payer audit intensity as well as coding quality. A payer that doubles the number of claims it reviews will find more disagreements even if coders have not changed at all, and Halvorsen's largest commercial payer expanded its inpatient review program in 2024. Internal audit agreement, by contrast, is measured the same way every month by staff who apply one standard to all coders.
References
Allen, T. D., Golden, T. D., & Shockley, K. M. (2015). How effective is telecommuting? Assessing the status of our scientific findings. Psychological Science in the Public Interest, 16(2), 40-68. https://doi.org/10.1177/1529100615593273
Gajendran, R. S., & Harrison, D. A. (2007). The good, the bad, and the unknown about telecommuting: Meta-analysis of psychological mediators and individual consequences. Journal of Applied Psychology, 92(6), 1524-1541. https://doi.org/10.1037/0021-9010.92.6.1524
O'Malley, K. J., Cook, K. F., Price, M. D., Wildes, K. R., Hurdle, J. F., & Ashton, C. M. (2005). Measuring diagnoses: ICD code accuracy. Health Services Research, 40(5, Pt. 2), 1620-1639. https://doi.org/10.1111/j.1475-6773.2005.00444.x
What the DDHA 8303 Week 2 instructions ask for
The second week typically asks you to turn a workplace complaint into a problem a study could address. State the complaint briefly, in a line, and then leave that register behind. Write a short background paragraph explaining why the issue matters to operations, supported by health services or management literature rather than feeling. Set the problem statement apart and make it one or two sentences naming a population, a setting, a condition and an observable outcome. Add a purpose sentence that says what the study will estimate or describe. Finish with boundaries that list what the study will not attempt. Keep the document compact, and do not drift into proposing methods yet.
How the DDHA 8303 Week 2 example is put together
The document opens with the director's complaint in one sentence. The background explains how inpatient coding sets payment and why errors cut both ways, then uses O'Malley and colleagues to show that errors arise at several points a move home might affect. It summarizes the telecommuting reviews and notes what they do not measure, before describing the staggered move and the monthly audits that make a local study possible. The problem statement names the coders, the move and DRG agreement relative to coders who stayed. The purpose sentence pairs an estimate of change with a description of how coders explain it. The boundary section excludes the decision itself, productivity, outpatient coding and payer downgrades, with a reason for the last.
Reading the DDHA 8303 Week 2 rubric
Problem statements are judged on precision. Markers check for a defined population, a setting, a condition and an outcome that could be observed, and a statement missing any of these loses ground. The background is assessed on relevance: literature that explains why the problem matters to operations is rewarded, while clinical trial citations or general commentary are not. The purpose must align with the problem rather than widening it. A boundary section shows judgment about scope. Because this is an early deliverable, writing a proposal or choosing methods too soon can count against you. Concise, scholarly prose and correct APA format matter more in a short document, since there is little room to recover from errors.
DDHA 8303 Week 2 help: mistakes that cost marks
Many drafts keep the emotional tone of the complaint throughout. Quote or paraphrase it once, then write as an analyst. Another weakness is an outcome that cannot be observed, such as quality or morale, without saying how it would be measured. Choose something an existing system records if you can. Be careful about outcomes driven by outside factors, as payer downgrades are by audit intensity. Write boundaries that are real choices, not filler. Avoid jumping ahead to design. If turning a complaint from your workplace into a clean problem statement is proving difficult, we are able to draft one from your notes and your course's template.
Get a DDHA 8303 Week 2 example written to your instructions
The desk writes a finished researchable problem to the prompt and rubric you forward, first one free and back inside 24-48 hours, built around the complaint you name. Examples are anchored to an invented service line, because nothing sitting in a workplace file gets rebuilt on this desk, and the local version stays yours to write afterward.
More DDHA 8303 papers and DHA samples
- DDHA 8303 Week 1: Researchable Questions Post
- DDHA 8303 Week 3: Article Appraisal
- DDHA 8303 Week 4: Research Question Set
- DDHA 8303 Week 5: Design Justification
- DDHA 8303 Week 6: Single-Site Claims Post
- DDHA 8303 Week 7: Sampling Plan
- DDHA 8303 Week 8: Instrument Appraisal
- DDHA 8303 Week 9: Ethics Protocol
- DDHA 8303 Week 10: Analysis Plan
- DDHA 8303 Week 11: Methodology Section
- DDHA 8203 Week 2: Process Map
- DDHA 8113 Week 2: Leadership Theory Comparison
- DDHA 8103 Week 2: Event Chronology Analysis
- DDHA 8006 Week 2: Scholarly Voice Exercise
DDHA 8303 Week 2 questions, answered
Where can I find a free DDHA 8303 Week 2 sample paper?
The full researchable problem statement on remote inpatient coders is posted on this page without charge.
What problem does the DDHA 8303 Week 2 example state?
Whether DRG agreement with internal auditors changed for inpatient coders after their 2024 move to remote work, compared with coders who did not move.
Why are payer downgrades not the outcome?
They depend on how many claims a payer reviews as well as on coding quality, and one large payer expanded its reviews in 2024.
What does the boundary note exclude?
The decision about remote work itself, coder productivity, outpatient and professional fee coding and payer downgrades as the outcome.
Which sources support the background?
O'Malley and colleagues on ICD coding error, plus reviews of telecommuting by Gajendran and Harrison and by Allen and colleagues.