Building my map of FHIR

ImOnFHIR is the engineering workbench I use every day to understand healthcare interoperability. Every tool starts as something I needed while solving a real implementation problem—debugging payloads, comparing implementation guides, validating assumptions, or exploring new standards.

As those tools become useful, I open them to the community. Use them. Break them. Challenge the results. If something doesn’t work, tell me. If something is missing,

It’s an evolving engineering lab where I document what I’m learning, track how FHIR changes over time, and build practical tools that make interoperability easier to understand.

Paste a Da Vinci PAS payload and see what a payer would reject, what a finding actually means, and what changed between IG versions. Runs on synthetic data, in your browser — or start from a sample payload · open the Factory.

Everything runs on synthetic data. Nothing here requires PHI. Everything is open to feedback and improvement.

  1. Synthetic DataControlled healthcare test records
  2. Layered ValidationFHIR structure through synthetic payer rules
  3. Version ComparisonFindings diffed across IG releases
  4. Provenance-Labeled FindingsDownloadable evidence packs

Interoperability is easier to understand when you can see it work.

Standards and implementation guides define how healthcare systems should exchange information. Real implementation requires more: test data, repeatable scenarios, integration logic, expected outcomes, traceability, and evidence.

ImOnFHIR turns those concepts into working demonstrations and practical engineering tools.

Build

Create controlled healthcare interoperability workflows using synthetic data.

Test

Run repeatable scenarios and compare expected behavior with observed results.

Explain

Make complex integrations understandable through architecture, IG version differences, provenance, and evidence.

FHIR-focused. Healthcare-wide.

ImOnFHIR begins with FHIR and prior-authorization workflows, but healthcare interoperability extends across payers, providers, electronic health records, implementation teams, clinical systems, administrative transactions, and emerging healthcare technologies.

Designed as a controlled interoperability environment

The application database remains the controlled source of truth. External FHIR environments are integration targets, allowing test data and scenarios to remain repeatable, observable, and replaceable.