Once a backup strategy and infrastructure are in place, a VNA is ready to be installed. Due to certain requirements that their systems may have to meet, not every PACS vendor is ready to connect to a VNA. Some of those requirements may include:
- The PACS archive needs to be able to hand-off the responsibility for storage to the VNA. This requires that a storage commitment request be initiated. Unfortunately most PACS only implement SCP, assuming that their archive will be the final and long-term storage provider.
- If there are any changes in patient demographics, the study information has to be exchanged between the PACS and the VNA.
- A PACS typically has a workflow manager that keeps track of the study status, like whether it is read, completed or unread. Pre-fetched studies from the VNA have to be identified as completed or read, or they could end up on the unread work list.
- Image deletions have to be coordinated between the PACS and VNA and there should be an aging process for images after a configurable amount of time.
For more information about developing a Vendor Neutral Architecture, the VNA Institute of Technology, or to enroll for CPHIMS (CE) Continuing Education Hours, visit http://www.vnait.org.For information about TeraMedica, visit: http://www.teramedica.com