Synthetic dataset
How does use of care differ between people with and without insurance?
Recorded encounter counts, distinct-user proportions and person-time rates by health coverage state.
HEALTH-5 · Made-to-order synthetic research dataset
- Proposed study unit
- Resident during a coverage period
- Catalogue structure
- Question-specific research data
- Custom city requests
- African Major Cities
- Dates and final scope
- Agreed with your quote
Overview
Custom study · Scope and validation required
Population, dates, source fields, joins and question-specific validation must be agreed for this study.
- Population
- Residents with dated health coverage status and documented care-observation intervals; retain unknown coverage separately.
- Proposed unit
- resident_coverage_period
- Observation anchor
- Start of each coverage-valid observation interval; coverage changes divide follow-up into separate periods.
- Measure to define
- Recorded encounter counts, distinct-user proportions and person-time rates by health coverage state.
Recorded encounter counts, distinct-user proportions and person-time rates by health coverage state.
The study calls for Coverage start and end dates, Dated care encounters, Eligible residents and observation time and Household context at care date. The measure to examine is recorded encounter counts, distinct-user proportions and person-time rates by health coverage state.
Research datasets are prepared after an order for the selected city, date range and study requirements. The final schema and dated relationships are agreed for that extract.
- Onboarded city options
- Nairobi (Kenya) · Lagos (Nigeria)
- Custom city requests
- African Major Cities · Additional cities require availability, scope and quote confirmation.
- Data type
- Synthetic
- Priced domains
- Health, Households, Insurance, Demographics
- Catalogue structure
- Question-specific research data
Key features
Record concepts for your order-specific extract.
Coverage start and end dates
Required record concept; source fields and joins to verify.
Dated care encounters
Required record concept; source fields and joins to verify.
Eligible residents and observation time
Required record concept; source fields and joins to verify.
Household context at care date
Required record concept; source fields and joins to verify.
Who it is for
- Researchers
- analysts
- data scientists
- policy teams
Data & Schema
- Proposed study unit
- Resident during a coverage period
Planned records and relationships for this study.
Record concepts for your extract
- Coverage start and end dates
- Dated care encounters
- Eligible residents and observation time
- Household context at care date
The agreed specification defines the final columns, keys, relationships and observation period for your order.
Question-specific sample in preparation
The CSV is a template of planned record concepts. It does not contain verified sample records or establish the paid schema.
Use Cases
Describe covered versus uncovered rates using comparable observation windows and stated case-mix assumptions.
Proposed questions for your custom order
- How does use of care differ between people with and without insurance?
Proposed research and analytical applications
- Study design
- group comparison
- longitudinal analysis
Methodology & Quality
- Data generation
- FCTE synthetic city engine
- Data classification
- Synthetic
FCTE generation methods and published city/domain checks provide source context. The order defines the final extract and the release-specific checks, documentation and limitations supplied with it.
Known limitations
- Time-specific health coverage and observation eligibility require source verification.
- Coverage selection and care need may explain differences; this comparison does not identify an insurance effect.
- Absence of recorded care does not prove lack of access or unmet need.
- Confirm coverage dates and benefit scope; a coverage flag does not establish benefit adequacy.
- Synthetic records describe generated scenarios; they do not establish observed population prevalence or real-world causal effects.
Delivery & License
- Catalogue base price
- $395 USD
- Price basis
- Base price per selected city
- Availability
- Prepared after order
The displayed catalogue amount is a base price per selected city. Your requested dates, population, fields, formats and usage rights determine the agreed scope and final quote. Applicable published discounts and taxes are confirmed with that quote.
Your prepared package
Your order confirms the data files, documentation, evidence, examples and release controls included in the prepared package.
- Agreed data extract
- Schema and field documentation
- Release-specific evidence and limitations
- Agreed loading or analysis examples
- Licence, manifest, checksums and delivery note
Package layout
Illustrative filenames. Your agreed order lists the final files and formats. Certification, benchmark splits and model examples are included only when specified.
SD_RESEARCH_DATASET/ ├── data/ │ ├── health_records.parquet │ ├── household_history.parquet │ ├── insurance_records.parquet │ └── citizens.parquet ├── documentation/ │ ├── README.md │ ├── DATA_DICTIONARY.csv │ ├── SCHEMA.md │ └── METHODOLOGY.md ├── evidence/ │ ├── CERTIFICATION.json │ ├── VALIDATION_REPORT.pdf │ └── KNOWN_LIMITATIONS.md ├── MANIFEST.json ├── CHECKSUMS.sha256 └── LICENSE.pdf
Delivery process
Confirm the cities, date range, records, formats, rights and price in writing. The order-specific extract is then prepared and supplied under the agreed payment and delivery conditions.
One secure download package for the agreed release and licensed entity.
Delivery timing, access expiry, formats and prerequisites are confirmed in the accepted order.
Support, refreshes, future releases, hosting and APIs are included only when expressly ordered.
Data Licensing Agreement · 2026-10
A non-exclusive, non-transferable licence for the named customer within the accepted scope and duration.
- Permitted use
- Internal research, development, testing and analytics within the accepted order.
- Model training
- Model training, external applications, commercial distribution and access by other legal entities must be expressly addressed in the order.
- Redistribution
- Raw or substantially reconstructable data cannot be resold, published or redistributed without separate written authorization.
- Attribution
- Preserve release provenance and applicable third-party notices. Published outputs must identify the data as synthetic.
FAQ
Is this real personal data?
No. The records are synthetic and do not represent actual identifiable people or reproduce an individual's historical experience.
What does the catalogue price cover?
The displayed amount is a base price per selected city. The final scope and quote are agreed for your requested dates, population, fields, formats and rights. Adding a dataset to the cart starts the existing checkout inquiry; it does not purchase an unrestricted custom extract.
What can I inspect before ordering?
Review the planned record concepts and sample template. Question-specific sample records are in preparation; you can request sample review before agreeing the release.
Is the dataset prepared for my requested dates?
Yes. Regular and Research datasets are prepared after an order, with the city, date range, population and other required scope agreed before preparation.
Can records be joined across domains?
The profile explains the intended relationships. The order-specific schema documents the supported keys, effective dates and joins for your agreed extract.
Can I use the dataset for AI or machine learning?
Review the study-specific inputs, outcomes and information cutoffs. The commercial order must expressly address model training and external applications. Public samples allow non-commercial AI and ML experimentation under the current free-sample policy.
Can I use the data commercially?
Commercial use follows the accepted dataset-specific scope and licence. A sample download, cart selection, inquiry or consent checkbox does not activate a commercial licence or complete payment.
Can I request another city, period or format?
Yes. Use Data Request to describe the required city, population, dates, record concepts and formats. Onboarded city options for this product: Nairobi and Lagos. Other African major cities can be requested; availability, scope and the quote must be confirmed.
What documentation and evidence are included?
The accepted order confirms the schema, methodology, evidence, examples and release controls supplied with your prepared extract.
How do I receive the dataset?
After scope, terms and payment conditions are agreed, Fidelra Africa prepares the order-specific extract and supplies it through a secure download package. Timing and download-access expiry are defined in the order.
Need different data?
Tell us the entities, fields, cities and time span you need.