Japan Health & Medical Data Search

Search official Japanese health and medical public data from e-Gov health open data and the Ministry of Health, Labour and Welfare portal in one run.

• ✅ Search 2 official Japanese health data sources at once
• ✅ Find datasets, portal resources, health publications, and medical information pages by keyword
• ✅ Get structured results with source labels and export them as CSV, JSON, or Excel
• ✅ Use one simple keyword input instead of checking multiple government sites manually
• ✅ Run it from Apify, automation tools, or AI assistants through Apify MCP

If you are researching Japanese healthcare, medical policy, public health topics, ministry resources, or open health datasets, the first problem is usually fragmentation. One source lives in the Japanese government's e-Gov open data catalog. Another source lives in the Ministry of Health, Labour and Welfare portal. Both are official, but they are separate search surfaces.

This Actor gives you one search workflow across both.

It is designed for:

• researchers
• analysts
• healthcare market intelligence teams
• policy researchers
• consulting teams
• public sector users
• AI agents that need structured access to Japanese health data discovery

---

What you can do with it

1. Search Japanese public health datasets by keyword

Use a topic like:

• cancer
• diabetes
• mental health
• vaccination
• elder care
• hospital
• drug safety

The Actor queries the supported official sources and returns matching dataset or portal entries.

This is useful when you need a fast first-pass discovery layer before doing deeper source-specific work.

2. Discover MHLW publications, pages, and health resources

The Ministry of Health, Labour and Welfare publishes a large amount of health-related information through its own portal structure.

This Actor helps surface:

• relevant ministry pages
• public information resources
• topic pages
• health-related government content

That makes it useful for:

• policy scanning
• health program research
• stakeholder briefings
• market entry research for Japan

3. Pull e-Gov health open data catalog matches

The e-Gov side is useful when you want open data catalog results rather than only ministry navigation pages.

This is especially useful for:

• data discovery
• public health research support
• identifying official datasets for downstream analysis
• sourcing Japanese government health data for dashboards or internal studies

4. Build a repeatable Japan health research workflow

Because the Actor runs on Apify, you can reuse it in:

• scheduled runs
• no-code automation
• agent workflows
• MCP-connected assistants

That makes it useful both for one-off discovery and repeated monitoring of a topic.

---

How to use it

This Actor is intentionally simple.

You only need:

1. a keyword
2. one or more sources
3. a maxResults limit

Default input

The default configuration is:

{
  "keyword": "cancer",
  "sources": ["egov_health", "mhlw"],
  "maxResults": 50
}

This matches the default input schema and is the easiest way to test the Actor.

Input fields

Field	Type	Default	What it does
keyword	string	cancer	Search term used across the selected Japanese health data sources
sources	array	["egov_health", "mhlw"]	Which official source groups to search
maxResults	integer	50	Maximum results returned per source, capped at 200

Available sources

Source key	What it searches
egov_health	e-Gov Health & Medical Open Data Catalog
mhlw	Ministry of Health, Labour and Welfare portal navigation links

If you leave sources empty in practice, the Actor defaults to both supported sources.

---

Example use cases

Use case 1: Find cancer-related Japanese health resources

If you want a broad discovery run for oncology-related official resources:

{
  "keyword": "cancer",
  "sources": ["egov_health", "mhlw"],
  "maxResults": 50
}

This is useful for:

• public health research
• market landscape scans
• ministry resource discovery
• dataset discovery before deeper analysis

Use case 2: Search only the ministry portal

If you only want Ministry of Health, Labour and Welfare portal results:

{
  "keyword": "vaccination",
  "sources": ["mhlw"],
  "maxResults": 50
}

This is useful when you want:

• ministry pages
• policy resources
• official public guidance pages

Use case 3: Search only e-Gov open data

If you only want open data catalog matches:

{
  "keyword": "hospital",
  "sources": ["egov_health"],
  "maxResults": 100
}

This is useful when your goal is dataset discovery rather than portal navigation.

---

What you get back

The Actor pushes matching rows from the selected source or sources into the default dataset.

Every result keeps its source-native structure as returned by the underlying SIP gateway search response. The Actor also adds a shared field:

Field	Meaning
source	The source key that produced the result (egov_health or mhlw)

Typical fields you may see

Depending on the source, rows may contain fields like:

• title
• url
• description
• other source-native metadata fields

The default dataset view is configured around the most common discovery-style fields:

• source
• title
• url
• description

Example output shape

{
  "title": "Cancer-related health resource",
  "url": "https://www.example.go.jp/health/cancer",
  "description": "Official health-related information page or catalog entry.",
  "source": "mhlw"
}

Actual rows vary by source. This Actor is a discovery/search tool, not a full normalized medical data warehouse.

---

Data sources included

This Actor currently supports 2 official Japanese health-related source groups.

1. e-Gov Health & Medical Open Data Catalog

Best for:

• official open data discovery
• dataset hunting
• identifying public health and medical data resources

2. MHLW portal navigation links

Best for:

• ministry resource discovery
• topic page lookup
• public guidance and official portal content

Together, these two sources make the Actor a practical first-step discovery tool for Japanese health and medical public data.

---

Pricing

This Actor uses Apify platform pricing.

At the time of writing, the Actor page pricing is:

What triggers a charge	Cost
Actor start	$0.005
Each record	$0.002

If you want a cheap test run:

• use one keyword
• keep maxResults small
• search only one source first

That gives you a fast preview before running broader discovery searches.

---

When to use this Actor

Use this Actor when you want:

• quick discovery of Japanese health and medical public resources
• one search across e-Gov and MHLW
• source-tagged results that can feed spreadsheets, automation, or LLM workflows
• a lightweight Japan health public data lookup workflow

It is especially useful for:

• healthcare research
• policy scanning
• Japanese public sector intelligence
• health-tech market research
• international research teams working on Japan

---

When to use something else

This Actor is best for discovery and search, not deep record extraction from a single specialized medical database.

You may want another tool if you need:

• a dedicated disease registry
• a full regulatory or pharma workflow
• one specific ministry dataset with custom filters
• hospital/provider-level structured extraction beyond search discovery

In those cases, a more specialized actor or source-specific workflow may be better.

---

FAQ

Does this Actor search all Japanese healthcare databases?

No. It currently searches the 2 official source groups configured in the Actor: e-Gov health open data and the MHLW portal layer.

Is this Actor good for discovery or deep extraction?

Primarily discovery. It is meant to help you find relevant official resources quickly.

Can I search in English?

You can try English keywords, but Japanese-language queries will often be more effective depending on the source content.

Does the Actor normalize all fields across sources?

No. It keeps source-native results and adds a source field for routing.

What is the result cap?

maxResults is capped at 200 per source.

Can I use it from AI assistants?

Yes. You can use it through Apify MCP or standard Apify integrations.

---

Connect it to your workflow

This Actor can be used from:

• the Apify UI
• Make
• n8n
• Zapier via Apify
• ChatGPT and Claude via Apify MCP
• your own code through the Apify API

If your workflow already uses Apify Actors, this is a lightweight Japan health data discovery step you can drop in immediately.