Content Sources — Workshop Prep

Hi Greg,

Thanks for reaching out — really helpful to have these questions surfaced ahead of the new developers starting. Below is a summary of where things stand on each content source, plus a few additional suggestions. I've included a diagram for quick reference.

────────────────────────────────────
CONTENT SOURCES — STATUS SUMMARY
────────────────────────────────────

1. HEALTH NEWS
For the MVP, we won't have budget allocated for a paid health news feed. We can include a lightweight version using free/publicly available sources (e.g., HPRA alerts, EMA news feeds). A premium/paid feed could be added as a later enhancement once funding is confirmed.

Status: MVP (free sources) | Paid feed = later enhancement

2. RESEARCH PAPERS
Cathal and Cris would be best positioned to define which research papers are relevant and to assess whether a feed or curated URL list of new/relevant papers is viable. We'd need them to identify the source(s) and confirm whether an automated feed (RSS, API) is available. Only then can we build automation around it.

Status: Cathal & Cris to define sources & assess feed viability

3. LASA (Look-Alike Sound-Alike)
Cathal and Cris are currently working on defining LASA pairs and how to feed them into the app. The key discussion point for the workshop is the ingestion method — it needs to be suitable for automation with minimum human intervention. Ideally we'd align on a format (e.g., CSV upload or API endpoint) that can be maintained externally and pulled in automatically rather than manually entered.

Status: Pairs in progress | Ingestion method = workshop discussion

4. DRUG DATABASE
We currently use a free/open-source drug database. Cathal and Cris would define the ideal source; we'd then need pricing data for it. If it's too expensive, we'd need a lower-cost alternative. Ideally, this would be parameterised so an admin user can "set" or select the drug database and supply a URL/API credentials to access it — making the system flexible rather than hard-coded to one provider.

Status: Free DB for MVP | Ideal source & pricing = Cathal & Cris to define | Admin-configurable connection = dev work

5. ADDITIONAL CONTENT SOURCES TO CONSIDER
These weren't in your list but would add significant value to AI-generated scenarios:
  • Clinical Guidelines & Formularies (e.g., BNF, NICE, local formularies) — evidence-based clinical content
  • Regulatory Updates (PSI, HPRA, EMA) — critical for compliance scenarios
  • Drug Interaction Checking Service — for interaction-based scenario generation
  • Medicine Shortages / Recall Alerts — time-sensitive and clinically relevant
  • Patient Information Leaflets (PILs) — for counselling scenario content
  • Vaccination / Immunization Schedules — for vaccination training modules
  • Controlled Drug Regulations — for CD register and legal scenarios

────────────────────────────────────
WORKSHOP & USER TRIALS
────────────────────────────────────

Happy to attend the workshop on Tuesday July 28, 2pm–4pm, face-to-face at Learnovate. I'll also bring some initial thoughts on the 2027 User Trials milestones so we can review them together and start mapping out development dependencies.

If there's anything specific you'd like me to prepare beforehand, just let me know.

Thanks,
[Your name]