UK Imaging Informatics Group
Updating AEs and IPs - frustratiions PreviousNext
UK Imaging Informatics Group > Questions & Answers > PACS Integration & Standards >
Message/Author
 Link to this message Mike Smith  posted on Tuesday, December 03, 2002 - 10:30 am Edit Post Delete Post Print Post
Every time we install a new piece of DICOM compliant imaging kit, we typically want to enable links to at least two or three other DICOM devices (e.g. printers, workstations). This requires each modality to be set up with the AE titles etc. of the linked devices. I find this is becoming an increasingly frustrating and time- consuming exercise, primarily because the majority of equipment vendors will not allow end users to configure their equipment. Therefore a 20 minute job becomes a major organisational hassle, contacting and coordinating engineers. I wondered if anyone else has the same problem? Has anyone come to a "special" arrangement with manufacturers to allow on-site configuration? Is there anything in DICOM like a "DNS server" which maintains a central database of devices and connections?
Mike
 Link to this message  D S Martin  posted on Wednesday, December 04, 2002 - 09:41 am Edit Post Delete Post Print Post
Perhaps we have been lucky in respect of our suppliers in Nuclear Medicine (SMV/GE ADAC/Philips) but all configurations to add AE titles etc are possible by the user. I have however heard of this being an issue with some manufacturers and in some cases high charges have been made. Perhaps we should bear this in mind when writing specifications for new equipment and / or maintenance contracts and specify full user access to change these parameters?
 Link to this message  D S Martin  posted on Wednesday, December 04, 2002 - 09:52 am Edit Post Delete Post Print Post
Perhaps we have been lucky in respect of our suppliers in Nuclear Medicine (SMV/GE ADAC/Philips) but all configurations to add AE titles etc are possible by the user. I have however heard of this being an issue with some manufacturers and in some cases high charges have been made. Perhaps we should bear this in mind when writing specifications for new equipment and / or maintenance contracts and specify full user access to change these parameters?
 Link to this message Michael Sparks  posted on Wednesday, December 04, 2002 - 04:18 pm Edit Post Delete Post Print Post
Our in house engineers do all of this themselves. Where possible all first line maintenance is done in house. The only manufacturer who has been a tad diffident about letting us fiddle with the configuration files is IGE but after persistent badgering we are graciously allowed to modify the settings. Usually a single phone call for advice is required when we get stuck. Most manufacturers run courses on their equipment and we regularly send our engineers on these when we buy new stuff. They prefer Philips and really enjoy their trips to Holland.
 Link to this message Michael Sparks  posted on Thursday, December 05, 2002 - 07:55 am Edit Post Delete Post Print Post
Yes - we have. Our in house engineers configure all the equipment themselves. Sometimes they have to contact the manufacturers if there are problems but mostly can solve it with a simple phone call. Part of our requirements in any tendering exercise is that serious pressure is put on the manufacturer to agree to allow first line maintenance to be carried out by our own engineers and that they be allowed on the manufacturers training courses. Obviously we usually have to fund these courses but they do quite enjoy the trips to Holland! We have always employed two engineers locally because of our locality - response time of some of the manufacturers is not good enough. IGE are the one company that have been reluctant to allow us into their systems but with some badgering we have managed to get access to the Advantage Windows and MRI workstation to configure our network.
 
Add Your Message Here
Post:
Username: Posting Information:
This is a private posting area. Only registered users may post messages here.
Password:
Options: Automatically activate URLs in message
Action: