Vishalgiri Goswami

Really useful lens on MCP, A2A, ACP, and ANP. The layered view makes it so much easier to understand where each protocol fits in building agent-driven system

7

1 Comment

I’ve been working with REST APIs for quite some time, and over the years, I’ve seen how APIs have evolved far beyond basic design principles — incorporating new capabilities that make them truly distributed, scalable, and integral to modern architectures. Hence in my latest article, I’ve shared some practical insights on how to approach API discovery in modern distributed architectures. It covers real-world practices around centralizing API metadata, automating registration through CI/CD, and integrating observability for live visibility. The goal is to help teams build scalable, secure, and developer-friendly API ecosystems that actually work in production. https://lnkd.in/dZnK-rri

19

2 Comments

Architect Guidance → Pragmatic Design → Real Business Impact Architecture creates value when it connects strategy to everyday team decisions. Pragmatic design is that bridge—turning organizational goals into solutions customers actually feel. Architect guidance aligns squads around shared outcomes: faster time to market, reliable platforms, secure data, and seamless user journeys. It prevents siloed optimization and replaces it with reusable capabilities, common models, and clear guardrails. Success is measured not by diagrams but by results—fewer customer frustrations, simpler operations, and predictable delivery. Pragmatic design balances today’s needs with tomorrow’s growth: “just enough” architecture, managed risk, and incremental modernization. When architects collaborate closely with product and engineering, teams solve the right problems at the right time. The outcome is trust—trust from users, from the business, and from the organization investing in the future. Architecture is not control; it is enablement. Pragmatic design is not about building the perfect system; it is about building the right system at the right time for real people and real business needs. #PragmaticDesign #SoftwareArchitecture #DigitalTransformation #HealthcareIT #ProductEngineering #CustomerExperience #Leadership

5

The hardest part of legacy EMR modernization isn't technical Most CTOs think legacy migration is a technical challenge. Migrate databases. Modernize APIs. Update infrastructure. That's the easy part. 🚫 The hard part? Convincing a 55-year-old physician who's used your system for 15 years that the "new improved" interface is actually better. Here's a real conversation from last month: Physician: "Where did the patient chart go?" Us: "It's in this collapsible sidebar. Cleaner design." Physician: "The old system kept it visible always. I need to SEE my patient while documenting." Us: "You can expand it anytime." Physician: "I don't want to expand. I want it THERE. Always visible." We thought we were improving the design. We were removing her cognitive safety net. 🔍 The insight: Legacy systems aren't just software. They're 15 years of learned muscle memory, mental models, and coping strategies. 👉 When you "modernize," you're asking users to: 🚩 Unlearn 15 years of habits 🚩 Trust your judgment over their experience 🚩 Rebuild their cognitive shortcuts 🚩 Risk mistakes during transition No wonder adoption fails. What successful legacy migration looks like: Phase 1: Technical infrastructure Modernize backend, APIs, databases without touching interface Phase 2: Invisible improvements Add capabilities users requested without changing what works Phase 3: Progressive enhancement Introduce modern patterns gradually where they solve actual problems Phase 4: Optional modernization Let users choose modern vs classic interface elements 🚨 The controversial approach: Sometimes the best legacy modernization preserves the interface. Update what's underneath. Keep what users trust on top. Example: A client wanted to modernize 20-year-old scheduling system. Their plan: Complete redesign. Modern interface. "Better UX." User reaction: Massive resistance. Training burden. Adoption failure. Our approach: ✅ Keep scheduling interface exactly the same ✅ Modernize backend to enable features users wanted ✅ Add new capabilities as optional enhancements ✅ Let users gradually adopt modern features The Result: 💫 Zero learning curve 💫 Immediate adoption of new capabilities 💫 Users happy with "improvements" not "changes" 💫 Technical modernization successful The lesson: 💡 Legacy systems survive because they work for users who learned them. Before "modernizing," ask: ➡️ What problem are we solving? ➡️ For whom? ➡️ Does visual modernization solve that problem? ➡️ Or are we redesigning because it LOOKS old? Sometimes legacy interface IS the feature. Asking all CTOs reading this: Have you seen legacy modernization fail because you changed too much too fast? #LegacyModernization #EMRStrategy #ChangeManagement

5

💡 Why Revenue Cycle, Clinical Workflows & Clearinghouses Must Work Together for Successful EMR Adoption One of the biggest lessons from EMR implementations is simple: clinical workflows and revenue cycle workflows cannot function in silos. A well-documented clinical encounter ensures accurate billing, and a well-designed revenue cycle ensures the organization gets paid for the care delivered. But there’s a third critical component that often gets overlooked - Clearinghouses. Platforms like Oracle Health and Epic Systems connect clinical documentation directly to charge capture and billing workflows, but clearinghouses act as the bridge between hospitals and payers - ensuring claims are transmitted, validated, and accepted. 🔹 Where It Works Well In optimized EMR environments: 1. Clinicians document accurately using structured templates 2. Charges are captured automatically from orders and procedures 3. Coding is completed with minimal queries 4. Claims are scrubbed and transmitted via clearinghouses like Availity or 5. Change Healthcare 5. Errors are identified early before reaching payers 📌 Example: Proper documentation of procedures and diagnoses flows into coding, charges generate automatically, and clean claims pass through the clearinghouse with minimal rejections. 🔹 Where It Breaks Down In less optimized implementations: 1. Clinicians rely on free-text documentation 2. Orders are not mapped correctly to billable charges 3. Coding queries delay billing 4. Claims fail clearinghouse edits 5. Rejections increase due to missing or inconsistent data 📌 Example: A procedure may be performed and documented, but if diagnosis codes or modifiers are missing, the clearinghouse may reject the claim before it even reaches the payer - delaying reimbursement. 🔹 Why This Matters A successful EMR adoption isn’t just about clinical documentation - it’s about ensuring that clinical actions translate into clean claims and timely payments. When Clinical teams, Revenue Cycle teams, and Clearinghouses work together: ✅ Cleaner claims ✅ Faster reimbursements ✅ Fewer denials ✅ Better EMR adoption ✅ Stronger financial performance 📌 The most successful EMR organizations don’t treat these as separate workflows - they treat them as one continuous lifecycle from patient care → documentation → billing → reimbursement. #HealthcareIT #EMR #RevenueCycle #Clearinghouse #OracleHealth #Epic #RCM #HealthcareKPIs

32

1 Comment

CMMI’s IOTA policy creates new incentives for transplant centers.    We built IOTACalculator.com to help transplant administrators quickly understand how performance translates into reimbursement under IOTA. The calculator is simple and free to use, and provides an unofficial reimbursement estimate.   Our goal at Project Donor is to remove operational friction that keeps life-saving transplants from happening. This is one small step in that direction. 🔗 https://lnkd.in/ghwMDbmK #transplant #transplantadministrator #organdonation #kidneydonation #liverdonation #livingdonorcoordinator #socialwork #transplantsocialworker #iota

17

5 Comments

$1.5M saved. 50,000+ hours logged. 20+ hiring managers enabled. What started as a pilot has become the backbone of this health system’s IT contractor strategy — and Revuud is at the center of it. Before Revuud: Oracle Health contractors were slow to source Budgets ballooned with inconsistent agency fees Managers lacked visibility and control Now? They post roles, onboard talent, and extend contracts in clicks — all while tracking every hour and dollar in real time. The results speak for themselves: ✅ $1.5M+ saved ✅ 123 contractor engagements ✅ Faster project delivery across departments and regions “Revuud gave our managers the speed and visibility they’d been asking for. We’re not just saving money — we’re hiring faster and smarter.” 👉 Read the full case study to see how this health system built a scalable, high-performing Oracle Health talent strategy: https://lnkd.in/gmQRzzgU #healthcareIT #OracleHealth #contractormanagement #healthsysteminnovation #Revuud #digitalhealth #HITstaffing #talentmanagement #healthIT

14

Fun session today with Ramakant Joshi talking through AI agents in Revenue Cycle Management. RCM isn’t very sexy but it’s where the money is! Agents enabling these types of traditionally difficult workflows is a really good example of how AI is actually creating differentiated solutions in Healthcare. https://lnkd.in/exmHWFPb

9