A VNA Does Not Require Data Migration or Conversion – The Requirements that Make Up a VNA #HealthcareIT

A VNA Does Not Require Data Migration or Conversion

Data migration when exchanging PACS vendors has become a major expense, requiring significant resources and delaying new PACS implementations. Migrating data to a format that might have to be migrated again in a couple of years does not make sense. A much better choice would be to migrate it once to an open and widely supported standard.

Of course, this does not mean that the actual objects would stay on the same physical media forever. As hardware storage technology improves, data might still be moved. However, the data formats would not change and there would be no disruption of the image availability.

The same applies for storage software technologies, improvements to support different database technologies, and virtual storage architectures. Again, the latter should not impact the image availability and might be done to improve performance and cost rather than a forced, costly migration because of vendor changes.

  • Data migration has become a major expense
  • Migrating data once to an open and widely supported standard is ideal
  • As technology and storage capabilities improve, the data should be able to be migrated easily

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: