Last time...
We discussed lifecycle of PACS projects. Study, Design, Execution. We saw that first two phases usually are implemented by a PACS consultant where third phase is done at last by a vendor.
I don't know my needs !
This is actually a normal case in many projects when healthcare provider doesn't have enough experience. In fact, PACS is limited by IT and storage solution of current technology. Thus, if healthcare provider is not up to date with latest and most effective technology then they may endup with unstable, or outdated technology.
Consultancy Services
In that case, people will hire another body to verify and find there needs. The body who will study your needs is called a "Consultant". There are; infact, many consultants for PACS around the world. For list of consultants for PACS and related field you can refer to
SIIM consultant list, or auntminnie.com PACS Consulting.
Hiring a consultant is too expensive..
Yes !! This is a fact. Consultancy services can cost about 10 to 15% percent of project cost ... a full implementation of PACS can cost up to 1/2 million KD. So, consultancy (study & design) can cost up to 75,000 KD.
Thus, some hospitals will do the study phase themselves. They will study there needs like archive capacity, and fetching throughput to save the expensive cost of hiring a consultant. If hospital decides to do this, they; actually, need to understand their needs first !
Understanding Your needs
It starts with understanding your needs. Very simple: Input and output, it is about the income and outcome of such system. You may never be an IT expert but you can still make the right decision. Keen on the understanding of your needs !
Your pacs vendor may keen on some state of art technology used in his system, but what if non of this works! You can always go back to internet societies to review some technology or some brand name, but there will be no one better than you in understanding your needs..
Put Needs in Writing
Good ! You have been giving thoughts and thoughts about your needs and your work throughput. Later, you started telling your choice vendor about your thoughts and you started negotiating price and might be give up on some parts of your system for the sake of budget limitations. At the end, project accomplished, system starts and then you discover that this wasn't your expectation. The system doesn't meet your requirements and the worst thing that can happen that after few years you find out that your storage archive is FULL !
The big mistake you have done was that you never put your requirements in paper. Your contract was missing the important stuff.
Honostly, in many cases contract was explicit about some requirment; however, all requirement were written in technology specific terms. For example, amount of storage in Tera bytes of storage, type of storage used, servers and H.W used, and no. of client licenses.
In fact, you should state your archive capacity only if you know how much space in Terabytes your center will consume. This is an easy calculation if you study your needs in terms of No. Modalities, Compression rate and etc. Other wise, leave this job to the other party. Of course this will cost you a lot, but I think this is a good solution until we all have a better experience and better sense for our needs.
Request for proposal (RFP)
Now, you decided to call all PACS vendors to submit their offer to supply you with PACS. The invitation letter should; in fact, contain your basic requirments. Those requirments will be your evaluation criteria to decided wich PACS you will buy. The document which will contain your initial requirments is called "Request For Proposal (RFP)" or some times it's called Terms Of Reference (TOR). Down, you can see example of two RFP templates.
1. Georgetown University Medical Center PACS/RIS RFP
2. RFP from David Clunie Website
RFP can have many requirments apart from the system; like, training requirments and integeration services. Project schedule and total period have to be stated there.
Moreover, RFP can have finanical requirments as well. Financial requirments can be some thing like your budget range, your payment policy, and contract penalties.
If you have optional requirments which you think it's good to have but not sure if this will fit in your budget then you should state them as OPTIONAL requirments. Then, you can;first , evaluate (score) all mandatory requirments and later the optional requirments.
Afterwards, vendor can put his/her proposal and then you can score each proposal since all proposals are written based on your requriments
In Summary..
PACS is a full automation solution for imaging departments. Thus, knowing your workflow, and your requirments will lead to a successful PACS implementation. However, not knowing your detailed requirments like storage capacity doesn't mean that you cannot get good PACS. You can still do that by hiring a consultant to do the job or asking vendor to adopt any new requirment which comes in the future. In either way, your requirments should be written in official documents such as RFP. The RFP lists all certain requriments you decided (or consultant decided). RFP gives good way to evaluate different vendor proposal.
Previous Articles..
1. PACS Project lifecycle
2. DICOM SOP
3. DICOM Definition and basic setup
No comments:
Post a Comment