Dr. Gopala Krishna Behara

Moving from "Digital-First" to "Intelligence-Sovereignty" 🇮🇳 The Union Budget 2026 isn't just a fiscal document; it’s a blueprint for India’s role as the world’s "Intelligence Backbone." Three strategic shifts stood out to me from yesterday’s announcements that every technology leader should be watching: 1️⃣ Compute as Capital: By reframing infrastructure this way, the government is signaling that AI capacity is now a national strategic asset, much like power or water. The tax holiday until 2047 for global cloud giants is a massive incentive for building "Sovereign-Ready" tech on Indian soil. 2️⃣ ISM 2.0 & Full-Stack IP: We are moving beyond just assembling chips. The shift toward producing equipment, materials, and domestic IP (India Semiconductor Mission 2.0) means India is aiming to own the entire value chain—not just the consumption of it. 3️⃣ The "Public Infrastructure" Bet: From 'Bharat-VISTAAR' in agriculture to the new AI Content Labs in schools, the focus is on population-scale impact. We aren't just building AI for the elite; we are building it for the last mile. My Take: For those of us architecting enterprise systems, the mandate is clear: The "Wait and See" era of AI is over. The focus must now shift from experimental pilots to building High-Trust, Logic-Driven systems that respect local data dignity while driving real economic ROI. India isn't just participating in the AI race anymore—we are setting the rules of the track. What part of the #Budget2026 tech push are you most excited (or concerned) about? Let’s discuss below. 👇 #UnionBudget2026 #IntelligenceSovereignty #AILeadership #DigitalIndia #TechStrategy #ViksitBharat

1

Can #healthcare organizations deliver real-time, governed #data and #analytics without duplicating and centralizing sensitive patient information? A large public health system in Asia Pacific faced this challenge while modernizing its data ecosystem across 90+ clinical systems serving nearly 2 million residents. By adopting a logical #dataarchitecture with the #DenodoPlatform at its core, the organization: ✅Minimized data replication across 600+ fragmented systems ✅Ensured strict governance and privacy across regions ✅Enabled real-time clinical decisions and better patient outcomes Discover how this health system leveraged Denodo to transform patient care: https://okt.to/5UABO7 #DataManagement #DataVirtualization #DataGovernance #DataforALL #NoDataLeftBehind

2

"Additional Resources" in FHIR: problem & solution... R6 core must be stable and mostly normative, but some important parts are still evolving. Keeping them in core risks churn; removing them breaks implementations. Working Groups need a supported lane to iterate between releases without fragmenting the ecosystem. ## Solution: Additional Resources An active development lane for resources/operations/pages not yet ready for core. Content remains official HL7 FHIR, canonicals stay under "http://hl7.org/fhir". It’s not a demotion: items are expected to progress, then either graduate to core (often normative) or retire. ## How the system works Packaging: additional content is published in IG packages; your IG declares dependencies and the publisher/validator resolves them. Referencing: an “allowed targets” extension declares which core/Additional elements may reference an Additional Resource (approved by the owning WG of the referencing element), and a compartment-membership extension states the compartment and the search/chained parameters that define membership. Prefer extensions over hard elements for optional cross-links; avoid blanket wildcards unless intentional. Namespaces: Additional Resource definitions use the same "http://hl7.org/fhir" canonical namespace to keep resolution straightforward. Governance flow: propose → incubate in an IG → prove maturity (use, tests, bindings) → graduate back to core or retire. FMG coordinates with intentionally light admin. Compatibility: core references won’t break—consumers fetch the packages. Validation is being tuned for cross-IG references and the new extensions. ## Where it goes (by destination IG) * API Incubator IG: GraphDefinition and $graph; lifecycle ops/pages ($current, $find); large-resource ops ($add, $remove, $filter); Async Bulk and Async Interactions pages; meta ops ($meta, $meta-add, $meta-delete) pending Security WG. * Testing IG: TestScript, TestPlan, TestReport, and testing narrative. Core keeps a brief overview pointing here. * Subscriptions Backport IG: subscription extras (e.g., $get-ws-binding-token) with widened version coverage. * Feature Capabilities IG: capability helpers ($implements, $conforms, $subset) and the “subset” page. * Topic IGs (e.g., SDC): mature topical homes such as $questionnaire → SDC. ## What stays in core (examples) The Requirements resource remains and proceeds to Normative. Pages are scrubbed and clearly marked Normative or Informative; Trial-Use narrative is removed from core. ## Practical impact * Add package dependencies when you use moved content (API Incubator, Testing, Feature Capabilities, Subscriptions Backport, SDC as needed). * Canonicals stay the same; ensure your tooling fetches/resolves those packages. * Use the allowed-targets and compartment extensions; avoid broad targetProfile of "*" unless that’s truly intended.

43

2 Comments

More on Remote Patient Monitoring “In terms of cost-related outcomes, there was a clear downward trend in the risks of hospital admission/readmission, length of stay, number of outpatient visits and non-hospitalisation costs.” https://lnkd.in/d32P6BBR.

12

1 Comment

Appreciated being featured in 𝗧𝗵𝗲 𝗔𝗜 𝗜𝗻𝗻𝗼𝘃𝗮𝘁𝗼𝗿 for a grounded conversation on where 𝗲𝗻𝘁𝗲𝗿𝗽𝗿𝗶𝘀𝗲 𝗔𝗜 is headed. Deborah Yao and I discussed 𝗴𝗼𝘃𝗲𝗿𝗻𝗮𝗻𝗰𝗲, 𝗿𝗲𝗹𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆, 𝗥𝗢𝗜, and the rise of 𝗮𝗴𝗲𝗻𝘁𝗶𝗰 𝘀𝘆𝘀𝘁𝗲𝗺𝘀. One observation from the field: 𝗮𝗴𝗲𝗻𝘁𝗶𝗰 𝗰𝗼𝗱𝗶𝗻𝗴 can feel fast at commit time, but without disciplined 𝘀𝗰𝗼𝗽𝗶𝗻𝗴, 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲, and 𝘁𝗲𝘀𝘁 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆, teams often inherit higher 𝗣𝗥 𝗰𝗵𝘂𝗿𝗻, 𝗿𝗼𝗹𝗹𝗯𝗮𝗰𝗸 𝗿𝗶𝘀𝗸, and fragile production code. ⚠️ I also shared a concern I hope never proves true: it may take a major 𝗔𝗜-𝗿𝗲𝗹𝗮𝘁𝗲𝗱 𝗰𝘆𝗯𝗲𝗿 𝗯𝗿𝗲𝗮𝗰𝗵 before 𝗔𝗜 𝗴𝗼𝘃𝗲𝗿𝗻𝗮𝗻𝗰𝗲 gets the attention it deserves. 𝗔𝗜 𝗶𝘀 𝗺𝗼𝘃𝗶𝗻𝗴 𝗳𝗮𝘀𝘁. 𝗚𝘂𝗮𝗿𝗱𝗿𝗮𝗶𝗹𝘀 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗺𝗼𝘃𝗲 𝗳𝗮𝘀𝘁𝗲𝗿. Thanks to Deborah Yao the thoughtful interview. 🔗 Read here: https://lnkd.in/gpppEW2T #AI #EnterpriseAI #Cybersecurity #AIGovernance UST #RDBuzz

16

3 Comments

"It is the mark of an educated mind to be able to entertain a thought without accepting it." — Aristotle, Ancient Greek Philosopher Really good food for thought in this talk by Advait Sarkar (who while having a number of impressive titles used cool Thought Researcher one for his talk on AI’s effect on critical thinking). Sarkar is currently part of a team at Microsoft called Tools for Thought (again a cool name) which is working on addressing an emerging issue in AI/human interaction – namely AI’s potential to negatively affect humans’ willingness and ability to use critical thinking skills and creativity when “partnering” with AI. For example, Sarkar believes that the growing reliance on tools such as chatbots is leading people to passively accept AI’s answers to their prompts instead of using the tools to help them expand their thinking and explore more possibilities. In other words, we are increasingly letting AI do our brainwork. And as Sarkar amusingly comments, “Studies show that when we don't use our brains, they get worse at brain things.” To make his case, Sarkar walks through an AI use scenario that describes how AI is typically used today, and then effectively points out the ways AI can blunt our creativity, critical thinking skills, and even our memory. Though he recognizes the benefits of using AI as an assistant, he maintains AI is far more valuable (not to mention less restrictive), when used as a tool for thought. Sarkar then effectively explains the AI as a tool for thought concept by demonstrating a prototype that his Tools for Thought research team is developing. Notably, the most notable characteristic of the tool is what is what it doesn’t have – a chatbot. And with that, I end this with the question that Sarkar ends his talk with – “What would you rather have? A tool that thinks for you, or a tool that makes you think?” #AI #modernITleader #leadershipdevelopment https://lnkd.in/dUSZcb2U

15

1 Comment

Quantum will fundamentally change our lives, and we are helping shape that future. In "Our Quantum Future", our leaders share their vision alongside Nobel laureates, scientists, and technology pioneers from across the globe. For Takahito Tokita, the future of quantum computing lies in building the technology with integrity, prioritizing quality, transparency, and early collaboration across industries to create strong foundations today for long-term impact. For Shintaro Sato, progress in quantum innovation depends on trust and deep ecosystem collaboration. Advancing this technology requires close cooperation between government, academia, and private companies to turn ambition into practical, reliable solutions. Participating in this documentary highlights our role in driving quantum advancement and reinforces our commitment to continuous innovation in this field. By combining quality, precision, and long-term vision, we are actively shaping the future of quantum computing. "Our Quantum Future" premiered this week for a selected audience and will be available soon. Discover the trailer here: https://okt.to/xU5FNi #QuantumComputing #OurQuantumFuture #Innovation

2