Hi Jonathan, I thought that while you had a larger number of codes than you'd like, it was appropriate and never too hard to combine, if fitting. Your thoughts re: why there were so many is likely true and insightful of you to have thought about. I had a similar question about the underlying reason that groups wanted non-physicians following-up labs. Whether they feel this is part of their role in patient care or not is a good question. You memoing is different from others in the class and I'm gathering appreciation for that. I thought your method of coding and memoing is helpful for me to gather a sort of structure to how I could discuss mine in the future. Thanks!
Thanks for sharing your codes-- super interesting to see what you actually used to code your data. Having analyzed a fraction of your transcripts, I could see some of the themes that your codes allude to, particularly provider responsibility.
I thought it was interesting that you created separate codes for "definition of subcritical results" and "no uniform system (/definition) of subclinical results", since they were so related, but I can see how the additional granularity of the second code would be useful in finding that idea. I hadn't thought of that, creating both sides of the variable, but had come across a similar situation, where someone would be discussing something related to a code, but essentially saying the opposite of the code's idea.
I also agree that collapsing some of the "responsibility" codes could be useful, and liked the way that last week's presenter did this, using a main idea, colon, sub-idea so that you could group them together (in nvivo). Not sure if the program you are using has similar functionality. In a way, it seems like all of the codes could represent different tangents that the groups went off on related to responsibility. If there was repetition across groups, could be useful to identify in this way. But if not, then perhaps trying to find some aspect that was less specific about responsibility (something like responsibility: relationships) that covers a lot of these ideas might help you see patterns across groups, as opposed to being able to name each idea that each group came up with.
Great work!
I like the way you've communicated how the codes have developed (or perhaps proliferated) over time. This is a classic moment in qualitative analysis -- when you realize that the "master" code you've developed needs to be broken down and then you find myself making a gazillion codes and ponder if it is time to roll things back up. In terms of process issues: the definitions you've provided in this short memo are pretty concise and it may be as you push yourself to more thoroughly define codes you'll discover which can be easily combined or which really aren't different after all. And then a substantive thought: you seem to have some codes which are pretty rich and analytic and others that are a bit more concrete and descriptive. It may be worth clustering those groups together (or seeing if other clusterings emerge). These types of codes do different things in a project. Often you need both types but it is also typically helpful to be clear about which is which.