Wednesday, July 25, 2007

Getting The Right Bandwidth Configuration For Medical Imaging Applications

Medical imaging network applications are in regular use across the world today, and the capacity and topology required depends on who is deploying it (picking up the bill).

If you are building an overlay network (most likely scenario for an imaging specialist company) then go for a supplier with extensive MPLS network (gigabit backbone or higher) and usage pricing. Local Ethernet connections add a cost at each end, but the backbone charge is only for usage, so costs are very reasonable.

A Health Authority has many applications and requirements, and may be better to opt for "all you can eat" pricing on the MPLS backbone to support multiple applications including imaging, video, conferencing, voice, high priority data and generic data (email, browsing).

Appropriate COS/QOS ensures each application gets what it needs without impacting other applicatiions. Keep local firewall requirements minimal by using multiple Ethernet Ports or VLANS to distribute applications securely and seprately (Layer 2 local security is maintained in the cloud using MPLS rather than IP). Also embed Internet Access within the cloud (Internet Firewall managed by supplier or authority - according to needs).

Both overlay and one-stop-shop networks support image storage and applications hosted in the cloud - which saves tromboning data and traffic to a hub site, and reduces costs / demands on capacity.

TIP - these capacities also allow bandwidth intensive file transfer for backup, disaster recovery, distributing and manipulating large media files. A media or medical company for example could use their network for business by day, backup & DR by night.

For help in navigating the maze of decisions when assessing bandwidth requirements for medical imaging applications....I suggest using the free services from at: Bandwidth Solutions For Medical Imaging


Labels: , , , ,


Post a Comment

Links to this post:

Create a Link

<< Home