Skip to main content
STRIPED DONKEYWe do the heavy lifting.

Nairobi · 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 Nairobi certification records

Published domain facts

Patients · Nairobi
3.44M
Healthcare visits
14.27M
Facilities
1,252
Historical health events
20

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 →

Known limits

Early histories rely on sparse, sometimes broader geographic evidence. Visits sample eligible citizens. Eligibility coverage and channel balance remain calibration gaps; diagnoses may use current geography. Co-occurring conditions do not establish clinical relationships unless explicitly modeled. Records are synthetic.

Review the source limits →
Full scope reference 2 documented sections
Published domain scope.

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 · Nairobi
3.44M
Healthcare visits
14.27M
Facilities
1,252
Historical health events
20
Domain scope.

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.

Nairobi City Twin™ · 1940–2026

Samples & fields

Published sample records.

Public sample · rows and field definitions

Public sample

Given nameFamily nameVisit dateVisit typeAge at visitVisit facility nameTriage priorityDiagnosis code (ICD-10)
KinuthiaMuriuki2026-06-30OPD50Kiamaiko Community ClinicNot recordedA09
AdipoOuma2026-06-30OPD62MakinaDispensaryNot recordedI63.9
NjambiNderitu2026-06-30IPD46Kayole North Private HospitalNot recordedA15.0

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: Kinuthia

Family name

The family name assigned to the synthetic resident.

Original field: LastName
Example: Muriuki

Visit date

The date recorded for the visit event.

Original field: VisitDate
Example: 2026-06-30

Visit type

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

Original field: VisitType
Example: OPD

Age at visit

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

Original field: AgeAtVisit
Example: 50

Visit facility name

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

Original field: VisitFacilityName
Example: Kiamaiko Community Clinic

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: A09

CSV ↓JSON ↓PARQUET ↓Field guide CSV ↓Field guide JSON ↓Inspect the dataset →
Research sample · rows and field definitions

Research sample

Visit dateVisit typeAge at visitVisit facility nameTriage priorityDiagnosis code (ICD-10)Visit referenceResident reference
9/19/2011 12:00:00 AMOPD23PHC MakongeniNot recordedD57.4100588613430155
9/15/2023 12:00:00 AMOPD24Dandora Area II Mission HospitalNot recordedC53.957396271969481
1/27/2017 12:00:00 AMIPD46PHC Kayole Central IINot recordedA53.91856629719126

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

Published field definitions · 8 visible fields

Visit date

The date recorded for the visit event.

Original field: VisitDate
Example: 9/19/2011 12:00:00 AM

Visit type

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

Original field: VisitType
Example: OPD

Age at visit

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

Original field: AgeAtVisit
Example: 23

Visit facility name

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

Original field: VisitFacilityName
Example: PHC Makongeni

Triage priority

The recorded urgency category assigned during the visit.

Original field: TriageLevel
Example: 1

Diagnosis code (ICD-10)

The published ICD-10 code identifying the recorded diagnosis.

Original field: DiagnosisICD10Code
Example: D57.4

Visit reference

The reference used to identify the visit associated with this record.

Original field: VisitId
Example: 10058861

Resident reference

The synthetic resident reference used to connect this record to other city data.

Original field: CitizenId
Example: 3430155

CSV ↓JSON ↓PARQUET ↓Field guide CSV ↓Field guide JSON ↓Inspect the dataset →
Complete published field dictionary · 128 fields · sample 1
CitizenIdResident reference
The synthetic resident reference used to connect this record to other city data.Example: 4458013
NationalIdNational identity reference
The synthetic national identity reference recorded for the resident.Example: NID001030004
FirstNameGiven name
The first name assigned to the synthetic resident.Example: Kinuthia
MiddleNameMiddle name
Any middle name assigned to the synthetic resident.Example: Mukami
LastNameFamily name
The family name assigned to the synthetic resident.Example: Muriuki
DOBDate of birth
The resident’s recorded date of birth.Example: 1975-12-15
GenderGender
The gender recorded for the synthetic resident; M and F denote male and female in these samples.Example: Male
EthnicGroupIdEthnic group reference
The reference used to identify the ethnic group associated with this record.Example: 1
CitizenWardIdCitizen ward reference
The reference used to identify the citizen ward associated with this record.Example: 84
CitizenWardResident’s ward
The ward recorded for the synthetic resident.Example: Kiamaiko
CitizenRegistrationDateCitizen registration date
The date recorded for the citizen registration event.Example: 1989-10-19
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: Head
PatientIdPatient reference
The reference used to identify the patient associated with this record.Example: 3346412
PatientNumberPatient number
The published reference number associated with the patient.Example: NRB-PAT-04458013
BloodGroupBlood group
The blood group recorded for the synthetic patient.Example: AB+
NHISNumberHealth insurance reference
The synthetic health-insurance reference recorded for the patient.Example: Not provided
PatientRegistrationDatePatient registration date
The date recorded for the patient registration event.Example: 2001-03-06
RegisteredFacilityIdRegistered facility reference
The reference used to identify the registered facility associated with this record.Example: 231
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: NRB-HLT-084-201
RegisteredFacilityNameRegistered facility name
The name recorded for the registered facility associated with this record.Example: Kiamaiko Community Clinic
RegisteredFacilityLevelRegistered facility level
The service level assigned to the patient’s registered healthcare facility.Example: 2
RegisteredFacilityTypeRegistered facility type
The category or type assigned to the registered facility in the source record.Example: Private-Clinic
RegisteredFacilityOwnershipRegistered facility ownership
The ownership category of the patient’s registered healthcare facility.Example: Private
VisitIdVisit reference
The reference used to identify the visit associated with this record.Example: 15134877
VisitDateVisit date
The date recorded for the visit event.Example: 2026-06-30
VisitTypeVisit type
The category or type assigned to the visit in the source record.Example: OPD
TriageLevelTriage priority
The recorded urgency category assigned during the visit.Example: 4
AdmissionDateAdmission date
The date recorded for the admission event.Example: 2026-06-30
DischargeDateDischarge date
The date recorded for the discharge event.Example: 2026-07-04
VisitWardIdVisit ward reference
The reference used to identify the visit ward associated with this record.Example: 84
EncounterStatusEncounter status
The state recorded for the encounter in this extract.Example: OUTPATIENT
AdmissionLengthDaysLength of admission (days)
The recorded duration of the admission, in days.Example: 4
AgeAtVisitAge at visit
The synthetic patient’s age in years at the time of the visit.Example: 50
VisitFacilityIdVisit facility reference
The reference used to identify the visit facility associated with this record.Example: 231
VisitFacilityCodeVisit facility code
The published code identifying the visit facility. Codes are retained as supplied in the source.Example: NRB-HLT-084-201
VisitFacilityNameVisit facility name
The name recorded for the visit facility associated with this record.Example: Kiamaiko Community Clinic
VisitFacilityLevelVisit facility level
The service level assigned to the facility where this visit took place.Example: 2
VisitFacilityTypeVisit facility type
The category or type assigned to the visit facility in the source record.Example: Private-Clinic
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: 15
HasMaternityMaternity recorded
Whether maternity is present in the associated source record. In the source file, 1 means yes and 0 means no.Example: No
HasEmergencyEmergency recorded
Whether emergency is present in the associated source record. In the source file, 1 means yes and 0 means no.Example: No
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: No
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: YES
AttendingStaffIdAttending staff reference
The reference used to identify the attending staff associated with this record.Example: 201
AttendingStaffNumberAttending staff number
The published reference number associated with the attending staff.Example: KMC-0000229
AttendingStaffNameAttending staff name
The name recorded for the attending staff associated with this record.Example: Mukwanjeru Simiyu
AttendingStaffCategoryAttending staff category
The classification assigned to the attending staff in the published source.Example: CHW
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: KMPDC-0001375
AttendingMDCNNumberAttending clinician registration
The published MDCN registration reference for the attending staff member.Example: Not provided
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-06-30
SystolicBPSystolic blood pressure
The upper value recorded in the patient’s blood pressure reading.Example: 122
DiastolicBPDiastolic blood pressure
The lower value recorded in the patient’s blood pressure reading.Example: 75
HeartRateBpmHeart rate (beats/min)
The recorded number of heartbeats per minute.Example: 91
TemperatureCTemperature (°C)
The recorded body temperature in degrees Celsius.Example: 36.9
RespRatePerMinBreathing rate (breaths/min)
The recorded number of breaths per minute.Example: 13
SpO2PctOxygen saturation (%)
The oxygen saturation percentage recorded for the patient.Example: 95
WeightKgWeight (kg)
The recorded body weight in kilograms.Example: 57.0
HeightCmHeight (cm)
The recorded height in centimetres.Example: 168.0
BMIBody mass index
The body mass index value recorded in the synthetic health data.Example: 20.20
DiagnosisCountDiagnosis count
The number of diagnosis records included in this extract for the associated person or entity.Example: 2
ConfirmedDiagnosisCountConfirmed diagnosis count
The number of confirmed diagnosis records included in this extract for the associated person or entity.Example: 2
DiagnosisIdDiagnosis reference
The reference used to identify the diagnosis associated with this record.Example: 12362347
DiagnosisICD10CodeDiagnosis code (ICD-10)
The published ICD-10 code identifying the recorded diagnosis.Example: A09
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: 2
ConditionICD10CodeCondition code (ICD-10)
The published ICD-10 code identifying the recorded condition.Example: I50.9
ConditionOnsetDateCondition onset date
The date recorded for the condition onset event.Example: 2026-06-30
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: 5
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: ONC
TestCodeTest code
The published code identifying the test. Codes are retained as supplied in the source.Example: AFP
ResultDateResult date
The date recorded for the result event.Example: 2026-06-30
ResultValueLaboratory result
The value recorded for the laboratory test; read alongside the result unit.Example: 1.640
UnitResult unit
The measurement unit recorded for the laboratory result.Example: ng/mL
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: 66574330
MedicationCodeMedication code
The published code identifying the medication. Codes are retained as supplied in the source.Example: CHL
MedicationNameMedication name
The name recorded for the medication associated with this record.Example: Chloramphenicol Eye Drops
DosageFormMedication form
The physical form of the medication, such as a tablet or liquid.Example: Drops
QuantityQuantity
The amount recorded for the medication or service, in the source’s stated units.Example: 3
DurationDaysDuration (days)
The recorded duration of the medication course or service, in days.Example: 5
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: 189863
ProcedureCodeProcedure code
The published code identifying the procedure. Codes are retained as supplied in the source.Example: PCI
ProcedureDateProcedure date
The date recorded for the procedure event.Example: 2026-06-30
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: I25.10
PerformingStaffNamePerforming staff name
The name recorded for the performing staff associated with this record.Example: Chebet Rono
PerformingStaffCategoryPerforming staff category
The classification assigned to the performing staff in the published source.Example: CHW
PerformingStaffSpecializationPerforming staff specialization
The clinical specialty recorded for the performing staff.Example: General Practice
ProcedureFacilityNameProcedure facility name
The name recorded for the procedure facility associated with this record.Example: Nyayo Highrise Tertiary 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: 433569
ReferralICD10CodeReferral diagnosis code
The ICD-10 code recorded in connection with the referral.Example: I50.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-06-30
ReferralOutcomeReferral outcome
The result recorded for the referral event.Example: Missed
ReferralFromFacilityReferring facility
The healthcare facility recorded as sending the referral.Example: Kiamaiko Community Clinic
ReferralFromFacilityLevelReferring facility level
The service level recorded for the facility sending the referral.Example: 2
ReferralToFacilityReceiving facility
The healthcare facility recorded as receiving the referral.Example: Babadogo 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 ↓
Complete published field dictionary · 177 fields · sample 2
VisitIdVisit reference
The reference used to identify the visit associated with this record.Example: 10058861
CitizenIdResident reference
The synthetic resident reference used to connect this record to other city data.Example: 3430155
HouseholdIdHousehold reference
The reference used to identify the household associated with this record.Example: 937053
PatientIdPatient reference
The reference used to identify the patient associated with this record.Example: 2342732
FullNameResident name
The full name assigned to the synthetic resident.Example: Nur Abdullahi
SnapshotDateSnapshot date
The date represented by this extract of the synthetic data.Example: 7/2/2026 12:00:00 AM
DOBDate of birth
The resident’s recorded date of birth.Example: 2/6/1988 12:00:00 AM
GenderGender
The gender recorded for the synthetic resident; M and F denote male and female in these samples.Example: Male
EthnicGroupEthnic group
The ethnic group assigned to the synthetic resident.Example: Somali
CitizenWardNameCitizen ward name
The name recorded for the citizen ward associated with this record.Example: Makongeni
HouseholdTypeHousehold type
The recorded household structure, such as a single-person or extended household.Example: Nuclear
HouseholdRoleRole in household
The resident’s recorded role within the household.Example: Head
HouseholdSizePeople in household
The number of residents recorded in the household.Example: 3
PatientNumberPatient number
The published reference number associated with the patient.Example: NRB-PAT-03430155
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: Not provided
PatientRegistrationDatePatient registration date
The date recorded for the patient registration event.Example: 9/4/1998 12:00:00 AM
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
RegisteredFacilityNameRegistered facility name
The name recorded for the registered facility associated with this record.Example: PHC Makongeni
RegisteredFacilityLevelRegistered facility level
The service level assigned to the patient’s registered healthcare facility.Example: 2
RegisteredFacilityOwnershipRegistered facility ownership
The ownership category of the patient’s registered healthcare facility.Example: Public
VisitDateVisit date
The date recorded for the visit event.Example: 9/19/2011 12:00:00 AM
VisitTypeVisit type
The category or type assigned to the visit in the source record.Example: OPD
TriageLevelTriage priority
The recorded urgency category assigned during the visit.Example: 1
AdmissionDateAdmission date
The date recorded for the admission event.Example: 1/27/2017 12:00:00 AM
DischargeDateDischarge date
The date recorded for the discharge event.Example: 1/30/2017 12:00:00 AM
VisitWardIdVisit ward reference
The reference used to identify the visit ward associated with this record.Example: 69
EncounterStatusEncounter status
The state recorded for the encounter in this extract.Example: OUTPATIENT
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: 23
VisitFacilityNameVisit facility name
The name recorded for the visit facility associated with this record.Example: PHC Makongeni
VisitFacilityLevelVisit facility level
The service level assigned to the facility where this visit took place.Example: 2
VisitFacilityTypeVisit facility type
The category or type assigned to the visit facility in the source record.Example: Health-Centre
VisitFacilityOwnershipVisit facility ownership
The ownership category of the facility where the visit took place.Example: Public
BedCountBed count
The number of bed records included in this extract for the associated person or entity.Example: 20
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: No
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: No
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: Yes
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. In the source file, 1 means yes and 0 means no.Example: Yes
AttendingStaffNameAttending staff name
The name recorded for the attending staff associated with this record.Example: Ogal Ouma
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: Anaesthesiology
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: 9/19/2011 12:00:00 AM
SystolicBPSystolic blood pressure
The upper value recorded in the patient’s blood pressure reading.Example: 124
DiastolicBPDiastolic blood pressure
The lower value recorded in the patient’s blood pressure reading.Example: 73
HeartRateBpmHeart rate (beats/min)
The recorded number of heartbeats per minute.Example: 74
TemperatureCTemperature (°C)
The recorded body temperature in degrees Celsius.Example: 36.9
RespRatePerMinBreathing rate (breaths/min)
The recorded number of breaths per minute.Example: 15
SpO2PctOxygen saturation (%)
The oxygen saturation percentage recorded for the patient.Example: 99
WeightKgWeight (kg)
The recorded body weight in kilograms.Example: 79.0
HeightCmHeight (cm)
The recorded height in centimetres.Example: 152.0
BMIBody mass index
The body mass index value recorded in the synthetic health data.Example: 34.19
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
DiagnosisICD10CodeDiagnosis code (ICD-10)
The published ICD-10 code identifying the recorded diagnosis.Example: D57.4
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: D57.4
ConditionOnsetDateCondition onset date
The date recorded for the condition onset event.Example: 9/19/2011 12:00:00 AM
ConditionResolvedDateCondition resolved date
The date recorded for the condition resolved event.Example: 3/10/2017 12:00:00 AM
ConditionStatusCondition status
The state recorded for the condition in this extract.Example: Chronic
ConditionSeverityCondition severity
The severity category recorded for the condition.Example: Mild
CancerStageCodeCancer stage code
The published code identifying the cancer stage. Codes are retained as supplied in the source.Example: IV
CancerStagedDateCancer staged date
The date recorded for the cancer staged event.Example: 9/15/2023 12:00:00 AM
LabResultCountLab result count
The number of lab result records included in this extract for the associated person or entity.Example: 5
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: CBC
TestCodeTest code
The published code identifying the test. Codes are retained as supplied in the source.Example: WBC
ResultDateResult date
The date recorded for the result event.Example: 9/15/2023 12:00:00 AM
ResultValueLaboratory result
The value recorded for the laboratory test; read alongside the result unit.Example: 10.448
UnitResult unit
The measurement unit recorded for the laboratory result.Example: 10*3/uL
AbnormalFlagResult flagged abnormal
The source’s indicator of whether the laboratory result is flagged as abnormal.Example: N
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
MedicationCodeMedication code
The published code identifying the medication. Codes are retained as supplied in the source.Example: AZI500
MedicationNameMedication name
The name recorded for the medication associated with this record.Example: Azithromycin 500mg
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: 9
IsDispensedDispensed
Whether the associated record is marked as dispensed. In the source file, 1 means yes and 0 means no.Example: Yes
MedicationDispensedDateMedication dispensed date
The date recorded for the medication dispensed event.Example: 1/27/2017 12:00:00 AM
DispensedQuantityQuantity dispensed
The quantity of medication recorded as supplied to the patient.Example: 7
DispensedDaysSupplyMedication supply (days)
The recorded number of days covered by the dispensed medication.Example: 9
DispenseStatusDispense status
The state recorded for the dispense in this extract.Example: completed
ProcedureCountProcedure count
The number of procedure records included in this extract for the associated person or entity.Example: 1
ProcedureCodeProcedure code
The published code identifying the procedure. Codes are retained as supplied in the source.Example: TONSIL
ProcedureDateProcedure date
The date recorded for the procedure event.Example: 3/10/2005 12:00:00 AM
ProcedureOutcomeProcedure outcome
The result recorded for the procedure event.Example: Success
PerformingStaffNamePerforming staff name
The name recorded for the performing staff associated with this record.Example: Hassan Mahad
ProcedureFacilityNameProcedure facility name
The name recorded for the procedure facility associated with this record.Example: PHC Pangani IV
ReferralCountReferral count
The number of referral records included in this extract for the associated person or entity.Example: 1
ReferralReasonReferral reason
The reason recorded for the referral event.Example: HasOncology not available at referring facility
ReferralDateReferral date
The date recorded for the referral event.Example: 9/15/2023 12:00:00 AM
ReferralOutcomeReferral outcome
The result recorded for the referral event.Example: Attended
ReferralFromFacilityReferring facility
The healthcare facility recorded as sending the referral.Example: Dandora Area II Mission Hospital
ReferralToFacilityReceiving facility
The healthcare facility recorded as receiving the referral.Example: Babadogo Tertiary Hospital
AllergyCountAllergy count
The number of allergy records included in this extract for the associated person or entity.Example: 1
AllergyCodeAllergy code
The published code identifying the allergy. Codes are retained as supplied in the source.Example: DUSTMITE
ReactionTypeReaction type
The category or type assigned to the reaction in the source record.Example: Rash
AllergySeverityAllergy severity
The severity category assigned to the recorded allergy.Example: Severe
RiskFactorCountRisk factor count
The number of risk factor records included in this extract for the associated person or entity.Example: 1
RiskFactorCodeRisk factor code
The published code identifying the risk factor. Codes are retained as supplied in the source.Example: AIR_PM25
RiskFactorSeverityRisk factor severity
The severity category assigned to the recorded risk factor.Example: Low
ImmunizationCountImmunization count
The number of immunization records included in this extract for the associated person or entity.Example: 5
VaccineNameVaccine
The name of the vaccine recorded for the immunization.Example: Yellow Fever Vaccine
DoseNumberVaccine dose number
The dose sequence number recorded for the immunization.Example: 1
AdministeredDateAdministered date
The date recorded for the administered event.Example: 11/5/1988 12:00:00 AM
ImmunizationCompletedImmunization completed
Whether the immunization is recorded as complete. In the source file, 1 means yes and 0 means no.Example: Yes
MaternityCountMaternity count
The number of maternity records included in this extract for the associated person or entity.Example: 1
GestationalAgeWeeksGestational age (weeks)
The recorded stage of pregnancy, in weeks.Example: 41
ExpectedDeliveryDateExpected delivery date
The date recorded for the expected delivery event.Example: 6/5/2007 12:00:00 AM
DeliveryDateDelivery date
The date recorded for the delivery event.Example: 6/11/2007 12:00:00 AM
DeliveryModeDelivery method
The recorded mode of delivery for the maternity event.Example: SVD
MaternityOutcomeMaternity outcome
The outcome category recorded for the maternity event.Example: Live-Birth
HealthClaimCountHealth claim count
The number of health claim records included in this extract for the associated person or entity.Example: 1
HealthClaimServiceTypeHealth claim service
The service category associated with the health claim.Example: Visit
HealthClaimAmountHealth claim amount
The amount recorded for the health claim, in local currency.Example: 800.00
HealthClaimStatusHealth claim status
The state recorded for the health claim in this extract.Example: PartiallyApproved
CoverageIdCoverage reference
The reference used to identify the coverage associated with this record.Example: Not provided
CoverageAcquisitionTypeHow coverage was obtained
The recorded route through which the insurance coverage was acquired.Example: Not provided
CoverageIsPrimaryPrimary coverage
Whether this insurance coverage is recorded as primary.Example: Not provided
CoverageStatusCoverage status
The state recorded for the coverage in this extract.Example: Not provided
InsClaimCountInsurance claim count
The number of insurance claim records included in this extract for the associated person or entity.Example: Not provided
InsClaimAmountInsurance amount claimed
The amount requested in the insurance claim, in local currency.Example: Not provided
InsClaimApprovedAmountInsurance amount approved
The approved amount for the insurance claim, in local currency.Example: Not provided
InsClaimPaidAmountInsurance amount paid
The amount paid against the insurance claim, in local currency.Example: Not provided
InsClaimStatusInsurance claim status
The state recorded for the insurance claim in this extract.Example: Not provided
InsClaimFraudFlagInsurance fraud flag
The source’s synthetic flag for possible fraud in the insurance claim.Example: Not provided
DiseaseStateCountDisease state count
The number of disease state records included in this extract for the associated person or entity.Example: 6
DiseaseStateCodeDisease state code
The published code identifying the disease state. Codes are retained as supplied in the source.Example: UNCONTROLLED
DiseaseStateDateDisease state date
The date recorded for the disease state event.Example: 12/29/2021 12:00:00 AM
DiseaseStateICD10CodeDisease state icd-10 code
The published code identifying the disease state icd-10. Codes are retained as supplied in the source.Example: D57.2
CarePlanCountCare plan count
The number of care plan records included in this extract for the associated person or entity.Example: 3
CarePlanICD10CodeCare plan icd-10 code
The published code identifying the care plan icd-10. Codes are retained as supplied in the source.Example: D57.2
CarePlanStatusCare plan status
The state recorded for the care plan in this extract.Example: active
CarePlanStartDateCare plan start date
The date recorded for the care plan start event.Example: 12/29/2021 12:00:00 AM
CarePlanEndDateCare plan end date
The date recorded for the care plan end event.Example: Not provided
CarePlanGoalDescriptionCare plan goal
The stated goal recorded for the patient’s care plan.Example: Complete full 6-month treatment regimen
CarePlanGoalTargetDateCare plan goal target date
The date recorded for the care plan goal target event.Example: 9/3/2023 12:00:00 AM
CarePlanGoalAchievementStatusCare goal progress
The recorded progress or completion status of the care plan goal.Example: in-progress
CareTeamStatusCare team status
The state recorded for the care team in this extract.Example: active
CareTeamMemberCountCare team member count
The number of care team member records included in this extract for the associated person or entity.Example: 1
CareTeamMemberRoleCare team role
The role recorded for the member of the patient’s care team.Example: PRIMARY
CareTeamMemberStaffCategoryCare team member staff category
The classification assigned to the care team member staff in the published source.Example: Clinical-Officer
ImagingStudyCountImaging study count
The number of imaging study records included in this extract for the associated person or entity.Example: 1
ImagingStudyCodeImaging study code
The published code identifying the imaging study. Codes are retained as supplied in the source.Example: CXR
ImagingOrderedDateImaging ordered date
The date recorded for the imaging ordered event.Example: 9/25/2019 12:00:00 AM
ImagingPerformedDateImaging performed date
The date recorded for the imaging performed event.Example: 9/25/2019 12:00:00 AM
ImagingSourceICD10CodeImaging-related diagnosis code
The ICD-10 code recorded as the reason for the imaging study.Example: A15.0
ImagingFindingImaging finding
The finding recorded in the synthetic imaging study.Example: No acute abnormality
ImagingIsAbnormalImaging flagged abnormal
Whether the source flags the imaging finding as abnormal. In the source file, 1 means yes and 0 means no.Example: No
ImagingReportedDateImaging reported date
The date recorded for the imaging reported event.Example: 9/27/2019 12:00:00 AM
PatientDeviceCountPatient device count
The number of patient device records included in this extract for the associated person or entity.Example: 1
DeviceCodeDevice code
The published code identifying the device. Codes are retained as supplied in the source.Example: MOBILITY
DeviceStartDateDevice start date
The date recorded for the device start event.Example: 4/24/2024 12:00:00 AM
DeviceEndDateDevice end date
The date recorded for the device end event.Example: Not provided
DeviceStatusDevice status
The state recorded for the device in this extract.Example: active
SymptomCountSymptom count
The number of symptom records included in this extract for the associated person or entity.Example: 1
SymptomCodeSymptom code
The published code identifying the symptom. Codes are retained as supplied in the source.Example: FEVER
SymptomOnsetDateSymptom onset date
The date recorded for the symptom onset event.Example: 1/26/2022 12:00:00 AM
SymptomSeveritySymptom severity
The severity category assigned to the recorded symptom.Example: Moderate
SymptomResolvedDateSymptom resolved date
The date recorded for the symptom resolved event.Example: 2/12/2025 12:00:00 AM
SpecimenCountSpecimen count
The number of specimen records included in this extract for the associated person or entity.Example: 1
SpecimenTypeSpecimen type
The category or type assigned to the specimen in the source record.Example: Blood
SpecimenCollectionDateSpecimen collection date
The date recorded for the specimen collection event.Example: 9/14/2023 12:00:00 AM
DiagnosticReportCountDiagnostic report count
The number of diagnostic report records included in this extract for the associated person or entity.Example: Not provided
DiagnosticReportCategoryDiagnostic report category
The classification assigned to the diagnostic report in the published source.Example: Not provided
DiagnosticReportIssuedDateDiagnostic report issued date
The date recorded for the diagnostic report issued event.Example: Not provided
DiagnosticReportConclusionDiagnostic conclusion
The conclusion recorded in the synthetic diagnostic report.Example: Not provided
DiagnosticReportStatusDiagnostic report status
The state recorded for the diagnostic report in this extract.Example: Not provided
Download complete field guide JSON ↓
Additional records and schema context 1 documented sections
Take the Nairobi Health demo with you.

Take the Nairobi Health demo with you.

Inspect the published definitions and release context.

Read the published detail

Download the same public synthetic examples used in this Health preview. Use them to inspect structure, test research workflows, prototype analytics or evaluate grounded narrative behavior.

Structured encounter details, readable narratives, claim evidence and grounding summaries from the technology preview above.

A spreadsheet- and notebook-ready sample for inspecting synthetic health records and testing analysis or research workflows.

Continue into the public data explorer when you want to inspect the wider Health domain without downloading a file.

Need the release evidence instead? Certification and realism results remain available in the dedicated evidence views.

Download JSON ↓Download CSV ↓Explore Health Data →Browse Nairobi certification records →View Health Evidence →

Connections

Known and possible relationships

Inspect the published definitions and release context.

Domain or contextRelationship and published scope
DemographicsPatient or resident identity, lifespan, sex and ward provide care context. Dated visits must respect the resident lifespan.
Facilities and geographyVisits carry facility and area context where supplied; the same resident can have repeated visits.
BusinessFacility-to-business context is optional, not an identity link on every care record.
InsuranceCare eligibility and claims can be analysed alongside health events; the public guide does not expose every physical linkage.
TransportMobility incidents can be compared with injury and diagnosis context. This does not assert a direct trip-to-visit join.
WaterThe 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.

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 contextRelationship and published scope
DemographicsPatient or resident identity, lifespan, sex and ward provide care context. Dated visits must respect the resident lifespan.
Facilities and geographyVisits carry facility and area context where supplied; the same resident can have repeated visits.
BusinessFacility-to-business context is optional, not an identity link on every care record.
InsuranceCare eligibility and claims can be analysed alongside health events; the public guide does not expose every physical linkage.
TransportMobility incidents can be compared with injury and diagnosis context. This does not assert a direct trip-to-visit join.
WaterThe documented area health-profile field is nullable and is not populated by a Water-domain generation model in the cited guide.
DemographicsInsuranceWaterBusinessTransport

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

Early histories rely on sparse, sometimes broader geographic evidence. Visits sample eligible citizens. Eligibility coverage and channel balance remain calibration gaps; diagnoses may use current geography. Co-occurring conditions do not establish clinical relationships unless explicitly modeled. Records are synthetic.

Read the source limits →
Open PDF ↗Download recorded guide ↓
Accessible HTML reference 6 documented sections
Modelled entities.

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 Nairobi.

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

Specimens, lab results, diagnostic reports and imaging studies tied to each visit through a real order → result chain.

Care plans, care teams and disease-state transitions tracked as a citizen's condition evolves over time.

Medication dispensing events, modeled as distinct from the prescription order that triggered them.

Patient-reported symptoms and medical device assignments connected to diagnosis and care context.

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.

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 Nairobi. 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.

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 →

Explore Historical Health Events →
Historical events aren't decorations.

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.

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.

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.

Published healthcare activity and service-use evidence where available.

Health facility, infrastructure and geographic sources.

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

Open Health Source Catalogue →

Review Nairobi release history →Open Health Source Catalogue →
From a structured health event to a narrative you can verify.

From a structured health event to a narrative you can verify.

Inspect the published definitions and release context.

Read the published detail

Choose a synthetic Nairobi encounter. The narrative is assembled only from facts present in the encounter or from explicitly declared derivations. Select a narrative line to see why it is there.

The underlying encounter contains vital signs but no recorded diagnosis, medication, procedure, laboratory result or referral. FCTE does not invent missing clinical facts.

GROUNDED claims come directly from the synthetic encounter. DERIVED claims use declared, reproducible transformations of recorded values. This preview does not add speculative clinical content.

Grounded narratives can also surface semantic inconsistencies that are difficult to notice when records are reviewed only as rows and fields.

DemoSynthetic residentEncounterDateCare facilityClinical recordGrounded narrativeClaimsGroundingOpen
Open Grounded Narrative Demo →Download JSON ↓Download these 4 records as JSON ↓Explore Health Data →

Evidence & limits

Scope and known limits

Early histories rely on sparse, sometimes broader geographic evidence. Visits sample eligible citizens. Eligibility coverage and channel balance remain calibration gaps; diagnoses may use current geography. Co-occurring conditions do not establish clinical relationships unless explicitly modeled. Records are synthetic.

Evidence, findings and release history 2 documented sections
Known limits.

Known limits.

Early histories rely on sparse, sometimes broader geographic evidence. Visits sample eligible citizens. Eligibility coverage and channel balance remain calibration gaps; diagnoses may use current geography. Co-occurring conditions do not establish clinical relationships unless explicitly modeled. Records are synthetic.

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. Earlier decades are reconstructed from dated public-health reports and broader national or regional evidence where city-specific observations are unavailable.

Some historical disease counts and health-system indicators are available only at Kenya-wide or broader geographic resolution. Nairobi values derived from those sources are calibrated city estimates and are labeled as such rather than presented as direct city 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.

Some longitudinal diagnosis context uses current rather than period-specific geography. The measured impact is small and remains a disclosed model boundary; the public site does not publish the exact affected-record count or internal weighting method.

The current Patient population and eligibility-channel mix are generated through the Health eligibility model and remain calibration targets rather than fixed empirical truths. These are tracked realism gaps, not referential-integrity defects: every generated Patient row remains internally consistent with its linked citizen and health records.

View All Health Limitations →

View All Health Limitations →
Health gets stronger with every release.

Health gets stronger with every release.

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

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.

Nairobi Health data refresh — 21/21 structural checks now pass (closed the last disclosed visit-dating regression) and two independently-discovered defects were fixed at the source: a TB diagnostic flow and a transport-accident diagnosis flow could each attach a diagnosis to a maternal/child-health visit outside its clinical scope, confirmed in the published source and closed with 0 remaining violations. Also closed: specimen/lab-result linking, TB confirmatory-result date ordering, and a disease-state transition date-ordering edge case.

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

Removed unnecessary performance restrictions from record generation, Nairobi, 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
Published access and recorded examples 1 documented sections
Recorded example.

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 real, documented event in the historical health calendar — intensity multiplier 3.00, the highest of any entry in the table, sourced to the global pandemic period.

Male, DOB 1991-05-01 — a real Patient record eligible during the outbreak window.

A confirmed U07.1 (COVID-19) diagnosis on a published synthetic Visit row, dated inside the documented outbreak period.

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

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

Explore Nairobi city overview →Browse Nairobi 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 →