Convert ORA to DCM
Turn ORA images into DICOM. The flattened picture saved inside the file is read; layers are not read one by one, and a file without one, as some older programs wrote, is refused.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop ORA files on the dialor turn it to pick what to do
A DICOM image made from your layered file.The merged picture becomes one uncompressed DICOM file.
What you get
One DCM file that holds the same pixels as the ORA image, at 8 bits per channel. It is stored as an uncompressed DICOM secondary capture image.
Transparent areas are placed on white, because the output has no transparency.
What is left empty or made up
Patient and study fields are left empty. The file carries no name, ID or other details about a person or an exam.
New study, series and image IDs are made up for the file. They do not come from the ORA file.
Going back
To turn a DICOM image into a layered file again, use DCM to ORA.
ORA and DCM.What each format is.
The formats
OpenRaster
The open layered image format of MyPaint, GIMP and Krita. A zip with the layers and a merged preview.
- Extensions
- .ora
- MIME type
- image
/openraster - Kind
- Images
DICOM
Medical images from CT, MRI, X-ray and ultrasound, with the patient and study tags alongside the pixels.
- Extensions
- .dcm .dicom
- MIME type
- application
/dicom - Kind
- Images
In your code.The same ORA to DCM conversion through the API, for your app or your agent.
$ cv convert photo.ora photo.dcm$ cv convert photo.ora photo.dcmQuestions.What people ask about ORA to DCM.
Yes. The pixels are the same, stored at 8 bits per channel and uncompressed.
They are placed on white. The DICOM output has no transparency.
No. Patient and study fields are left empty. Only the study, series and image IDs are filled, with new made-up values.
Yes. The conversion gives you one DCM file.