Use a MedicalDeviceInput node
in a message flow to collect data from medical devices.
Each MedicalDeviceInput node
uses configuration information, which is stored in a configurable
service.
The configurable service defines device connections and measurement
sets. A device connection contains the connection parameters of a
medical device. A measurement set specifies the medical measurements
that are collected from a medical device. To connect a medical device
to a MedicalDeviceInput node,
you must assign a device connection and a measurement set to that
device. For more information about configurable services, see Configurable services in the IBM® Integration Bus product
documentation.
When you use
MedicalDeviceInput nodes,
be aware of the following information:
- Use each configurable service for a MedicalDeviceInput node in only
one node.
- Do not use a medical device in more than one configurable service.
- Ensure that every device you use has a unique device ID.
Device connections
A device connection defines
a connection to a medical device. The
MedicalDeviceInput node can connect
to devices that use serial port or LAN connections. A device connection
specifies the following information:
- The device type that is connected
- The device ID of the device
- The connection parameters for the device, for serial port or LAN
connections
- The measurement set used by the device
- Location, patient ID, notes, and tag information to help identify
the device connection. For an example of how to use the patient ID
field, see Healthcare: Medical Devices to EMR.
Measurements and measurement sets
A measurement
set defines the medical measurements that are collected by a device.
Measurements within a measurement set can be discrete values, alarm
alerts, or waveforms. Discrete values and alarm alerts require a polling
interval to be defined in the measurement set, which specifies how
often that measurement is collected. Waveform measurements generate
a series of discrete values at a built-in polling interval. The measurement
set used by a device is specified in the device connection for that
device. A measurement set contains the following information:
- The device type that uses the measurement set.
- Notes and tags information about the measurement set.
- A list of measurements, taken from the list of possible measurements
available to the selected device type. Each measurement contains the
following information:
- A primary ID and sub ID. These IDs are used to identify the data
that is sent from the MedicalDeviceInput node.
- Descriptions that provide more information about the measurement
and the parameter that is being measured.
- If the measurement is a discrete value or an alarm alert, it has
a polling interval, measured in seconds, which defines how frequently
the measurement is collected from the medical device.
- Notes and tag information about the measurement.
Medical device data in message flows
The
configuration of the MedicalDeviceInput node
determines the devices that are connected and the data that is collected
from those devices. When the message flow containing the MedicalDeviceInput node is deployed,
the data from the connected devices is sent from an output terminal
of the node. The data can then be processed by your message flow using
any of the nodes available in your edition of IBM Integration Bus. The measurement data is
passed into the message flow as a logical message tree that you can
filter, transform, aggregate, and route using standard IBM Integration Bus capabilities before writing
the data to an endpoint. Example endpoints include databases, IBM WebSphere®Â MQ queues, or service calls.
For
reference information about the MedicalDeviceInput node, including
information about the logical message tree and node terminals, see MedicalDeviceInput node. For more information
about developing message flow applications, see Developing message flow applications in the IBM Integration Bus product
documentation.
Medical device status messages
Medical devices
generate status messages, for example, when a device is started. Status
messages that are generated by medical devices can be viewed by the
following methods:
- By viewing the messages generated at the Status terminal of the MedicalDeviceInput node. For more
information about the format of the message generated by the Status
terminal, see MedicalDeviceInput node.
- By viewing messages in the IBM
Integration Explorer,
in the Healthcare Operational Monitoring view. For more information
about monitoring medical devices by using the Healthcare Operational Monitoring view, see Monitoring medical devices.
- By viewing messages in the local error logs. To view messages
in the local error logs, see Local error logs in the IBM Integration Bus product
documentation.
- By viewing messages in a trace. To view messages in a trace, see Trace in the IBM Integration Bus product
documentation.