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.
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.
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 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.
API integration requires the Ultimate 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 Ultimate 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.
Enterprise — tailored scope and pricing
Large healthcare organisations and software vendors with high study volumes, dedicated onboarding requirements, or bespoke integration needs. Base plan, add-ons, storage, and user counts are all agreed individually.
Everything you need to know before getting started.
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 Ultimate 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 Ultimate and Custom plans. The 7-day free trial on the Ultimate 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 your primary storage location from 12 independent 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)). Your data is hosted within your selected jurisdiction to help you meet local data residency requirements and comply with regional healthcare privacy laws (such as GDPR or HIPAA).
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.
By submitting this form, you agree to our Privacy Policy. Your data is processed in accordance with our Privacy Policy and applicable data protection laws.