Platform · Public facility directories

Public Facility Directory Data

Where every hospital, pharmacy and care home is, and what the regulator last said about it. Facility by facility, dated.

Public facility directory data covers official directories of healthcare facilities — for example the CMS Provider of Services files and Care Compare data in the US, NHS organisation data and the CQC directory in England. Records are facility-level. Inspection ratings are the regulator's, recorded with their date. Some directories also name individuals, such as registered managers; those names are excluded by default.

A facility directory is the map every other healthcare dataset gets joined to. It has to be current, and honest about when it was.

Get a free sample See sample data

Free pilot on your own Public facility directories list, returned in 24 hours. No card, no trial clock — and you keep the sample data either way.

facility_directories_sample.jsonl LIVE FEED

{"directory":"CMS POS","facility_id":"as published","facility_type":"hospital"} {"rating":"as published","rating_date":"as published","rating_body":"regulator"} {"registered_manager_name":null,"event":"closure","event_date":"2026-06-30"}

illustrative sample rows · per directoryfacilities, dated · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to Public facility directories or its owners. Public facility directories and related marks belong to their respective owners, used here only to name the publicly accessible source this service collects from.

Our Data Powers

B2C Marketplace

amazon

D2C + Marketplace

NYKAA

D2C + Marketplace

Walmart

FMCG Marketplace

udaan

Food Delivery

Uber Eats

Quick Commerce

blinkit

Taxi Aggregator

Uber

E-Commerce

Tmall

Public facility directories at a glance

How we handle Public facility directories specifically

Platform-specific handling, not a generic retail template pointed at a different domain.

Sources: CMS POS and Care Compare; NHS ODS; CQC and equivalents
Unit: The facility
Ratings: The regulator's, with inspection date
Named individuals: Excluded by default
Identifiers: Official codes kept as published
Changes: Openings, closures, re-registrations as events
Formats: Bulk files where offered
Refresh: On each directory's release cycle

Platform specifics

Facilities, dated

These are the reasons a Public facility directories dataset needs its own handling rather than a shared retail schema.

What a directory record is

Official directories give each facility an identifier, a type, an address and a status, and some add services, capacity or ratings. Many are published as downloadable files on a regular cycle.

directory, release and read_at on every record.
facility_id exactly as published, with its code system.
rating and rating_date recorded as the regulator's, never recalculated or combined into our own score.
Openings, closures and re-registrations recorded as dated events.

Joins, individuals and what we do not do

Joining directories

Facilities are matched across directories on official identifiers where available, otherwise on name and address, with match_basis recorded. Hospital price files join here too — see our price transparency page.

Named individuals

Where a directory names individuals, such as registered managers, the names are excluded unless a documented purpose requires them, on the same terms as our provider register page.

What we do not do

Recalculate or combine ratings, keep closed facilities without a date, include named individuals by default, or collect any patient data.

Scope

What we collect on Public facility directories, and what we do not

The right column matters more than the left. Anyone can list fields; the limits are what tell you whether the dataset will hold up.

✅ What we collect

directory, release and read_at on every record
facility_id with its code system
rating and rating_date as the regulator's
Openings and closures as dated events
Cross-directory joins with match_basis
Bulk files used where offered
Services and capacity as published
Named individuals excluded by default
Refresh on each release cycle

❌ What we do not, and why

Ratings recalculated or combined into scores
Closed facilities kept without a date
Named individuals included by default
Inspection report text republished
Any patient data

Core Public facility directories fields

The full dictionary is agreed during scoping. These are the fields specific to this platform.

Field	What it is on this platform
directory / release / read_at	Source and date
facility_id / code_system	As published
facility_name / facility_type	As published
address / region	As published
status / status_date	As published
services / capacity	As published
rating / rating_date / rating_body	The regulator's
event / event_date	Openings, closures, re-registrations
match_basis	For cross-directory joins
geocode_derived	Labelled, if requested
observed_at	Timestamp

Use cases

What teams do with Public facility directories data

Healthcare network mapping

Every facility of a type, by area, current on a date.

Market entry and coverage

Where facilities open and close.

Quality context

Regulator ratings beside other data, each dated.

Master data for joins

A facility key for pricing and directory datasets.

The 24-hour sample — run on your sources, not ours

Send us a Public facility directories item or category list. We run real collection against it and return the output within 24 hours, with the platform-specific fields populated so you can check them yourself rather than take our word for it.

Real extraction from your actual sources
Returned within 24 hours
Coverage and QA note included
You keep the data either way
No card, no trial clock
Named engineer on the call

Get my free sample Book a 20-min scoping call Reply within one business day. Reference calls available under NDA.

How we engage

Three ways to engage us

Same collection pipeline and QA underneath. The difference is who holds the schedule and how the data reaches you.

Managed service (most common)

We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.

Dedicated engineer assigned to your account
Site changes fixed by us, not reported to you
Scheduled delivery to your warehouse or S3
Named contact on Slack or email

Best fit: Teams who need the data, not the infrastructure.

API access

The same collection pipeline exposed as an authenticated REST endpoint your systems query directly.

On-demand and scheduled endpoints
Rate limits agreed to your load profile
Sandbox keys for integration testing
Versioned schema with deprecation notice

Best fit: Product and engineering teams building on live data.

One-time or project extraction

A defined pull for a specific question — market sizing, diligence, a pitch, a one-off audit.

Fixed scope agreed in writing upfront
Single delivery with full QA report
Methodology documented for your records
Converts to managed if you want continuity

Best fit: Research, strategy and diligence work with a deadline.

Pricing

Every engagement is quoted individually, because the honest answer depends on your scope: how many sources, how many records, how often, and how the data reaches you. We scope it with you, run a free pilot on your own sources, and then quote a fixed monthly figure — no per-request metering and no overage billing when volumes move. Request a quote and you will have a number after one call.

Public facility directories is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Public facility directories data becomes useful when it sits next to the competitor set on one schema, refreshed on one schedule, so a price index or availability comparison is genuinely like-for-like.

That is what healthcare & pharmacy data covers, and a Public facility directories-only engagement can be expanded into it without rebuilding. If you already know you need several platforms, start there instead — it is the same pipeline and usually the better scoping conversation.

FAQ

Public facility directories data scraping: frequently asked questions

Platform-specific questions, including what cannot be collected here.

No. They are the regulator's, recorded with the inspection or rating date. We never recalculate them.

Because the facility is the unit, and names of individuals are personal data. They are included only for a documented purpose.

As current as each directory's release, which is recorded on every record.

Yes, on official identifiers where possible, with the match basis recorded.

No.

It depends on directories, regions and refresh.

Talk to us.

See real Public facility directories data before you commit to anything

Send us an item or category list. We return the output within 24 hours with the platform-specific fields populated.

Get a free sample Talk to an engineer

Free pilot, no card, no obligation. If we cannot collect a field you need on this platform, the sample shows you that too.

Hear It Directly from Our Clients

Watch how businesses like yours are using Actowiz data to drive growth.

▶

1 min

★★★★★

"Actowiz Solutions offered exceptional support with transparency and guidance throughout. Anna and Saga made the process easy for a non-technical user like me. Great service, fair pricing!"

Thomas Galido

Co-Founder / Head of Product at Upright Data Inc.

▶

2 min

★★★★★

"Actowiz delivered impeccable results for our company. Their team ensured data accuracy and on-time delivery. The competitive intelligence completely transformed our pricing strategy."

Iulen Ibanez

CEO / Datacy.es

▶

1:30

★★★★★

"What impressed me most was the speed — we went from requirement to production data in under 48 hours. The API integration was seamless and the support team is always responsive."

Febbin Chacko

-Fin, Small Business Owner