A VNA Does Not Require Interfaces to be Changed – Understanding the Requirements that Make Up a VNA

A VNA Does Not Require Interfaces to Be Changed

The VNA has plugins that allow different applications and vendors to be connected. There should not be a need to custom-develop interfaces to various vendors. However, some vendors have peculiar implementations that might require specific information in the DICOM headers to make their workflow function optimally.

An example would be the definition of specific study or series description to match the prefetching of corresponding studies and selection of specified hanging protocols. In the absence of a true vendor neutral interface at the PACS, middleware might be needed to mitigate a vendor’s idiosyncrasies.

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

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: