Mcp Ratchet Clinical Charting

io.github.m2ai-mcp-servers由 GitHub 帳號 m2ai-mcp-servers 發布v0.1.0更新於 Oct 27, 2026

MCP server for clinical charting with Claude - document patient visits to EMR

發布方自己的服務:[PREPROD] Clinical.ly Research Suite

已驗證STDIO僅桌面位置與生活檔案與儲存

概覽

AI 產生的概覽

本機 MCP 伺服器,讓 Claude 查詢病患並撰寫居家護理訪視紀錄,目前僅使用模擬資料。

可以做什麼
  • 依姓名、ID 或電話尋找病患
  • 為病患建立含生命徵象的訪視紀錄
  • 查詢病患的訪視歷史
  • 預設以模擬模式執行,內建五名虛構測試病患,紀錄保存在記憶體中
適用情境
適合在真正的 EMR 整合完成前,於 Claude Desktop 中試用或示範 AI 輔助臨床紀錄。由於 PointCare 正式環境整合尚未完成,暫不適合用於真實病患紀錄。
執行需求
透過 npx 在本機執行,需要 Node.js,並在 Claude Desktop 設定檔中設定。正式模式需要 POINTCARE_API_URL 與 POINTCARE_API_KEY 環境變數;未設定時維持模擬模式。另有選用的 RATCHET_MOCK_MODE 與 LOG_LEVEL。
安裝前請注意
正式模式需要 EMR API 金鑰(POINTCARE_API_KEY),並會將病患資料傳送至 PointCare API。伺服器會建立並儲存訪視紀錄,涉及寫入操作。模擬模式僅在記憶體中保存虛構資料;真實 EMR 整合尚未實作。

安裝

在 SourceWeft 中

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

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

mcp-ratchet-clinical-charting

MCP server for clinical charting with Claude (codename: Ratchet) - Enables Claude to document patient visits directly into Electronic Medical Records, reducing administrative burden for home health nurses.

Note: Currently runs in Mock Mode for development/testing. Production EMR integration coming soon.

Status

ComponentStatus
MCP Server✅ Working (Mock Mode)
Unit Tests✅ 20/20 Passing
Claude Desktop✅ Ready for Testing
PointCare API⏳ Pending API Documentation

Current Mode: Mock Mode - Uses realistic test data for development and testing.

Quick Start

From npm (Recommended)

bash
npx mcp-ratchet-clinical-charting

From Source

bash
git clone https://github.com/m2ai-mcp-servers/mcp-ratchet-clinical-charting.gitcd mcp-ratchet-clinical-chartingnpm installnpm run buildnpm run dev  # Development modenpm test     # Run tests

Mock Mode

Ratchet runs in mock mode by default when POINTCARE_API_URL is not configured. Mock mode:

  • Uses 5 fictional test patients
  • Stores visit notes in memory
  • Returns realistic responses
  • Perfect for development and Claude Desktop testing

Available Tools

ToolDescriptionMock Mode
search_patientFind patient by name, ID, or phone✅ Working
create_visit_noteDocument a patient visit with vitals✅ Working
get_patient_historyRetrieve patient visit history✅ Working

Example Usage (in Claude)

"Search for patient Eleanor Thompson"→ Returns patient PT-10001 with demographics and status
"Create a visit note for PT-10001 with blood pressure 120/80"→ Creates and stores visit note with vitals
"Get visit history for PT-10001"→ Returns list of previous visits

Claude Desktop Integration

Configure Claude Desktop

Add to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

json
{  "mcpServers": {    "ratchet": {      "command": "npx",      "args": ["-y", "mcp-ratchet-clinical-charting"]    }  }}

For production mode with EMR integration:

json
{  "mcpServers": {    "ratchet": {      "command": "npx",      "args": ["-y", "mcp-ratchet-clinical-charting"],      "env": {        "POINTCARE_API_URL": "https://api.pointcare.com",        "POINTCARE_API_KEY": "your-api-key"      }    }  }}

Step 3: Restart Claude Desktop

Restart Claude Desktop to load the new MCP server.

Step 4: Verify

In Claude Desktop, you should see:

  • search_patient tool available
  • create_visit_note tool available
  • get_patient_history tool available

Try: "Search for patient Eleanor"

Test Patients (Mock Mode)

IDNameStatusPrimary Diagnosis
PT-10001Eleanor ThompsonActiveType 2 Diabetes, CHF
PT-10002Robert MartinezActiveCOPD, Post-surgical
PT-10003Margaret WilsonActiveParkinson's Disease
PT-10004James ThompsonActivePost-stroke rehab
PT-10005Dorothy AndersonDischargedHip replacement

Origin Story

Ratchet evolved from the M2AI NurseCall n8n workflow, built to help home health nurses with visit documentation:

Current Flow (M2AI NurseCall):┌─────────┐    ┌─────────┐    ┌─────────┐    ┌─────────┐│ Twilio  │───>│  n8n    │───>│  VAPI   │───>│  Email  ││  SMS    │    │ Workflow│    │  Call   │    │ Summary │└─────────┘    └─────────┘    └─────────┘    └─────────┘

The Problem: Visit notes go to email but still need manual entry into PointCare EMR.

Ratchet's Solution:

Future Flow (with Ratchet):┌─────────┐    ┌─────────┐    ┌──────────┐    ┌───────────┐│ Twilio  │───>│  n8n    │───>│ Ratchet  │───>│ PointCare ││  SMS    │    │ Workflow│    │   MCP    │    │    EMR    │└─────────┘    └─────────┘    └──────────┘    └───────────┘

Configuration

VariableRequiredDescription
POINTCARE_API_URLNo*PointCare API base URL
POINTCARE_API_KEYNo*API key or token
RATCHET_MOCK_MODENoForce mock mode (true/false)
LOG_LEVELNoLogging level (debug/info/warn/error)

*Required for production use. Mock mode activates when not set.

Project Structure

ratchet/├── src/│   ├── index.ts              # MCP server entry point│   ├── config.ts             # Configuration management│   ├── tools/                # Tool implementations│   │   ├── search-patient.ts│   │   ├── create-visit-note.ts│   │   └── get-patient-history.ts│   ├── services/             # Business logic│   │   ├── patient-service.ts│   │   └── mock-data.ts│   ├── types/                # TypeScript types│   └── utils/                # Logger, errors├── tests/│   └── patient-service.test.ts├── dist/                     # Compiled output├── prds/│   └── RATCHET-PRD.yaml├── docs/│   └── API_REQUIREMENTS.md├── package.json├── tsconfig.json└── jest.config.js

Development

bash
# Run in watch modenpm run dev
# Run testsnpm test
# Run tests with coveragenpm test -- --coverage
# Lintnpm run lint

Next Steps

  1. Acquire PointCare API documentation - See docs/API_REQUIREMENTS.md
  2. Complete PRD - Fill in tool specifications with real API details
  3. Implement real API calls - Replace mock responses
  4. Integration testing - Test with PointCare sandbox

Related Projects

License

MIT


Built with GRIMLOCK - Autonomous MCP Server Factory

來源:README.md,提交 f6a9782

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

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

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Clinical 整合