Talking about FHIR <br/><br/><a href="https://evestel.substack.com?utm_medium=podcast">evestel.substack.com</a>

Out of the FHIR Podcast
Claim This Podcastby Gene Vestel
Podcast Authority
Beta
Podcast Overview
Talking about FHIR <br/><br/><a href="https://evestel.substack.com?utm_medium=podcast">evestel.substack.com</a>
Language
🇺🇲
Publishing Since
4/23/2025
Unlock The Full Podcast Authority Score Report
See how your podcast performs across key metrics
Podcast Authority
Beta
Recommendations available
Unlock the full report to see detailed tips
Recommendations available
Unlock the full report to see detailed tips
Unlock comprehensive insights including:
- • YouTube presence analysis
- • Social media reach metrics
- • RSS compliance scoring
- • Podcast 2.0 features
- • Technical standards
Detailed Analytics
- Complete breakdown of all 19 authority metrics
- Personalized recommendations for each metric
- Industry benchmarks and comparisons
- Technical RSS feed analysis and compliance scoring
Growth Strategies
- Step-by-step action plans for improvement
- Quick wins to boost your score immediately
- Pro tips from successful podcasters
See how your show performs across every key metric
High authority scores make your podcast more attractive to industry leaders and influencers who want to appear on credible shows.
Sponsors look for podcasts with proven authority and engagement. Your score demonstrates your podcast's value to potential partners.
Understanding your strengths and weaknesses helps you make data-driven decisions to expand your listener base effectively.
1 verified contact email on file for Out of the FHIR Podcast
Pitch yourself as a guest, propose sponsorships, or reach out directly to the host.
Recent Episodes

June 12, 2026
Nurses need AI too, and how it needs to be deployed at scale to ease administrative burden.
<p><strong>Gene Vestel</strong> sits down with <strong>Michelle Skinner</strong>, Chief Clinical Executive at TeleTracking, to unpack the operational side of healthcare execution. Michelle is a nurse by background with an MBA who spent decades running emergency departments and trauma centers before moving into health-tech leadership.</p><p>In this episode, she breaks down how TeleTracking a rare, 35-year-old owner-operated pillar in a sea of PE-backed digital health firms is using computational twin technology to radically optimize hospital operations without breaking clinical workflows.</p><p>Listen now on YouTube, Spotify, and Apple Podcasts.</p><p>We discuss:</p><p>* <strong>The Reality of Hospital Patient Flow:</strong> Why emergency department boarding is a symptom of systemic operational gridlock, not an ER failure.</p><p>* <strong>Computational Twins in Action:</strong> How simulating real-time capacity scenario planning can drop a hospital’s length of stay by over a full day.</p><p>* <strong>The Nursing Cognitive Load Crisis:</strong> Why AI strategies must pivot from administrative data logging to keeping nurses at the bedside.</p><p>* <strong>The Business vs. Care Matrix:</strong> How having clinical leadership embedded directly within engineering teams alters how code is written.</p><p>* <strong>The Imperative of Rural Healthcare Access:</strong> Why urban-centric health models collapse when applied to regional communities.</p><p>My 3 Biggest Takeaways from This Conversation</p><p>1. Hospital crowding is a patient flow problem, not a capacity problem</p><p>When patients are held in emergency department hallways for days, the default reaction is often to blame ER throughput or demand more physical beds. The tactical reality is that ER boarding is a lagging symptom of poor downstream operational orchestration. When a hospital cannot cleanly coordinate transitions from the post-anesthesia care unit (PACU) to intensive care or general medical floors, the entire pipeline backs up. TeleTracking’s deployment of computational twin software builds a predictive digital replica of a facility’s entire capacity landscape, running scenario trade-offs 48 hours in advance. The result isn’t just arbitrary data tracking; it’s a systematic blueprint that has driven over a 50% reduction in ED holds while simultaneously allowing hospitals to scale up overall volume.</p><p>2. If technology doesn’t actively reduce a nurse’s cognitive load, it’s a failure</p><p>While ambient listening models have made incredible strides in reducing “pajama time” and burnout metrics for physicians, the wider health-tech ecosystem has largely ignored the operational burden placed on nursing staff. Nurses have been turned into administrative traffic controllers spending critical clinical hours manually tracking down bed availability, coordinating discharge paperwork, or calling radiology to check on exam slots. We must evaluate new technology platforms through a singular, hyper-focused product lens: Does this give clinical hours back to the patient, or does it add friction to the system?. If it doesn’t systematically strip administrative steps out of the clinical loop, it shouldn’t be built.</p><p>3. Engineering teams need immediate clinical guardrails</p><p>A distinct trap for tech-first companies entering healthcare is treating healthcare metrics as abstract, unfeeling datasets or lines of code. True product maturity occurs when engineering squads have an operational bridge to the clinical frontline. Having nurses embedded directly into development processes creates a permanent shift in engineering empathy. When developers understand that a minor database lag or a clunky workflow pattern directly delays a bed placement for a critical trauma patient, the quality of execution spikes. We must build software with a human-in-the-loop mentality, ensuring code serves the explicit, real-world workflow realities of active caregivers.</p><p>Where to find Michelle Skinner & TeleTracking:</p><p>* <strong>LinkedIn:</strong> <a target="_blank" href="https://www.linkedin.com/in/michelleskinner712/">Michelle Skinner</a></p><p>* <strong>Website:</strong> <a target="_blank" href="https://www.teletracking.com/">TeleTracking</a></p><p>If you found this operational breakdown valuable, consider subscribing to Out of the FHIR for weekly technical product leadership deep dives.</p> <br/><br/>This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit <a href="https://evestel.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_2">evestel.substack.com/subscribe</a>

June 1, 2026
Navigating the Shift to Bulk Data and AI
<p><strong>Ron Urwongse</strong>, co-founder of Defacto Health, and I sit down to break down the rapid shifts hitting CMS regulations, the transition from standard FHIR APIs to national bulk data datasets, and how agentic AI workflows are compressing engineering timelines from months to an afternoon.</p><p>Listen now on YouTube, Spotify, and Apple Podcasts.</p><p>We discuss:</p><p>* <strong>The Bulk Data Pivot:</strong> Why CMS is expanding beyond endpoint APIs into massive bulk NDJSON files for Medicare Advantage plans.</p><p>* <strong>The National Provider Directory Ecosystem:</strong> A technical audit of the new data release, where it shines, and where the logical models are still failing.</p><p>* <strong>AI as an Engineering Accelerator:</strong> How teams are using agentic workflows (like Claude Code) to build production-ready validation engines overnight.</p><p>* <strong>Smart Scheduling Links:</strong> The inevitable roadmap toward universal, consumer-centric open appointment booking.</p><p>* <strong>The CMS Feedback Loop:</strong> Why the newly established CMS Health Tech Ecosystem Slack channel is radically altering how regulations are refined in real time.</p><p>My 3 Biggest Takeaways</p><p>1. Compliance cycles have compressed from six months to a single weekend</p><p>In the legacy enterprise playbook, updating a platform to conform with newly dropped technical implementation guides took a quarter or more of roadmap planning. Today, that layout is dead. Ron noted that when CMS dropped updated technical guidance on a Friday afternoon, multiple forward-thinking payers had already fully conformed by Monday morning.</p><p>The differentiator isn’t engineering headcount; it’s the shift toward AI accelerators. If your senior architects aren’t actively feeding CMS Implementation Guides into tools like Claude Code to interpret, write, and deploy schemas, you are building an operational bottleneck.</p><p>2. We are transitioning from simple Master Data Management to Federated Graphs</p><p>The industry has long clamored for CMS to run a centralized database as a mastered system of record. Instead, the tactical reality looks much more like a federated graph across hundreds of independent nodes. CMS isn’t attempting top-down data cleansing; they are supplying the network scaffolding to link provider organizations, practitioners, endpoints, and digital footprints. Payers must now prioritize internal accuracy auditing because upcoming mandates like the Real Health Providers Act will require plans to publicly score and publish the validity of their directory data.</p><p>3. Open scheduling is the ultimate bottleneck for value-based care</p><p>Up to 75% of open care gaps remain unfilled simply because of the high friction involved in patient engagement such as transcribing an identical medical history onto a 40-page clipboard during an intake cycle. Universalizing lightweight specifications like <strong>Smart Scheduling Links</strong> originally built to aggregate vaccine availability during COVID will allow insurance directories to natively embed real-time booking slots. The monetization model still needs guardrails to protect providers from high platform fees and patient acquisition gaming, but opening up EHR scheduling data to the wider ecosystem is an absolute necessity to drive actual consumerism in healthcare.</p><p>Deep Dive: Auditing the National Provider Directory</p><p>The launch of the National Provider Directory marked a major milestone for healthcare data liquidity, but looking under the hood reveals clear technical hurdles that the developer community is currently solving.</p><p> [ Practitioner ] │ Is associated with ▼ [ Provider Organization ] ── Publishes ──► [ Bulk NDJSON Dataset ] │ │ Resolves endpoint to │ Contains ▼ ▼ [ Patient-Centric Endpoint ] ◄── Audited by ── [ AINPI.dev Engine ] </p><p>The Architectural Gaps in the NPD Release</p><p>To test the real-world utility of the new data, Gene imported the entire publicly available directory into an open-source tool built over a weekend to evaluate and audit conformance: <a target="_blank" href="https://ainpi.dev/"><strong>AINPI.dev</strong></a>. The audit highlighted several distinct areas where the logical models require iteration:</p><p>* <strong>Endpoint Association Confusion:</strong> There remains an ongoing architectural debate within CMS working groups regarding where endpoints should sit logically. Attaching a FHIR connection endpoint directly to an individual practitioner creates massive, unmanageable data duplication. The correct semantic approach maps endpoints strictly to the Provider Organization, which then establishes relationships down to the underlying practitioners.</p><p>* <strong>The Specialty Taxonomy Mess:</strong> There is still no clean, unified consensus on processing specialty codes. Payers are left navigating multiple conflicting sources of truth published across PECOS, NPPES, and specialized CMS charts, leading to distinct fragmentation in search results.</p><p>* <strong>Missing Endpoints:</strong> The front door to patient-directed data access relies on clean endpoint visibility. Currently, a vast percentage of active provider organizations feature zero mapped digital endpoints, making true interoperability a fragmented experience depending entirely on where a patient lives.</p><p>Where to find Ron Urwongse & Defacto Health:</p><p>* <strong>LinkedIn:</strong> <a target="_blank" href="https://www.linkedin.com/in/rurwongse/">Ron Urwongse</a></p><p>* <strong>Website:</strong> <a target="_blank" href="https://defacto.health/">De facto Health</a></p><p>Referenced in the show:</p><p>* <strong>The Open-Source Audit Tool:</strong> <a target="_blank" href="https://ainpi.dev/">AINPI.dev</a></p><p>* <strong>The Agentic Healthcare Assistant Concept:</strong> <a target="_blank" href="https://healthclaw.io/">HealthClaw.io</a></p><p>* <strong>The Technical Repository Framework:</strong> <a target="_blank" href="https://github.com/aks129">Smart Health Connect</a></p><p>* <strong>Gene’s AI Builder Cohort:</strong> <a target="_blank" href="https://fhiriq.com/workshop">FHIRIQ Workshop</a></p><p>If you found this breakdown valuable, consider subscribing to Out of the FHIR for weekly deep dives into technical health-tech leadership.</p> <br/><br/>This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit <a href="https://evestel.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_2">evestel.substack.com/subscribe</a>

May 28, 2026
State of Prior Authorization with Mark Fleming (Availity)
<p><strong>Mark Fleming</strong> is Senior Director of Prior Authorization, Interoperability, and Portal Solutions at Availity, a leading healthcare clearinghouse and data network. With over 25 years of experience in healthcare IT and revenue cycle management starting back when Epic had only 500 employees Mark is one of the industry’s foremost experts on modernizing the administrative friction between payers and providers.</p><p>Listen on <a target="_blank" href="https://www.youtube.com/@OutoftheFHIRPodcast">YouTube</a>, <a target="_blank" href="https://open.spotify.com/show/6GBZT7KA1Ug8xMZ4l5LThU?si=8d077e7044d84644">Spotify</a>, and <a target="_blank" href="https://podcasts.apple.com/us/podcast/out-of-the-fhir-podcast/id1822845248">Apple Podcasts</a>.</p><p>We discuss:</p><p>* Why a staggering two-thirds of prior authorizations are still stuck on manual faxes, phone calls, and isolated web portals.</p><p>* The massive structural shift behind the <strong>CMS-0057 mandate</strong> and how standardized FHIR APIs will force standard authorization timelines from weeks down to a strict 72-hour window.</p><p>* Moving from isolated transactions to real-time clinical transparency—letting providers query exact documentation and medical policy rules directly inside their EHR at the point of care.</p><p>* How digitizing clinical data allows modern AI platforms to parse requirements instantly, letting patients schedule sensitive procedures within days rather than waiting for weeks.</p><p>* The daunting scaling bottleneck of point-to-point connections, why the average health system routinely deals with 40 to 80 distinct payers each month, and why the industry must look toward centralized networks over customized developer builds.</p><p>My biggest takeaways from this conversation:</p><p>* <strong>The Stagnant State of Healthcare Administrative Friction</strong>: Despite immense technological progress in other areas of our daily lives, healthcare transactions remain stubbornly legacy. Currently, only about a third of prior authorization transactions utilize automated electronic X12 standards; the remaining two-thirds are split evenly between manual payer portals and decades-old faxes and phone calls.</p><p>* <strong>The Clinical Shift of CMS-0057</strong>: The incoming federal FHIR API standards mandate a massive operational pivot. Historically, providers gathered documentation and “threw it over the fence,” resulting in back-and-forth rejections because of highly specific medical policies. By introducing Coverage Requirements Discovery (CRD) and Documentation Templates and Rules (DTR) directly into the point-of-care workflow, providers will instantly know exactly what clinical information is required before a submission occurs.</p><p>* <strong>Real-Time Automated Care Approvals</strong>: Integrating real-time bi-directional FHIR streams with clinical decision platforms paves the way for immediate automated processing. By utilizing modern AI architectures to evaluate digital clinical datasets against explicit payer criteria, current production implementations (like Availity’s authAI tool) are already approving up to 78% of initial submissions within 60 seconds. This eliminates the safety buffer where providers schedule slots weeks out just to wait for a manual determination.</p><p>* <strong>The Network Scalability Challenge</strong>: Point-to-point custom integrations simply do not scale for provider ecosystems. Because an average mid-sized health system must route documentation to 40 distinct payers every single month and larger ones route to up to 80 building out separate point-to-point lines of communication is logistically unfeasible. Centralized networks must step in to act as translation and trust clearinghouses to standardize operations between varying EHR versions and complex payer architectures.</p><p>* <strong>The Cost-Burden Equivalence</strong>: Transitioning away from legacy administrative manual procedures can remove immense financial waste from the healthcare system. Current metrics show that a manual submission for a prior authorization costs an average of $9.00 per submission, whereas an fully electronic transaction utilizing standardized networks drops that cost to just $0.25.</p><p>Where to find Mark Fleming:</p><p>* <strong>LinkedIn</strong>: <a target="_blank" href="https://www.linkedin.com/in/markjfleming/">Mark Fleming on LinkedIn</a></p><p>* <strong>Website</strong>: <a target="_blank" href="https://www.availity.com/">Availity Official Portal</a></p><p>Referenced in the show:</p><p>* <strong>CMS-0057 (Interoperability and Prior Authorization Final Rule)</strong>: <a target="_blank" href="https://www.cms.gov/priorities/burden-reduction/overview/interoperability/policies-regulations/cms-interoperability-prior-authorization-final-rule-cms-0057-f">CMS Official Summary</a></p><p>* <strong>CMS-0062 (Proposed Rule Expanding FHIR to Medications)</strong>: <a target="_blank" href="https://www.cms.gov/priorities/burden-reduction/overview/interoperability/policies-regulations/cms-interoperability-standards-prior-authorization-drugs-proposed-rule-cms-0062-p">Federal Register Rule Details</a></p><p>* <strong>HL7 Da Vinci Project & Burden Reduction Group</strong>: <a target="_blank" href="https://build.fhir.org/ig/HL7/davinci-crd/en/burden.html">Da Vinci Framework Overview</a></p><p>* <strong>Trebuchet Project</strong>: <a target="_blank" href="https://confluence.hl7.org/spaces/DVP/pages/234423487/Da+Vinci+Trebuchet+FHIR+Pilots">Trebuchet Connectivity Infrastructure Initiative</a></p><p>* <strong>HealthClaw</strong>: <a target="_blank" href="https://github.com/aks129/HealthClawGuardrails">Open Source Fire Data Quality Assessment Layer</a></p><p>* <strong>Epic Systems</strong>: <a target="_blank" href="https://www.epic.com/">Epic Corporate Page</a></p><p>* <strong>Athenahealth & Humana Joint Case Study</strong>: <a target="_blank" href="https://www.athenahealth.com/">Reference Implementation Learnings</a></p><p>* <strong>Medical Group Management Association (MGMA) Survey</strong>: <a target="_blank" href="https://www.mgma.com/">Prior Authorization Burden Metric Report</a></p><p>* <strong>TEFCA (Trusted Exchange Framework and Common Agreement)</strong>: <a target="_blank" href="https://www.healthit.gov/">HealthIT.gov TEFCA Details</a></p><p>* <strong>FAST (FHIR At Scale Taskforce) Security Initiative</strong>: <a target="_blank" href="https://www.healthit.gov/">ONC FAST Security and Identity Working Group</a></p> <br/><br/>This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit <a href="https://evestel.substack.com/subscribe?utm_medium=podcast&utm_campaign=CTA_2">evestel.substack.com/subscribe</a>
30 total episodes available
Recent guests on Out of the FHIR Podcast
Guests from recent episodes — sign up to see every guest that has ever appeared on this show.
Cody Ebberson
Guest
Darren Devitt
Guest
Grahame Grieve
Guest
Similar Podcasts
Discover related shows you might enjoy
Deep-dive analytics for Out of the FHIR Podcast
Frequently asked questions
Have a different question and can't find the answer you're looking for? Reach out to our support team by sending us an email and we'll get back to you as soon as we can.
- What is Out of the FHIR Podcast?
- How often does this podcast release new episodes?
This podcast updates daily.
- Where can I listen to this podcast?
This podcast is available on 4 platforms including Apple Podcasts, Spotify, and more. You can also use the RSS feed directly.
- Does this podcast accept guests?
Yes, this podcast regularly features guests.
Legal Disclaimer
Pod Engine is not affiliated with, endorsed by, or officially connected with any of the podcasts displayed on this platform. We operate independently as a podcast discovery and analytics service.
All podcast artwork, thumbnails, and content displayed on this page are the property of their respective owners and are protected by applicable copyright laws. This includes, but is not limited to, podcast cover art, episode artwork, show descriptions, episode titles, transcripts, audio snippets, and any other content originating from the podcast creators or their licensors.
We display this content under fair use principles and/or implied license for the purpose of podcast discovery, information, and commentary. We make no claim of ownership over any podcast content, artwork, or related materials shown on this platform. All trademarks, service marks, and trade names are the property of their respective owners.
While we strive to ensure all content usage is properly authorized, if you are a rights holder and believe your content is being used inappropriately or without proper authorization, please contact us immediately at hey@podengine.ai for prompt review and appropriate action, which may include content removal or proper attribution.
By accessing and using this platform, you acknowledge and agree to respect all applicable copyright laws and intellectual property rights of content owners. Any unauthorized reproduction, distribution, or commercial use of the content displayed on this platform is strictly prohibited.
