Ratchet Clinical Charting

Provides a mock-mode MCP server for clinical charting with Claude to document patient visits into PointCare EMR.

typescript

GitHub Stars

typescript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "m2ai-mcp-servers-mcp-ratchet-clinical-charting": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-ratchet-clinical-charting"
      ],
      "env": {
        "LOG_LEVEL": "info",
        "POINTCARE_API_KEY": "YOUR_API_KEY",
        "POINTCARE_API_URL": "https://api.pointcare.com",
        "RATCHET_MOCK_MODE": "true"
      }
    }
  }
}

You can run Ratchet, an MCP server that enables Claude to document patient visits directly into electronic medical records during home health care workflows. In development, it operates in mock mode to simulate realistic responses and test your Claude integration without requiring live EMR connections.

How to use

You interact with Ratchet through an MCP client like Claude Desktop. Start by running the MCP server locally or via a command that loads the Ratchet server, then use Claude’s available tools to search for patients, create visit notes with vitals, and retrieve patient history. In production, Ratchet can connect to PointCare’s EMR via a configured API URL and key.

How to install

Prerequisites: you need Node.js and npm installed on your system. Ensure you have a compatible environment for running JavaScript/TypeScript projects.

npm install -g npm@latest
node -v
npm -v

From source, follow these steps to install and run in development mode:

git clone https://github.com/m2ai-mcp-servers/mcp-ratchet-clinical-charting.git
cd mcp-ratchet-clinical-charting
npm install
npm run build
npm run dev  # Development mode
npm test     # Run tests

Additional sections

Mock mode is active by default when POINTCARE_API_URL is not configured. In mock mode, Ratchet uses five fictional test patients, stores visit notes in memory, and returns realistic responses. This mode is ideal for development and Claude Desktop testing.

Environment variables control mode and integration. The following variables are recognized: RATCHET_MOCK_MODE, POINTCARE_API_URL, POINTCARE_API_KEY, and LOG_LEVEL. You can override the default mock mode by setting RATCHET_MOCK_MODE to true or false.

Configuration and tools usage notes

To run in production with EMR integration, configure Claude Desktop to load Ratchet with environment variables for the PointCare API. The production configuration uses an MCP command that loads the package via npx and passes the necessary environment values.

Troubleshooting and tips

If Claude Desktop does not show the expected tools, restart Claude Desktop after updating the MCP server configuration to ensure the new process is loaded.

Next steps to production

Acquire PointCare API documentation, implement real API calls, and run integration tests with a PointCare sandbox to verify end-to-end behavior in production mode.

Available tools

search_patient

Find a patient by name, ID, or phone to begin documentation workflow.

create_visit_note

Document a patient visit and record vitals as a visit note.

get_patient_history

Retrieve the visit history for a specific patient.

Built by

VeilStrat

AI signals for GTM teams