PawPacsConnect each site appropriately
A local PawPacs Node connects imaging devices to the central infrastructure through a VPN. Device types, connections and DICOM destinations are checked for each site.
PACS for multiple sites
Connect your sites. Assign access deliberately.
A clinic group needs access to the right studies even when scanning and image review happen in different places. PawPacs connects local devices to your agreed archive model with appropriate user rights.
From €250 net per PACS per month, including 1 TB of primary storage. A 14-day trial is available on request. Pricing and options
Agree the archive model first
Shared or separate PACS instances are planned around your organisation and responsibilities. Adding a site does not automatically grant it access to all data.
Plan permissions and capacity
Define which teams can see which studies and who can manage external shares. Storage, backup and support are quoted for your required scope.
Example workflow · CT
From the scan to the radiologist.
A clinic acquires a CT study. An authorised radiologist needs to review the complete series from another workstation.
An illustrative workflow using existing product features, not a customer case study. Device connectivity and required modules are checked before use.
The CT sends the study
The device transfers DICOM data directly to the agreed destination or through a local PawPacs Node with a VPN connection. The transfer path is tested together.
Find the study in the archive
The clinic checks the import and patient assignment. The explorer lets users find the study by patient, modality or date range.
Open the CT series and MPR
An authorised user opens the study in a browser, selects a series and views the slices in MPR. The PawPacs viewer and OHIF integration both connect to the same archive.
Grant access to the radiologist
A configured user account or a specific share in the optional customer-server module enables remote access. The recipient and expiry of the share are defined.
Operations & privacy
Know where your images are stored and who can access them.
- Hosting location
- Our central PACS infrastructure runs in Berlin-Tempelhof, Germany. Deployment on your own infrastructure is also possible. The locations of your instance and backups are specified in your proposal.
- Backup and recovery
- The central infrastructure has encrypted backups and a copy on a separate backup system. The customer data, capacity and retention covered by your contract are agreed separately. External backup is a separate pricing option; primary storage is not a backup.
- Access control
- Users and roles restrict access to studies. Site access and external shares are configured for your workflow. Imaging devices connect through the agreed network path.
- DPA and technical measures
- Request the data processing agreement (DPA) and technical and organisational measures (TOMs) intended for your operating model before entering into a contract. Scope, responsibilities and services are defined for your installation.
- Support
- Contact us at info@pawpacs.de. Standard and priority support, as well as bespoke on-call cover, are separate options. Contractual availability and response times depend on the support scope you select.
Check connectivity
Can your existing CT or X-ray system connect to PawPacs?
We assess connectivity with your existing imaging equipment free of charge. The manufacturer, model and intended transfer workflow are enough for an initial assessment.
You receive an assessment of the connection path and any further information needed. Setup, device licences and any data migration are quoted separately afterwards.
Please do not send patient, owner or login details. The manufacturer's DICOM conformance statement helps with the technical assessment.