K01 Synthetic Health Data

Registre officiel Santé

Privacy-preserving synthetic health data generation. FHIR R4/R5 compliant.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http k01-synthetic-health-data 'https://mcp.k01.is/mcp' --header 'Authorization: <API key for authentication (Bearer token)>'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "k01-synthetic-health-data": {
            "type": "http",
            "url": "https://mcp.k01.is/mcp",
            "headers": {
                "Authorization": "<API key for authentication (Bearer token)>"
            }
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. K01 MCP Server
  2. Available Tools
  3. Quick Start
  4. Authentication
  5. Examples
  6. Privacy and Security
  7. Links
  8. License

K01 MCP Server

Generate and query clinically realistic synthetic health data directly from your AI workflow.


K01's MCP server gives AI agents and LLM-powered tools access to privacy-preserving synthetic health data generation. Generate FHIR-compliant patient cohorts, query structured EHR data, and compare across FHIR versions — all with built-in differential privacy. The server never handles real patient records: it serves synthetic data from generators that were trained on real records, under differential privacy, inside a separate controlled environment.

This repository contains documentation and configuration for the K01 MCP server. The server implementation is proprietary and runs on K01 infrastructure.

Available Tools

ToolDescriptionKey Parameters
generate_synthetic_cohortGenerate synthetic patient cohorts with demographic and clinical constraintscount, age_min/age_max, gender, condition (ICD-10), seed, locale
search_patientsSearch a virtual patient database with advanced healthcare filtersgender, birthdate, numberOfMedicinesFrom/To, conditionTypes, locale
get_patient_recordRetrieve a complete patient record with medication and condition summariespatient_id, fhir_version
get_patient_medicationsGet detailed medication records with ATC codes and therapeutic indicationspatient_id, seed, fhir_version
get_patient_conditionsRetrieve patient conditions with ICD-10 codes and localized namespatient_id, seed, fhir_version
compare_fhir_versionsCompare the same patient data across FHIR R4 and R5patient_id, resource_type

All tools support both FHIR R4 and R5. See docs/tools.md for full parameter documentation.

Quick Start

Claude Desktop

Add to your Claude Desktop configuration (Settings > MCP Servers):

{
  "mcpServers": {
    "k01": {
      "url": "https://mcp.k01.is/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
Cursor

Add to your Cursor MCP configuration (.cursor/mcp.json):

{
  "mcpServers": {
    "k01": {
      "url": "https://mcp.k01.is/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Restart the application after adding the configuration. The K01 tools will appear in the tool list.

Authentication

The K01 MCP server uses Bearer token authentication. Include your API key in the Authorization header.

To get an API key, contact K01 at k01.is. Self-service key provisioning is coming soon.

See docs/authentication.md for details.

Examples

Generate a diabetic cohort

"Generate 100 patients aged 40-65 with Type 2 diabetes"

The generate_synthetic_cohort tool creates a FHIR Bundle with Patient, Condition, MedicationStatement, Procedure, and Observation resources:

generate_synthetic_cohort(count=100, age_min=40, age_max=65, condition="E11.9", seed=42)
Search for complex patients

"Find patients with 3+ medications and chronic conditions"

search_patients(numberOfMedicinesFrom=3, conditionTypes="chronic", _count=20)
Compare FHIR versions

"How do this patient's medications look in R4 vs R5?"

compare_fhir_versions(patient_id="0101302989", resource_type="Medication")

See docs/examples.md for more workflows.

Privacy and Security

All data this server returns is fully synthetic. No real patient data passes through the server, is stored by it or is referenced by it.

  • Differential privacy — noise injection with configurable epsilon values ensures generated distributions cannot be reverse-engineered to identify real individuals
  • Real data stays behind the firewall — the generators are trained on real records under differential privacy inside a separate controlled environment; only the trained generators, never the records, are reachable from this server
  • FHIR-compliant output — all resources conform to HL7 FHIR R4/R5 specifications, making them safe drop-in replacements for real data in development and testing
  • Deterministic seeding — use seeds for reproducible results without persisting any patient data server-side

License

This repository (documentation, configuration, and examples) is licensed under MIT. The K01 server implementation is proprietary.

Questions fréquentes

Qu'est-ce que K01 Synthetic Health Data ?

Privacy-preserving synthetic health data generation. FHIR R4/R5 compliant.

Comment installer K01 Synthetic Health Data ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http k01-synthetic-health-data 'https://mcp.k01.is/mcp' --header 'Authorization: <API key for authentication (Bearer token)>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour K01 Synthetic Health Data ?

Oui. Il attend Authorization, à renseigner dans sa configuration.

K01 Synthetic Health Data est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient K01 Synthetic Health Data ?

Il est publié par K01labs. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.