Z-1191-2012

Microsoft Amalga UIS 2009 is Microsoft Amalga Unified Intelligence System (UIS), Calculator/data processing...

Name: Z-1191-2012 Microsoft Amalga UIS 2009 is Microsoft Amalga Unified Intelligence System (UIS), Calculator/data processing...
Creator: Microsoft Corporation Health Solutions Group
Published: 2012-01-11
License: https://open.fda.gov/license/

Microsoft Corporation Health Solutions Group / initiated 2012-01-11 / Terminated / root cause: software

FDA source

Microsoft Corporation Health Solutions Group began a recall of Microsoft Amalga UIS 2009 is Microsoft Amalga Unified Intelligence System (UIS), Calculator/data processing module, for clinical use. Microsoft Amalga UIS 2009... on 2012-01-11. The reason FDA records is "The problem occurs when a user filters the data in Amalga datagrid to exclude specific values. If the field specified in the filter criteria contains NULL values, the filtering will exclude those records as well". As of 2026-09-10, the recall status on record is Terminated, and MDM tags the root cause as software.

Recall record

Recall number: Z-1191-2012
Status: Terminated
Initiated: 2012-01-11
Posted: 2012-03-08
Terminated: 2012-12-12
Recalling firm: Microsoft Corporation Health Solutions Group
Product: Microsoft Amalga UIS 2009 is Microsoft Amalga Unified Intelligence System (UIS), Calculator/data processing module, for clinical use. Microsoft Amalga UIS 2009 enables healthcare providers to create a comprehensive continually updated data ecosystem to aggregate, store, display, and share disparate data either coming from many source systems or directly entered by end users for rapid self-service data exploration and analysis by front line managers, clinicians and ancillary staff. Furthermore, Amalga UIS allows healthcare providers to rapidly create new applications to respond to evolving business and clinical needs.
Product code: JQP Calculator/Data Processing Module, For Clinical Use
Reason for recall: The problem occurs when a user filters the data in Amalga datagrid to exclude specific values. If the field specified in the filter criteria contains NULL values, the filtering will exclude those records as well.
Root cause tag: software
FDA root cause: Software design
Action: Microsoft Corporation Health Solutions Group sent a "Urgent Field Safety Notice" email dated January 19, 2012, to all affected customers. Notification of customers in China is still pending due to the Chinese New Year Holiday. Customers were instructed to : 1. If the user notices varying row counts or inconsistent values in a given column and they are using the exclude filter, they may have to look for alternative ways to filter the data that do not use the above mentioned filter conditions. 2. To avoid the indicated issue in your implementation there are two steps to be taken: a. Ensure that all parsers are inserting empty strings () rather than NULL when ingesting data into the system and b. Identify all Baseview definitions (i.e. the sql view that a baseview is accessing) that include an outer join and update those definitions to include the ISNULL replacement function [e.g. ISNULL( column_name, )] on any columns which may return NULL due to a non-matching row in the outer join tab As of January 23, 2012 The firm's members of Services Team have spoken by phone with representative of every customer. Customers should call 425-882-8080 for any questions about this recall.
Quantity in commerce: 28 units
Distribution: Worldwide Distribution -- USA (nationwide) including the states of AR, CA, KY, HI, FL, MA, MD, MN, NC, NJ, NY, WA, WI and countries China, Switzerland, and United Kingdom.
Product codes and lots: 2009; R2; R2 SP1; R2 SP2, R2 SP3, RTM.

Product code JQP

The FDA recall record names no cleared device, and no clearance has been matched to it.

MDM coverage of this record lists here, newest first.

About this record

Sourced from the FDA device recall database and the FDA enforcement reports, both ingested from openFDA. The recall record supplies the product, the reason and the product code; the enforcement report supplies the classification. The two datasets are exported by FDA on different days, and the date above is the older of the two, so nothing on this page is newer than it says.

MDM adds the root cause tag, derived from FDA’s own root cause text, and the cross-links to the product code, the clearances named on the record and MDM coverage. Where a recall has not been joined to an enforcement report, no classification is shown.

Data as of 2026-09-30, the FDA export date for this dataset. Page last changed 2026-09-05. View this recall on fda.gov (opens on fda.gov)