Entity-driven
Structured objects rather than duplicated hardcoded content.
DI DATA CLOUD™
One governed data layer beneath every Disease Intelligence product.
The long-term architecture avoids separate silos for diseases, providers, trials, referrals and analytics. Every product should resolve to shared entities, typed relationships, provenance and permissions.
DI DATA CLOUDGoverned entity + relationship layerIdentity · provenance · permissions · freshness · audit
Diseaseconditions · subtypes · biomarkersCapabilityprogrammes · technology · servicesEvidenceassertions · sources · conflictsAccessroutes · geography · preferencesResearchtrials · investigators · sitesConsentsharing · revocation · auditReferralsstatus · ownership · closureSignalschange · anomalies · freshness
DESIGN PRINCIPLE
The website, apps, agents and APIs should query the same source of truth.
Provenance-native
Assertions carry source, reviewer, timestamp and confidence state.
Permission-aware
Sensitive data access is evaluated before the query, not after it.