Bronchitis

Podcast 2 — In conversation

Speaker A: I have been off work for nearly two weeks. The doctor confirmed it was bronchitis rather than just a chest cold.

Speaker B: How did they distinguish between the two? I always assume a cough is just a cough.

Speaker A: The key difference is the cough itself. With bronchitis the cough is productive — you are bringing up mucus, it is deep and persistent, and it lingers for weeks rather than days. A simple chest cold tends to be shorter and drier.

Speaker B: And the treatment is different too, I suppose.

Speaker A: Interestingly, for acute bronchitis the treatment is largely the same: rest, fluids, and time. Antibiotics are almost never prescribed because the cause is usually viral, not bacterial. People sometimes expect a prescription and feel shortchanged.

Speaker B: That is worth knowing. I have heard people say they have chronic bronchitis — is that just a more severe version of the same thing?

Speaker A: No, and this is where people often go wrong. Chronic bronchitis is a distinct, long-term condition — classified as part of COPD. It means a persistent productive cough for at least three months a year, two years running. It is not just a bad recurring infection; it reflects structural changes in the airways.

Speaker B: So using chronic bronchitis loosely to mean I keep getting bronchitis every winter is inaccurate.

Speaker A: Precisely. Recurrent bronchitis is the better phrase for that. Chronic bronchitis carries a specific clinical definition that implies lasting airway damage, usually from smoking or prolonged exposure to pollutants.

Speaker B: What about the related word bronchial? I see that used fairly often.

Speaker A: Bronchial is the adjective form — it means relating to the bronchi. A bronchial infection, bronchial tubes, bronchial asthma. It is a useful companion word when you need to specify the airways without necessarily implying inflammation.

Speaker B: And bronchitis versus pneumonia — I always conflate those.

Speaker A: Different locations. Bronchitis is inflammation of the airways themselves — the tubes. Pneumonia is an infection of the lung tissue — the air sacs. Pneumonia is generally more serious and much more likely to require antibiotics or hospitalisation. The distinction matters clinically.

Speaker B: So bronchitis stays in the pipes and pneumonia goes deeper into the lungs themselves.

Speaker A: That is the clearest way to remember it, yes. Bronchitis — the airways. Pneumonia — the lung tissue.

Podcast 3 — Prompt engineering

Speaker B: Today we are working with bronchitis in development prompts. It is a precise medical term that immediately contextualises any application in respiratory healthcare — patient tracking, clinical records, symptom analysis, COPD management. Generic health terms produce generic systems. Bronchitis signals the specific domain and pulls in the right clinical details automatically. Let us work through the applications. First, a patient record system:

Speaker B: Build a patient management web application for a respiratory clinic. Each patient record should include a diagnosis field supporting both acute bronchitis and chronic bronchitis as selectable categories, a symptom log tracking cough frequency, mucus colour, and breathlessness score on a scale of one to ten, a treatment timeline recording prescribed medications, GP referral dates, and review appointments, and a flag that escalates any chronic bronchitis case to COPD screening review after two consecutive annual diagnoses. Use a Node.js API and PostgreSQL.

Speaker A: The automatic escalation flag after two consecutive annual diagnoses directly encodes the clinical definition of chronic bronchitis into the application logic. That kind of domain knowledge makes the system actively useful rather than just a record store.

Speaker B: Clinical logic in the database, not just in the UI. Now a database schema:

Speaker B: Design a PostgreSQL schema for a respiratory health monitoring system. Include a patients table, a diagnoses table with a bronchitis_type enum of acute and chronic, onset_date, resolved_date nullable, and a severity integer from one to five. Create a symptom_logs table linked to each diagnosis recording daily cough_score, sputum_colour as a text field, breathlessness_score, and log_date. Add a medications table and a patient_medications junction table tracking dosage and duration. Index diagnoses on bronchitis_type and onset_date for dashboard query performance.

Speaker A: Separating the two bronchitis types in a dedicated enum rather than a free text field means all reporting and filtering is consistent from day one. Free text diagnosis fields are a common mistake in health application schemas.

Speaker B: Enums enforce clinical vocabulary. Now a dashboard:

Speaker B: Create a responsive clinical dashboard in vanilla JavaScript and CSS Grid for a GP surgery respiratory lead. The dashboard should display active bronchitis cases segmented by type — acute versus chronic — with trend lines for new acute diagnoses over the past twelve weeks, a heat map of symptom severity scores across the active chronic bronchitis cohort, an alert panel listing patients whose chronic bronchitis has met the two-year clinical threshold for COPD referral, and a medication compliance tracker. Use a clean clinical white and deep teal colour scheme.

Speaker A: The COPD referral alert panel transforms the dashboard from a passive display into a clinical decision support tool. That is the difference between reporting what happened and prompting what should happen next.

Speaker B: Decision support is the most valuable feature a clinical dashboard can have. Now a mobile symptom tracker for patients:

Speaker B: Generate a React Native symptom tracking application for patients managing chronic bronchitis. The app should present a daily check-in screen where patients rate their cough severity, log sputum colour using a colour picker calibrated to clinical sputum colour charts, record breathlessness using the MRC Dyspnoea Scale, and add free-text notes. The app should send a weekly summary report to the patient's linked GP portal, alert the patient if three consecutive days show worsening scores, and allow the patient to request an urgent appointment directly from within the app. Use Supabase for backend.

Speaker A: Using the MRC Dyspnoea Scale rather than an arbitrary number means the data collected aligns directly with what clinicians already use for assessment. That interoperability is crucial for the GP portal integration to be useful.

Speaker B: Matching clinical measurement standards is what makes patient-generated data clinically actionable. Now a public health analytics prompt:

Speaker B: Build a public health analytics platform using Node.js and PostgreSQL that aggregates anonymised bronchitis diagnosis data from multiple GP surgeries across a health region. Track weekly acute bronchitis incidence rates by age band and postcode area, detect seasonal outbreak clusters using a rolling seven-day case rate threshold, generate automated reports comparing chronic bronchitis prevalence against air quality index data from the environment agency API, and alert the regional public health team when acute bronchitis cases exceed a configurable weekly threshold by more than twenty percent.

Speaker A: Correlating chronic bronchitis prevalence with air quality index data moves the platform into genuine epidemiological territory. That is the kind of insight that informs public health policy rather than just describing individual patients.

Speaker B: Population-level analysis is where medical vocabulary really shows its precision. And a full platform to close:

Speaker B: Build a full-stack respiratory health management platform using Next.js, TypeScript, and PostgreSQL. The platform covers patient-facing symptom tracking for both acute and chronic bronchitis, a clinician portal with cohort management and COPD escalation alerts, a pharmacy module tracking inhaler and antibiotic prescriptions per bronchitis type, integration with NHS FHIR-compliant patient records API for read-only demographic data, an analytics module surfacing geographic bronchitis incidence trends, and a role-based access system distinguishing patient, GP, respiratory nurse, and admin roles.

Speaker A: The FHIR integration for read-only demographic data is the detail that makes this a real NHS-compatible application rather than a standalone prototype. Interoperability standards are what turn a clinical tool into a deployable one.

Speaker B: In every prompt today, bronchitis provided immediate clinical precision. It signals the respiratory domain, distinguishes acute from chronic pathways, aligns the data model with clinical definitions, and connects the application to public health measurement standards. A generic term like respiratory condition produces vague systems. Bronchitis produces systems that match how clinicians actually think and work.