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.
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.
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.