Skip to main content
Beta Limina supports scanning Digital Imaging and Communications in Medicine (DCM or DICOM) files for PII and creating de-identified or redacted copies. Limina’s supported entity types function across each file type, with localized variants of different PII (Personally Identifiable Information) entities, PHI (Protected Health Information) entities, and PCI (Payment Card Industry) entities being detected. Our Supported Languages and Supported Entity Types page provides a more detailed look.

​
How DCM/DICOM Files Are Processed

DICOM files are processed as follows:
  1. The DICOM file’s contents which include images, metadata and other elements as described in the DICOM file standard are extracted.
  2. Text components of the DICOM file, including supported properties and metadata are processed by Limina’s text module, except for the fields listed below in constraints that are assumed to never contain PII. More information about sensitive fields in DICOM files can be accessed here.
  3. Any image components of the DICOM file are processed by Limina’s image module. This process finds and masks any sensitive text, such as scan date and operator name. The scan itself, such as an MRI isn’t altered.
  4. A new DICOM file is constructed using the de-identified or redacted equivalents created in the steps above.
Graphical content where text is present will be OCRed and then redacted. You can configure the OCR System by setting it as an Environment Variable or sending it in the request object. Check out our OCR Guide to further understand the OCR modes and their usage.

​
Constraints

  • Limina only supports DICOM files with 2D images, DICOM files containing 3D images or videos are not currently supported. Please split 3D images up into a series of 2D images for processing.
  • The following metadata and parameters are assumed to never contain PII and are always passed through the output DICOM file:
    Metadata & Parameters
    "AcquisitionNumber",
"BitsAllocated",
"BitsStored",
"Columns",
"ConvolutionKernel",
"DataCollectionCenter",
"DataCollectionCenterPatient",
"DataCollectionDiameter",
"DetectorBinning",
"DistanceSourceToDirector",
"DistanceSourceToPatient",
"DistanceSourceToDetector",
"Exposure",
"ExposureTime",
"FieldOfViewDimensions",
"FieldOfViewShape",
"FieldOfViewOrigin",
"FilterType",
"FrameOfReferenceUID",
"FocalSpots",
"GantryDetectorTilt",
"GeneratorPower",
"Grid",
"HighBit",
"ImageOrientationPatient",
"ImagePositionPatient",
"ImageType",
"ImagerPixelSpacing",
"InstanceCreationDate",
"InstanceCreationTime",
"InstanceNumber",
"IrradiationEventUID",
"KVP",
"LargestImagePixelValue",
"Modality",
"NumberOfPhaseEncodingSteps",
"NumberOfStudyRelatedInstances",
"PhotometricInterpretation",
"PixelData",
"PixelPaddingValue",
"PixelRepresentation",
"PixelSpacing",
"PositionReferenceIndicator",
"ReconstructionDiameter",
"ReconstructionTargetCenterPatient",
"RescaleIntercept",
"RescaleSlope",
"RotationDirection",
"Rows",
"SOPClassUID",
"SOPInstanceUID",
"SamplesPerPixel",
"ScanOptions",
"SeriesInstanceUID",
"SeriesNumber",
"SliceLocation",
"SliceThickness",
"SmallestImagePixelValue",
"SoftwareVersions",
"SpatialResolution",
"SpecificCharacterSet",
"StudyInstanceUID",
"TableHeight",
"WindowCenter",
"WindowWidth",
"XRayTubeCurrent",
"XRayTubeCurrentInuA"

​
Support Matrix

CPU ContainerGPU ContainerCommunity APIProfessional API
SupportedYesYesUp to 10 MiBNo

​
Sample Request

Connect with one of our privacy experts to run this code.
{
  "file": {
    "data": "<file_content_base64>",
    "content_type": "application/dicom"
  },
  "entity_detection": {
    "return_entity": true
  }
}

​
Sample Response

Response
{
  "processed_file": "Base64 Encoded File Content of the Redacted File",
  "processed_text": "string",
  "entities": "List[Entity]",
  "entities_present": true,
  "languages_detected": {"lang_1": 0.67, "lang_2": 0.74}
}