FAQ · Neurovia

Can your system handle clinical text and reports in local languages?

Yes. Structured fields and report drafts support localized output; terminology lists can be configured per department. The imaging pipeline remains DICOM-centric; text capabilities support summaries and tumor board materials.

Do we have to replace our existing EHR / PACS?

No. Neurovia connects primarily via sidecar integration—physicians continue reading and signing in familiar workstations. We provide standard DICOM / HL7 / FHIR integration paths.

Will AI conclusions be written directly into final reports?

Not by default. Output enters draft and human-confirmation workflows; key conclusions include feature contributions and confidence information, with override and QA trails preserved.

Which clinical scenarios do you support?

Current focus areas include oncology centers, radiology, and translational research—capabilities cover AI-assisted reading, risk stratification, and multimodal fusion. Modules can be scoped to pilot department needs.

Where is data stored? Is it encrypted?

In on-premises mode, data and models run in facility data centers or isolated networks; dedicated cloud deploys in customer-specified regions. Data in transit and at rest supports encryption and can integrate with institutional key management.

Do you support data residency / no data leaving the network?

Yes. On-premises deployment can keep training and inference entirely on the internal network. Cross-facility collaboration can proceed under access isolation and de-identification policies.

How do you meet audit and QA requirements?

The system retains key inference and human override trails, with exportable audit packages for QA sampling, teaching review, and compliance review.

Can you integrate with institutional SSO / LDAP?

Yes. On-premises delivery supports unified identity and permissions, with role-based control of modules and data scope.

How long does deployment typically take?

Most organizations complete on-premises pilot integration in 4–8 weeks (interfaces, permissions, and shadow operation). Full rollout depends on node count and change windows.

What IT support is required?

Typically network and server resources, PACS and identity interfaces, and test environment accounts. We provide data checklists and interface documentation to reduce back-and-forth.

How should we measure pilot success?

Define 2–3 metrics at kickoff—for example tumor board prep time, high-risk wait time, and QA traceability coverage—and compare before and after the pilot.

How are operations and upgrades handled after go-live?

On-premises supports offline patches and version control; dedicated cloud supports unified upgrades. Both can configure health checks and alert integration.

Is there a free trial?

Time-limited pilots or demo environments are available. Formal pilots typically run against agreed scope and success metrics—contact us for details.

Annual or monthly billing?

Subscription (primarily annual) and module licensing are supported. On-premises pricing can be per node or module; dedicated cloud combines subscription and usage tiers.

Do you charge per study volume?

Optional. Some customers pay module annual fees; high-throughput sites may add usage tiers. We recommend combinations based on department peak load and expansion plans.

How do we get a quote?

Book a demo via the website with department scope, deployment preference (on-premises / dedicated cloud), and timeline—we will provide a matching quote framework.

Frequently Asked Questions