Categories › Knowledge & Everyday › Health, fitness & medical
imonfhir.com tools: HL7 digest, Jira status, PAS validation, IG and payload compare, rule evidence.
Remote server: your requests and data go to imonfhir.com. Claude Code: claude mcp add --transport http imonfhir https://imonfhir.com/api/v1/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
search_digest — Search the public digest of HL7 standards discussions. Returns at most 20 items, each with every claim's evidence record and canonical_url —get_digest_item — One digest item in full: each claim (question, outcome, impact, stage, next step) with its own evidence record, plus HL7 Jira statuses and cget_jira_status — Up to 50 HL7 Jira keys: status, resolved, resolution, last_verified with its jira_verified evidence record, lifecycle stage, source_url (HL7validate_bundle — Validate a synthetic Da Vinci PAS Submit Bundle with the ImOnFHIR validator. Synthetic payloads only. Never send real patient data. Findingscompare_igs — Compare two implementation guides, each "packageId#version": one guide at two versions (version diff) or two guides (stack compare). Over MCcompare_payloads — Compare two synthetic FHIR payloads (a resource or a Bundle each, 1 MB at most per side) and report where they differ: which rows are missinexplain_finding — The evidence behind a semantic validator rule, not an explanation of it. Give rule_id (a rule id such as PAS-SEM-PROV-001) and get the rule'Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.