Thematic analysis

From Infogalactic: the planetary knowledge core
(Redirected from Thematic Analysis)
Jump to: navigation, search

Thematic analysis is the most common form of analysis in qualitative research.[1] It emphasizes pinpointing, examining, and recording patterns (or "themes") within data.[2] Themes are patterns across data sets that are important to the description of a phenomenon and are associated to a specific research question.[3] The themes become the categories for analysis.[4] Thematic analysis is performed through the process of coding in six phases to create established, meaningful patterns. These phases are: familiarization with data, generating initial codes, searching for themes among codes, reviewing themes, defining and naming themes, and producing the final report.[5]

What is thematic analysis?

Thematic analysis is used in qualitative research and focuses on examining themes within data.[3] This method emphasizes organization and rich description of the data set. Thematic analysis goes beyond simply counting phrases or words in a text and moves on to identifying implicit and explicit ideas within the data.[6] Coding is the primary process for developing themes within the raw data by recognizing important moments in the data and encoding it prior to interpretation.[7] The interpretation of these codes can include comparing theme frequencies, identifying theme co-occurrence, and graphically displaying relationships between different themes.[6] Most researchers consider thematic analysis to be a very useful method in capturing the intricacies of meaning within a data set.[1]

There is a wide range as to what a "data set" entails (see qualitative data). Texts can range from a single-word response to an open-ended question or as complex as a body of thousands of pages.[8] As a consequence, data analysis strategies will likely vary according to size. Most qualitative researchers analyze transcribed in-depth interviews that can be 2-hours in length, resulting in nearly 40 pages of transcribed data per respondent. Also, it should be taken into consideration that complexity in a study can vary according to different data types.

Thematic analysis takes the concept of supporting assertions with data from grounded theory. This work is designed to construct theories that are grounded in the data themselves.[9] This is reflective in thematic analysis because the process consists of reading transcripts, identifying possible themes, comparing and contrasting themes, and building theoretical models.[10]

Thematic analysis is also related to phenomenology in that it focuses on the human experience subjectively.[10] This approach emphasizes the participants' perceptions, feelings and experiences as the paramount object of study. Rooted in humanistic psychology, phenomenology notes giving voice to the "other" as a key component in qualitative research in general. This allows the respondents to discuss the topic in their own words, free of constraints from fixed-response questions found in quantitative studies.

Like most research methods, this process of data analysis can occur in two primary ways—inductively or deductively.[11] In an inductive approach, the themes identified are strongly linked to the data because assumptions are data-driven.[7] This means that the process of coding occurs without trying to fit the data into a pre-existing model or frame. It is important to note that throughout this inductive process, it is not possible for the researchers to free themselves from their theoretical epistemological responsibilities. Deductive approaches, on the other hand, are theory-driven.[12] This form of analysis tends to be less descriptive overall because analysis is limited to the preconceived frames. The result tends to focus on one or two specific aspects of the data that were determined prior to data analysis. The choice between these two approaches generally depends on the researchers' epistemologies (see epistemology).

What is a theme?

A theme represents a level of patterned response or meaning from the data that is related to the research questions at hand. Determining what can be considered a theme can be used with deciding prevalence. This does not necessarily mean the frequency at which a theme occurs, but in terms of space within each data item and across the data set. It is ideal that the theme will occur numerous times across the data set, but a higher frequency does not necessarily mean that the theme is more important to understanding the data. A researcher's judgement is the key tool in determining which themes are more crucial. A potential data analysis pitfall occurs when researchers use the research question to code instead of creating codes and fail to provide adequate examples from the data. Eventually, themes need to provide an accurate understanding of the "big picture".[13]

There are also different levels at which themes can be identified—semantic and latent.[14] A thematic analysis generally focuses wholly or mostly on one level. Semantic themes attempt to identify the explicit and surface meanings of the data. The researcher does not look beyond what the participant said or wrote. In this instance, the researcher wishes to give the reader a sense of the important themes. Thus, some depth and complexity is lost. However, a rich description of the entire data set is represented. Conversely, latent themes identify underlying ideas, patterns, and assumptions. This requires much interpretation of the data, so researchers might focus on one specific question or area of interest across the majority of the data set.

A theme is different from a code. Several texts recommend that researchers "code for themes".[15] This can be misleading because the theme is considered the outcome or result of coding, not that which is coded. The code is the label that is given to particular pieces of the data that contribute to a theme. For example, "SECURITY can be a code, but A FALSE SENSE OF SECURITY can be a theme."[15]

Methodological issues

Reflexivity journals

Given that qualitative work is inherently interpretive research, the biases, values, and judgments of the researchers need to be explicitly acknowledged so they are taken into account in data presentation.[16] This type of openness is considered to be positive in the qualitative community.[17] Researchers shape the work that they do and work as the instrument for collecting and analyzing data. In order to acknowledge the researcher as the tool of analysis, it is necessary for one to create and maintain a reflexivity journal.[18]

The reflexivity process can be described as the documenting close reflections of potential findings and implications of the research study. Reflexivity journals are often referred to as analytic memos or memo writing, which can be useful for reflecting on emergent patterns, themes and concepts.[19] Throughout the coding process researchers should have detailed records of the development of each of their codes and potential themes. In addition, changes made to themes and connections between themes are incorporated into the final report to assist the reader in understanding decisions that were made throughout the coding process.[20]

Once fieldwork and interviews are complete and researchers are beginning the data analysis stages, they should take notes from the transcription and interviews. Researchers can take notes by writing down any words that may be of use during data analysis in a journal or notebook. The logging of ideas for future analysis can aid in getting thoughts and reflections written down and may serve as a reference for potential coding ideas as one progresses from one stage to the next in the thematic analysis process. Items written in journal do not have to be accurate or final but instead should contain considerations for further analysis. Researchers must take into consideration that analytic memos will assist them in the future coding of potential overreaching themes.[21]

While working on reflexivity journal entries it is important to make certain that notes written in journals are different from the data. The use of italics, bolding words, and adding brackets will assist in showing distinctions between data and journaling. Researchers should write their reflexivity notes fully avoiding abbreviations. This will assist the researcher in the final stages of analysis and through the process of data complication and reduction.[22] Auerbach & Silverstein (2003) suggest keeping a log of concerns with the research, theoretical framework, central research questions, goals, and major issues to help focus on the coding process.[22] Analytic memos reveal information about the researchers thinking process pertaining to the codes and categories that have emerged throughout the analysis process.[23] One of the most critical outcomes of qualitative data analysis is to interpret how each individual components of the study relate to each other, in particular researchers should focus on observations of the population to gain an image of the bigger picture that may lead to universal observations.[24] Emerson, Fretz & Shaw (1995) recommend the following questions should be considered when coding fieldwork notes:

Coding practice

Question to consider as you code may include:[25]

  • What are people doing? What are they trying to accomplish?
  • How exactly do they do this? What specific means or strategies are used?
  • How do members talk about and understand what is going on?
  • What assumptions are they making?
  • What do I see going on here? What did I learn from note taking?
  • Why did I include them?

The questions above should be asked throughout all cycles of the coding process and the data analysis. It is also important that what jumps out while coding is written. Keep in mind that codes can emerge from data that is unexpected, so keeping a thick detailed reflexivity journal will assist researchers in identifying potential codes that were not initially pertinent to the study.[22]

Sample size considerations

There is little reliable guidance on what sample size is needed for a thematic analysis,[26][27][28] with suggestions ranging from 6 to 400+ depending on the type of data collection and size of the project.[29][30]

It is common not to specify the number needed at the outset, but for decisions to be made as the research proceeds.[31][32] One approach is to continue to include material (e.g. further interviews) until no further themes are found; that is, until saturation.[33] The number needed to reach saturation has been investigated empirically,[34][26][35] but such approaches do not readily allow a prospective estimation of the sample needed.[30][26] Fugard & Potts (2015) offered a prospective, quantitative tool to support thinking on sample size by analogy to quantitative sample size estimation methods.[30]

Phases of Thematic Analysis

Phase Process Result Reflexivity Journal Entries[5]
Phase 1 Read and re-read data in order to become familiar with what the data entails, paying specific attention to patterns that occur. Preliminary "start" codes and detailed notes. List start codes in journal, along with a description of what each code means and the source of the code.
Phase 2 Generate the initial codes by documenting where and how patterns occur. This happens through data reduction where the researcher collapses data into labels in order to create categories for more efficient analysis. Data complication is also completed here. This involves the researcher making inferences about what the codes mean. Comprehensive codes of how data answers research question. Provide detailed information as to how and why codes were combined, what questions the researcher is asking of the data, and how codes are related.
Phase 3 Combine codes into overarching themes that accurately depict the data. It is important in developing themes that the researcher describes exactly what the themes mean, even if the theme does not seem to "fit." The researcher should also describe what is missing from the analysis. List of candidate themes for further analysis. Reflexivity journals need to note how the codes were interpreted and combined to form themes.
Phase 4 In this stage, the researcher looks at how the themes support the data and the overarching theoretical perspective. If the analysis seems incomplete, the researcher needs to go back and find what is missing. Coherent recognition of how themes are patterned to tell an accurate story about the data. Notes need to include the process of understanding themes and how they fit together with the given codes. Answers to the research questions and data-driven questions need to be abundantly complex and well-supported by the data.
Phase 5 The researcher needs to define what each theme is, which aspects of data are being captured, and what is interesting about the themes. A comprehensive analysis of what the themes contribute to understanding the data. The researcher should describe each theme within a few sentences.
Phase 6 When the researchers write the report, they must decide which themes make meaningful contributions to understanding what is going on within the data. Researchers should also conduct "member checking." This is where the researchers go back to the sample at hand to see if their description is an accurate representation. A thick description of the results. Note why particular themes are more useful at making contributions and understanding what is going on within the data set. Describe the process of choosing the way in which the results would be reported.

[5]

Phase 1: Becoming Familiar with the Data

The initial phase in thematic analysis is for researchers to familiarize themselves with the data. Prior to reading the interview transcripts, researchers should create a "start list" of potential codes. These start codes should be included in a reflexivity journal with a description of representations of each code and where the code is established.[36] analyzing data in an active way will assist researchers in searching for meanings and patterns in the data set. At this stage, it is tempting to skip over the data; however, this will aid researchers in identifying possible themes and patterns. Reading and re-reading the material until the researcher is comfortable is crucial to the initial phase of analysis. While becoming familiar with the material, note-taking is a crucial part of this step in order begin developing potential codes.[5]

Transcription

After completing data collection, the researcher needs to begin transcribing the data into written form. For further information on this process, please refer to transcription. Transcription of the data is imperative to the dependability of analysis. Transcribed data can come from television programs, interviews (see interviewing), and speeches, among others.[37]

Criteria for transcription of data must be established before the transcription phase is initiated to ensure that dependability is high.[6] Inconsistencies in transcription can produce biases in data analysis that will be difficult to identify later in the analysis process. The protocol for transcription should explicitly state criteria of transcription. Inserting comments like "*voice lowered*" will signal a change in the speech. In this stage, it is especially important to draw upon non-verbal utterances and verbal discussions to lead to a richer understanding of the meaning of data.[38] A general guideline to follow when transcribing includes a ratio of 15 minutes of transcription for every 5 minutes of dialog.

After this stage, the researcher should feel familiar with the content of the data and should be able to identify overt patterns or repeating issues in one or more interviews. These patterns should be recorded in a reflexivity journal where they will be of use when coding and checking for accuracy. Following the completion of the transcription process the researcher's most important task is to begin to gain control over the data. At this point, it is important to mark data that addresses the research question. This is the beginning of the coding process.[39]

Phase 2: Generating Initial Codes

The second step in thematic analysis is generating an initial list of items from the data set that have a reoccurring pattern. This systematic way of organizing, and gaining meaningful parts of data as it relates to the research question is called coding. The coding process evolves through an inductive analysis and is not considered to be linear process, but a cyclical process in which codes emerge throughout the research process. This cyclical process involves going back and forth between phases of data analysis as needed until you are satisfied with the final themes.[40] Researchers conducting thematic analysis should attempt to go beyond surface meanings of the data to make sense of the data and tell an accurate story of what the data means.[13]

The coding process is rarely completed the first time. Each time, researchers should strive to refine codes by adding, subtracting, combining or splitting potential codes.[41] Start codes are produced through terminology used by participants during the interview and can be used as a reference point of their experiences during the interview. Dependability increases when the researcher uses concrete codes that are based on dialogue and are descriptive in nature.[6] These codes will facilitate the researcher's ability to locate pieces of data later in the process and identify why they included them. Initial coding sets the stage for detailed analysis later by allowing the researcher to reorganize the data according to the ideas that have been obtained throughout the process. Reflexivity journal entries for new codes serve as a reference point to the participant and their data section, reminding the researcher to understand why and where they will include these start codes in the final analysis.[6] Throughout the coding process, full and equal attention needs to be paid to each data item because it will help in the identification of unnoticed repeated patterns. Coding for as many themes as possible and coding individual aspects of the data may seem irrelevant but can potentially be crucial later in the analysis process.[42]

Coding also involves the process of data reduction and complication. Reduction of codes is initiated by assigning tags or labels to the data set based on the research question(s). In this stage, condensing large data sets into smaller units permits further analysis of the data by creating useful categories. In-vivo codes are also produced by applying references and terminology from the participants in their interviews. Coding aids in development, transformation and re-conceptualization of the data and helps to find more possibilities for analysis. Researchers should ask questions related to the data and generate theories from the data, extending past what has been previously reported in previous research.[43]

Data reduction

Coding can be thought of as a means of reduction of data or data simplification. Using simple but broad analytic codes it is possible to reduce the data to a more manageable feat. In this stage of data analysis the analyst must focus on the identification of a more simple way of organizing data. using data reductionism researchers should include a process of indexing the data texts which could include: field notes, interview transcripts, or other documents. Data at this stage are reduced to classes or categories in which the researcher is able to identify segments of the data that share a common category or code. [44] Siedel and Kelle (1995) suggest three ways to aid with the process of data reduction and coding: (a) noticing relevant phenomena, (b) collecting examples of the phenomena, and (c) analyzing phenomena to find similarities, differences, patterns and overlying structures. This aspect of data collection is important because during this stage researchers should be attaching codes to the data to allow the researcher to think about the data in different ways.[45] Coding can not be viewed as strictly data reduction, data complication can be used as a way to open up the data to examine further.[46] The below section addresses the process of data complication and its significance to data analysis in qualitative analysis.[46]

Data complication

The process of creating codes can be described as both data reduction and data complication. Data complication can be described as going beyond the data and asking questions about the data to generate frameworks and theories. The complication of data is used to expand on data to create new questions and interpretation of the data. Researchers should make certain that the coding process does not lose more information than is gained.[46] Tesch (1990) defines data complication as the process of reconceptualizing the data giving new contexts for the data segments. Data complication serves as a means of providing new contexts for the way data is viewed and analyzed.[47]

Coding is a process of breaking data up through analytical ways and in order to produce questions about the data, providing temporary answers about relationships within and among the data.[47] Decontextualizing and recontextualizing help to reduce and expand the data in new ways with new theories.[47]

Phase 3: Searching For Themes

Searching for themes and considering what works and what does not work within themes enables the researcher to begin the analysis of potential codes. In this phase, it is important to begin by examining how codes combine to form over-reaching themes in the data. At this point, researchers have a list of themes and begin to focus on broader patterns in the data, combining coded data with proposed themes. Researchers also begin considering how relationships are formed between codes and themes and between different levels of existing themes. It may be helpful to use visual models to sort codes into the potential themes.[48]

Themes differ from codes in that themes are phrases or sentences that identifies what the data means. They describe an outcome of coding for analytic reflection. Themes consist of ideas and descriptions within a culture that can be used to explain causal events, statements, and morals derived from the participants' stories. In subsequent phases, it is important to narrow down the potential themes to provide an overreaching theme. Thematic analysis allows for categories or themes to emerge from the data like the following: repeating ideas; indigenous terms, metaphors and analogies; shifts in topic; and similarities and differences of participants' linguistic expression. It is important at this point to address not only what is present in data, but also what is missing from the data.[49] conclusion of this phase should yield many candidate themes collected throughout the data process. It is crucial to avoid discarding themes even if they are initially insignificant as they may be important themes later in the analysis process.[48]

Phase 4: Reviewing Themes

This phase requires the researchers to search for data that supports or refutes the proposed theory. This allows for further expansion on and revision of themes as they develop. At this point, researchers should have a set of potential themes, as this phase is where the reworking of initial themes takes place. Some existing themes may collapse into each other, other themes may need to be condensed into smaller units.[42]

Specifically, this phase involves two levels of refining and reviewing themes. Connections between overlapping themes may serve as important sources of information and can alert researchers to the possibility of new patterns and issues in the data. Deviations from coded material can notify the researcher that a code may not actually exist. Both of this acknowledgements should be noted in the researcher's reflexivity journal, also including the absence of themes.[6] Codes serve as a way to relate data to a person's conception of that concept. At this point, the researcher should focus on interesting aspects of the codes and why they fit together.

Level 1

Reviewing coded data extracts allows researchers to identify if themes form coherent patterns. If this is the case, researchers should move onto Level 2. If themes do not form clear patterns, consideration of the potentially problematic themes should be considered in addition to determining if data does not fit into the theme.[42] If themes are problematic, it is important to rework the theme and during the process, identification of new themes may emerge.[42] For example, it is problematic when themes do not appear to work or a significant amount of overlap between themes exists. This can result in a weak or unconvincing analysis of the data. If this occurs, data may need to be recognized in order to create cohesive, mutually exclusive themes.[13]

Level 2

Considering the validity of individual themes and how they connect to the data set is crucial to completing this stage. It is imperative to assess whether the potential thematic map accurately reflects the meanings in the data set in order to provide an accurate representation of participants' experiences. Once again, at this stage it is important to read and re-read the data to determine if current themes relate back to the data set. To assist you in this process it is imperative to code any additional items within the themes may have been missed earlier in the initial coding stage. If the potential map works then the researcher should progress to the next phase of analysis. If the map does not work it is crucial to return to the data in order to continue to review and refine existing codes. Mismatches between data and analytic claims reduce the amount of support that can be provided by the data. This can be avoided if the researcher is certain that their interpretations of the data and analytic analysis correspond.[50] Researchers repeat this process until they are satisfied with the thematic map. By the end of this phase, researchers have an idea of what themes are and how they fit together so that they convey a story about the data set.[42]

Phase 5: Defining and naming themes

Defining and refining existing themes that will be presented in the final analysis assists the researcher in analyzing the data within each theme. At this phase, identification of the themes' essences relate to how each specific theme affects the entire picture of the data. Analysis at this stage is characterized by identifying which aspects of data are being captured, what is interesting about the themes, and why themes are interesting.

In order to identify whether current themes contain sub-themes and to discover further depth of themes, it is important to consider themes within the whole picture and also as autonomous themes. Researchers must then conduct and write a detailed analysis to identify the story of each theme and its significance.[42] By the end of this phase, researchers can (1) define what current themes consist of, and (2) explain each theme in a few sentences. It is important to note that researchers begin thinking about names for themes that will give the reader a full sense of the theme and its importance.[42] Failure to fully analyze the data occurs when researchers do not include the data extracts use the data to support their analysis beyond the content. Researchers conducting thematic analysis should attempt to go beyond surface meanings of the data to make sense of the data and tell an accurate story of what the data means.[13]

Phase 6: Producing the Report

After final themes have been reviewed, researchers begin the process of writing the final report. While writing the final report, researchers should decide on themes that make meaningful contributions to answering research questions which should be refined later as final themes. Researchers present the dialogue connected with each theme in support of increasing dependability through a thick description of the results.[6] The goal of this phase is to write the thematic analysis to convey the complicated story of the data in a manner that convinces the reader of the validity and merit of your analysis. A clear, concise, and straightforward logical account of the story across and with themes is important for readers to understand the final report. The write up of the report should contain enough evidence that themes within the data are relevant to the data set. Extracts should be included in the narrative to capture the full meaning of the points in analysis. The argument should be in support of the research question. The final step in producing the report is to include member checking as a means to establish credibility, researchers should consider taking final themes and supporting dialog to participants to elicit feedback.[6]

Advantages and disadvantages

Researchers conducting qualitative analysis should select the most appropriate method to the research question. The method of analysis should be driven by both theoretical assumptions and the research questions. Thematic analysis provides a flexible method of data analysis and allows for researchers with various methodological backgrounds to engage in this type of analysis.[51] Reliability with this method is a concern because of the wide variety of interpretations that arise from the themes, as well as applying themes to large amounts of text. Increasing reliability may occur if multiple researchers are coding simultaneously, which is possible with this form of analysis. To increase reliability with this method researchers should plan tor monitoring themes and codes tables throughout the process.[52] This method of analysis contains several advantages and disadvantages, it is up to the researchers to decide if this method of analysis best explains their results.

Advantages

  • Flexibility it allows researchers, in that multiple theories can be applied to this process across a variety of epistemologies.[51]
  • Well suited to large data sets.[53]
  • Allows researchers to expand range of study past individual experiences.[53]
  • Great for multiple researchers.
  • Interpretation of themes supported by data.[53]
  • Applicable to research questions that go beyond an individual's experience.
  • Allows for categories to emerge from data.[54]

Disadvantages

  • Reliability is a concern due to wide variety of interpretations from multiple researchers.[52]
  • Thematic analysis may miss nuanced data.[53]
  • Flexibility makes it difficult to concentrate on what aspect of the data to focus on.[51]
  • Discovery and verification of themes and codes mesh together.[55]
  • Limited interpretive power if analysis excludes theoretical framework.[51]
  • Difficult to maintain sense of continuity of data in individual accounts.[51]
  • Does not allow researchers to make claims about language usage.[56]

See also

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 5.2 5.3 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 6.2 6.3 6.4 6.5 6.6 6.7 Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 13.2 13.3 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. 22.0 22.1 22.2 Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. 26.0 26.1 26.2 Guest, G., Bunce, A., & Johnson, L. (2006). How many interviews are enough?: An experiment with data saturation and variability. Field Methods, 18, 59–82. doi:10.1177/1525822X05279903
  27. Emmel, N. (2013). Sampling and choosing cases in qualitative research: A realist approach. London: Sage.
  28. Onwuegbuzie, A. J., & Leech, N. L. (2007). A call for qualitative power analyses. Quality & Quantity, 41, 105–121. doi:10.1007/s11135-005-1098-1
  29. Braun, V., & Clarke, V. (2013). Successful qualitative research: A practical guide for beginners. London: Sage.
  30. 30.0 30.1 30.2 Lua error in package.lua at line 80: module 'strict' not found.
  31. Hammersley M (2015). Sampling and thematic analysis: A response to Fugard and Potts. International Journal of Social Research Methodology, published online. doi10.1080/13645579.2015.1005456
  32. Sandelowski, M. (1995). Sample size in qualitative research. Research in Nursing & Health, 18, 179–183
  33. Glaser, B. (1965). The constant comparative method of qualitative analysis. Social Problems, 12, 436–445
  34. Francis, J. J., Johnston, M., Robertson, C., Glidewell, L., Entwistle, V., Eccles, M. P., & Grimshaw, J. M. (2010). What is an adequate sample size? Operationalising data saturation for theory-based interview studies. Psychology and Health, 25, 1229–1245. doi:10.1080/08870440903194015
  35. Wright, A., Maloney, F. L., & Feblowitz, J. C. (2011). Clinician attitudes toward and use of electronic problem lists: a thematic analysis. BMC Medical Informatics and Decision Making, 11, 36. doi:10.1186/1472-6947-11-36
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. 42.0 42.1 42.2 42.3 42.4 42.5 42.6 Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. 46.0 46.1 46.2 Lua error in package.lua at line 80: module 'strict' not found.
  47. 47.0 47.1 47.2 Lua error in package.lua at line 80: module 'strict' not found.
  48. 48.0 48.1 Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. 51.0 51.1 51.2 51.3 51.4 Lua error in package.lua at line 80: module 'strict' not found.
  52. 52.0 52.1 Lua error in package.lua at line 80: module 'strict' not found.
  53. 53.0 53.1 53.2 53.3 Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.