Layman manual
analyse.pdhc is the population / research workspace of the PDHC platform.
It lets an analyst define a cohort of patients across the regional CDRs and
look at aggregate, de-identified distributions — never a single patient's chart
(that is the clinical dashboard / cd-assist).
Access requires the analysis phase on your account (or SU admin). A
treating clinician without the analysis phase will be turned away here — use
the clinical dashboard instead.
https://analyse.pdhc.se/.Your session is re-checked with SSO on every action, so if you log out (or an
admin revokes your session) access stops immediately.
cdr_ids: which CDRs to search (empty = all configured).demographics: age_min, age_max, sex.conditions: list of condition code URIs (e.g. a SNOMED diabetes code).medications: list of medication code URIs (e.g. an ATC class).n).Cohort membership is the intersection ("AND") of every predicate you supply.
Members are always consent-filtered: patients who have opted out of secondary
use, or who have not consented to your research project, are excluded — and the
exclusion is re-applied on every later read, so a consent withdrawn after you
defined the cohort takes effect immediately.
For a saved <cohort_id>:
- Histogram — distribution of a variable:
GET /api/cohort/<id>/variable/<canonical>/histogram
- Boxplot — stratified summary (?group_by=region|cdr):
GET /api/cohort/<id>/variable/<canonical>/boxplot
- Scatter — paired latest values of two variables (?x=&y=&max=):
GET /api/cohort/<id>/scatter
- Trend — per-month percentiles over a window (?canonical=&window=):
GET /api/cohort/<id>/trend
- Export — streamed CSV (?format=csv&variables=<a,b,...>):
GET /api/cohort/<id>/export
A <canonical> is a variable identifier in either system|code or
.../system/code form.
Every read (including denied ones) is recorded in the analyse kontroller log
with who, when, which route, how many rows, and the purpose. Exports write an
additional receipt row with the export id and the exact streamed row count.
These logs exist to satisfy the Patientdatalag chain-of-custody requirements —
treat cohort data as sensitive and export only what your project needs.
If a cohort resolves to 503, the consent service (ips.pdhc) was temporarily
unreachable — research reads fail closed by design; retry shortly. For access
problems (analysis phase, research project membership), contact your PDHC
operator.