Integration Administrator
You connect Veona to the outside world. You manage the facility’s external integrations — wallets and online payments, insurance e-claims, and time-attendance devices — and the read-only records export that lets authorised partners pull a patient’s record over a standard interface. These are powerful connections, so configuring providers and their credentials is a privileged, deny-by-default capability.
BYOK means Bring Your Own Keys — the facility supplies its own provider credentials, which Veona stores encrypted. FHIR is the international standard for exchanging health records. An e-claim is an insurance claim submitted electronically.
What you can do
Section titled “What you can do”As an integration administrator, you can:
- Configure providers — set up each integration, store its encrypted credentials, toggle it on or off, and test the connection.
- Manage online payments and wallets — including diaspora top-up links for relatives paying from abroad.
- Submit insurance e-claims — electronic claim submission and eligibility checks where the payer integration is enabled.
- Read time-attendance — view and map staff clock data from attendance devices.
- Run the accounting export — push billing into the general ledger.
- Manage API keys — create and revoke the scoped, programmatic credentials a partner system uses, shown masked.
- Export records to partners — provide the read-only records export of a single resource or a patient’s whole record to an authorised partner.
What you cannot do
Section titled “What you cannot do”The integration-administrator role is scoped to integrations and interoperability. It is not a clinical role — you do not write notes, results or prescriptions, and the records export is read-only. Stored credentials and API-key secrets are never shown back to you once saved; keys are always displayed masked. The records export is a deliberate disclosure of patient data to an outside system, so every read is logged as such — it is granted to this role only, never as a clinician default.
Where you work
Section titled “Where you work”| Screen | Module | What you do there |
|---|---|---|
| Providers | Integrations | Configure and test integrations |
| Payments & Wallets | Integrations | Online payments, diaspora top-up links |
| Insurance Claims | Integrations | Submit e-claims, run eligibility |
| Time Attendance | Integrations | Read and map clock data |
| API Keys | Integrations | Create and revoke partner credentials |
| Records Export | Integrations | Read-only partner records export |
A typical day
Section titled “A typical day”- Open Providers (Integrations) and check each integration is connected — test any that look off.
- Set up a new payment or wallet provider, storing its credentials, and confirm a test charge.
- Where insurance is integrated, run eligibility and submit e-claims for the day’s payers.
- Provision or revoke an API key for a partner system, handing over the masked credential securely.
- Authorise a partner’s records export for a patient where consent and entitlement are in place — each read is logged.
Related guides
Section titled “Related guides”- How-to: Patient wallet top-up and pay, Submit an insurance claim, Staff time attendance, Export a patient record
- Module: Integrations
- Reference: Records export