A
licenseA
qualityB
maintenanceTranslates HL7 v2.x messages to FHIR R4, validates against profiles like US Core, and explains errors in natural language for AI agents.
4
8 npm
Apache 2.0
HL7 v2.5.1 → FHIR R4 Mapping MCP Server
Related Servers
Alternatives to HL7 v2.5.1 → FHIR R4 Mapping MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables healthcare systems to parse HL7 v2 messages, convert them to FHIR R4 Bundles, validate FHIR resources, and detect/govern PHI with HIPAA, EU MDR, and GDPR compliance evidence for AI governance.MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to retrieve segment, field, message-structure, and code-table details; parse pipe-delimited messages; and validate messages with deep profiles for ORM^O01, ADT^A08/A31/A40, and ORU^R01.MIT
- FlicenseNot gradedqualityAmaintenanceConnects MCP clients to FHIR R4+ clinical APIs over SMART on FHIR v2 Backend Services, exposing resources, named operations, terminology lookup, and pagination as configurable tools. It adds metadata- and scope-aware search/CRUD, compact responses with FHIRPath filtering, safe pagination, audit events, and bundle execution.63 npm17-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely interact with FHIR R4 servers for clinical decision support workflows, including PlanDefinition execution, FHIR resource management, terminology services, and Questionnaire/StructureMap transformation via Matchbox.1-
- AlicenseNot gradedqualityBmaintenanceEnables natural-language querying of a mock legacy healthcare database and returns validated FHIR resources (Patient, Observation, Condition).MIT
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues