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.
CSV or Excel, one row per interface. Read in your browser.
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.
Three steps. About a minute.
No template to fill in first. Ariha works from the spreadsheet your team already maintains, headers and all.
-
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
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
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.
-
IF-0117
Message type
ORU HL7ORM HL7
- 2 systems Merged into Pharmacy 6 interfaces updated
| Your column | Read as | Example |
|---|---|---|
| Sending App | Source system | Patient Access |
| Rcv App | Target system | LIS |
| Msg | Message type | ADT^A08 |
| Via | Route | HealthConnect |
| Transport | Transport | MLLP |
| Owner | Not used | J. 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.
- Patient AccessSelected
- EHRImpact
- LISImpact
- PharmacyImpact
- BillingImpact
- RIS
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.
What happens to your data.
Interface inventories describe how your organization works. Here is exactly where they go.
-
Read in your browser
Your spreadsheet is opened and parsed in the browser.
-
Sent to OpenAI for one job
Rows are sent to OpenAI's API only to propose the column mapping. OpenAI does not train on API data. Ariha keeps no copy on its servers.
-
The AI doesn't draw
It proposes the mapping and the views. It never places boxes or draws arrows. Layout and routing are deterministic, so diagrams are consistent and reviewable.
-
Nothing changes silently
Similar names aren't auto-merged. Malformed rows aren't dropped. Ariha flags them for review and leaves the decision to you.
Bring a real inventory to the demo.
Messy headers welcome. Rows to diagrams takes about a minute.