dicom-metadata-extract

To extract DICOM metadata and check for PHI presence, this skill uses pydicom to read the file header and returns a structured JSON payload containing modality, study, series, image fields, and a phi_present indicator based on DICOM PS3.15 basic-profile tags.

Yes, pydicom reads the DICOM headers, and this skill flags PHI presence by checking against a standard subset of DICOM PS3.15 basic-profile tags, returning phi_present and phi_tags_found fields for validation.

No, you cannot use this skill for clinical data de-identification workflows because it explicitly does not perform de-identification; it only extracts metadata and returns a phi_scope_disclaimer outlining the limitations of its PHI detection scope.

The best way to validate PHI handling in non-clinical DICOM pipelines is to run this skill on a file to produce a JSON payload with phi_present and phi_tags_found fields, enabling engineers to review sensitive data visibility without altering the original file.

The JSON metadata extraction output includes modality, study, series, and image metadata fields, alongside the phi_present boolean, phi_tags_found list, and a phi_scope_disclaimer to support engineering testing scenarios.

A phi_scope_disclaimer appears in the DICOM metadata extraction output to explicitly outline the scope and limitations of the PHI detection mechanism, reminding users that the skill checks a subset of PS3.15 basic-profile tags and does not perform de-identification.