Data sources

Strong care-sector data, built from government and regulator sources.

CareHomeData starts with official care-sector records, then adds public-register matching, geography, planning evidence and organisation-published signals so every useful field has a source class.

Why the data is defensible

Commodity lists sell rows. CareHomeData keeps official facts, public evidence and inferred signals apart so users can see what came from government, what was matched, and what needs review.

Official

CQC care service spine

The regulator record is kept separate from enrichment and inference.

Public

Government register matching

Companies House and related public registers add ownership context.

Tracked

Planning and market signals

Local authority planning evidence highlights supply before registration.

Source map

The source categories behind the dashboard

Official

CQC regulated care data

The Care Quality Commission provides the core England record for regulated care homes, homecare agencies, providers, service types, locations, ratings and registration status.

Used as the protected source of truth for regulated-service facts.

Government

Companies House and public registers

Company identity, officers, persons with significant control, filings, charity links and controller signals help turn provider names into an ownership and group context.

Stored as matched evidence with confidence, not as overwritten CQC facts.

Geography

NHS, ODS, ONS and local authority geography

NHS and government geography joins help place care services into ICB, region, local authority and postcode-market views for territory planning.

Used for segmentation, account planning and regional market analysis.

Signals

Planning applications and property evidence

Planning records can reveal new supply, extensions, redevelopment, change-of-use and operator intent before a new service appears in a regulator file.

Every planning signal should keep authority, reference, proposal and source URL.

Published

Organisation-published web evidence

Provider websites and lawful public pages can add contact routes, group pages, service descriptions and commercial context that official registers do not publish.

Contact routes are labelled separately from official facts and reviewed for acceptable use.

Product

CareHomeData matching and workflow layer

The value is not a raw file. It is cleaning, matching, provenance, confidence labels, saved research workflows, exports and repeatable territory intelligence.

Designed for business intelligence, not consumer care advice or resident-level data.

How it becomes intelligence

Built to go beyond a contact CSV

Established care-sector data products prove buyers value coverage, freshness and exportability. CareHomeData improves the trust layer by making provenance visible and separating official records from enriched commercial signals.

  1. 1

    Import official and public-source records without mixing source classes.

  2. 2

    Standardise names, addresses, postcodes, identifiers and service categories.

  3. 3

    Match providers to legal entities, groups, geography and public-register records.

  4. 4

    Attach source URLs, dates, confidence labels and boundary notes to enriched fields.

  5. 5

    Expose the useful workflow in the dashboard while keeping exports protected.

Field labels

Every important field should explain itself

Label
OfficialRegulator or government-origin fact.
Public-registerMatched company, charity or public body record.
Organisation-publishedEvidence published by the provider or related organisation.
InferredCareHomeData-derived signal that needs confidence and review.

Boundaries

Clear limits make the product stronger

CQC does not provide care-home or homecare agency email addresses in its care directory. Contact routes are enriched separately from provider-published websites and other lawful public or organisation-published sources.

Planning applications are treated as evidence-backed signals, not proof that a future care service will open. Resident-level data is not part of the product.