Healthcare IT Network Diagram Builder
Drag-and-drop PACS, RIS, EHR, interface engines and more, connect them with protocol-labelled links, and share a link or export PNG, SVG or PDF. Start blank or from 12 reference architectures.
Read-only on phones. The editor needs a 1024px+ screen — you can still view and download diagrams here.
Start from a reference architecture
Each template explains its components, data flow and every interface — then opens in the builder for you to adapt.
How to draw a healthcare IT architecture diagram
From a blank page to a diagram you can drop into a design document in a few minutes.
- STEP 1
Pick a starting point
Load one of the 12 reference architectures from Templates, or start from a blank canvas.
- STEP 2
Add your systems
Drag PACS, modalities, RIS, EHR, interface engines and infrastructure from the node library, then rename them to your products.
- STEP 3
Connect and label
Drag from one node’s handle to another, choose the protocol and add the detail — message type, DICOM service or port.
- STEP 4
Tidy the layout
Click Auto-layout to arrange everything left-to-right or top-to-bottom, or select several nodes to align them. Group systems into zones such as a DMZ or a site.
- STEP 5
Share or export
Copy a share link for a colleague, save to your browser, or export PNG, SVG or PDF for your design document.
Connection types
Every link is coloured by protocol. Add a detail label — a message type, DICOM service or port — to make the diagram an interface reference.
| Protocol | Typically used for |
|---|---|
| DICOM | Image storage and transfer between modalities, PACS and archives (C-STORE, C-ECHO, Storage Commitment). Ports 104 or 11112 by convention. Learn more → |
| HL7 | HL7 v2 event messages over MLLP — ADT, orders (ORM/OML), results (ORU), charges (DFT). Ports are assigned per interface. Learn more → |
| FHIR | RESTful API for clinical resources over HTTPS, with SMART on FHIR (OAuth 2.0) for app authorization. Learn more → |
| WADO-RS | DICOMweb retrieval of studies, series and instances over HTTPS — typical for web viewers. |
| DICOMweb | QIDO-RS search, STOW-RS upload and WADO-RS retrieval over HTTPS. |
| TCP/IP | Generic network link — storage protocols (iSCSI, NFS), instrument interfaces, database replication. |
| VPN | Encrypted site-to-site tunnel (IPsec) between hospitals, DR sites or external providers. |
| HTTP | Web traffic, viewer launch URLs and vendor portals. |
| API | Vendor-specific REST or SOAP APIs and desktop context integration. |
| DICOM MWL | Modality Worklist C-FIND from the modality to the RIS or worklist broker. Learn more → |
| DICOM Q/R | C-FIND, C-MOVE and C-GET queries and retrievals between viewers, PACS and archives. |
| Custom | Anything else — describe it with the connection’s detail label. |
Frequently asked questions
Is the Healthcare IT Diagram Builder free?
Yes. Building diagrams, saving them in your browser, share links, all 12 templates and PNG export (with a small majware.com credit) are free. SVG, PDF, the CSV interface list and credit-free exports need a one-time free email unlock.
Is my diagram uploaded anywhere?
No. The builder runs entirely in your browser. Diagrams are saved to your browser’s local storage, and share links carry the diagram inside the link itself, so nothing is sent to Majware’s servers.
How do I share a diagram with a colleague?
Click Share in the toolbar. You get a link that contains the whole diagram; anyone who opens it gets their own editable copy. For very large diagrams, export JSON from My Diagrams and send the file instead.
Can I get a list of every interface in my diagram?
Yes. Export as CSV to get one row per connection with both systems, their zones, AE titles, hosts and ports, the protocol and the message detail — ready for an interface register, a firewall change request or a go-live test plan.
Can I use the diagram in Visio, draw.io or PowerPoint?
Export as SVG or PNG and insert it into Visio, draw.io (diagrams.net), PowerPoint, Word or Confluence. SVG stays sharp at any size.
What can I draw with it?
55 healthcare-specific components — PACS, VNA, modalities, RIS, EHR, LIS, analyzers, interface engines, FHIR servers, EMPI, firewalls and more — connected by DICOM, HL7, FHIR, DICOMweb and network links, each with an optional detail label such as ORM^O01 or C-STORE :104.
Does it work on a phone or tablet?
The editor needs a screen at least 1024px wide. On a phone you get a read-only view of the diagram — including shared links — with zoom and a PNG download, and the template gallery works on any screen.
Related free tools
DICOM Header Validator
Validate DICOM headers and check interoperability issues in seconds.
HL7 Message Viewer
Parse and decode HL7 v2.x messages instantly in your browser.
HL7 to FHIR Converter
Map HL7 v2 messages to FHIR R4 resources, client-side.
DICOM Anonymizer
Remove PHI from DICOM files without uploading them.