Many elements of asthma care are used across multiple PCIT templates — including OneLTC Asthma, OneTemplate Prescriber, OneTemplate Non-Prescriber, and OneTemplate Acute.
This guide summarises the shared template components that may appear dynamically within these templates, and links you to full support articles for each one.
Shared template components are standardised clinical building blocks embedded across different templates. They support consistent coding, guideline adherence, and QOF/LES compliance. They:
Follow national and international guidance (NICE, BTS/SIGN, PCRS)
Trigger dynamically based on patient context
Ensure documentation supports income and quality targets
Used to record the onset, symptoms, treatment, and outcome of any flare-up.
🔗 Go to Exacerbation Support Article
Prompts to check how the patient is using their inhaler, assess adherence, and document coaching if needed.
🔗 Go to Inhaler Technique Support Article
Allows for the creation or update of a personalised asthma action plan. Includes peak flow zones, usage instructions, and safety-netting advice.
🔗 Go to AST007 Support Article
Helps clinicians review current maintenance therapy and decide whether medication should be adjusted based on symptom control.
🔗 Go to Therapy Titration Guide
Streamlined approach to capturing smoking history, advice, referrals, and exemption reasons. Adjusts dynamically by patient status.
🔗 Go to Smoking Status Support Article
These components are embedded into multiple templates:
Component | OneLTC | Prescriber |
| Acute | ||
Exacerbation Recording | ✅ | ✅ | ✅ | ✅ | ||
Inhaler Technique & Adherence | ✅ | ✅ | ✅ | ❌ | ||
Self-Management Plan (AST007) | ✅ | ✅ | ✅ | ❌ | ||
Step-Up / Step-Down Therapy | ✅ | ✅ | ❌ | ❌ | ||
Smoking Status Handling | ✅ | ✅ | ✅ | ✅ |
When completing an asthma review in any template:
Check for any visible shared template components
Use dynamic prompts to guide accurate coding
Refer to the linked shared support articles if unsure
For a full overview of how these components are used within each role-based template: