Vladimir Kouznetsov

Continuing with our FHIR Open Source Project series we have released a FHIR R4 #EMR CDR system to showcase how FHIR resources work in real clinical workflows and how they map to actual healthcare scenarios. More releases coming soon!!!!

2

FHIR is shaping the future of healthcare data—and open source is powering it. 🔋 Rob Ferguson walks through how to secure HAPI FHIR data at rest, with practical steps any developer can follow. If you're working with patient data, this is worth your time. Check it out 👇 https://bit.ly/3SGmEOM

1

Patient satisfaction is critical for any healthcare facility and one of the biggest driving factors is a smooth and timely experience… Long wait times and inefficient hand offs not only impact patient satisfaction but also a facility’s capacity. Optimizing and monitoring patient flow with mindzie’s Process Flow command center is transforming the way healthcare providers operate without having to break the bank when compared to traditional legacy healthcare command center systems. Learn more at www.mindzie.com

2

1 Comment

The CMS ACCESS Model FHIR Implementation Guide is Up. My co-founder Hadi Javeed sat down with me last night and we pulled up the specs. Four API operations, seven subscription event types, twelve FHIR profiles. More impressive than that- he created an interactive sandbox for builders!! We mapped each operation against the clinical tracks, walked through the payment model line by line, and sketched out how we would integrate this into our software infrastructure. Then we wrote it up on The Techy Surgeon! I still believe the most compelling component to this model is the partnership architecture. An MSK practice collecting $180 per care episode while forgoing downstream surgical revenue of FFS billing is thin. Impractical as a standalone play. But an MSK practice or PT group that functions as the specialty care node in a broader value-based network -- receiving referrals from ACOs, coordinating with rehab partners for triage and PROM collection, with co-management payments flowing to the upstream entities that feed the pipeline and expanding their tech enabled capabilities -- that's a different model entirely. The ACCESS Model doesn't reward isolation. It rewards coordination. And the participants who build the network around them will be the ones who make the economics work. We're in the MSK and Behavioral Health tracks. The MSK improvement-only design with early success reporting at Day 185 maps directly to what we've built at RevelAi Health -- PROM trajectory monitoring, clinically informed AI powered patient engagement, distributed care coordination, partner data exchange. And the BH track opens an adjacent market where the same partnership-dependent architecture applies and the need for coordination infrastructure is even more acute. And yes, without AI -- it becomes impossible for this program to work for the ACCESS participant. Will this program actually enhance access? That remains to be seen, but we're determined to try. The full analysis and sandbox on The Techy Surgeon (link in comments). If you're an ACO, PT group, or specialty practice exploring ACCESS and want to talk partnership structures: hello@revelaihealth.com or visit us at the MSK ACCESS website (link in comments) #ACCESSModel #CMS #ValueBasedCare #FHIR #MSK #BehavioralHealth #DigitalHealth #CareCoordination

40

7 Comments

Case Study: From Fragmented Systems to a Unified EHR—How DIBS Technologies Helped One Clinic Regain Control The Challenge: A growing multi-location clinic was juggling multiple software systems for patient records, scheduling, billing, and lab integration. The result? 📉 Disconnected workflows 📉 Repetitive data entry 📉 Frustrated staff—and even more frustrated patients They needed a solution that wasn’t just “digital”—they needed a system that worked together. The Solution: That’s when they turned to DIBS Technologies to build a custom Electronic Health Record (EHR) application tailored to their real-world operations. What DIBS Delivered: 🧩 Centralized EHR System – All patient records, lab results, imaging, and prescriptions in one secure place 🔗 Integrated Workflows – EHR connected to billing, scheduling, and pharmacy systems 📊 Custom Dashboards & Reporting – Real-time insights for both clinical and administrative teams 🔐 HIPAA-Compliant Architecture – Built from the ground up for privacy, audit control, and secure access 📱 Patient Access Portal – Empowering patients to view records, communicate with providers, and manage care remotely ⚙️ Built Around their Workflow – Not generic software, but a tool designed to fit their process The Impact: ✔ 3 systems consolidated into one seamless platform ✔ 55% improvement in documentation speed ✔ 2x faster access to patient records across locations ✔ Fewer administrative errors and stronger data accuracy ✔ Increased staff satisfaction—and improved patient outcomes Why it worked: Because DIBS Technologies doesn’t build just software. We build bespoke EHR platforms that fit the way your clinic actually operates—while ensuring regulatory compliance and data security at every step of the way. 💡 When your EHR system fits your practice, everything else runs smoother—care, compliance, and communication. 📞 Is your current EHR slowing you down—or helping you grow? Let’s build one that truly works for you. #DIBSTechnologies #EHRDevelopment #CustomSoftware #HealthcareIT #DigitalHealth #HIPAACompliance #PatientCare #HealthTech #ClinicOperations #MedicalSoftware #HealthcareInnovation

1

Stopping paying "hostage fees" to your legacy EMR vendors. 🛑 Every time a healthcare network acquires a new practice, a hidden tax gets levied. You migrate the active patients to your corporate Epic or Cerner instance. But what happens to the 7 to 10 years of historical clinical data, dead CPOE interfaces, and archived charts required by federal compliance? Usually, one of two things: You keep paying staggering annual maintenance fees just to keep the old legacy server on life support. You pay an astronomical, six-figure extraction fee to the sunsetted vendor just to get your own data back in a messy, unstructured format. Both options are a failure of data architecture. When we engineered the Axiom Vault, we looked at this fractured plumbing and decided to treat legacy data as an asset, not an expensive liability. You don’t need a massive, bloated enterprise software contract to stay compliant. You need a clean, containerized, repeatable blueprint: Production-Grade Infrastructure: A secure, Windows-server-backed, MySQL and Mirth Connect core environment. Modern Interoperability: Automated data-mapping pipelines that ingest chaotic legacy HL7 v2 segments or raw database dumps and morph them seamlessly into clean, compliant FHIR-native APIs. The Command Center: A sleek, glassmorphic UI dashboard that gives your compliance and IT teams instant, high-end visibility into historical archives without the technical debt. Interoperability shouldn’t be a bespoke, hand-crafted money pit. It should be standardized, repeatable, and elegant. We are currently looking for two regional healthcare networks or multi-site provider groups to run a 30-day, zero-risk Pilot Architecture Review. We spin up the Vault on a secure test environment, map a subset of your legacy data, and hand you a complete compliance audit report. If you're ready to liquidate your technical debt and take back control of your data, drop a comment below or send me a DM. Let’s build. #HealthcareIT #HealthIT #FHIR #HL7 #MirthConnect #Interoperability #AxiomFlow

1

What does it really mean for AI to "think" like an experienced human adjuster in healthcare?   In their latest blog, Mahesh Shinde, VP of Architecture and Integration Strategy, and Vinay Nadig, Chief Strategy Officer at Simplify Healthcare, apply the concept of Context Graphs for Healthcare Payers — and why they're becoming the foundation of transparent, explainable, and auditable AI for healthcare payers.   From prior authorization to claims adjudication to member self-service, AI agents are only as good as the context they operate on. Mahesh and Vinay explain Context Layer and Context Graph, and why payers need them to move from systems-of-record to systems-of-why.   As regulatory pressure mounts — CMS interoperability mandates, California SB 1120, and rising scrutiny of AI-mediated decisions — the ability to explain and audit every AI decision isn't just good practice. It's becoming a compliance imperative.   Read the full blog to understand how Context Graphs can transform payer operations: https://lnkd.in/gbrUNdX6 Read the blog on Medium: https://lnkd.in/gUSWuacZ   #SimplifyHealthcare #AgenticAI #HealthcarePayers #ContextGraphs #ExplainableAI #PriorAuthorization #ClaimsAdjudication #HealthcareAI #AuditableAI

37

From Telegram Command to RCM Analysis: Introducing OpenClaw. We can make accessing complex RCM and clinical insights as easy as sending a text. Our Telegram Bot, OpenClaw, allows you to query the local system with simple commands like "billing review for Maria Santos" and get an instant, structured summary. The conversational layer runs on a local LLM via Ollama. What’s Next for Us? We’re hardening the platform with Rate Limits, better Auth, and exploring Tailscale for secure remote access. If your organization is ready to move beyond cloud-dependent AI and embrace a truly private, auditable, and local platform, let's connect.

1

Payers aren't playing fair in 2026. They're using hyper-specialized AI to find every reason to deny your claims. If you're showing up to that fight with a generic chatbot, you’ve already lost. We see it constantly: teams trying to use standard LLMs to appeal denials. While ChatGPT is a great assistant for drafting letters, it doesn't understand the specific logic of a Blue Cross surgical policy or clinical ICD-10 nuances. Generic AI treats every prompt the same: payers don’t. RCM success today requires tools built for the industry, not general conversation. Specialized automation identifies the "why" behind a denial and matches it with exact evidence. At Consulting & Media, we don't just give recommendations; we implement the specialized workflows that move the needle on your DNFB and clean claim rates. Keep in mind: even the best AI requires manual homework. Reviewing outputs and validating claims is non-negotiable for professional, human-grade results. For automation that actually wins against payer AI, check out: https://lnkd.in/e-zWzUTp Let’s stop losing revenue to "smart" payer denials. cc: Marcia Leighton (https://lnkd.in/eV7z5yk3)

1

🧠 AI is quietly fixing one of healthcare’s biggest headaches — EMR workflows and prior authorizations. Instead of endless forms and back-and-forth with payers, AI now: • Pulls data from EMRs automatically • Predicts if a procedure needs pre-auth • Submits and tracks approvals in real time The result? Faster care, fewer denials, and less admin fatigue. For MedTech, this is huge — it’s where innovation meets access. The same AI powering diagnostics can now streamline the workflows that get patients treated faster. 💡 AI isn’t just transforming care — it’s transforming how care gets delivered. #MedTech #AIinHealthcare #HealthIT #EMR #PriorAuthorization #DigitalHealth #HealthcareInnovation #Automation #FutureOfHealthcare

5

PEV agents create auditable AI workflows for documentation, prior auth, RCM, and RPM, integrating with EHR/FHIR, HL7 v2, SMART on FHIR, and payer APIs.

1

Too often, healthcare payers try to automate broken or outdated workflows and process that end up with systems that move faster but solve the wrong problems. That is why successful system implementations start with alignment. When business and IT teams map processes together, they can identify what to fix, what to automate, and how to make systems truly work for the organization. Our new executive white paper, From Disconnect to Delivery, shows how to: ✅ Use process mapping to bridge the business–IT divide ✅ Prioritize automation that delivers measurable impact ✅ Build systems that support real operational efficiency Get your copy: https://lnkd.in/eUETsTzY #HealthcarePayers #SystemImplementation #BusinessITAlignment #Automation #HealthcareTechnology

14

The HITECH Act (2009) reshaped digital health in the U.S. Before HITECH, hospital EHR adoption was only ~10–20%. Today, it’s above 96%. What drove this massive shift: • USD 30B in incentives to adopt certified EHRs. • Meaningful Use standards to ensure better care, not just digital paperwork. • Penalties for staying non-digital. • Stronger HIPAA rules for data privacy and breach reporting. • A national push for interoperability through HIEs. • ONC empowered to set standards and certify systems. • Workforce programs to build health IT talent. • Funding that accelerated innovation across the ecosystem.  With India’s hospital EHR adoption still around ~35%, is it time for a similar nationwide push? #DigitalHealth #HealthIT #HITECH #EHR #Interoperability #HealthcareInnovation #HealthTech #MeaningfulUse #ONC #HIPAA #HealthTransformation

11

1 Comment

FHIR-based electronic Prior Authorization (ePA) offers far more than regulatory compliance. When implemented with #interoperability in mind, it can streamline workflows, reduce administrative burden, and improve care coordination across the healthcare system. But the key to realizing those benefits is real-world #testing, not just pilots or one-off validations. Testing platforms like FHIRplace simulate real environments to uncover integration gaps early, helping #providers, #payers, and #healthIT developers launch with confidence and scale effectively. ✅ Faster decisions ✅ Fewer claim denials ✅ Better patient outcomes ✅ Stronger system performance The future of #priorauthorization depends on making real-world #FHIR interoperability the standard, not the exception. Explore how real-world testing drives better #ePA outcomes: https://cstu.io/0d9467

2

Discover the power of Centaur Data Connectors in our latest blog! 🚀 Say goodbye to custom pipelines and effortlessly integrate complex healthcare data for seamless processing. Our connectors are purpose-built for the healthcare industry, tackling its unique challenges with precision and ease. 🩺 #HealthcareInnovation #DataIntegration #CentaurDataConnectors #HealthChain #Centaur

25

FHIR R4 looks clean in documentation. In production, it’s a different conversation. Here’s what nobody tells you about FHIR integration when you’re building clinical AI at scale: 1. Resource profiles vary by EHR vendor. An Observation resource from Epic carries different extensions than one from Cerner. Your normalisation layer needs to handle both without losing clinical meaning. 2. Subscription-based real-time feeds are still inconsistent. Some vendors support websockets. Others push to webhooks with variable latency. Your event architecture needs to absorb this variance. 3. Terminology mapping between SNOMED, LOINC, ICD-10, and proprietary codes is a full workstream. Not a lookup table. A workstream. With clinical validation at every step. We’ve integrated with multiple EHR systems across different health systems. The architecture patterns are proven. The edge cases are documented. Comment PIPELINE for our FHIR integration architecture brief and I’ll DM it to you.

7

2 Comments

Nursing Home Ownership Changes Hit Record Highs in 2025 While celebrating a small milestone at mimilabs (1K SQL runs per week! 🎉), I decided to stress-test our system with one of the trickier healthcare datasets: facility ownership data. The Centers for Medicare & Medicaid Services collects ownership information for nursing homes, but despite its importance, the dataset is notoriously difficult to work with—lots of noise and a complex structure. I hadn't touched it in a while for these reasons. So I asked mimibot if it could analyze M&A activity in the SNF market. And it delivered this beautiful chart. The findings are striking: Ownership changes remained relatively stable from February 2024 through December 2024, ranging from just 5 to 21 facilities per month. December 2024 hit the lowest point with only 8 facilities changing hands. Then everything changed. Starting in January 2025, the numbers began climbing: 19 facilities, then 43 in February, 37 in May. By June 2025, we hit a record peak of 89 facilities changing ownership in a single month—more than 11x the December low. The elevated activity has continued through September 2025 with 72 facilities. What's driving this surge? What are you hearing about the nursing home market? I'd love to hear your perspectives on what's driving these ownership changes.

18

11 Comments

Some of the most interesting conversations around payer data infrastructure are happening in California right now. But the questions being asked there, such as how to ensure encounter data integrity, how to enable cross-sector data exchange, and how to make clinical and claims data operationally usable, are the ones that health plans across the country are working through. Our own Sue Riddell will be attending California Association of Health Plans Strengthening Data Infrastructure seminar next week. If you’ll be there and would like to connect, reach out to Sue.

20

❗Here’s the uncomfortable truth:  𝐌𝐨𝐬𝐭 𝐄𝐇𝐑 𝐢𝐧𝐭𝐞𝐠𝐫𝐚𝐭𝐢𝐨𝐧𝐬 𝐟𝐚𝐢𝐥. Not because the tech isn’t there. HL7, FHIR, APIs — they all exist. They fail because teams treat integration like a checkbox project instead of a clinical workflow transformation. We’ve seen it happen: 🔺 Data comes through, but providers can’t use it because it doesn’t fit their workflow. 🔺 APIs are connected, but no one thought about patient context, so notes get buried. 🔺 Integrations go live, but without monitoring, they silently break — and no one knows until a patient gets hurt. 👉 The truth is: EHR integration isn’t about moving data. It’s about 𝗺𝗮𝗸𝗶𝗻𝗴 𝘁𝗵𝗮𝘁 𝗱𝗮𝘁𝗮 𝘂𝘀𝗮𝗯𝗹𝗲, 𝗿𝗲𝗹𝗶𝗮𝗯𝗹𝗲, 𝗮𝗻𝗱 𝘃𝗮𝗹𝘂𝗮𝗯𝗹𝗲 𝗮𝘁 𝘁𝗵𝗲 𝗽𝗼𝗶𝗻𝘁 𝗼𝗳 𝗰𝗮𝗿𝗲. At Vervelo, we’ve turned failing integrations into success stories by focusing on three things: 1. 𝗦𝘁𝗮𝗿𝘁 𝘄𝗶𝘁𝗵 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄, 𝗻𝗼𝘁 𝘁𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆. How will clinicians actually use this data? 2. 𝗗𝗲𝘀𝗶𝗴𝗻 𝗳𝗼𝗿 𝘀𝗰𝗮𝗹𝗲. Today’s integration with Epic may need to expand to Cerner, athena, or eCW tomorrow. 3. 𝗗𝗼𝗻’𝘁 “𝘀𝗲𝘁 𝗶𝘁 𝗮𝗻𝗱 𝗳𝗼𝗿𝗴𝗲𝘁 𝗶𝘁.” Ongoing monitoring and support keep data flowing when regulations and APIs change. The irony? Everyone talks about interoperability, but very few do it right. 💡 If you’re leading a healthtech product or provider system, here’s a question worth asking your team today: 𝐴𝑟𝑒 𝑤𝑒 𝑖𝑛𝑡𝑒𝑔𝑟𝑎𝑡𝑖𝑛𝑔 𝑑𝑎𝑡𝑎… 𝑜𝑟 𝑎𝑟𝑒 𝑤𝑒 𝑡𝑟𝑢𝑙𝑦 𝑒𝑛𝑎𝑏𝑙𝑖𝑛𝑔 𝑏𝑒𝑡𝑡𝑒𝑟 𝑐𝑎𝑟𝑒? #EHRIntegration #Interoperability #HealthcareIT #DigitalHealth #HealthcareTechnology #HealthTech #DigitalHealth #HealthIT #HealthcareInnovation #FHIR #HL7 #EMRIntegration #HealthcareData #ClinicalDataExchange #ConnectedCare

3