Skepsis Insights

Account settings

Two kinds of thing live on this screen and they are not the same kind. One is a customer setting, which nothing in this API stores yet. The other is a fact about the deployment, which the service publishes about itself and which no customer can edit from here. What is absent is the third kind, and it is the part a reviewer came to read.

SampleNothing below is a measurement.

No account-settings route exists in this API and no table holds a customer setting, so the field below is drawn rather than loaded and its value goes nowhere. NP-08 is the decision that requires it: one fixed insight category list for every customer, whose safety item opens the customer's own reporting page.

Check it: Read this deployment's own OpenAPI document at /openapi.json and search it for a settings path. It lists every route this API serves, and there is none, which is the same way you can check that there is no export route either.

Safety reporting

One URL per customer, and it is the whole of this product’s part in pharmacovigilance. The safety item in insight capture opens it and captures nothing: no symptom, no outcome, no free text. Nothing stores this URL on this deployment, so that item currently has no link to open, and the capture screen says so rather than dropping the hand-off in silence.

Where this deployment holds data

Live, from GET /api/status on this deployment. Not a setting and not editable from here: it is what this installation is configured to be, reported by the service about itself, because a residency claim nobody can check is worth nothing to a procurement reader.

Hosting region	`eu` OQ-30 fixed the territory at EU data centres, and a deployment names its own region within that. This one has named it, so the claim can be checked rather than trusted.
Requirement	`SEC-05` What OQ-30 released.
Environment	production, skepsis-insights-api 0.1.0

Export log

Every export is logged with the user, the time and the content (NP-11, ACC-04). That is a rule rather than a preference, so there is no switch for it here and there never will be: an export log a customer can turn off is not an export log.

There is nothing in it. No export route exists anywhere in this API, so nothing has ever been exported from this deployment, and no route reads the log back either. No retention period and no review cadence is set here, because none is stated anywhere: SEC-04 ships log review as an operator action with a recorded reviewer rather than on a schedule this build invented.

Open the export log no route reads it, and it has no rows to read

What account settings will never hold

A conflict-of-interest field, flag or note NP-09Not a setting that defaults to off, and not a field a customer can enable. It is absent from every screen and from the types behind them, so no part of this product can start collecting one.
A payment, claims or prescribing data source OQ-28No connector, no credential field and no toggle. The decision named all three and dropped COMP-03 with them, so there is nothing here to configure on or off.
A box for the detail of a safety report NP-08The hand-off is a URL, and it leaves. Under GVP Module VI the clock starts when adverse-event information reaches any personnel of the marketing authorisation holder, so text merely sitting in a table is the trigger whether or not anybody reads it. A field that does not exist is a control nobody can fail.
An editor for the insight categories OQ-24The six codes are fixed for every customer, which is what makes two customers' insights comparable and what keeps a free-text box from arriving under another name.

The registers that do hold personal data, and every requirement OQ-28 settled.

What this screen is for

The safety hand-off is a configured URL per customer rather than a form in this product, because the moment a side effect is typed here, Skepsis Insights is holding pharmacovigilance data it decided never to hold. The rest of this screen is the same argument in reverse: the settings that are missing are missing on purpose, and they are missing from the types, not merely from the screen.