| Course | HS880 Doctoral Project III: Data Collection and Analysis |
|---|---|
| Unit | Unit 4 |
| Paper type | Codebook draft |
| Length | About 890 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | Doctor of Health Science (DHSc) |
| Updated | October 2026 |
Free sample paper for HS880 Unit 4
Fourteen Parent Codes Before the First Transcript: A Unit 4 Codebook Draft for a Theory-Led Study of Shielding Habits
[Student Name]
Purdue University Global
HS880: Doctoral Project III: Data Collection and Analysis
Unit 4 Codebook Draft
[Instructor Name]
[Date]
The study and the example passages are composite and invented for illustration before any data exist; the methods and framework sources cited are real.
Approach
The study codes interview transcripts using directed content analysis, in which initial codes come from an existing theory and are refined as data are analyzed, rather than emerging entirely from the text (Hsieh & Shannon, 2005). The theory here is the Theoretical Domains Framework, and each of its validated domains becomes one parent code (Cane et al., 2012). Following published guidance on using the framework in qualitative research, coders will first assign passages to domains and then write belief statements, short summaries of shared beliefs within each domain, such as "parents will complain if no shield is used" (Atkins et al., 2017).
Code Structure
Each parent code has five parts: name, definition, include when, exclude when and boundary note. Child codes, the belief statements, will be added during analysis. Version numbers start at 1.0 and rise with every change, each logged with a date and reason.
Selected Parent Codes
Knowledge. Definition: awareness of the current guidance on gonadal shielding and its rationale. Include when the participant describes what the guidance says, when it changed or why. Exclude when the participant describes what others expect, which belongs to social influences. Invented example: "I know the physicists said we can stop, and why." Boundary note: knowing the guidance and believing it are different; a passage doubting the rationale belongs to beliefs about consequences.
Beliefs about consequences. Definition: what the participant expects will happen if a shield is or is not used. Include outcomes for the patient, the image, the participant or the department. Exclude statements about the participant's ability to perform without a shield. Invented example: "If I skip it and the mum notices, I'm the one who gets the complaint." Boundary note: when the expected consequence comes from another person's reaction, code here and also under social influences.
Social influences. Definition: what other people expect, do or say that bears on shielding. Include patients, parents, colleagues, supervisors and radiologists. Exclude physical features of the room. Invented example: "The older techs still shield every kid, so the new grads copy them." Boundary note: a parent asking where the shield is belongs here, even when the shield's absence from the room prompted the question.
Environmental context and resources. Definition: physical, material and organizational features of the setting. Include where shields are stored, whether they hang on the table, workload and room layout. Exclude other people's expectations. Invented example: "The shield hangs right on the bucky handle, so it just goes on." Boundary note: the presence of an object that cues behavior belongs here; a person who cues behavior belongs under social influences.
Memory, attention and decision processes. Definition: how shielding decisions are made in the moment, including habit and automatic action. Include descriptions of not thinking about it or doing it without deciding. Invented example: "Honestly, my hands do it before I think." Boundary note: overlaps with behavioral regulation when the participant describes efforts to stop.
Social or professional role and identity. Definition: how shielding relates to the participant's sense of being a radiographer. Include statements that shielding shows care or professionalism. Invented example: "Putting the shield on is part of being careful with kids."
The remaining eight domains, skills, beliefs about capabilities, optimism, reinforcement, intentions, goals, emotion and behavioral regulation, follow the same structure in the full codebook.
A boundary note earns its place when two careful coders, reading the same passage, would otherwise reach for different codes.
Residual Code
Outside framework. Definition: content relevant to shielding decisions that no domain captures. Every passage placed here will be reviewed at each codebook revision, either to refine a domain definition or to report as a finding the framework did not anticipate.
How the Codebook Connects to the Survey
Every parent code matches a block of survey items measuring the same domain, so the joint display can set each domain's survey result beside what interviewees said about it. This matching is why the codebook keeps the framework's domain names exactly as the survey does, even where a plainer label might read better in a transcript. When the survey shows a domain differing between routine shielders and others, the codebook's belief statements for that domain will be read first, to see whether interviewees explain the difference. When a domain shows no survey difference but is prominent in interviews, that discordance will be reported rather than smoothed over.
Procedures for Use
The student will code all transcripts. A second coder will independently code [25] percent, chosen to span shielding practice and site type. Disagreements will be discussed, and any resulting change to a definition will produce a new version of the codebook. Agreement will be reported descriptively rather than as a single coefficient, in line with debates about the value of reliability statistics in interpretive work (O'Connor & Joffe, 2020).
Limits
Invented examples may not resemble real speech. Domains overlap, especially social influences and environmental context, and the boundary notes may need revision once real passages arrive.
References
Atkins, L., Francis, J., Islam, R., O'Connor, D., Patey, A., Ivers, N., Foy, R., Duncan, E. M., Colquhoun, H., Grimshaw, J. M., Lawton, R., & Michie, S. (2017). A guide to using the Theoretical Domains Framework of behaviour change to investigate implementation problems. Implementation Science, 12, 77. https://doi.org/10.1186/s13012-017-0605-9
Cane, J., O'Connor, D., & Michie, S. (2012). Validation of the theoretical domains framework for use in behaviour change and implementation research. Implementation Science, 7, 37. https://doi.org/10.1186/1748-5908-7-37
Hsieh, H.-F., & Shannon, S. E. (2005). Three approaches to qualitative content analysis. Qualitative Health Research, 15(9), 1277-1288. https://doi.org/10.1177/1049732305276687
O'Connor, C., & Joffe, H. (2020). Intercoder reliability in qualitative research: Debates and practical guidelines. International Journal of Qualitative Methods, 19, 1-13. https://doi.org/10.1177/1609406919899220
Reading the HS 880 Unit 4 instructions
The fourth unit typically asks candidates to draft the codebook they will use to analyze qualitative data, often four to six pages. Instructors expect the analytic approach to be named and justified, codes defined clearly enough for a second person to apply them, inclusion and exclusion rules, examples and a plan for revising the codebook as analysis proceeds. For theory-led studies, the framework's constructs usually supply the initial codes, with a residual code for content outside the framework. Many prompts ask how codes relate to other study components, such as survey items, and how consistency between coders will be checked. Examples written before data collection should be labeled as invented.
Inside the HS880 Unit 4 example
The draft explains directed content analysis and belief statements with citations, then describes the five parts of each code and the version numbering. Six parent codes are written out in full: knowledge, beliefs about consequences, social influences, environmental context and resources, memory and decision processes, and professional role and identity, each with an invented example and a boundary note. The highlighted sentence explains when a boundary note earns its place. A residual code is defined. A section links each code to its matching survey block and explains how discordant domains will be reported. Procedures for a second coder and descriptive reporting of agreement precede the limits.
Reading the HS880 Unit 4 grading rubric
Codebooks are commonly graded on clarity of definitions, usefulness of inclusion and exclusion rules, grounding in the chosen analytic approach, provisions for revision and consistency checks, and connection to the study's other components. Clarity often counts most, since a definition two coders interpret differently undermines the analysis. Rules and boundary notes earn credit when they address known overlaps between codes. Grounding rewards accurate description of the analytic method with citations. Revision and consistency provisions show that the codebook will evolve transparently. Linking codes to survey items for integration can raise the score in mixed methods projects. Honest labeling of invented examples is expected. Committee members often apply a definition to a sample passage themselves, so precise wording pays off.
HS880 Unit 4 help: mistakes that cost points
The most frequent weakness is codes defined in a single word, which leaves every boundary to the coder's judgment. Another is a codebook with no residual code, forcing all content into the framework whether it fits or not. Some candidates present invented examples as if they were real data. Others plan to report a single reliability coefficient without considering whether it suits interpretive work. Codebooks that never mention how they will change during analysis suggest a rigid approach. If your study uses a different framework or an inductive approach, send your research questions and interview guide, and a codebook can be drafted with definitions, rules and boundary notes. Using framework domain names inconsistently between the codebook and survey also complicates integration later.
Get an HS880 Unit 4 example written to your instructions
Codebooks follow the analytic approach: theory-driven, inductive, or a hybrid of the two. Share the Unit 4 prompt, the rubric, your framework and research questions, and say how many coders will work. The sample defines each code with inclusion, exclusion and boundary rules and leaves belief statements for your own data. First custom sample free; back in 24-48h. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More HS880 papers and DHSc samples
- HS880 Unit 1: Survey and Interview Recruitment Plan
- HS880 Unit 2: Low Survey Response Discussion Post
- HS880 Unit 3: Research Data Management Protocol
- HS880 Unit 5: Coding Memo
- HS880 Unit 6: Seminar Reflection
- HS880 Unit 7: Descriptive Results Summary
- HS880 Unit 8: Analysis Output Narrative
- HS880 Unit 9: Deviation and Limitation Memo
- HS880 Unit 10: Results Chapter Draft
- HS865 Unit 4: Gonadal Shielding Thematic Review
- HS810 Unit 4: Legislative History Brief
- HS860 Unit 4: Purpose and Research Question Alignment
- HS820 Unit 4: France Health Financing Analysis
HS880 Unit 4 questions, answered
What is directed content analysis?
One of three approaches to qualitative content analysis described by Hsieh and Shannon in 2005. It starts from existing theory or research to define initial coding categories, then codes the data against them. Text that does not fit is identified and later examined as a possible new category. It suits studies that aim to extend or test a framework rather than build one from scratch.
What are belief statements in TDF research?
Short summaries of the shared beliefs participants express within a domain, such as parents expect a shield and will complain without one. Atkins and colleagues recommend generating them during analysis, grouping similar quotations under each, then judging which domains matter by frequency, conflict among beliefs and likely effect on the behavior. They make domain-level findings concrete.
Why include invented examples in a codebook?
Examples show coders how a definition applies, which improves consistency. Before collection there is no real data, and using participants' words before consent would be improper. Invented extracts, clearly labeled, serve the teaching purpose. Once coding begins, many teams replace them with real anonymized extracts in later versions, recording the change in the version log.
Where can I find a free HS880 Unit 4 sample paper?
This page presents the complete Unit 4 codebook draft with fourteen framework-based parent codes, boundary notes and a residual code.
Why write boundary notes before any data exist?
Because some framework domains are known to overlap, and agreeing in advance how to code borderline passages reduces disagreements between coders later.