Skip to content
UnoPACS

PACS integrations

Connect the systems your practice already uses.

Start with your image sources and patient records. We work through the connection to UnoPACS, the information that accompanies each study and how your team will access the result.

Discuss your integration Explore the study inbox
01 / DICOM How your sources connect to UnoPACS

Your practice network

Imaging devices DICOM
Cloud Connector Unomed
Connection to the cloud
UnoPACS

Archive · study inbox · viewer

Existing PACS / patient-record system UnoPACS
Connection overview. We confirm the interfaces and rollout scope with your team.

Cloud Connector

The connection, visible in your settings.

  • DICOM image sources
  • Existing PACS workflows
  • Connection requirements up front
Original Unomed components · example data · English interface

Original Unomed components · example data · English interface

Original Unomed Cloud Connector settings with example connection details and connection status.

From source to record

Map the route before connecting.

A useful integration starts with a clear picture of where the data comes from and who needs it.

  1. Identify the sources

    List your modalities, existing PACS and external imaging partners. Include the system versions and the way studies are sent today.

  2. Connect and receive

    DICOM-capable equipment can use a connector in the practice network. We confirm the required routing, network access and interfaces for the proposed connection.

  3. Verify the workflow

    Check a representative study from delivery through patient assignment to browser access. Agree who handles exceptions and how the team gets support.

Existing PACS / patient-record system

Define what each connection needs to do.

Supporting a standard does not by itself establish compatibility with every system. We confirm the specific data flow and configuration before rollout.

Modalities and DICOM
Review how your imaging equipment sends studies, which patient identifiers accompany them and where a local connector will run.
Existing PACS
UnoPACS can complement an archive you already use for receiving external studies, browser access and sharing. Replacing the archive is a separate decision.
Patient records and APIs
Discuss patient context, orders and opening images from your record system. Ask which DICOMweb, HL7 or API interfaces are available for your particular workflow.

Questions

What to bring to an integration review

A short list of systems is enough to begin.

What needs to be installed locally?

The viewer runs in the browser. Connecting traditional DICOM equipment can require a connector installed once within the practice network; its requirements are reviewed during setup.

Do you support our EHR or practice-management system?

Send us the vendor, product name and version, together with the workflow you need. We will confirm the supported connection and any configuration or additional work required.

Can we keep historical studies in our current PACS?

Keeping the existing archive can be part of the setup. Access to historical studies, any transfer and the system responsible for each part of the workflow are agreed during the review.

How long does implementation take?

It depends on the number of sources, network configuration, partner coordination and any archive transfer. We agree the scope and rollout steps after reviewing those dependencies.

Plan the next part of your setup

UnoPACS

Start with your system list.

Tell us the modalities, PACS and patient-record system you use. We will work through a proposed connection with you.

Arrange an integration review