Layman manual
This guide covers day-to-day usage for professionals and patients. It reflects
the current access model, in which what you can do is decided by your
affiliations (which clinic you work at and in which role), the phases
an SU admin has granted you, and whether your account has been activated.
/login)If you arrived from another service (SSO handshake), you will be automatically
redirected back after login.
Three independent things combine to decide what you can do in each PDHC
service:
At the moment you use a service, the system works out your session phases —
the phases you have been granted and that your current role is allowed to use.
For example, an Other care professional role does not permit the analysis
phase, so even if you were granted analysis, it would not apply while you act
in that role. (The planning/Plan phase is special: it involves no patient
data and applies whenever it is granted, regardless of role.)
Being granted a phase is not enough — your account must be activated
A brand-new professional account starts unactivated. Until an SU admin
activates it, every phase-gated service treats you as having no access,
even if phases have already been granted. An SU can only activate your
account once your profile is complete: at least one affiliation, at least
one granted phase your role can actually use, and — for any Researcher
affiliation — at least one research project attached. If something is
missing, the SU is shown exactly what to fix.
After login, the dashboard shows:
To join an existing group:
/request-join, select the group you want to joinJoining a group does not grant phase access
Group membership shows who you are associated with (e.g. "Oncology
Planning"). Its category is a free-form label only; it does not by itself
give you access to any service phase. If you need access to a new phase,
ask an SU admin to grant it.
If you received an invite token from a group admin:
/joinTo request admin privileges for a group you belong to:
/request-join or use the dashboard/suggest-groupplanning, request, provider, or analysis/change-password (also accessible from the dashboard)An SU administrator can force you to pick a new password (for example, after
you report a forgotten password or a suspected leak). When this happens:
sso.pdhc.se/change-passwordIf you are instead told that all your sessions have been cleared (a separate
admin action, typically for a security incident), you will simply be logged out
everywhere and asked to log in again with your existing password. No automatic
redirect to change-password in that case.
/register-patient/loginThe patient dashboard shows:
Your registry enrolment status is shown on the dashboard. This information comes
from the IPS (Integrated Patient Summary) system and reflects your current
participation in quality registries.
If you are a new professional who does not yet have an account:
/request-accessWhen you click a link to another PDHC service:
Your access level in each service depends on your session phases (your
granted phases narrowed by the role of your active affiliation), your affiliated
care unit / caregiver (for scope), and your group memberships (for category).
Each service composes its own policy from these inputs; the SSO supplies the
facts.
Every page carries the platform ribbon in the top left:
PDHC / sso.pdhc
PDHC returns you to the service index at https://www.pdhc.se/services.html;
sso.pdhc is this service's own home. It is the same ribbon every PDHC service
carries, so it means the same thing everywhere (#784 A1/A2).
Documentation files are served from /docs/download/<name>.
The landing page no longer carries a Documentation pane — it was removed in
in #784 (D1) along with the Service Registry pane, because neither told a
anything they could act on. The download routes themselves are unchanged and
still work; only the pane that listed them is gone.
The landing page (/) offers two things, and nothing else:
| card | who it is for |
|---|---|
| Register as a patient to join the health data registry | a private person creating their own account |
| Request access as a healthcare professional | a clinician who needs an account created for them |
Each card is titled with the action it performs rather than the audience it
names, so a first-time visitor can tell which one applies to them without
reading further (#784 A4/A5).
What it no longer shows, and why, since the earlier version of this guide
described it: the page used to render a Platform Services table and a set
of Connected Services cards, built by polling every service's health
endpoint and reading oath_overview.csv. Both were removed in #784 (A3).
That removal was deliberate rather than tidying. A visitor arriving at the
sign-in page of an identity provider is there to sign in; a live status board
of twenty services is noise at best, and when the prober could not reach a
service the page implied an outage that the service itself would have denied.
Platform status belongs on https://www.pdhc.se/services.html, which is
built for it. The ribbon above is the way there.