Built for hospital IT and clinical operations
Integration, data residency and deployment are product architecture concerns, not afterthoughts bolted on after a demo. NerveDX is designed for regulated environments where EMR hand-off, tenant isolation and auditability matter from day one.
Works with your existing EEG systems
NerveDX is an interoperable workflow layer, not a replacement for acquisition hardware or established review tools where they remain in use. We connect to the data path after recording and add governed review, triage, reporting, EMR hand-off and audit.
| Path | Public status |
|---|---|
| BDF / BDF+ / EDF / EDF+ | Primary planned import for pilots |
| Synchronised clinical video | Core product requirement - scoped per site |
| Hospital export / review-station export | Typical ingest path after recording; agreed in discovery |
| HL7 v2 / FHIR report hand-off | Architecture target - dry-run against your interface catalogue |
| SSO (SAML / OIDC) | Planned with deployment |
| Vendor-native or DICOM waveform | Assessed per site, not a universal connector claim |
NerveDX is a workflow layer after recording. It sits beside acquisition hardware, existing review stations and detection tools where they remain in use - including Natus / Nihon Kohden / Cadwell-class stacks when export paths allow. Clinical engineering and HTM teams typically own the export path, not a hardware replacement. Certified workflow badges are published only after validation. Integration scope is agreed per hospital. See Integrations & deployment.
One auditable path from signal to hospital record
Every integration point sits inside a governed workflow with provenance, access control and quality evidence.
- Ingest - Import & store
- Review - Playback & qEEG
- AI triage - Prioritise windows
- Confirm - Clinician sign-off
- Report - Structured output
- EMR - Hospital hand-off
- Audit - Provenance & analytics
HL7 / FHIR-oriented hospital hand-off
NerveDX is architected to deliver structured clinical outputs into hospital systems, not to operate as a disconnected review island.
Report & result delivery
Confirmed findings and structured reports are prepared for EMR consumption. Integration scope - message types, document formats, routing and deployment phase - is agreed per customer and documented before pilot go-live.
HL7 v2 & FHIR patterns
We design toward common hospital interoperability patterns (HL7 v2 messaging, FHIR resources for documents, diagnostic reports and service requests where appropriate). Exact interfaces depend on your EMR landscape and IT standards.
Major hospital EMR patterns
Many hospitals standardise on enterprise EMR platforms with HL7 v2 and FHIR interface catalogues. We plan integration dry-runs against your documented interfaces, not a generic “connects to everything” claim. Share your EMR vendor and integration team early in discovery.
Identity & access
Hospital SSO, role-based access and service-to-service authentication are planned as part of deployment - aligned with your identity provider and security review requirements.
Import formats
BDF/BDF+/EDF/EDF+ is the primary planned import for pilots, with synchronised clinical video. Vendor-native and DICOM waveform paths are assessed per site, not claimed as universal connectors. See the formats table on this page and on Platform.
Integration diligence
Share your EMR vendor, integration team contacts and existing interface catalogue. We can outline a practical integration path under NDA before clinical pilot scope is finalised.
Where your data lives - by design
Tenant isolation
Multi-tenant architecture with institutional separation - a first-class requirement for hospital EEG data, not an add-on configuration.
Regional deployment
Cloud deployment regions and data residency constraints are scoped per customer. EU/EEA hosting and GDPR-oriented processing are core design assumptions.
Data minimisation
Processing aligned to agreed pilot or production scope. Website forms and chat are not channels for patient-identifiable or clinical EEG data.
Cloud, dedicated tenant, or hybrid
Deployment choice depends on your security review, integration complexity and operational preferences. We discuss options early - before clinical users invest time in a pilot.
Managed cloud (SaaS)
Default path for pilots: isolated tenant, controlled access, operational monitoring and agreed data residency. Fastest route to measured workflow evaluation.
Dedicated tenant
Single-institution or partner-dedicated environment with stricter network and access boundaries - suitable for larger health systems with defined cloud governance.
Customer-controlled
Hybrid or customer-managed deployment for sites that require data to remain inside hospital infrastructure. Scoped per engagement with explicit integration and support model.
On-prem roadmap
On-premises deployment patterns are on the product roadmap where hospital policy requires it. Discuss timing and scope if this is a hard requirement for your organisation.
Specific architecture diagrams, network requirements and security controls are available under NDA for procurement and hospital IT review. See our Security & Compliance page for the public summary.
Planning an integration review?
Tell us about your EMR landscape, data residency requirements and deployment preferences.