Occupational health

Checklist: choosing a client portal

25 questions to ask before choosing a client portal for occupational health: the client's view, permissions, login, data protection, setup and gaps.

By PortwayPublished 9 min read

client portal, ordering portal, occupational health, checklist

In this article
  1. Before you start comparing
  2. The checklist
  3. How to read the answers
  4. Common mistakes when choosing
  5. How Portway answers
  6. Frequently asked questions

Short answer: Choose a client portal by how the client company experiences it and how little you have to do by hand, not by the length of the feature list. Ask every vendor the same questions: what does the client company see, who sees what, how does an occasional user log in, where is the data stored, what can your staff set up themselves, and what does the system not do. Ask to see the answers in a demo with one of your own client companies, not in slides.

This checklist is written for those of you running an occupational health service who are about to choose the system your client companies order and follow up in. It complements the requirements for an ordering portal, which goes through what the portal should handle. This one is about how you compare vendors and what to ask them to show.

Before you start comparing

Three things make the comparison easier and more honest.

Pick two real client companies as test cases. One large with several departments and one small that orders a few times a year. The large one shows whether the permissions hold, the small one whether an occasional user manages without help.

Write down what you do today, step by step. An order that arrives by e-mail, who reads it, how it gets into the calendar and how the client hears back. That is your yardstick. A portal that shortens none of those steps does not solve your problem, however good it looks.

Decide the must-haves in advance. If you need BankID because a procurement requires it, or invoicing has to happen in the same system, put it at the top. It saves a demo with a vendor that cannot do it.

The checklist

Go through the questions with each vendor. The answer should be yes, no or "show me", and a no is not automatically disqualifying. What matters is that you know.

The client company's view

  1. Does each client company see only the services it may order, or the same catalogue as everyone else?
  2. Can the client company write to you on the order itself, so that questions do not end up in e-mail?
  3. How many states does an order have, and does someone ordering understand what each one means?
  4. Do documents belonging to an order sit on the order, and what happens to a document sent by mistake?
  5. Are prices shown to the client? If so, who keeps them up to date?

Permissions

  1. Can an administrator for one department be limited to their own department?
  2. Does the client company's administrator see every department without someone linking them one by one?
  3. Does an employee see only their own cases?
  4. Can you limit which colleagues on your side see health data, and is it logged when someone reads it?

Login

  1. How does someone log in who uses the portal four times a year?
  2. How long is an invitation valid, and what happens when it has expired?
  3. Is there BankID or SSO, if you or your clients require it?

Data protection

  1. Where are the database and the files stored, in which country and with which provider?
  2. Which sub-processors are used, for example for e-mail and text messages, and are they in the data processing agreement?
  3. How are personal identity numbers protected: is the field encrypted, and is it shown only when someone actively chooses to show it?
  4. What happens when a person asks for a copy of their data or wants it erased?
  5. Is it clear what is a medical record and what is not? The portal must not become a record.

Anyone processing personal data on your behalf must be bound by an agreement that meets Article 28 of the GDPR, and health data is a special category under Article 9. An honest answer to questions 13 to 16 is therefore not a detail but the basis for your own agreement with the client companies.

Setup and everyday work

  1. Can your own staff set up a new client company, its departments and users, or is the vendor needed?
  2. Can you switch off part of the system for a client company that does not buy it, without it showing up as an error for the client?
  3. Does the portal carry your brand, your logo and your reply-to address, or the system vendor's?
  4. Can you change the wording of invitations and reminders yourselves?
  5. Is there a log where you can see who did what and when?

What is missing

  1. What does the system not do? Ask for a list.
  2. What is handled outside it, such as medical records, invoicing or the report to Försäkringskassan, and how does that fit together in practice?
  3. What has changed in the system in the last six months, and who decides what gets built next?

How to read the answers

A no with an explanation is worth more than a yes with conditions. A vendor who says "we do not do that, this is how clients solve it" gives you a basis for a decision. An "it can be solved" without showing how is a no that arrives later.

Question 23 says the most. A vendor who cannot say what the system lacks either does not know the system or does not want you to know. Both are worth knowing before the contract.

Weigh in the occasional user. The biggest risk with a client portal is not a missing feature but that the client company keeps sending e-mail. Questions 1, 2 and 10 decide that more than any other.

Let the client company try. Give the test client a login and ask them to order something without instructions. It takes fifteen minutes and says more than an hour of demo.

Common mistakes when choosing

  • Starting from the feature list. Two systems with the same list can differ completely in how many steps an order takes.
  • Looking only at your own view. The client company decides whether the portal gets used.
  • Leaving the data protection questions to the lawyer afterwards. Where the data is stored and which sub-processors are used affect your own agreements.
  • Counting on integrations that do not exist. Ask what exists today, not what is planned.

How Portway answers

We think a vendor should be able to answer its own checklist, so here are our answers in short:

  • The client company's view: you control per client company which services can be ordered. An order has the states New, In progress, Done and Cancelled, a thread for messages with the client, internal notes only your staff see, and documents that are withdrawn rather than deleted. Prices are never shown to the client.
  • Permissions: the client company's administrator sees every department, a department administrator sees their own, the employee their own cases. On your side an administrator can switch off access to health data for individual colleagues, and reads of health data are logged.
  • Login: by default a one-time link by e-mail, valid for ten minutes; a password is optional. Invitations are valid for seven days. There is no BankID or SSO.
  • Data protection: the database, files and backend are within the EU, with Railway in the Netherlands. Personal identity numbers are encrypted per field and shown only when someone chooses "Show", which is logged. A request for a copy of data is made through a support ticket; export and erasure are carried out by us, not through a self-service flow.
  • Setup: your administrator sets up client companies, departments and users and switches the modules (orders, booking, surveys and Sjuk & Frisk) on per client company. The portal shows your logo and colour, messages go out in your name with your reply-to address, and eleven message texts can be changed by you. The sending domain is portway.se, and a custom domain is not available.
  • What is missing: medical records, invoicing, payments, BankID, SSO and integrations with other systems. The report to Försäkringskassan is made outside Portway.

More about the modules is on the features page. If you want to go through the checklist with one of your own client companies, you can book a walkthrough.

Frequently asked questions

What is the difference between a client portal and an ordering portal?

The words are often used for the same thing. An ordering portal is the part where the client company orders services; a client portal usually also covers what the client follows up, such as bookings, documents and sick leave. Ask the questions above whatever the vendor calls it.

How many vendors should we compare?

Two or three is usually enough. More makes it hard to keep the same questions and the same test clients through the whole comparison.

Do we need a data processing agreement with the portal vendor?

Yes, if the vendor processes personal data on your behalf, which a client portal does. The agreement must meet the requirements of Article 28 of the GDPR and cover the sub-processors the vendor uses.

Should the client companies take part in the choice?

One or two, ideally. They do not need to join the whole evaluation, but fifteen minutes where a real person who orders tries the portal without help says a lot about how it will be used.

What do we do if no vendor meets every must-have?

Check whether the requirement really is a must-have or a habit. If it is a real requirement, for example from a procurement, it has to be solved outside the portal or with another vendor. Better to know before the contract than after.

See Portway in your everyday work.

We show Portway with what you do today, so you can see what would take care of itself at your place.