← PV Literature Screening — Z:II:X Capital

Screening protocol ZIIX-PV-LS-001

Version 1.0 — published 2026-10-31. This document is the protocol referenced by the sample screening record and rendered on the offer page. It is the rule set that was executed, verbatim, against the public literature.


1. Scope

A single medicinal product is screened against a defined, dated literature corpus. The run below is a demonstration over public literature, not client data.

FieldValue
Protocol idZIIX-PV-LS-001
Version1.0
Medicinedaridorexant (INN)
SourceNCBI PubMed / MEDLINE via E-utilities (esearch.fcgi + efetch.fcgi)
Window2023/11/01 → 2026/10/31 (36 months ending on the retrieval date)
Sortingdate (most recent first)
Retrieval cap300 records

2. Search string, as executed

("daridorexant"[Title/Abstract]) AND (adverse[tiab] OR safety[tiab] OR "side effect"[tiab] OR "adverse event"[tiab]) AND ("2023/11/01"[Date - Publication] : "2026/10/31"[Date - Publication])

The exact string, the exact request URL and the raw API responses are retained with the record. A third party can re-run the search and reproduce the corpus.

3. Inclusion criteria

A record is INCLUDED (and flagged as a case candidate) only when all three hold:

observational study, a case report or case series, real-world evidence, or a spontaneous report.

tolerability finding or safety outcome. Attribution is assessed at sentence level: at least one sentence must contain both the medicine name and adverse-event vocabulary.

authors, abstract) so the decision is auditable by a third party.

4. Exclusion criteria

Exactly one primary reason code is recorded per excluded record. The codes are applied in a fixed order; the first that matches is the recorded reason.

CodeNameRule
X1NOT_HUMANNo human exposure. In vitro, animal or other non-clinical evidence only.
X2NO_NEW_CASESA review, editorial, comment, guideline or meta-analysis carrying no new case data.
X3NO_SAFETY_DATAThe record reports no adverse event, tolerability or safety outcome.
X4DRUG_NOT_IMPLICATEDThe medicine is mentioned, but no reported adverse event is attributed to it.
X5RECORD_INCOMPLETECitation data insufficient to screen. Routed to manual review — never silently dropped.
X6STUDY_PROTOCOLA study protocol or design paper reporting no results. It can contain no case.

5. Decision rule order

X1 → X2 → X6 → X5 → X3 → X4 → INCLUDE

The order is fixed because the classes are not disjoint:

record is human evidence is settled before whether it carries new cases.

determinable without the abstract. They are settled before the content rules.

not read. An unreadable record is routed to manual review, not decided by absence of evidence.

record than "not implicated".

The order is enforced by an automated check that compares the published order against the order the code actually applies, so the two cannot drift apart silently.

6. Completeness rule

Every retrieved record receives a decision and a reason. The run asserts:

included + excluded == retrieved

If this fails, the run aborts and no record is emitted. There is no path that drops a record silently.

7. Dual screening

The run published here is a single-pass demonstration. Production delivery applies dual independent screening with adjudication of disagreements, per the client's instructions.

8. Boundaries of this protocol

This protocol produces a screening decision and a flag. It does not produce, and must not be represented as producing:

Those determinations belong to the marketing-authorisation holder's qualified person.