The Spacelabs 1.4.0 adapter provides the following new features:

The Spacelabs 1.3.0 adapter provides the following new features:

• The adapter initiates a Device Inventory request to verify data integrity when it loses connection with the Spacelabs Xprezznet server. Both request failure and success lead to the generation of an audit event. (ADP-10847)
• The adapter will include location information in the audit event for the matched clinical event if the alert matches a Location Type. (ADP-10846)

The Spacelabs 1.2.1 adapter provides the following new features:

• This is a maintenance release and has no new features.

The Spacelabs 1.2.0 adapter provides the following new features:

• Vocera is pleased to announce that Spacelabs Xprezznet can now support an Xprezznet clustered server environment.
• We are also announcing that with this release a caregiver can now stop the alarm at the Xprezznet monitor.

The Spacelabs 1.1.0 adapter provides the following new features:

• This is a maintenance release only. The adapter has been versioned to work with Vocera Platform 6.3.

The Spacelabs 1.0.0.19 adapter provides the following new features:

• This is the initial release of Spacelabs Xprezznet.

The following issues are fixed in Spacelabs 1.4.0:

• There are no fixed issues in this release.

The following issues are fixed in Spacelabs 1.3.0:

• There are no fixed issues in this release.

The following issues are fixed in Spacelabs 1.2.1:

• Processing high frequency vital payloads as clinical details resulted in a slow memory leak. (ADP-10646)

  This issue has been fixed. The adapter no longer has a slow memory leak when processing vital payloads.

• When under a high volume of alert payloads from one or more devices, the adapter was backing up while processing messages, resulting in an eventual memory error. (ADP-10647)

  This issue has been fixed. The adapter now limits the maximum number of messages that will be processed for a given device when under a high frequency of alert messages for that device.

• The adapter was erroneously suppressing some alerts if they were sent at the same time (within one millisecond). (ADP-10664)

  This issue has been fixed. The adapter was using the alert name, start time, and interface ID for the Clinical ID. If alerts had the same StartDateTime, then the first alert was sent and the subsequent alerts were suppressed. The alerts generated by Xprezznet now have unique Clinical IDs by location and device.

• The adapter recreated suppressed alerts when new active alerts were received. After the adapter stores suppressed alerts, it removes them from the internal cache. If new messages were received with the same suppressed alert, the adapter erroneously stored the alert again as suppressed even though the original alert was removed from the internal cache. (ADP-10669)

  This issue has been fixed. The adapter does not store the secondary alerts as suppressed.

The following issues are fixed in Spacelabs 1.2.0:

• There were no known issues to fix in this version.

The following issues are fixed in Spacelabs 1.1.0:

• This is a maintenance release only. The adapter has been versioned to work with Vocera Platform 6.3.

The following issues are fixed in Spacelabs 1.0.0.19:

• This is the initial release of Spacelabs Xprezznet. There are no known issues.