POPULARITY
Categories
231 episodes with Documentation
207 episodes with Documentation
89 episodes with Documentation
84 episodes with Documentation
36 episodes with Documentation
98 episodes with Documentation
28 episodes with Documentation
30 episodes with Documentation
29 episodes with Documentation
21 episodes with Documentation
18 episodes with Documentation
14 episodes with Documentation
15 episodes with Documentation
17 episodes with Documentation
43 episodes with Documentation
16 episodes with Documentation
14 episodes with Documentation
13 episodes with Documentation
11 episodes with Documentation
11 episodes with Documentation
18 episodes with Documentation
10 episodes with Documentation
11 episodes with Documentation
12 episodes with Documentation
10 episodes with Documentation
13 episodes with Documentation
10 episodes with Documentation
15 episodes with Documentation
11 episodes with Documentation
10 episodes with Documentation
12 episodes with Documentation
6 episodes with Documentation
8 episodes with Documentation
8 episodes with Documentation
10 episodes with Documentation
8 episodes with Documentation
7 episodes with Documentation
17 episodes with Documentation
18 episodes with Documentation
11 episodes with Documentation
8 episodes with Documentation
8 episodes with Documentation
7 episodes with Documentation
14 episodes with Documentation
8 episodes with Documentation
6 episodes with Documentation
9 episodes with Documentation
10 episodes with Documentation
6 episodes with Documentation
8 episodes with Documentation
6 episodes with Documentation
5 episodes with Documentation
5 episodes with Documentation
7 episodes with Documentation
7 episodes with Documentation
5 episodes with Documentation
5 episodes with Documentation
5 episodes with Documentation
8 episodes with Documentation
6 episodes with Documentation
4 episodes with Documentation
7 episodes with Documentation
4 episodes with Documentation
6 episodes with Documentation
10 episodes with Documentation
5 episodes with Documentation
10 episodes with Documentation
8 episodes with Documentation
6 episodes with Documentation
5 episodes with Documentation
7 episodes with Documentation
5 episodes with Documentation
5 episodes with Documentation
3 episodes with Documentation
3 episodes with Documentation
11 episodes with Documentation
4 episodes with Documentation
3 episodes with Documentation
6 episodes with Documentation
6 episodes with Documentation
5 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
12 episodes with Documentation
4 episodes with Documentation
7 episodes with Documentation
4 episodes with Documentation
6 episodes with Documentation
3 episodes with Documentation
3 episodes with Documentation
5 episodes with Documentation
5 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
10 episodes with Documentation
3 episodes with Documentation
5 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
7 episodes with Documentation
3 episodes with Documentation
5 episodes with Documentation
3 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
4 episodes with Documentation
3 episodes with Documentation
2 episodes with Documentation
4 episodes with Documentation
3 episodes with Documentation
3 episodes with Documentation
2 episodes with Documentation
3 episodes with Documentation
3 episodes with Documentation
3 episodes with Documentation
9 episodes with Documentation
4 episodes with Documentation
8 episodes with Documentation
4 episodes with Documentation
2 episodes with Documentation
4 episodes with Documentation
7 episodes with Documentation
6 episodes with Documentation
7 episodes with Documentation
3 episodes with Documentation
4 episodes with Documentation
5 episodes with Documentation
3 episodes with Documentation
3 episodes with Documentation
Growing a business requires more than the right technology. It requires business systems that make important work repeatable, consistent, and easier to scale.In this episode of MOJO: The Meaning of Life and Business, Jennifer R. Glass speaks with Adi Klevit, founder of Business Success Consulting Group and host of the Systems Simplified podcast, about how processes and standard operating procedures, or SOPs, help businesses operate more effectively.Jennifer and Adi explore the difference between a business process, an SOP, and the technology used to support them. They discuss why buying a new software platform does not automatically solve an underlying process problem and why businesses need to understand what they are trying to accomplish before adding another tool to their technology stack.The conversation also looks at one of the biggest risks facing growing businesses: important knowledge that exists only in one person's head. From employee onboarding and customer service to sales, payroll, marketing, and inventory, documenting repeatable processes can create greater consistency and make delegation easier.You'll also hear practical advice about deciding which processes to document first, keeping systems updated as the business changes, improving adoption across a team, and making sure industry terminology and acronyms are clearly understood.Whether you're starting a business or managing a fast-growing company, this episode will help you think differently about the systems behind your business and what needs to be in place before you can truly scale.Key takeaways:A system is bigger than software. Technology can execute or automate part of a process, but the underlying business process needs to be understood first.A process and an SOP are related but different. The process maps how work moves from point A to point B. The SOP explains how the work is executed step by step.Document what is repeatable. If something happens regularly, it may be a candidate for systematization.Protect institutional knowledge. A business becomes vulnerable when essential knowledge resides only in one employee's head.Systems support delegation. Documented processes make it easier to train people and move work away from the owner.Systems must stay alive. Documentation should be reviewed and improved rather than created once and forgotten.Technology needs a purpose. Before adding another platform, determine what role it plays in the larger business process. About my guest: Adi Klevit is the leader and visionary behind Business Success Consulting Group. With thirty years of experience as a trained Industrial Engineer and management consultant, she brings a unique understanding of the challenges businesses face today. Adi utilizes her practical know-how to help organizations of any size dramatically improve their efficiency and performance. By leveraging her ability to understand both business processes and people, she helps business owners bring order to their lives and achieve their goals. She is also the host of the Systems Simplified podcast, where she interviews successful entrepreneurs about the power of systematizing a business.Connect with Adi:Website | LinkedInSystems Simplified Podcast
(Premier épisode) Au matin du mardi 11 mars 1980, le cadavre d'une jeune fille blonde est retrouvé le long de la RN20, une route nationale qui relie la capitale à la frontière franco-espagnole. Dans les mois et les années qui suivent, les corps de trois autres jeunes femmes blondes sont retrouvés à proximité de la voie. Elles ont toutes été étranglées et entièrement dénudées.Pour la brigade criminelle de Versailles, il est clair qu'un seul et même tueur est derrière tous ces meurtres, mais les enquêteurs peinent à trouver des pistes fiables. En 2009, un test ADN réalisé sur un mouchoir retrouvé à côté d'une victime permet néanmoins d'identifier un suspect.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette affaire avec Damien Delseny, le chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau, Victor Beaunoir et Damien Delseny - Production : Barbara Gouy, Clara Garnier-Amouroux, Thibault Lambert et Marin Guillon Verne - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network. Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
(Deuxième et dernier épisode) Au matin du mardi 11 mars 1980, le cadavre d'une jeune fille blonde est retrouvé le long de la RN20, une route nationale qui relie la capitale à la frontière franco-espagnole. Dans les mois et les années qui suivent, les corps de trois autres jeunes femmes blondes sont retrouvés à proximité de la voie. Elles ont toutes été étranglées et entièrement dénudées.Pour la brigade criminelle de Versailles, il est clair qu'un seul et même tueur est derrière tous ces meurtres, mais les enquêteurs peinent à trouver des pistes fiables. En 2009, un test ADN réalisé sur un mouchoir retrouvé à côté d'une victime permet néanmoins d'identifier un suspect.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette affaire avec Damien Delseny, le chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau, Victor Beaunoir et Damien Delseny - Production : Barbara Gouy, Clara Garnier-Amouroux, Thibault Lambert et Marin Guillon Verne - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network. Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
⚠️ What Happens If Your Ex Stops Paying Court-Ordered Spousal Support? | Los Angeles Divorce
Marie and Chris hop on CodePen Radio for a little chat on how we're still happily using WordPress for a variety of things here on CodePen. We've got it hosted on a subdomain and on a different (WordPress-specific) hosting plan than our main monorepo, so it has its own deployment process and such. We use WordPress for our blog, where this very podcast is published, because WordPress handles RSS well, and a podcast is an RSS feed with an audio file. We also, quite importantly, use it for our docs. For 2.0, we re-wrote the docs and used a Custom Post Type in WordPress to organize them, which feels much more organized. Time Jumps Links
Today we are talking about Aaron Winborn, The award named after him, and what winning is like with guests George DeMet & April Sides. We'll also cover Summit as our module of the week. For show notes visit: https://www.talkingDrupal.com/561 Topics Who Was Aaron Winborn Award Origin Story How Winners Are Chosen Why Community Matters What Winners Share April Learns She Won Handcrafted Award Stories On Stage Emotions After Winning Reflections How To Contribute Nominations And Makers Surprise Award Ideas Wrap Up And Contacts Resources TD Cafe #018 - Drupal Site Templates Aaron Winborn Award Winner AskWookiee Guests April Sides - weekbeforenext George DeMet - palantir.net gdemet Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Ashraf Abed - drupito.com ashrafabed MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to create a website purpose-built for an event like a Drupal camp, that collects, moderates, and schedules user-submitted sessions, and do all of that within the Drupal CMS installer? There's a site template for that. Module name/project name: Summit Site Template Brief history How old: created in June 2026 by yours truly Versions available: 1.0.0, released yesterday Maintainership Actively maintained Security and test coverage Documentation some in the repo we'll talk about later Number of open issues: no open issues, though there are a couple of open issues on the Event Platform Starter, from which Summit was created Module features and usage We've talked before on this podcast about the Event Platform that grew out of an initiative from the Event Organizers Working Group. The goal is to remove friction for anyone organizing a Drupal camp or similar event in creating a website that sets them up for success The Event Platform was created before Recipes were a thing in the Drupal-verse, even though it was initially built in ways that were similar to recipes A couple of years ago, I started working on the Event Platform Starter recipe to help spin up a fully-built event website in a single step. That ran into some technical complexities, so it ended up being being a time-saver, but still required a number of manual steps As the newer concept of site templates took shape, I could see that the Event Platform ecosystem had the necessary elements to become a site template, in particular a theme and a battle-tested a content architecture I ended up needing to decouple the configuration and the functional code that had previously been in Event Platform. The configuration would reside solely in the site template, so the functional code was moved to a new project, Event Platform Helper Along the way, there have been a number of significant changes: Canvas integration for a fully customizable homepage, also a set of Canvas components to allow building new, custom layouts, a new, custom cache context, improved management of event information, and more Now, you set everything up with a single click in the Drupal CMS installer. There's an open issue to get it into the Drupal CMS installer by default, but today it's just a composer require away The repo does also include an AGENTS.md and CONTENT-STRUCTURE.md files, to help human or AI agents who want to work a site built using Summit to understand the initial state of the content architecture it provides, as well as the different logical components and how to troubleshoot them, individually or in combination
What's up fraud fighters, and welcome back to Fraud Forward!Over the last few months, I've had more conversations about agentic payments than just about any other topic. At conferences, on webinars, and in discussions with some of the smartest people in payments, compliance, and fraud, one thing has become clear to me: I think we're asking the wrong question.Most people want to know whether AI will start moving money.The question I keep coming back to is this: How do fraud teams investigate transactions when software starts making decisions?In this solo episode, I pull together insights from recent conversations with Matt Vega, Mary Ann Miller, and Matt Janiga to explore what agentic commerce really means for fraud investigations, SAR reporting, and the future of financial crime investigations. We talk about why traditional fraud models have always assumed a human initiated the payment, why that assumption no longer holds, and what investigators will need to understand when AI agents begin making decisions on behalf of customers.The technology may be changing, but the principles of good fraud prevention are not. Documentation, audit trails, authority management, explainability, and strong transaction monitoring will become even more important as agentic payments move from theory to reality.What you'll hear in this episode:Why agentic payments are fundamentally different from traditional payment automation.How agentic commerce changes the way fraud teams investigate payment fraud.Why audit trails, attribution, and explainability will become essential during fraud investigations.How SAR reporting and AML investigations may evolve as AI becomes part of the payment decision process.Why regulators are focused on enabling innovation safely instead of slowing it down.The three questions every fraud investigator should begin asking today to prepare for the future.You should listen to this episode if you:Work in fraud prevention, AML compliance, investigations, or financial crime.File suspicious activity reports or conduct SAR reporting.Lead fraud operations, transaction monitoring, or payment investigations.Are evaluating how AI and agentic commerce will affect your institution.Want practical steps your team can begin implementing today instead of waiting for the rulebook to catch up.
Sales management often focuses on adding more process. Jesse Davis believes that's exactly what slows great sales teams down. In this episode of the B2B Sales Trends Podcast, Harry sits down with Jesse Davis, Head of Sales at Dandy, to explore why the best sales organizations don't scale through more approvals, more CRM updates, or more playbooks. They scale by removing unnecessary variability, documenting what actually works, and building systems that make exceptional performance repeatable. Jesse also explains why modern B2B sales requires a different approach to consultative selling and sales discovery. Buyers arrive informed, distracted, and skeptical. The sellers who stand out aren't the ones asking more questions. They're the ones who combine genuine curiosity with the ability to make complex ideas remarkably simple.
Dr. Beckett discusses advice for a collector flying to this weekend's West Coast Burbank card show who wants to buy an expensive card and is considering bringing $30,000 in cash. He weighs show buying versus auctions, explains why cash is often preferred at shows, and reviews alternatives like wires, credit cards (often with a 3% fee), checks (requiring strong trust/vouching), and digital payments with limits. Beckett emphasizes security and discretion, planning ahead with the bank, understanding cash-withdrawal documentation over $10,000, and being prepared for airport screening. He recommends documenting any big deal (seller identity, card/grade details, photos) to reduce risk, warns about brokered transactions and a high-profile Tom Brady deal that went wrong, and concludes that cash can be reasonable for $30,000 if handled carefully. 01:16 Payment Options Overview 02:24 Cash Logistics and Risks 03:47 Trust and Verification 05:43 Show Deal Mechanics 06:51 Wires Cards and Checks 08:47 Getting Cash and Flying 11:54 Documentation and Safety Tips 13:33 Broker Deal Gone Wrong 15:25 Best Plan for 30K
(Deuxième et dernier épisode) Durant l'automne 1977, un homme sème la terreur dans le Xème arrondissement de Paris. Plusieurs femmes sont violées et tuées par strangulation dans leur parking ou leur appartement. Peu à peu, une psychose s'installe.En quatre jours, le mystérieux tueur fait trois victimes. Les enquêteurs de la 3e brigade territoriale de Paris sont persuadés qu'il s'agit d'un seul et même prédateur, mais ne parviennent pas à l'appréhender. C'est finalement une intervention banale qui va les mettre sur la bonne piste.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette affaire avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Clémentine Spiler, Clara Garnier-Amouroux, Thibault Lambert et Marin Guillon Verne - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network - Archives : INA.Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
(Premier épisode) Durant l'automne 1977, un homme sème la terreur dans le Xème arrondissement de Paris. Plusieurs femmes sont violées et tuées par strangulation dans leur parking ou leur appartement. Peu à peu, une psychose s'installe.En quatre jours, le mystérieux tueur fait trois victimes. Les enquêteurs de la 3e brigade territoriale de Paris sont persuadés qu'il s'agit d'un seul et même prédateur, mais ne parviennent pas à l'appréhender. C'est finalement une intervention banale qui va les mettre sur la bonne piste.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette affaire avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Clémentine Spiler, Clara Garnier-Amouroux, Thibault Lambert et Marin Guillon Verne - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network - Archives : INA.Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
Cameron is joined by Tom Terranova, CEO of QUAD A, and they discuss the critical theme of compliance in the medical aesthetics industry. They explore the evolving landscape of regulations, the importance of accreditation, and how practices can enhance patient safety and trust through compliance. They highlight the need for a structured approach to compliance, emphasizing that it is not merely a checkbox but a continuous process of improvement and accountability. Tom shares insights on how QUAD A supports practices in achieving and maintaining high standards, ultimately benefiting both providers and patients.Cameron and Tom talk about the evolving landscape of medical aesthetics, focusing on the importance of patient trust, compliance, and accreditation. They explore the common deficiencies in medical practices, the accreditation process, and the potential impact of AI on healthcare. They also emphasize the need for practices to adapt to changing regulations and patient expectations while maintaining high standards of care. Listen In!Thank you for listening to this episode of Medical Millionaire!Takeaways:Compliance is essential for safety and regulation in medical aesthetics.The wellness industry is at a pivotal moment for maturation.Patients should be treated as individuals, not just consumers.Accountability and continuous improvement are key aspects of compliance.A compliant practice is characterized by thoughtful and intentional operations.Standards for compliance are evolving as the industry grows.Optimizing operations is as important as meeting compliance standards.Patients value impartial accreditation as a sign of quality.Compliance should be viewed as an ongoing process, not a one-time checklist.Practices should aim to compete on quality rather than just price. Patients prioritize safety, results, compliance, and trust in their healthcare.The rise in popularity of aesthetic treatments has led to increased adverse events.Accreditation significantly boosts patient trust and confidence in medical facilities.Many patients remain unaware of the benefits of elective wellness treatments.Documentation is the most common deficiency in medical practices.The accreditation process typically takes around five months for facilities.Accreditation may soon become a standard expectation in the industry.Legislation regarding medical aesthetics is on the horizon.AI has the potential to enhance compliance but must be used cautiously.Practices need to differentiate themselves to thrive in a saturated market.Medical Millionaire: The Blueprint for Scaling a World-Class Medical Aesthetics PracticeWelcome to Medical Millionaire, the go-to podcast for forward-thinking Medspa owners, Medical Aesthetics leaders, Plastic Surgery & Dermatology practices, Concierge Wellness clinics, and Elective Healthcare entrepreneurs who are ready to scale with intention and operate like a true, high-performing business.If you're building, growing, optimizing, or preparing to exit your aesthetics or wellness practice, this show is your competitive advantage.Hosted by Cameron Hemphill Your Guide to Sustainable, Scalable Growth Your host, Cameron Hemphill, is one of the most trusted growth strategists in Medical Aesthetics and Elective Wellness.With over 10 years in the industry, Cameron has helped scale 1,000+ practices and more than 2,300 providers, working alongside the most recognized KOLs, national brands, EMRs, tech companies, and private equity groups, shaping the future of aesthetics. From marketing to operations, from finance to leadership, Cameron brings a real-world, data-driven perspective on what it takes to turn a practice into a powerful business engine.What This Podcast Is All About: Each episode takes you behind the scenes of the fastest-growing practices in the country, revealing the systems, strategies, and mindset required to win in today's Medical Aesthetics landscape.Expect tactical insights, step-by-step frameworks, and conversations with:Industry thought leadersTop injectors & medical directorsEMR & tech innovatorsOperations expertsMarketing strategistsPrivate equity & M&A advisorsWellness and longevity pioneersThis is where aesthetics, business, technology, and wellness converge. What You'll Learn on Medical Millionaire Every week, you'll access expert guidance to help you scale profitably and predictably, including:Marketing & Brand PositioningCRM + Lead Management SystemsPatient Acquisition & ConversionEMR Optimization & Tech Stack ArchitectureSales Psychology & Consultation MasteryFinance, KPIs, and Practice EconomicsOperational Workflows & AutomationIndustry Trends Backed by Real Benchmark DataPatient Retention & Lifetime Value ExpansionMindset, Leadership & Team DevelopmentWhether you're opening your first location or running a multi-million-dollar enterprise, you'll gain the clarity and direction to grow with confidence. A Show Designed for Every Stage of Practice Growth Medical Millionaire breaks down the journey into four essential stages, showing you exactly how to move from one to the next:Startup – Build the foundation and attract your first wave of patientsGrowth – Scale revenue, expand services, and strengthen operationsOptimize – Increase efficiency, margins, and customer experienceExit – Prepare your practice for maximum valuation and acquisitionIf You're Ready to Grow, This Is Where You Start. Tune in weekly for actionable insights, expert interviews, and the exact playbooks high-performing practices use to dominate their markets. This is the podcast for Medspa owners who want more than a job; they want a scalable, profitable, industry-leading business. Welcome to Medical Millionaire.Let's build your practice into the empire it deserves to be.
Send us Fan MailIn this episode, Scott Kuhlman and Chasity Owens sit down with Founder Jesse Sprague, Director of Research & Intelligence Phinehas Lampman, and Software Developer and Data Scientist Kathleen Matos from Axon Intelligence to talk about the future of wildland fire investigation, origin and cause documentation, data science, remote sensing, AI, drone imagery, and fire investigation technology. The conversation explores how the new app EchoSpectra is helping investigators organize field data, document wildland fire indicators, track GOA/SOA development, export maps and photo logs, and strengthen the scientific method through better case organization. The group also discusses how computer vision, mapping, drone-based imagery, and pattern recognition may shape the future of both wildland and structure fire investigations, while also touching on firefighter health, smoke exposure, Valley Fever, and the need for better respiratory protection in the field.Thank you for listening! If you enjoyed the episode, give us 5 stars, hit the follow button, and subscribe on Spotify, Apple Podcasts, and anywhere you are listening in from. Follow us on social media!Instagram: @infocusfire_podcastLinkedIn: INFOCUS podcastFacebook: INFOCUS podcastTikTok: @infocus_podcast
In this episode of Building Better Developers, Jim Hodapp and Bob Belderbos discuss why Rust continues to gain momentum among experienced developers. The conversation explores software craftsmanship, memory safety, AI-assisted development, and why language choice is becoming less important than understanding how software actually works. Key Discussion Points Why Rust attracted both systems programmers and Python developers The relationship between AI coding tools and strongly typed languages How Rust improves software reliability The importance of understanding software fundamentals Why developer growth often requires embracing discomfort The Rust Developer Mindset is not really about Rust. That may sound strange coming from two developers actively teaching the language, but one of the strongest themes from the discussion with Jim Hodapp and Bob Belderbos was that successful software development starts with understanding systems, not syntax. As AI generates code faster than ever, developers who understand architecture, performance, and reliability are becoming increasingly valuable. Rust simply happens to be one of the best environments for developing those skills. About our Guests Jim Hodapp Jim Hodapp is a veteran software engineer, engineering leader, and technical coach with deep roots in systems programming. His background spans C, C++, Linux, embedded systems, software architecture, and engineering management. In recent years, he has become a recognized Rust advocate, helping developers transition from traditional systems languages into modern, memory-safe development practices. Through RefactorCoach and his Rust training initiatives, Jim focuses on improving engineering effectiveness, software quality, and developer growth. Follow Jim on LinkedIn: https://www.linkedin.com/in/jim-hodapp/ Bob Belderbos Bob Belderbos is a software developer, educator, coach, and co-founder of PyBites. Originally coming from a finance background, Bob transitioned into software through automation, scripting, and Python development. He has spent years helping developers improve their coding skills through practical challenges, mentoring, and community-based learning. More recently, Bob has expanded his focus into Rust, combining his Python expertise with modern systems programming practices to help developers build faster, safer, and more maintainable software. Follow Bob on LinkedIn: https://www.linkedin.com/in/bbelderbos/ Why the Rust Developer Mindset Starts with Fundamentals Many developers begin their careers with languages that allow rapid progress. Python is an excellent example. Developers can create useful applications quickly, automate repetitive work, and see results almost immediately. That accessibility explains much of Python's popularity. The challenge appears later. The Rust Developer Mindset encourages developers to move beyond writing code that works and toward building systems that remain reliable over time. Great developers eventually become students of systems, not just programming languages. How Rust Forces Better Engineering Habits One reason both guests spoke so positively about Rust is that the language encourages deliberate thinking. Rust's ownership model, compiler checks, and strict type system often prevent entire categories of bugs before software ever runs. For developers accustomed to highly dynamic environments, this can feel restrictive at first. Eventually, however, the restrictions become guardrails. Instead of discovering issues in production, developers discover them during compilation. That shift changes how software gets built. The language rewards planning, understanding data flow, and thinking carefully about how components interact. Those are valuable skills regardless of which language a developer uses professionally. Rust Developer Mindset in the Age of AI One of the most interesting topics from the episode was AI-assisted development. A common assumption is that AI reduces the importance of programming expertise. The opposite may be true. Modern AI tools can generate large amounts of code rapidly. However, generated code still requires evaluation, validation, testing, and architectural oversight. Strongly typed languages create an interesting advantage. When AI generates imperfect code, the compiler immediately becomes part of the feedback loop. The compiler identifies errors, exposes assumptions, and forces corrections. This creates a collaborative cycle between the developer, AI, and compiler that often produces more reliable outcomes. The Rust Developer Mindset embraces this reality by treating AI as a productivity multiplier rather than a replacement for engineering judgment. Faster code generation does not eliminate the need for software design expertise. Learning Through Productive Friction Bob described his transition from Python to Rust as a challenge. That challenge turned out to be valuable. Many developers plateau because they remain inside familiar environments. They become highly productive but stop expanding their understanding. Learning Rust introduces concepts that many scripting languages intentionally hide: Ownership Borrowing Memory management Concurrency considerations Compiler-guided design These concepts can initially feel uncomfortable. Yet that discomfort often signals growth. Developers gain a deeper appreciation for what their software is doing beneath the surface. The result is not merely Rust knowledge. It is a broader engineering capability. Why Performance Still Matters The conversation also highlighted a topic that often gets overlooked in modern development. Performance still matters. Cloud resources may be abundant, but inefficient software still creates costs. Applications that consume excessive memory, waste CPU cycles, or scale poorly eventually impact users and businesses. Rust provides developers with low-level control while maintaining modern safety guarantees. This combination helps engineers build software that remains efficient without sacrificing maintainability. The Rust Developer Mindset recognizes that performance is not about optimization for its own sake. It is about creating software that respects resources and scales effectively. Identify one application you currently maintain and investigate where performance bottlenecks originate before attempting optimization. The Future Belongs to Software Engineers The strongest takeaway from the episode is that language debates are becoming less important. AI can help generate syntax. Documentation can explain APIs. Tutorials can teach frameworks. What remains difficult is understanding how systems behave. Developers who can reason about architecture, reliability, performance, and maintainability will continue to stand out regardless of tooling trends. That is ultimately what Rust helps reinforce. The future belongs to engineers who understand systems deeply enough to guide both AI and software toward better outcomes. Conclusion The Rust Developer Mindset is not simply about adopting a new language. It is about developing a stronger understanding of software itself. By encouraging developers to think more carefully about correctness, performance, and system behavior, Rust creates opportunities for long-term growth that extend far beyond any individual technology stack. Stay Connected: Join the Developreneur Community
SummaryIn this episode of the Blue Security Podcast, hosts Andy Jaw and Adam Brewer discuss Andy's career transition from Microsoft to Zscaler, the return of the AI model Fable and its user experience, and a critical SharePoint vulnerability that has caught CISA's attention. They delve into the implications of these topics for security professionals and the importance of staying updated on actively exploited vulnerabilities.----------------------------------------------------YouTube Video Link: https://youtu.be/3VbR22krL-w----------------------------------------------------Documentation: https://www.bleepingcomputer.com/news/artificial-intelligence/claude-fable-relaunch-disappoints-users-with-nerfed-performance/https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45659https://www.cisa.gov/known-exploited-vulnerabilities-catalog----------------------------------------------------Contact Us:Website: https://bluesecuritypod.comBluesky: https://bsky.app/profile/bluesecuritypod.comLinkedIn: https://www.linkedin.com/company/bluesecpodYouTube: https://www.youtube.com/c/BlueSecurityPodcast-----------------------------------------------------------Andy JawBluesky: https://bsky.app/profile/ajawzero.comLinkedIn: https://www.linkedin.com/in/andyjaw/Email: andy@bluesecuritypod.com----------------------------------------------------Adam BrewerTwitter: https://twitter.com/ajbrewerLinkedIn: https://www.linkedin.com/in/adamjbrewer/Email: adam@bluesecuritypod.com
Episode Summary In this episode of All Things Wildfire, OP sits down with Steve Slepcevic of Strategic Response Partners to talk about the reality of private wildfire response, home hardening, evacuation planning, and why relying on fire departments alone is not enough during major wildfire events. Steve explains that during large wind-driven fires, municipal fire departments can quickly become overwhelmed, hydrants can run dry, and access can become restricted. The conversation highlights why prevention, preparation, and layered defense matter: home hardening, vegetation management, fire retardant pre-treatment, pool-based fire pump systems, air scrubbers, evacuation planning, digital documentation, and professional strike teams all work together to reduce risk. A major theme of the episode is that homeowners should not wait until the fire is already coming. By then, access may be blocked, evacuation routes may be overwhelmed, and response resources may already be assigned elsewhere. The episode also covers the insurance side of wildfire loss, including the limits and frustrations many homeowners face with the California FAIR Plan, especially around smoke, ash, and cleaning coverage. The key takeaway: wildfire resilience is not one product, one service, or one last-minute decision. It is a full 360-degree plan that needs to be built before disaster strikes. Key Highlights 1. Fire departments are not built for thousands of homes burning at once Steve explains that local fire departments are effective for everyday structure fires, but catastrophic wildfire conditions can overwhelm water supply, staffing, apparatus, and access. 2. Pools can become a critical emergency water source The episode discusses using a homeowner's pool as a 25,000–30,000 gallon water source when hydrants fail, but only if the right commercial-grade, maintained pump system is already in place. 3. DIY fire pumps can create a false sense of security Steve warns that many consumer-grade pumps are not built for extended wildfire conditions. If a pump fails during the critical moment, the homeowner or firefighters may be put in danger. 4. Staying behind can increase home survivability, but it can be deadly OP and Steve discuss the hard truth: homes often have a better chance when someone is there to address spot fires, but hurricane-force winds, ember storms, smoke, blocked exits, and poor visibility can make staying extremely dangerous. 5. Evacuation should happen before the chaos begins Steve emphasizes getting family out early, especially when wind patterns suggest the fire could move toward the area. Waiting for a mandatory order can put people into traffic jams, smoke, and blocked roads. 6. True wildfire defense is layered The strongest strategy combines home hardening, vegetation management, ember-resistant vents, fire retardant pre-treatment, defensible space, pumps, hose layouts, air scrubbers, and professional response teams. 7. Pre-treatment buys firefighters time Fire retardant and defensible space reduce heat exposure and create buffer zones, helping private firefighters safely protect the property when the fire front arrives. 8. Credentialed access matters Steve explains that professional teams need proper firefighter credentials, communication with incident command, and strong reputations to access restricted zones during active incidents. 9. Your neighbor's house can become your biggest threat The episode highlights the danger of radiant heat, especially in neighborhoods where homes are only 10–20 feet apart. Even if your property is prepared, nearby structure fires can break windows and ignite your home. 10. Documentation matters before a loss OP shares how Matterport scans, photos, and videos can help homeowners prove finishes, contents, and property condition after a wildfire loss. 11. FAIR Plan coverage can be a major issue The episode discusses frustrations around the California FAIR Plan, including limited coverage, lack of cleaning/deodorization support, slow response, and gaps many homeowners do not discover until after a fire. 12. The best time to prepare is before the call for help Steve makes it clear that private fire response cannot be arranged at the last second. Teams, pumps, plans, and access need to be established before a wildfire threatens the property.
What does it really mean to advocate for your teenager? In this episode, I break down the difference between doing the work for your kid and equipping them to do it themselves. I cover the 5 tools every teen needs from their dad, how to handle the hardest moments of adolescence without taking over, and a special word for the dads who feel like they've missed the window. Plus, a challenge that could change the conversation in your home this week.Key Takeaways:Advocacy means equipping, not rescuingThe 5 tools: Language, People, Regulation, Documentation, BeliefHow to handle school, social, and opportunity situationsIt is never too late to re-engageThe conversation your teen needs you to start this weekResources: nooffseason4dads.com | @nooffseason4dads
(Deuxième et dernier épisode) Le 31 octobre 2008, un cadavre est découvert dans une voiture calcinée à Villard-Bonnot (Isère), une petite ville située à 15 kilomètres au nord de Grenoble. Impossible d'identifier le corps à ce stade mais les enquêteurs retrouvent le nom du propriétaire de la voiture brûlée : il s'agit de Daniel Cano, un homme de 58 ans qui habite à 150 mètres du lieu où a été retrouvé le véhicule.Les gendarmes se rendent à son domicile, sonnent, et tombent sur son épouse, Manuela Gonzalez. Elle leur dit qu'elle ne sait pas où est son mari, mais la profusion de détails qu'elle fournit aux enquêteurs, alors que ces derniers ne lui ont pas encore parlé du corps retrouvé quelques heures plus tôt, va éveiller leurs soupçons.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette affaire avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Marin Guillon Verne, Clémentine Spiler et Clara Garnier-Amouroux - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network. Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
(Premier épisode) Le 31 octobre 2008, un cadavre est découvert dans une voiture calcinée à Villard-Bonnot (Isère), une petite ville située à 15 kilomètres au nord de Grenoble. Impossible d'identifier le corps à ce stade mais les enquêteurs retrouvent le nom du propriétaire de la voiture brûlée : il s'agit de Daniel Cano, un homme de 58 ans qui habite à 150 mètres du lieu où a été retrouvé le véhicule.Les gendarmes se rendent à son domicile, sonnent, et tombent sur son épouse, Manuela Gonzalez. Elle leur dit qu'elle ne sait pas où est son mari, mais la profusion de détails qu'elle fournit aux enquêteurs, alors que ces derniers ne lui ont pas encore parlé du corps retrouvé quelques heures plus tôt, va éveiller leurs soupçons.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette affaire avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Marin Guillon Verne, Clémentine Spiler et Clara Garnier-Amouroux - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network. Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
Send us Fan MailDeliver at 11 PM Tuesday and round at 1 AM Wednesday: paid. Deliver at 8 AM Tuesday and round at 4 PM Tuesday: included in the delivery code, and billing it separately is a compliance violation. Same clinical work, two different outcomes. The only variable is the calendar. Starting January 1, 2027 postpartum care moves to E/M billing with hospital rounds, discharge management, and outpatient checkups all individually billable. Dr. Heather Signorelli walks through the code sets, the same-day trap, the multi-provider wrinkle, and the three-step workflow that catches it every time. The end of the postpartum bundle: Code 59430 (postpartum care only) is deleted January 1, 2027. All postpartum care moves to E/M billing. Two settings, two code sets: inpatient (hospital rounds) and outpatient (office visits). Inpatient postpartum codes: Subsequent hospital care: 99231, 99232, 99233 for daily rounding visits after the date of delivery. Discharge day management: 99238 (30 minutes or less) or 99239 (over 30 minutes). Every rounding day after delivery, on a new calendar date, is a separately billable E/M encounter. Documentation has to support the level. A one-liner does not support a 99233. Outpatient postpartum codes (with telehealth correction): Standard office E/M: 99212 through 99215 with modifier TH. Telehealth uses the same 99212 through 99215 codes with modifier 95 or GT, and place of service 02 or 10. There is no separate “98000” telehealth code set, contrary to earlier references in this series. Modifier TH on all postpartum E/M codes communicates the maternity context to the payer. The same-day rule: Postpartum E/M codes CANNOT be reported on the same calendar date as the delivery code. Same-day postpartum management is included in the delivery code. Calendar date means midnight to midnight, not twenty-four hours from delivery time. The multi-provider wrinkle: If Dr. Smith delivers at 8 AM and Dr. Jones rounds at 4 PM the same day, Dr. Jones cannot bill an E/M for that visit. The delivery code covers same-day postpartum regardless of which provider from the same group performs it. This requires an internal compensation and attribution policy, not just a billing rule. The workflow fix — three steps: Timestamp discipline on every delivery and rounding note Billing team hard stop: verify delivery date before dropping any postpartum E/M charge Daily L and D reconciliation: track delivery date, rounding date, and provider by patient, daily The revenue opportunity: Every hospital rounding day after the delivery date is a new billable E/M. Extended stays from complications (postpartum hemorrhage, severe preeclampsia, wound infection, NICU situations) all generate additional charges. Complexity matters for reimbursement. Outpatient two-week and six-week checks are now individually billable instead of absorbed into a global fee. The same-day rule is the risk. Everything after midnight is the opportunity. Quick Reference Table:Topic What to knowDeleted postpartum code 59430 — deleted Jan 1, 2027 Inpatient rounds 99231 – 99233 Discharge codes 99238 (≤30 min) · 99239 (>30 min)Outpatient postpartum 99212 – 99215 + modifier TH Telehealth modifier Modifier 95 or GT · POS 02 or 10 NOT a separate 98000 code set Same-day rule Postpartum E/M cannot be billed on the same calendar date as the delivery Calendar definition Midnight to midnight Multi-provider same-day Delivery code covers regardless of which group provider roundsWorkflow fix Timestamps · billing hard stop · daily reconciliationRESOURCES BLOCK Save your seat: Live OB/GYN Global Codes Update Webinar (July 7, 2026, 4:00 PM ET) · eligibility.natrevmd.com/obgyn-global-updates-webinar Book a 1:1 with Dr. Signorelli · calendly.com/heather-natrevmd/ Practice Revenue Leak Scorecard · eligibility.natrevmd.com/nrm-revenue-scorecard-v3 Payment Posting Audit Checklist · eligibility.natrevmd.com/payment-posting-checklist RECOVER Diagnostic Quiz · natrevmd.com/quiz Series Part 3 (EP191): https://podcasts.apple.com/us/podcast/191-labor-management-is-no-longer-invisible/id1624182351?i=1000775009191
How good is your consent for orthodontics — really? More adults are having ortho, and more GDPs are providing it. So which risks should you be discussing with every single patient — and which ones depend on the person in the chair? When a case is heading for a big overjet or a tricky rotation, is that a conversation you have at the start, or one you scramble to explain halfway through? And what actually makes a consent form legally valid — the signature, or everything around it? This episode brings together two perspectives you don't often hear in the same room. Dr Zaid Esmail is a specialist orthodontist and founder of the Online Orthodontic Academy, who mentors GDPs through fixed and aligner cases. Dr Neel Jaiswal returns for the dento-legal view — he's a dentist and the founder of Professional Dental Indemnity (PDI). Together with Jaz, they get very specific about what individualised consent looks like in practice, and how to build a process your patients remember and a court respects. https://youtu.be/YvsiIiX1Q1w Watch PDP273 on YouTube Protrusive Dental Pearl: Make Your Patient Feel Unique It might be your 100th, 500th or 1,000th case — but for the patient in the chair, this is a significant event. Never forget that. A routine extraction is routine for you; for them it's a big deal, and remembering that makes you a better communicator. To make a specific risk stick, make the patient feel unique. Point to their OPG: “Your sinus here is actually really interesting,” or “Did you know your roots are unusually long?” Patients remember a risk framed as if they're a special case far better than a generic warning. Make it personal, and the consent becomes memorable. What You'll Take From This Episode The whole episode turns on one idea: generic, templated consent is no longer defensible — the skill is individualising the form to the patient in front of you. Premium members get the full breakdown; here's the shape: The layers of valid consent — consent is like an onion; a signed form and a documented conversation each cover a gap the other leaves open. Individualising risk from the records — how the OPG and photos turn a generic warning (resorption, devitalisation, recession, relapse) into a patient-specific one. The two-appointment consent flow — records, individualised risks, thinking time, and why you sign or initial every line. The Class II Div 2 overjet trap — the case that looks like simple crowding and ends in a big overjet, and how to consent for it before you start. When to treat, add an option, or refer — the GDC line on offering all options, and building alternatives into the form. Highlights of This Episode: 00:00 Teaser 01:01 Consent in Orthodontics: Why It Has to Be Individualised 02:59 Protrusive Dental Pearl: Make Your Patient Feel Unique 07:58 What Makes Orthodontic Consent Different 10:08 How Much Ortho Litigation Comes From Consent? 11:53 What Makes Consent Valid and Patient-Specific 12:26 Individualising Ortho Risk from the OPG 13:11 Using the ClinCheck as a Consent Tool 14:40 How to Structure the Consent Appointment 15:30 Root Resorption, Devitalisation, Recession and Relapse 19:37 Should You Initial Every Line of a Consent Form? 21:50 Midroll 27:11 Building a Multi-Layered Consent Process 29:31 Consenting for Fees, Relapse and Retainers 34:41 The Class II Div 2 Overjet Trap 37:51 When Should a GDP Refer an Ortho Case? 40:31 How to Learn Orthodontics with Mentorship 47:01 Outro Dr Zaid Esmail is a specialist orthodontist. He founded the Online Orthodontic Academy to teach GDPs orthodontics — assessment, diagnosis and treatment planning across fixed appliances and aligners — with one-to-one case mentorship. He's extended a 10% discount to the community with the code PROTRUSIVE.
Patients are coming home from the hospital sooner, sicker, and with more complex needs than ever before. For home health agencies, that shift is changing everything from clinical workflows and documentation to staffing, caregiver support, and revenue cycle performance. In this episode of Home Health Revealed, Hannah Vale sits down with Rachel Trombly, Director of Clinical Services at Mosai, to discuss what higher-acuity care really means for today's home health providers. Together, they explore how agencies can move from reactive to proactive care through stronger risk stratification, better care coordination, more meaningful documentation, and empowered caregivers. Tune in to learn: Why patient acuity is increasing—and what it means for your agency How documentation can better capture patient complexity The critical role caregivers play in preventing rehospitalizations Why risk stratification is becoming essential for operational success How agency leaders can better support clinicians while improving quality and financial performance Whether you're a clinician, operational leader, or revenue cycle professional, this conversation offers practical strategies to help your agency adapt to the new reality of higher-acuity home health. Access Rachel's recently published a blog, "Why Risk Stratification Is Becoming Essential Amid Staffing Shortages in Home-Based Care" which expands on many of the themes discussed in the interview: www.mosai.com/blog/why-risk-stratification-is-becoming-essential-amid-staffing-shortages-in-home-based-care Chapters (00:00:03) - Home Health Revealed: The Shift towards higher-acuity patients(00:01:39) - Interviews with Home Health Agency Executives(00:02:50) - Home Health Care: Higher Acuity in the Home(00:04:39) - Home Health Care: Complex Care Needs(00:08:12) - OASIS 12, Documentation(00:10:56) - What are the biggest gaps or risks when agencies are managing higher ac(00:13:27) - The Plan of Care for High-Acuity Patients(00:15:59) - Caregiver-centered care(00:22:35) - What are the biggest drivers of home health hospitalizations?(00:25:53) - Capacity planning for complex patients(00:30:11) - How to better support complex cardiac patients?(00:37:36) - What's the One Thing Home Health Companies Need to Do to Man(00:39:53) - Interviews with Mosay On Home Based Care
Send us Fan MailHow can nonprofits build community support for after-school programs while creating measurable value for children, families, funders, and local leaders? JonPaul Reed, founder and executive director of Pure Momentum Group and founder of Athlete University, shares how the hours between 3:00 and 6:00 p.m. can become a powerful platform for youth development and stronger communities.The school day may end before parents finish working, but JonPaul sees that gap as much more than a supervision problem. It is an opportunity to build work ethic, decision-making, teamwork, leadership, communication skills, and what he calls “monetizable skill sets.”“We're either taking advantage of that window or we're not,” he explains.JonPaul also examines how youth sports have become increasingly driven by money, exclusivity, and winning. For nonprofit leaders, his warning is clear: programs must remain grounded in access, developmental outcomes, and the needs of young people—not simply the ambitions of adults.The conversation moves from program philosophy into the business of running and growing a youth-serving nonprofit. JonPaul discusses building parent buy-in, choosing the right time for difficult conversations, maintaining organizational paperwork, meeting with commissioners, submitting proposals, developing municipal relationships, and presenting a program in language decision-makers understand.His experience also shows why passion alone is not enough. Nonprofits need a defined model, consistent follow-up, credible documentation, accessible leadership, and a message that community partners can quickly understand. As JonPaul advises, “Package your product and package it well, and also get the right person to speak for you.”For nonprofit executives, program directors, board members, coaches, and community leaders, this episode offers a candid look at how mission, culture, communication, and operational discipline work together to create sustainable youth programs.Key Takeaways:* Treat the 3-to-6 p.m. period as a youth-development and workforce-readiness opportunity—not merely a childcare gap.* Build parent participation through timely, honest communication and shared accountability.* Define developmental outcomes before allowing competition, revenue, or adult expectations to shape the program.* Establish tax-exempt status, documentation, proposals, and operating records before approaching major partners.* Translate personal passion into a clear model that public officials, businesses, and funders can understand.* Delegate communications and introductions when another team member can position the organization more effectively.00:00:00 Why the 3-to-6 PM Window Matters00:02:31 Building Access Through Pure Momentum Group00:05:49 The Daily Gap Between School and Home00:07:28 Turning a Youth Development Gap Into a Gateway00:08:14 Preparing Young People for a Competitive World00:11:29 Reclaiming the Developmental Purpose of Sports00:16:14 Building Accountability With Parents and Children00:19:05 Creating Culture and Organizational Buy-In00:20:42 How Youth Programs Gain Community Support00:22:10 Packaging a Mission for Partners and Funders00:23:28 Documentation, Legitimacy, and Funding Readiness00:28:23 Leading Through Criticism, Risk, and Resilience#AfterSchoolPrograms #NonprofitLeadership #TheNonprofitShowFind us Live daily on YouTube!Find us Live daily on LinkedIn!Find us Live daily on X: @Nonprofit_ShowOur national co-hosts and amazing guests discuss management, money and missions of nonprofits! 12:30pm ET 11:30am CT 10:30am MT 9:30am PTSend us your ideas for Show Guests or Topics: HelpDesk@AmericanNonprofitAcademy.comVisit us on the web:The Nonprofit Show
This special compilation brings together three of our most important episodes exploring the medico-legal aspects of pre-hospital care. From documentation and communication to legal responsibilities and ethical decision-making, this collection provides practical guidance to help clinicians navigate some of the most challenging situations they will encounter in practice.We begin with Mark Faulkner, who was the Assistant Medical Director at the London Ambulance Service at the time of recording. Drawing on more than a decade of experience supporting and leading the organisation's pre-hospital legal department, Mark shares invaluable insights into the legal principles that underpin safe clinical practice and how clinicians can protect both their patients and themselves.Across the series, we explore:High-quality documentation and effective clinical handoversDuty of care, negligence, and professional accountabilityMandatory reporting and safeguardingConfidentiality and working alongside law enforcementManaging legal challenges during major incidentsPatient autonomy, capacity, and refusal of treatmentAdvance decisions and end-of-life carePractical approaches to ethical and legal decision-makingThe compilation concludes with Steve Bell, Consultant Paramedic and Consultant HEMS Paramedic, who discusses the complex intersection between ethics and law in pre-hospital care, providing practical strategies for navigating difficult decisions in the field.Documentation and Communication: Medico-Legal Aspects of Care – Part 1 (Mark Faulkner)Managing Complex Legal Scenarios: Medico-Legal Aspects of Pre-Hospital Care – Part 2 (Mark Faulkner)Ethical and Legal Decision-Making: Medico-Legal Aspects of Pre-Hospital Care – Part 3 (Steve Bell)Whether you're a student, paramedic, critical care practitioner or physician working in pre-hospital care, these conversations offer practical, evidence-informed advice to strengthen your clinical decision-making, improve patient safety and reduce medico-legal risk.This episode is sponsored by PAX: The gold standard in emergency response bags.When you're working under pressure, your kit needs to be dependable, tough, and intuitive. That's exactly what you get with PAX. Every bag is handcrafted by expert tailors who understand the demands of pre-hospital care. From the high-tech, skin-friendly, and environmentally responsible materials to the cutting-edge welding process that reduces seams and makes cleaning easier, PAX puts performance first. They've partnered with 3M to perfect reflective surfaces for better visibility, and the bright grey interior makes finding gear fast and effortless, even in low light. With over 200 designs, PAX bags are made to suit your role, needs, and environment. And thanks to their modular system, many bags work seamlessly together, no matter the setup.PAX doesn't chase trends. Their designs stay consistent, so once you know one, you know them all. And if your bag ever takes a beating? Their in-house repair team will bring it back to life.PAX – built to perform, made to last.Learn more at https://www.pax-bags.com/en/
Rent To Retirement: Building Financial Independence Through Turnkey Real Estate Investing
This episode is sponsored by…NCH:Set up an LLC to protect your investments! – https://nchinc.com/rtrBLUPRINT HOME LOANS:Get pre-approved with one of RTR's preferred lenders at - https://bluprinthomeloans.com/renttoretirement/ ROI Property Group:If you are interested in direct lending with ROI Property Group, give Rob Fuller a call at 707-365-6891 to learn more. 12-24 month loan options are available. Let him know that Rent To Retirement sent you! - https://www.roipropertygroup.com/rtrAre you taking full advantage of the tax strategies available to real estate investors?
It's Shark Storytime! Derk Remmers and Isadora Abuter share their rare encounter with a great white shark (Big Ben) with Dr Scarlett Smash and Dr Craken. Guest information Derk Remmers, Ghost Diving and dive instructor for GUE (Global Underwater Explorers www.ghostdiving.de Isadora Abuter, Marine Biologist, Marine Research and Communications Coordinator at Healthy Seas www.healthyseas.org Guest Information Healthy Seas organized the mission, continuing its broader work on ghost-net removal and biodiversity monitoring on Mediterranean shipwrecks. The project was carried out together with Ghost Diving and SDSS (The Society for Documentation of Submerged Sites) combining marine conservation, technical diving, scientific collaboration and underwater documentation. Volunteer technical divers from Ghost Diving carried out the underwater recovery operations, while Healthy Seas coordinated the mission and its scientific activities in collaboration with SDSS, which contributed historical shipwreck expertise and underwater documentation throughout the project. www.healthyseas.org Podcast Information Contact info@absolutelysmashingllc.com for more information about sponsoring MCHH episodes Music credits By Jolly Shore Leave "Al For Me Grog (Trad.)" HandsomeForrune-FE (Adapted Lyrics by Taran Christen : Musical Arrangement by K. Ryan Hart) Represented by Rebellious Entertainment Dr Scarlett Smash Instagram Dr Scarlett Smash TikTok Dr Craken MacCraic Instagram MCHH Instagram MCHH Facebook Dr Scarlett Smash YouTube
In this episode of Senior Living Executive Strategy, Melissa Brown welcomes Rob Schenk of Schenk Nursing Home Abuse Law for a candid conversation about what senior living and skilled nursing leaders need to understand about legal risk.Rob shares the perspective of a plaintiff's attorney who works on nursing home cases, including what attorneys look for when evaluating potential claims, why staffing data has become more important, and how documentation gaps can create serious risk for providers.The conversation also covers how PBJ data, acuity, AI-generated documentation, ignored alerts, private equity ownership, and administrator decision-making can all play a role in nursing home liability.For operators, owners, administrators, DONs, and senior living executives, this episode is a valuable look at the legal blind spots that can develop inside a building, especially when staffing, documentation, and care delivery are not aligned.Read the companion article here: https://gravityhealthcareconsulting.com/senior-living-executive-strategy-podcast/nursing-home-risk-management-staffing-documentation-lawsuits/ Senior Living Executive Strategy is brought to you by Gravity Consulting, an outcomes-focused consulting firm for senior living, skilled nursing, and home health organizations.If something in today's conversation connects to a challenge you're facing—or if your organization has an operational, clinical, reimbursement, or growth issue that needs to be solved—visit gravityconsulting.com to learn how Gravity can help.Support the show
Rent To Retirement: Building Financial Independence Through Turnkey Real Estate Investing
This episode is sponsored by…NCH:Set up an LLC to protect your investments! – https://nchinc.com/rtrBLUPRINT HOME LOANS:Get pre-approved with one of RTR's preferred lenders at - https://bluprinthomeloans.com/renttoretirement/ ROI Property Group:If you are interested in direct lending with ROI Property Group, give Rob Fuller a call at 707-365-6891 to learn more. 12-24 month loan options are available. Let him know that Rent To Retirement sent you! - https://www.roipropertygroup.com/rtrAre you taking full advantage of the tax strategies available to real estate investors?
TestTalks | Automation Awesomeness | Helping YOU Succeed with Test Automation
Most API testing stops at the happy path. The problem is that the bugs that actually hurt you in production are sitting in everything many testers skip, like the boundary values, the oversized payloads, the missing tokens, the security headers, the inputs that make no sense at all. In this episode, Joe sits down with Liudas Jankauskas, who has spent almost twenty years breaking software and testing APIs since 2008. Liudas demonstrates Rentgen, his free and open-source API testing tool, live on screen. You'll watch him take a single request from a real app, map it in seconds, and generate dozens of tests covering security, boundaries, performance, and load—all from one click. You'll learn: How to discover APIs hiding under the hood of any application, even when there is zero documentation Why happy path testing leaves you exposed How to run a fast hygiene check before your real automation ever starts Liudas also explains why Rentgen runs completely locally with no server and no data leaving your machine, making it safe for banking, healthcare, and other regulated environments. Plus, he demonstrates the killer Copy Bug Report feature that drops a standards-based ticket straight into Jira or Trello. In This Episode You'll Discover How to find and test undocumented internal APIs using the browser DevTools Network tab Why happy path-only testing misses the bugs that matter most How Rentgen turns one request into security, boundary, performance, and load tests automatically Where Rentgen fits in your workflow as a pre-automation hygiene layer—not a Postman replacement How to use it for regression by comparing results across environments The one piece of advice Liudas gives every tester to level up their API testing Try Rentgen, free and open source, at Rentgen.io. Connect with Liudas Jankauskas on LinkedIn: https://www.linkedin.com/in/liudas-jankauskas/
In this episode, Dr. Jordan Whatley and Dr. Temara Hajjat talk to Dr. Katie Larson-Nath, Pediatric Gastroenterologist and Division Director at the University of Minnesota M Health Fairview Masonic Children's Hospital, who specializes in pediatric nutrition and leads the Intestinal Rehabilitation Program. We talk about the recently published joint AAP/NASPGHAN Clinical Practice Guideline for Diagnosis and Management of Faltering Weight, a new term that replaces "failure-to-thrive".Learning objectives1. Understand the basis for the change in terminology from “failure-to-thrive” to “faltering weight” per the 2026 joint AAP/NASPGHAN Clinical Practice Guideline2. Describe the defining criteria for a diagnosis of faltering weight3. Understand the recommended comprehensive evaluation and management of children with faltering weightLinksJoint AAP/NASPGHAN Clinical Practice Guideline for Diagnosis and Management of Faltering WeightWHO Weight Gain Velocity Standards2015 AND/ASPEN Consensus Statement for the Identification and Documentation of Pediatric Malnutrition (Undernutrition)Send us Fan MailSupport the showThis episode may be eligible for CME credit! Once you have listened to the episode, click this link to claim your credit. Credit is available to NASPGHAN members (if you are not a member, you should probably sign up). And thank you to the NASPGHAN Professional Education Committee for their review!As always, the discussion, views, and recommendations in this podcast are the sole responsibility of the hosts and guests and are subject to change over time with advances in the field.Check out our merch website!Follow us on Bluesky, Twitter, Facebook and Instagram for all the latest news and upcoming episodes.Click here to support the show.
Today we are talking about Marketing, AI, and Drupal with guest Paul Johnson. We'll also cover Curated Colors as our module of the week. For show notes visit: https://www.talkingDrupal.com/559 Topics Paul's Current Projects Enterprise AI Summit Details Marketing the AI Initiative Partnering on Event Booths Drupal's Outside Perception What's Working Now Growing the Marketing Team How to Contribute Outside In Storytelling Case Study Examples AI Initiative Impact Roadmap and Launch Planning Finding New Adopters Where Pros Research Conference Pitch Story Local Event Playbook Funnel and Webinars Industry Guides and Demos SEO and AI Search Why Agents Avoid Drupal High Leverage Contributions Measuring AI Mentions Vibe Coders to Governance Fixing Misconceptions Resources Drupal AI Initiative home page Slack #ai-initiative-marketing Enterprise AI Summit Rotterdam AI Dev Summit Rotterdam Drupal AI TV We've curated a selection of the best presentations, workshops and demonstrations freely available to provide a practical way to stay informed about the latest innovations in Drupal AI. Drupal AI Webinars playlist Demos Ryan Whitcombe 1xINTERNET S1xSignals free AIO GEO assessment All things open World cancer day Guests Paul Johnson - pdjohnson Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Scott Falconer - managing-ai.com scott-falconer MOTW Correspondent Martin Anderson-Clutz - mandclu.com mandclu Brief description: Have you ever wanted to allow editors on your Drupal site to choose styling from a brand-approved color palette? There's a module for that. Module name/project name: Curated Colors Brief history How old: created in Apr 2026 by Kyle Einecker (ctrladel) of True Summit Versions available: 1.0.0 which works with Drupal 10.3, 11, and 12 Maintainership Actively maintained Security coverage Test coverage Documentation - in-depth README Number of open issues: 2 open issues, neither of which are bugs Usage stats: 27 sites Module features and usage Curated Colors enforces brand consistency by replacing generic color text inputs or wide-open color pickers with a curated, visual swatch popover containing only pre-approved, named options It streamlines rebranding by storing abstract keys (such as brand-primary) instead of raw hex values (e.g., #0678be) in the database. That means updating a brand color in the future only requires a CSS or configuration change rather than a massive data migration Curated Colors is also extensible beyond colors. It functions as a generic visual variant selector. Site builders can repurpose it to let editors pick card layouts, button styles (like primary, outline, or danger), hero text alignments, or icon themes Editors can pick from neatly organized groups with human-readable labels and see a live preview swatch of their selection before saving Palettes are managed as exportable Drupal configuration. Each entry maps a machine key to a label, administrative hex preview, and optional custom CSS The module provides a curated_color field type and an accompanying swatch-based popover widget that can be restricted to specific palette groups. It also features a native curated_color_picker Form API element and integrates with the Canvas module via SDC annotations The field exposes properties like value, hex, style, and css, making it simple to output selections as classes, inline styles, or raw codes in Twig templates Finally, Curated Colors includes an example submodule providing a working SDC component and sample palette templates so you can see exactly how it's meant to be used
(Deuxième et dernier épisode) À sa naissance en 1997, Karine est déjà considérée comme une enfant en danger. À la maternité, des puéricultrices s'inquiètent du comportement de ses parents et déclenchent un premier signalement. Dans les années qui suivent, sa tante Laurence Brunet-Jambu multiplie les alertes auprès des services sociaux et de la justice, convaincue que sa nièce est en grand danger.Malgré de nombreux signalements, les institutions peinent à agir. Karine grandit dans une famille marquée par les négligences, les violences et les agressions sexuelles. Pendant des années, les alertes s'accumulent sans qu'une protection efficace ne soit mise en place. Il faudra attendre qu'elle ait 11 ans pour que sa parole soit enfin entendue et qu'elle soit éloignée de cette famille…Dans Crime story, la journaliste Clawdia Prolongeau raconte cette affaire avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Clara Garnier-Amouroux et Barbara Gouy - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network.Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
(Premier épisode) À sa naissance en 1997, Karine est déjà considérée comme une enfant en danger. À la maternité, des puéricultrices s'inquiètent du comportement de ses parents et déclenchent un premier signalement. Dans les années qui suivent, sa tante Laurence Brunet-Jambu multiplie les alertes auprès des services sociaux et de la justice, convaincue que sa nièce est en grand danger.Malgré de nombreux signalements, les institutions peinent à agir. Karine grandit dans une famille marquée par les négligences, les violences et les agressions sexuelles. Pendant des années, les alertes s'accumulent sans qu'une protection efficace ne soit mise en place. Il faudra attendre qu'elle ait 11 ans pour que sa parole soit enfin entendue et qu'elle soit éloignée de cette famille…Dans Crime story, la journaliste Clawdia Prolongeau raconte cette affaire avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Clara Garnier-Amouroux et Barbara Gouy - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network.Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
Most supervisors worry about paperwork last. Licensing boards look at it first.In this episode, I sit down with Dr. Ashley Durbin to talk about the supervision paperwork that actually matters. We move beyond forms and checklists and look at the complete documentation system every supervisor needs. From contracts and evaluations to supervision notes, hour tracking, malpractice insurance, and employment records, we break down what belongs in your supervision file and why it matters.We also discuss one of the biggest mistakes supervisors make. They wait until the end of the supervision process to organize documentation. By then, records are missing, hours are difficult to verify, and everyone is stressed.Ashley shares how she uses her EHR to simplify supervision paperwork, automate evaluations, store contracts, and keep records organized. We also talk about external supervision agreements, supervision notes, state-specific requirements, and how documentation protects both supervisors and supervisees when questions arise.This conversation is about creating better systems. When your documentation is organized, supervision becomes easier, more defensible, and far less stressful.In this episode, you'll learn: Why supervision paperwork is much more than a contract and a few forms How supervision notes and documentation protect both supervisors and supervisees The easiest ways to track hours, evaluations, and compliance requirements What records supervisors commonly forget until it is too late If paperwork has been the thing keeping you from becoming a supervisor, this episode is for you. Documentation does not have to be complicated. It just needs to be intentional.Want to learn more? Check out this month's free resource from Kate Walker Training. If this episode raised questions about supervision paperwork, documentation systems, hour tracking, or board compliance, those are exactly the conversations we continue inside the Step It Up Membership. You'll find tools, guidance, and a community of supervisors building supervision practices that are organized, compliant, and sustainable.Get your step by step guide to private practice. Because you are too important to lose to not knowing the rules, going broke, burning out, and giving up. #counselorsdontquit.
Many clinicians assume that being a great therapist naturally translates into being a great clinical supervisor. But supervision requires an entirely different set of skills.In this episode of Supervision Simplified, Dr. Amy Parks is joined by Sharon Greene, LCSW, clinical supervisor, educator, and founder of Mental Health CE Hub, for a conversation about what separates effective supervisors from effective clinicians.Together they discuss competency-based supervision, developmental supervision models, constructive feedback, ethics, documentation, burnout prevention, and the practical tools supervisors can use to better support the next generation of mental health professionals.Whether you're a new supervisor, seasoned clinical leader, or therapist considering a supervisory role, this episode offers actionable insights you can apply immediately.Topics discussed:• Why being a good clinician doesn't automatically make you a good supervisor• Constructive feedback that supervisees actually appreciate• Competency-based supervision and developmental models• Documentation, ethics, and risk mitigation• Building confidence as a clinical supervisor• The future of supervisor trainingConnect with Sharon Greene:
Derk Remmers, Ghost Diving and dive instructor for GUE (Global Underwater Explorers), and Isadora Abuter, Marine Biologist, Marine Research and Communications Coordinator at Healthy Seas share their underwater encounters during their new mission. Guest Information Healthy Seas organized the mission, continuing its broader work on ghost-net removal and biodiversity monitoring on Mediterranean shipwrecks. The project was carried out together with Ghost Diving and SDSS (The Society for Documentation of Submerged Sites) combining marine conservation, technical diving, scientific collaboration and underwater documentation. Volunteer technical divers from Ghost Diving carried out the underwater recovery operations, while Healthy Seas coordinated the mission and its scientific activities in collaboration with SDSS, which contributed historical shipwreck expertise and underwater documentation throughout the project. www.healthyseas.org www.ghostdiving.de Podcast Information Contact info@absolutelysmashingllc.com for more information about sponsoring MCHH episodes Music credits By Jolly Shore Leave "Al For Me Grog (Trad.)" HandsomeForrune-FE (Adapted Lyrics by Taran Christen : Musical Arrangement by K. Ryan Hart) Represented by Rebellious Entertainment Dr Scarlett Smash Instagram Dr Scarlett Smash TikTok Dr Craken MacCraic Instagram MCHH Instagram MCHH Facebook Dr Scarlett Smash YouTube
After a two-year hiatus, the PEPPER (Program for Evaluating Payment Patterns Electronic Report) is back. It's now available to all acute care hospitals and critical access hospitals. During the next live edition of Talk Ten Tuesday, Dr. Ronald Hirsch will share some insights that listeners can get from their PEPPER to improve their hospital's compliance, quality, and revenue. To learn more, register now to secure your seat at the table during the next live edition of Talk Ten Tuesdays, coming up at 10 a.m. EST on Tuesday, June 23.Other well-known subject-matter experts will also join the broadcast with more news to report, including the following: •Tech Report: Senior healthcare analyst Frank Cohen concludes the third installment in his three-part series on AI and coding.•POV: Penny Jefferson, cohost of Talk Ten Tuesdays, will share her point of view (POV) during the broadcast.•The Coding Report: Rose Dunn, who will substitute for Christine Geiger, will report on the latest coding news.•CDI Report: Cheryl Ericson will provide an update on clinical documentation integrity (CDI).•SDoH Report: Tiffany Ferguson, the CEO for Phoenix Medical Management, will report on news that's happening at the intersection of patient care and medical record coding
Ask a burned-out pelvic therapist what's draining them and they'll usually say the same thing: it's a lot. The emotional weight of the work, the intimacy of the specialty, the complexity of the cases.But that's not what's actually breaking providers.Pelvic therapists who love their patients are burning out anyway — because the system they work inside was never designed to sustain them. Documentation that bleeds into evenings. Reimbursement rates that haven't kept pace with inflation in a decade. Visit lengths decided by insurance instead of clinical need. And no business training to help them see the exit before they hit the wall.In this episode, Kelly breaks down the real structural drivers of burnout in pelvic health — the ones that have nothing to do with your caseload and everything to do with the model you inherited. She covers the documentation load nobody warned you about in school, the autonomy gap that comes with insurance dependency, and why this is a practice design problem — not a mindset problem, not a resilience problem, and not a you problem.She also covers what the providers who escaped burnout actually did differently. Not the ones who took a vacation and came back to the same broken model. The ones who restructured and stayed.By the end of this episode, you'll know exactly what broke — and where to start fixing it.KEY TAKEAWAYSPelvic therapist burnout is structural, not personal — it's a model problem built into the system before you ever graduatedDocumentation load, reimbursement erosion, and the autonomy gap are the three real drivers — not patient volume or emotional laborThe providers who escaped burnout didn't work less — they rebuilt the model that was consuming them
(Troisième épisode) Luc Tangorre, étudiant modèle, est condamné à 15 ans de prison en 1983 pour avoir commis plusieurs viols et agressions sexuelles entre 1979 et 1981 dans les quartiers Sud de Marseille (Bouches-du-Rhône). Défendu depuis son arrestation par des intellectuels, malgré les preuves accablantes, il obtient finalement la grâce présidentielle de François Mitterrand.Il ressort de prison 1988, avec la ferme intention de laver son honneur, lui qui a toujours clamé son innocence. À peine libéré, Luc Tangorre est pourtant de nouveau soupçonné.Dans Crime story, la journaliste Clawdia Prolongeau raconte cette enquête avec Damien Delseny, chef du service police-justice du Parisien.Crédits. Direction de la rédaction : Pierre Chausse - Rédacteur en chef : Jules Lavie - Ecriture et voix : Clawdia Prolongeau et Damien Delseny - Production : Thibault Lambert - Réalisation et mixage : Julien Montcouquiol - Musiques : Audio Network - Archive : INA, Faîtes entrer l'accusé.Documentation. Cet épisode de Crime story a été préparé en puisant dans les archives du Parisien, avec l'aide de nos documentalistes. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.
We all know that documentation is a heavy burden for therapists. But home health therapists arguably face one of the heaviest loads, with mandated OASIS reporting layered on top of standard clinical documentation — a dual requirement unique to this setting.They also face challenges that clinic-based therapists rarely encounter: coordinating care across disciplines — physicians, nurses, and other therapists — often without shared documentation systems, as well as navigating privacy considerations and internet instability when documenting in patients' homes.But, as we've already discussed around outpatient EHRs, there are changes on the horizon. In this discussion, we'll zoom in on what's becoming possible in this complex environment, from clinical decision support to practical automation. We'll be joined by Rohit Shetty of AutoMynd — Rohit is excellent at explaining exactly what's possible, while staying grounded in reality.See full course details here:https://otpotential.com/ceu-podcast-courses/home-health-therapy-documentationSee all OT CEU courses here:https://otpotential.com/ceu-podcast-coursesCheck our our live webinar schedule here:https://otpotential.com/live-ot-ceu-webinarsSupport the show by using the OTPOTENTIAL Medbridge Code:https://otpotential.com/blog/promo-code-for-medbridgeTry 2 free OT Potential courses here:https://otpotential.com/free-ot-ceusSupport the show
Send us Fan MailShow notes On January 1, 2027, every global OB code your practice has billed for the last thirty years is being deleted. Seventeen CPT codes. Gone. Replaced with a completely new structure for how every dollar of maternity revenue is earned, attributed, and collected. And the real deadline for your practice is not January 1, 2027. The real deadline is right now. What is actually going away For over thirty years, OB practices have lived in a bundled global world: one patient, one pregnancy, one code. Effective January 1, 2027, 17 global obstetric CPT codes (including 59400 for a global vaginal delivery and 59510 for a global C-section) are being deleted entirely. The AMA and ACOG determined the global model no longer reflects modern OB standard of care, and so the structure is being fully replaced, not patched. The four new phases of maternity billing Phase 1, Antepartum care. All bundled antepartum codes deleted. Every prenatal visit billed as individual E/M with TH modifier (99202 through 99215). Phase 2, Labor management. New dedicated code category for the first time in CPT history. Reported per calendar day, with straightforward vs complex management distinction. Phase 3, Delivery. Vaginal vs cesarean restructured. VBAC coded differently than first-time vaginal. Add-on procedures (3rd/4th degree laceration repair, uterine tamponade) now separately billable. Phase 4, Postpartum care. All existing postpartum codes deleted. Hospital care codes for inpatient day-after-delivery. Office E/M for outpatient follow-up. Same-date postpartum bundled into delivery. Why the real deadline is Q3 and Q4 2026 Cash flow in January 2027 will be decided this Q3 and Q4. Payer contracts reference CPT codes by number, so contracts that reference deleted codes need renegotiation now. Documentation habits have to change before the new codes go live, because every prenatal visit now needs to support E/M level selection. A 200-patient OB practice undercoding prenatal visits by even $40 each is leaving close to $100,000 a year on the table from day one. The multi-provider attribution problem Under the global model, attribution was easy: one practice, one fee, regardless of which provider saw which visit. Under the new model, every encounter is attributed to the individual provider who performed it. Practices with midlevels, hospitalists, or shared call need a clear protocol for labor management billing, on-call coverage, and cross-coverage now, or they will either double-bill (compliance risk) or miss charges (phantom revenue) from day one. Three actions this week Pull a payer contract audit. List every commercial contract referencing global OB codes that needs renegotiation before January 1. Run a prenatal documentation review. Pull 10 recent prenatal charts per provider and assess them against current 99213 and 99214 E/M standards. The gap is your single biggest revenue risk. Map your provider attribution workflow. Write out exactly how labor management, on-call coverage, cross-coverage, and same-day postpartum care will be tracked when every encounter is attributed individually. Episode breakdown 1. The 17 deleted codes 2. The four new phases of maternity billing 3. Why Q3 and Q4 of this year is your real deadline 4. The multi-provider attribution gap 5. What patients will see on their EOBs 6. Your 90-day action plan 7. What is ahead in the rest of the OB Global Coding Series Resources → Live OB Global Updates Webinar (PRIMARY): eligibility.natrevmd.com/obgyn-global-updates-webinar → Book a call with Heather: calendly.com/heather-natrevmd → Payment Posting Audit Checklist: eligibility.natrevmd.com/payment-posting-checklist → Practice Revenue Leak Scorecard: eligibility.natrevmd.com/nrm-revenue-scorecard-v3 → Coming next in the series: EP189 — How to Bill Antepartum Care Under the New E/M Model
This episode tackles a topic that impacts every BAS project but rarely gets the attention it deserves: control panel design and wiring. The quality of your panel affects commissioning, troubleshooting, inspections, and long-term serviceability. A well-built panel does more than power a system. It helps the next technician quickly understand what they're looking at when it matters most. If you've ever opened a panel and wondered why it was wired the way it was, this episode explores the principles that separate a panel that works today from one that remains reliable for years. Topics Covered • Why panel design should happen before the first wire is landed • Common wiring practices that create future troubleshooting headaches • Key considerations for power, grounding, shielding, and communications • MSTP network fundamentals that improve reliability • Documentation and wire management practices that make panels serviceable The real test of a control panel isn't how quickly it was built. It's whether the next technician can understand it in minutes.
A growing concern among auditors, coders, and compliance professionals is the increasing reliance on template driven documentation. While electronic health records have improved efficiency, copied, carried-forward, and pre-populated information can create significant compliance risks when it does not accurately reflect the patient’s current encounter. Auditors frequently identify contradictory statements, outdated histories, normal findings that conflict with the assessment and plan, and documentation that appears disconnected from the services actually provided. Simply completing documentation fields does not create credible documentation. On this episode of the CodeCast Podcast, Terry discusses why E/M documentation is not a checklist, the compliance risks associated with template generated notes, and practical strategies to ensure your documentation accurately tells the patient’s story and supports the care delivered. Subscribe and Listen Find all of Terry’s official links in one place: https://www.terryfletcher.net/links The post E/M Documentation Is Not a Checklist: Tell the Patient’s Story appeared first on Terry Fletcher Consulting, Inc..
Dr. Monica Sanford's story begins with a mother's determination to save her child and evolves into a national mission to improve healthcare access for patients and veterans alike. As a Doctor of Nursing Practice, cardiology specialist, healthcare advocate, educator, and policy leader, Monica has spent decades helping congenital heart disease patients navigate some of healthcare's most complex challenges. In this episode, she shares: • The realities of congenital heart disease • Why patients need lifelong specialized care • The transition from pediatric to adult cardiac medicine • Healthcare access barriers • Legislative advocacy and policy reform • Telehealth's role in modern medicine • Common VA disability claim mistakes • Practical advice for veterans navigating benefits This episode combines healthcare expertise, personal experience, and real-world solutions for patients, families, caregivers, and veterans. If you've ever struggled to navigate healthcare systems or wondered how advocacy changes lives, this conversation is for you. Key Takeaways ✓ Congenital heart disease requires lifelong management ✓ Access to specialized care remains a major challenge ✓ Telehealth can dramatically improve outcomes ✓ Veterans often underreport legitimate claims ✓ Documentation is critical for successful VA claims ✓ Advocacy can create real policy change Learn more about your ad choices. Visit megaphone.fm/adchoices
Podcast Family, in this episode we will focus on the “20-minute rule” for vacuum assisted vaginal delivery. This is an important aspect of neonatal safety and is a vital part of procedure documentation. Documentation for vacuum assisted vaginal delivery should include station at application, number of tractions, number of pop-offs and the total traction time and the vacuum trackable time (time from first application to delivery). This has historical roots as well as new data to validate it (March 2026). Listen in for details. 1. ACOG PB 219; 20202. Preuss E, Porto A, Sheiman V, Bitton M, Tovbin J, Kedem HI, Barzilay E. When to stop? A single center experience on vacuum-assisted deliveries. Eur J Obstet Gynecol Reprod Biol. 2026 Mar 25;320:114983. 3. Teng FY, Sayre JW. Vacuum Extraction: Does Duration Predict Scalp Injury?.Obstetrics and Gynecology. 1997. 4. Tsakiridis I, Giouleka S, Mamopoulos A, et al.Operative Vaginal Delivery: A Review of Four National Guidelines. Journal of Perinatal Medicine. 2020. 16% OFF TONA ACTIVE WEAR PROMO: https://tonaactive.com/discount/CHAPANOSPINOBG
In this episode of the Crazy Wisdom Podcast, host Stewart Alsop sits down with Larry Swanson, creator of the Knowledge Graph Insights Podcast, for their second conversation together. The two cover a wide range of interconnected topics, starting with a correction Larry makes about the true origin of the term "artificial intelligence," tracing it back to the 1956 Dartmouth Conference and its distinction from Norbert Wiener's cybernetics. From there, the conversation moves through the history and structure of knowledge graphs, ontologies, RDF (Resource Description Framework), and the W3C standards process, touching on concepts like the T-box, A-box, and C-box, as well as the 25th anniversary of the Semantic Web paper. Stewart and Larry also dig into the limitations of large language models — particularly around reasoning, confabulation, and what Larry describes as "cognitive surrender" — and why symbolic AI and knowledge engineering may hold answers that the neural network world hasn't fully embraced. The episode also ventures into consciousness, panpsychism, Michael Pollan's ideas, and Stewart's own hands-on experience vibe coding a personal chatbot to replace functionality he feels he's lost with recent changes to Claude. Larry's podcast can be found at kgi.fm.Timestamps00:00 - Stewart introduces Larry Swanson; Larry corrects the record on AI's origin, distinguishing it from Norbert Wiener's cybernetics at the 1956 Dartmouth conference.05:00 - Larry discusses interviewing semantic web paper coauthors on its 25th anniversary; RDF's hidden ubiquity compared to SIM cards powering everything invisibly.10:00 - Knowledge graphs explained through t-box terms, a-box assertions, and Dave McComb's c-box; IKEA's three-layer knowledge graph as a practical example.15:00 - Stewart connects metadata complexity to AI needs; faceted search explained as c-box attributes driving product filtering experiences.20:00 - RDF 1.2 reification standards discussed; W3C's rigorous recommendation process powering governments and enterprises worldwide through collaborative standards.25:00 - Cyc project examined as influential "successful failure"; Pat Hayes bringing description logic into semantic web; LLMs lacking true reasoning capability.30:00 - Epistemological fault lines between human and computer intelligence; cognitive surrender paper reveals no intelligence threshold protects against AI manipulation.35:00 - Stewart's Claude regression problem drives chatbot vibe coding quest; small language models and domain-specific approaches explored as alternatives.40:00 - Consciousness discussion through Michael Pollan's panpsychism lens; language versus cognition disconnect revealing LLMs as pure token-stitching without genuine thought.45:00 - Context graphs as purpose-built knowledge graphs for AI; Stewart's planning agents versus coding agents architecture and ground truth verification problem.50:00 - Docs-as-code versus code-as-docs paradigm shift; knowledge graphs as universal verifiers against validated facts; RDF 1.2 enabling provenance and degrees of certainty.55:00 - Jessica Talisman's Knowledge Graph Academy recommended for onboarding; kgi.fm podcast shared; knowledge representation community needs better abstraction for wider adoption.Key Insights1. The term "artificial intelligence" was not a marketing gimmick but was coined deliberately at the 1956 Dartmouth Conference to distinguish the work of John McCarthy from Norbert Wiener's cybernetics. The two camps represented genuinely different approaches, and the AI label was a form of intentional intellectual branding rather than empty promotion.2. The semantic web, often called the most successful failure in technology history, has quietly embedded itself everywhere despite never achieving its original vision. Technologies like RDF power metadata standards inside every Adobe product and form the invisible backbone of government systems, enterprise data infrastructure, and cultural heritage organizations worldwide.3. Knowledge graphs are best understood as an ontology combined with all the instances that populate it. The distinction between things and strings, popularized by Google in 2012, captures the core idea that knowledge representation is about concepts as distinct from the labels we give them.4. The t-box, a-box, and c-box framework offers a practical model for understanding knowledge architecture. The t-box holds terminology and concepts, the a-box holds assertions about specific instances, and the c-box manages the attributes, taxonomies, and controlled vocabularies that sit between them and enable things like faceted search.5. Large language models produce fluent, convincing output but lack genuine reasoning, epistemological grounding, or judgment. Research on cognitive surrender shows that even people who understand how LLMs work are still susceptible to being misled by their fluency, meaning intelligence and awareness offer no reliable protection against being deceived.6. The gap between language and cognition matters deeply when evaluating AI. Evidence from people with aphasia shows that thinking can occur without language, which suggests LLMs, being purely language-based systems, are missing a fundamental layer of cognition that cannot be recovered through more tokens or better training.7. Knowledge graphs and RDF-based representation are well suited to the problem of verification and grounding in AI systems. Rather than relying on vectorized embeddings of language, a knowledge graph can store validated, provenance-tracked facts with degrees of certainty, making it a natural foundation for building trustworthy AI applications.
This week's episode dives into one of the most powerful tools for motivating and engaging neurodivergent learners: project-based learning—but not the Pinterest-perfect kind! The conversation focused on how project-based approaches can be tailored specifically for kids with asynchronous development, executive function challenges, creative passions, and unique learning needs. Key Takeaways Projects should have visible finish lines and clear scopes—defining what "done" looks like helps neurodivergent learners experience success and confidence. Flexible timelines and checkpoints—rather than setting large, rigid deadlines, breaking projects into small chunks helps maintain motivation and accommodate fluctuating energy levels. Documentation can be creative—photos, voice notes, and video walkthroughs can serve as evidence of learning, supporting reflection without interrupting the learning process. Links and Resources from Today's Episode Thank you to our sponsors: CTC Math – Flexible, affordable math for the whole family! The Learner's Lab – Online community for families homeschooling outside-the-box learners! The Lab: An Online Community for Families Homeschooling Neurodivergent Kiddos The Homeschool Advantage: A Child-Focused Approach to Raising Lifelong Learners Raising Resilient Sons: A Boy Mom's Guide to Building a Strong, Confident, and Emotionally Intelligent Family The Anxiety Toolkit Sensory Strategy Toolkit | Quick Regulation Activities for Home Affirmation Cards for Anxious Kids Project Based Learning And Your Gifted Child: A Guide For Parents RLL #101: Project-Based Learning with Cindy West When Passions Turn Into Pathways | Rethinking Motivation and Learning for Neurodivergent Kids Interest-Led Homeschooling and Your Gifted Child Embracing Interest-Led Homeschooling with Lydia Rosado Homeschooling High School With Interest-Led Learning Interest-Led Learning In The Early Years: Preschool and Beyond Interest Led Homeschooling: Helping Your Child Find Their Interests Homeschooling Your Gifted Child With Interest-Led Learning Homeschooling Middle School Using Your Own Interest-Based Curriculum What's The Difference Between Interest-Led and Strength Based Learning? RLL 12: What About Relaxed and Interest-Led Homeschooling for Gifted Kids? | A Listener Question RLL 02 Caitlin Curley: Diving Down Rabbit Holes and Following Kids' Interests Creating Your Own Interest-Based Middle School Curriculum Why LEGO STEM Challenges Belong in Your Homeschool – Especially If You're Raising Neurodivergent Kids Beating Boredom Without Busy Work: Motivating Neurodivergent Learners at Home
In 1993, the Uffizi Gallery in Florence, Italy was damaged by a car bomb. But this story starts in the 16th century with painter Bartolomeo Manfredi, and reaches all the way to the 2000s with an extraordinary restoration project. Research: “600 fragments and one photograph. The restoration of Bartolomeo Manfredi’s “Card Players.” Scala Archives. May 23, 2023. https://scalarchives.com/600-fragments-and-one-photograph-the-restoration-of-bartolomeo-manfredis-card-players/#:~:text=The%20Georgofili%20bombing%20also%20left,to%20have%20been%20destroyed%20forever. Clough, Patricia. “Blast Tears Apart 400 Years of Italy’s Heritage.” The Independent. May 28, 1993. https://www.newspapers.com/image/718976357/?match=1&terms=uffizi Cowell, Alan. “Italians Try to Place Blame For Bomb Damage at Uffizi.” New York Times. May 29, 1993. https://www.nytimes.com/1993/05/29/world/italians-try-to-place-blame-for-bomb-damage-at-uffizi.html “Cupid Chastised.” Art Institute of Chicago. https://www.artic.edu/artworks/59847/cupid-chastised “Documentation of the damage from the 1993 bombing in Via dei Georgofili.” Uffizi Galleries. https://www.uffizi.it/en/artworks/documentation-damage-1993-bombing-georgofili Folkestad, William B. and Mark Miller. “Bomb Damages the Uffizi Gallery.” EBSCO. 2023. https://www.ebsco.com/research-starters/law/bomb-damages-uffizi-gallery Follain, John. “Push Comes to Shove at Italy’s Uffizi.” Miami Herald. March 21, 1993. https://www.newspapers.com/image/637973344/?match=1&terms=uffizi Gage, Frances. “Caravaggio’s Rumore: Fact, Fiction and Authority in Giovanni Baglione’s Lives of the Painters, Sculptors and Architects.” Past & Present. Volume 257, Issue Supplement_16, November 2022, Pages 111–140. https://doi.org/10.1093/pastj/gtac031 “History of the Uffizi Gallery.” https://www.visituffizi.org/museum/history/ Kimmelman, Michael. “Bombed Uffizi Begins Recovery.” Berkshire Eagle. June 20, 1993. https://www.newspapers.com/image/533051992/?match=1&terms=uffizi Moir, Alfred. “An Examination of Bartolomeo Manfredi's ‘Cupid Chastised.’” Art Institute of Chicago Museum Studies , Spring, 1985, Vol. 11, No. 2 (Spring, 1985), pp. 156-167. https://www.jstor.org/stable/4108732 Morselli, Raffaella. “Bartolomeo Manfredi and Pomarancio: Some New Documents.” The Burlington Magazine, Vol. 129, No. 1015 (Oct., 1987), pp. 666-668. https://www.jstor.org/stable/883135 Nicolson, Benedict. “Caravaggesques in Florence.” The Burlington Magazine. Sep., 1970, Vol. 112, No. 810 (Sep., 1970), pp. 636+639- 641. https://www.jstor.org/stable/876434 Pianigiani, Gaia. “Florence’s Answer to Mafia Violence: A Painting’s Loving Restoration.” New York Times. May 25, 2018. https://www.nytimes.com/2018/05/25/world/europe/uffizi-florence-mafia-card-player.html Robb, Peter. “M: The Man Who Became Caravaggio.” Henry Holt and Co. 2015. “Uffizi: on display two masterpieces damaged by the 1993 Georgofili mafia attack.” Uffizi Galleries. https://www.uffizi.it/en/events/georgofili-commemoration-2024 Wakin, Daniel J. “Prosecutor Joins Italy Bomb Probe.” Florence Morning News. May 16, 1993. https://www.newspapers.com/image/985131856/?match=1&terms=%22Maurizio%20Costanzo%22 “World: Europe Mafia bosses jailed for life.” BBC. June 6, 1998. http://news.bbc.co.uk/2/hi/europe/108127.stm See omnystudio.com/listener for privacy information.
© 2020-2026 Ivy Podcast Discovery LLC
