🏥 MCP Server for AWS HealthLake (Mocked)

Name: 🏥 MCP Server for AWS HealthLake (Mocked)
Author: anandkiran2007

@anandkiran2007

Repository

About 🏥 MCP Server for AWS HealthLake (Mocked)

No overview available yet

#mcp-server #aws-healthlake #mock-server

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "ahl-mcp-server": {
      "command": "python3",
      "args": [
        "-m",
        "venv",
        "venv"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is 🏥 MCP Server for AWS HealthLake (Mocked)?

This is an open-source Model Context Protocol (MCP) server that connects to (mocked) AWS HealthLake data sources and provides structured, standardized context bundles for clinical models.

How to use 🏥 MCP Server for AWS HealthLake (Mocked)?

Clone the repository, create a Python virtual environment, install dependencies with pip install -r requirements.txt, and run the server locally with uvicorn app.main:app --reload. By default the server runs in mock mode; set the environment variable USE_AWS=true to prepare for future AWS integration (AWS mode is not yet implemented). Access the interactive documentation at http://localhost:8000/docs.

Key features of 🏥 MCP Server for AWS HealthLake (Mocked)

Mocked AWS HealthLake APIs based on FHIR
Context bundling per MCP spec (FHIR + NLP)
Model registration and tailored context delivery
Mocked model invocation endpoint
Audit logging
Optional USE_AWS flag for future AWS integration

Use cases of 🏥 MCP Server for AWS HealthLake (Mocked)

Providing structured context bundles for clinical model predictions
Registering models and retrieving tailored patient context
Testing MCP workflows without incurring real AWS costs
Prototyping and validating FHIR-based integrations with HealthLake
Simulating patient data (conditions, medications, observations) for development

FAQ from 🏥 MCP Server for AWS HealthLake (Mocked)

What is the default mode of operation?

The server runs in mock mode by default, using mocked AWS HealthLake APIs. Real AWS integration is not yet implemented.

How can I prepare for real AWS integration?

Set the environment variable USE_AWS=true to switch to AWS mode. Note that AWS mode is not implemented yet but the infrastructure is ready for integration.

What FHIR endpoints are available for testing?

Mock endpoints include POST /ahl/Patient, GET /ahl/Patient/{id}, and GET endpoints for Condition, MedicationRequest, and Observation. You can also add mock data via /ahl/mock/add_* endpoints.