Picture Archiving and Communication System (PACS) consist of electronic, mechanic and software components.

Each component has different life span, and sooner or later one of them will stop functioning. Then, you will face the hard reality of loosing your patient records, forever.

Do not wait for the failure occur. Prepare a backup and recovery plan. Then, take action immediately.

Integrate your Hospital Information System (HIS), Radiology Information System (RIS) or Electronic Health Record (EHR) to the PostDICOM Cloud.

Some of the integration points are:
HL7 ADT (Admit Discharge Transfer) messages.
HL7 ORM (Order Management) messages.
HL7 IAN (Instance Available Notification) messages
HL7 ORU (Observation Result) message
Opening patient images

View DICOM images and clinical documents with easy to use zero-footprint HTML5 DICOM viewer. It works on internet browsers, and you do not need to install any on your hardware. When you finished viewing the images, close your Internet Browser. No patient data is left on client machine after usage.

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

PostDICOM Cloud PACS provides reporting workflow to be used by its users.

At every step of the reporting workflow, orders are assigned to the responsible user and mistakes are minimized.

PostDICOM operates on six different regions and ten different locations. These are as follows.

European Union - Frankfurt (GE), Paris (FR)
United Kingdom - London (UK)
United States of America - Washington DC (USA), San Francisco (USA)
Canada - Montreal (CA)
Asia & Pacific - Singapore (SG), Sydney (AU), Mumbai (IN)
South America - Sao Paulo (BR)

Each region works isolated from each other and patient data (DICOM images, clinical documents, and patient information in the database) are stored only on that region. They are not replicated to other PostDICOM regions.

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.

Supported functions are uploading DICOM files, creating folders, searching, viewing and deleting patient orders.

PostDICOM's top priority is secure storage and secure retrieval of the patient data. We provide following security measures to ensure data is safe at all times.

Session and Data Transfer Security: 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.

Encryption: PostDICOM uses AES 256 encryption by default. When user data reaches to PostDICOM, it is encrypted using AES 256 and then stored them on Amazon Web Services S3 storage.

Password Policy: All of the users have to use strong passwords for their accounts. Passwords must be at least 6 characters long and must contain at least one uppercase, one lowercase and one special character. This is enforced by PostDICOM password set up policy.

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, referring 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.