Lagos · People & society

Health.
Trace recorded care encounters.

Move from a synthetic resident to care encounters, facilities and the clinical context included in the published sample.

Public sample available

Read certification →Read evidence →Read audit findings →

← Back to Lagos certification records

Published domain facts

Patients · Lagos: 7.7M
Healthcare visits: 27.4M
Facilities: 2,302
Historical health events: 17

Overview

Domain scope

Move from a synthetic resident to care encounters, facilities and the clinical context included in the published sample.

Read the published guide →

Public sample access

Public sample available

Preview samples & fields →

Known limits

Patient coverage remains below the target band and eligibility channels are uneven. Older evidence is sparse and sometimes national. Diagnosis risk uses current rather than historical wards. Visits are sampled; co-occurrence does not establish clinical relationships unless explicitly modeled. Records are synthetic.

Review the source limits →

Full scope reference 2 documented sections

Published domain scope.

Connect synthetic residents to facilities, care encounters and clinical histories. Review the published scope before clinical or population-level analysis.

Inspect visits and facility context
Compare encounter and diagnosis fields
Review longitudinal coverage and clinical limits

Patients · Lagos: 7.7M
Healthcare visits: 27.4M
Facilities: 2,302
Historical health events: 17

Domain scope.

Inspect the published scope and deployment boundaries.

Read the published detail

FCTE models disease, healthcare access, facilities, visits and population health within the same synthetic city where people live, work, travel, age and experience historical events.

Health records remain connected to the citizens, households, geography, insurance and other city systems that shape healthcare demand.

Lagos City Twin™ · 1940–2026

Samples & fields

Published sample records.

Public sample · rows and field definitions

Public sample

Given name	Family name	Visit date	Visit type	Age at visit	Visit facility name	Triage priority	Diagnosis code (ICD-10)
Modupe	George	2026-07-02	IPD	46	Sabo-Shomolu Private Hospital	Not recorded	I63.9
Nkem	Ezeji	2026-06-30	IPD	68	Festac-Phase2 Community Clinic	Not recorded	A15.0
Osayuki	Igbinedion	2026-06-30	IPD	78	Ikoyi-North Mission Hospital	Not recorded	I64

Showing 3 of 100 sample rows and 8 of 128 fields. “Not recorded” is a display label; downloads retain original values.

Published field definitions · 8 visible fields

Given name

The first name assigned to the synthetic resident.

Original field: FirstName
Example: Modupe

Family name

The family name assigned to the synthetic resident.

Original field: LastName
Example: George

Visit date

The date recorded for the visit event.

Original field: VisitDate
Example: 2026-07-02

Visit type

The category or type assigned to the visit in the source record.

Original field: VisitType
Example: IPD

Age at visit

The synthetic patient’s age in years at the time of the visit.

Original field: AgeAtVisit
Example: 46

Visit facility name

The name recorded for the visit facility associated with this record.

Original field: VisitFacilityName
Example: Sabo-Shomolu Private Hospital

Triage priority

The recorded urgency category assigned during the visit.

Original field: TriageLevel
Example: 4

Diagnosis code (ICD-10)

The published ICD-10 code identifying the recorded diagnosis.

Original field: DiagnosisICD10Code
Example: I63.9

CSV ↓JSON ↓PARQUET ↓Field guide CSV ↓Field guide JSON ↓Inspect the dataset →

Complete published field dictionary · 128 fields

CitizenIdResident reference: The synthetic resident reference used to connect this record to other city data.Example: 6827875
NationalIdNational identity reference: The synthetic national identity reference recorded for the resident.Example: NIN00010653706
FirstNameGiven name: The first name assigned to the synthetic resident.Example: Modupe
MiddleNameMiddle name: Any middle name assigned to the synthetic resident.Example: Omorede
LastNameFamily name: The family name assigned to the synthetic resident.Example: George
DOBDate of birth: The resident’s recorded date of birth.Example: 1979-08-30
GenderGender: The gender recorded for the synthetic resident; M and F denote male and female in these samples.Example: Female
EthnicGroupIdEthnic group reference: The reference used to identify the ethnic group associated with this record.Example: 5
CitizenWardIdCitizen ward reference: The reference used to identify the citizen ward associated with this record.Example: 19
CitizenWardResident’s ward: The ward recorded for the synthetic resident.Example: Sabo-Shomolu
CitizenRegistrationDateCitizen registration date: The date recorded for the citizen registration event.Example: 2001-08-22
ResidencyStatusResidency status: The resident’s recorded relationship to the city, such as resident or diaspora.Example: Resident
CurrentCountryCodeCurrent country code: The country code recorded for the resident’s current location.Example: Not provided
DepartureDateDeparture date: The recorded date on which the resident left the city.Example: Not provided
IsPhysicallyResidentPhysically resident: Whether the resident is recorded as physically living in the city. In the source file, 1 means yes and 0 means no.Example: Yes
RelationshipCodeRelationship to household head: The recorded relationship between this resident and the household head.Example: Child
PatientIdPatient reference: The reference used to identify the patient associated with this record.Example: 5896465
PatientNumberPatient number: The published reference number associated with the patient.Example: LOS-PAT-06827875
BloodGroupBlood group: The blood group recorded for the synthetic patient.Example: B+
NHISNumberHealth insurance reference: The synthetic health-insurance reference recorded for the patient.Example: NHIS-96378984
PatientRegistrationDatePatient registration date: The date recorded for the patient registration event.Example: 2005-06-12
RegisteredFacilityIdRegistered facility reference: The reference used to identify the registered facility associated with this record.Example: 95
PatientIsActivePatient active: Whether the patient is marked as active in the source record. In the source file, 1 means yes and 0 means no.Example: Yes
RegisteredFacilityCodeRegistered facility code: The published code identifying the registered facility. Codes are retained as supplied in the source.Example: LOS-HLT-019-401
RegisteredFacilityNameRegistered facility name: The name recorded for the registered facility associated with this record.Example: Sabo-Shomolu Mission Hospital
RegisteredFacilityLevelRegistered facility level: The service level assigned to the patient’s registered healthcare facility.Example: 3
RegisteredFacilityTypeRegistered facility type: The category or type assigned to the registered facility in the source record.Example: Faith-Based
RegisteredFacilityOwnershipRegistered facility ownership: The ownership category of the patient’s registered healthcare facility.Example: Faith-Based
VisitIdVisit reference: The reference used to identify the visit associated with this record.Example: 21867789
VisitDateVisit date: The date recorded for the visit event.Example: 2026-07-02
VisitTypeVisit type: The category or type assigned to the visit in the source record.Example: IPD
TriageLevelTriage priority: The recorded urgency category assigned during the visit.Example: 4
AdmissionDateAdmission date: The date recorded for the admission event.Example: 2026-07-02
DischargeDateDischarge date: The date recorded for the discharge event.Example: 2026-07-05
VisitWardIdVisit ward reference: The reference used to identify the visit ward associated with this record.Example: 19
EncounterStatusEncounter status: The state recorded for the encounter in this extract.Example: DISCHARGED
AdmissionLengthDaysLength of admission (days): The recorded duration of the admission, in days.Example: 3
AgeAtVisitAge at visit: The synthetic patient’s age in years at the time of the visit.Example: 46
VisitFacilityIdVisit facility reference: The reference used to identify the visit facility associated with this record.Example: 497
VisitFacilityCodeVisit facility code: The published code identifying the visit facility. Codes are retained as supplied in the source.Example: LOS-HLT-019-501
VisitFacilityNameVisit facility name: The name recorded for the visit facility associated with this record.Example: Sabo-Shomolu Private Hospital
VisitFacilityLevelVisit facility level: The service level assigned to the facility where this visit took place.Example: 3
VisitFacilityTypeVisit facility type: The category or type assigned to the visit facility in the source record.Example: Private-Hospital
VisitFacilityOwnershipVisit facility ownership: The ownership category of the facility where the visit took place.Example: Private
BedCountBed count: The number of bed records included in this extract for the associated person or entity.Example: 60
HasMaternityMaternity recorded: Whether maternity is present in the associated source record. In the source file, 1 means yes and 0 means no.Example: Yes
HasEmergencyEmergency recorded: Whether emergency is present in the associated source record. In the source file, 1 means yes and 0 means no.Example: Yes
HasOperatingTheatreOperating theatre recorded: Whether operating theatre is present in the associated source record. In the source file, 1 means yes and 0 means no.Example: Yes
HasICUIntensive care available: Whether the facility is recorded as having an intensive care unit. In the source file, 1 means yes and 0 means no.Example: No
HasOncologyOncology recorded: Whether oncology is present in the associated source record. In the source file, 1 means yes and 0 means no.Example: No
HasDialysisDialysis recorded: Whether dialysis is present in the associated source record. In the source file, 1 means yes and 0 means no.Example: No
HasTBServicesTuberculosis services available: Whether the facility is recorded as providing tuberculosis services. In the source file, 1 means yes and 0 means no.Example: No
HasLaboratoryLaboratory recorded: Whether laboratory is present in the associated source record. In the source file, 1 means yes and 0 means no.Example: Yes
VisitAtRegisteredFacilityVisit at registered facility: Whether the visit took place at the patient’s registered facility.Example: NO
AttendingStaffIdAttending staff reference: The reference used to identify the attending staff associated with this record.Example: 1081
AttendingStaffNumberAttending staff number: The published reference number associated with the attending staff.Example: LSMOH-0001209
AttendingStaffNameAttending staff name: The name recorded for the attending staff associated with this record.Example: Abiodun Fadahunsi
AttendingStaffCategoryAttending staff category: The classification assigned to the attending staff in the published source.Example: Clinical-Officer
AttendingSpecializationAttending clinician specialty: The specialty recorded for the staff member attending this visit.Example: Internal Medicine
AttendingLicenceNumberAttending clinician licence: The synthetic professional licence reference recorded for the attending staff member.Example: Not provided
AttendingMDCNNumberAttending clinician registration: The published MDCN registration reference for the attending staff member.Example: MDCN-0001494
AttendingStaffIsActiveAttending staff active: Whether the attending staff is marked as active in the source record. In the source file, 1 means yes and 0 means no.Example: Yes
VitalRecordCountVital record count: The number of vital record records included in this extract for the associated person or entity.Example: 1
VitalRecordedDateVital recorded date: The date recorded for the vital recorded event.Example: 2026-07-02
SystolicBPSystolic blood pressure: The upper value recorded in the patient’s blood pressure reading.Example: 108
DiastolicBPDiastolic blood pressure: The lower value recorded in the patient’s blood pressure reading.Example: 69
HeartRateBpmHeart rate (beats/min): The recorded number of heartbeats per minute.Example: 62
TemperatureCTemperature (°C): The recorded body temperature in degrees Celsius.Example: 37.9
RespRatePerMinBreathing rate (breaths/min): The recorded number of breaths per minute.Example: 16
SpO2PctOxygen saturation (%): The oxygen saturation percentage recorded for the patient.Example: 100
WeightKgWeight (kg): The recorded body weight in kilograms.Example: 88.0
HeightCmHeight (cm): The recorded height in centimetres.Example: 160.0
BMIBody mass index: The body mass index value recorded in the synthetic health data.Example: 34.38
DiagnosisCountDiagnosis count: The number of diagnosis records included in this extract for the associated person or entity.Example: 1
ConfirmedDiagnosisCountConfirmed diagnosis count: The number of confirmed diagnosis records included in this extract for the associated person or entity.Example: 1
DiagnosisIdDiagnosis reference: The reference used to identify the diagnosis associated with this record.Example: 18001268
DiagnosisICD10CodeDiagnosis code (ICD-10): The published ICD-10 code identifying the recorded diagnosis.Example: I63.9
DiagnosisTypeDiagnosis type: The category or type assigned to the diagnosis in the source record.Example: Primary
DiagnosisIsConfirmedDiagnosis confirmed: Whether the source marks the recorded diagnosis as confirmed. In the source file, 1 means yes and 0 means no.Example: Yes
ConditionCountCondition count: The number of condition records included in this extract for the associated person or entity.Example: 1
ConditionICD10CodeCondition code (ICD-10): The published ICD-10 code identifying the recorded condition.Example: I63.9
ConditionOnsetDateCondition onset date: The date recorded for the condition onset event.Example: 2026-07-02
ConditionResolvedDateCondition resolved date: The date recorded for the condition resolved event.Example: Not provided
ConditionStatusCondition status: The state recorded for the condition in this extract.Example: Chronic
ConditionSeverityCondition severity: The severity category recorded for the condition.Example: Mild
LabResultCountLab result count: The number of lab result records included in this extract for the associated person or entity.Example: 4
AbnormalLabCountAbnormal lab count: The number of abnormal lab records included in this extract for the associated person or entity.Example: 0
PanelCodePanel code: The published code identifying the panel. Codes are retained as supplied in the source.Example: LIPID
TestCodeTest code: The published code identifying the test. Codes are retained as supplied in the source.Example: TRIG
ResultDateResult date: The date recorded for the result event.Example: 2026-07-02
ResultValueLaboratory result: The value recorded for the laboratory test; read alongside the result unit.Example: 139.892
UnitResult unit: The measurement unit recorded for the laboratory result.Example: mg/dL
AbnormalFlagResult flagged abnormal: The source’s indicator of whether the laboratory result is flagged as abnormal.Example: N
LabResultStatusLab result status: The state recorded for the lab result in this extract.Example: NORMAL
PrescriptionCountPrescription count: The number of prescription records included in this extract for the associated person or entity.Example: 1
DispensedPrescriptionCountDispensed prescription count: The number of dispensed prescription records included in this extract for the associated person or entity.Example: 1
PrescriptionIdPrescription reference: The reference used to identify the prescription associated with this record.Example: 103523548
MedicationCodeMedication code: The published code identifying the medication. Codes are retained as supplied in the source.Example: HSC10
MedicationNameMedication name: The name recorded for the medication associated with this record.Example: Hyoscine Butylbromide 10mg
DosageFormMedication form: The physical form of the medication, such as a tablet or liquid.Example: Tablet
QuantityQuantity: The amount recorded for the medication or service, in the source’s stated units.Example: 7
DurationDaysDuration (days): The recorded duration of the medication course or service, in days.Example: 8
IsDispensedDispensed: Whether the associated record is marked as dispensed. In the source file, 1 means yes and 0 means no.Example: Yes
ProcedureCountProcedure count: The number of procedure records included in this extract for the associated person or entity.Example: 1
ProcedureIdProcedure reference: The reference used to identify the procedure associated with this record.Example: 295136
ProcedureCodeProcedure code: The published code identifying the procedure. Codes are retained as supplied in the source.Example: HERNIA
ProcedureDateProcedure date: The date recorded for the procedure event.Example: 2026-07-02
ProcedureOutcomeProcedure outcome: The result recorded for the procedure event.Example: Success
ProcedureSourceICD10CodeProcedure-related diagnosis code: The ICD-10 code recorded as the source diagnosis for the procedure.Example: K35.80
PerformingStaffNamePerforming staff name: The name recorded for the performing staff associated with this record.Example: Abiodun Fadahunsi
PerformingStaffCategoryPerforming staff category: The classification assigned to the performing staff in the published source.Example: Clinical-Officer
PerformingStaffSpecializationPerforming staff specialization: The clinical specialty recorded for the performing staff.Example: Internal Medicine
ProcedureFacilityNameProcedure facility name: The name recorded for the procedure facility associated with this record.Example: Sabo-Shomolu Private Hospital
ReferralCountReferral count: The number of referral records included in this extract for the associated person or entity.Example: 1
ReferralIdReferral reference: The reference used to identify the referral associated with this record.Example: 553380
ReferralICD10CodeReferral diagnosis code: The ICD-10 code recorded in connection with the referral.Example: I63.9
ReferralReasonReferral reason: The reason recorded for the referral event.Example: HasICU not available at referring facility
ReferralDateReferral date: The date recorded for the referral event.Example: 2026-07-02
ReferralOutcomeReferral outcome: The result recorded for the referral event.Example: Attended
ReferralFromFacilityReferring facility: The healthcare facility recorded as sending the referral.Example: Sabo-Shomolu Private Hospital
ReferralFromFacilityLevelReferring facility level: The service level recorded for the facility sending the referral.Example: 3
ReferralToFacilityReceiving facility: The healthcare facility recorded as receiving the referral.Example: Apapa-Wharf Tertiary Hospital
ReferralToFacilityLevelReceiving facility level: The service level recorded for the facility receiving the referral.Example: 5
HasDiagnosisDiagnosis recorded: Whether diagnosis is present in the associated source record.Example: YES
ReceivedPrescriptionPrescription recorded: Whether a prescription is recorded for the encounter.Example: YES
HadProcedureProcedure recorded: Whether a procedure is recorded for the encounter.Example: YES
ReferralStatusReferral status: The state recorded for the referral in this extract.Example: REFERRED
TemporalValidationStatusDate consistency check: The published result of checking the timing and sequence of the recorded events.Example: VALID

Download complete field guide JSON ↓

Additional records and schema context 1 documented sections

From city health conditions to one citizen's record.

Inspect the published definitions and release context.

Read the published detail

Representative synthetic Lagos care records illustrate the public longitudinal model. Physical source IDs, joins and exact extraction path are intentionally withheld.

Direct synthetic records from the current City Twin™ release. No record represents a real patient.

Explore Health Data →

Public entity family	Represents	Disclosure boundary
Population health context	Area and resident health-profile context	Exact risk weights and physical fields are controlled
Care facilities	Facility type, geography and availability context	Physical facility identifiers are controlled
Care encounters	Visit, treatment and utilization context through time	Exact event-generation mechanics and fields are controlled
Disease & historical context	Disease burden and documented health-event context	Exact temporal weights and propagation mechanics are controlled

FacilityId

FacilityName

WardId

Level

Type

Ownership

Beds

Explore Health Data →

Connections

Known and possible relationships

Inspect the published definitions and release context.

Domain or context	Relationship and published scope
Demographics	Patient or resident identity, lifespan, sex and ward provide care context. Dated visits must respect the resident lifespan.
Facilities and geography	Visits carry facility and area context where supplied; the same resident can have repeated visits.
Business	Facility-to-business context is optional, not an identity link on every care record.
Insurance	Care eligibility and claims can be analysed alongside health events; the public guide does not expose every physical linkage.
Transport	Mobility incidents can be compared with injury and diagnosis context. This does not assert a direct trip-to-visit join.
Water	The documented area health-profile field is nullable and is not populated by a Water-domain generation model in the cited guide.

Full relationship reference 1 documented sections

Known and possible relationships.

Inspect the published definitions and release context.

Read the published detail

Connections follow the published domain scope. Optional, contextual and planned relationships retain their stated limits below.

Domain or context	Relationship and published scope
Demographics	Patient or resident identity, lifespan, sex and ward provide care context. Dated visits must respect the resident lifespan.
Facilities and geography	Visits carry facility and area context where supplied; the same resident can have repeated visits.
Business	Facility-to-business context is optional, not an identity link on every care record.
Insurance	Care eligibility and claims can be analysed alongside health events; the public guide does not expose every physical linkage.
Transport	Mobility incidents can be compared with injury and diagnosis context. This does not assert a direct trip-to-visit join.
Water	The documented area health-profile field is nullable and is not populated by a Water-domain generation model in the cited guide.

Demographics Insurance Water Business Transport

Domain guide

Health · archived guide edition

Striped Donkey V5.89 - 7 September 2026

Counts, prices and “live/today” certification statements reflect this dated edition. They are not a current rerun or offer. The current scope, known limits and accepted quote take priority.

Published scope and limits

Read the source limits →

Open PDF ↗Download recorded guide ↓

Accessible HTML reference 5 documented sections

Modelled entities.

Explore the entities and states represented by this domain.

Read the published detail

FCTE Health represents the health conditions, disease environment, healthcare infrastructure and utilization patterns needed to model healthcare within the wider city.

Health characteristics and risk patterns tied to demographic and geographic context — ward-level socioeconomic health profiles, blood group, chronic condition registries.

Disease definitions, ICD-10 diagnoses, prevalence and temporal behavior — including disease-specific weighting that changes by era and ward.

Hospitals, clinics and other modeled points of care — facility level, ownership, bed capacity and clinical staffing.

Synthetic utilization generated against citizens and healthcare infrastructure — OPD, IPD, emergency, maternity and immunization encounters.

Documented disease events that alter health conditions and healthcare demand during affected periods — 37 real, cited events across Lagos.

Relationships between citizens, geography, healthcare availability and coverage — including insurance/eligibility channel mix.

Synthetic, not clinical: FCTE Health does not reproduce real patient records, diagnoses or medical histories. It generates statistically grounded synthetic health relationships from aggregate evidence and documented modeling rules.

Health changes as the citizen does.

Published release reference · These recorded checks are not a current rerun.

Inspect the published definitions and release context.

Read the published detail

Health is not a single status field attached to a citizen — it moves through the same lifecycle stages every other domain does.

Health events remain temporally constrained by the citizen's demographic history — healthcare activity cannot occur before the citizen exists or after applicable lifecycle boundaries. Four certification checks enforce this directly: certification check (registration ≥ birth), certification check (visit ≥ birth), certification check (visit ≥ registration) and certification check (visit ≤ death) — all four caught real, large-scale violations (up to ~72% of rows) before being fixed, and all four pass in the published check results.

A related but distinct boundary sits at the other end of the timeline: a record that was valid when generated but drifts past the platform's own in-universe "today" (NowDate). A 2026-08-05 audit traced a four-link chain of exactly this — future-dated Patient cascading into Visit, Condition, Prescription and Claim — back to a single unbounded date window, fixed the generation model, and retroactively corrected 1,096,381 synthetic rows in the recorded release across Lagos. Three new checks were added for this release: certification check , certification check , certification check . See the full audit →

the full audit →

The city remembers its outbreaks.

Inspect the published definitions and release context.

Read the published detail

Select a marker below to see the underlying evidence.

37 documented events shown as 4 markers per city above — the full calendar (83 year-weighted rows, including polio, HIV, typhoid, H1N1, TB and smallpox eras) is available via the source catalogue.

Explore Historical Health Events →

Historical events aren't decorations.

Inspect the published definitions and release context.

Read the published detail

Historical health events alter population-level enrollment and diagnosis tendencies during documented windows. Certification verifies directional historical response at release level; exact coefficients, probability adjustments and internal methods are intentionally withheld.

The event modifies generated healthcare utilization according to documented FCTE rules — it does not assert an exact real-world causal visit count.

Evidence becomes synthetic health activity.

Review the documented generation rules and assumptions.

Read the published detail

Health generation follows a controlled clinical lifecycle from population and geography through facility access, patient context, visits, diagnoses and downstream care records. Exact phase ordering, per-condition generation models, probabilities and orchestration are not published.

Directly supported by health statistics, surveillance or published evidence — e.g. WHO Disease Outbreak News, NCDC situation reports.

Calculated from observed health evidence — e.g. living-population baselines from Citizen/Death cohort data.

Disease burden, care access, outbreak timing and population-health distributions are calibrated to cited health evidence and validated at release level. Exact weights and thresholds remain controlled.

Individual synthetic assignments are generated under controlled domain rules. Exact sampling, assignment order and parameterization are not published.

View Health Generation Methodology →

Surveys, public-health reports and demographic health statistics.

Surveillance reports, outbreak records and epidemiological publications.

Health facility, infrastructure and geographic sources.

Official and peer-reviewed evidence for documented outbreaks and health shocks.

Open Health Source Catalogue →

Review Lagos release history →Open Health Source Catalogue →

Evidence & limits

Scope and known limits

Evidence, findings and release history 3 documented sections

Known limits.

Read the published detail

No synthetic citizen corresponds to a real person, and generated health histories should not be interpreted as reconstructed medical records.

Older health evidence is substantially less granular for some diseases, periods and geographies — e.g. 1920s Lagos plague figures rely on a single colonial-era report.

Some historical disease counts and epidemic evidence are available nationally rather than at Lagos-specific resolution. Those values are used as calibration evidence, not presented as direct Lagos observations.

Unless explicitly modeled via DiseaseRelationship, FCTE does not imply clinical relationship, comorbidity or disease progression merely because multiple conditions occur within the same synthetic population.

Informal, unreported and historically undocumented healthcare use is not directly observable. Visit generation therefore samples a controlled share of the eligible population rather than pretending to represent a universal registry (certification check). The sampling rate is a disclosed calibration choice and remains subject to realism review.

The Diagnosis phase's ward-affluence disease-risk weighting uses a citizen's current ward for their entire visit history rather than the period-appropriate historical ward the Visit phase already threads through elsewhere. Accepted as a documented limitation rather than queued for remediation, the same disposition already applied to the analogous Transport longitudinal-matching finding (certification check).

Lagos's Patient population currently covers 21.16% of citizens (certification check), below the 50–85% band the eligibility-gated model targets, and its four eligibility channels (Insurance, MaternalCare, ChildImmunization, IllnessEncounter) are not yet evenly balanced (certification check). Both are disclosed, tracked gaps in the underlying eligibility calibration, not a data-integrity defect — every generated Patient row is still internally consistent.

View All Health Limitations →

Does the synthetic health system resemble the city?

Inspect the published definitions and release context.

Read the published detail

Three realism dimensions are defined, sourced and now run against a fully populated Patient/Visit base in Lagos — not a placeholder pass.

The certification WARN has a known, disclosed cause: visit-history volume is intentionally bounded in this release, which suppresses the per-capita rate below the cited benchmark band. The exact sampling rate and volume-control parameter are retained in controlled technical documentation.

Open Health Realism Report →

A full 21-check structural battery plus a 12-check realism pass run live against the Lagos release. All 21 structural checks pass in Lagos — the battery has grown from 19 to 21 checks since this page was last refreshed, with no new violations on either addition.

Lagos: 8 PASS / 0 FAIL / 3 WARN / 1 INFO — Lagos additionally shows certification check (population coverage 21.16%, below the 50–85% expected band) and certification check (eligibility channel mix) as WARN; every WARN/INFO in Lagos is a disclosed, documented cause, not an open defect.

Explore Every Health Check →

certification check — Facilities populated (≥50) — 1,252 / 2,303
certification check — One patient record per citizen
certification check — Prescription Quantity/DurationDays > 0
certification check — BedOccupancy never exceeds TotalBeds

certification check — Visit dates within SeedEpoch–NowDate
certification check — patient registration date ≥ resident date of birth
certification check — visit date ≥ resident date of birth
certification check — visit date ≥ patient registration date

certification check — Discharge date ≥ Admission date
certification check — Maternity delivery within valid window
certification check — Mother age at delivery in [12,55] — 89,820 / 170,827 records
certification check — visit date ≤ own citizen DeathDate

certification check — patient/resident reference integrity
certification check — clinical-staff/resident reference integrity
certification check — Every citizen ward has a facility
certification check — Health foundation ready

certification check — condition-resolution date never a phantom future resolution
certification check — prescription timestamp within 7 days of NowDate
certification check — claim submission date within 7 days of NowDate

Open Health Realism Report →Explore Every Health Check →

Health gets stronger with every release.

Inspect the published definitions and release context.

Read the published detail

A transparent record of what changed, what was verified, and how the synthetic health system improved over time.

Traced and corrected a future-dating issue affecting patient registration, visits, conditions, prescriptions and claims — 1,096,381 records corrected across Lagos. Three new checks added to catch this permanently. Full audit →

Removed unnecessary performance restrictions from record generation, Lagos, with no service disruption.

Performance improvement to claims processing (the largest single cost in data generation, cut by roughly two-thirds) and a diagnosis-calculation restructure, independently verified against 5,000 real visits with zero discrepancies.

Closed a performance issue that had stalled data generation for nearly 15 hours, by adding missing indexes across four clinical records.

Fixed a patient-record generation crash affecting citizens with multiple household history entries; verified against the real failing case.

Fixed an error-handling gap that had been masking the true cause of a release run-generation failure behind a generic error message.

Standardized health-domain deployment release processes for consistency across cities.

Platform-wide scheduling reorganization to reduce cross-domain generation risk.

Added enrollment-year weighting to patient eligibility, driven by real population and historical-event data, per city and year.

Full change log →Full audit →View Full Health Change Log →

Access & datasets

Scope your data request

Choose the records, dates and connected domains you need. Final availability, delivery scope and licensing are agreed with your quote.

Request this domain Browse datasets

Review rights and delivery

Read the terms for public previews and commercial orders before requesting your extract.

Licensing & rights →Delivery standard →

Published access and recorded examples 1 documented sections

Recorded example.

Published release reference · These recorded checks are not a current rerun.

Explore the supplied synthetic example and its source references.

Read the published detail

A documented cholera outbreak exists in DiseaseEvent — 324 reported, 9 confirmed, 15 deaths, cited to NCDC's 2024 Situation Reports.

Lagos citizens alive during Jun–Dec 2024 become eligible via the HistoricalDiseaseEvent channel in PatientEligibility.

Male, DOB 1984-10-27 — a confirmed A00 (cholera) diagnosis on a published synthetic Visit row, dated inside the documented 6 Jun – 31 Dec 2024 outbreak window.

The diagnosis, visit and patient records above are included in the published Lagos release — Health generation certified 21/21 structural PASS.

Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™

Explore Lagos city overview →Browse Lagos certification records →See the Evidence →Review licensing & delivery details →Configure full-domain access →Browse Health Data →Explore Multi-Domain Access →

Contact SD for supporting artifacts →

Health.Trace recorded care encounters.

Overview

Domain scope

Public sample access

Known limits

Published domain scope.

Domain scope.

Samples & fields

Published sample records.

Public sample

Given name

Family name

Visit date

Visit type

Age at visit

Visit facility name

Triage priority

Diagnosis code (ICD-10)

From city health conditions to one citizen's record.

Connections

Known and possible relationships

Known and possible relationships.

Domain guide

Health · archived guide edition

Modelled entities.

Health changes as the citizen does.

The city remembers its outbreaks.

Historical events aren't decorations.

Evidence becomes synthetic health activity.

Evidence & limits

Scope and known limits

Known limits.

Does the synthetic health system resemble the city?

Health gets stronger with every release.

Access & datasets

Scope your data request

Review rights and delivery

Recorded example.

Health.
Trace recorded care encounters.