Skip to main content

Connect the services
your clinic relies on.

Bring messaging, payments, clinical sources, and records into the clinic workflow. Keep each connection’s purpose, requirements, and outcome in view.

Connection availability depends on provider approval and setup.

Connections around a visit
MessagingPaymentsClinical sources
Bractis clinic workflowOne originating action
Provider responseRecord exchange

Provider setup and consent define each connection.

Explore what
each connection supports.

All six integration areas are included below. Open the scope details for the current catalog status and requirements before planning a rollout.

Connect the visit to the next step.

Bring communication and financial outcomes back to the visit, with provider status visible.

WhatsApp, SMS, and email

Appointment reminders, signed records, follow-up journeys, and human escalation with consent and template governance.

Scope and requirements: WhatsApp, SMS, and email

Catalog status: Pilot boundary. Provider category: Provider-dependent.

Provider approval, delivery, opt-out, and outage states remain visible. Essential care records are not lost when messaging fails.

Payments and receipts

Clinic charges, receipts, cash/manual payments, gateway callbacks, refunds, and day-close reconciliation.

Scope and requirements: Payments and receipts

Catalog status: Pilot boundary. Provider category: Gateway-dependent.

Recorded payment is separate from gateway capture. Unknown provider outcomes require reconciliation before retry.

Bring sources into clinical review.

Keep clinical content and generated drafts connected to their sources and the clinician’s review.

Clinical knowledge sources

Medication terminology, allergy context, safety checks, and clinical content with source and version.

Scope and requirements: Clinical knowledge sources

Catalog status: Governed. Provider category: Reviewed providers.

Commercial inputs cannot alter clinical ranking. Rules and content require clinical governance before live use.

AI, handwriting, and OCR

Consent-aware capture, source-linked drafts, correction, evaluation, cost controls, and degraded modes.

Scope and requirements: AI, handwriting, and OCR

Catalog status: Planned. Provider category: Model gateway.

No autonomous diagnosis or prescribing. Generated content remains visibly marked until reviewed.

Carry records and services forward.

Keep consent, exchange, and patient choice explicit when care crosses systems or providers.

ABDM and FHIR

Patient-consented identity, care context, mapping, exchange, and reconciliation designed as one lifecycle.

Scope and requirements: ABDM and FHIR

Catalog status: Planned. Provider category: Interoperability layer.

ABHA is optional for care. Production and certification claims wait for the documented release gates.

Pharmacy and laboratory network

Patient-choice comparison, fulfilment states, result ingestion, quality management, and complaints.

Scope and requirements: Pharmacy and laboratory network

Catalog status: Planned. Provider category: Verified local partners.

Choice is independent of clinical order entry. Sponsorship and ranking criteria are disclosed.

Local partner verification is a rollout requirement. This listing does not establish that any provider is currently verified or available.

Keep the request
and its outcome distinct.

A queued message, recorded payment, or requested exchange is one step in the workflow. Follow the provider response before treating the action as complete.

Explore connection recovery
  1. 01Record the requested action
  2. 02Show pending, confirmed, or failed status
  3. 03Reconcile unknown outcomes before retrying

Agree the setup
before connecting live work.

Confirm the provider, supported actions, consent, access, and handling of failures. Clinical sources require governance, generated content requires review, and record exchange has its own release requirements.

Plan your evaluation

Questions about
connecting your clinic.

Review availability and responsibilities for your intended workflow.

Are all of these integrations live?

No. Bractis is preparing for launch. The directory presents the full planned scope with catalog status and requirements for each connection. Confirm availability and supported actions with Bractis before rollout.

Does a provider category identify a confirmed vendor?

No. Labels such as model gateway or reviewed providers describe the category of connection. Vendor selection, approval, verification, and configuration need to be confirmed for the agreed scope.

Is ABHA required to receive care?

No. ABHA is optional for care. Record exchange requires separate consent and the relevant interoperability release requirements.

What happens when a provider does not respond?

The outcome remains pending or unknown until it can be confirmed. Preserve the originating action and reconcile its status before retrying, especially for payments or other consequential actions.

Can we discuss a connection that is not listed?

Yes. Describe your workflow and the service involved through the contact form. Bractis can discuss requirements; an inquiry does not imply that the connection is available or committed.

Tell us what
your clinic needs to connect.

Start with the workflow, the service, and the outcome your team needs to follow.

Talk to Bractis