Hospital facility record

医療法人定生会谷口病院

A summary of fields in the published hospital facility record. The facility name and other source proper names remain in Japanese unless the source supplies an English or romanized form.

Source-listed English or romanized name: Taniguchi Hospital

This value is shown as supplied by the source. MedOpen does not independently certify or rewrite source-supplied facility names and does not machine-translate or guess them.

This public record does not assess healthcare quality, treatment outcomes, rank, recommendation or current ability to accept patients. A listed service or notification does not establish current availability.

Facility overview

Reported beds
37The total is from the facility survey. The source field does not say whether beds are licensed, staffed, available or occupied. If the field is blank or unspecified, this page does not infer why.
Listed specialties
4Listing does not establish that appointments are available
Municipality
泉佐野市Osaka Prefecture
Address
大阪府泉佐野市大西1-5-20Original source text
Facility website
Open the facility websiteThe external site may be in Japanese.
Explore the public record

Analyse this hospital

Review ward-level public reporting, reference dates and comparison rules alongside the source.

Public healthcare data record

Hospital Intelligence

Beds & wards

From facility facts to ward-level published reporting.

Matched to official public data

The 2025 report matched 1 ward records. Function categories below count wards; they are not bed counts.

Current bed-function categories by ward count

Categories are reported for 1 of 1 matched wards. Wards without a published category are not assigned to a function.

  • Acute care1 wards
Comparison group

Reported-bed comparison

Comparison view

Regional context uses the same secondary medical area first and widens to the prefecture when needed.

  • Hospital
  • Same secondary medical area · 泉州
Structural peers
68
Facilities eligible for reported beds
68
Facilities with observed values
68
About these comparison conditions

The structural cohort and the facilities eligible for this metric can differ. Facilities without a verified match or an observed value are not treated as zero.

This is descriptive context. It does not establish equivalent clinical services or patient populations, and it is not a measure of quality or superiority.

Peer Engine: hospital-intelligence-peer-engine-v1 · hospital-intelligence-peer-set-v1
Facility reported beds37 beds
Peer median150 beds
Peer middle 50 percent79–300 beds

Reported-bed source: MHLW hospital facility information · reference date 2026-06-01 · MHLW source page

Geographic boundary source: e-Stat secondary medical-area mapping · 2024-10-01 · e-Stat source page

This uses a separate dataset and reference date from the FY2025 ward report.

Differences between published reports

Among 1 wards with a stable source ward code, name and facility link, 4 observed values differed between releases. These are publication differences; no real-world cause is inferred.

FY2025 ward report

Function reference date 2025-07-01 · patient flows use the annual period shown separately

1 wards

The em dash marks source 0 values where true zero and unanswered cannot be distinguished. Open a ward for the raw value and source location.

病棟Acute carePermitted bedsGeneral 37 bedsLong-term care —
Same ward key confirmed across reports
Permitted general beds
37 beds
Permitted long-term care beds
Source shows 0; true zero and unanswered cannot be distinguished
Maximum general beds reported in use
27 bedsA reported maximum; this is not an occupancy or utilization rate.
Maximum long-term care beds reported in use
Source shows 0; true zero and unanswered cannot be distinguishedA reported maximum; this is not an occupancy or utilization rate.
New ward entries (annual)
1,563 entries
Ward inpatient-days (annual)
7,443 days
Ward exits (annual)
1,579 exitsMay include transfers between wards; it is not a hospital-wide discharge count.
Planned function at the next report date
Reported as plannedShown separately from the current function.
Field-level source locations
  • Current bed functionbed_function_2025_ward_kinki.xlsx · Sheet1!P2440563748ac62bbff241bff277985f1243aa861cebdb606b282e99ecd0a9ce487f6
  • Maximum long-term care beds reported in usebed_function_2025_ward_kinki.xlsx · Sheet1!X2440563748ac62bbff241bff277985f1243aa861cebdb606b282e99ecd0a9ce487f6
  • Maximum general beds reported in usebed_function_2025_ward_kinki.xlsx · Sheet1!T2440563748ac62bbff241bff277985f1243aa861cebdb606b282e99ecd0a9ce487f6
  • New ward entries (annual) bed_function_2025_ward_kinki.xlsx · Sheet1!BG2440563748ac62bbff241bff277985f1243aa861cebdb606b282e99ecd0a9ce487f6
  • Permitted long-term care bedsbed_function_2025_ward_kinki.xlsx · Sheet1!W2440563748ac62bbff241bff277985f1243aa861cebdb606b282e99ecd0a9ce487f6
  • Permitted general bedsbed_function_2025_ward_kinki.xlsx · Sheet1!S2440563748ac62bbff241bff277985f1243aa861cebdb606b282e99ecd0a9ce487f6
  • Planned function at the next report datebed_function_2025_ward_kinki.xlsx · Sheet1!Q2440563748ac62bbff241bff277985f1243aa861cebdb606b282e99ecd0a9ce487f6
  • Ward exits (annual)bed_function_2025_ward_kinki.xlsx · Sheet1!DT2440563748ac62bbff241bff277985f1243aa861cebdb606b282e99ecd0a9ce487f6
  • Ward inpatient-days (annual)bed_function_2025_ward_kinki.xlsx · Sheet1!DG2440563748ac62bbff241bff277985f1243aa861cebdb606b282e99ecd0a9ce487f6
Sources, reference periods and matching
Official data

Ministry of Health, Labour and Welfare, Japan · Bed Function Report Open Data

Official FY2024 release page

Official FY2025 release page

Reference and refresh

Ward function report date: 2025-07-01

Patient-flow period: 2024-04-01/2025-03-31

MedOpen import: 10/6/2026

Release: 2024-2025-v1.1.1 · hospital-intelligence-beds-wards-292cf0fd5ccb

Release manifest SHA-256: 293bf394c431fa07daec71bc3284f74af1a0016100966ecb5efe5b6c0137883d

Facility match

TIER_3_EXACT_COMPOUND

NFKC + whitespace-collapsed exact name; exact 2-digit prefecture; exact 5-digit official municipality code; unique in contemporaneous P13 snapshot

Current P13 identity snapshot: 2026-06-01

Reuse and modification

Source: Ministry of Health, Labour and Welfare, Japan, Bed Function Report Open Data (FY2024/FY2025). Modified and linked to P13 using exact deterministic matching.

MHLW terms of use · PDL 1.0

The source code is not an official P13 identifier. Displayed rows require a unique exact facility name, prefecture and municipality match in the historical P13 snapshot, followed by unchanged current name, address and geography. Match rule: exact-name-prefecture-municipality-temporal/v1.

Ward reports may not cover all facility activity. Permitted beds, reported maximum use, ward entries/exits and inpatient-days are ward-level fields. No facility totals, occupancy rate or average length of stay are calculated.

Outpatient function

1 April 2024 to 31 March 2025 (FY2025 reporting vintage)

Linked hospitals only; not nationally representative.

Peer counts are structural / outpatient-eligible / metric observed; middle 50% is Q1–Q3.

Referral rate (annual)· Form 1

10.9%

Published annual rate: annual referred patients ÷ annual initial patients.

泉州 · 68/30/30
Peer median 20.3% · Q1–Q3 7.1%–34.1%

Reverse-referral rate (annual)· Form 1

0.0%

Published value: 0%

Published annual rate: annual reverse-referred patients ÷ annual initial patients.

泉州 · 68/30/30
Peer median 11.1% · Q1–Q3 2.3%–40.1%

Referral-focused outpatient share (initial visit)· Form 2

21.0%

Published share: referral-focused consultation-days ÷ all initial outpatient consultation-days (not people).

泉州 · 68/32/29
Peer median 32.9% · Q1–Q3 15.4%–47.9%

Referral-focused outpatient share (revisit)· Form 2

16.6%

Published share: referral-focused consultation-days ÷ all revisit outpatient consultation-days (not people).

泉州 · 68/32/32
Peer median 9.4% · Q1–Q3 4.0%–26.8%

Descriptive published values; no quality assessment or recommendation.

Source: MHLW Outpatient Function Reporting · MedOpen English labels.

Professional hospital intelligence

Facility standards

Published records

Explore notifications listed in the official Regional Bureau publication. MedOpen groups them into categories based on Japan’s medical fee schedule.

We couldn’t confirm a notification for this hospital in the latest covered publication. This does not prove that no notification exists.

We use sections of Japan’s medical fee schedule as categories. These MedOpen analytical groups are not official ministry categories and do not show which services a hospital provides.

Changes across published snapshots

This compares published snapshots. First observed means first found in the MedOpen archive, not a filing date. A prior item missing from the latest snapshot does not prove withdrawal or cancellation.

No facility-level change counts are shown because no notification was observed for this hospital in the latest published snapshot. This does not establish filing status or a change.

Comparison group and published-record context

Source and reference

Release: facility-standards-notification-20261006-3ccdf50e017e1dfe

Kinki Regional Bureau of Health and Welfare · snapshot: 2026-10-01 · published: 2026-10-05 · Official source page (Japanese)

These records show notifications listed in an official Regional Bureau publication. They do not establish care quality, actual billing or care provided, or whether a service is currently available.

Professional hospital intelligence

Clinical activity in published DPC data

This section summarizes categories and counts appearing in the Ministry of Health, Labour and Welfare’s published DPC data. It does not represent all hospital activity or assess quality.

No case counts or composition are shown because this hospital could not be linked deterministically to the covered DPC publication.

Source records

Data periods can differ by source. Specialty and facility-standard lists are shown only where a verified source-to-facility match is available.

Sources and reference periods

Source titles and official records may be in Japanese. Dates and geographic units are shown separately for each source.