Clinical data environments have zero tolerance for data exposure during performance investigations. PGFlare’s read-only IAM model ensures no patient data is ever accessible — we operate exclusively on PostgreSQL performance statistics views. UK data residency, DPA available, DSP Toolkit compatible.
HealthTech workloads combine the compliance requirements of healthcare regulation with the performance demands of high-volume clinical data processing. The patterns we see most often on first engagement:
PGFlare connects exclusively via a read-only IAM role scoped to PostgreSQL performance
statistics views: pg_stat_statements, pg_stat_bgwriter,
pg_locks, and pg_stat_user_tables. These views contain
query performance metrics — not clinical data, not patient identifiers, not
health records. We cannot access patient data under any circumstances.
View IAM setup →
PGFlare maintains records of processing activities (RoPA) for all engagements. A signed Data Processing Agreement is available to all HealthTech clients. All processing takes place in AWS eu-west-2 (London) by default — patient data never leaves the UK.
Database performance failures in clinical environments are not just operational problems — they can directly affect patient safety. When a prescribing system times out, when an EHR query takes 30 seconds during a ward round, or when a FHIR API fails under integration load, the impact extends beyond SLA breach into clinical risk.
PGFlare’s written session reports provide full documentation of the performance issues identified and the remediation actions taken — suitable for inclusion in your Clinical Safety Case and NHS DTAC (Digital Technology Assessment Criteria) submissions where database performance is a relevant factor.
pg_stat_statements (no patient data)Zero patient data exposure. UK data residency. Fixed-fee sessions from £497. DPA provided as standard. Limited consultation spots available each month.
Enquire Now →