The questions people actually ask.

Ordered by how often they come up, not by how well they reflect on us.

Does CBS replace our hospital information system?: No, and it is not designed to. The HIS stays the system of record. CBS reads from it over HL7 v2 or FHIR R4 and writes back to it. A hospital that stops using CBS keeps its data where it always was.
Can the AI make a clinical decision on its own?: No. There is no configuration in which a model writes to a patient record, contacts a patient, or closes a follow-up. Every output is presented for a clinician to accept, change or reject, and that decision is logged against their name.
Is CBS Health a registered medical device?: No. It is not registered with the CDSCO, the MHRA or the FDA, and it is positioned as clinical decision support rather than as a diagnostic device. If your intended use would place it in a regulated class, that is a conversation to have before deployment, not after.
Where does patient data live?: Wherever the deployment is provisioned. CBS is deployed per region, and data residency is a deployment decision rather than a vendor default. Indian deployments keep data in India.
What happens to data we send to a language model?: See the Responsible AI page for the current answer, which depends on which model the deployment is configured against. It is a question with a real answer per deployment and no honest single answer across all of them.
Which languages does the interface support?: Nine: English, Hindi, Marathi, Telugu, Kannada, Tamil, Malayalam, Malay and Chinese. The clinical application is fully translated. This public website is currently English-only.
How long does integration take?: For a solo practitioner uploading documents, the same day. For a multi-specialty hospital with an interface engine, plan for the integration conversation to be longer than the clinical one.
Can we see it against our own data?: Against your own anonymised case, yes. A demonstration on synthetic data proves the interface; a demonstration on a case you already know the answer to proves whether the synthesis is any good.

For developers and integrators

What exists right now.

These are live links into this deployment, not brochure pages.

API documentation

The OpenAPI reference for this deployment, generated from the running application rather than maintained separately.

Open the reference

System status

The liveness endpoint for this deployment.

Check status

FHIR R4 interoperability

CBS reads and writes FHIR R4 resources. The resource coverage and the HL7 v2 mappings are covered in the integration call rather than published here.

Ask about integration

Not yet published

What is missing from this page.

There is no clinical knowledge base, no implementation guide and no case study library here yet, because none of them exist. A resources page padded with links to pages that turn out to be a form is worse than a short one.

If you need something that would have been in one of those — an implementation plan, a reference from a comparable site, a written answer to a security questionnaire — ask, and you will get the real thing rather than a download.

Ask for it directly