The answers below clarify CuriQ's role, access model, integration approach and human-review boundaries.
What is in scope for CuriQ, and what is not?
CuriQ is an intelligence and workflow orchestration layer for hospitals. It connects context, supports decisions, automates approved workflows and improves visibility. It does not replace ERP, CRM, HIS, EMR/EHR, laboratory, radiology, pharmacy or billing systems; it works with them.
Will CuriQ be accessible from a patient's home?
Yes. Selected patient-facing services can be made available remotely when enabled by the hospital—for example, pre-visit intake, document upload, education, reminders, follow-up and recovery monitoring. Access, consent and available features remain controlled by the hospital.
How can CuriQ connect to the hospital website or mobile app?
CuriQ can be presented through a hospital-branded portal, a secure redirect, an embedded journey, single sign-on or API-based integration. The final approach depends on the hospital's digital architecture, security standards and patient-experience design.
Does CuriQ make the final clinical decision?
No. CuriQ provides evidence-based assistance, highlights missing information and explains recommendations. Authorised clinicians remain responsible for review, approval and patient-care decisions.
Does the demo use real patient data?
No. The scenarios, names, scores and recommendations in this conference demo are illustrative. They are designed to explain the workflow and are not medical advice or production results.
Can CuriQ work with the hospital's existing technology?
That is the intended operating model. CuriQ is designed to connect to approved hospital systems and data sources using secure integration patterns, while the existing source systems continue to own official transactions and records.
