MCP catalogue

Every tool on the production MCP gateway, by hospital system. Descriptions come from the service code, read live: nothing here is written by hand.

Read live 2026-10-12 04:10 (Taipei)

Gateway: https://orbit-medical-systems.orbit-poc.com (production), read live.

Code: development db5614ac, 2026-10-12 03:34 GMT+8 · production db5614ac, 2026-10-12 03:34 GMT+8 (same commit)

How to connect如何連線

Step by step, from no key to the first answer. Use an MCP client (Claude, Hermes or any other) and call the tools directly.

五個步驟：取得金鑰、確認連線、選擇位址、連接工具、第一次呼叫 · Five steps: key, reach, address, client, first call

1
取得金鑰 Get a key
Ask the MCP admin for a key. The admin opens https://orbit-medical-systems.orbit-poc.com/mcp/admin and:
1. opens the tab 權杖 (Tokens);
2. in the card 內部閘道器權杖 (internal gateway key), types who it is for in 簽給誰;
3. picks the end date (到期日), or 無到期 for no end;
4. presses 產生權杖 (Generate). The key is shown once: copy it and hand it over privately. Keep it like a password: never in a group chat, an e-mail or a screenshot.
1 · MCP 控制, tab 權杖 Tokens
2 簽給誰 recipient · 3 到期 end date · 4 產生權杖 Generate
You should see 應該看到： a long code that starts with hismcp_gk_, and the date it ends.
確認連線 Check you can reach the gateway
Open https://orbit-medical-systems.orbit-poc.com/api/mcp/v1/systems in a browser. It needs no key.
You should see 應該看到： text that starts with [{"scheme":: the list of addresses.
If not 如果沒有： your network blocks the gateway. Ask for the VPN, or ask the MCP admin to allow your address.

選擇位址 Pick an address

Each address is one group of tools. Pick the one you need; one client entry per address. staff-schedule, nhi-ops and comms are chat flows: they take a chat identity instead of a key (see the usage guide, section 3).

MCP addresses
Name	Purpose	Tools	Services	MCP address
analytics 數據分析與 AI	Governed analytics and AI: FHIR exchange, data platform, BI reports, AI models.	44	ai-inference, bi-reporting, data-platform, fhir-exchange	https://orbit-medical-systems.orbit-poc.com/mcp/analytics/
ancillary 醫療輔助（檢驗、影像、檢查）	Order fulfilment: laboratory, radiology and exam scheduling; microbiology and pathology reports and MDRO flags; sterile supply (CSSD) status (read only).	490	cssd, diagnostics, exam-scheduling, laboratory, micropath, radiology	https://orbit-medical-systems.orbit-poc.com/mcp/ancillary/
audit	Read the audit trail: events, verification runs, a patient's access report, review-queue items and archive query results; start a chain verification; assign a review item to a reviewer.	10	audit	https://orbit-medical-systems.orbit-poc.com/mcp/audit/
clinical 臨床診療	Run a visit and inpatient stay: workspace, orders, notes, CDSS, queue, nursing, ER, admissions, surgery, closed-loop safety.	389	adt, bff, cdss, closed-loop-safety, emergency, emr, nursing, orders, queue, surgery	https://orbit-medical-systems.orbit-poc.com/mcp/clinical/
comms 客服通話	Call-centre staff: work the outbound call list, call patients, book callbacks, read call logs and contact records, search call transcripts, and keep meeting minutes and decisions.	35	comms, notification	https://orbit-medical-systems.orbit-poc.com/mcp/comms/
finance 批價與健保申報	Price a visit, take payment and submit NHI claims.	134	billing, erpbridge, nhi-claims, payment	https://orbit-medical-systems.orbit-poc.com/mcp/finance/
knowledge 規範與知識文件	Search and read controlled policy documents (SOP, NHI review notes, accreditation standards, regulations), cite them, add notes, and draft and submit new versions.	35	knowledge	https://orbit-medical-systems.orbit-poc.com/mcp/knowledge/
laboratory 檢驗	Laboratory orders, tracking, results, microbiology, pathology, send-out and QC.	79	laboratory	https://orbit-medical-systems.orbit-poc.com/mcp/laboratory/
leave-rulings 醫師請假與代診	Read doctor leave requests and the cover ruling of each affected clinic session.	3	org-config	https://orbit-medical-systems.orbit-poc.com/mcp/leave-rulings/
microbiology 微生物檢驗	Read microbiology: the culture worklist, one case worksheet, and a patient's culture reports.	3	micropath	https://orbit-medical-systems.orbit-poc.com/mcp/microbiology/
nhi-ops 健保卡作業	NHI card operations (read-only): card transactions, uploads, workstation health and active alerts; MediCloud lookups remain unavailable until a stronger identity check is decided.	6	nhi-card, org-config	https://orbit-medical-systems.orbit-poc.com/mcp/nhi-ops/
notification 通知	Send notices to patients and staff (one or many recipients) and check delivery.	27	notification	https://orbit-medical-systems.orbit-poc.com/mcp/notification/
office	Office email and official documents (公文): send email, dispatch a 公文, register, assign and close received documents, follow deadlines and receipts.	11	erpbridge	https://orbit-medical-systems.orbit-poc.com/mcp/office/
pharmacy 藥局	Dispense and administer medications; manage stock.	172	inventory, pharmacy	https://orbit-medical-systems.orbit-poc.com/mcp/pharmacy/
reference 共用主檔	Master data for staff: codes and dictionaries, orderables, fees and prices, the organization, beds, clinic sessions, parameters, staff, licences and privileges.	208	org-config, terminology	https://orbit-medical-systems.orbit-poc.com/mcp/reference/
registry 病人與掛號	Find patients and manage encounters, registration, NHI-card visits and healthcare-certificate (HCA) signatures.	210	hca, nhi-card, patient-registry, registration	https://orbit-medical-systems.orbit-poc.com/mcp/registry/
staff-schedule 醫師門診班表	Doctors: check your clinic sessions and file or withdraw leave by chat.	6	org-config	https://orbit-medical-systems.orbit-poc.com/mcp/staff-schedule/
workforce 人力排班	Build and publish nursing/medical staff rosters, leave, overtime, nurse-to-patient ratios and the float pool.	116	workforce	https://orbit-medical-systems.orbit-poc.com/mcp/workforce/

4
連接你的工具 Connect your client
Address for the commands below
Replace hismcp_gk_YOUR-KEY with your key. The address must end with /.
Claude Code
terminal
```
claude mcp add --scope user --transport http his-clinical https://orbit-medical-systems.orbit-poc.com/mcp/clinical/ --header "Authorization: Bearer hismcp_gk_YOUR-KEY"
claude mcp list
```
Claude Desktop
Needs Node.js 18 or newer (node -v). Settings, Developer, Edit Config, then paste into claude_desktop_config.json (merge with any existing mcpServers), save, and quit Claude Desktop completely before opening it again.
claude_desktop_config.json
```
{
  "mcpServers": {
    "his-clinical": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://orbit-medical-systems.orbit-poc.com/mcp/clinical/",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer hismcp_gk_YOUR-KEY"
      }
    }
  }
}
```
MCP Inspector (no AI, for testing)
Start it, then on the left: Transport Type Streamable HTTP, URL below, Authentication, header Authorization with the value below, Connect.
terminal
```
npx @modelcontextprotocol/inspector
```
URL
```
https://orbit-medical-systems.orbit-poc.com/mcp/clinical/
```
Authorization header value
```
Bearer hismcp_gk_YOUR-KEY
```
You should see 應該看到： Claude Code: his-clinical with ✓ Connected. Claude Desktop: the entry running under Settings, Developer. Inspector: a green dot and Connected.
5
第一次呼叫 First call
Ask your assistant: “Use his-clinical. Read its system card and tell me in five short points what you can do.” In Inspector: Tools, List Tools, pick a read tool, Run Tool. An empty list [] is a success: there is no data yet.
- 401: the key is missing, mistyped, ended or revoked. The answer's hint names the header it expects.
- 403: the shared service account may not use that tool. Tell the MCP admin the tool name.
- Server disconnected (Claude Desktop): Node.js missing, the file saved as .txt, or Claude not fully quit.
You should see 應該看到： a short list of what the system can do, or the tool's answer marked success.

Full reference (endpoints, chat identity, tokens, security): docs/mcp-usage-guide.md in the medical repo.

MCP catalogueMCP 工具目錄

Every tool on the gateway, by hospital system, read live from the service code.

MCP toolsMCP 工具

1,851

All tools in the hospital systems; the list below adds up to this

Hospital systems醫院系統

37 have MCP tools, 21 not yet

APIsAPI

1,971

1,705 have an MCP tool, 266 not yet

MCP addressesMCP 連線位址

Where an agent connects: see How to connect

Tools by system各系統 MCP 工具

Every system and its MCP tools, numbered 1 to the system total, with what each tool does and the API it calls. Descriptions come from the code.

Route map: production code 466c58ff0 (committed 2026-10-11 05:12 GMT+8), built 2026-10-11 06:03 GMT+8.

Showing 1,949 of 1,949 tools in 37 systems

adt · 65 tools

MCP tools of adt
#	Tool	API it calls	Access
1	`adt.get_admission_holds` Admission holds, the active ones by default	`GET /api/adt/v1/admission-holds`	read
2	`adt.post_admission_holds_hold_id_release` Release Hold	`POST /api/adt/v1/admission-holds/{hold_id}:release`	write
3	`adt.get_admission_requests` List admission requests	`GET /api/adt/v1/admission-requests`	read
4	`adt.post_admission_requests` Enter an admission request (admission centre); Idempotency-Key required	`POST /api/adt/v1/admission-requests`	write
5	`adt.get_admission_requests_request_id` Get an admission request	`GET /api/adt/v1/admission-requests/{request_id}`	read
6	`adt.patch_admission_requests_request_id` Change a request that has no bed yet	`PATCH /api/adt/v1/admission-requests/{request_id}`	write
7	`adt.post_admission_requests_request_id_cancel` Withdraw a request; a bed it holds is released	`POST /api/adt/v1/admission-requests/{request_id}:cancel`	write
8	`adt.post_admission_requests_request_id_no_show` The patient did not come: release the bed and return the request or cancel it	`POST /api/adt/v1/admission-requests/{request_id}:no-show`	write
9	`adt.get_admission_requests_request_id_bed_candidates` Ranked beds for a request, with flags	`GET /api/adt/v1/admission-requests/{request_id}/bed-candidates`	read
10	`adt.get_admission_requests_request_id_calls` The calls made for a request	`GET /api/adt/v1/admission-requests/{request_id}/calls`	read
11	`adt.post_admission_requests_request_id_calls` Record a call to the patient or family to come in	`POST /api/adt/v1/admission-requests/{request_id}/calls`	write
12	`adt.post_admissions` Complete an admission into the reserved bed; Idempotency-Key required	`POST /api/adt/v1/admissions`	write
13	`adt.get_bed_board` Beds of a ward or campus with status, occupant and block state	`GET /api/adt/v1/bed-board`	read
14	`adt.get_bed_board_stream` Follow bed changes (server-sent events)	`GET /api/adt/v1/bed-board/stream`	read
15	`adt.get_bed_forecast` Empty beds for each of the next days	`GET /api/adt/v1/bed-forecast`	read
16	`adt.get_beds_bed_id` One bed: master attributes, occupancy, occupant summary, open cleaning request	`GET /api/adt/v1/beds/{bed_id}`	read
17	`adt.post_beds_bed_id_mark_clean` Housekeeping: the bed is clean and available again	`POST /api/adt/v1/beds/{bed_id}:mark-clean`	write
18	`adt.post_beds_bed_id_reserve` Hold a bed for a request or for a patient; Idempotency-Key required	`POST /api/adt/v1/beds/{bed_id}:reserve`	write
19	`adt.post_beds_bed_id_cleaning_requests` Ask for a bed to be cleaned, routine or urgent	`POST /api/adt/v1/beds/{bed_id}/cleaning-requests`	write
20	`adt.get_beds_bed_id_history` Every status change of one bed, newest first	`GET /api/adt/v1/beds/{bed_id}/history`	read
21	`adt.get_census` The daily census: ward rows, and department rows within them	`GET /api/adt/v1/census`	read
22	`adt.post_census_recompute` Recompute the census of a past day (replaces its rows; audited)	`POST /api/adt/v1/census:recompute`	write
23	`adt.get_census_summary` Beds by ward level: NHI and differential beds, occupied, empty, with the time counted	`GET /api/adt/v1/census/summary`	read
24	`adt.get_cleaning_requests` Cleaning requests, urgent first and then the longest waiting	`GET /api/adt/v1/cleaning-requests`	read
25	`adt.get_department_quotas` Bed quota and use per department	`GET /api/adt/v1/department-quotas`	read
26	`adt.get_discharge_summaries_overdue` Discharged patients whose discharge summary is not signed in time (chart completion)	`GET /api/adt/v1/discharge-summaries/overdue`	read
27	`adt.get_expected_discharges` Who is expected to leave, by date	`GET /api/adt/v1/expected-discharges`	read
28	`adt.post_jobs_reservation_expiry_run` Return every bed whose hold has run out, now	`POST /api/adt/v1/jobs/reservation-expiry:run`	write
29	`adt.get_length_of_stay` Average length of stay by department and campus, with the period's occupancy	`GET /api/adt/v1/length-of-stay`	read
30	`adt.get_movements` Every move of every stay in the order it happened, a page at a time	`GET /api/adt/v1/movements`	read
31	`adt.get_overrides` Placement rules people went past, with their reasons	`GET /api/adt/v1/overrides`	read
32	`adt.post_placement_checks` Check a named bed for a patient before placing them	`POST /api/adt/v1/placement-checks`	write
33	`adt.get_planned_transfers` Planned transfers, by day, bed level or stay	`GET /api/adt/v1/planned-transfers`	read
34	`adt.post_planned_transfers_plan_id_cancel` Cancel a planned transfer and release its bed for that day	`POST /api/adt/v1/planned-transfers/{plan_id}:cancel`	write
35	`adt.post_planned_transfers_plan_id_execute` Make the planned transfer, on its day, into the held bed	`POST /api/adt/v1/planned-transfers/{plan_id}:execute`	write
36	`adt.get_reservations` Beds being held, to find the hold of a request (default: active ones)	`GET /api/adt/v1/reservations`	read
37	`adt.patch_reservations_reservation_id` Extend a hold, once, with a reason	`PATCH /api/adt/v1/reservations/{reservation_id}`	write
38	`adt.post_reservations_reservation_id_release` Let a held bed go; the request returns to the waiting list	`POST /api/adt/v1/reservations/{reservation_id}:release`	write
39	`adt.get_stays` List stays	`GET /api/adt/v1/stays`	read
40	`adt.post_stays_backfill_encounters` Open the IPD encounter of open stays that were admitted without one	`POST /api/adt/v1/stays:backfill-encounters`	write
41	`adt.get_stays_stay_id` Get a stay	`GET /api/adt/v1/stays/{stay_id}`	read
42	`adt.post_stays_stay_id_cancel_admission` Undo an admission that was entered in error	`POST /api/adt/v1/stays/{stay_id}:cancel-admission`	write
43	`adt.post_stays_stay_id_relocate` Move a patient to a chosen suitable bed (condition change or overflow)	`POST /api/adt/v1/stays/{stay_id}:relocate`	write
44	`adt.get_stays_stay_id_bed_candidates` Beds a patient could move to, ranked like admission candidates	`GET /api/adt/v1/stays/{stay_id}/bed-candidates`	read
45	`adt.post_stays_stay_id_card_not_presented` No NHI card at admission: the card is still to be read before discharge	`POST /api/adt/v1/stays/{stay_id}/card:not-presented`	write
46	`adt.get_stays_stay_id_discharge_checklist` What is still open before this patient can leave	`GET /api/adt/v1/stays/{stay_id}/discharge-checklist`	read
47	`adt.post_stays_stay_id_discharge_ready` Mark the patient ready for discharge (出院準備完成), or not	`POST /api/adt/v1/stays/{stay_id}/discharge-ready`	write
48	`adt.post_stays_stay_id_discharge_depart` Record the departure: the stay closes and the bed goes to cleaning	`POST /api/adt/v1/stays/{stay_id}/discharge:depart`	write
49	`adt.put_stays_stay_id_expected_discharge` Record or change the expected discharge: date or time, confidence, note	`PUT /api/adt/v1/stays/{stay_id}/expected-discharge`	write
50	`adt.get_stays_stay_id_expected_discharge_history` The expected discharges this stay used to have, newest first	`GET /api/adt/v1/stays/{stay_id}/expected-discharge/history`	read
51	`adt.get_stays_stay_id_leaves` The leaves a stay has had, oldest first	`GET /api/adt/v1/stays/{stay_id}/leaves`	read
52	`adt.post_stays_stay_id_leaves` Record a leave of absence: the bed is kept `on-leave` for the patient	`POST /api/adt/v1/stays/{stay_id}/leaves`	write
53	`adt.post_stays_stay_id_leaves_return` The patient is back: the bed is `occupied` again	`POST /api/adt/v1/stays/{stay_id}/leaves:return`	write
54	`adt.get_stays_stay_id_movements` Every move of a stay: admission, transfers, discharge	`GET /api/adt/v1/stays/{stay_id}/movements`	read
55	`adt.post_stays_stay_id_planned_transfers` Plan a transfer for a future day and hold a bed for it	`POST /api/adt/v1/stays/{stay_id}/planned-transfers`	write
56	`adt.get_stays_stay_id_suitable_beds` Beds that fit this patient's current need, home ward first, overflow after	`GET /api/adt/v1/stays/{stay_id}/suitable-beds`	read
57	`adt.post_stays_stay_id_transfers` Move a patient to another bed or ward, or change department or attending	`POST /api/adt/v1/stays/{stay_id}/transfers`	write
58	`adt.post_stays_stay_id_wristband` Produce the identification wristband (ZPL); a reprint needs a reason	`POST /api/adt/v1/stays/{stay_id}/wristband`	write
59	`adt.get_stays_stay_id_wristband_preview` What the wristband will show, before printing; nothing is printed or recorded	`GET /api/adt/v1/stays/{stay_id}/wristband:preview`	read
60	`adt.post_transfers_movement_id_accept` The receiving unit accepts the transfer	`POST /api/adt/v1/transfers/{movement_id}:accept`	write
61	`adt.post_transfers_movement_id_arrive` The patient arrived: hand-off recorded, target bed occupied, source bed cleaning	`POST /api/adt/v1/transfers/{movement_id}:arrive`	write
62	`adt.post_transfers_movement_id_cancel` Cancel a transfer that has not happened; the held bed is released	`POST /api/adt/v1/transfers/{movement_id}:cancel`	write
63	`adt.get_waiting_list` Requests without a bed: urgent first, then longest waiting	`GET /api/adt/v1/waiting-list`	read
64	`adt.post_wards_ward_id_admission_holds` Stop new admissions to a ward for a time (e.g. an infection-control hold)	`POST /api/adt/v1/wards/{ward_id}/admission-holds`	write
65	`adt.get_wards_ward_id_rules` Room rules of a ward: sex policy against who is in it, class, surcharge, quota	`GET /api/adt/v1/wards/{ward_id}/rules`	read

No MCP tools yet 尚無 MCP 工具 (21): 27 感染管制監測系統 · 34 重症加護系統 · 40 化學治療系統 · 41 放射腫瘤系統 · 42 核子醫學系統 · 43 血液透析系統 · 44 產房與嬰兒室系統 · 45 復健系統 · 46 呼吸治療系統 · 47 牙科系統 · 48 預防保健與癌症篩檢系統 · 49 疫苗注射系統 · 53 抗生素管制系統 · 61 介面整合引擎 · 67 全國預防接種資訊系統（NIIS） · 74 健康檢查系統 · 77 陪病與訪客管理系統 · 79 病人傳送系統 · 84 數位看板系統 · 89 太平間管理系統 · 91 醫療物流機器人系統

Not mapped to a system尚未歸屬系統

To do: tools on the gateway that are not placed under a hospital system yet, so they are not counted above. Each one waits for a ruling on its system; once placed, it moves into Tools by system.

closed-loop-safety (8)

Not mapped: closed-loop-safety

GET	/api/safety/v1/dashboard	Dashboard	read	closed-loop-safety.get_dashboard	clinical
POST	/api/safety/v1/feedings:check	Feeding Check	write	closed-loop-safety.post_feedings_check	clinical
POST	/api/safety/v1/identity-checks	Identity Check	write	closed-loop-safety.post_identity_checks	clinical
POST	/api/safety/v1/loops	Open Loop Route	create	closed-loop-safety.post_loops	clinical
POST	/api/safety/v1/loops/{instance_id}:exception	Loop Exception	write	closed-loop-safety.post_loops_instance_id_exception	clinical
POST	/api/safety/v1/loops/{instance_id}/steps/{step_code}:advance	Advance	write	closed-loop-safety.post_loops_instance_id_steps_step_code_advance	clinical
POST	/api/safety/v1/milk-containers	Create Milk	write	closed-loop-safety.post_milk_containers	clinical
POST	/api/safety/v1/overdue:sweep	Overdue Sweep	write	closed-loop-safety.post_overdue_sweep	clinical

Shared services共用服務

Tools every hospital system uses, so they belong to no single system and are not counted above: AI models (risk scores, model deploy) and notification and staff chat (SMS, inbox, group chat).

Shared service tools

GET	/api/ai/v1/inferences/{inference_id}	Trace Inference	read	ai-inference.get_inferences_inference_id	analytics
POST	/api/ai/v1/inferences/{inference_id}/actions	Record Action	write	ai-inference.post_inferences_inference_id_actions	analytics
POST	/api/ai/v1/llm/complete	Llm Complete	write	ai-inference.post_llm_complete	analytics
POST	/api/ai/v1/models	Create Model	write	ai-inference.post_models	analytics
POST	/api/ai/v1/models/{model_id}/versions	Create Version	write	ai-inference.post_models_model_id_versions	analytics
POST	/api/ai/v1/models/{model_name}/predict	Model Predict	create	ai-inference.post_models_model_name_predict	analytics
POST	/api/ai/v1/monitor/metrics	Add Metric	write	ai-inference.post_monitor_metrics	analytics
GET	/api/ai/v1/patients/{patient_id}/risk	Patient Risk	read	ai-inference.get_patients_patient_id_risk	analytics
POST	/api/ai/v1/versions/{version_id}:approve	Approve Version	write	ai-inference.post_versions_version_id_approve	analytics
POST	/api/ai/v1/versions/{version_id}:deploy	Deploy Version	write	ai-inference.post_versions_version_id_deploy	analytics
GET	/api/notification/v1/admission-calls/{request_id}	What was sent to the patient for each call-down of an admission request: sent on which channels, or suppressed and why. The message text is not returned.	read	get_admission_call_messages	notification
GET	/api/notification/v1/deliveries	Delivery attempts, filtered by status (for example failed) or channel.	query	list_deliveries	notification
POST	/api/notification/v1/deliveries/{delivery_id}:retry	Retry one failed delivery. Needs the delivery-review permission.	write	retry_delivery	notification
GET	/api/notification/v1/inbox	The caller's own in-app inbox: unread first, with priority and whether an acknowledgement is required.	read	list_inbox	notification
POST	/api/notification/v1/inbox/{notification_id}:acknowledge	Acknowledge an inbox item that requires it, with an optional note.	write	acknowledge_inbox_item	notification
POST	/api/notification/v1/inbox/{notification_id}:read	Mark one of the caller's inbox items as read.	write	mark_inbox_read	notification
POST	/api/notification/v1/notification-batches	Send one template to a named batch of recipients and get a per-recipient result (sent, suppressed, unresolved).	create	send_notification_batch	notification
POST	/api/notification/v1/notifications	Send a notice from a template to one or more recipients (patients or staff); several recipients is a batch send. Returns the notification id, one delivery per recipient and the recipients that are unr	create	send_notification	notification
POST	/api/notification/v1/notifications:cancel-by-dedupe-key	Cancel every pending notification that carries one dedupe key.	write	cancel_notifications_by_dedupe_key	notification
GET	/api/notification/v1/notifications/{notification_id}	One notification with its timeline: per recipient and channel whether it was queued, sent, delivered, read, acknowledged or failed, and which recipients are unresolved (a role and unit nobody holds).	read	get_notification	notification
POST	/api/notification/v1/notifications/{notification_id}:cancel	Cancel a notification that is not yet sent (queued or scheduled).	write	cancel_notification	notification
POST	/api/notification/v1/patients/{patient_id}/channels/{channel}:verify	Verify a patient's contact on one channel (for example the mobile number).	update	verify_patient_channel	notification
PUT	/api/notification/v1/patients/{patient_id}/consents	Record a patient's channel consents (in-app, SMS). Withdrawal is honoured at once; notification checks the caller's permission.	update	set_patient_consents	notification
GET	/api/notification/v1/replies	Patient SMS replies received, filtered by handled or not.	query	list_sms_replies	notification
POST	/api/notification/v1/replies/{reply_id}:handled	Mark a patient SMS reply as handled by staff.	write	mark_sms_reply_handled	notification
POST	/api/notification/v1/sms	Send an SMS to a patient's mobile on record (patient_id required); no clinical detail in the text. 403 number-not-on-record, 409 sms-consent-withdrawn.	create	send_sms	comms
POST	/api/notification/v1/sms:simulate-inbound	Simulate a patient SMS reply (dev and test stacks only; the production adapter refuses it).	write	simulate_inbound_sms	notification
GET	/api/notification/v1/templates	Template catalogue, optionally for one audience (patient or staff).	read	list_templates	notification
GET	/api/notification/v1/templates/{key}/versions	Versions of one template and their status (draft, approved, retired).	read	list_template_versions	notification
POST	/api/notification/v1/templates/{key}/versions	Draft a new version of a template. Approval stays with a person; notification checks the caller's template permission.	write	create_template_version	notification

Sources: all ok

okTracker config
okMCP gateway (production) set listread 2026-10-12 04:10
okMCP set cards (18)
okService registry ai-agentic-platform/research/medical@stagread 2026-10-12 04:10
okOpenAPI documents (44, 20 not exposed on production)
okCatalogue sheetread 2026-10-12 04:10
okUI route manifests ai-agentic-platform/research/medical (29 packages, development and production)
okRoute map (06:00 job)read 2026-10-11 06:03

Reading from GitLab...

How to connect如何連線

Step by step, from no key to the first answer. Use an MCP client (Claude, Hermes or any other) and call the tools directly.

Name

Purpose

Tools

Services

MCP address

analytics

數據分析與 AI

Governed analytics and AI: FHIR exchange, data platform, BI reports, AI models.

ai-inference, bi-reporting, data-platform, fhir-exchange

https://orbit-medical-systems.orbit-poc.com/mcp/analytics/

ancillary

醫療輔助（檢驗、影像、檢查）

Order fulfilment: laboratory, radiology and exam scheduling; microbiology and pathology reports and MDRO flags; sterile supply (CSSD) status (read only).

490

cssd, diagnostics, exam-scheduling, laboratory, micropath, radiology

https://orbit-medical-systems.orbit-poc.com/mcp/ancillary/

audit

Read the audit trail: events, verification runs, a patient's access report, review-queue items and archive query results; start a chain verification; assign a review item to a reviewer.

audit

https://orbit-medical-systems.orbit-poc.com/mcp/audit/

clinical

臨床診療

Run a visit and inpatient stay: workspace, orders, notes, CDSS, queue, nursing, ER, admissions, surgery, closed-loop safety.

389

adt, bff, cdss, closed-loop-safety, emergency, emr, nursing, orders, queue, surgery

https://orbit-medical-systems.orbit-poc.com/mcp/clinical/

comms

客服通話

Call-centre staff: work the outbound call list, call patients, book callbacks, read call logs and contact records, search call transcripts, and keep meeting minutes and decisions.

comms, notification

https://orbit-medical-systems.orbit-poc.com/mcp/comms/

finance

批價與健保申報

Price a visit, take payment and submit NHI claims.

134

billing, erpbridge, nhi-claims, payment

https://orbit-medical-systems.orbit-poc.com/mcp/finance/

knowledge

規範與知識文件

Search and read controlled policy documents (SOP, NHI review notes, accreditation standards, regulations), cite them, add notes, and draft and submit new versions.

knowledge

https://orbit-medical-systems.orbit-poc.com/mcp/knowledge/

laboratory

檢驗

Laboratory orders, tracking, results, microbiology, pathology, send-out and QC.

laboratory

https://orbit-medical-systems.orbit-poc.com/mcp/laboratory/

leave-rulings

醫師請假與代診

Read doctor leave requests and the cover ruling of each affected clinic session.

org-config

https://orbit-medical-systems.orbit-poc.com/mcp/leave-rulings/

microbiology

微生物檢驗

Read microbiology: the culture worklist, one case worksheet, and a patient's culture reports.

micropath

https://orbit-medical-systems.orbit-poc.com/mcp/microbiology/

nhi-ops

健保卡作業

NHI card operations (read-only): card transactions, uploads, workstation health and active alerts; MediCloud lookups remain unavailable until a stronger identity check is decided.

nhi-card, org-config

https://orbit-medical-systems.orbit-poc.com/mcp/nhi-ops/

notification

通知

Send notices to patients and staff (one or many recipients) and check delivery.

notification

https://orbit-medical-systems.orbit-poc.com/mcp/notification/

office

Office email and official documents (公文): send email, dispatch a 公文, register, assign and close received documents, follow deadlines and receipts.

erpbridge

https://orbit-medical-systems.orbit-poc.com/mcp/office/

pharmacy

藥局

Dispense and administer medications; manage stock.

172

inventory, pharmacy

https://orbit-medical-systems.orbit-poc.com/mcp/pharmacy/

reference

共用主檔

Master data for staff: codes and dictionaries, orderables, fees and prices, the organization, beds, clinic sessions, parameters, staff, licences and privileges.

208

org-config, terminology

https://orbit-medical-systems.orbit-poc.com/mcp/reference/

registry

病人與掛號

Find patients and manage encounters, registration, NHI-card visits and healthcare-certificate (HCA) signatures.

210

hca, nhi-card, patient-registry, registration

https://orbit-medical-systems.orbit-poc.com/mcp/registry/

staff-schedule

醫師門診班表

Doctors: check your clinic sessions and file or withdraw leave by chat.

org-config

https://orbit-medical-systems.orbit-poc.com/mcp/staff-schedule/

workforce

人力排班

Build and publish nursing/medical staff rosters, leave, overtime, nurse-to-patient ratios and the float pool.

116

workforce

https://orbit-medical-systems.orbit-poc.com/mcp/workforce/

{ "mcpServers": { "his-clinical": { "command": "npx", "args": [ "-y", "mcp-remote", "https://orbit-medical-systems.orbit-poc.com/mcp/clinical/", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer hismcp_gk_YOUR-KEY" } } } }

Tools by system各系統 MCP 工具

Every system and its MCP tools, numbered 1 to the system total, with what each tool does and the API it calls. Descriptions come from the code.

Route map: production code 466c58ff0 (committed 2026-10-11 05:12 GMT+8), built 2026-10-11 06:03 GMT+8.

Showing 1,949 of 1,949 tools in 37 systems

adt · 65 tools

MCP tools of adt
#	Tool	API it calls	Access
1	`adt.get_admission_holds` Admission holds, the active ones by default	`GET /api/adt/v1/admission-holds`	read
2	`adt.post_admission_holds_hold_id_release` Release Hold	`POST /api/adt/v1/admission-holds/{hold_id}:release`	write
3	`adt.get_admission_requests` List admission requests	`GET /api/adt/v1/admission-requests`	read
4	`adt.post_admission_requests` Enter an admission request (admission centre); Idempotency-Key required	`POST /api/adt/v1/admission-requests`	write
5	`adt.get_admission_requests_request_id` Get an admission request	`GET /api/adt/v1/admission-requests/{request_id}`	read
6	`adt.patch_admission_requests_request_id` Change a request that has no bed yet	`PATCH /api/adt/v1/admission-requests/{request_id}`	write
7	`adt.post_admission_requests_request_id_cancel` Withdraw a request; a bed it holds is released	`POST /api/adt/v1/admission-requests/{request_id}:cancel`	write
8	`adt.post_admission_requests_request_id_no_show` The patient did not come: release the bed and return the request or cancel it	`POST /api/adt/v1/admission-requests/{request_id}:no-show`	write
9	`adt.get_admission_requests_request_id_bed_candidates` Ranked beds for a request, with flags	`GET /api/adt/v1/admission-requests/{request_id}/bed-candidates`	read
10	`adt.get_admission_requests_request_id_calls` The calls made for a request	`GET /api/adt/v1/admission-requests/{request_id}/calls`	read
11	`adt.post_admission_requests_request_id_calls` Record a call to the patient or family to come in	`POST /api/adt/v1/admission-requests/{request_id}/calls`	write
12	`adt.post_admissions` Complete an admission into the reserved bed; Idempotency-Key required	`POST /api/adt/v1/admissions`	write
13	`adt.get_bed_board` Beds of a ward or campus with status, occupant and block state	`GET /api/adt/v1/bed-board`	read
14	`adt.get_bed_board_stream` Follow bed changes (server-sent events)	`GET /api/adt/v1/bed-board/stream`	read
15	`adt.get_bed_forecast` Empty beds for each of the next days	`GET /api/adt/v1/bed-forecast`	read
16	`adt.get_beds_bed_id` One bed: master attributes, occupancy, occupant summary, open cleaning request	`GET /api/adt/v1/beds/{bed_id}`	read
17	`adt.post_beds_bed_id_mark_clean` Housekeeping: the bed is clean and available again	`POST /api/adt/v1/beds/{bed_id}:mark-clean`	write
18	`adt.post_beds_bed_id_reserve` Hold a bed for a request or for a patient; Idempotency-Key required	`POST /api/adt/v1/beds/{bed_id}:reserve`	write
19	`adt.post_beds_bed_id_cleaning_requests` Ask for a bed to be cleaned, routine or urgent	`POST /api/adt/v1/beds/{bed_id}/cleaning-requests`	write
20	`adt.get_beds_bed_id_history` Every status change of one bed, newest first	`GET /api/adt/v1/beds/{bed_id}/history`	read
21	`adt.get_census` The daily census: ward rows, and department rows within them	`GET /api/adt/v1/census`	read
22	`adt.post_census_recompute` Recompute the census of a past day (replaces its rows; audited)	`POST /api/adt/v1/census:recompute`	write
23	`adt.get_census_summary` Beds by ward level: NHI and differential beds, occupied, empty, with the time counted	`GET /api/adt/v1/census/summary`	read
24	`adt.get_cleaning_requests` Cleaning requests, urgent first and then the longest waiting	`GET /api/adt/v1/cleaning-requests`	read
25	`adt.get_department_quotas` Bed quota and use per department	`GET /api/adt/v1/department-quotas`	read
26	`adt.get_discharge_summaries_overdue` Discharged patients whose discharge summary is not signed in time (chart completion)	`GET /api/adt/v1/discharge-summaries/overdue`	read
27	`adt.get_expected_discharges` Who is expected to leave, by date	`GET /api/adt/v1/expected-discharges`	read
28	`adt.post_jobs_reservation_expiry_run` Return every bed whose hold has run out, now	`POST /api/adt/v1/jobs/reservation-expiry:run`	write
29	`adt.get_length_of_stay` Average length of stay by department and campus, with the period's occupancy	`GET /api/adt/v1/length-of-stay`	read
30	`adt.get_movements` Every move of every stay in the order it happened, a page at a time	`GET /api/adt/v1/movements`	read
31	`adt.get_overrides` Placement rules people went past, with their reasons	`GET /api/adt/v1/overrides`	read
32	`adt.post_placement_checks` Check a named bed for a patient before placing them	`POST /api/adt/v1/placement-checks`	write
33	`adt.get_planned_transfers` Planned transfers, by day, bed level or stay	`GET /api/adt/v1/planned-transfers`	read
34	`adt.post_planned_transfers_plan_id_cancel` Cancel a planned transfer and release its bed for that day	`POST /api/adt/v1/planned-transfers/{plan_id}:cancel`	write
35	`adt.post_planned_transfers_plan_id_execute` Make the planned transfer, on its day, into the held bed	`POST /api/adt/v1/planned-transfers/{plan_id}:execute`	write
36	`adt.get_reservations` Beds being held, to find the hold of a request (default: active ones)	`GET /api/adt/v1/reservations`	read
37	`adt.patch_reservations_reservation_id` Extend a hold, once, with a reason	`PATCH /api/adt/v1/reservations/{reservation_id}`	write
38	`adt.post_reservations_reservation_id_release` Let a held bed go; the request returns to the waiting list	`POST /api/adt/v1/reservations/{reservation_id}:release`	write
39	`adt.get_stays` List stays	`GET /api/adt/v1/stays`	read
40	`adt.post_stays_backfill_encounters` Open the IPD encounter of open stays that were admitted without one	`POST /api/adt/v1/stays:backfill-encounters`	write
41	`adt.get_stays_stay_id` Get a stay	`GET /api/adt/v1/stays/{stay_id}`	read
42	`adt.post_stays_stay_id_cancel_admission` Undo an admission that was entered in error	`POST /api/adt/v1/stays/{stay_id}:cancel-admission`	write
43	`adt.post_stays_stay_id_relocate` Move a patient to a chosen suitable bed (condition change or overflow)	`POST /api/adt/v1/stays/{stay_id}:relocate`	write
44	`adt.get_stays_stay_id_bed_candidates` Beds a patient could move to, ranked like admission candidates	`GET /api/adt/v1/stays/{stay_id}/bed-candidates`	read
45	`adt.post_stays_stay_id_card_not_presented` No NHI card at admission: the card is still to be read before discharge	`POST /api/adt/v1/stays/{stay_id}/card:not-presented`	write
46	`adt.get_stays_stay_id_discharge_checklist` What is still open before this patient can leave	`GET /api/adt/v1/stays/{stay_id}/discharge-checklist`	read
47	`adt.post_stays_stay_id_discharge_ready` Mark the patient ready for discharge (出院準備完成), or not	`POST /api/adt/v1/stays/{stay_id}/discharge-ready`	write
48	`adt.post_stays_stay_id_discharge_depart` Record the departure: the stay closes and the bed goes to cleaning	`POST /api/adt/v1/stays/{stay_id}/discharge:depart`	write
49	`adt.put_stays_stay_id_expected_discharge` Record or change the expected discharge: date or time, confidence, note	`PUT /api/adt/v1/stays/{stay_id}/expected-discharge`	write
50	`adt.get_stays_stay_id_expected_discharge_history` The expected discharges this stay used to have, newest first	`GET /api/adt/v1/stays/{stay_id}/expected-discharge/history`	read
51	`adt.get_stays_stay_id_leaves` The leaves a stay has had, oldest first	`GET /api/adt/v1/stays/{stay_id}/leaves`	read
52	`adt.post_stays_stay_id_leaves` Record a leave of absence: the bed is kept `on-leave` for the patient	`POST /api/adt/v1/stays/{stay_id}/leaves`	write
53	`adt.post_stays_stay_id_leaves_return` The patient is back: the bed is `occupied` again	`POST /api/adt/v1/stays/{stay_id}/leaves:return`	write
54	`adt.get_stays_stay_id_movements` Every move of a stay: admission, transfers, discharge	`GET /api/adt/v1/stays/{stay_id}/movements`	read
55	`adt.post_stays_stay_id_planned_transfers` Plan a transfer for a future day and hold a bed for it	`POST /api/adt/v1/stays/{stay_id}/planned-transfers`	write
56	`adt.get_stays_stay_id_suitable_beds` Beds that fit this patient's current need, home ward first, overflow after	`GET /api/adt/v1/stays/{stay_id}/suitable-beds`	read
57	`adt.post_stays_stay_id_transfers` Move a patient to another bed or ward, or change department or attending	`POST /api/adt/v1/stays/{stay_id}/transfers`	write
58	`adt.post_stays_stay_id_wristband` Produce the identification wristband (ZPL); a reprint needs a reason	`POST /api/adt/v1/stays/{stay_id}/wristband`	write
59	`adt.get_stays_stay_id_wristband_preview` What the wristband will show, before printing; nothing is printed or recorded	`GET /api/adt/v1/stays/{stay_id}/wristband:preview`	read
60	`adt.post_transfers_movement_id_accept` The receiving unit accepts the transfer	`POST /api/adt/v1/transfers/{movement_id}:accept`	write
61	`adt.post_transfers_movement_id_arrive` The patient arrived: hand-off recorded, target bed occupied, source bed cleaning	`POST /api/adt/v1/transfers/{movement_id}:arrive`	write
62	`adt.post_transfers_movement_id_cancel` Cancel a transfer that has not happened; the held bed is released	`POST /api/adt/v1/transfers/{movement_id}:cancel`	write
63	`adt.get_waiting_list` Requests without a bed: urgent first, then longest waiting	`GET /api/adt/v1/waiting-list`	read
64	`adt.post_wards_ward_id_admission_holds` Stop new admissions to a ward for a time (e.g. an infection-control hold)	`POST /api/adt/v1/wards/{ward_id}/admission-holds`	write
65	`adt.get_wards_ward_id_rules` Room rules of a ward: sex policy against who is in it, class, surcharge, quota	`GET /api/adt/v1/wards/{ward_id}/rules`	read

Not mapped to a system尚未歸屬系統

To do: tools on the gateway that are not placed under a hospital system yet, so they are not counted above. Each one waits for a ruling on its system; once placed, it moves into Tools by system.

closed-loop-safety (8)

Not mapped: closed-loop-safety

GET	/api/safety/v1/dashboard	Dashboard	read	closed-loop-safety.get_dashboard	clinical
POST	/api/safety/v1/feedings:check	Feeding Check	write	closed-loop-safety.post_feedings_check	clinical
POST	/api/safety/v1/identity-checks	Identity Check	write	closed-loop-safety.post_identity_checks	clinical
POST	/api/safety/v1/loops	Open Loop Route	create	closed-loop-safety.post_loops	clinical
POST	/api/safety/v1/loops/{instance_id}:exception	Loop Exception	write	closed-loop-safety.post_loops_instance_id_exception	clinical
POST	/api/safety/v1/loops/{instance_id}/steps/{step_code}:advance	Advance	write	closed-loop-safety.post_loops_instance_id_steps_step_code_advance	clinical
POST	/api/safety/v1/milk-containers	Create Milk	write	closed-loop-safety.post_milk_containers	clinical
POST	/api/safety/v1/overdue:sweep	Overdue Sweep	write	closed-loop-safety.post_overdue_sweep	clinical

Shared services共用服務

Tools every hospital system uses, so they belong to no single system and are not counted above: AI models (risk scores, model deploy) and notification and staff chat (SMS, inbox, group chat).

Shared service tools

GET	/api/ai/v1/inferences/{inference_id}	Trace Inference	read	ai-inference.get_inferences_inference_id	analytics
POST	/api/ai/v1/inferences/{inference_id}/actions	Record Action	write	ai-inference.post_inferences_inference_id_actions	analytics
POST	/api/ai/v1/llm/complete	Llm Complete	write	ai-inference.post_llm_complete	analytics
POST	/api/ai/v1/models	Create Model	write	ai-inference.post_models	analytics
POST	/api/ai/v1/models/{model_id}/versions	Create Version	write	ai-inference.post_models_model_id_versions	analytics
POST	/api/ai/v1/models/{model_name}/predict	Model Predict	create	ai-inference.post_models_model_name_predict	analytics
POST	/api/ai/v1/monitor/metrics	Add Metric	write	ai-inference.post_monitor_metrics	analytics
GET	/api/ai/v1/patients/{patient_id}/risk	Patient Risk	read	ai-inference.get_patients_patient_id_risk	analytics
POST	/api/ai/v1/versions/{version_id}:approve	Approve Version	write	ai-inference.post_versions_version_id_approve	analytics
POST	/api/ai/v1/versions/{version_id}:deploy	Deploy Version	write	ai-inference.post_versions_version_id_deploy	analytics
GET	/api/notification/v1/admission-calls/{request_id}	What was sent to the patient for each call-down of an admission request: sent on which channels, or suppressed and why. The message text is not returned.	read	get_admission_call_messages	notification
GET	/api/notification/v1/deliveries	Delivery attempts, filtered by status (for example failed) or channel.	query	list_deliveries	notification
POST	/api/notification/v1/deliveries/{delivery_id}:retry	Retry one failed delivery. Needs the delivery-review permission.	write	retry_delivery	notification
GET	/api/notification/v1/inbox	The caller's own in-app inbox: unread first, with priority and whether an acknowledgement is required.	read	list_inbox	notification
POST	/api/notification/v1/inbox/{notification_id}:acknowledge	Acknowledge an inbox item that requires it, with an optional note.	write	acknowledge_inbox_item	notification
POST	/api/notification/v1/inbox/{notification_id}:read	Mark one of the caller's inbox items as read.	write	mark_inbox_read	notification
POST	/api/notification/v1/notification-batches	Send one template to a named batch of recipients and get a per-recipient result (sent, suppressed, unresolved).	create	send_notification_batch	notification
POST	/api/notification/v1/notifications	Send a notice from a template to one or more recipients (patients or staff); several recipients is a batch send. Returns the notification id, one delivery per recipient and the recipients that are unr	create	send_notification	notification
POST	/api/notification/v1/notifications:cancel-by-dedupe-key	Cancel every pending notification that carries one dedupe key.	write	cancel_notifications_by_dedupe_key	notification
GET	/api/notification/v1/notifications/{notification_id}	One notification with its timeline: per recipient and channel whether it was queued, sent, delivered, read, acknowledged or failed, and which recipients are unresolved (a role and unit nobody holds).	read	get_notification	notification
POST	/api/notification/v1/notifications/{notification_id}:cancel	Cancel a notification that is not yet sent (queued or scheduled).	write	cancel_notification	notification
POST	/api/notification/v1/patients/{patient_id}/channels/{channel}:verify	Verify a patient's contact on one channel (for example the mobile number).	update	verify_patient_channel	notification
PUT	/api/notification/v1/patients/{patient_id}/consents	Record a patient's channel consents (in-app, SMS). Withdrawal is honoured at once; notification checks the caller's permission.	update	set_patient_consents	notification
GET	/api/notification/v1/replies	Patient SMS replies received, filtered by handled or not.	query	list_sms_replies	notification
POST	/api/notification/v1/replies/{reply_id}:handled	Mark a patient SMS reply as handled by staff.	write	mark_sms_reply_handled	notification
POST	/api/notification/v1/sms	Send an SMS to a patient's mobile on record (patient_id required); no clinical detail in the text. 403 number-not-on-record, 409 sms-consent-withdrawn.	create	send_sms	comms
POST	/api/notification/v1/sms:simulate-inbound	Simulate a patient SMS reply (dev and test stacks only; the production adapter refuses it).	write	simulate_inbound_sms	notification
GET	/api/notification/v1/templates	Template catalogue, optionally for one audience (patient or staff).	read	list_templates	notification
GET	/api/notification/v1/templates/{key}/versions	Versions of one template and their status (draft, approved, retired).	read	list_template_versions	notification
POST	/api/notification/v1/templates/{key}/versions	Draft a new version of a template. Approval stays with a person; notification checks the caller's template permission.	write	create_template_version	notification

MCP catalogue

How to connect如何連線

取得金鑰 Get a key

確認連線 Check you can reach the gateway

選擇位址 Pick an address

連接你的工具 Connect your client

Claude Code

Claude Desktop

MCP Inspector (no AI, for testing)

第一次呼叫 First call

MCP catalogueMCP 工具目錄

Tools by system各系統 MCP 工具

adt · 65 tools

Not mapped to a system尚未歸屬系統

closed-loop-safety (8)

Shared services共用服務

MCP catalogue

How to connect如何連線

取得金鑰 Get a key

確認連線 Check you can reach the gateway

選擇位址 Pick an address

連接你的工具 Connect your client

Claude Code

Claude Desktop

MCP Inspector (no AI, for testing)

第一次呼叫 First call

MCP catalogueMCP 工具目錄

Tools by system各系統 MCP 工具

adt · 65 tools

Not mapped to a system尚未歸屬系統

closed-loop-safety (8)

Shared services共用服務