Jhnrd

io.github.ogasurfproject-jpg由 GitHub 帳號 ogasurfproject-jpg 發布v0.24.0更新於 Oct 27, 2026

Japan home-visit nursing reimbursement rules, each with its source and that source's standing.

已驗證Streamable HTTP可網頁執行位置與生活金融知識與記憶

概覽

AI 產生的概覽

唯讀 MCP 端點,提供日本居家訪視護理給付規則的附出處資料庫,每項要求都標明所依據的文件及其效力層級。

可以做什麼
  • 檢視資料庫目前狀態:版本、項目數、出處層級組成、未確認要求數與未解決歧異數
  • 依保險類型與類別篩選並讀取項目,含要求、效果、期限及已解析的出處
  • 在項目名稱、要求本文與效果敘述中搜尋,找不到時明確回報未找到而不作推測
  • 檢視出處:列出全部出處及其層級與現行/已廢止計數,或讀取單一出處的效力
  • 檢視資料庫的弱點:未確認要求及原因、已記錄的歧異、已知缺口與擷取失敗紀錄
  • 閱讀利益衝突揭露與引用方式,包括應標註的版本號
適用情境
適合需要查詢日本居家訪視護理的加算、減算、單位數或醫囑期限,並希望看到每條規則出處的情境。適用於重視出處層級與未確認事項的研究與草擬工作,不適用於做出給付申報判斷。
執行需求
需要可連線的遠端 Streamable HTTP 端點;不需 API 金鑰、帳號或環境變數。README 說明此服務為唯讀且不保存任何儲存。
安裝前請注意
維護方銷售以本資料庫為基礎的居家訪視護理付費服務,存在利益衝突,伺服器對此有所揭露。資料庫明確不完整:59 個項目、147 項未確認要求、11 項未解決歧異、14 處已知缺口,且不判斷某項費用能否申報。引用時須註明版本號,因為不同版本內容不同。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Jhnrd,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.ogasurfproject-jpg%2Fjhnrd/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "jhnrd": {
      "type": "http",
      "url": "https://jhnrd-mcp.oga-surf-project.workers.dev/mcp"
    }
  }
}

README

JHNRD

Part of Awesome HORIZON SHIELD — the checkable index of every dataset, MCP server and ledger we run.

Japan Home-visit Nursing Reimbursement Database

[validate] [live] [version] [items] [current statute sources] [unconfirmed requirements] [open conflicts] [License: CC BY 4.0] [DOI]

A record of Japanese home-visit nursing reimbursement rules — additions, reductions, and the expiry of physician instructions — in which every requirement carries the document it rests on.

The numbers themselves are public. What this dataset holds is where each number came from.

日本語版はこちら → README.ja.md

間違いを見つけた方へ。 この資料の誤りに気づけるのは、現場で算定している方です。 直し方は CONTRIBUTING.md に日本語で書いてあります。 出典を1つ添えて Issue を立ててください。 「この加算の要件が違う」の一行でも構いません。訂正は不具合として扱います。


Do not make a billing decision on this alone

23 sources currently rest on the statute text itself (statute — the ministerial notice, ordinance or circular). statute is 28 in total; 8 of those are superseded revisions and cannot be used as current authority. They are kept only so that the revision history is legible.

The rest are ministry material that is not the statute text (agency, 26) and private commentary (secondary, 16).

147 requirements are unconfirmed. Anything we could not check against the statute text says so. It is not left blank.

What this dataset can say is: "this reduction has requirements A, B and C, and C has not yet been confirmed against the statute text." It never says "you may bill this" or "this applies to you."

The reason for that line is simple: when a claim is returned, someone has to be accountable, and a dataset cannot be.


Where it stands

Version2024-kaitei.seed.24
Items59
Sources — statute (the notice/ordinance/circular itself)28
of which current23
Sources — agency (MHLW material, not the statute text)26
Sources — secondary (private commentary)16
Sources, total70 (8 not current)
Unconfirmed requirements147
Conflicts15 total / 11 unresolved
Field reports0 (never a source of rules)
Last validated2026-09-26

59 items. This is not a complete map of the rules. The name runs ahead of the contents, and the item count is put first so that this is not hidden.


Japanese statutory terms are never translated away

Names that come from a statute — 看護体制強化加算 (Ⅰ), 特別管理加算, 告示第95号 — are kept verbatim in this repository, in the data and in this README, with an English gloss beside them where one helps.

They are not replaced by an English name. No English name for them exists in any Japanese statute, so inventing one would create a precision the source does not have. That is the same reason an unconfirmed requirement is published as unconfirmed rather than tidied away.

The disciplines

  1. No number without a source. Every unit value and every requirement carries a source.
  2. Every source declares its own standing, in three tiers. statute / agency / secondary. Material published by the ministry is not treated as equal to the statute text.
  3. An unconfirmed item is never left blank. It carries confirmed: false and an unconfirmed_reason. Blank and unconfirmed are different things.
  4. When sources disagree, we do not pick one and go quiet. Both readings go into conflicts, and the conflict stays marked unresolved. The moment one is chosen, the reason for choosing it disappears.
  5. Nothing that reads as "you may bill this" is allowed into the data. The validator rejects it.
  6. Revisions cut a new version; the old one is not deleted. Otherwise past decisions cannot be audited afterwards.
  7. Every requirement is bound one-to-one to an interview question. A requirement with no question attached is a requirement nobody has actually asked about.

These are not aspirations. tools/validate.py checks them mechanically, and CI fails on any breach.


Public MCP endpoint (no key, read-only)

https://jhnrd-mcp.oga-surf-project.workers.dev

The dataset is served over MCP (JSON-RPC 2.0 / Streamable HTTP at POST /mcp) and over plain HTTP (/status.json, /items, /items/<id>, /sources, /search?q=, /unconfirmed, /conflicts, /gaps, /disclosure, /cite). No key. No write path.

The content is CC BY 4.0 already — but a JSON file on its own means every consumer writes a parser, and every parser mixes in its author's reading. Serving it means that happens in one place.

The same line is drawn on the serving side:

  • It does not decide whether a claim may be billed. That it never returns such a statement is checked mechanically by the test suite.
  • Every response carries the version, the "this does not decide billing" notice, and the conflict-of-interest disclosure. All eleven tools are tested for it.
  • It holds no key and is wired to no storage. The moment it is, it starts holding something of someone's.
  • The tools that expose the weaknesses come first: jhnrd_unconfirmed, jhnrd_gaps (including searches that came back empty), jhnrd_conflicts (both readings kept).

The copy it serves is generated from the dataset and never fetched at runtime — a CDN edge once kept a stale revision alive and an internal server handed out old numbers. CI fails if the copy drifts from the source.

Once a day, both the version the live endpoint is actually serving and the manifest listed in the official MCP registry are compared against the repository (the live badge above) — because pushing and forgetting to deploy, and publishing a manifest whose metadata the registry silently dropped, have both already happened here.

That check does not fail when the connection cannot be made — being unreachable is not evidence of being stale — but it does fail when an HTTP status comes back and is not 200, because a status is an answer. The first version of this gate conflated the two and spent its life reporting green while receiving 403s. Its logic is exercised against seventeen mocked endpoints on every push, since a gate that runs once a day can stay broken for a day without anyone knowing.

json
{ "mcpServers": { "jhnrd": { "type": "http", "url": "https://jhnrd-mcp.oga-surf-project.workers.dev/mcp" } } }

See mcp/README.md; the registry manifest is server.json.


Conflict of interest

The HORIZONs Inc., which maintains this dataset, sells a paid service to home-visit nursing providers that is backed by it. Payment is taken as an initial build fee and a monthly fee.

So: the people building this dataset are paid when it is believed to be useful. That has to be stated first, or the numbers above cannot be used. A dataset whose central discipline is that every source declares its own standing cannot exempt itself from declaring its own.

Four things could bend, and each is bound in advance:

TemptationWhat is bound against it
Make it look completeThe item count is the headline, with "not a complete map" next to it
Make the risk look largerThe validator rejects any wording that reads as a billing decision
Delete an inconvenient conflictConflicts keep both readings; total and unresolved counts are published separately
Hide a correctionCorrections stack on top of the original wording, which is never deleted

Every number in this README is generated from status.json, and CI fails if it is edited by hand. Inflating a figure is not something that can be done quietly.

  • Revenue comes only from those customers. No government, trade-association or vendor funding. No listing fees. No advertising.
  • There is no separate or extended dataset for paying customers. What is here is all of it.
  • Practice notes gathered from providers are never added without their consent (currently 0), and are never a source of rules even when present.

Full text, and what the maintainer can and cannot decide: GOVERNANCE.md (Japanese).


Citing

Always cite the version (the seed number). Different versions hold different content. Because corrections are stacked rather than overwritten, a citation without a version cannot be reconciled afterwards.

The HORIZONs Inc. (2026). JHNRD — Japan Home-visit Nursing Reimbursement Database,version 2024-kaitei.seed.19. Zenodo. https://doi.org/10.5281/zenodo.22083722 (CC BY 4.0)

DOI: 10.5281/zenodo.22083722 — this is the concept DOI covering all versions; it always resolves to the newest. To cite a specific release, use the per-version DOI on its Zenodo record. Different versions hold different content.

Machine-readable descriptions — all generated from status.json, none written by hand: CITATION.cff ・ datapackage.json ・ .zenodo.json ・ CHANGELOG.md

Each version carries an annotated tag: git tag -l 'seed.*', then git show seed.19.


Corrections are treated as defects

If a statement here is wrong, or disagrees with the statute text, please open an issue. You do not need to run a provider to do so.

  • A correction never deletes the original wording. Deleting it would make it impossible to check afterwards whether the correction itself was right.
  • A correction grounded in statute outranks agency, which outranks secondary.
  • Where we say "not confirmed" rather than staying silent, that is exactly the place to push back.

How to file: CONTRIBUTING.md. Contact: [email protected]


What is still missing

Unfilled gaps are recorded in known_gaps inside data/rules_2024.json — currently 14 (resolved ones are kept, marked as resolved).


Maintainer

The HORIZONs Inc. (Japan corporate number 7021001075279) Toshikatsu Oga (ORCID 0009-0000-9180-903X)

Maintained by a single company. Not a peer-review body, not a public authority, not a trade association. No relationship with the Ministry of Health, Labour and Welfare or any other government body, and nothing here has been confirmed by any of them.

A construction-cost database built to the same disciplines exists at JCCDB. JHNRD aims to stand in the same place for home-visit nursing. It is 59 items so far.

來源:README.md,提交 597dfa5

工具

11

jhnrd_status

このデータベースのいまの状態。版・項目数・出典の素性の内訳・未確認の要件の数・未解決の食い違いの数。項目数は訪問看護の算定要件を網羅した数ではない。まずここを見ること。

無需輸入參數。

jhnrd_list_items

収録している項目の一覧(要約)。insurance(介護/医療/介護・医療)と kind(加算/減算/単位数/療養費/期限・交付ルール/振り分けルール)で絞れる。詳細は jhnrd_get_item。

輸入參數kindinsuranceonly_unconfirmed

jhnrd_get_item

項目1件の全部。要件・効果・期限に加えて、参照している出典を素性(tier)と現行かどうかつきで解決して返す。

輸入參數id必填

jhnrd_unconfirmed

原文で確認できていない要件の一覧と、なぜ確認できていないかの理由。空欄にせず残してあるもの。このデータベースの弱いところを、先に見るための口。

無需輸入參數。

jhnrd_conflicts

出典どうし、あるいは同じ出典の読み取りどうしが食い違った記録。解決済みも残す。どちらかを選んで黙る、ということをしていない証拠でもある。

無需輸入參數。

jhnrd_gaps

埋まっていないもの(known_gaps)、取りに行って取れなかった記録(attempts)、途中まで分かったこと(findings)。何が無いかを、無いと言えるようにするための口。

輸入參數include_resolved

jhnrd_get_source

出典1件の素性。tier(statute/agency/secondary)と、現行版かどうか(current)を必ず返す。

輸入參數id必填

jhnrd_list_sources

出典の一覧。素性ごと、現行かどうかごとに数えたものも返す。statute が何件あるかだけを言うと実態より良く見えるので、現行版の数を分けて出す。

輸入參數tieronly_current

jhnrd_disclosure

誰がこれを作り、誰に養われているか。利益相反の開示。出典の素性を名乗ることを規律にしている以上、この口自身の素性も名乗る。

無需輸入參數。

jhnrd_how_to_cite

引用の仕方。版(seed 番号)を添えること。訂正しても元の記述を消さない方針のため、版が分からないと後から突き合わせられない。

無需輸入參數。

版本歷史

2
  1. v0.24.0最新Sep 26, 2026
  2. v0.22.0Sep 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。