imonfhir.com tools: HL7 digest, Jira status, PAS validation, IG and payload compare, rule evidence.
Score is being calculated.
Compare two implementation guides, each "packageId#version": one guide at two versions (version diff) or two guides (stack compare). Over MCP the answer is a bounded summary (counts per change type, the most serious findings, and where the whole report is); POST /api/v1/compare returns the whole report.
Inputs: ig_a (required), ig_b (required). Returns: ig_a, ig_b, mode, risk, +10 more
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 missing or extra, which field paths changed, and counts. It returns no field values; it lists up to 200 rows and 300 field paths (the paths come from the key names in the payloads) and counts the rest. Synthetic data only. The payloads are sent to imonfhir.com for the call and the site does not store them; the browser Compare tool at /lab/compare keeps them on your machine.
Inputs: a (required), b (required). Returns: rows, stats, notice, identical, +5 more
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's id, version, title, description, source, category and default severity as the validator states them, plus, only when the rule's explanation entry declares anchors that all resolve, the HL7 statements for them: package, version, key, conformance word, HL7's statement text verbatim (its markdown) and the sha256 of that text. It abstains, with the reason, when no anchor is committed or one does not resolve. 0 of 17 rule explanations have committed anchors; a rule id abstains until its anchors are committed. Or give requirement ({packageId, version, key}) and get that one HL7 statement the same way. An unknown package, version or key is an error, and so is a package version that has a catalog but no committed statement text. Statement text is committed for hl7.fhir.us.davinci-pas@2.2.1; a package version that has a catalog but no committed text is an error. It also returns an instruction block telling your assistant how to use the evidence. It calls nothing outside this site. Prose your assistant writes around the passages is not controlled by ImOnFHIR.
Inputs: rule_id, requirement. Returns: mode, rule, notice, abstain, +3 more
One digest item in full: each claim (question, outcome, impact, stage, next step) with its own evidence record, plus HL7 Jira statuses and canonical_url.
Inputs: id (required). Returns: id, jira, stage, title, +8 more
Up to 50 HL7 Jira keys: status, resolved, resolution, last_verified with its jira_verified evidence record, lifecycle stage, source_url (HL7 Jira) and the canonical_url of public items that cite it. "applied" is not "published".
Inputs: keys (required). Returns: statuses, attribution
Search the public digest of HL7 standards discussions. Returns at most 20 items, each with every claim's evidence record and canonical_url — no summary text. Use get_digest_item for one item in full.
Inputs: q, since, workgroup. Returns: count, items, attribution
Validate a synthetic Da Vinci PAS Submit Bundle with the ImOnFHIR validator. Synthetic payloads only. Never send real patient data. Findings describe a synthetic Bundle. Body cap 2 MB, 10 calls per minute.
Inputs: bundle (required), ig, version. Returns: ig, notice, outcome, version, +1 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Privacy-preserving synthetic health data generation. FHIR R4/R5 compliant.
Diagnoses, drugs & lab codes: ICD-11, LOINC, RxNorm, MeSH, ATC, CID-10. 33 tools, MIT.
Open healthcare quality measures: CQL, SQL and FHIR with provenance and known issues
Clinical trials, RxNorm drug lookups, FDA drug and device data, PubMed and NHS organisations.
Add one secure layer between your agents and this server.
