Understand Abi products
Abi helps partners make health guidance and consultations available inside their existing product. The integration you choose changes the presentation and control surface, but the core service model remains the same.
The shared service model
Section titled “The shared service model”Your system creates or identifies the user, assigns the service context agreed for the partnership, and controls access through subscriptions. A user with active access can use the services enabled for them, such as consultation workflows or Health Navigator.
| Concept | Role in the product |
|---|---|
| User account | The Abi record representing one of your customers. |
| Subscription | The period in which that user can access Abi. |
| Consultation | A medical question and its service lifecycle. |
| Health Navigator | Conversational health guidance and configured signposting. |
| Prescription request | A structured prescription and indication-survey workflow where enabled. |
Choose how to deliver the experience
Section titled “Choose how to deliver the experience”- GoApp embeds Abi’s consultation experience in a web product.
- The REST API lets your backend manage users, access, and supported workflows directly.
- The React Native SDK delivers a native mobile consultation experience.
These options can be combined when agreed with Abi. For example, a backend can manage user access through the API while a web application presents GoApp to the user.
Keep product and integration facts separate
Section titled “Keep product and integration facts separate”Use the guides to understand the product model and the choices available to your users. Use the API reference for current endpoint paths, fields, schemas, authentication, and responses.