Basic Networking for Medical Equipment

What biomeds need to know.

A plain-English introduction to IP addresses, MAC addresses, hostnames, wired and wireless connections, servers, VLANs, and the growing overlap between Biomed and IT.

Back to Biomed Basics

What This Page Explains

Medical equipment is not just standalone equipment anymore.

A patient monitor may talk to a central station. An ultrasound system may send images to PACS. A ventilator may send data to middleware. An infusion pump may connect to a server. A bed may talk to nurse call.

A device may need Wi-Fi, Ethernet, IP settings, certificates, servers, ports, VLANs, and IT support before it is fully useful.

That means modern biomed work is not just about fixing the box.

Sometimes the device works, but it does not communicate. Sometimes the network works, but the device is configured wrong. Sometimes IT says the network is fine. Sometimes Biomed says the device is fine. And sometimes the truth is somewhere in the middle.

This page explains basic networking for medical equipment in plain English.

The goal is not to turn every biomed into a network engineer. The goal is to help biomeds understand enough networking to troubleshoot smarter, collect better information, and work better with IT.

Jump to a Section

Why Networking Matters in Modern Medical Equipment

Years ago, a lot of medical equipment troubleshooting was local.

Did it power on? Did the buttons work? Did it measure correctly? Did it pass PM? Did the alarm sound? Did the motor move? Did the pump run?

That still matters.

But now a device can pass all of that and still be considered “not working” because it is not communicating.

Examples:

The device may be physically working, but clinically incomplete because the data is not going where it needs to go.

That is why networking matters.

Medical equipment does not just treat, monitor, measure, and alarm anymore. It communicates.

How Biomed and IT Started Overlapping

Biomed and IT used to feel more separate.

Biomed handled medical equipment. IT handled computers and networks.

That line is not as clean anymore.

A modern medical device may include:

That is where the line gets blurry.

Biomed may understand the clinical device better. IT may understand the network better. The vendor may understand the application better. Clinical staff may understand the workflow better. And the problem may require all of them.

That is the modern reality.

A good biomed does not need to know everything IT knows.

But a good biomed should understand enough to know what information matters and when to escalate.

The Simple Version

A network lets devices communicate.

For medical equipment, that communication might be between:

The network is the road system that lets medical devices send and receive information.

If the road is blocked, the device may not communicate.

If the device has the wrong address, the data may not go where it should.

If the destination server is down, the device may have nowhere to send data.

If the device is configured wrong, the network may be fine but communication still fails.

That is the basic idea.

What a Network Actually Does

A network connects devices so they can exchange information.

That information may be:

The network is not one single thing.

It may include:

So when someone says, “the network is down,” that may mean a lot of different things.

A good first question is:

What exactly is not communicating, and where is it supposed to communicate?

Wired vs Wireless Medical Devices

Some medical devices are wired. Some are wireless. Some use both.

Wired devices usually connect using an Ethernet cable.

Examples:

Common wired problems include:

Wireless devices connect through Wi-Fi or another wireless system.

Examples:

Common wireless problems include:

The device needs the right connection, the right settings, and a working destination.

IP Address Explained

An IP address is like a device’s network address.

Example:

10.25.40.123

An IP address tells the network where the device lives.

If a device has no IP address, it may not be connected properly.

If it has the wrong IP address, it may be on the wrong network.

If two devices have the same IP address, they can conflict.

If the IP address does not match the expected range for that area or system, something may be configured wrong.

Biomed does not always need to fix the IP address, but biomed should know how to find it when needed.

MAC Address Explained

A MAC address is a unique hardware address for a network interface.

It usually looks something like:

00:1A:2B:3C:4D:5E

A MAC address is like the network card’s serial number.

IT may ask for the MAC address when adding a device to the network, troubleshooting a connection, checking switch logs, or approving a device.

A device may have more than one MAC address:

If IT asks for the MAC address, make sure you are giving the correct one for the connection being used.

Hostname Explained

A hostname is the device’s network name.

Examples:

A hostname is the device’s network name tag.

Hostnames can help identify devices, locations, or systems.

But they can also cause problems if they are duplicated, incorrect, or not updated after equipment moves.

A monitor named for ICU Bed 4 that is now sitting in ED Bed 12 may confuse troubleshooting.

Names matter.

DHCP vs Static IP

Devices usually get an IP address in one of two ways.

DHCP means the network automatically gives the device an IP address.

The device asks the network for an address, and the network assigns one.

Static IP means the IP address is manually set on the device.

The device is told exactly what address to use.

Both methods are used in healthcare.

DHCP can be easier to manage, especially for mobile devices.

Static IPs can be useful for devices that need a fixed address, like servers, gateways, central stations, or certain integrations.

Common problems include:

If a device is not communicating, checking whether it has the correct IP setup is a good starting point.

Subnet, Gateway, and DNS in Plain English

Subnet tells the device what local network it belongs to.

The subnet tells the device who is in its local neighborhood.

Gateway is the path out of that local network.

The gateway is the door the device uses to reach other networks.

DNS helps convert names into IP addresses.

DNS is like a phonebook for network names.

If DNS is wrong, a device may not reach a server by name.

If the gateway is wrong, the device may talk locally but not reach systems outside its local network.

If the subnet is wrong, the device may think it is in the wrong network neighborhood.

What a Switch Port Is

A network switch connects wired devices to the network.

A wall jack usually connects back to a switch port somewhere in a network closet.

When a device is plugged into the wall, it is really connecting through:

Device → Ethernet cable → Wall jack → Building cabling → Patch panel → Switch port → Network

If the switch port is disabled, wrong, misconfigured, or assigned to the wrong VLAN, the device may not communicate.

That is why IT may ask what wall jack it is plugged into or whether the device has link lights.

What a Wall Jack Is

A wall jack is the physical network connection in the room.

Common wall jack issues include:

If a device does not communicate, try to find out:

What a VLAN Is

A VLAN is a virtual network.

A VLAN separates network traffic into different lanes.

A hospital may have different VLANs for:

A medical device may need to be on the correct VLAN to reach the correct server or system.

A device plugged into the wrong network can look like it is connected but still not communicate with the correct destination.

What a Server Connection Means

Many medical devices do not just connect to “the network.” They connect to a specific server or system.

Examples:

If the device cannot reach the server, it may show errors like:

This could be caused by the device, the network, the server, credentials, certificates, firewall rules, or configuration.

That is why the exact error matters.

What “Device Not Communicating” Can Actually Mean

“Device not communicating” is vague.

It could mean:

Do not stop at: It is not communicating.

Ask: What is it supposed to communicate with, and what part is failing?

Common Networked Medical Equipment Examples

Some devices send patient data. Some send images. Some send alarms. Some receive configuration files. Some receive drug libraries. Some only need network access for service, software, or logs.

The network need depends on the device and workflow.

Central Stations, Middleware, and EMR Connections

A device may not send data directly to the EMR.

There may be multiple systems in between.

Patient monitor → Central station/server → Middleware → EMR

Infusion pump → Pump server → Integration engine → EMR

Ventilator → Gateway/middleware → Clinical documentation system

This matters because the problem may be at any point in the chain.

If the monitor shows data locally but the central station does not show it, the issue may be between the monitor and central station.

If the central station shows data but the EMR does not, the issue may be middleware or interface-related.

If one device is failing, the issue may be local.

If every device on a unit is failing, the issue may be network, server, or system-wide.

Where does the data stop?

That question is huge.

HL7, DICOM, and Nurse Call: Different Kinds of Communication

Not all medical device communication is the same.

HL7 is commonly used for healthcare data exchange, like results, observations, admissions, orders, and patient information.

HL7 helps healthcare systems pass patient and clinical data between systems.

DICOM is commonly used for medical imaging.

DICOM helps imaging devices store, send, and manage medical images.

Nurse call is often about alerts, calls, bed exit, alarm integration, or staff notification.

Nurse call helps get the right alert to the right staff location.

A device can have network connectivity and still fail HL7. A modality can be on the network and still fail DICOM send. A bed can work mechanically and still fail nurse call output.

That is why “networked” does not mean “all communication is the same.”

Cybersecurity and Medical Devices

Medical devices are part of the hospital’s cybersecurity environment.

That means IT and security teams may care about:

This can create tension.

Biomed may say: The device needs to stay running for patient care.

IT may say: The device is a security risk.

Both may be right.

The goal is not for Biomed and IT to fight. The goal is to manage risk together.

Medical equipment has to be safe for patients and safe for the network.

What Biomeds Should Check Before Calling IT

Before escalating to IT, check the basics.

For a wired device:

For a wireless device:

You do not need to solve every network issue yourself.

But you should collect enough information that escalation is useful.

What IT May Need From Biomed

When calling IT, do not just say: The monitor is not working.

Give them useful information:

Better escalation sounds like:

Bedside monitor in ICU 12 is monitoring locally but not appearing at central station. Device is wired to jack ICU-12A. Tested with known-good Ethernet cable. Device has no IP address. Other monitors on the unit are communicating normally.

That gives IT something to work with.

Common Networking Problems in Medical Equipment

The fix depends on the cause.

That is why details matter.

Not Everything Is an IT Problem

This section matters.

Not every communication complaint is IT’s fault.

A device may fail to communicate because:

It is easy to say: Call IT.

Sometimes that is correct. But sometimes Biomed needs to check the device side first.

The best troubleshooting is not Biomed vs IT.

It is Biomed and IT narrowing the problem together.

Documentation Tips

Network-related notes should be specific.

Weak note:

Network issue. Called IT.

Better note:

Reported monitor not appearing at central station. Monitor powered on and displaying patient parameters locally. Checked Ethernet cable and wall jack connection. Tested with known-good cable. Device showed no IP address. Escalated to IT with device location, asset tag, MAC address, and wall jack number.

Another example:

Reported ultrasound unable to send images to PACS. Device connected to network and able to reach local worklist. DICOM send failed with destination error. PACS team notified with AE title, IP address, error message, and exam details.

That is much better than: Won’t send. IT notified.

For a deeper explanation of better documentation, see the Biomed Basics page on writing better work order notes using the CCR method.

Final Thoughts

Modern biomed work is not just fixing isolated boxes anymore.

Medical devices are part of bigger systems.

They connect to networks. They send data. They receive configuration. They talk to servers. They support clinical workflows. They create cybersecurity questions.

And when communication breaks, the problem may sit somewhere between the device, the network, the server, the software, the vendor, and the user workflow.

That can be frustrating.

But it also makes the work more important.

A good biomed does not need to know every networking detail.

But a good biomed should know enough to ask better questions, check the obvious things, collect useful information, and work with IT instead of just throwing the problem over the wall.

The future of biomed and IT is already overlapping.

The better we understand each other, the better we support patient care.

— Jake

Important Note

This page is an educational overview for biomedical equipment technicians, clinical engineers, students, and healthcare technology staff. Always follow your facility policy, network security requirements, manufacturer service documentation, IT procedures, cybersecurity requirements, and the requirements of your organization.

Related Biomed Basics

Back to Biomed Basics