Dalai has a post about PACS customization that touches on something that I have been thinking about. The current state of what vendors call customization is sadly pathetic. Changing some options is not customization. The first and most basic method of customization is being able to build completely custom UIs. This goes far beyond hanging protocols and would allow the user to alter any visual element in the PACS. The second is having an open and documented API for third party software developers to build software that runs inside or on top of the PACS. This is a toolkit for programmers. The third would be a widget like interface, something like Google IG or netvibes. This would allow power users who are not software developers but are comfortable with editing HTML or other markup languages to make addins and UI widgets.
Why would a PACS vendor ever offer such a thing? Well why does Microsoft allow anyone to write software that runs ontop of Microsoft Office? The reason is simple. Software that is built as a platform is much more valuable than a standalone application. Open source office software is not going to have trouble trying to take market share from Microsoft Office because it is not as good, but rather because vendors and organizations have built thousands of pieces of software that add value to Microsoft Office, making it much more valuable than what comes out of the box.
The first PACS vendor to treat their PACS like a platform will have a real advantage. A good platform is hard to replicate. It is a strong competitive advantage. Do I see this happening? No. PACS companies are too busy replicating each others features to think about truly changing the industry. This is one time where a company should lead its users.
Technorati Tags: radiology, software, PACS, technology