

Whitepaper
AI-Driven Digital Twins in Healthcare & MedTech
From simulation to continuous intelligence, governed autonomy and lifecycle value
Navigation
Navigation- Executive summary
- How digital twins evolved from simulation to continuous intelligence
- What is a digital twin in healthcare?
- How AI-driven digital twins create value in MedTech
- How much autonomy should an AI digital twin have?
- Designing digital twins for imperfect healthcare data
- Why scaling digital twins in healthcare is an ecosystem problem
- Patient digital twins: from episodic care to longitudinal care
- Digital twin governance, privacy and regulatory compliance
- How to implement a healthcare digital twin: an eight-step blueprint
- The future of digital twins in healthcare
- Digital twins in healthcare: frequently asked questions
- References
Executive summary
Digital twins are becoming a lifecycle intelligence layer
Digital twins in healthcare are emerging as a lifecycle intelligence layer connecting patients, providers, and medical devices. As healthcare organizations accelerate digital transformation initiatives, digital twins are emerging as a foundational capability enabling predictive analytics, personalized healthcare, and more intelligent clinical decision support.
Healthcare and medical technology are moving from digitization toward continuously informed systems that can represent the evolving state of a patient, device, process or care environment. The digital twin is a useful organizing construct for this shift because it connects data, context, prediction, simulation and action around a living representation of reality.
Digital twins have moved decisively beyond pre-development simulation. Device connectivity, telemetry, continuous monitoring, cloud platforms, large healthcare datasets and advances in AI now allow twins to create value across design, manufacturing, imaging, clinical workflows, treatment optimization, maintenance and post-market learning. In parallel, the digital twin can be understood as a data and intelligence architecture capable of linking the complete healthcare product lifecycle.
Five conclusions
- A true twin is continuously updated. Static representations are useful models, but they do not achieve the adaptive behavior expected from a mature digital twin.
- AI is horizontal infrastructure, not a single use case. It can improve diagnosis support, prediction, optimization, maintenance and workflow decisions, but adoption speed is constrained by data quality, privacy and regulation.
- Autonomy should be earned progressively. Decision boundaries, thresholds, escalation, accountability and expert intervention must be designed explicitly to avoid both unsafe automation and the supervisory trap of excessive human review.
- Scale is now more an ecosystem problem than a raw technology problem. Interoperability, regulatory validation, trust in data, cybersecurity and ROI determine whether prototypes become operating systems.
- Patient-focused twins can transform episodic care into longitudinal engagement, but consent, governance, validation and data protection must mature in parallel with the technology.
Management implication
The strategic question is no longer whether digital twins are technically possible. It is how to design the data, AI, governance, security and operating model so that the twin can be trusted to influence increasingly consequential workflows.
How digital twins evolved from simulation to continuous intelligence
Historically, digital twins were used primarily to simulate a device or process before it was built. That capability remains valuable, but it represents only a fraction of the opportunity now emerging in healthcare and MedTech. Today, the digital twin can become a continuously synchronized representation of a patient, device, process or healthcare system.
This evolution is enabled by the digitalization of medical devices, richer connectivity, continuous monitoring, growing healthcare datasets, cloud platforms and advances in AI. Together, these capabilities allow the twin to persist beyond design and follow the patient or asset through manufacturing, deployment, clinical use, service and post-market learning. The defining shift is from "model and simulate" to "sense, learn, predict and act."
"The digital twin is no longer just a virtual replica. It is becoming a living intelligence layer around the physical world."
From model to continuously learning operational asset
| Stage | Capability | Operating mode |
|---|---|---|
| 1. Simulation | Pre-development models | Static / periodic |
| 2. Connected twin | Telemetry and state sync | Near-real-time |
| 3. Learning twin | AI and feedback loops | Adaptive |
| 4. Governed twin | Bounded actions and escalation | Operational |
| 5. Lifecycle twin | Design-to-care continuity | Enterprise scale |
Figure 1. The twin evolves from a static model into a continuously learning and governed operational asset.
Where value is expanding
- Device design and virtual prototyping before physical builds.
- Manufacturing process modeling, quality optimization and operational visibility.
- Imaging optimization and parameter tuning.
- Treatment planning and patient-specific decision support.
- Predictive maintenance and remote monitoring of connected medical equipment.
- Closed-loop learning from field performance into the next generation of products.
What is a digital twin in healthcare?
Continuous synchronization, learning and context
A digital twin becomes meaningfully different from a conventional model when it can maintain an up-to-date representation of reality. Continuous ingestion of new information, telemetry, observability, machine learning and adaptive behavior are foundational to maintaining that fidelity. The twin should refine its state as conditions change rather than remain a frozen representation of an earlier moment.
Digital-twin maturity should be viewed as cumulative rather than instantaneous. Capability increases as the twin accumulates models, simulations, diagnostic information, operational observations and validated feedback. This framing supports realistic expectations for maturity, validation and controlled expansion of functionality over time.
Working definition
A healthcare digital twin is a continuously synchronized, data-driven representation of a patient, device, process or system that maintains context, learns from observations, supports prediction or simulation, and informs action within explicit governance boundaries.
Reference architecture for a healthcare and MedTech digital twin
| Layer | Components |
|---|---|
| Real world | Patient | Device | Imaging | Manufacturing | Clinical environment |
| Data and connectivity | Sensors | Telemetry | EHR and clinical data | Device logs | Imaging | Edge and cloud |
| Twin core | State model | Context | Relationships | Simulation | Digital thread | Observability |
| AI and prediction | Diagnosis support | Forecasting | Optimization | Anomaly detection | Maintenance |
| Action layer | Recommendations | Workflow automation | Escalation | Bounded autonomous action |
| Governance and trust | Consent | Privacy | Validation | Confidence | Auditability | Cybersecurity |
Figure 2. A reference stack links the real world to a stateful twin, AI-based prediction, governance and bounded action.
The architecture is rarely a single monolithic model. In practical systems, multiple interconnected twins, models and services represent components, relationships, dependencies and behaviors. The quality of the twin therefore depends as much on system integration and state management as on model accuracy.
How AI-driven digital twins create value in MedTech
AI changes the value proposition: from context to foresight
Data keeps the digital twin synchronized with reality. AI changes the value proposition by enabling the twin to move from understanding what is happening toward predicting what could happen next and informing what should be done about it.
In MedTech, AI-driven digital twins create opportunities across clinical decision support, predictive analytics in healthcare, diagnosis support, treatment planning, AI-enabled medical devices, imaging optimization and lifecycle management. The pace and degree of adoption will depend on the intended use, data quality, confidence, validation requirements, privacy constraints and regulatory status.
"Digital twin gives us context. AI gives us foresight. Together, they create the opportunity for better decisions."
Digital twin value across the healthcare and MedTech lifecycle
| Design & R&D | Manufacturing | Clinical use | Service & operations | Next product |
|---|---|---|---|---|
| Virtual prototyping | Process twin | Personalization | Predictive maintenance | Field learning |
| Device optimization | Quality prediction | Diagnosis support | Remote monitoring | Post-market insight |
| Imaging parameter tuning | Yield and throughput | Treatment optimization | Workflow optimization | Closed-loop redesign |
Figure 3. Digital twins can connect the healthcare and MedTech lifecycle, allowing operational, clinical, data and product intelligence to compound over time.
Think across the entire MedTech product lifecycle
The greatest opportunity is not an isolated digital-twin application, but a continuous digital thread spanning the entire medical device product lifecycle, from design and validation to deployment, monitoring, servicing, and post-market learning. By connecting engineering, operational, clinical and field information, the twin can allow learning to accumulate across lifecycle stages rather than remain confined within individual functions.
Design → Simulation → Manufacturing → Clinical deployment → Connected medical device monitoring → Service → Post-market learning → Next-generation product
This closed-loop model allows field performance, medical device service insights, clinical outcomes and post-market evidence to become inputs into future product development. The result is a learning lifecycle in which each deployed product can contribute to the design and optimization of the next generation.
A stakeholder-centric value lens
The value of a digital twin is inherently stakeholder-dependent. A clinician may focus on diagnosis and treatment support; a laboratory professional may value prediction and quality; a medical device engineering team may prioritize product optimization, predictive maintenance, regulatory compliance, and lifecycle performance; an enterprise may prioritize lifecycle integration and operating efficiency. Digital-twin programs should therefore begin with a clear stakeholder and decision context rather than with technology alone.
Design principle
Define the stakeholder, decision and value pool first. Then determine what state the twin must maintain, what evidence is required, and how AI should influence the workflow. For connected medical devices, the value proposition should extend across the entire lifecycle, from product development and deployment to post-market surveillance and continuous improvement.
How much autonomy should an AI digital twin have?
The automation boundary is critical
Healthcare should not equate intelligence with autonomy. A digital twin may generate valuable insights, predictions and recommendations without being authorized to act independently.
The appropriate level of automation should depend on the consequence of failure, the system's confidence, the available evidence, regulatory status and clear accountability. Each use case should therefore define explicit autonomous boundaries, confidence policies, escalation paths, kill switches and audit trails.
- Consequence of failure
- Confidence
- Available evidence
- Regulatory status
- Clear accountability
"Autonomy in healthcare should be earned progressively, not assumed technologically."
Human-in-the-loop cannot mean human-in-every-loop
Healthcare systems must manage two competing risks. Too much autonomy can create unacceptable safety risks when a system encounters uncertain, rare or unanticipated conditions. Too much human oversight can create a supervisory bottleneck that removes the operational value of automation.
The objective should therefore be bounded autonomy, with human intervention concentrated where the consequence of failure or level of uncertainty warrants it. Routine, well-evidenced and low-consequence actions may operate within approved boundaries, while ambiguous, high-impact or low-confidence situations should trigger expert review.
The goal is not to remove people from the system, but to apply human judgment where it creates the greatest safety and decision value.
A governed path from assistance to bounded autonomy
| Level* | Behavior |
|---|---|
| 1. Observe | Twin mirrors state; no decisions. |
| 2. Recommend | AI proposes; expert decides. |
| 3. Approve-to-act | System acts after explicit approval. |
| 4. Bounded autonomy | System acts within thresholds; escalates exceptions. |
| 5. Adaptive autonomy | Privileges expand only with evidence, validation and audit. |
*Guardrails, confidence, escalation, accountability, kill switch and audit trail apply at every stage.
Figure 4. A progressive delegation model allows autonomy to expand only as evidence, controls and operational trust mature.
Role clarity creates accountability
Accountability depends on explicit role definition across the workflow. Some wearable devices already execute automated actions within tightly defined parameters. In many clinical decisions, by contrast, AI may provide diagnostic support while the clinician retains final responsibility for treatment. Clear role definition establishes ownership, liability, trust and escalation behavior.
- Autonomous boundary: what the system may decide or execute without review.
- Confidence policy: when low confidence automatically triggers human review.
- Escalation path: who is responsible for exceptions and how quickly they must respond.
- Kill switch: how action can be suspended if safety or integrity is uncertain.
- Audit trail: what evidence is retained for review, validation and accountability.
Designing digital twins for imperfect healthcare data
Imperfect data is part of the design problem
Healthcare data will rarely be complete, perfectly standardized or free from bias. A mature digital twin must therefore be designed for uncertainty rather than built on the assumption of ideal inputs.
The twin should make uncertainty visible and manage it through confidence thresholds, validation, safe fallback behavior, feedback loops and continuous data-quality improvement. These mechanisms allow the system to remain useful while clearly signalling when its evidence is incomplete or its recommendations require additional review.
"We should not wait for perfect healthcare data. We should design twins that understand when their data is imperfect."
A practical data-quality loop
| 1. Detect | Assess completeness, provenance, drift, outliers and bias. |
| 2. Bound | Apply confidence thresholds, constraints and safe fallback behavior. |
| 3. Validate | Use expert review in early adoption and for high-impact exceptions. |
| 4. Learn | Feed validated outcomes back into the data and model lifecycle. |
Probabilistic outputs require calibrated trust
Large language models and other probabilistic AI systems produce outputs with uncertainty. During early adoption, human validation is therefore essential not only for safety but also as a source of high-quality feedback. Over time, this feedback can improve model judgment, sharpen confidence thresholds and reveal where the underlying data requires remediation.
Organizations with limited local datasets can also explore federated learning and related privacy-preserving techniques that enable learning across distributed data environments without requiring all raw data to be centralized. The objective is not to eliminate data constraints, but to build a system that can become more robust despite them.
Data principle
A mature twin does not hide uncertainty. It makes confidence visible, defines safe behavior when inputs are weak, and uses validated outcomes to improve both data and decision quality.
Why scaling digital twins in healthcare is an ecosystem problem
Technology alone will not determine scale
Foundational digital-twin technology is increasingly mature and available. Moving from proof of concept to production, however, depends on more than demonstrating technical feasibility. Scale requires the wider ecosystem to support, validate, govern and trust the solution.
Successful deployment of a digital twin in healthcare requires healthcare interoperability across clinical, operational and device ecosystems. Standards such as HL7 and FHIR play a critical role in enabling scalable and connected digital health environments.
- Interoperability
- Regulatory validation
- Data quality and stewardship
- Privacy and consent
- Cybersecurity
- Trust
- Demonstrable ROI
"A successful prototype proves that the technology works. Scaling requires proving that the ecosystem can trust it."
These requirements determine whether a successful prototype can become a trusted, interoperable and economically sustainable operating system. They should therefore be addressed as part of the initial design and proof-of-value approach, rather than deferred until after the technology has been demonstrated.
Scaling requires more than technology maturity
| Constraint | What must be resolved |
|---|---|
| Interoperability | Fragmented vendors, schemas and interfaces. |
| Regulation and validation | Evidence, change control and intended-use boundaries. |
| Data trust | Completeness, provenance, bias and confidence. |
| Privacy and consent | Use rights, de-identification and longitudinal governance. |
| Cyber resilience | An expanded attack surface across devices, AI and data flows. |
| ROI and operating model | Clear value pools, workflow integration and accountability. |
Figure 5. Scale depends on resolving ecosystem, evidence and operating-model constraints, not only on building the twin itself.
Prototype success is not production trust
A prototype that demonstrates technical potential is not equivalent to a system that stakeholders will trust for consequential healthcare decisions. Production deployment requires validation frameworks, data stewardship, traceability, change control and repeatable evidence that the twin behaves within intended boundaries.
A proof-of-value sequence
- Start with a bounded use case where the value pool and stakeholder are explicit.
- Instrument the workflow so that value, error modes and intervention rates can be measured.
- Use the proof of concept to establish economic evidence as well as technical feasibility.
- Prioritize interoperability and data contracts early; avoid creating an isolated twin that cannot join the wider ecosystem.
- Expand scope only after validation, governance and operating ownership are in place.
Patient digital twins: from episodic care to longitudinal care
From episodic encounters to longitudinal care
Healthcare today is often episodic: the patient is observed at specific points in time, and each encounter may be treated as a largely separate episode of care. A patient-focused digital twin creates the possibility of maintaining longitudinal context across those encounters.
For patients managing chronic conditions such as diabetes and hypertension, a digital twin can combine continuous measurements, medication context and historical response into a longitudinal view. This context can support more informed interactions before, during and after a hospital encounter, while helping the care team understand how the patient's condition is evolving over time.
A patient digital twin can become a foundation for personalized healthcare, precision medicine and longitudinal care management.
"Instead of asking only 'What is this patient's condition today?', the twin helps us ask 'How is this patient evolving, and what emerging risks or care needs should we evaluate?'"
From episodic care to a continuously informed patient journey
| Home | Pre-visit | Consult | Treatment | Post-care |
|---|---|---|---|---|
| Sensors, CGM, blood pressure | Longitudinal summary | Decision support | Plan and monitoring | Remote feedback |
| Continuous context | Relevant history ready | Personalized options | Adaptive follow-up | Early escalation |
The digital twin provides longitudinal state, prediction, governed actions and feedback across the journey.
Figure 6. A patient twin can connect home monitoring, pre-visit context, consultation, treatment and post-care feedback.
How does a digital twin improve the patient experience at a hospital?
Before arriving: the hospital already has context
For a patient with diabetes and hypertension, the twin can bring together continuous glucose patterns, blood-pressure trends, activity, medication context and historical response.
Patient experience: instead of arriving as "a new episode of care," the patient arrives with a longitudinal picture of their health.
At registration: less repetition
Relevant contextual information can be available before consultation, reducing repetitive history collection.
Patient experience: "I don't have to tell my medical story all over again."
During consultation: the conversation becomes more meaningful
Rather than considering only today's glucose or blood-pressure measurement, the care team can use longitudinal patterns and accumulated context to support a more individualized treatment pathway.
Patient experience: the conversation shifts from "What is your blood pressure today?" toward "What has been happening to you over time, and what should we do differently?"
Treatment becomes more personalized
Digital twins can support patient-specific decision support and treatment planning while keeping clinical judgment and accountability appropriately involved.
Leaving the hospital does not end the journey
The twin can continue incorporating monitoring information after discharge, connecting home monitoring, treatment and post-care feedback.
Key takeaway
| Today | Patient → Hospital → Diagnosis → Treatment → Discharge |
| With a digital twin | Continuous patient data → Living patient context → Personalized consultation → Individualized intervention → Continuous monitoring → Learning → Next intervention |
"A digital twin enables the hospital to stop treating every visit as a new episode and start treating the patient as a continuously understood individual."
Illustrative applications
- Diabetes: continuous glucose patterns, activity, medication context and historical response inform personalized monitoring and escalation.
- Hypertension: longitudinal blood-pressure patterns and contextual data can help identify trends that are missed by occasional measurements.
- Connected devices: device performance and patient state can be evaluated together instead of in separate operational silos.
- Clinical workflows: relevant history can be summarized before consultation, helping reduce repetitive data collection and improve continuity.
Boundary condition
Patient digital twins should augment clinical judgment and care continuity. The level of autonomous action must remain aligned with evidence, intended use, regulatory status and explicit accountability.
Digital twin governance, privacy and regulatory compliance
Trust is a system property, not a model feature
Patient-focused twins combine some of the most sensitive data categories with models that may evolve over time. Persistent barriers include privacy, consent management, interoperability, AI governance in healthcare, and regulatory compliance. As digital twins increasingly support AI-enabled medical devices and Software as a Medical Device (SaMD), organizations must address evolving requirements from regulators such as the FDA and EU MDR while maintaining trust, transparency, and patient safety. Implementations are often easier within a single-vendor ecosystem, where data contracts and system behavior are more controlled, and where personally identifiable information can be appropriately removed or protected.
Validation and data stewardship determine whether an organization will trust a twin for consequential decisions. A continuously learning twin creates a governance challenge: the system is expected to improve, yet every material change can affect the evidence on which trust was established. For AI-driven digital twins used in healthcare and MedTech environments, governance extends beyond model performance to include traceability, validation, explainability, cybersecurity, and change management. These requirements are particularly important for AI-enabled medical devices and SaMD solutions, where continuous learning must remain aligned with regulatory expectations and clinical risk management practices.
Governance domains
| Domain | Scope |
|---|---|
| Data | Consent, provenance, access, de-identification, retention. |
| Model | Validation, drift monitoring, versioning, explainability, confidence scoring, responsible AI practices, and model lifecycle governance. |
| Decision | Role ownership, thresholds, human review, escalation. |
| Operations | Medical device cybersecurity, monitoring, change control, auditability, incident response, and regulatory compliance management. |
Model maturity should be staged
- Establish intended use and unacceptable failure conditions before model selection.
- Validate the twin in representative workflows, not only on benchmark datasets.
- Capture human overrides and exceptions as learning signals, while preserving accountability.
- Monitor data drift and model behavior continuously after deployment.
- Revalidate when data sources, models, interfaces or action boundaries change materially.
- Ensure ongoing compliance with applicable regulatory frameworks such as FDA guidance, EU MDR requirements, and organizational policies governing responsible AI in healthcare.
Governance principle
The twin should become more capable over time, but capability must grow inside a controlled lifecycle of evidence, traceability, AI governance, regulatory compliance, and explicit decision rights.
How to implement a healthcare digital twin: an eight-step blueprint
Start with value, not with the twin
Before asking, "How do we build a digital twin?", leadership should first identify whose decision the twin is intended to improve, what value that improvement will create and what evidence would make stakeholders trust the outcome.
This value-first logic helps prevent technically impressive but isolated solutions. It connects the stakeholder need to the required data, twin state, AI capability, governance model and permitted action.
Stakeholder → Decision → Value → Data → Twin → AI → Governance → Action
"Whose decision are we trying to improve, what value will that create, and what evidence would make us trust the twin?"
An eight-step blueprint
| 1. Frame the value Select the stakeholder, decision, value pool and measurable outcome. Define what the twin must represent and why. |
2. Establish the data spine Connect relevant telemetry, clinical, operational and historical data with provenance, quality checks and consent rules. |
| 3. Build the living state model Create the twin core: state, context, relationships, simulation, observability and update mechanisms. |
4. Add AI with confidence Introduce prediction and optimization; expose confidence and design safe fallback behavior for uncertain outputs. |
| 5. Govern the action boundary Define who decides, what can be automated, when to escalate, and how actions are audited or stopped. |
6. Validate end-to-end Test the complete workflow including data failure, model error, cyber events, human handoffs and recovery. |
| 7. Scale through interoperability Standardize interfaces, integrate multi-vendor components and extend the digital thread across lifecycle stages. |
8. Learn continuously Use outcomes, overrides, maintenance data and post-market evidence to improve the twin without losing governance control. |
What leaders should measure
- Business and clinical value: quality, time, cost, utilization, patient experience or maintenance benefit.
- Twin fidelity: state accuracy, freshness, coverage and behavior under missing data.
- AI trust: accuracy, calibration, confidence distribution, override rate and exception rate.
- Operational performance: latency, availability, integration reliability and workflow adoption.
- Governance performance: validation status, auditability, unresolved exceptions, privacy and security incidents.
- Scaling economics: reuse of data and models, interoperability cost, operating effort and time-to-value.
North star
Scale the twin only when value, fidelity, trust and operating control improve together. A larger system is not a more mature system if governance and evidence lag behind capability.
The future of digital twins in healthcare
Scale value, fidelity, trust and governance together
"The future of digital twins in MedTech and healthcare is not about building a perfect digital replica, nor is it a race toward maximum autonomy. It is about creating a continuously learning connection between the physical and digital worlds, where data builds context, AI creates foresight, and governed automation translates that intelligence into better outcomes. The winners will be those who scale value, fidelity, trust and governance together."
The future of digital twins in healthcare will depend on how organizations combine AI, connected medical devices, predictive analytics, interoperability and governance to deliver measurable outcomes across patients, providers and MedTech ecosystems.
An executive operating model
Sense → Understand → Predict → Decide → Act → Learn
The implementation blueprint defines how to establish the twin; the executive operating model defines how it creates value continuously. The twin senses changes, understands context, predicts possible outcomes, supports decisions, enables bounded action and learns from results, while trust, governance and security constrain every stage.
Tata Elxsi's experience across medical devices, connected health, regulatory engineering, digital health platforms, AI-enabled solutions and product lifecycle engineering uniquely positions it to help MedTech organizations progress from isolated digital twin initiatives to scalable, governed, and value-driven digital twin ecosystems.
Executive framework
Sense, understand, predict, decide, act and learn, within an operating environment surrounded by trust, governance and security.
Digital twins in healthcare: frequently asked questions
What is a digital twin in healthcare?
A healthcare digital twin is a continuously synchronized, data-driven representation of a patient, medical device, process, or healthcare system that supports prediction, simulation, and informed decision-making.
How do AI-driven digital twins work?
AI-driven digital twins combine real-world data with AI models to continuously learn, predict future scenarios, generate insights, and support better operational and clinical decisions.
How are digital twins used in medical devices?
Digital twins help optimize medical device design, simulation, manufacturing, connected monitoring, predictive maintenance, and post-market learning throughout the product lifecycle.
How do digital twins improve patient outcomes?
Digital twins provide longitudinal patient context, enabling personalized healthcare, earlier intervention, more informed clinical decisions, and continuous care management.
What are the challenges in scaling digital twins?
Successful scaling requires interoperability, regulatory validation, data quality, cybersecurity, privacy, trust, and demonstrable business or clinical value.
How much autonomy should AI have in healthcare?
AI autonomy should be introduced progressively based on risk, confidence, evidence, regulatory requirements, and accountability, with human oversight retained for high-impact decisions.
Why is medical device cybersecurity important?
As connected medical devices and digital twins become integral to patient care, cybersecurity is essential to protect data integrity, system reliability, patient safety, and clinical operations.
References
- O-RAN Next Generation Research Group workshop, February 2024: https://www.o-ran.org/event/o-ran-ngrg-6g-workshop-architecture-evolution-digital-twin-and-convergence-of-communications-and-computing-in-6g-era
- Telecom Standards Development Society of India (TSDSI), Technical Deep Dive 2025 keynote: https://ttdd.tsdsi.in/wp-content/uploads/2025/07/Keynote-4-RajaG_TataElxsi_AgenticDTBasedOrch6G.pdf








