A JavaScript Cloud API, DICOMweb endpoints (STOW-RS, WADO-RS, QIDO-RS), and FHIR support give your HIS, RIS, EHR, or custom application a complete medical imaging backend — without building one from scratch.
Card required for verification. No charges today. Cancel anytime during your trial. Auto-renews unless cancelled.
Trusted Global Compliance & Medical Certifications
Who Uses PostDICOM Integrations
Any organisation that manages DICOM imaging data can connect PostDICOM to their existing systems via the JavaScript Cloud API or DICOMweb endpoints — including HIS and RIS vendors, hospital IT teams, telehealth platforms, healthcare software developers, clinical research platforms, and large multi-site healthcare groups.
Software companies building hospital information, radiology information, or electronic health record systems. Embed PostDICOM into your platform via the JavaScript API or DICOMweb to give your users a full cloud PACS and CE-certified diagnostic viewer without building one from scratch.
IT teams connecting PostDICOM to an existing HIS or RIS via the JavaScript Cloud API. PostDICOM receives patient demographics and orders from your HIS through API calls, routes completed studies back, and delivers worklists to DICOM modalities — without requiring changes to the imaging devices.
Platforms delivering remote consultations, second opinions, or chronic disease management that need to incorporate DICOM imaging. Use the PostDICOM JavaScript API to embed the zero-footprint viewer inside your patient or clinician portal — no plugin, no download, no redirect.
Independent developers and agencies building custom applications for healthcare clients. The PostDICOM Cloud API handles study upload, patient order management, folder organisation, share link generation, and permission management — so your application handles the clinical workflow while PostDICOM handles the imaging backend.
Research platforms that collect medical imaging data across multiple sites and investigators. Use the DICOMweb STOW-RS endpoint to push studies from any DICOM source, QIDO-RS to query studies by patient, modality, or date, and the API to anonymise and route studies to investigator accounts.
Healthcare organisations with multiple facilities that need automated study routing and programmatic share link distribution to patients and referring clinicians. The API supports bulk operations so every study reaching PostDICOM can trigger automated downstream actions without manual steps.
Integration Capabilities
PostDICOM supports DICOMweb (STOW-RS, WADO-RS, QIDO-RS), FHIR endpoints, DICOM Modality Worklist, and a JavaScript Cloud API — covering every major protocol used in HIS, RIS, EHR, and modality integration today.
A browser- and server-compatible JavaScript library covering the full lifecycle of a study: upload DICOM and clinical documents, create and manage patient orders, organise studies into folders, generate viewer links, assign orders to users, move studies between locations, and set access flags — all from a single authenticated API client.
Full DICOMweb standard support. Push studies from any DICOM-compliant system using STOW-RS multipart POST requests. Query at study, series, or instance level via QIDO-RS with parameters including Patient ID, Study Instance UID, accession number, modality, and date range. Retrieve individual instances or full studies via WADO-RS.
FHIR-enabled endpoints allow PostDICOM to participate in FHIR-based workflows alongside your EHR. Share imaging results and study metadata with FHIR-compliant downstream systems. Contact PostDICOM to discuss your specific FHIR implementation requirements — endpoint scope and version can be aligned to your integration.
Deliver worklists to imaging devices automatically from the PostDICOM order database. When a patient order is created — via the API or manually in the web interface — the modality queries PostDICOM MWL and pre-fills patient demographics and accession numbers at the device, eliminating manual data entry and reducing transcription errors.
Create password-protected, time-limited share links for individual studies or entire folders via a single API call. Set expiry dates, enable or disable download, and optionally trigger email delivery to specified recipients — all without anyone logging into the PostDICOM web interface. Automate patient image distribution at the end of every study.
Integration Workflow
A PostDICOM DICOMweb integration follows four steps: authenticate with your API credentials, push studies via STOW-RS or the JavaScript API, query and retrieve via QIDO-RS and WADO-RS, then distribute viewer links or report results — all without manual interaction with the PostDICOM web interface.
Every API request is authenticated with a unique apiKey and accountKey pair issued to your PostDICOM account. Credentials are scoped to your account and can be rotated at any time from the PostDICOM settings panel.
DICOM modalities and archive systems send studies to PostDICOM via a standard STOW-RS multipart POST to the DICOMweb endpoint. Server-side applications can use the JavaScript API to upload DICOM files or clinical documents with optional anonymisation applied on upload.
Downstream systems query PostDICOM using QIDO-RS at study, series, or instance level — filtering by Patient ID, accession number, modality, date range, or Study Instance UID. Individual instances or full studies are retrieved via WADO-RS and saved as standard .dcm files.
Once a study is in PostDICOM, your application generates a password-protected viewer link via the API and delivers it to the referring clinician or patient by email. The recipient opens the CE-certified DICOM viewer in any modern browser — no additional software or PostDICOM account required at their end.
Supported Standards & Protocols
Pricing
API integration requires the Enterprise plan as a base subscription. JavaScript Cloud API, DICOMweb, and FHIR endpoint access are available as add-ons priced on top.
Required base subscription for API access
API and DICOMweb access requires the Enterprise plan as a base subscription. The three integration add-ons — JavaScript Cloud API, DICOMweb, and FHIR endpoints — are available on top of this plan at additional cost.
Required base subscription for API access
API and DICOMweb access requires the Enterprise plan as a base subscription. The three integration add-ons — JavaScript Cloud API, DICOMweb, and FHIR endpoints — are available on top of this plan at additional cost.
FAQ
The PostDICOM Cloud API is a JavaScript library that runs in both browser and Node.js environments. DICOMweb endpoints (STOW-RS, WADO-RS, QIDO-RS) are standard HTTP endpoints accessible from any language or framework — Python, Java, C#, Ruby, Go, or any HTTP client library. API and DICOMweb access requires the Enterprise or Custom plan.
PostDICOM supports the three core DICOMweb services: STOW-RS (Store) for uploading DICOM instances via multipart/related POST requests, QIDO-RS (Query) for searching at study, series, or instance level using standard DICOM attributes, and WADO-RS (Retrieve) for downloading instances or full studies as standard .dcm files.
Yes. The PostDICOM viewer runs in any modern browser. Once your application generates a share link via the API, you can open it in a new browser tab or embed it inside an iframe within your platform. The CE-certified diagnostic viewer supports MPR, 3D volume rendering, measurements, window/level adjustment, and report creation — all without additional software at the viewing end.
Contact PostDICOM to discuss a sandbox or evaluation setup. API access is available on the Enterprise and Custom plans. The 7-day free trial on the Enterprise plan lets you explore all API and DICOMweb endpoints before committing to a paid plan.
When an order is created in PostDICOM — via the JavaScript API or the web interface — it becomes available on the PostDICOM MWL server. Your DICOM modality is configured to query that MWL server; when the patient arrives, the technician selects the order from the device's worklist screen and patient demographics and accession numbers are pre-filled automatically.
Yes. The JavaScript API supports an anonymisation option on upload. Patient-identifying DICOM tags are stripped or replaced before the study is stored in PostDICOM, making it suitable for research, trial data collection, or cross-border data sharing where anonymisation is a regulatory requirement.
When you create your PostDICOM account, you select one of 12 Microsoft Azure regions: EU (Germany (Frankfurt), France (Paris)), USA (East, West, South Central), UK (London), Switzerland (Zurich), Canada (Montreal), Asia-Pacific (Singapore, Australia (Sydney), India (Pune)), and South America (Brazil(São Paulo)). All studies and documents are stored exclusively within your selected jurisdiction.
Yes. All data in transit is encrypted via TLS 1.2 or 1.3 over HTTPS. Data at rest is encrypted with AES-256. Access controls, API key scoping, and role-based user permissions allow you to restrict what each application or user can see and do. PostDICOM holds CE Mark Class IIb medical device certification, ISO 13485, and ISO 27001 certification. HIPAA-compliant and GDPR-compliant architecture is available in the appropriate Azure regions.
Before cancelling, download all DICOM studies and documents you wish to retain. When your subscription ends, all patient data is permanently deleted from our systems. Your account record is retained for accounting purposes only.
Yes. All plans include a 7-day free trial with full access to your selected plan's features. A card is required at sign-up for verification — you are not charged until your 7-day trial expires, and your subscription auto-renews unless cancelled. You can easily cancel any time before the trial ends.
7-day free trial. No charge until it expires, and your subscription auto-renews unless cancelled. No additional software to install for viewing or sharing. Simply connect your imaging devices via our lightweight communicator and start your cloud workflow in minutes. Connect your first device and upload a study today.