Why the Menlyn team asked for a common CYP450 brief
The project came from an integrative care team in Menlyn, Pretoria that wanted a clearer way to talk about CYP450 enzymes across consulting rooms, case discussions and patient handovers. Their team worked with people asking about medicines, supplements and everyday health choices, but the language used by different practitioners was uneven. Some used technical terms, others used simplified wording, and there was uncertainty around what could be said confidently without drifting into guesswork.
They asked us to prepare a briefing that stayed within established science, kept the focus on enzyme pathways and drug-enzyme interactions, and gave their staff a shared reference point. The brief also needed to work for a mixed audience of clinicians, pharmacists and wellness practitioners, so we had to keep it precise without making it stiff. In plain terms, the goal was not to explain everything about liver metabolism, but to give the team a workable common language for routine conversations and case notes.
- Client type: integrative care team
- Town: Menlyn, Pretoria
- Purpose: common CYP450 language for team use
- Main focus: medicine response, interaction awareness and plain wording
What the brief had to cover, and what it could not
The team was clear about the boundaries from the start. They needed educational material only, not testing, treatment or personal medical guidance. They also wanted us to avoid strong claims about predicting outcomes, because CYP450 enzymes are only one part of a much wider clinical picture. That meant every section had to be framed carefully, with enough detail to be useful but not enough to overstate what enzyme knowledge can tell you on its own.
We also had to keep the language suitable for different levels of science background. Some readers wanted the exact enzyme names and common interaction patterns, while others wanted a brief explanation they could use when speaking to clients. The brief had to respect that medicines, health status, age, liver function and other factors all matter, and that patients should speak to their own doctor or pharmacist about their medicines. No dosing advice was included, and no diagnosis language was used.
- Educational only, no testing or treatment advice
- No personal medical advice or dosing guidance
- Clear mention that medicines should be discussed with the person's own doctor or pharmacist
- Suitable for clinical, pharmacy and wellness use
How we shaped the literature review and notes
We started with a structured literature scan of widely accepted CYP450 material, then organised the findings into a short reference pack. The aim was to separate core facts from areas where caution is needed. We focused on the main ideas a care team uses every day: enzyme families, how medicines can inhibit or induce certain pathways, why interactions can matter, and why the same medicine may behave differently from one person to another.
From there, we wrote a plain-language summary that the team could use in meetings and when reviewing notes. We also prepared a short interaction overview that described common situations in neutral, non-prescriptive language. A few sections were rewritten twice to make the wording simpler without losing accuracy, and the final pack was checked for consistency in terms like substrate, inhibitor and inducer. That kept the material readable for non-specialists while still useful for clinical staff.
- Literature scan and source sorting
- Plain-language summary for team use
- Interaction overview with careful wording
- Terminology checked for consistency across the pack
Delivery format and timeline in weeks
The work ran over three weeks. In week one we clarified the scope, audience and the exact questions the team wanted answered. In week two we prepared the literature review outline and drafted the first set of notes. In week three we refined the language, prepared a clean reference list and delivered the final version for internal use. The turnaround was steady rather than rushed, which helped keep the terminology consistent and gave the client time to review the tone.
The final handover included a literature review summary, educational brief, plain language version and a short set of meeting notes. We kept the file structure simple so the team could drop sections into their own internal training and case discussion material without extra editing. Where needed, we added short explanatory lines for terms that often cause confusion in mixed practice settings, especially when different team members use different wording for the same enzyme concept.
- Timeline: 3 weeks
- Week 1: scoping and topic list
- Week 2: drafting and source review
- Week 3: editing, reference list and delivery
What the Menlyn team received
The project delivered a practical set of materials that could support team training and day to day discussions. The brief did not try to replace a clinician's judgement, and it did not tell anyone how to manage a patient. Instead, it gave the team a shared vocabulary and a reliable way to explain why CYP450 pathways are relevant when medicines interact or when a person asks about supplements and other compounds that may affect those pathways.
We also included content that could be reused in internal education, which saved the team from rewriting the same explanation for each meeting. The material was written so it could be used with a little adjustment for different contexts, whether the audience was a pharmacist-led discussion, a clinician handover or a wellness practitioner learning the basics. There was enough technical detail for accuracy, but not so much that it became hard to use in practice.
- Common CYP450 language for team meetings
- Plain wording for mixed clinical audiences
- Reference list support for later use
- Reusable notes for education and case discussion
What we would do again for a similar care team
For a similar brief, we would again start with the questions the team actually needs answered rather than a broad theory overview. That keeps the writing grounded and avoids overloading the reader with details that will never be used. We would also keep the format modular, because a team often needs one version for internal discussion and another for short training sessions or note-writing. A single long document is usually less useful than a set of focused pieces.
We would keep the same careful approach to claims, especially around enzyme variation and medicine response. CYP450 science is important, but it should be explained as one part of a bigger clinical picture. That approach works well for South African teams as well, because many work across different settings and need wording that holds up in a busy consultation, not just in an academic paper. If the team needed updates later, we would build from the same structure and refresh the sources rather than starting over.
- Start with the team's real questions
- Keep the pack modular and easy to reuse
- Use careful language around medicine response
- Refresh sources before expanding the brief
Key facts
| Project type | Educational CYP450 briefing for an integrative care team |
|---|---|
| Town | Menlyn, Pretoria |
| Timeline | 3 weeks |
| Core outputs | Literature review, educational brief, plain-language summary, interaction overview |
| Audience | Clinicians, pharmacists and wellness practitioners |
| Compliance note | Educational only, no testing, treatment, dosing or diagnosis advice |
