[Loris-dev] Different StudyInstanceUIDs

[Nicolas Brossard]

Hi Samson,

This will not be sufficient as LORIS would expect in this case different
SeriesInstanceUID/echo time combinations for these images...Unfortunately,
I don't think there is any way around this.


Best,
Nicolas

On Fri, Sep 25, 2020 at 4:47 PM Samson Antel <samson at neurorx.com> wrote:

> Hi Nicolas,
>
> The dual echo PD/T2 sequences we are dealing with will indeed have
> distinct echo times.
>
> We also have some MT-On/MT-Off image pairs that were acquired on Philips
> scanners using a dynamic sequence.  In those cases, the images will share a
> SeriesInstanceUID _and_ an echo time.  However, they will contain distinct
> InstanceNumbers and TemporalPositionIdentifiers; will that be sufficient
> for LORIS?
>
> Thanks,
> Samson
>
>
> On Fri, Sep 25, 2020 at 4:37 PM Nicolas Brossard <
> nicolasbrossard.mni at gmail.com> wrote:
>
>> Hi Alfredo,
>>
>> I am afraid what I said earlier was not 100% correct: each
>> SerieInstanceUID/echo time combo has to be unique. So yeah, you could have
>> two DICOM files associated with different modalities that have identical
>> SeriesInstanceUIDs (in that case though, it is expected that the echo times
>> will be different). I am guessing the studies you are referring to in your
>> email fit that requirement, right?
>>
>> Apologies for the confusion.
>>
>>
>> Best,
>> Nicolas
>>
>>
>> On Fri, Sep 25, 2020 at 4:29 PM Morales Pinzon, Alfredo <
>> AMORALESPINZON at bwh.harvard.edu> wrote:
>>
>>> Hi Nicolas,
>>>
>>> We are working on this issue but a question. Sometimes studies have dual
>>> echo and dynamic sequences (e.g., a dual-echo PD/T2 sequence produces a
>>> PD-weighted image and a T2-weighted image together) that result in in
>>> two sequences sharing the same “ SeriesInstanceUID”. This seems to be
>>> quite common, don’t you have a workaround already available in LORIS?
>>>
>>> Best,
>>> Alfredo.
>>>
>>> On May 4, 2020, at 8:50 AM, Morales Pinzon, Alfredo <
>>> AMORALESPINZON at BWH.HARVARD.EDU> wrote:
>>>
>>> Hi Nicolas,
>>>
>>> Thank you for your answer. We’ll handle these cases based on LORIS
>>> requirements.
>>>
>>> Best,
>>> Alfredo.
>>>
>>> On May 1, 2020, at 1:39 PM, Nicolas Brossard <
>>> nicolasbrossard.mni at gmail.com> wrote:
>>>
>>>         External Email - Use Caution
>>>
>>> Hi Alfredo,
>>>
>>> You cannot insert in the database a scan archive containing two
>>> different study UIDs: all the scans inside the archive must have the same
>>> study UID, that's a LORIS requirement. I suggest you split your original
>>> archive into two archives, based on their study UIDs, and then
>>> upload/insert both. You could also "hack" you original archive so that all
>>> study UIDs are identical but I am not a big fan of this strategy since you
>>> are altering the original data you got from the scanner...
>>>
>>>
>>> Best,
>>> Nicolas
>>>
>>> p.s: if you are not comfortable splitting archives, I can help
>>>
>>> On Fri, May 1, 2020 at 11:03 AM Morales Pinzon, Alfredo <
>>> AMORALESPINZON at bwh.harvard.edu> wrote:
>>>
>>>> Dear LORIS-Dev Team,
>>>>
>>>> In the IPMSA project some scans have acquisitions with two different StudyInstanceUIDs.
>>>> This leads to an error in the insertion pipeline. The reason for having two
>>>> different StudyInstanceUIDs is because some acquisitions failed QC and
>>>> were re-acquired and added to the same study but with a different StudyInstanceUIDs. Here
>>>> are our questions:
>>>>
>>>> 1. Would it be possible to insert a study having acquisitions with
>>>> two different StudyInstanceUIDs?
>>>>
>>>> 2. If we were to change the StudyInstanceUIDs to have only one in a
>>>> study, would LORIS insert they study with acquisitions having different
>>>> scan date?
>>>>
>>>> Thank you for your help.
>>>>
>>>> Regards,
>>>> Alfredo.
>>>>
>>>> The information in this e-mail is intended only for the person to whom
>>>> it is
>>>> addressed. If you believe this e-mail was sent to you in error and the
>>>> e-mail
>>>> contains patient information, please contact the Partners Compliance
>>>> HelpLine at
>>>> http://www.partners.org/complianceline . If the e-mail was sent to you
>>>> in error
>>>> but does not contain patient information, please contact the sender and
>>>> properly
>>>> dispose of the e-mail.
>>>> _______________________________________________
>>>> Loris-dev mailing list
>>>> Loris-dev at bic.mni.mcgill.ca
>>>> https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev
>>>>
>>>
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20200930/e6638e09/attachment.html>