https://deepc.ai/assets/FAQ-WYNl-JIB.js

1import{r as m,j as e}from"./react-vendor-DkA7xE2p.js";import{S as w,n as f,H as y,P as v,B as b,D as k,E as I,G as A,I as x,F as C,o as g}from"./index-Cw9LQMk_.js";import{M as T,r as q}from"./index-CVEz8c4_.js";import"./supabase-vendor-DRR_Es6B.js";import"./tanstack-vendor-BzDmRgfF.js";const j=`# deepc FAQ
2
3Source: rebuilt for clinical AI infrastructure positioning
4
5Updated: 2026-05-31
6
7---
8
9## Category: Clinical AI infrastructure basics
10
11### What is deepc?
12
13deepc is clinical AI infrastructure for health systems.
14
15It connects to the systems an organization already runs and provides a reusable foundation to build, deploy, monitor, and govern AI workflows across clinical, operational, data, and AI environments.
16
17The goal is not to add another isolated application. The goal is to help health systems move from fragmented AI pilots to scalable, governed AI adoption across routine care.
18
19### What problem does deepc solve?
20
21Health systems are increasingly evaluating, deploying, and managing many AI capabilities across departments, vendors, and workflows. Without shared infrastructure, every new AI workflow can create another integration project, security review, governance process, monitoring setup, and operational dependency.
22
23deepc helps reduce that fragmentation by providing one infrastructure layer for AI workflows - with reusable integration, deployment, monitoring, governance, and evidence capture.
24
25### Is deepc an AI marketplace?
26
27No. deepc can help health systems access and deploy commercial AI solutions, but the core product is clinical AI infrastructure.
28
29A marketplace primarily helps buyers discover and procure models. deepc focuses on making AI workflows operational: integrated into existing systems, deployed safely, monitored in production, and governed across the organization.
30
31### Is deepc only for radiology?
32
33No. deepc has deep experience in imaging and radiology, but the infrastructure is designed for clinical AI workflows more broadly.
34
35Imaging remains an important environment and evidence source. But the broader purpose is to help health systems operationalize AI across existing clinical, operational, documentation, data, and governance workflows.
36
37### What does "one integration, every AI workflow" mean?
38
39It means deepc connects once to the relevant systems in the health-system environment. New AI workflows can then reuse the same integration layer, runtime, monitoring, and governance foundation instead of starting a new implementation project every time.
40
41The practical benefit is that AI adoption becomes more repeatable, scalable, and governable.
42
43### Who is deepc for?
44
45deepc is relevant for executive, clinical, technical, operational, and governance stakeholders.
46
47Typical stakeholders include CEOs, CFOs, CIOs, CTOs, CMIOs, CDIOs, clinical transformation leaders, service-line leaders, AI governance teams, data protection teams, and innovation teams.
48
49---
50
51## Category: Strategy and transformation
52
53### Why does clinical AI need infrastructure?
54
55AI adoption is moving beyond isolated pilots. Health systems are now facing many AI models, vendors, departments, workflows, agents, and internally developed capabilities.
56
57Without infrastructure, each new workflow can require custom integration, new governance work, separate monitoring, and unclear operational ownership. Clinical AI infrastructure creates a shared operating model so AI can scale safely across the organization.
58
59### How is this different from buying individual AI tools?
60
61Buying individual AI tools can solve a specific use case. But over time, a health system may end up with many disconnected tools, each with its own integration, monitoring, support model, governance process, and evidence trail.
62
63deepc helps health systems build an operating layer underneath those tools so they can deploy and govern many AI workflows through a shared foundation.
64
65### Why is this relevant now?
66
67The number and variety of healthcare AI capabilities are increasing quickly. Commercial AI models, in-house AI, foundation models, and agentic workflows are all becoming part of the strategic roadmap.
68
69The challenge is no longer only "Which model should we buy?" It is also "What infrastru

69cture will let us deploy, monitor, govern, and scale many AI workflows safely?"
70
71### How does deepc help avoid fragmented AI adoption?
72
73deepc standardizes the infrastructure around AI workflows: integration, deployment, routing, monitoring, governance, evidence, and operational control.
74
75That means teams do not need to reinvent the operating model for every new use case. They can reuse the same foundation while adapting workflow logic to local clinical and institutional needs.
76
77### What is the strategic value for a health system?
78
79The strategic value is repeatability.
80
81A health system can start with one high-priority AI workflow, establish the infrastructure and governance foundation, then expand into additional workflows, departments, sites, and AI capabilities without rebuilding the entire deployment model.
82
83### Does deepc help with AI strategy or only implementation?
84
85deepc is infrastructure, but infrastructure decisions are strategic. The right operating layer affects AI vendor strategy, governance, clinical adoption, data security, cost, and long-term scalability.
86
87deepc works with health systems to align technical implementation with clinical, operational, governance, and value priorities.
88
89---
90
91## Category: Value and ROI
92
93### What value does deepc create?
94
95deepc creates value by reducing duplicated implementation work, accelerating deployment, supporting consistent governance, and helping health systems reuse infrastructure across multiple AI workflows.
96
97The value is not limited to one model or one department. It compounds as more workflows are deployed on the same foundation.
98
99### How should a CFO think about the business case?
100
101The business case should not be limited to the ROI of one AI algorithm.
102
103A stronger infrastructure case includes avoided duplicated integration work, shorter deployment timelines, reduced governance overhead, better reuse of technical architecture, operational consistency across sites, and improved visibility into adoption and value.
104
105### Why not build this infrastructure ourselves?
106
107Some large health systems can build parts of this internally, but doing so requires sustained investment in integrations, workflow tooling, monitoring, governance, security, vendor management, and clinical deployment operations.
108
109deepc provides a specialized infrastructure layer so health systems can focus internal resources on strategy, workflow design, governance, and value creation rather than rebuilding the operating layer from scratch.
110
111### How does deepc reduce implementation effort?
112
113Once the infrastructure layer is in place, additional workflows can reuse established connectivity, routing, runtime, monitoring, audit, and governance patterns.
114
115That means new workflows become more about configuration, validation, and operational rollout, rather than starting from scratch with every model, vendor, or use case.
116
117### How quickly can a workflow go live?
118
119Timelines depend on the systems involved, workflow complexity, governance requirements, customer readiness, and deployment scope.
120
121The purpose of deepc is to materially reduce time to value by reusing the same integration and governance foundation across workflows.
122
123### How does deepc help measure value after deployment?
124
125AI value should be observed in production, not assumed at procurement.
126
127Depending on the workflow, deepc can support monitoring of usage, adoption, performance, operational impact, incidents, and evidence. This helps leadership understand what is working, what needs adjustment, and where additional value can be created.
128
129### Is deepc a platform investment or a single use-case investment?
130
131The strategic value is infrastructure. A health system may start with one use case, but the long-term value comes from reusing the same foundation across many workflows.
132
133This is especially relevant for organizations expecting to deploy multiple AI capabilities over time.
134
135### Does deepc help compare vendors or models?
136
137deepc can support a more structured approach to AI deployment and monitoring, but vendor/model selection depends on the clinical need, regulatory status, evidence, customer requirements, and local workflow.
138

139The infrastructure makes it easier to deploy and observe different AI capabilities in a governed way.
140
141### How does deepc help prevent wasted AI spend?
142
143AI spend is wasted when models are bought but not adopted, not integrated, not trusted, not monitored, or not aligned with workflow reality.
144
145deepc helps reduce that risk by focusing on operational deployment, workflow-native integration, governance, and evidence from the start. The goal is not only to acquire AI capabilities, but to make them usable in the clinical and operational processes where value is actually created.
146
147---
148
149## Category: Integration and deployment
150
151### Which systems can deepc connect to?
152
153deepc is designed to connect into existing health-system environments, including EHR, imaging, worklists, reporting, documents, claims, data infrastructure, identity systems, AI models, and agentic workflows.
154
155Standards such as DICOM, HL7, and FHIR may sit underneath these integrations depending on the workflow and system architecture.
156
157The integration goal is not only connectivity, but making AI outputs usable inside the workflows where teams already make decisions.
158
159### Does deepc replace existing clinical systems?
160
161No. deepc does not replace EHRs, PACS, reporting systems, worklists, data platforms, or operational systems.
162
163It sits as an infrastructure layer that connects AI capabilities to the systems and workflows teams already use.
164
165The goal is to make AI work through the existing environment, not force the organization to rebuild it.
166
167### What does the initial integration usually involve?
168
169The initial integration depends on the customer environment and target workflows.
170
171Typical work may include connectivity to clinical systems, data flows, identity and access requirements, workflow triggers, output destinations, monitoring requirements, and governance processes.
172
173### Does every new workflow require a new integration?
174
175No. That is the purpose of the infrastructure model.
176
177After the foundation is in place, new workflows can reuse the existing integration layer, runtime, routing, monitoring, audit, and governance capabilities.
178
179### What makes deepc different from simply integrating an AI model?
180
181A technical model integration is only one part of adoption. AI also needs to appear in the right workflow, at the right time, with the right clinical or operational context, output format, routing logic, monitoring, and governance.
182
183deepc provides the infrastructure layer around the model so health systems can move from "the model runs" to "the workflow works."
184
185### Can deepc support multi-site health systems?
186
187Yes. deepc is designed for multi-site environments where different hospitals, departments, or care sites need consistent deployment and governance while still respecting local workflow differences.
188
189### Can deepc work with different local systems across sites?
190
191Yes. Health systems often have heterogeneous IT environments. deepc is designed to work around the systems that already exist rather than forcing every site into an identical application landscape.
192
193The exact implementation depends on the systems, interfaces, deployment model, and workflow scope.
194
195### Where does deepc run?
196
197Deployment architecture depends on the customer environment, security requirements, data-handling requirements, and workflow design.
198
199The deployment model is agreed with the health system during technical, security, and governance review.
200
201### Is deepc cloud-based, on-premise, or hybrid?
202
203The architecture can vary. Some workflows may involve cloud-based components, some may require local components, and some may be hybrid.
204
205The important point is that deployment should align with the institution's security posture, data protection requirements, and operational model.
206
207### Can deepc integrate with downstream operational systems?
208
209Yes. AI workflows often need to route outputs into clinical, operational, documentation, billing, quality, or reporting systems.
210
211deepc's role is to help make AI outputs usable inside real workflows, not just run a model in isolation.
212
213---
214
215## Category: Clinical workflow adoption
216
217### How does AI appear to clinicians?
218
219AI should appear where clinical work already happens.
220
221Depending on the workflow, outputs may surface in worklists, EHR context, imaging environments, reporting tools, documentation workflows, alerts, operational queues, or review workflows.
222
223### Does deepc force clinicians into another application?
224
225The goal is to avoid unnecessary workflow disruption.
226
227Some workflows may include dedicated interfaces, but deepc is designed to deliver AI into existing systems and processes wherever possible. For clinicians, the best AI workflow is often the one that appears naturally inside the work they are already doing, without adding avoidable clicks, portals, or context switching.
228
229### How does deepc reduce workflow disruption?
230
231deepc is designed to make AI available inside the systems and workflows teams already use, rather than forcing clinicians, operators, or administrators into disconnected tools.
232
233Depending on the workflow, AI outputs can be routed into EHR context, worklists, imaging environments, reporting tools, documentation workflows, alerts, review queues, or operational systems. The goal is smooth adoption: less context switching, fewer manual steps, and AI that supports the clinical process rather than 

233interrupting it.
234
235### Are workflows off-the-shelf products?
236
237Workflows shown on the website are illustrative.
238
239deepc partners with health systems to configure AI workflows, agents, integrations, and governance around their existing clinical environment. The exact workflow depends on clinical goals, local systems, operating model, and governance requirements.
240
241### Can imaging be part of a broader workflow?
242
243Yes. Imaging remains important, but it does not need to be the entire workflow.
244
245For example, imaging evidence may be combined with EHR context, laboratory values, documentation, routing, care-team notification, coding support, or trial eligibility workflows.
246
247### Can deepc support documentation workflows?
248
249Yes. AI workflows may include documentation support, report drafting, summarization, structured outputs, or routing of relevant information to downstream systems.
250
251The exact configuration depends on clinical governance, customer requirements, and the approved workflow.
252
253### Can deepc support clinical prioritization or triage?
254
255Yes. Clinical prioritization, triage, and routing are possible workflow patterns when appropriate and governed.
256
257These workflows must be configured carefully around clinical context, safety, accountability, escalation logic, and institutional policies.
258
259### Who remains accountable for clinical decisions?
260
261Clinical accountability remains with the health system and its clinical governance model.
262
263deepc provides infrastructure to deploy, monitor, route, and govern AI workflows, but AI outputs should be embedded into approved clinical processes with appropriate human review, escalation logic, and institutional oversight.
264
265### How does deepc support clinical adoption?
266
267Clinical adoption depends on trust, workflow fit, governance, and visible value.
268
269deepc supports adoption by embedding AI into real workflows, reducing unnecessary friction, and enabling monitoring of usage, performance, and impact. When AI appears inside the systems teams already use, it is easier for clinicians to trust, easier for operations to scale, and easier for leadership to understand where value is being created.
270
271### Who designs the workflow?
272
273Workflow design is collaborative.
274
275deepc works with the health system's clinical, operational, technical, and governance stakeholders to define triggers, inputs, outputs, routing, review points, escalation logic, and monitoring requirements.
276
277### Can workflows vary by department or site?
278
279Yes. Different sites and departments may need different routing logic, integrations, governance requirements, and user experiences.
280
281The value of infrastructure is that these differences can be configured on a shared foundation rather than built as disconnected one-off projects.
282
283---
284
285## Category: Governance and evidence
286
287### How does deepc support AI governance?
288
289deepc provides infrastructure for monitoring, auditability, oversight, and evidence capture across deployed AI workflows.
290
291This helps health systems understand what is running, where it is running, how it performs, how it is used, and what governance actions have been taken.
292
293### Why does governance need to be part of the infrastructure?
294
295Governance cannot scale if every AI workflow has its own disconnected monitoring and audit process.
296
297A shared governance layer helps institutions manage AI consistently across departments, vendors, models, agents, and workflows.
298
299### What can be monitored in production?
300
301Depending on the workflow, deepc can support monitoring of usage, adoption, performance, workflow status, drift signals, incidents, audit events, and evidence trails.
302
303The goal is to make AI workflows observable and governable in routine care.
304
305### Can we evaluate AI performance in our own environment before scaling?
306
307Yes. Health systems often need to understand how an AI capability performs in their own environment before broad rollout.
308
309deepc can support evaluation and deployment workflows that help institutions review performance, workflow fit, operational impact, and governance requirements before scaling.
310
311### Can leadership see what AI is running across the organization?
312

313That is a core part of the infrastructure value.
314
315Health systems need an operational view of AI workflows in production, including adoption, incidents, performance, evidence, and value.
316
317### Who should own AI governance inside the health system?
318
319Ownership usually spans multiple functions: clinical leadership, IT, data protection, quality, compliance, operations, and executive sponsors.
320
321deepc does not replace institutional governance. It provides infrastructure that helps those stakeholders monitor, review, and manage AI workflows consistently.
322
323### How does deepc support auditability?
324
325deepc can support evidence trails around workflow execution, system events, monitoring activity, governance actions, and operational decisions.
326
327The exact audit scope depends on the workflow, deployment model, and institutional requirements.
328
329### Does deepc support regulatory oversight?
330
331deepc is designed around the governance expectations health systems are accountable to, including auditability, safety oversight, evidence, and institutional review.
332

333Specific regulatory responsibilities depend on the workflow, technology, region, and implementation model.
334
335### How does deepc help with drift or performance concerns?
336
337AI workflows need ongoing observation after deployment.
338
339deepc can help surface signals related to performance, drift, incidents, and workflow behavior so teams can review and respond through appropriate governance processes.
340
341### Can AI workflows be reviewed, paused, or changed after deployment?
342
343AI workflows should not be treated as static once deployed.
344
345Depending on the implementation, governance teams may need to review workflow behavior, adjust thresholds or routing logic, pause workflows, update policies, or trigger additional validation. deepc's infrastructure is designed to support that operational control layer.
346
347### Can deepc help create evidence for internal committees?
348
349Yes. Governance committees need evidence about what has been deployed, how it is used, how it performs, and what controls are in place.
350
351deepc helps make this evidence easier to collect, review, and operationalize.
352
353### How does deepc support safe scaling?
354
355Safe scaling requires repeatable integration, controlled deployment, monitoring, auditability, and clear governance.
356
357deepc helps provide that foundation so scaling AI does not mean multiplying unmanaged operational risk.
358
359---
360
361## Category: Security and data protection
362
363### How does deepc handle patient data?
364
365Data handling is defined around the health system's security, privacy, and deployment requirements.
366
367deepc is designed so AI workflows can operate within institutional boundaries, security policies, and approved data-handling models.
368
369### Does patient data leave the institution?
370
371There is no one-size-fits-all answer because deployment architecture depends on the workflow and the institution's requirements.
372
373deepc works with health systems to define approved data flows, processing locations, retention rules, and security controls before deployment.
374
375### How does deepc reduce repeated security review?
376
377A reusable infrastructure layer means security, integration, monitoring, and governance patterns can be reviewed once and reused across additional workflows.
378
379This can reduce the burden of repeating the entire review process for every new AI capability.
380
381### Does deepc support identity and access control?
382
383deepc can integrate with existing identity and access-control approaches so AI workflows fit into the institution's operational and security environment.
384
385Access control requirements are defined during implementation.
386
387### What data is logged and retained?
388
389Logging and retention depend on the deployment model and workflow requirements.
390
391In general, AI infrastructure should capture enough operational and audit information to support monitoring, governance, and incident review while aligning with institutional privacy, security, and retention policies.
392
393### How does deepc handle vendor risk?
394
395Health systems increasingly work with multiple AI vendors and technologies. deepc helps reduce operational complexity by providing an infrastructure layer for deployment, monitoring, governance, and evidence.
396
397Vendor-specific legal, regulatory, and technical requirements still need to be handled as part of the overall deployment process.
398
399### How does deepc support data protection requirements?
400
401deepc works with health systems to align deployment and data handling with local requirements, institutional policies, and applicable data protection frameworks.
402
403The exact configuration depends on geography, architecture, data flows, and workflow design.
404
405### Can deepc operate inside institutional boundaries?
406
407deepc is designed to support deployment models that respect institutional security and data-handling requirements.
408
409The exact architecture should be reviewed with the health system's IT, security, and data protection teams.
410
411### What should our CISO or DPO evaluate?
412
413They should evaluate data flows, identity and access control, hosting model, subprocessors, auditability, encryption, logging, retention, incident handling, and how additional workflows reuse the approved architecture.
414
415---
416
417## Category: AI capabilities and future workflows
418
419### What kinds of AI capabilities can deepc support?

420
421deepc can support commercial AI models, in-house AI, clinical decision support, triage, reporting support, documentation support, quality review, operational routing, governance monitoring, and agentic workflows.
422
423The exact workflow is configured with the health system.
424
425### Can deepc deploy commercial AI models?
426
427Yes. Commercial AI models can be deployed through deepc as part of governed clinical workflows, subject to regulatory, technical, contractual, and customer requirements.
428
429### Can deepc support in-house or home-grown AI?
430
431Yes. deepc can help operationalize in-house or home-grown AI capabilities by connecting them into the same infrastructure for deployment, monitoring, governance, and workflow integration.
432
433This does not mean deepc is an AI training infrastructure provider.
434
435### Does deepc train AI models?
436
437deepc's core role is clinical AI infrastructure, not model training infrastructure.
438
439The platform can support commercial, in-house, and agentic AI workflows, but the main value is making those capabilities deployable, integrated, observable, and governable in routine care.
440
441### Can deepc support AI agents?
442
443Yes. Agentic workflows are part of the broader infrastructure direction.
444
445Agents still need integration, security, workflow context, monitoring, auditability, and governance. deepc's role is to help health systems operationalize such workflows safely in their environment.
446
447### Can deepc support foundation-model based workflows?
448
449Yes, where appropriate and governed.
450
451Foundation-model based workflows may involve summarization, documentation, routing, retrieval, reasoning support, or operational assistance. They still require security, integration, monitoring, and institutional governance.
452
453### How future-proof is deepc?
454
455The infrastructure approach is designed to support a changing AI landscape.
456
457As new models, agents, and workflow patterns emerge, health systems should not need to rebuild the operating model from scratch.
458
459### Does deepc create vendor lock-in?
460
461deepc is designed around vendor-neutral infrastructure.
462
463The goal is to help health systems avoid being locked into a single AI model vendor, workflow pattern, or point solution architecture.
464
465### Can multiple AI vendors run on the same foundation?
466
467Yes. That is one of the core reasons for an infrastructure layer.
468
469Different AI models and vendors can be operationalized through shared deployment, monitoring, and governance patterns where clinically and technically appropriate.
470
471---
472
473## Category: Procurement and partnership
474
475### Who typically buys deepc?
476
477deepc is relevant for executive, clinical, technical, operational, and governance stakeholders.
478
479Typical buyers and sponsors may include CEOs, CIOs, CMIOs, CDIOs, CFOs, clinical transformation leaders, service-line leaders, AI governance teams, and innovation leaders.
480
481### Where should a health system start?
482
483Many health systems start with one or a few priority workflows.
484
485The first workflow can establish the integration and governance foundation. Additional workflows can then reuse the same infrastru

485cture.
486
487### Is deepc bought as infrastructure or as a workflow solution?
488
489The strategic value is infrastructure.
490
491A health system may start with a specific workflow, but the long-term value comes from reusing the same foundation across many workflows, departments, sites, and AI capabilities.
492
493### How should procurement compare deepc with point solutions?
494
495Point solutions should be evaluated for the value of a specific use case.
496
497deepc should be evaluated as infrastructure: how it reduces repeated implementation work, supports governance, enables multiple AI workflows, and creates a scalable operating model for AI across the organization.
498
499### How does implementation work?
500
501deepc works with the health system to understand existing systems, target workflows, governance requirements, deployment architecture, security posture, and value priorities.
502
503The goal is to configure workflows around the institution's environment, not force the institution into a generic product flow.
504
505### What determines the scope of a deepc engagement?
506
507Scope depends on the number of workflows, systems, sites, deployment requirements, governance needs, and level of integration required.
508
509Many organizations start with a focused workflow and expand once the infrastructure foundation is proven.
510
511### What internal stakeholders should be involved?
512
513Relevant stakeholders usually include clinical leadership, IT, security, data protection, AI governance, operational leadership, procurement, finance, and the teams responsible for the first target workflow.
514
515The exact group depends on the workflow and deployment scope.
516
517### How should we evaluate whether deepc is right for us?
518
519Ask whether your organization expects to deploy multiple AI capabilities over time.
520
521If yes, the key question is not only "Which model should we buy?" but "What infrastru

521cture will let us deploy, monitor, govern, and scale many AI workflows safely?"
522
523### Can we start small and expand later?
524
525Yes. This is often the most practical approach.
526
527Starting with one workflow can create the technical and governance foundation for broader expansion.
528
529### What makes a good first workflow?
530
531A good first workflow is clinically or operationally meaningful, has clear ownership, connects to existing systems, has measurable value, and can establish reusable infrastructure patterns for future workflows.
532
533### How collaborative is implementation?
534
535Implementation is collaborative.
536
537deepc works with clinical, operational, technical, and governance stakeholders to configure workflows around the institution's real systems and operating model. The goal is not to force a generic product flow, but to operationalize AI in a way that fits the health system's environment.
538
539---
540
541## Category: AI ecosystem and partners
542
543### Can AI vendors work with deepc?
544
545Yes. AI vendors may work with deepc to make their capabilities deployable into health-system workflows through deepc's infrastructure.
546
547The goal is to reduce integration friction and make AI capabilities easier for health systems to operationalize and govern.
548
549### Does deepc compete with AI model vendors?
550
551deepc is primarily infrastructure. It helps health systems deploy and govern AI workflows, including workflows that may use third-party AI models.
552
553This can complement AI model vendors by making their capabilities easier to bring into real clinical environments.
554
555### What does deepc expect from AI vendors?
556
557Requirements depend on the workflow, market, and customer environment.
558
559Typical considerations include regulatory status, technical integration, performance evidence, security review, support expectations, documentation, and customer-specific deployment requirements.
560
561### Can research teams or universities bring models to deepc?
562
563Yes. deepc can support the operationalization of in-house or research-developed AI capabilities where appropriate.
564
565Clinical production use requires careful attention to regulatory status, governance, validation, deployment architecture, and institutional approval.
566
567### Does deepc support non-regulatory cleared models?
568
569For clinical production use, regulatory and institutional requirements must be respected.
570
571Research, evaluation, or non-production contexts may have different requirements, but those must be clearly separated from routine clinical deployment and configured with appropriate governance.
572
573### How does deepc help AI vendors reach health systems?
574
575Health systems often struggle with repeated integration and governance work for each AI vendor.
576
577By connecting through deepc infrastructure, vendors can fit into a broader deployment and governance model that health systems can scale.
578
579---
580
581## Category: Working with deepc
582
583### What happens after we contact deepc?
584
585The next step is usually a discussion about your organization's AI strategy, existing systems, priority workflows, deployment requirements, security posture, and governance expectations.
586
587From there, deepc can help define a practical starting point.
588
589### What information should we prepare before a first discussion?
590
591Helpful information includes target workflows, current systems, key stakeholders, existing AI initiatives, security requirements, deployment preferences, governance processes, and the business or clinical outcomes you want to improve.
592
593### Do we need a full AI strategy before starting?
594
595No. Many organizations begin with a focused workflow and build from there.
596
597However, it helps to understand whether your organization expects to deploy multiple AI workflows over time, because that is where infrastru

597cture becomes strategically important.
598
599### How do we avoid overbuilding?
600
601Start with a meaningful workflow, but design the foundation so it can be reused.
602
603The goal is not to build a massive program before value is proven. The goal is to avoid one-off decisions that make the second, third, and tenth workflow harder than necessary.
604
605### How do we know whether we are ready?
606
607You are likely ready if your organization is evaluating multiple AI capabilities, struggling with fragmented pilots, facing repeated integration and security reviews, or trying to create a governance model for AI in routine care.
608
609### What is the best way to engage?
610
611Start with a strategic and technical conversation.
612
613deepc can help identify where infrastructure will create the most leverage, which workflow is a practical starting point, and what stakeholders should be involved.
614`;function H(t){return t.toLowerCase().replace(/[^a-z0-9]+/g,"-").replace(/(^-|-$)/g,"")}function N(t){const c=t.split(/\r?\n/),r=[];let o=null,i=null,n=[];const a=()=>{i&&o&&(i.answer=n.join(`
615`).trim(),o.items.push(i)),i=null,n=[]};for(const s of c){const l=s,d=/^##\s+Category:\s+(.+?)\s*$/.exec(l),p=/^###\s+(?:\d+\.\s+)?(.+?)\s*$/.exec(l);if(d){a();const h=d[1].trim();o={name:h,slug:H(h),items:[]},r.push(o);continue}if(p&&o){a(),i={question:p[1].trim(),answer:""};continue}if(/^---\s*$/.test(l)){a();continue}i&&n.push(l)}return a(),r.filter(s=>s.items.length>0)}const u=N(j),W=u.flatMap(t=>t.items),S={"Clinical AI infrastructure basics":"Basics","Strategy and transformation":"Strategy","Value and ROI":"Value & ROI","Integration and deployment":"Integration","Clinical workflow adoption":"Workflows","Governance and evidence":"Governance","Security and data protection":"Security","AI capabilities and future workflows":"AI capabilities","Procurement and partnership":"Procurement","AI ecosystem and partners":"Ecosystem","Working with deepc":"Working with deepc"},z=`${g}/faq`,D={"@context":"https://schema.org","@type":"FAQPage",mainEntity:W.map(t=>({"@type":"Question",name:t.question,acceptedAnswer:{"@type":"Answer",text:t.answer}}))},O={"@context":"https://schema.org","@type":"BreadcrumbList",itemListElement:[{"@type":"ListItem",position:1,name:"Home",item:`${g}/`},{"@type":"ListItem",position:2,name:"FAQ",item:z}]},$=()=>{const[t,c]=m.useState(""),r=t.trim().toLowerCase(),o=m.useMemo(()=>r?u.map(n=>{if(n.name.toLowerCase().includes(r))return n;const s=n.items.filter(l=>`${n.name} ${l.question} ${l.answer}`.toLowerCase().includes(r));return{...n,items:s}}).filter(n=>n.items.length>0):u,[r]),i=o.reduce((n,a)=>n+a.items.length,0);return e.jsxs("div",{className:"theme-deepcos min-h-screen bg-background text-foreground",children:[e.jsx(w,{collectionKey:"page.faq",path:"/faq"}),e.jsxs(f,{children:[e.jsx("script",{type:"application/ld+json",children:JSON.stringify(D)}),e.jsx("script",{type:"application/ld+json",children:JSON.stringify(O)})]}),e.jsx(y,{}),e.jsxs("main",{children:[e.jsx(v,{eyebrow:"LEARN",title:"Frequently asked questions",subtitle:"Answers for health system leaders evaluating clinical AI infrastructure - how to integrate, deploy, govern, and scale AI workflows safely across existing systems."}),e.jsx("section",{className:"border-y border-border bg-background",children:e.jsx("div",{className:"container py-5",children:e.jsxs("div",{className:"mx-auto max-w-4xl",children:[e.jsx("label",{htmlFor:"faq-search",className:"sr-only",children:"Search frequently asked questions"}),e.jsxs("div",{className:"relative",children:[e.jsx("input",{id:"faq-search",type:"search",value:t,onChange:n=>c(n.target.value),placeholder:"Search questions about ROI, governance, integration, security, agents...",className:"w-full rounded-full border border-border bg-background px-5 py-3 pr-12 text-sm md:text-base text-foreground placeholder:text-muted-foreground/70 outline-none transition-colors focus:border-primary/50 focus:ring-2 focus:ring-primary/15"}),t&&e.jsx("button",{type:"button",onClick:()=>c(""),className:"absolute right-3 top-1/2 -translate-y-1/2 rounded-full px-3 py-1 text-xs font-medium text-muted-foreground hover:bg-muted hover:text-foreground transition-colors","aria-label":"Clear FAQ search",children:"Clear"})]}),r&&e.jsx("p",{className:"mt-3 text-sm text-muted-foreground","aria-live":"polite",children:i===1?"1 matching question":`${i} matching questions`})]})})}),e.jsx("nav",{"aria-label":"FAQ categories",className:"border-y border-border bg-muted/30",children:e.jsxs("div",{className:"container py-4 flex flex-wrap items-center gap-2 text-sm",children:[e.jsx("span",{className:"mr-2 text-[11px] uppercase tracking-eyebrow text-muted-foreground font-medium",children:"Jump to"}),o.map(n=>e.jsx("a",{href:`#${n.slug}`,className:"inline-flex items-center rounded-full border border-border bg-background px-3 py-1.5 text-xs md:text-sm font-medium text-foreground

615/70 transition-colors hover:border-primary/40 hover:bg-primary/5 hover:text-primary",children:S[n.name]??n.name},n.slug))]})}),e.jsx("section",{className:"container py-20 md:py-28",children:e.jsx("div",{className:"mx-auto max-w-4xl space-y-20",children:r&&o.length===0?e.jsxs("div",{className:"mx-auto max-w-2xl py-20 text-center",children:[e.jsx("p",{className:"eyebrow",children:"No results"}),e.jsx("h2",{className:"display mt-3 text-2xl text-foreground",children:"No matching FAQ found."}),e.jsx("p",{className:"mt-4 text-base text-muted-foreground",children:"Try searching for integration, governance, security, ROI, workflows, agents, or deployment."}),e.jsx("button",{type:"button",onClick:()=>c(""),className:"mt-6 inline-flex rounded-full border border-border px-4 py-2 text-sm font-medium text-foreground hover:bg-muted transition-colors",children:"Clear search"})]}):o.map(n=>e.jsxs("section",{id:n.slug,"aria-labelledby":`${n.slug}-heading`,className:"scroll-mt-28",children:[e.jsx("h2",{id:`${n.slug}-heading`,className:"display text-subsection text-foreground",children:n.name}),e.jsxs("p",{className:"mt-2 text-sm text-muted-foreground",children:[n.items.length," questions"]}),e.jsx(b,{type:"multiple",className:"mt-8",children:n.items.map((a,s)=>e.jsxs(k,{value:`${n.slug}-${s}`,className:"border-border",children:[e.jsx(I,{className:"text-left text-base md:text-lg font-medium text-foreground hover:no-underline",children:e.jsx("h3",{className:"m-0",children:a.question})}),e.jsx(A,{children:e.jsx("div",{className:"prose prose-neutral dark:prose-invert max-w-none prose-p:text-foreground/80 prose-a:text-primary text-base leading-relaxed",children:e.jsx(T,{remarkPlugins:[q],children:a.answer})})})]},s))})]},n.slug))})}),e.jsx(x,{})]}),e.jsx(C,{})]})};export{$ as default};
616//# sourceMappingURL=FAQ-WYNl-JIB.js.map