Skip to content

Public FDA record

Z-1638-2016: Ascom Mobile Monitoring Gateway (versions 4.1.1 and 4.2.0) and Ascom Unite Connect for Nurse Call (versio

Recall record Z-1638-2016 for Ascom US, INC.. View source facts, labeled dates, and the original FDA record.

FDA identifier
Z-1638-2016
Company in FDA record
Ascom US, INC.
FDA record creation date
May 10, 2016
First observed by MedTech Watch
Nov 16, 2026
Latest observed content change
Nov 16, 2026
Recall classification
Class II

Reason stated in the source

Due to a malfunction of software, the secondary module will not automatically take over messaging if the primary module fails after a software upgrade to one of the other affected versions. Messages from GE Carescape/Nurse Call will not forward to handset until primary module is restored.

Source facts

Action
On January 4, 2016 , the firm is initiating a field corrective action to update the software in the installed base and resynchronize the primary and secondary servers. All customers were sent a letter January 4, 2016, informing them of the voluntary recall of Ascom Mobile Monitoring Gateway and Unite Connect for Nurse Call. The reason stated for why the recall was initiated was that the secondary module would not take over the messaging function when the primary module failed, following a software upgrade. Ascom instructed customers to check if their software was one of the affected versions they should contact their local Ascom representative to review the MMG configuration and determine if the system is subject to malfunction. The same instructions were directed towards those who were not able to determine their software version. If it is determined that the program is subject to malfunction, the primary and secondary modules should be re-synchronized. A test of module redundancy should be conducted on re-synchronized modules. The second module should take over for the primary module within thirty seconds. Model redundancy should be tested frequently and following system upgrades. For more information call (919) 535-6143 , 8am till 4:30pm.
Initiated
2015-12-10
Root cause
Software design
Terminated
2017-10-13
Distribution
CA, CT, FL, IA, ID, IL, IN, KY, LA, MA, MD, ME, MI, MO, NJ, NM, OH, OK, PA, TN, TX, VA, WA, WI and Hawaii. Australia, Austria, Belgium, Canada, France, Germany, Netherlands, Poland, Qatar, Sweden, Switzerland, and United Arab Emirates.
Recall number
Z-1638-2016
Recall status
Terminated
CDRH record ID
144525
FDA record created
2016-05-10
Recall event number
73578

Source facts and excerpts are reproduced for research. Dates retain their source meanings. “First observed” describes collection, not FDA publication or product launch.

Recall classification is supplied only when the recall number matches an enforcement record. Recall class and device class are different fields. Several recall records may belong to one recall event.

Useful context

Device classifications

FDA dataset:

Last successful check: Nov 22, 2026

Source classifications may change.

510(k) clearances

FDA dataset:

Last successful check: Nov 22, 2026

FDA publishes this dataset monthly.

Recall records

FDA dataset:

Last successful check: Nov 22, 2026

FDA publishes this dataset weekly.

Keep this research moving.

Follow ten competitors and ten product codes. Get matching changes in your dashboard and a weekly brief, for $49/month.

Start a 14-day free trial ↗