Most infusion pump manufacturers have all released integration gateways to take pump messages upstream and push things like drug libraries downstream, and also push infusion events upstream for hospital systems and billing records etc.
AT the point of this integration gateways, it is not deeply difficult to push alarm messages to a central console ( i.e. at a nurses station) [this company I worked with had developed a Nurse console application to display ward level infusion pump data and alarms]
HL7 is probably not the solution at the level of alarms, too heavy and not a precise standard.
NIST and the FDA released a vast best practice document several years regards infusion pumps and security and yes, they should be on a protected subnet etc .....
There are no alarm standards and a hierarchy of alarms as far as I am aware. Manufacturers try to capture events on the pump and issue alarms but there needs to be a vast body of work to standardise alarms in hospitals.
The FDA requirements for an infusion Pump and it's hardware alarms are harder to meet than a Medical software standard. It is about risk. In reference to the alarm centralisation software, it was shipped as an advisory to the actual physical pump alarm, if it supersedes a pump alarm, then the cost of having the software accepted by the FDA goes up by a lot.
There is no standard to the message protocols issues by devices ..... every manufacturor creates their own, either a serial protocol, or maybe something like MQTT carrying device specific data upstream to a device driver at an integration framework.
HL7 does help in terms of defining how you locate where the pump is .....