IT & Security
What your security team will want to check
Integration, architecture, security and compliance in one place. Where we make a claim, we say which kind it is: certified, compliant, designed for, or planned.
Minimum data requirement
We don't need your entire medical record.
Naibor starts with the information needed to understand the discharge and coordinate follow-up:
- patient contact information
- discharge date
- diagnosis / reason for admission
- discharge summary
- medication information
- department
- follow-up plan
Deeper integration can come later and never holds up a pilot. Records are accepted as they arrive; where a field is missing, the feature that used it degrades rather than demanding it.
Integration
- Discharge feedADT, FHIR, HL7v2, API, CSV
- Minimum dataseven fields, nothing more
- Processingpolicy gate, append-only event log
- Care operationsworklist, outreach, escalation
FHIR-first canonical model
Every inbound record is normalized at the edge into one FHIR-aligned contract. The adapters translate, so the core never needs to know which system a record came from.
HL7v2 and legacy feeds
ADT and discharge messaging from an existing integration engine is the route most hospitals will use, and it is supported in its own right.
API, webhook, CSV
A signed webhook to push, an API to pull, and CSV for a pragmatic start. All three land on the same contract.
EHR landscape
Built for the European hospital landscape, including ChipSoft, Epic, Dedalus, Nexus and Oracle Health, through standard interfaces.
RPA bridge
Where a system offers only a portal, a controlled RPA runner posts through the same signed webhook, with drift detection and per-script error monitoring.
RPA exit criteria
RPA is a bridge with a documented way off. When a real interface becomes available the runner is retired, and the criteria for that go into the integration plan from the start.
Optional on-prem runner
Where hospital policy requires it, the ingestion runner can operate inside your network and push outbound only.
Architecture & data
Event-level lineage
Every clinical change lands in an append-only event log, so audit and analytics read the same history, and neither can be edited afterward.
Analytics exports
Nightly Parquet exports per organization, so your data stays queryable with ordinary tools and does not depend on us.
Regional data pinning
Each organization's region is fixed at creation and immutable. EU deployments stay in the EU; a UK deployment path is documented.
EU-hosted subprocessors
Messaging and email ride EU-hosted, EU-entity providers with recorded DPAs. A public subprocessor register lists every one.
GDPR processor model
The hospital remains controller; Naibor processes under instruction, with a DPA, records of processing, and a customer DPIA template.
Status page
Operational status, incidents and maintenance windows are published, and availability is measured against a public SLO.
Hosting and encryption
EU hosting, region pinned
Frankfurt for EU organizations, London for UK ones. The region is fixed when the organization is created, and backups and exports never leave it. One deployment serves one region, so a group spanning both runs two.
Encrypted at rest with customer-managed keys
The database, its backups and point-in-time log, the shared file volume and the logs are encrypted with a per-region KMS key that never leaves the provider's HSM. Rotated annually.
TLS everywhere, enforced in code
TLS 1.2+ at the edge with a 2-year HSTS policy, TLS to the database (production refuses a plaintext connection string) and HTTPS only to every provider.
Secrets in a vault, not in files
Application secrets are injected from the secrets manager at start and rotated by runbook. Tokens for provisioning are stored hashed.
Compliance posture
The words in the table are specific. Certified: audited by an external body. Compliant: we meet the requirements. Designed for: the controls exist and await formal assessment. Planned: on the roadmap with a date.
For EU-generic deployments, GDPR and the AI Act posture below apply directly.
| Framework | Status | What it means here |
|---|---|---|
| GDPR / UK GDPR | Compliant | Processor model, DPAs, EU residency, records of processing, DPIA support. |
| ISO 27001 | Designed for | ISMS controls follow ISO 27001 as the baseline; certification is on the roadmap and will be stated here only when externally audited. |
| NEN 7510 (NL) | Designed for | Dutch healthcare information-security norm; controls mapped, assessment planned with first Dutch deployments. |
| DTAC (UK) | Planned | Digital Technology Assessment Criteria package prepared for UK market entry. |
| DSPT (UK) | Planned | Data Security and Protection Toolkit submission planned alongside UK deployment. |
| §75c SGB V (DE) | Designed for | German hospital IT-security obligations reflected in the deployment architecture for German sites. |
| EU AI Act | Designed for | Human oversight by design, no automated clinical decisions: AI is off for every hospital until its own administrator switches it on, and even then the model reads in the shadow and decides nothing; every run logged with model, prompt and graph versions. |
| Human oversight | Compliant | Automated signals only add contact; clinicians own every intervention, escalation and de-escalation. This is architecture, not policy. |
Nothing above claims a certification we do not hold. A status changes when an external audit says so, and not before.
Security posture
Tenancy is enforced in one tested data-access layer; audit logs are append-only at database level; support access needs named, expiring, customer-visible grants; sessions are hardened; rate limiting protects auth and webhook endpoints; dependencies are scanned and an SBOM ships with every build.
No PII in URLs or logs, PII scrubbing before any AI call, secrets in environment configuration, and no third-party analytics on the clinical platform.