Selectively routing patient data between field devices and treatment center destinations

A non-transitory computer-readable medium comprising instructions that cause a programmable processor of a server to:

• receive, at the server located remotely from a plurality of medical devices, medical event data from at least one of the plurality of medical devices, wherein the plurality of medical devices at least one of monitors or treats a patient outside of a patient treatment center, wherein the medical event data comprises physiological data of the patient;
• maintain, by the server, event data filtering rules for a plurality of destinations used by the server for determining whether the medical event data received from the at least one of the plurality of medical devices is routed to a destination of the plurality of destinations, wherein each destination of the plurality of destinations is associated with one of a plurality of patient treatment centers, wherein the event data filtering rules specify qualifications of a type of data that an associated destination should receive;
• determine a data type of the physiological data included within the medical event data;
• make a comparison of the medical event data to historical medical event data for the patient retrieved from a patient data server;
• based on the comparison, determine whether the patient has a particular physiological condition;
• based on (i) whether the patient has the particular physiological condition and (ii) on the determined data type, determine to which of the plurality of patient treatment centers the patient may be taken;
• for the plurality of patient treatment centers to which the patient may be taken, apply the event data filtering rules to determine to which destinations to route the medical event data;
• and
• route the medical event data from the at least one of the plurality of medical devices to the determined destinations.

A system comprising:

• a server including a processor;
• memory storing instructions executable by the processor to perform functions comprising:
• receiving, at the server located remotely from a plurality of medical devices, medical event data from at least one of the plurality of medical devices, wherein the plurality of medical devices at least one of monitors or treats a patient outside of a patient treatment center, wherein the medical event data comprises physiological data of the patient;
• maintaining, by the server, event data filtering rules for a plurality of destinations used by the server for determining whether the medical event data received from the at least one of the plurality of medical devices is routed to a destination of the plurality of destinations, wherein each destination of the plurality of destinations is associated with one of a plurality of patient treatment centers, wherein the event data filtering rules specify qualifications of a type of data that an associated destination should receive;
• determining a data type of the physiological data included within the medical event data;
• making a comparison of the medical event data to historical medical event data for the patient retrieved from a patient data server;
• based on the comparison, determining whether the patient has a particular physiological condition;
• based on (i) whether the patient has the particular physiological condition and (ii) on the determined data type, determining to which of the plurality of patient treatment centers the patient may be taken;
• for the plurality of patient treatment centers to which the patient may be taken, applying the event data filtering rules to determine to which destinations to route the medical event data;
• and
• routing the medical event data from the at least one of the plurality of medical devices to the determined destinations.