
DS Core Open API
Connects AI models to DS Core's healthcare API to search and retrieve patient records, medical documents, DICOM imaging studies, and dental scan data.
Integrates with DS Core Open API healthcare system to provide search and retrieval of patient records, DICOM studies, digital impressions, and clinical documents with pagination, filtering, and comprehensive medical data access.
What it does
- Search patients by name or card ID
- Retrieve complete patient medical records
- List and fetch healthcare documents with metadata
- Access DICOM medical imaging studies
- Manage digital dental impression data
- Filter results with pagination support
Best for
About DS Core Open API
DS Core Open API is a community-built MCP server published by silverjava that provides AI assistants with tools and capabilities via the Model Context Protocol. DS Core Open API: Securely search and retrieve patient records, DICOM studies, digital impressions, and clinical documen It is categorized under ai ml, developer tools.
How to install
You can install DS Core Open API in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
License
DS Core Open API is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
DS Core MCP Server
A monorepo collection of Model Context Protocol (MCP) servers for DS Core's Open API platform, enabling AI Large Language Models to seamlessly interact with healthcare data and services.
Powered by DS Core Open API Platform - Complete AI-Ready Healthcare Data Access
MCP Servers
This monorepo contains four specialized MCP servers for different DS Core healthcare domains:
1. Patient Management (dscore-openapi-patient)
AI-enhanced patient data access with search and retrieval capabilities.
Tools:
search-patient- Search patients by name, card ID with paginationget-patient- Retrieve complete patient records
2. Document Management (dscore-openapi-document)
Healthcare document discovery and retrieval with advanced filtering.
Tools:
list-documents- List documents with patient/time filteringget-document- Get complete document metadata and content URIs
3. DICOM Study Management (dscore-openapi-dcmstudy)
Medical imaging study access with DICOM metadata support.
Tools:
list-dicom-studies- List DICOM studies with customizable metadata masksget-dicom-study- Retrieve complete study information with series/instance data
4. Digital Impression Management (dscore-openapi-digitalimpression)
Dental scan data access and management.
Tools:
list-digital-impressions- List digital impressions with filteringget-digital-impression- Get complete dental scan data and metadata
Quick Start
Prerequisites
- Node.js (v16 or higher recommended)
- DS Core Open API credentials from https://open.dscore.com/
Installation
# Clone the repository
git clone <repository-url>
cd dscore-mcp-server
# Install dependencies
npm install
# Build all servers
npm run build
Build Individual Servers
npm run build:patient
npm run build:document
npm run build:dcmstudy
npm run build:digitalimpression
Configuration
All MCP servers require DS Core Open API credentials:
Required Environment Variables:
GENAPI_BASE_URL- Your DS Core Open API endpoint URLGENAPI_API_KEY- Your DS Core Open API authentication key
Usage
Each MCP server can be run independently. See individual server READMEs for detailed usage instructions:
- Patient Server README
- Document Server README
- DICOM Study Server README
- Digital Impression Server README
Example: Running with npx
# Set environment variables
export GENAPI_BASE_URL=your_genapi_base_url
export GENAPI_API_KEY=your_genapi_api_key
# Run any server
npx dscore-openapi-patient-mcp@latest
npx dscore-openapi-document-mcp@latest
npx dscore-openapi-dcmstudy-mcp@latest
npx dscore-openapi-digitalimpression-mcp@latest
Development
# Build all servers
npm run build
# Run tests
npm run test
# Lint code
npm run lint
# Clean build artifacts
npm run clean
Monorepo Structure
dscore-mcp-server/
├── mcp-servers/
│ ├── dscore-openapi-patient/
│ ├── dscore-openapi-document/
│ ├── dscore-openapi-dcmstudy/
│ └── dscore-openapi-digitalimpression/
├── package.json
├── tsconfig.base.json
└── README.md
About DS Core Open API Platform
The DS Core Open API Platform provides comprehensive, secure, and scalable infrastructure for healthcare data access in the AI era. These MCP servers enable seamless integration of DS Core's healthcare capabilities with modern Large Language Models.
Platform Benefits:
- Complete healthcare data ecosystem access
- AI-ready architecture for LLM integration
- Enterprise-grade security and compliance
- Real-time data synchronization
- Developer-friendly APIs
License
MIT License
Alternatives
Related Skills
Browse all skillsMaster API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
Use when working with the OpenAI API (Responses API) or OpenAI platform features (tools, streaming, Realtime API, auth, models, rate limits, MCP) and you need authoritative, up-to-date documentation (schemas, examples, limits, edge cases). Prefer the OpenAI Developer Documentation MCP server tools when available; otherwise guide the user to enable `openaiDeveloperDocs`.
.NET/C# backend developer for ASP.NET Core APIs with Entity Framework Core. Builds REST APIs, minimal APIs, gRPC services, authentication with Identity/JWT, authorization, database operations, background services, SignalR real-time features. Activates for: .NET, C#, ASP.NET Core, Entity Framework Core, EF Core, .NET Core, minimal API, Web API, gRPC, authentication .NET, Identity, JWT .NET, authorization, LINQ, async/await C#, background service, IHostedService, SignalR, SQL Server, PostgreSQL .NET, dependency injection, middleware .NET.
Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".
Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc.) into focused tools people will pay for. Not just 'ChatGPT but different' - products that solve specific problems with AI. Covers prompt engineering for products, cost management, rate limiting, and building defensible AI businesses. Use when: AI wrapper, GPT product, AI tool, wrap AI, AI SaaS.
Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits); prioritize OpenAI docs MCP tools and restrict any fallback browsing to official OpenAI domains.