Part 2: How Quality Improvement Shapes the Modules
Q: In Part 1, we talked about member feedback as an important part of quality improvement. What are some of the other quality improvement projects happening behind the scenes?
One project involves the patient handouts that we produce with some of our modules.
The handouts are patient-oriented, so we take information from a module and turn it into something that a member could upload to their EMR and print out for a patient. For example, we produced a handout for our osteoporosis module, so if someone diagnoses osteoporosis in clinic, they can give the patient something that provides useful information about the condition.
Part of the development process is deciding whether a handout would be helpful and whether something appropriate already exists. There are a lot of good patient resources available, and if, for example, the Canadian Diabetes Association already has a good handout on something, we would provide a link to it instead of creating something new.
We have guidelines around how we produce handouts, and there is naturally variation from one handout to the next. Periodically, we go back and look at the handouts that have been published and audit things like readability, word count, and the types of infographics being used. Then we summarize what we find and feed that back to the team. The point is to look at what we’re producing and ask how we can keep making it better.
Q: Another significant quality improvement project you mentioned is around equity, diversity, inclusion, and accessibility. What does that involve?
There are various aspects to this project and one stream of activity involves making sure that we are not using oppressive language in modules, and that we are writing in as inclusive a way as possible. Our copy editor does a sensitivity read as part of the module development process, and if issues are identified, those get fed back to us.
There are also times when we must think carefully about how research itself is presented. The literature may group people in certain ways, and we are bound to report the evidence that way, but we also can provide additional context.
For example, a study might identify being Indigenous as a risk factor for a particular health outcome. But is indigeneity itself really the risk factor? Or is that confounded by things like access to housing, access to health care, and other systemic factors? Those are the kinds of questions we think about when we present information in a module.
Q: What happens to the information members submit through the Practice Reflection Tools?
We look at those and create a summary of what members said they wanted to change, what they were able to change, and what barriers they encountered.
One of the main ways we’ve used those summaries is when we update a topic. If we’re developing a module on a topic we’ve done before, such as osteoporosis, we can look back to the Practice Reflection Tool summaries from the previous osteoporosis module. What did members want to change? What were they able to change? Where did they run into difficulty? Then we can look at whether there is newer evidence or practical information that might help members overcome some of those barriers and we can make that part of the new module.
We also use Practice Reflection Tool summaries to develop our review modules. Every year or two, we’ll look across several related modules and identify some of the common things members found difficult to change. We then build cases that bring together information from those modules and revisit the barriers in a practical way.
We also use the Practice Reflection Tool summaries for our Top 10 presentation at Family Medicine Forum and to produce newsletter articles. There have also been situations where outside organizations have been interested in whether members used a particular tool that we referenced in a module.
Essentially, we are not just producing a module and considering the job finished. We also want to understand what happens after members complete a module, what they found useful, what they changed, where they had difficulty, and then feed that back into what we do next.

Read “Part 1: The Role of Member Feedback in Module Development”