Ariha Request a demo

Your interface spreadsheet, as an architecture diagram, in a minute.

Upload the inventory you already keep. Ariha finds the systems, spots the integration engine, and draws focused diagrams you can check line by line.

Request a demo See it on a sample inventory

CSV or Excel, one row per interface. Read in your browser.

interfaces_2026Q3.xlsx
214 rows, 8 columns Sheet 1

For enterprise architects and interface analysts in healthcare, insurance, and anywhere else the inventory lives in Excel.

Diagramming an inventory by hand doesn't hold up.

It takes days.
Someone exports 200 rows, opens Visio or Lucid, and drags boxes until the week is gone.
It's out of date on delivery.
The spreadsheet changes on Tuesday. The diagram doesn't. By the next review, nobody trusts it.
Nobody can read it.
Put every interface on one page and you get a hairball. Reviewers nod and move on.
What one page of 214 interfaces usually looks like.

Three steps. About a minute.

No template to fill in first. Ariha works from the spreadsheet your team already maintains, headers and all.

  1. 1

    Drop in your spreadsheet

    CSV or Excel, one row per interface. Column names can be whatever your team settled on years ago.

    interfaces_2026Q3.xlsx214 rows, 8 columns
  2. 2

    Ariha maps columns and plans views

    It works out the sender, receiver, message type and route, finds the engine most traffic passes through, and splits the inventory into views a person can read.

    • Sending AppSource system
    • Rcv AppTarget system
    • MsgMessage type
    • ViaRoute

    HealthConnect carries 171 of 214 interfaces. Drawn as a hub.

  3. 3

    Review, edit, export

    Check how each column was read. Fix what's wrong in plain English. Export a PDF for the review board.

    • Core clinical11 interfaces
    • ADT feeds96 interfaces
    • Orders and results58 interfaces
    • Revenue cycle41 interfaces

Built for the inventory you actually have.

Inconsistent headers, a hub that touches everything, two names for the same system. Ariha expects all of it.

interfaces_2026Q3.xlsx4 views
Core clinical6 systems
ADT feeds7 systems
Orders and results6 systems
Revenue cycle6 systems
Route column: ViaEngine detected
Drawn point to point
Drawn through the hub
EngineHealthConnect
Routes through it171 of 214
Direct, point to point43
EditCore clinical
this is ORM, not ORU
  • IF-0117 Message type ORU HL7 ORM HL7
merge Pharm and Pharmacy
  • 2 systems Merged into Pharmacy 6 interfaces updated
Column mapping8 columns
Your columnRead asExample
Sending AppSource systemPatient Access
Rcv AppTarget systemLIS
MsgMessage typeADT^A08
ViaRouteHealthConnect
TransportTransportMLLP
OwnerNot usedJ. Ruiz

Flagged for review

Row 88. Rcv App is empty. Kept and flagged, not dropped.

"Pharm" and "Pharmacy" look alike. Not merged until you say so.

Impact analysisOn
  • Patient AccessSelected
  • EHRImpact
  • LISImpact
  • PharmacyImpact
  • BillingImpact
  • RIS
Try it on the sample diagram below
ariha_interfaces_2026Q3.pdf4 pages
Core clinical
ADT feeds
Orders and results
Revenue cycle

What's affected if this system changes?

Turn on impact analysis and select a system. Every system that directly receives its interfaces is tagged, on every diagram in the workbook. Everything else steps back.

Core clinicalView 1 of 4
Click any system

Bring a real inventory to the demo.

Messy headers welcome. Rows to diagrams takes about a minute.

Request a demo See it on a sample inventory

Your spreadsheet is parsed in the browser, rows are sent to OpenAI only to propose the column mapping, and Ariha keeps no copy.