Custom Zivver integration software for healthcare and government
Appfront builds the integration between your own system and Zivver. The software retrieves the message and attachments from your file, chooses the right security level for each recipient, sends via mail submission or the API, keeps accounts and groups in sync and writes every sent message back to the file. So nobody has to retype data from your system into an email window by hand any more.
What is Zivver integration software for secure email and account management?
A Zivver integration is software that lets your own system talk to the secure email platform. The integration composes the message from the data in your application, adds the right attachments, determines the security level required for each recipient, submits the message via mail submission or the API and records the status against the case or client.
Without an integration, secure email becomes manual work. An employee opens the file, copies the name and address, exports a PDF, opens Outlook, switches on secure email and chooses an access code. With a series of appointment confirmations, that happens again for every message. Documents go to the wrong address, the sending is not recorded anywhere in the file and afterwards there is no way to see who sent what.
We build this as custom software because your message flows come from your own systems and follow your own rules: which documents may be included, which level applies to a citizen service number (BSN), which sender belongs to which department. That logic lives in your EHR, case management system or CRM and in agreements with your data protection officer. A standard plug-in knows nothing about your fields, your templates or your record structure.
Building messages from your system
The integration pulls the recipient, template and attachments from your application and prepares a message from them, including a sender per department and attachments that exceed the email size limit.
Security level per recipient
For each message type and recipient, the software determines whether an access code, an SMS check or standard delivery is required, following the rules you have agreed with your privacy officer.
Status written back to the record
Offered, delivered, opened or failed: every status change is written back to the client, customer or case, with an audit log showing who sent which document and when.
How we build Zivver integration software for secure email and account management
We start with the messages you currently send by hand: which screen, which attachment and which recipient.
We walk through your sending moments: appointment confirmation, referral letter, invoice or decision. For each flow, we define which data must be included, which attachments belong with it and which security level applies.
We set up the foundation: sender addresses per department or shared mailbox, templates per message type, the recipient verification rules and the mapping of users and groups to accounts.
The employee clicks send in your own system. The integration builds the message, queues it, submits it, retries if something goes wrong and reports a failure.
We take the integrations live with your own keys, set up monitoring on the queue and error reports, and take over the management, logging and updates of the integration.
What Zivver integration software for secure email and account management actually does
The components below appear in almost every Zivver integration. Which ones you need depends on the message types you send and the systems where that data is stored.
Mail submission via SMTP
Messages from your application enter the platform through a dedicated SMTP user, so sending works without an employee having to open an email client.
Security level rules
For each message type, recipient type and attachment, you define which level applies, so sensitive documents never leave without an extra check.
Send queue with retries
Messages stay in the queue until they have been submitted. If something fails, a new attempt follows and the case handler is notified.
Account management via SCIM
New employees, name changes and leavers flow from your source system to accounts, aliases and groups, so licences and mailboxes stay accurate.
Attachments and large files
The integration adds PDFs and record documents directly from your system and converts files above the email size limit into a secure download.
Audit log and feedback
Every message sent, status change and recall is recorded on the right case or client, searchable by sender, recipient, period and message type.
Who we build Zivver integration software for secure email and account management for
The software is designed for organisations that send a lot of sensitive post digitally and where that post comes from a line-of-business application rather than from a mailbox.
Healthcare providers and mental health care
Appointment confirmations and referral letters come from the EHR. The key point is that every document sent is visible in the client record, including who sent it.
Municipalities and public service providers
Decisions and supporting documents belong to a case. Here, feeding the delivery status back to the case file is the most important part.
Educational institutions
Messages about pupils and students come from the student administration system. The key points are senders per location and account management at the start of each school year.
Accountants, lawyers and financial service providers
Annual accounts and case documents leave your practice system. The focus here is on attachments above the email size limit and on the audit log.
Technology and integrations
This page is about integrating your own system with Zivver for secure email. For secure email in healthcare, see our page on the ZorgMail integration; for information security in healthcare, our page on NEN 7510-compliant software; and you can read how we set up integrations under smart API integrations. You can read about our approach on custom software development.
Why Appfront for your Zivver integration for secure email and account management software?
A secure email integration is only as good as the rules behind it. That is what we build on: your message types, your senders and your record-keeping.
Secure email belongs in the workflow, not alongside it
Your staff keep working in your own system and press send there. That means no second administration of sent post and no more copying between the case file and the email client.
The security level is a rule, not a choice
If someone has to think about an access code for every message, they will get it wrong at some point. We build your rules into the integration, so the level follows from the message type and the recipient.
Feedback is half the work
A message that does not arrive or is not opened needs to stand out. The integration alerts the case handler and records it against the case or client.
Security and privacy for the Zivver integration for secure email and account management software
The integration contains names, address details, case numbers and attachments with medical or financial content. Access is role-based: a case handler sees their own messages, an administrator sees the queue and the error messages, and a privacy officer sees the audit log. Logging records who sent and recalled which document. Retention periods follow your policy; in healthcare, NEN 7510 applies alongside the GDPR.
The software runs in a European data centre, with encrypted storage and daily backups. Integrations with the secure email platform, your EHR, case management system or CRM use their own keys, which can be revoked per integration.
Frequently asked questions about the Zivver integration for secure email and account management software
Questions that administrators and privacy officers ask before they get started.
The integration connects your own system to the secure email platform. It takes the recipient, template and attachments from your application, determines the security level, submits the message via mail submission or the API, and writes the status back to the right client or case.
Yes. For sending from an application, the integration uses mail submission with a dedicated SMTP user, or the platform's available interfaces. The plug-in remains useful for individual messages that a member of staff writes themselves, but it is not needed for messages that your system sends automatically.
Yes. The platform offers a SCIM interface that lets you manage accounts, aliases and groups from a source system. We connect it to your HR system or directory, so new staff get an account straight away, a change of name is carried through and leavers are removed without any manual work by an administrator.
With rules you define in advance. For each message type, recipient type and attachment, the software decides whether standard sending is enough or whether an extra recipient check is needed. Those rules live in one place, can be changed without a new release and can be traced in the audit log.
The message stays in the queue and the integration tries again later. If it still doesn't go through, the case handler receives a notification with the reason: an incorrect address, a missing mobile number or an attachment that is too large. Nothing silently disappears from the queue.
Yes. For each department, location or functional mailbox, you define which sender address and which template apply, and who may send on behalf of that mailbox. The integration picks the right one based on the user or the case, so a recipient replies to the mailbox that actually handles the message.
Check that first. For many line-of-business applications there is a ready-made setup, and if you mainly use Outlook, the plug-in is enough. Custom development makes sense if messages come from your own or heavily customised system, if the security level needs to follow from your rules, or if the sending status needs to be recorded back in the file.
Do you want to send secure email from within your own system rather than alongside it?
Tell us which messages you currently send by hand, which system that data comes from and which rules apply to sensitive documents. We'll show you what the sending queue, the security-level rules and the feedback in the file look like in custom software.