DIDisease IntelligenceHealthcare intelligence platform
Start now
What we provideChoose the product for your roleGlobal Health FabricFederated medical intelligenceHealthcare OrchestrationUnderstand → verify → route → coordinateGlobal Healthcare ExchangeVerified request, agreement and network infrastructureGlobal Disease AtlasPatients & publicPhysicians & practicesHospitals & health systemsPharma & CROsResearchers & universitiesGovernment & public healthDashboard demosCompare productsValue calculatorImplementationPricingPlatform technologyAPI & integrationsTrust CentreFunding & investorsInvestor roomProof & pilotsPilot FactorySaaS CoreContact
IMPLEMENTATION

What happens after you choose Disease Intelligence?

Implementation depends on the product. Self-service users can begin quickly; institutional customers require configuration, governance and validation before production use.

01

Commercial scope

Confirm product, users, sites, modules, integrations, support level, data responsibilities and success measures.

Output: agreed scope
02

Workspace setup

Create organisation structure, permission groups, roles, branding and initial module configuration.

Output: configured workspace
03

Data & integrations

Connect contracted data sources or APIs only where lawful, technically supported and necessary.

Output: validated connections
04

Quality & governance

Test workflow, evidence states, security controls, access, auditability, privacy and agreed acceptance criteria.

Output: launch checklist
05

Launch & training

Train users, activate production access, publish operating procedures and define support/escalation routes.

Output: production launch
06

Measure & improve

Review usage, response times, data freshness, workflow outcomes and commercial value against the agreed baseline.

Output: optimisation plan
PROPOSED ONBOARDING WINDOWS

Different products need different implementation effort.

These are indicative planning ranges, not guaranteed deployment times.

DI NavigateImmediate

Public/core tools can be used without institutional implementation.

DI ClinicianSame day → team setup

Individual access can be self-service; practice workflows and permissions require configuration.

DI Health System2–6 weeks

Depends on users, sites, workflow scope, SSO, integrations and data onboarding.

DI Life Sciences2–4 weeks

Workspace and portfolio configuration; enterprise data/API scope may extend this.

DI ResearchImmediate → 2 weeks

Self-service for individuals; institution workspaces require user/project configuration.

DI Public SectorDiscovery-led

Public-sector pilots and national programmes require agreed governance, scope and data sources.

BEFORE CONTRACT

See exactly what needs to be agreed.

  • Product and plan
  • Users/sites/roles
  • Data controller/processor responsibilities
  • Integrations and data sources
  • Security and procurement requirements
  • Success metrics and review cadence
NEXT STEP

Start with the product, not a generic sales call.

Select your role and objective first. Institutional customers can then submit a scoped enquiry with the correct product already identified.

Find my product