{"uid":"cap_hZtDl-zTTEi7vWIlXo6O3","slug":"hl7-v2-message-broker-mcp-0e3d81a1","name":"HL7 v2 Message Broker MCP","description":"The premier global index of 1,069 monetized MCP nodes across 205 specialized subdomains. Gasless USDC runtime settlements via x402 V2 Spec on Base L2. Save 95% token context.","url":"https://api.m2mcent.com/hl7-v2-message-broker-mcp/api/process?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":null,"responseSchema":{"type":"json","example":{"success":true}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.15","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.15/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.15","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.15","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_0tNx6Ucn-fHUkflu7Ppiw","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.15","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Processes and brokers HL7 v2 healthcare messages, parsing and routing clinical data payloads","exampleAgentPrompt":"Can you process this HL7 v2 ADT message for me and extract the patient demographics and visit information from it? Here's the raw message: 'MSH|^~\\&|EPIC|EPICADT|SMS|SMSADT|199912271408|...'","exampleUseCases":[{"title":"Extract patient data from ADT message","prompt":"I have this raw HL7 v2 ADT^A01 admission message and I need you to parse it and pull out the patient name, DOB, and visit details from it."},{"title":"Route lab result HL7 messages","prompt":"We're receiving HL7 v2 ORU^R01 lab result messages from our LIS system — can you process this message and route the structured result data so it's usable downstream?"},{"title":"Validate HL7 order message format","prompt":"Can you run this HL7 v2 ORM^O01 order message through the broker to check if it's valid and properly structured before we send it to our EHR system?"}],"resultDescription":"Returns the processed result of the HL7 v2 message, which may include parsed segment data, structured clinical fields, routing outcomes, or validation status depending on the message type submitted.","failureModes":["Malformed HL7 v2 message string causes parse error","Unsupported HL7 message type returns error","Empty or missing 'data' field returns validation failure","Non-HL7 payload submitted returns format error","Network timeout or service unavailability returns 5xx"],"whenToPreferThis":"Choose this endpoint when you need to parse, validate, route, or transform raw HL7 v2 message strings in a healthcare interoperability pipeline. Ideal for agents integrating with legacy EHR systems, LIS, or RIS that emit HL7 v2 over MLLP or HTTP. Prefer this over FHIR-based endpoints when your source system specifically produces HL7 v2 (not FHIR or HL7 v3).","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-16T06:55:07.481Z","isFirstParty":false,"canonicalSlug":"hl7-v2-message-broker-mcp-0e3d81a1"}