Connect your records system
Link a CRM, ERM, EMR or point of sale so tickets follow each visit and staff call people from the records they already use.
What you get
- A ticket follows each visit. Checking someone in, in your system, creates their ticket for the first stop, such as Consultation or Cashier.
- Staff call the next person from the visit or encounter, into the room they picked, and send them on to the next stop when it ends.
- Paid bills clear the payment gate, and bookings made in your system are placed by booked time on arrival.
- A desk bar inside your system for reception, cashier and other departments.
This works with any system that supports Klargy Connect. Serenity Health EMR is a complete, working example, and the steps below are the same for every system.
Before you start
- A Klargy plan that includes Connected systems (CRM, POS, EMR). Pro includes it.
- A Klargy admin, and someone who can manage integrations in your system.
- Nothing else in Klargy yet: your system can create the locations and services for you. If you set them up in Klargy first, the Outpatient clinic template is the quickest way for a clinic.
- Staff in Klargy with the same email addresses they use in your system, so they are matched automatically.
1. Create the connection in Klargy
- In Klargy, go to Integrations. Under System connections, press Connect a system.
- Name it after the system, for example “Serenity”, and press Create API key.
- Klargy shows the API key once. Copy it and keep it somewhere safe until the next step, then press I’ve saved it.
2. Connect from your system
In your system’s integration settings, a connection that supports Klargy Connect asks for the same few things:
- Your Klargy Workspace URL, for example
https://yourclinic.klargy.com, and the API key from step 1. A Test connection button should show your Klargy organisation’s name. - Registration: your system tells Klargy where to send queue events. This is done once per organisation.
- Catalogue: your system sends its locations, clinics or departments, and staff to Klargy. Publish again whenever they change.
3. Match locations and services
A ticket for a service that isn’t matched is refused, so each place in your system needs its Klargy equivalent.
| Klargy | In your system | Notes |
|---|---|---|
| Locations | Facilities or branches | One to one. Can be created from your system. |
| Services | Clinics, departments or counters | Cashier, laboratory and pharmacy are services too. |
| Desks & rooms | Optional | Rooms live in Klargy; staff pick theirs after signing in. |
| Staff | Users or practitioners | Matched by email the first time they open the desk. Match by hand in Klargy if the emails differ. |
You can match from Klargy too: press Match on the connection under Integrations. Auto-match shows the matches it suggests and why, and Apply saves them.
4. Check it end to end
- In your system, check someone in. A ticket appears in Klargy’s queue for the matched service.
- As a member of staff, pick your room, open the visit and call the person. The display screen announces the ticket and the room.
- End the visit and choose where they go next. Their ticket moves to that service, and their ticket page says where to go.
If something doesn’t work
| What you see | What to do |
|---|---|
| Test connection fails | Check the Workspace URL has no extra path, and that the key was copied whole. Create a new key if in doubt. |
| “System connections aren’t on your plan” | Upgrade from Billing, or ask your Klargy contact to add Connected systems to your plan. |
| Catalogue shows “Not published” | Publish the catalogue again from your system, after registering. |
| Check-in creates no ticket | The service isn’t matched yet. Match it, or press Auto-match. |
| A staff call goes nowhere | They haven’t picked a room, or their email differs between the two systems. Match them under Staff. |
Connect your own system
Klargy Connect is an open API: issue tickets for your own visits or bookings, call and send people on, embed the desk in your app and get signed events back. There are TypeScript and Python libraries, and a sandbox workspace to test against. See Webhooks and the API, or talk to us and we’ll help you build the connection.