DICOMweb Specifications
Tricefy supports uploading of ultrasound captures through DICOMweb. Below are some of the technical details of the Tricefy DICOMweb API.
| Specification | Description |
|---|---|
| DICOMweb service | Store DICOM objects (STOW-RS) |
| Transfer syntaxes | JPEG Baseline (1.2.840.10008.1.2.4.50) JPEG Lossless (1.2.840.10008.1.2.4.70) Explicit VR Little Endian (1.2.840.10008.1.2.1) |
| DICOM file types (SOPClassUID) | Ultrasound Image (1.2.840.10008.5.1.4.1.1.6.1) Ultrasound multiframe (1.2.840.10008.5.1.4.1.1.3.1) Structured Report (1.2.840.10008.5.1.4.1.1.88.33) Secondary Capture (1.2.840.10008.5.1.4.1.1.7) Encapsulated PDF (1.2.840.10008.5.1.4.1.1.104.1) |
| API endpoints | Tricefy Global: https://tricefy4.com/dicomweb/studies Tricefy USA: https://us.tricefy.com/dicomweb/studies |
| HTTP Methods | POST | GET |
| Content-type | application/dicom |
| Body | raw DICOM file bytes |
| Authorization | Basic <base64 email:token> Username: Tricefy user email address Password: Tricefy Account API token |
| Max file size allowed | 10 MB |
| Max connection time | 60 seconds (one file upload per connection/request) |
An account API token can be generated in the Tricefy account settings (admin only)
- Token is shown only once when created, so copy and store it securely
- If lost, delete it and issue a new token
- The authenticated user must have access to the account associated with the token
A GET request to the DICOMweb endpoint can be used to verify authentication/connectivity:
curl --location \ --request GET "" \ --user "user@example.com:ACCOUNT_API_TOKEN"
Example POST request:
curl --location \ --request POST "<TRICEFY_DICOMWEB_ENDPOINT>" \ --user "user@example.com:ACCOUNT_API_TOKEN" \ --header "Content-Type: application/dicom" \ --data-binary "<dicom_file>"
Copyright ©