Occupational health

Ordering portal for occupational health

What an ordering portal for occupational health must handle: a service catalogue per client company, roles, status flow, login and the line to the record.

By PortwayPublished Updated 10 min read

ordering portal, occupational health, digitalization, guide

In this article
  1. What the person ordering actually does
  2. A service catalogue per agreement
  3. Roles and permissions
  4. The status flow, and what the client sees
  5. Login for occasional users
  6. History and documents
  7. The line to the medical record
  8. Your brand, not the system vendor's
  9. Common pitfalls
  10. How we do it in Portway
  11. Frequently asked questions

Short answer: An ordering portal for occupational health should show each client company exactly the services its agreement covers, let the right person order without calling, and show where the order stands. Whether it gets used rarely depends on the feature list. It depends on two details: that the person ordering gets in without handling a password they use four times a year, and that the portal does not collect health data it does not need. Expect the agreement work, not the technology, to be what takes time.

Many client companies expect a digital ordering portal, and in a public procurement it can be a mandatory requirement rather than an advantage. But "portal" means different things to different providers. This article goes through what actually has to work, in the order it usually goes wrong.

What the person ordering actually does

Before the feature list: the person ordering at the client company is often an HR administrator or a manager who does this perhaps a couple of times a quarter. They are not your daily user, will never learn the system, and have no patience with a portal that requires them to remember something.

That explains why portals fail for reasons that are not in the requirements specification. The order is not placed in the portal but in an e-mail to a case handler the person happens to know, and then the whole investment is lost. Everything below is really about making the portal the easiest route.

A service catalogue per agreement

The basic requirement: the client company should see its services, not yours. A generic catalogue where half the rows are not part of the agreement leads to orders you have to turn down, and a turned-down order costs more than a phone call.

In practice that means services are linked per client company, with the selection that agreement covers. Two clients who buy a "health check" rarely buy the same thing, and whoever negotiated their own content expects to see only that.

Price is a separate question. One reason not to show prices in the portal at all is that agreed prices change, discounts are negotiated and a figure in the portal quickly becomes wrong. Decide it deliberately instead of letting the system decide.

The same applies the other way: if a client company has its own form or an extra question to be asked with every order, it belongs in their flow and nowhere else.

Roles and permissions

Not everyone at the client company should see everything. The split that usually works has three levels:

  • Administrator for the whole client company, often HR, sees every department and every order
  • Administrator for one department, sees only their own department
  • Employee, sees their own cases and nothing else

The middle level is the one that tends to be missing. Without a department boundary, everyone who orders sees every order in the whole company, and since an order contains the names of employees going for a health check, that is a privacy question, not a convenience question.

The status flow, and what the client sees

An order needs a few understandable states. We use four: New, In progress, Done and Cancelled (Ny, Pågår, Klar and Avbruten in the Swedish interface). More states sound more informative and end up saying less: no one ordering knows what the difference between "being prepared" and "being processed" means for them.

What makes the status worth anything is that it is kept current. A status that no one updates is worse than no status at all, because the client trusts it.

A detail that is easy to miss when writing requirements: internal notes and messages the client can see must be two separate things on the same order. Case handlers need to be able to write "call Anna before we book, it went wrong last time" without the client seeing it, and the client needs to be able to ask a question on the order instead of sending an e-mail. Portals with a single comment field end up with either empty notes or an unpleasant leak.

Login for occasional users

This is where most portals lose their users. Someone who logs in four times a year has forgotten the password every time, and a forgotten login in an urgent situation becomes a phone call, which is exactly what the portal was meant to remove.

The alternatives that work:

  • Magic link: the person enters their e-mail address and receives a one-time link. No password to forget, and access depends on the e-mail account, which is already the channel you communicate in. This is our default.
  • BankID: common when the portal also gives employees access to their own data, and sometimes a requirement in the public sector.
  • SSO against the client company's directory: best for large clients, but it takes work per client and rarely pays off below a certain size.

Ordinary passwords are the worst option for exactly this user, however good the reset flow is.

History and documents

Two things people ask for that are often forgotten when the portal is built:

  • History: what has been ordered, by whom and when. HR should be able to answer "what have we ordered so far this year" without contacting you. Invoicing itself is usually handled in the finance system, but the basis starts with the orders.
  • Documents on the order: certificates, background material and answers that belong to an order should sit on the order, not in someone's inbox. Once they are there, you stop sending them a second time.

The line to the medical record

The most important architectural decision, and the one that is rarely in a requirements specification: an ordering portal must not become a medical record.

An order says that a named employee is going for a health check on a given date. It should not contain the reason, earlier complaints or results. What is healthcare documentation belongs in the record system under the Swedish Patient Data Act, with the retention requirements and access control that follow, the same split we go through in the checklist for switching systems.

If the two are mixed, two problems arise at once. The client company gets access to data an employer should not have, and you get record data in a system that is not built to keep it for the at least ten years the Patient Data Act requires (chapter 3, section 17 of the Patient Data Act, in Swedish).

That does not make the portal insensitive. The mere fact that a particular person is going to counselling is sensitive personal data under the GDPR, and the requirements on access control, logging, where the data is stored and a data processing agreement apply in full. We go through them in GDPR and security in occupational health.

Your brand, not the system vendor's

A client company that logs in to a portal with an unfamiliar system name sees it as yet another tool. A client company that logs in to a portal with your logo and your colours sees it as your service. The difference shows in how often it is used and how it is described inside the client's organization, and it is easier to have from the start than to add later.

The same goes for the messages: invitations, confirmations and reminders should arrive in your name, with a reply-to address that reaches you. We write more about that in white label for health and care providers.

Common pitfalls

  • Setup that needs a developer. If adding a new client company takes developer work, sales will stop promising the portal. Clients, departments and which services they can order should be something your own staff can set up.
  • No mobile. People often order from their phone, standing in a corridor.
  • Notifications that only go out. What reduces calls is word when something happens on the order, such as a new message or a new document, and a reminder before the visit.
  • No traceability. When a client asks who ordered what in March, you need to answer without guessing.
  • Statistics no one asked for. A few figures the client actually uses beat a dashboard that looks impressive in a demo.

How we do it in Portway

In Portway's ordering portal the client company picks a service and a person. You decide per client company which services they can order, so each one sees only its own selection. Prices are never shown to the client. An order moves through four states, New, In progress, Done and Cancelled, and has a thread for messages with the client, a tab for internal notes that only your staff see, documents (up to 10 MB, PDF, Word or image) and a log. A document is withdrawn rather than deleted.

The client company's administrator sees every department; a department administrator sees only their own. Login is by a one-time link sent by e-mail by default, and a password is optional. Portway does not offer BankID or SSO. E-mail goes out when an order is created, when a message arrives and when a document is added. The portal shows your logo and colour, not ours.

What the portal does not do: it does not invoice, and it does not turn an order into a project automatically. If the client also needs to book times, the order connects to booking. If you are comparing providers, the checklist for choosing a client portal is the companion to this article.

If you want to see how the flow looks with your own services, you can book a walkthrough.

Frequently asked questions

What is the difference between an ordering portal and a record system?

The ordering portal handles what the client has ordered, by whom and when. The record system handles the healthcare documentation and falls under the Patient Data Act. They should be kept apart: the client company should have access to the first and never to the second.

Does the client company need BankID to order?

No. For an order, a verified e-mail address is normally enough, for example through a one-time link. BankID becomes relevant when individual employees are to see data about themselves, and is sometimes required in public procurements.

What takes time when a new client company is set up?

The setup itself is an administrative task: the client company, its departments, the users and which services they can order. What takes time is deciding what should be included, in other words the agreement work, not the system.

Can each client company see different services?

Yes, and that is the whole point. A portal that only handles one shared catalogue forces you to handle the exceptions by hand, which is the administration the portal was meant to remove. In Portway you control per client company which services can be ordered; prices are not shown to the client. We go through that effect in reducing administration in occupational health.

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.