BEAM by OneMedNet: Secure Exchange Made Simple™

Frequently Asked Questions

What is BEAM?

BEAM is an electronic medical information exchange delivering:

  • Secure transmission of medical information worldwide
  • Interoperability with existing PACS solutions
  • Permission-based access control workflow
  • Demographics, MRN and accession number reconciliation
  • HIPAA and Joint Commission audit compliance
  • Timely, efficient, and appropriate patient care

What is unique about BEAM?

BEAM is much better than other study exchange solutions in many ways:

  • Patented peer-to-peer, web-based technology
  • No VPN infrastructure required
  • Secure network connections established only “as needed”
  • Central servers manage and log network transaction activity
  • Data encryption, secure conduit, and key authorization
  • Images are stored directly into PACS

Are the transfers secure?

Transfers are 100% secure. Connections and study data are fully encrypted during transfer. File transfer connections are peer-to-peer and only established for the duration of an authorized transfer. Participating sites are provided a unique, revolving key for network authentication. In addition:

  • No direct, uncontrolled access of one PACS to another
  • Granular control of access for each study with permission-based protocols
  • The connection between facilities is created only when needed and only for approved transfers
  • No persistent open pipes (aka VPN)

Does BEAM store or retain a copy of the transferred study?

BEAM customers transfer studies peer-to-peer, so study images travel directly from one site to another, thereby avoiding any storage of the images on BEAM’s central servers.  With BEAM, customers utilize their existing investments in their primary PACS for storage and display.  BEAM’s direct transfer technology allows customers to avoid:

  • The added risk and complexity of multiple storage and viewing locations.
  • The added burden of increased control and oversight of PHI on 3rd party systems.
  • The added cost of external storage.

Do I need hardware?

No. Although BEAM is available on different hardware platforms (such as a 1U server), BEAM is also available for deployment in a virtual environment such as VMware or Microsoft’s Hyper-V.

Can I download BEAM?

Yes. BEAM is available for download to run on a virtual environment such as VMware or Microsoft’s Hyper-V.

What are the client’s minimum system requirements?

The BEAM UI can be accessed from a browser on any computer in your facility and no additional software is required to access the BEAM UI.  To obtain the best experience the following are the configurations we’ve tested and approved to-date:

  • Browser: IE Explorer 6+, FireFox 3+ or Safari (the most recent browsers provide the best user experience)
  • Operating system: Any system capable of running the above browsers in Windows, Linux, Mac, etc. systems
  • Hardware: 1 Ghz CPU, 512 MB RAM and 1024 x 768 resolution monitor
  • Network: 100 Mbps internal network
  • Firewall: Access to port 443 to and from the BEAM client

Does BEAM help me comply with HIPAA?

BEAM includes the following features to help you comply with HIPAA:

  • Authorized, authenticated, encrypted, and validated data transfers
  • Peer to peer transfer eliminates exposure of data residing in the cloud
  • Audit trails and transfer logs
  • User authentication, access controls, auto-logoff and reports
  • Secured, tamper resistant appliance protected from malicious software
  • Fault tolerance and fast recovery in the event of outages

How does BEAM protect PHI?

BEAM does not store or display imaging data. BEAM only allows users access to patient demographic information for patient matching and study identification. Only the basic information necessary to identify transactions is retained in BEAM for audit logs and billing purposes. All PHI is fully encrypted by BEAM during transfers.

How much does BEAM cost?

BEAM’s cost varies based on equipment selected and subscription volume.  Please contact us for more details, but to give you a general idea, customers can choose between a ‘pay as you go’ fee per transaction model or a pre-paid, volume-based transaction model.  Customers can also choose between free software download or hardware equipment.  Initial training is included at no charge and all technical support and upgrades are included with the subscription.

Does BEAM transfer full resolution images?

Yes. BEAM pulls the full resolution images from the source PACS and transmits them to the destination PACS without loss of quality or altering the original image content. The image quality is the same on the receiving side as on the send side. The DICOM images do not undergo any loss due to compression and arrive at the destination with full fidelity.

With the concerns about the open accessibility of DICOM, how is my PACS system secure from “spying” (open queries) by another facility’s PACS?

Unlike standard VPN connections using DICOM, BEAM does not allow for open queries to your PACS database from outside entities. BEAM was specifically designed to preclude unauthorized access to your data. BEAM addresses this issue by allowing only authorized access utilizing permission-based protocols for specific patient exam requests and approved access.

How does BEAM reconcile Patient IDs?

BEAM assists in patient ID reconciliation by querying the respective local PACS database to correctly identify or propose matches to the target patient. Once the correct patient is selected, BEAM automatically substitutes the appropriate patient ID of the receiving institution during the transfer.

How long does it take to send a study?

Transfer times will depend upon several factors such as available bandwidth between both facilities, the number of images and the size of each individual image object. The key advantage to BEAM is that transfers occur directly between two sites, unlike cloud transfers where studies are first uploaded to the cloud and then downloaded from the cloud, which takes at least twice as long. BEAM’s direct transfer technology makes it ideally suited for trauma transfer.

What technical resources are required for implementation?

Installation and configuration of the BEAM client is very simple.  Your PACS will need to be configured to allow DICOM connectivity from the BEAM appliance.  If you install BEAM in a data center, then BEAM will need access to the Internet and the PACS, and end users will need access to BEAM’s UI via a browser.