Health Record MCP

🚀 EHR Tool Project Documentation

This project aims to provide a toolset based on the SMART on FHIR standard and the Model Context Protocol (MCP) for the medical and health field. The tool allows users to access and process Electronic Health Record (EHR) data in various ways.

🚀 Quick Start

✨ Features

1. SMART on FHIR Integration: Supports interaction with the ehr - sim platform that complies with the SMART on FHIR standard.
2. Model Context Protocol (MCP): Enables access to and control of the ehr - sim simulator through the MCP protocol.

📚 Documentation

Operation Modes

1. Local Running Mode (via Standard Input and Output)

This mode is suitable for use in a development environment. It supports starting the service through a command - line tool and interacting with the ehr - sim simulator.

Usage Steps

1. Create a Database:

   # Example: Save data to the data/my_record.sqlite file
   bun run src/cli.ts --create-db --db ./data/my_record.sqlite
   

   Open a browser and follow the prompts to connect to the ehr - sim simulator.

2. Start the MCP Service:

   # Example: Start the service using the created database file
   bun run src/cli.ts --db ./data/my_record.sqlite
   

Configuration Requirements

• Configuration File: A brand configuration file (e.g., config.epicsandbox.json) is required, which contains the following information:

  • url: Specifies the path to the brand's definition file (e.g., static/brands/epic-sandbox.json).
  • tags: An array of brand tags for classification and filtering (e.g., [ "epic", "sandbox" ]).
  • vendorConfig: Contains detailed information about the SMART on FHIR client (e.g., clientId, scopes).

• Client Configuration:

  {
    "mcpServers": {
      "local-ehr": {
        "name": "Local EHR Search",
        "command": "bun", // or the absolute path of bun
        "args": [
          "/home/user/projects/smart-mcp/src/cli.ts", // the absolute path of cli.ts
          "--db",
          "/home/user/projects/smart-mcp/data/my_record.sqlite" // the absolute path of the database file
        ]
      }
    }
  }
  

2. Global Running Mode (via Server - Sent Events)

This mode provides a persistent network service that supports multiple client connections. It uses Server - Sent Events (SSE) for communication.

Features

• Authentication: Implements client authentication using the OAuth 2.1 protocol.
• Data Acquisition: Automatically completes the SMART on FHIR process during the authorization process and stores ClientFullEHR data in memory or a persistent session.

Important Note

• Currently, the support for OAuth 2.1 clients is limited and is only suitable for specialized development or debugging tools.
• This mode is still in the experimental stage.

The above is the core content of this project, covering the main functions, operation modes, and configuration requirements. For further information, please refer to the relevant technical documentation or contact the project maintainers.