cloud-healthcare-search-dicom-instances

A “cloud-healthcare-search-dicom-instances” tool searches for DICOM instances in a DICOM store.

About

A cloud-healthcare-search-dicom-instances tool searches for DICOM instances in a DICOM store based on a set of criteria. It’s compatible with the following sources:

search-dicom-instances returns a list of DICOM instances that match the given criteria.

Example

tools:
  search_dicom_instances:
    kind: cloud-healthcare-search-dicom-instances
    source: my-healthcare-source
    description: Use this tool to search for DICOM instances in the DICOM store.

Reference

fieldtyperequireddescription
kindstringtrueMust be “cloud-healthcare-search-dicom-instances”.
sourcestringtrueName of the healthcare source.
descriptionstringtrueDescription of the tool that is passed to the LLM.

Parameters

fieldtyperequireddescription
StudyInstanceUIDstringfalseThe UID of the DICOM study.
PatientNamestringfalseThe name of the patient.
PatientIDstringfalseThe ID of the patient.
AccessionNumberstringfalseThe accession number of the study.
ReferringPhysicianNamestringfalseThe name of the referring physician.
StudyDatestringfalseThe date of the study in the format YYYYMMDD. You can also specify a date range in the format YYYYMMDD-YYYYMMDD.
SeriesInstanceUIDstringfalseThe UID of the DICOM series.
ModalitystringfalseThe modality of the series.
SOPInstanceUIDstringfalseThe UID of the SOP instance.
fuzzymatchingbooleanfalseWhether to enable fuzzy matching for patient names. Fuzzy matching will perform tokenization and normalization of both the value of PatientName in the query and the stored value. It will match if any search token is a prefix of any stored token. For example, if PatientName is “John^Doe”, then “jo”, “Do” and “John Doe” will all match. However “ohn” will not match.
includefield[]stringfalseList of attributeIDs to include in the output, such as DICOM tag IDs or keywords. Set to ["all"] to return all available tags.
storeIDstringtrue*The DICOM store ID to search in.

*If the allowedDICOMStores in the source has length 1, then the storeID parameter is not needed.

Last modified November 7, 2025: chore(main): release 0.19.1 (#1901) (cd8d68d)