Store clinical research images on PostDICOM anonymized and share them with researchers and doctors.
They can view the studies from different dates, compare the progress and create reports. Use PostDICOM API for integration with your systems. Query the studies in your PostDICOM and get information about the measurements the doctors have done on the images.
Start For Free Have Questions?PostDICOM offers Cloud PACS services with affordable pricing. Cloud based PACS is like regular PACS but with a crucial difference: its storage and features are provided by cloud-based servers.
Basically, we PostDICOM deal with the hosting, retrieval and maintenance of data for you. Upload your DICOM images and non-DICOM documents to PostDICOM. Store, view, create reports and share them with patients and doctors.
Data anonymization is the process of the protecting private or sensitive information by erasing identifiers that connect an individual to stored data. For example, name, patient id, social security number, address, phone numbers are the values that may contain protected health information.
Before uploading the images to PostDICOM, you can use the web interface to anonymize the DICOM data such as Patient Name, Patient ID, Patient Other Ids, Address, Study Description, Accession Number etc. Moreover, you can anonymize the DICOM data after the images are uploaded to PostDICOM.
You can use PostDICOM Medical Device Communicator (MeDiC) software to connect your imaging devices to PostDICOM. MeDiC software works securely behind the firewalls and it does not require any VPN connection. MeDiC software is installed to one of the computers in the clinic or hospital. When DICOM configuration is completed, you can send images from your imaging devices (CT scanner, MRI, x-ray, ultrasound, etc.) to MeDiC software. When it gets the images, MeDiC will upload the images to your PostDICOM Account automatically.
For more information, visit Medical Device Communicator (MeDiC) software.
You can create user groups and user accounts. Moreover, you can manage which users can access which clinics or hospitals and manage users' authorizations such as upload, view, merge, share, delete, etc.
Users will login to your PostDICOM account with their user name and password. They will only access the interface and functions that they are authorized.
If you have multiple clinics or hospitals in different locations, we have you covered. You can use PostDICOM as your Cloud PACS solution in your clinics or hospitals and manage all of your them in one place.
You will have one storage that can be shared between multiple locations. Moreover, you can view all patient's data in one patient folder no matter which hospital you are in.
PostDICOM Cloud API is provided as a Javascript library and it is designed in a way that it provides all of the functions needed by the Medical Companies. You can use the API to integrate PostDICOM to your existing applications and workflows.
Supported functions are uploading DICOM files, creating folders, searching, viewing and deleting patient orders. Moreover, you can automatize share link and password creation using PostDICOM Cloud API and send the links to your patients, doctors, etc.
For more information, visit PostDICOM Cloud API.
PostDICOM offers CE certified Diagnostic DICOM Viewer on top of its Cloud PACS solution.
You can access the medical images and clinical documents with our CE certified Diagnostic DICOM Viewer and create reports with ease.
You can view DICOM images using PostDICOM multi-modality DICOM Viewer. PostDICOM is equipped with advanced functions such as image processing tools such as MPR (multi-planar reconstruction), MIP (maximum intensity projection), MINIP, AVGIP and 3D rendering.
You can use standard functions like zoom, window level, pan, thickness, rotates on HTML5 zero-footprint online DICOM Viewer. Moreover, you can perform measurements such as length, density, angle and more. Our zero footprint HTML5 DICOM viewer ensures that no patient information is left on the client machine after viewing the data.
Supported operating systems and browsers are:
Windows: Google Chrome, Mozilla Firefox
Mac OS: Apple Safari, Google Chrome
Linux: Google Chrome
IOS: Apple Safari, Google Chrome
Android: Google Chrome
In a current clinical environment, patients have many supporting documents such as lab results, pathology results and consultation reports. Moreover, these documents are not in DICOM format and they cannot be stored into a standard PACS (Picture Archiving and Communication Systems). PostDICOM support storage of these type of clinical documents.
You can store documents in JPEG, BMP, AVI and MPEG formats and associate them with the corresponding patient record.
For many years, clinics and hospitals used on-premise PACS on the site. In those systems, they distribute DICOM images by burning images into CDs and distribute them by mail. Distribution of CDs is a cumbersome process, and no one knows when the recipient gets the CDs and when will the evaluation occurs. Moreover, CDs contain a basic DICOM viewer and they support only one operating system. If the CD viewer is not compatible with the operating system of the recipient, they cannot view and process the images at all.
Do not hassle with DICOM CDs. Use PostDICOM to share DICOM images, and clinical documents with patients, doctors and reporters. Create a share link with an access password, then, share them with the recipients. As soon as they have the link and the password, they can access the images immediately.
PostDICOM Cloud PACS provides reporting workflow to be used by its users. You can create report templates by modality.
At every step of the reporting workflow, orders are assigned to the responsible user and mistakes are minimized.
PostDICOM uses secure communications (SSL) internally between its servers. Also, user requests are only supported over HTTPS. Moreover, when a user logs in, a session is created and it remains active until user logs out or a timeout occurs. Only requests from valid sessions are processed by PostDICOM servers.
PostDICOM uses AES 256 encryption by default. When user data reaches to PostDICOM, servers first encrypt data with AES 256 and then stores them on Microsoft Azure storage of that region.
All of the users have to use strong passwords for their accounts. Passwords must be at least 8 characters long and must contain at least one uppercase, one lowercase and one special character. This is enforced by PostDICOM password set up policy. Also, PostDICOM supports Two Factor Authentication (2FA) and users can use Two Factor Authentication (2FA).
USD
per month.