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 集成