• Decrease font size
  • Return font size to normal
  • Increase font size
U.S. Department of Health and Human Services

MAUDE Adverse Event Report: MERGE HEALTHCARE ICONNECT ACCESS; PICTURE ARCHIVING AND COMMUNICATIONS SYSTEMS AND WORKSTATIONS

  • Print
  • Share
  • E-mail
-
Super Search Devices@FDA
510(k) | DeNovo | Registration & Listing | Adverse Events | Recalls | PMA | HDE | Classification | Standards
CFR Title 21 | Radiation-Emitting Products | X-Ray Assembler | Medsun Reports | CLIA | TPLC
 

MERGE HEALTHCARE ICONNECT ACCESS; PICTURE ARCHIVING AND COMMUNICATIONS SYSTEMS AND WORKSTATIONS Back to Search Results
Model Number 8.2
Device Problems Application Program Problem: Parameter Calculation Error (1449); Defective Component (2292)
Patient Problem No Clinical Signs, Symptoms or Conditions (4582)
Event Date 02/09/2022
Event Type  malfunction  
Manufacturer Narrative
Merge healthcare investigated the issue identified by an iconnect access software component supplier, (b)(4).(b)(4) requirement to check for square or equal x and y pixels, prior to rendering dicom compliant 3d image datasets, was not fully implemented in their software toolkit.(b)(4) performed their own investigation and did not find any customer/user complaints for non-square pixels in 3d rendered images over the past 18 years.(b)(4) searched their image database, amassed over 18 years, and did not find a single 3d renderable dataset with non-square pixels.Merge healthcare analyzed over 12 years of service records and complaints and was unable to find a single instance of a customer or user with an issue related to 3d images with non-square pixels.Merge healthcare also analyzed internal imaging databases and could not find any 3d renderable datasets with non-square pixels.(b)(4) complainant identified the missing requirement by using a non-square pixel 3d renderable dataset that was mathematically manipulated.Between (b)(4) and merge healthcare, neither company could find any real-world clinical/medical 3d renderable imaging datasets with non-square pixels.While there is a potential of non-square 3d renderable images existing in the field for ct, mr, pt and a few other imaging dataset types, no actual real-world evidence was found.Research into medical imaging design and standards also indicated that non-square x,y pixels in 3d dicom compliant image datasets is atypical.If real-world medical imaging 3d datasets with non-square pixels were generated in the viewer, there is a potential that diagnostic or treatment decisions may be inaccurate due to image distortion or incorrect measurements.Neither (b)(4) or merge healthcare have had any allegations from users indicating or alleging that patients were injured or harmed due to diagnostic or treatment decisions being made in the 3d viewer.Clinicians may render images in 3d for improved visualization of the patient's anatomy or a specific region of interest (roi).However, standard clinical practice is to measure a patient's anatomy or regions of interest in 2d.Merge healthcare's resolution for the missing (b)(4) requirement is to add a screening check to iconnect access.This check will prevent dicom compliant 3d image datasets with non-square x,y pixels from being rendered for viewing in (b)(4) tooklit.No further action is indicated.
 
Event Description
The ibm iconnect access application provides internet access to multi-modality softcopy medical images, reports, and other patient-related information to conduct diagnostic review, planning and reporting through the interactive display and manipulation of medical data.Ibm iconnect access provides healthcare professional tools to aid in interpreting medical images.On 1/11/2022, merge healthcare received an email notification from an approved supplier, (b)(4).(b)(4) provides a 3d medical imaging software toolkit that is used with iconnect access to render dicom compliant 3d images for viewing.The email provided information regarding a requirement that was not fully implemented within (b)(4) 3d medical imaging toolkit.The requirement is that: x and y pixel spacing must be equal for data loaded into 3d image rendering engines.Per (b)(4), "although cross sectional 3d imaging data almost always has equal x & y spacing as additional assurance, and to protect from the rare events they are not equal, our next release of the sdk will now not allow this data to load into 3d render engines (2d render engines will continue to support it)." merge healthcare has received no complaints from customers or users of iconnect access regarding the rendering of non-square x,y pixel 3d images.Merge healthcare, in conversations with (b)(4), learned that the missing requirement was identified by a customer/oem that uses (b)(4) 3d imaging toolkit.This customer was doing research and development (r&d) on a feature unrelated to 3d image rendering.To perform their r&d activities, (b)(4) customer created a derived mathematical phantom dataset.When this mathematically manipulated image dataset was rendered in (b)(4) 3d viewer, the image was observed to be out of proportion.There is a potential that diagnostic or treatment decisions made from 3d images with unequal or non-square x,y pixels may be incorrect due to image distortion & inaccurate measurements.There are no reports of patient injury or harm as a result of this issue.Reference complaint (b)(4).
 
Search Alerts/Recalls

  New Search  |  Submit an Adverse Event Report

Brand Name
ICONNECT ACCESS
Type of Device
PICTURE ARCHIVING AND COMMUNICATIONS SYSTEMS AND WORKSTATIONS
Manufacturer (Section D)
MERGE HEALTHCARE
900 walnut ridge dr
hartland WI 53029
Manufacturer (Section G)
MERGE HEALTHCARE
900 walnut ridge drive
hartland WI 53029
Manufacturer Contact
brian bell
75 binney street
cambridge, MA 02142-1123
3123540189
MDR Report Key13502374
MDR Text Key293281890
Report Number2183926-2022-00002
Device Sequence Number1
Product Code LLZ
UDI-Device Identifier00842000101017
UDI-Public(01)00842000101017(10)8.2(11)211027
Combination Product (y/n)N
Reporter Country CodeUS
PMA/PMN Number
K203104
Number of Events Reported1
Summary Report (Y/N)N
Report Source Manufacturer
Source Type Other,Company Representative
Reporter Occupation Non-Healthcare Professional
Type of Report Initial
Report Date 02/09/2022
1 Device was Involved in the Event
1 Patient was Involved in the Event
Date FDA Received02/09/2022
Is this an Adverse Event Report? No
Is this a Product Problem Report? Yes
Device Model Number8.2
Was Device Available for Evaluation? Yes
Date Manufacturer Received01/11/2022
Was Device Evaluated by Manufacturer? Yes
Date Device Manufactured11/16/2021
Is the Device Single Use? No
Is This a Reprocessed and Reused Single-Use Device? No
Type of Device Usage Reuse
Patient Sequence Number1
-
-