Securely access and manage FHIR healthcare data stored in Medplum.
com.medplum/mcp (MCP) โ Medplum FHIR Access Server
The com.medplum/mcp Model Context Protocol (MCP) server is designed to securely access and manage FHIR healthcare data stored in Medplum. It supports developer workflows that need programmatic interaction with Medplum-hosted FHIR resources via MCP.
๐ ๏ธ Key Features
Secure access to Medplum-stored FHIR healthcare data
Manage FHIR healthcare data in Medplum
๐ Use Cases
Accessing FHIR data stored in Medplum
Managing FHIR healthcare data held by Medplum systems
โก Developer Benefits
Uses MCP to interact with Medplum FHIR data
Provides a focused interface for secure Medplum FHIR data access and management
Medplum is a developer platform that enables flexible and rapid development of healthcare apps.
Medplum Auth - End-to-end identity solution for easy user authentication, sign-in, and permissions using OAuth, OpenID, and SMART-on-FHIR.
Medplum Clinical Data Repository (CDR) - Backend server that hosts your healthcare data in a secure, compliant, and standards-based repository.
Medplum API - FHIR-based API for sending, receiving, and manipulating data.
Medplum SDK - Client libraries that simplify the process of interacting with the Medplum API.
Medplum App - Web application where you can view your data and perform basic editing tasks. You can also use the Medplum App to manage basic workflows.
Medplum Bots - Write and run application logic server-side without needing to set up your own server.
UI Component Library - React components designed to help you quickly develop custom healthcare applications.
We heartily welcome any and all contributions that match our engineering standards!
That being said, this codebase isn't your typical open-source project because it's not a library or package with a
limited scope -- it's our entire product. Our Contributing documentation has
all the information you need to get started.
All conversations and communities on Medplum are expected to follow GitHub's Community Guidelines
and Acceptable Use Policies. We expect
discussions on issues and pull requests to stay positive, productive, and respectful. Remember: there are real people on
the other side of the screen!
Reporting a bug or proposing a new feature
If you found a technical bug on Medplum or have ideas for features we should implement, the issue tracker is the best
place to share with us. (click here to open a new issue)
Writing documentation or blog content
Did you learn how to do something using Medplum that wasn't obvious on your first try? By contributing your new knowledge
to our documentation, you can help others who might have a similar use case!
For relatively small changes, you can edit files directly from your web browser on GitHub.dev
without needing to clone the repository.
Fixing a bug or implementing a new feature
If you find a bug and open a Pull Request that fixes it, we'll review it as soon as possible to ensure it meets our engineering standards.
If you want to implement a new feature, open an issue first to discuss with us how the feature might work, and to ensure
it fits into our roadmap and plans for the app.
With the ground rules out of the way, let's talk about the coarse architecture of this mono repo:
Full-stack TypeScript: We use Node.js to power our servers, and React to power our frontend apps. Almost all of the code you'll touch in this codebase will be TypeScript.
Here is a list of all the big technologies we use:
PostgreSQL: Data storage
Redis: Background jobs and caching
Express: API server
TypeScript: Type-safe JavaScript
React: Frontend React app
Folder structure
sh
medplum/
โโโ packages
โย ย โโโ agent # On-premise agent
โย ย โโโ app # Frontend web app
โย ย โโโ bot-layer # AWS Lambda Layer for Bots
โย ย โโโ cdk # AWS CDK infra as code
โย ย โโโ cli # Command line interface
โย ย โโโ core # Core shared library
โย ย โโโ definitions # Data definitions
โย ย โโโ docs # Documentation
โย ย โโโ examples # Example code used in documentation
โย ย โโโ fhir-router # FHIR URL router
โย ย โโโ fhirtypes # FHIR TypeScript definitions
โย ย โโโ generator # Code generator utilities
โย ย โโโ graphiql # Preconfigured GraphiQL
โย ย โโโ hl7 # HL7 client and server
โย ย โโโ mock # Mock FHIR data for testing
โย ย โโโ react # React component library
โย ย โโโ react-hooks # React hooks library
โย ย โโโ server # Backend API server
โโโ scripts # Helper bash scripts
Thanks
Thanks to Chromatic for providing the visual testing platform that helps us review UI changes and catch visual regressions.