A
licenseNot graded
qualityB
maintenanceEnables 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
HL7-Bridge MCP
by GlennRTC
Related Servers
Alternatives to HL7-Bridge MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables users to look up how specific v2 fields, datatypes, and table codes translate to R4, and to convert whole ORM, ADT, and ORU messages into transaction Bundles with explicit warnings for unmapped values.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 gradedqualityCmaintenanceProvides FHIR resource validation, synthetic test fixture generation, and HIPAA-safe logging review as MCP tools for AI agents.-
- AlicenseAqualityCmaintenanceLet AI agents read, validate and acknowledge EDI documents. Parses raw X12 and EDIFACT interchanges into structured JSON, validates envelope integrity, produces plain-language summaries, and generates 997 Functional Acknowledgments.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables natural-language querying of a mock legacy healthcare database and returns validated FHIR resources (Patient, Observation, Condition).MIT
TDQS
A3.9/5.0
Scored across 4 tools
Disambiguation4/5
Each tool has a clear core purpose (parse, validate, map, explain), but map_v2_to_fhir and validate_message both perform validation, which could create confusion when an agent is deciding which tool to use for a raw input check. The descriptions are specific enough to generally disambiguate.
Naming Consistency5/5
All tool names follow a consistent verb-first snake_case pattern (parse, validate, map, explain), with clear object references. There is no mixing of casing or verb styles, making the set predictable.
Tool Count5/5
Four tools is a well-scoped count for an HL7-to-FHIR bridge workflow. Each tool covers a distinct step without unnecessary duplication, and nothing feels like filler.
Completeness4/5
The core pipeline (parse, validate, map, explain) is well covered, but a 'bridge' might imply bidirectional conversion. Since all tools are v2-to-FHIR oriented, a reverse mapping tool is a natural but missing addition, and there is no map management tool, which would be a minor gap.
Maintenance
ActivityStale
ResponsivenessNo issues