Distinguish source modality

  • I've problem identifying the study.


    Here's the situation:
    Two clinics have same model Fujifilm x-ray modalities with local pacs. The local pacs forwards images to central hospital Conquest pacs. Is there a way I can uniquely distinguish study is coming from which clinic?


    Clinic1:
    Fujifilm modality forwards the images to local pacs with default ae_title e.g. "AETITLE"
    The local pacs forwards the images to centrally located hospital Conquest PACS.
    e.g. studyid = 1.2.392.200036.9125.2.3079200157247.64584720960.24602


    Clinic2 at different location:
    Fujifilm modality forwards the images to local pacs with default ae_title e.g. "AETITLE"
    The local pacs forwards the images to centrally located hospital Conquest PACS.
    e.g studyid = 1.2.392.200036.9125.2.26160169177194.64584817748.24162


    Now conquest PACS is receiving images from both clinics. Earlier idea was to identify the clinics by the originating ae_title. But don't ask me why but changing the default ae_title of forwarding local pacs is not an option. Also can't rely on institute tag as it's not filled in consistently.


    My question is - Is there a way I can distinguish study is coming from which clinic?
    Is there a tag or combination of tags which can help differentiate which clinic the study belongs to?


    Unfortunately Institute tag is not always filled in and patientId is not guaranteed to be unique among two clinics.


    Clinic 1 studyid: 1.2.392.200036.9125.2.3079200157247.64584720960.24602
    Clinic 2 studyid = 1.2.392.200036.9125.2.26160169177194.64584817748.24162


    From the studyid - 1.2.392.200036.9125.2 -> rootid + first two suffixes are common. Should I look at the modality if there is a UID string they use and is this common for all modalities?


    I would appreciate any kind of input or direction to resolve this issue - thanks in advance.


    -Vinod

  • Give each of the local pacs a different AE title to send to, but the same IP/port. You can run converters based on "CalledAE".


    For example,
    Clinic1:
    The local pacs (with an AE Title of AETITLE) sends to conquest (AE Title: CLINIC1)


    Clinic2:
    The local pacs (with an AE Title of AETITLE) sends to conquest (AE Title: CLINIC2)


    The Conquest hospital pacs is promiscuous and will accept images destined to ANY AE Title as long as the IP and port matches its own.


    I hope I explained that clear enough. I can provide a dicom.ini with an example if needed. -Scott

  • Thanks Scott - that looks like a good solution. I didn't think of converters.


    Is there a generic solution based on Dicom tags which can distinguish that, so I don't have to add new converters when additional clinics are added. I mean independent of converters?
    Thanks
    -Vinod

  • Hi Marcel,
    How can I access n-digit of UID in dicom.ini?


    Stationname is default to be same and originator is not filled in reliably.


    Do UID have any meaning? I thought you cannot rely on them to parse. If there is s reliable way in the structure then I would like to use them to distinguish the clinic.
    E.g.
    1.2.392.200036.9125.2.26160169177194.64584817748.24162
    1.2.392.200036 -> rootid
    9125.2 -> first two suffixes are common among two clinics.
    Should I look for 2 suffixes after rootid and is it consistent for all modalities?


    Thanks
    V

  • Hi,


    typically the root of an UID is set in the configuration (as in conquest). In the exportconverters you can test on a substring of any dicom tag, including the UIDs. But the UID root will be different for each machine.


    Marcel

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!