Get Kaddio clinic analytics in plain language, with patient PII masked at ingestion. Connect Kaddio to Ronja in four steps. Once connected, Ronja maps your appointments, billing, and operational journal metadata into a governed analytics layer. Patient names, personnummer, and clinical content never leave Kaddio. Then anyone on the clinic team can ask scheduling, no-show, and revenue questions and get answers traced back to source.
How to analyze Kaddio data with Ronja
Setup is two parts: a one-time admin step in Kaddio to enable the API module, then a few minutes to paste a personal API token into Ronja.
Step 1: Connect Kaddio to Ronja
Just ask Ronja to connect to Kaddio. Ronja surfaces a form to paste your personal Kaddio API token. No vendor consent screen, no OAuth redirect. Ronja stores the token securely. Your token is tied to your Kaddio role and permissions, so Ronja only sees the data you yourself are allowed to see.
Step 2: Let Ronja map your operational data
Ronja's agents map appointments, billing, invoices, practitioner availability, and journal metadata into structured tables. Patient names, personnummer, and clinical journal content are masked at ingestion and never leave Kaddio. Ronja works with operational metadata only, so you can ask "how many appointments this week" not "what was discussed in the appointment". Governance is enforced in software, not via prompts.
Step 3: Ask your first question in plain language
With your data mapped, ask anything operational. "What's our no-show rate by practitioner this month?" "Which insurance providers are slowest to pay?" Ronja runs the query against the mapped tables and shows exactly which Kaddio records the answer came from. Every number traces to source. Every query is audit-logged in Ronja's governance layer.
Step 4: Combine Kaddio with the rest of your stack
Kaddio alone gives you practice operations data. Combined with Fortnox accounting (revenue reconciliation), marketing tools (referral campaign ROI), or your booking widget data (conversion analytics), it's transformative. Ronja unifies all your sources into a single governed layer, so cross-system queries respect the same PII masking and audit trail.
Just ask
Questions you can answer with Kaddio data
Ask in plain language. Get answers traced to source. No analysts, no dashboards, no waiting.
What Kaddio data Ronja maps
When you connect Kaddio, Ronja's agents map the following operational data into its governed analytics layer. Clinical content stays in Kaddio.
- Appointments and bookings: scheduling data, no-shows, cancellations
- Clients: operational fields only (names and personnummer masked at ingestion)
- Invoicing and billing: amounts, payment status, insurance provider
- Journal metadata: entry count, type, practitioner, timestamp (clinical content NOT pulled)
- Practitioners: staff records, availability, workload metrics
Key takeaways
- Patient names, personnummer, and clinical journal content are masked at ingestion and never leave Kaddio
- Setup takes most teams under ten minutes once the admin has activated the Kaddio API module
- Ronja maps your operational data automatically. No schema definition needed
- Every query is audit-logged in Ronja's governance layer; access scoped to your Kaddio role
- Combines with Fortnox, marketing tools, and 100+ other sources with the same PII masking applied
Frequently asked questions
How long does it take to connect Kaddio to Ronja?
Before you start: your clinic admin must enable the API add-on module in Kaddio organisation settings, and you need to generate a personal API token in Kaddio under /my-profile. Most teams then complete the connection in under 10 minutes. Ronja stores the token, opens a session, and starts mapping operational data immediately.
What happens to patient PII and clinical notes?
Patient names, personnummer, and clinical journal content are masked at ingestion and never leave Kaddio. Ronja works with operational metadata only, so you can ask "how many appointments" not "what was discussed". Governance is enforced in software, not via prompts.
What Kaddio data does Ronja have access to?
Appointments and bookings (with no-shows and cancellations), de-identified client records, invoicing and billing data, journal entry metadata (count, type, practitioner, timestamp, not content), and practitioner availability. Access is scoped to whichever clinic and role your Kaddio token has rights to.
How is access governed?
Three layers. (1) The Kaddio API add-on must be explicitly enabled by a clinic admin. (2) Your personal API token is tied to your Kaddio role and permissions, so Ronja only sees what you can see. (3) Ronja's own governance layer audit-logs every query and enforces access control on top. Rate limited to two concurrent requests and five seconds of execution per ten-second window on the Kaddio side.
Does Ronja modify any data in Kaddio?
No. The connector reads operational metadata only into Ronja's own governed analytics layer. Your Kaddio records remain unchanged.
Can I combine Kaddio data with Fortnox or marketing tools?
Yes. Combining Kaddio billing data with Fortnox accounting for revenue reconciliation, or Kaddio referral sources with marketing tools to measure campaign ROI, are common use cases. All cross-system queries respect the same PII masking and governance enforcement.