The medical event did not reach P1
The P1 Health Dashboard shows four numbers and two certificate expiry dates. From them you read whether the whole of reporting has stopped or only a single visit — and that distinction decides what to do next.
Are you seeing these symptoms?
- The **Stalled** tile grows with every visit
- The **Failed (permanent)** tile shows a value greater than zero
- At the top stands **Certificate expired — submissions paused**
- An event has the state **Blocked — missing PESEL/passport**
- The **Last Success** tile shows **Never**
Reporting medical events to P1 stops for three reasons: a certificate has expired, data is missing on the visit's side, or the transport is switched off in the configuration. The P1 Health Dashboard separates those cases at a glance — its subtitle reads "Real-time P1 submission status and certificate health", and that is exactly what it shows.
How to do it
Read the four tiles
Last Success is the date of the last successful submission. The value Never means the clinic has not yet reported anything at all — the problem is in the configuration, not in a single visit.
Pending is events in flight; that number is entitled to go up and down. Stalled and Failed (permanent) are not entitled to grow in a healthy clinic — the first means events needing a manual decision, the second events that cannot be sent at all until the source is corrected.
Check the certificates
Two tiles give the days to expiry: TLS cert expiry and WSS cert expiry. The value Not uploaded means there is no certificate at all.
A warning appears above the tiles in good time: Certificate expires in N days — renew soon at thirty days, renew now at fourteen, and critical at seven. Past the date the sentence reads Certificate expired — submissions paused, and then nothing goes through, however correct the visits are.
The certificates are issued by RPWDL2 in an exchange file; you upload them in the Upload P1 certificates step of the configuration. Renewing a certificate is a matter of weeks, not hours — watch the thirty-day warning, not the seven-day one.
Open the stalled events list
The Stalled events section lists them with the columns Type, Status, Attempts, Created and Last error. The last column matters most here — it says what was missing.
When all is well you will see No stalled events — everything is flowing normally.
Fix the data and retry
The most common gaps are fixed in the patient record or in the practitioner's profile:
- Patient PESEL or passport is missing — fill in the identifier on the patient record. P1 will not accept an event without it.
- Practitioner is missing NPWZ — fill in the professional practice number on the profile of the practitioner who ran the visit.
Once the data is corrected, use Retry now on the relevant row. The app asks Retry event? and acknowledges with Event queued for retry.
Check whether reporting is switched on at all
If Last Success shows Never and the stalled list is empty, most likely nothing is being sent. Two settings can do this quietly, and both carry their own explanation in the configuration:
- the reporting transport switched off — no visit would actually reach P1;
- medical event reporting switched off for the clinic — no visit would reach P1 even with the transport on.
Check the entity status itself as well. Reporting applies to facilities entered in the register of entities performing medical activity; where there is no entry the app says so outright: This clinic is not registered as an RPWDL entity.
When something does not work
Certificate is expired
What this means: The TLS or WSS certificate has passed its expiry date. Nothing reaches P1.
Certificate is not parseable
What this means: The uploaded file is not what Heltio expects — most often a bundle was uploaded instead of the extracted certificate.
Patient PESEL or passport is missing
What this means: A medical event requires a patient identifier, and the record has none.
Practitioner is missing NPWZ
What this means: The practitioner who ran the visit has no professional practice number recorded.
P1 integration is not configured for this clinic
What this means: The clinic has not been through the P1 setup, or did not finish it.
P1 sandbox did not respond in time
What this means: The CeZ test environment did not answer. This affects clinics still working in the sandbox.
Who has access
Clinic AdminThe P1 Health Dashboard, the retries and the configuration are handled by the clinic owner and administrator. The Export audit log (last 30 days) button downloads the submission trail for the date range you give — that is the attachment to a CeZ ticket when the cause lies on their side.
Related
- Medical events (ZM) — what is reported and when.
- P1 configuration — certificates, practitioner identities and the move to production.
- P1 — overview — who reporting applies to, and why.