| Course | DDHA 8303 Research Methods for Healthcare Administrators |
|---|---|
| Week | Week 7 |
| Paper type | Sampling plan |
| Length | About 1,180 words, 7 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 7
Every Coder on the Roster, Sixteen in the Interview Room and the Ones Who Already Left: A Sampling Plan for a Study of Remote Inpatient Coders
Student Name
Walden University
DDHA 8303: Research Methods for Healthcare Administrators
Instructor Name
Month Day, Year
Every Coder on the Roster, Sixteen in the Interview Room and the Ones Who Already Left: A Sampling Plan for a Study of Remote Inpatient Coders
Target Population
The study's target population is every person employed by Halvorsen Health as an inpatient coder at any time from January 2023 through December 2025. For this plan, an inpatient coder is anyone who held the human resources job code for Inpatient Coder I or Inpatient Coder II and who assigned DRGs to inpatient accounts during that period. The definition is written so that an administrator could apply it to a roster without judgment: role by job code, unit by the inpatient coding department, tenure by dates in the job code and exposure by the work arrangement recorded in each month. Coding supervisors, outpatient and professional fee coders and clinical documentation specialists fall outside it, even if they occasionally coded inpatient accounts, because their work is audited differently.
Sampling Frame
The frame is built from three sources: the human resources roster of job codes, the coding workflow system's list of users who finalized inpatient accounts and the internal audit database. Matching the three produces 78 people who meet the definition, of whom 64 were employed at the end of 2025 and 14 had left.
The frame is not identical to the population, and the differences matter. First, agency coders hired through a staffing firm to clear backlogs appear in the workflow system but not in the roster, so their work arrangements are not recorded; there were nine during the period. Second, two coders changed job codes mid-period and appear twice under different identifiers, which the matching resolved by employee number. Third, the audit database begins recording coder identifiers consistently only from January 2023, which is why the study period starts there. Everyone who qualifies under the definition and was employed by Halvorsen can be listed. Agency coders qualify in every respect except employment and cannot be listed with the information the study needs.
Selection Technique
The two branches of the study select differently, consistent with the design argued in Week 5.
The quantitative branch uses a census. Every person in the frame with at least six consecutive months of audit records is included, because the difference-in-differences analysis depends on comparing each coder with themselves over time and on comparing groups that moved at different times. Sampling from 78 people would add sampling error without saving meaningful effort, since the records already exist.
The qualitative branch uses purposeful sampling for maximum variation. Palinkas et al. (2015) describe purposeful sampling as selecting information-rich cases, and maximum variation as choosing participants who differ on dimensions expected to shape the phenomenon. Here, those dimensions are work arrangement, move wave, tenure and hospital of origin. The target is sixteen coders: six from the January 2024 wave, five from the September wave and five who stayed onsite or hybrid, with each group including coders above and below five years of tenure and from at least three of the five hospitals.
Recruitment
Recruitment for the interviews proceeds in five steps, each dependent on a specific kind of access.
In the first step, the system's research office, not the director of health information management, sends an invitation to every current coder in the frame. This depends on the research office's agreement and on the coders' work email list, which human resources has agreed to provide. Second, coders who are interested reply directly to the research office, which keeps their response private from coding management. Third, a member of the research team screens respondents against the variation targets, using arrangement, wave, tenure and hospital from the frame rather than asking respondents to report them. Fourth, selected coders are scheduled for a 45-minute interview by video or in person during paid time that is excluded from productivity tracking, which depends on the coding manager's written agreement to suspend the productivity count for that period. Fifth, the consent process described in the ethics protocol takes place before the interview begins.
The quantitative branch requires no recruitment, because it uses existing audit records under an approved data use agreement.
Inclusion and Exclusion Rules
Inclusion for the quantitative branch: listed in the frame; at least six consecutive months with ten or more audited accounts; work arrangement recorded for every included month.
Inclusion for the qualitative branch: all of the above, plus currently employed at Halvorsen and holding the inpatient coder job code on the date of invitation.
Exclusion for both branches: any month in which the coder was in orientation, on leave for more than half the month or assigned to a special project that removed them from routine coding, as recorded in human resources and workflow data.
Exclusion for the qualitative branch only: members of the research team's own reporting line. One coder who serves on the audit team that produces the outcome data is excluded from interviews to avoid confusing her two roles.
Each rule can be checked against a record. None relies on a judgment about the coder's suitability.
Coverage: Who the Plan Misses
The most important group the plan cannot fully reach is the fourteen coders who left. Their audit records remain, so the quantitative branch includes them up to their departure. The interviews cannot include them. If coders who struggled with remote work were more likely to leave, the interviews will hear mainly from those for whom it worked, and the qualitative account of how remote coders resolve uncertain decisions will be biased toward successful strategies. The plan addresses this by asking human resources whether exit interview summaries for those fourteen can be shared in de-identified form; if they can, they will be analyzed as a separate source and labeled as such.
The second group is the nine agency coders. They did coding work during the period but cannot be placed in a work arrangement group. Excluding them is necessary, but readers should know that some accounts coded during busy months were coded by people outside the study.
The third group is current coders who decline interviews. Groves and Peytcheva (2008), in a meta-analysis of survey nonresponse, showed that a low response rate by itself says little about how biased results will be; what matters is whether the reasons people decline are connected to what is being studied. For this study, a coder anxious about their accuracy might be less willing to talk, which would be such a relationship. The plan will compare interviewed and non-interviewed coders on tenure, arrangement and audit agreement, using frame data, and report any differences.
What This Means for the Claim
The quantitative findings will apply to Halvorsen's employed inpatient coders over the study period, including those who left. The qualitative findings will describe how current coders, and possibly some former ones through exit data, explain their practices, and they should not be read as representing everyone who tried remote coding. Polit and Beck (2010) suggest that qualitative findings support transferability when their conditions are described clearly enough for readers to judge similarity. This plan's coverage section is part of that description.
References
Groves, R. M., & Peytcheva, E. (2008). The impact of nonresponse rates on nonresponse bias: A meta-analysis. Public Opinion Quarterly, 72(2), 167-189. https://doi.org/10.1093/poq/nfn011
Palinkas, L. A., Horwitz, S. M., Green, C. A., Wisdom, J. P., Duan, N., & Hoagwood, K. (2015). Purposeful sampling for qualitative data collection and analysis in mixed method implementation research. Administration and Policy in Mental Health and Mental Health Services Research, 42(5), 533-544. https://doi.org/10.1007/s10488-013-0528-y
Polit, D. F., & Beck, C. T. (2010). Generalization in quantitative and qualitative research: Myths and strategies. International Journal of Nursing Studies, 47(11), 1451-1458. https://doi.org/10.1016/j.ijnurstu.2010.06.004
What the DDHA 8303 Week 7 instructions ask for
The sampling plan typically asks you to specify who your study will include and how you will reach them. Define the target population in terms someone could apply to a roster, such as role, unit, tenure and exposure. Describe your sampling frame and be honest about how it differs from the population. Name the selection technique and justify it against your design. Set out recruitment as concrete steps, noting what access each depends on. Write inclusion and exclusion criteria as rules that can be checked. Close with coverage: identify who your route systematically misses and explain how that limits the claims you can make.
Inside the DDHA 8303 Week 7 example
The plan defines inpatient coders by job code and work between 2023 and 2025, and excludes supervisors and documentation specialists. The frame section matches three record systems to find 78 people and lists three gaps, including agency coders. Selection uses a census for the audit branch and maximum variation sampling for sixteen interviews, with targets by wave and tenure. Recruitment runs through the research office in five steps, from invitation to consent, including protected interview time. Inclusion and exclusion rules are listed by branch. The coverage section examines departed coders, agency coders and decliners in turn, citing Groves and Peytcheva, and the plan closes by stating what each branch's findings will and will not represent.
Where the marks sit in the DDHA 8303 Week 7 rubric
Sampling plans are assessed on precision and honesty. Markers look for a population definition that can be applied without judgment and a frame whose gaps are acknowledged. The selection technique must be named correctly and linked to the design chosen earlier. Recruitment steps should be concrete and realistic about access. Criteria written as checkable rules earn more than preferences. The coverage discussion is often the most heavily weighted part, because it shows whether the writer understands how sampling shapes the eventual claim. Correct use of sampling and nonresponse literature supports the evidence criterion, and an organized, procedural tone suits the format. Graders also check that the sample sizes promised here match what the design needs.
DDHA 8303 Week 7 help from the desk
A common weakness is treating the sampling frame as identical to the population, which hides coverage problems. List the frame's sources and its gaps. Another is choosing convenience sampling and calling it purposeful; explain what makes each participant information-rich. Recruitment through managers creates pressure in workplace studies, so route invitations elsewhere. Write criteria a stranger could apply. Do not skip the people your route will never reach, such as staff who left. If your setting makes sampling complicated, our writers are able to prepare a plan built around your organization's records and access. State the size of each group you cannot reach, even roughly, so readers can judge how much it matters. Then say what your findings will represent once those groups are missing.
Get a DDHA 8303 Week 7 example written to your instructions
Forward the Week 7 prompt, the rubric and the design already defended, and a finished sampling plan arrives inside 24-48 hours, the first one free, covering the recruitment route and its coverage gaps. Recruitment examples name a composite population, while the staff rosters and contact lists an actual department maintains are left untouched by the desk.
More DDHA 8303 papers and DHA samples
- DDHA 8303 Week 1: Researchable Questions Post
- DDHA 8303 Week 2: Researchable Problem Statement
- 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 8: Instrument Appraisal
- DDHA 8303 Week 9: Ethics Protocol
- DDHA 8303 Week 10: Analysis Plan
- DDHA 8303 Week 11: Methodology Section
- DDHA 8203 Week 7: Inventory Decision Paper
- DDHA 8113 Week 7: Substituted Supply Ethics Case
- DDHA 8103 Week 7: Disclosure Letter
- DDHA 8006 Week 7: Doctoral Position Paper
DDHA 8303 Week 7 questions, answered
Where can I find a free DDHA 8303 Week 7 sample paper?
The whole sampling plan for the remote coder study is posted here to read at no cost.
How is the population defined in the DDHA 8303 Week 7 example?
Everyone who held the Inpatient Coder I or II job code and assigned DRGs to inpatient accounts from 2023 through 2025.
Why does the audit branch use a census instead of a sample?
The design compares each coder over time, and sampling from 78 people would add error without saving effort since the records exist.
Who does the recruitment route miss?
Fourteen coders who left, nine agency coders without recorded work arrangements and current coders who decline interviews.
How are interview invitations kept away from managers?
The research office sends them, coders reply only to that office and managers are not told who responded.