by NextPV Services, s.r.o.
Podcast that will take your drug safety to the #NextLevel. Pharmacovigilance is a complex science, but it should not be complicated. We at NextPV want to bring you insights and knowledge through our conversations. We will cover everything from big strategic topics to smaller operational ones and current news. Welcome and enjoy listening.
Language
🇺🇲
Publishing Since
2/10/2026
Pitch yourself as a guest, propose sponsorships, or reach out directly to the host.
July 21, 2026
<p>Every pharmacovigilance system runs on a safety database — the central engine where every ICSR is entered, processed, and reported. But choosing, validating, and maintaining that database is one of the most consequential infrastructure decisions a biotech will make, and one of the most common sources of inspection findings when it is done badly.</p><p>In Episode 6 of What's Next in PV, Tereza Korecka speaks with Jan Kolouch and Vojtech Kvita from NextPV Services about how to approach the safety database decision end to end:</p><ul><li>What a safety database actually does inside the PV system, and when a company can function without one</li><li>How vendor choice depends on ICSR volume, functionality, region, and budget — not just brand name</li><li>Build vs. buy vs. outsource: control, cost, and who really owns your data in each model</li><li>What GAMP 5 and EU Annex 11 validation actually requires: URS, IQ/OQ/PQ, and change control</li><li>Practical setup steps: dictionaries, workflows, SOPs, and EudraVigilance gateway testing</li><li>What triggers a database migration, and why it is one of the most error-prone PV projects</li><li>Why due diligence, not the vendor's brand, determines whether the system holds up at inspection</li></ul><p>This is a practical conversation for PV, QA, IT, and biotech leaders selecting, validating, or migrating a safety database.</p><p>Hosted by Tereza Korecka | Guests: Jan Kolouch and Vojtech Kvita, NextPV Services</p><p>(00:00) - Intro music and episode introduction(00:31) - Opening and guest greetings(00:41) - Today's topic: safety databases(00:58) - What a safety database does inside the PV system(02:16) - Do you actually need one? Volume, PSURs, and reporting obligations(03:26) - Overview question: which vendors do companies choose from(03:51) - Main selection factors: volume, functionality, region, and budget(07:45) - Large vs. small organizations: enhanced functionality vs. practicality(11:26) - Build, buy, or outsource: framing the decision(11:59) - The build option, database ownership, and vendor-managed models(16:46) - Why building your own database is rare in practice today(18:21) - GAMP validation: what the process actually looks like(19:00) - URS, FS, IQ/OQ/PQ, GAMP 5, EU Annex 11, and the EU AI Act(23:21) - Beyond validation: what companies trip up on at setup(23:52) - Database setup: dictionaries, workflows, SOPs, and EudraVigilance gateway testing(29:22) - Changing databases: what actually triggers a migration(29:46) - Migration scenarios: E2B exports, script migration, and data enrichment(34:27) - When migrations slip: deviations, mitigation, and inspections(36:54) - Closing advice for biotechs facing a database decision(37:34) - Operating model, timeline buffers, and post-launch monitoring(42:18) - Due diligence as the thread through the whole process(45:23) - Migration usually happens alongside the day job(46:20) - Why it helps to have an internal database point person(47:33) - Closing remarks</p><p><br></p><p>Keywords:<br>pharmacovigilance, safety database, Oracle Argus, ArisGlobal LSMV, Veeva Vault Safety, GAMP 5, EU Annex 11, database validation, database migration, EudraVigilance gateway, ICSR, PV system, biotech pharmacovigilance</p><p></p>
May 26, 2026
<p>Choosing a PV tool is no longer just a safety database decision. Computerized systems now sit across pharmacovigilance operations: safety databases, PSMF tools, QMS platforms, reporting layers, integrations, dashboards, automation, and AI-enabled capabilities.</p><p>In Episode 5 of What's Next in PV, Tereza Korecka speaks with Jan Kolouch and Vojtech Kvita from NextPV Services about how PV teams should approach computerized systems as strategic infrastructure, not just software.</p><p>The conversation covers:</p><ul><li>What makes a tool relevant for pharmacovigilance and GxP work</li><li>Why companies should start with process, data flow, and intended use before vendor demos</li><li>Strategic routes: current vendor modules, new vendors, integrations, APIs, and internal builds</li><li>How scorecards, sandbox testing, and business requirements help decision makers</li><li>Why cost should be assessed beyond licence price</li><li>What validation means for configurable and cloud-based tools</li><li>Where AI fits, and why automation and audit trails still matter</li><li>How the approach differs for small biotechs and large pharma companies</li></ul><p>This is a practical episode for PV, QA, IT, regulatory, and biotech leaders reviewing their technology stack or preparing for a regulated tool selection project.</p><p>Hosted by Tereza Korecka | Guests: Jan Kolouch and Vojtech Kvita, NextPV Services</p><p>Keywords:<br>pharmacovigilance, computerized systems, computerized tools, PV systems, GxP validation, safety database, PV technology, AI in pharmacovigilance, automation, audit trail, data integrity, PSMF, QMS, vendor selection, biotech PV</p><p><br></p><p>(00:53) - Opening and guest greetings(01:01) - Episode topic: computerized tools in pharmacovigilance(01:20) - Computerized systems are broader than safety databases(02:55) - How to decide whether a tool is used for PV activities(04:07) - Why PV system decisions are becoming more complex(04:29) - Digitalization, AI momentum, and cross-functional decision-making(07:17) - Main strategic options for better PV tools(07:41) - Current vendor modules, new vendors, integrations, APIs, and internal builds(11:04) - Why teams should invest time in tool selection and interoperability(12:30) - What to assess before looking at vendor options(13:16) - Demos, system inventory, data flow, and validation considerations(16:03) - Scorecards, business requirements, and system requirements(17:02) - How to compare functionality without ignoring cost(17:39) - Shortlisting vendors, sandbox testing, and pricing models(20:06) - Building a viable business case and assessing benefit-risk(21:38) - What validation means for GxP tools(22:18) - Configuration, implementation, cloud setup, and validation packages(26:04) - Why validation can range from simple testing to a full project(27:11) - AI trends without turning the episode into an AI validation deep dive(28:05) - Enterprise LLMs, local models, system-of-record data, and human oversight(33:06) - Automation before AI and why audit trails matter(35:32) - Practical decision process: from use case to governance(36:13) - Define use case, regulatory impact, data access, cost, validation, and ownership(39:54) - Small biotech vs large pharma: what changes and what stays the same(40:21) - Lean compliant stacks, fragmentation, vendor lock-in, and governance(43:53) - Final takeaway question: choosing PV tools in May 2026(44:37) - Computerized systems as strategic PV infrastructure(47:07) - Do not be afraid to move toward computerized systems and supervised AI(48:44) - Closing remarks</p>
April 7, 2026
<p>Medical writing in pharmacovigilance is not just writing. It is the point where safety data, process outputs, cross-functional input, and benefit-risk judgement come together into a document regulators can evaluate.</p><p>In Episode 4 of What's Next in PV, Tereza Korecka speaks with Katarina Cechlovska and Hana Sourkova from NextPV Services about what strong PV medical writing actually requires, including:</p><ul><li>What medical writing covers in pharmacovigilance, from case narratives to aggregate reports and risk management documents</li><li>Why aggregate reports depend on signal detection, risk minimisation, case collection, exposure data, regulatory input, and source-data quality</li><li>Where DSURs, RMPs, PSURs/PBRERs, and addenda to clinical overviews appear across the product lifecycle</li><li>Why teams underestimate timelines, review cycles, and cross-functional coordination</li><li>Common quality issues such as inconsistent data, outdated content, and late submissions</li><li>What works, and what breaks, when medical writing is outsourced</li><li>How a small biotech should start planning its first major PV document</li></ul><p>This is a practical conversation for PV teams, regulatory teams, and biotech leaders who want documents that are not only submission-ready, but defensible.</p><p>Hosted by Tereza Korecka | Guests: Katarina Cechlovska and Hana Sourkova, NextPV Services</p><p><br></p><p>(00:12) - Recorded intro and episode overview(00:53) - Opening and guest introductions(00:58) - Defining medical writing in pharmacovigilance(01:10) - Safety documents across the product lifecycle(01:59) - Fixed structures, regulatory expectations, and strict timelines(02:40) - Why medical writing is more than "just writing"(02:56) - Aggregate reports, data interpretation, and the benefit-risk story(04:52) - Weak writing as a symptom of weak upstream process(05:44) - When these documents appear across the product lifecycle(06:00) - DSURs, RMPs, PSURs/PBRERs, and ACOs(07:12) - Documents as the evolving picture of benefit-risk over time(07:34) - Why teams underestimate the effort and timelines(07:58) - Medical writing timelines, review cycles, and data readiness(09:32) - Last-minute data chasing, review chaos, and lower document quality(10:59) - "Garbage in, garbage out" applied to medical writing(11:17) - Inputs and contributors needed for aggregate reports(13:01) - Authorship, reviewers, contributors, and deadlines(13:43) - Quality and compliance failure question(13:56) - Common quality failures: inconsistent data, outdated content, late submission(14:57) - Process failures behind aggregate report issues(16:06) - Outsourcing medical writing when internal capacity is limited(16:31) - Outsourcing while retaining MAH accountability(18:49) - Why outsourcing works best as a connected partnership(19:52) - Small biotech scenario: preparing a first major PV document(20:24) - Start with planning, document calendar, owner, and source-data checklist(21:12) - Reusing existing materials and identifying high-risk gaps(23:05) - Final advice question: reducing submission stress and findings(23:29) - Final advice: start long before the deadline(24:29) - Good documents reflect data quality and clear ownership(24:53) - Closing remarks</p><p><br></p><p>Keywords:pharmacovigilance, medical writing, PV medical writing, DSUR, PSUR, PBRER, RMP, benefit-risk evaluation, aggregate reports, drug safety, regulatory documents, biotech PV, submission readiness</p><p></p>
Have a different question and can't find the answer you're looking for? Reach out to our support team by sending us an email and we'll get back to you as soon as we can.
Podcast that will take your drug safety to the #NextLevel.
Pharmacovigilance is a complex science, but it should not be complicated. We at NextPV want to bring you insights and knowledge through our conversations. We will cover everything from big strategic topics to smaller operational ones and current news. Welcome and enjoy listening.
This podcast updates daily.
This podcast is available on 4 platforms including Apple Podcasts, Spotify, and more. You can also use the RSS feed directly.
Yes, this podcast regularly features guests.
Pod Engine is not affiliated with, endorsed by, or officially connected with any of the podcasts displayed on this platform. We operate independently as a podcast discovery and analytics service.
All podcast artwork, thumbnails, and content displayed on this page are the property of their respective owners and are protected by applicable copyright laws. This includes, but is not limited to, podcast cover art, episode artwork, show descriptions, episode titles, transcripts, audio snippets, and any other content originating from the podcast creators or their licensors.
We display this content under fair use principles and/or implied license for the purpose of podcast discovery, information, and commentary. We make no claim of ownership over any podcast content, artwork, or related materials shown on this platform. All trademarks, service marks, and trade names are the property of their respective owners.
While we strive to ensure all content usage is properly authorized, if you are a rights holder and believe your content is being used inappropriately or without proper authorization, please contact us immediately at hey@podengine.ai for prompt review and appropriate action, which may include content removal or proper attribution.
By accessing and using this platform, you acknowledge and agree to respect all applicable copyright laws and intellectual property rights of content owners. Any unauthorized reproduction, distribution, or commercial use of the content displayed on this platform is strictly prohibited.