[Loris-dev] BIDS Error
Cecile Madjar
cecile.madjar at mcin.ca
Mon Jun 7 16:50:06 EDT 2021
Hi Alfredo,
Interesting. I was expecting to see the Active field set to NULL which
would have explained why you do not see anything in the imaging browser. My
next theory is that you do not have anything for the parameter_type name
'acquisition_date' which is very likely to be the case for a BIDS dataset
with no date information.
Does the following query return anything for you? That is the query that is
supposed to return data to the imaging browser (that you can find in
modules/imaging_browser/php/imagingbrowserrowprovisioner.class.inc
<https://github.com/aces/Loris/blob/23.0-release/modules/imaging_browser/php/imagingbrowserrowprovisioner.class.inc>
).
SELECT
p.Name as Site,
c.PSCID as PSCID,
c.CandID as DCCID,
Project.Name as project,
s.Visit_label as visitLabel,
$PendingFailSubquery as Visit_QC_Status,
DATE_FORMAT(MIN(pf.Value), \"%Y-%m-%d\") as First_Acquisition,
FROM_UNIXTIME(MIN(f.InsertTime)) as First_Insertion,
FROM_UNIXTIME(MAX(fqc.QCLastChangeTime)) as Last_QC,
$NewDataSubquery as New_Data,
GROUP_CONCAT(DISTINCT OutputType) as Links,
s.ID as sessionID,
GROUP_CONCAT(DISTINCT modality.Scan_type) as sequenceType,
$PendingNewquery as pending,
$modalities_subquery
s.CenterID as CenterID,
c.Entity_type as entityType,
s.ProjectID
FROM psc AS p
JOIN session s ON (s.CenterID=p.CenterID)
JOIN candidate c ON (c.CandID=s.CandID)
LEFT JOIN Project ON (s.ProjectID=Project.ProjectID)
JOIN files f ON (f.SessionID=s.ID)
LEFT JOIN files_qcstatus fqc ON (fqc.FileID=f.FileID)
JOIN parameter_file pf ON (f.FileID=pf.FileID)
JOIN parameter_type pt USING (ParameterTypeID)
LEFT JOIN mri_scan_type modality ON
(f.AcquisitionProtocolID=modality.ID)
$left_joins
WHERE
s.Active = 'Y' AND
f.FileType IN ('mnc', 'nii') AND
pt.Name='acquisition_date'
GROUP BY s.ID
ORDER BY c.PSCID, s.Visit_label
If you get an empty result, try removing the following from the WHERE
section of the query above:
..... AND
pt.Name='acquisition_date'
If my second theory is right, you should then see rows returned, in which
case you will need to modify the query in the imaging_browser code.
Let me know how those go.
Regarding the Scan_type, I should probably be populated by the insertion
script so this may be a bug on the bids_import scripts specific to the
imaging component. In the meantime, you can indeed set the flag to Y for
the sessions you know contain scan data.
Hope this helps,
Cécile
On Mon, Jun 7, 2021 at 12:27 PM Morales Pinzon, Alfredo <
AMORALESPINZON at bwh.harvard.edu> wrote:
> Hi Cécile,
>
> Thank you for prompt answer. Here is the output of the query:
>
> ===
> mysql> SELECT CandID, Visit_label, Active, Scan_done, CenterID, ProjectID,
> SubprojectID FROM session WHERE Visit_label = 'screening' AND CandID=207019;
>
> +--------+-------------+--------+-----------+----------+-----------+--------------+
> | CandID | Visit_label | Active | Scan_done | CenterID | ProjectID |
> SubprojectID |
>
> +--------+-------------+--------+-----------+----------+-----------+--------------+
> | 207019 | screening | Y | NULL | 843 | 12 |
> 2 |
>
> +--------+-------------+--------+-----------+----------+-----------+--------------+
> 1 row in set (0.00 sec)
> ===
>
> I guess the “Scan_done” should be ‘Y’ instead of ’NULL’. Is this something
> that the BIDS importing script should take care of? Is the fix as simple as
> just setting Scan_done to ‘Y’?
>
> Best,
> Alfredo.
>
> On Jun 6, 2021, at 4:48 PM, Morales Pinzon, Alfredo <
> AMORALESPINZON at BWH.HARVARD.EDU> wrote:
>
> Hi Cécile,
>
> We managed to insert the candidates and the visits, and create the
> specific file names for BIDS before actually launching the BIDS script. The
> script finally worked, however I don’t see the images in LORIS. I am adding
> down below the bids log insertion. Is there something additional I need to
> do to be able to see the images? In the web site I see the candidate and
> the visit but the column “Imaging Scan Done” is marked with a question mark
> (see attachment).
>
> ===
> /PROJECT/bin/mri/python_virtualenvs/loris-mri-python/lib/python3.6/site-packages/bids/layout/validation.py:46:
> UserWarning: The ability to pass arguments to BIDSLayout that control
> indexing is likely to be removed in future; possibly as early as PyBIDS
> 0.14. This includes the `config_filename`, `ignore`, `force_index`, and
> `index_metadata` arguments. The recommended usage pattern is to initialize
> a new BIDSLayoutIndexer with these arguments, and pass it to the BIDSLayout
> via the `indexer` argument.
> warnings.warn("The ability to pass arguments to BIDSLayout that control "
>
> Connecting to:
> database: DATABASE
> username: USERNAME
> hostname: 111.222.333440
> port : 1234
>
>
> Executing query:
> SELECT Value FROM Config WHERE ConfigID = (SELECT ID FROM
> ConfigSettings WHERE Name = %s);
>
> With arguments:
> ('default_bids_vl',)
>
>
> Executing query:
> SELECT Value FROM Config WHERE ConfigID = (SELECT ID FROM
> ConfigSettings WHERE Name = %s);
>
> With arguments:
> ('dataDirBasepath',)
>
> AMP::bids_dir: /DATA/CAND_A/bids
> Loading the BIDS dataset with BIDS layout library...
>
> AMP::bids_config: /PROJECT/bin/mri/python/lib/bids.json
> root: /DATA/CAND_A/bids
> target:: /DATA/CAND_A/bids/dataset_description.json
> => BIDS dataset loaded with BIDS layout
>
> Grepping candidates from the BIDS layout...
> Validating the list of participants...
> subjects: ['207019']
> => Passed validation of the list of participants
>
> => List of participants found:
> 207019
>
>
> Grepping list of sessions from the BIDS layout...
> => List of sessions found:
>
> 207019: screening
>
>
> Grepping the different modalities from the BIDS layout...
> => Done grepping the different modalities from the BIDS layout
>
>
> Executing query:
> SELECT * FROM candidate WHERE PSCID = %s
>
> With arguments:
> ('207019',)
> Executing query:
> SELECT SubprojectID FROM subproject WHERE title = %s
>
> With arguments:
> ['Experimental']
>
>
> Executing query:
> SELECT * FROM session WHERE CandID = %s AND Visit_label = %s
>
> With arguments:
> ('622350', 'screening')
>
>
> Executing query:
> SELECT * FROM candidate WHERE PSCID = %s
>
> With arguments:
> ('207019',)
>
>
> Executing query:
> SELECT SubprojectID FROM subproject WHERE title = %s
>
> With arguments:
> ['Experimental']
>
>
> Executing query:
> SELECT * FROM session WHERE CandID = %s AND Visit_label = %s
>
> With arguments:
> ('622350', 'screening')
>
>
> Executing query:
> SELECT type FROM ImagingFileTypes
>
>
> Executing query:
> SELECT f.FileID, f.File FROM files AS f JOIN parameter_file USING
> (FileID) JOIN parameter_type USING (ParameterTypeID) WHERE Value=%s
>
> With arguments:
>
> ('248248fb303a762548e0be602b0b6bd6c6f33b4c860898c69faa8273be7a80f6d93b6413ec3bbeaadf22005fac04b07e9c08487e7b0a6690f64c2781d77d69b4',)
>
>
> Executing query:
> SELECT type FROM ImagingFileTypes
>
>
> Executing query:
> SELECT f.FileID, f.File FROM files AS f JOIN parameter_file USING
> (FileID) JOIN parameter_type USING (ParameterTypeID) WHERE Value=%s
>
> With arguments:
>
> ('b16bc029ea1cb8271a0728785d04eddaaa66e4d89c09e990552667b3c5598d17cee045b5b4ee3480dc2b8e08b5b05ca4e53c57f50b13b26f6467b9e4f455d09e',)
>
>
> Executing query:
> SELECT type FROM ImagingFileTypes
>
>
> Executing query:
> SELECT f.FileID, f.File FROM files AS f JOIN parameter_file USING
> (FileID) JOIN parameter_type USING (ParameterTypeID) WHERE Value=%s
>
> With arguments:
>
> ('44346136db049d0faf867a34d57d5714803a320b070013da0e1cf66e064f4dc9db92533f8aa8caaafcb78ce141c5444c5b8f8dc6b1d1c7dac530a4c2375eedcd',)
>
>
> Executing query:
> SELECT type FROM ImagingFileTypes
>
>
> Executing query:
> SELECT f.FileID, f.File FROM files AS f JOIN parameter_file USING
> (FileID) JOIN parameter_type USING (ParameterTypeID) WHERE Value=%s
>
> With arguments:
>
> ('ee91658a67d7d96007f6f0c625cceb700c9fa5bbecf34cea3cae8f1445a6efce5f735b2ab68d26717a6aaa418808b3d8fb30b03e03ae1982b0eeed834429d081',)
>
>
> Executing query:
> SELECT type FROM ImagingFileTypes
>
>
> Executing query:
> SELECT f.FileID, f.File FROM files AS f JOIN parameter_file USING
> (FileID) JOIN parameter_type USING (ParameterTypeID) WHERE Value=%s
>
> With arguments:
>
> ('749c00e5aa64583c91f29672b228b9d89e691cef7d8f3380eefbc1fee466bd3d987fd7178001f0e4f63684a50e139a7bb8ed197981d1588ffc4dfc4eed8278b8',)
> ===
>
> Thank you for your help.
>
> Best,
> Alfredo.
>
> <Screen Shot 2021-06-06 at 4.44.57 PM.png>
>
> On May 13, 2021, at 10:08 AM, Cecile Madjar <cecile.madjar at mcin.ca> wrote:
>
> External Email - Use Caution
>
> Hi Alfredo,
>
> The requirement of not having any special characters in the Participant ID
> or Session ID comes from BIDS and the libraries used to parse the BIDS
> dataset before insertion into LORIS.
>
> On the LORIS front:
>
> - the ID used next to sub-<ID> will be used for the PSCID field of the
> candidate table (the CandID field being automatically generated as 6 random
> digits by the insertion script).
> - the ID used next to ses-<ID> will be used for the visit label field
> of the session table
>
> There might be another solution for you: modifying the file
> https://github.com/aces/Loris-MRI/blob/main/python/lib/bids.json
> <https://secure-web.cisco.com/1GvLDW-g8RekA6xfXzTQGS9x-cvm3VJ64Me4gEy4E2Yh3_J_-W9ZJiP9DEv9M9oH_JN3CJGEaRyJUvOCUzrNqMXl0tpX8TJ_Cfrs5JA9p_ICYgDGAU_HcPRpK0aHBkRHCW9mHZTixcIoY9EEim1Tt4JhQWyQlJpaTKY-bd1bc5O1lxwHz6sj4nGQ5bXFiDLYRP4Y8DWJzxYpm8EMaj_QYRiVdUOwHiSGfVGMouhDDMYYwBHrEEdV1Ompf5QRyVkSSAJaGL2Q3tSABSa8USdVkOQ/https%3A%2F%2Fgithub.com%2Faces%2FLoris-MRI%2Fblob%2Fmain%2Fpython%2Flib%2Fbids.json>
> so that it matches the string used for your data. You would need to modify
> the pattern for subject and session in that file to match what you have. In
> theory, once done, pybids should be able to read your dataset.
>
> Hope this helps,
>
> Cécile
>
> On Thu, May 13, 2021 at 9:47 AM Morales Pinzon, Alfredo <
> AMORALESPINZON at bwh.harvard.edu> wrote:
>
>> Hi Cécile,
>>
>> Is it possible to modify your IDs to be alphanumerical?
>>
>>
>> It is possible but puts more burden on our side as every single file now
>> has to be modified. What would be best format for LORIS for the user ids
>> (e.g., six digits) and the visit labels (e.g., alphanumerical without
>> dash)? I just want to make sure we are compliant with LORIS requirements
>> before modifying the bids files.
>>
>> Best,
>> Alfredo.
>>
>> On May 11, 2021, at 6:34 PM, Cecile Madjar <cecile.madjar at mcin.ca> wrote:
>>
>> External Email - Use Caution
>>
>> Hi Alfredo,
>>
>> It looks like the pybids is not able to read your BIDS dataset, which is
>> why it returns an empty list of subjects.
>>
>> I just tried on the python terminal to load your dataset on pybids and it
>> does not find any subject or visit. This is probably due to the name of the
>> subject that contains special characters. That will also be problematic for
>> the session label of your dataset. I guess subjects in BIDS should remain
>> alphanumerical only. Is it possible to modify your IDs to be alphanumerical?
>>
>> Cécile
>>
>> On Tue, May 11, 2021 at 5:37 PM Morales Pinzon, Alfredo <
>> AMORALESPINZON at bwh.harvard.edu> wrote:
>>
>>> Hi Cécile,
>>>
>>> I just shared the dataset in the sftp in the following path:
>>> 2021_05_11/caseCecile_BIDS.zip
>>>
>>> Additionally, here is the output of the script after adding the prints
>>> in the PR 617:
>>>
>>> ===
>>> /PROJECT/bin/mri/python_virtualenvs/loris-mri-python/lib/python3.6/site-packages/bids/layout/validation.py:46:
>>> UserWarning: The ability to pass arguments to BIDSLayout that control
>>> indexing is likely to be removed in future; possibly as early as PyBIDS
>>> 0.14. This includes the `config_filename`, `ignore`, `force_index`, and
>>> `index_metadata` arguments. The recommended usage pattern is to initialize
>>> a new BIDSLayoutIndexer with these arguments, and pass it to the BIDSLayout
>>> via the `indexer` argument.
>>> warnings.warn("The ability to pass arguments to BIDSLayout that
>>> control "
>>>
>>> Connecting to:
>>> database: DATABASE
>>> username: USERDATABASE
>>> hostname: 111.222.333.44
>>> port : 3306
>>>
>>>
>>> Executing query:
>>> SELECT Value FROM Config WHERE ConfigID = (SELECT ID FROM
>>> ConfigSettings WHERE Name = %s);
>>>
>>> With arguments:
>>> ('default_bids_vl',)
>>>
>>>
>>> Executing query:
>>> SELECT Value FROM Config WHERE ConfigID = (SELECT ID FROM
>>> ConfigSettings WHERE Name = %s);
>>>
>>> With arguments:
>>> ('dataDirBasepath',)
>>>
>>> Loading the BIDS dataset with BIDS layout library...
>>> => BIDS dataset loaded with BIDS layout
>>>
>>> Grepping candidates from the BIDS layout...
>>> Validating the list of participants...
>>>
>>> ERROR: Participant ID mismatch between participants.tsv and raw data
>>> found in the BIDS directory/n
>>> CFTY720D2306.0102.00001is missing from the BIDS Layout
>>>
>>> List of subjects parsed by the BIDS layout:
>>> ===
>>>
>>> Best,
>>> Alfredo.
>>>
>>> On May 11, 2021, at 12:01 PM, Cécile Madjar <cecile.madjar at mcin.ca>
>>> wrote:
>>>
>>> External Email - Use Caution
>>>
>>> Sounds like a plan. Let me know once it is uploaded and I will ask
>>> Nicolas to give me access.
>>>
>>> Thanks!
>>>
>>> PS: you can view the diff on the PR and simply copy the code over to
>>> your files if easier
>>>
>>> On May 11, 2021, at 11:47 AM, Morales Pinzon, Alfredo <
>>> AMORALESPINZON at BWH.HARVARD.EDU> wrote:
>>>
>>> Hi Cecile,
>>>
>>> In my testing dataset I have only one subject, I can share it with you
>>> in the LORIS sftp, does that work for you?
>>>
>>> In the mean time I will diff and pull your PR, and then execute it. I’ll
>>> send you the output asap.
>>>
>>> Best,
>>> Alfredo.
>>>
>>> On May 11, 2021, at 11:36 AM, Cecile Madjar <cecile.madjar at mcin.ca>
>>> wrote:
>>>
>>> External Email - Use Caution
>>>
>>> Hi Alfredo,
>>>
>>> I do not have access to your dataset but is it possible that there is
>>> one or more sub-<ID> in the participants.tsv that are different from the
>>> sub-<ID> used in the directory structure? (a.k.a., folders sub-<ID> and
>>> filenames that should start with sub-<ID>.)
>>>
>>> This function is specifically cross checking the list provided in the
>>> participants.tsv file and the information gathered by the BIDSLayout
>>> library that read your BIDS dataset.
>>>
>>> I created a PR on LORIS-MRI to elaborate the log from the function you
>>> just sent: https://github.com/aces/Loris-MRI/pull/617
>>> <https://secure-web.cisco.com/17BHyJzFWfexg2et-D1qxjFw7-MsSpwCyZsKHDjuQa1Iruj-GV8fZRnaNOQe7rTfFaljPkHD9E0Kch6nwzSvbbe_48vUcKT3ozGDvxPfpe248W0Nml3EbqwefqTQo6V0gIBseIrXtJ4qwpUnrLVYpwZQyTPaDCbkm_NqrpLrBeXaHi-m5KCVluJqMYsb1DZBrqFL_XKJiIevFuiValC7eTehDRbTek9A5RvYsPN6hDTzEHFPQfCzzRD6W_iQSp80c_PbAKgxDUVLU2cePcP45pg/https%3A%2F%2Fgithub.com%2Faces%2FLoris-MRI%2Fpull%2F617> Maybe
>>> try adding the print statement in the diff of the PR to your code and rerun
>>> to get a better idea of what is going on?
>>>
>>> Let me know how it goes,
>>>
>>> Cécile
>>>
>>>
>>> On May 10, 2021, at 4:15 PM, Morales Pinzon, Alfredo <
>>> AMORALESPINZON at bwh.harvard.edu> wrote:
>>>
>>> Dear LorisDev team.
>>>
>>> I am running the BIDS uploading functionality of LORIS (from this PR
>>> suggested by Cecile: https://github.com/aces/Loris-MRI/pull/558/files
>>> <https://secure-web.cisco.com/1eWQtSLH8tHTpC1qsinKLnr4amf7Vdt1MLFNigX4jKdNz2mAoHV9ejLLcHZh1a0CUaUlzZMYTU9qzLaUEYYpyP1cl5UCR8e02WTmdMZUKXBNDeD8-cV2O5yTv8cgci7szP_MIGsvZ7FCjhqVmibPUnMFYbs6uYHGXZHOB5MsouWYLRHh89rJtQaFS8DOg4jfbwjp1bxwnO4FyuD3aKRv17dw9zoczaaXWnkbXXr87i6NQKYmA1NXhjM570IkyzSKuq-dlKj94vTZIlAChD5aFeg/https%3A%2F%2Fgithub.com%2Faces%2FLoris-MRI%2Fpull%2F558%2Ffiles> )
>>> but I’m getting the following error (see all the output below):
>>>
>>> ===
>>> ERROR: Participant ID mismatch between participants.tsv and raw data
>>> found in the BIDS directory/n
>>> ===
>>>
>>> After some debugging I saw that the array subjects in the following line
>>> is empty:
>>>
>>> https://github.com/laemtl/Loris-MRI/blob/3742522fa46b0ee2b9e384e30650a0c1f425c7af/python/lib/bidsreader.py#L134
>>> <https://secure-web.cisco.com/1sAIMc1N1U7sTpJYVEGfljx8iP9AUjxof1GeCQwNPKhd82OAXEZmdHoYu7n3Uq8jLaO-quBK1igoIw9Oo7d5JVNCfb3MNy6u-cvR2KkL-rfKwSOW_ovP_V5YKydvDMoE1ltw4MO29keFq-JiTymIk8Wm8TbXeHKxF2njboK6-6bctzRI-5K2tWwz82zUZyzDxyFdn4zXPqI8AihHeuWQQG3GOGgPSbRP-GOUfwbu2eVmvL_P_ldZetO1qjKowic0Gqnt-a9XN_8GORD5BLNlxTw/https%3A%2F%2Fgithub.com%2Flaemtl%2FLoris-MRI%2Fblob%2F3742522fa46b0ee2b9e384e30650a0c1f425c7af%2Fpython%2Flib%2Fbidsreader.py%23L134>
>>>
>>> I thought the issue was that we have symbolic links in our folder
>>> structure but after setting a testing example I am getting the same exact
>>> error.
>>>
>>> Any ideas why this is happening? The error does not help much. I’m happy
>>> to share the testing case, with all the BIDS structure to a LORIS
>>> developer, if this is helpful.
>>>
>>> Looking forward to hearing from you.
>>>
>>> Best.
>>> Alfredo.
>>>
>>> ===
>>> /PROJECT/bin/mri/python_virtualenvs/loris-mri-python/lib/python3.6/site-packages/bids/layout/validation.py:46:
>>> UserWarning: The ability to pass arguments to BIDSLayout that control
>>> indexing is likely to be removed in future; possibly as early as PyBIDS
>>> 0.14. This includes the `config_filename`, `ignore`, `force_index`, and
>>> `index_metadata` arguments. The recommended usage pattern is to initialize
>>> a new BIDSLayoutIndexer with these arguments, and pass it to the BIDSLayout
>>> via the `indexer` argument.
>>> warnings.warn("The ability to pass arguments to BIDSLayout that
>>> control "
>>>
>>> Connecting to:
>>> database: DATABASE
>>> username: USERDATABASE
>>> hostname: 111.222.333.444
>>> port : 3306
>>>
>>>
>>> Executing query:
>>> SELECT Value FROM Config WHERE ConfigID = (SELECT ID FROM
>>> ConfigSettings WHERE Name = %s);
>>>
>>> With arguments:
>>> ('default_bids_vl',)
>>>
>>>
>>> Executing query:
>>> SELECT Value FROM Config WHERE ConfigID = (SELECT ID FROM
>>> ConfigSettings WHERE Name = %s);
>>>
>>> With arguments:
>>> ('dataDirBasepath',)
>>>
>>> Loading the BIDS dataset with BIDS layout library...
>>>
>>> => BIDS dataset loaded with BIDS layout
>>>
>>> Grepping candidates from the BIDS layout...
>>> Validating the list of participants...
>>>
>>> ERROR: Participant ID mismatch between participants.tsv and raw data
>>> found in the BIDS directory/n
>>> ===
>>>
>>> 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 Mass General
>>> Brigham Compliance HelpLine at
>>> http://www.massgeneralbrigham.org/complianceline
>>> <http://secure-web.cisco.com/1qM_d-YnL441NX1CgLDc0-4p5P74OBrZe4qz8DQn4NKFJlMAA7HiKjibIOLkeFbmot5sDXcFfxupjvo_jX8vC9aYNvFDnADUwQFAF2ETaANXw3yIZaf8bb7_SvUXAkTxwK31eivXt_HlY2DxnGsZ739ls6VersNRKPQN2plxFNbqAzR65ZCFC8YSBrs5Vrcr1GWNsx7YN7RWdCvcDN1j8l1v9uD8Je4NlxsZBp9G86xq4w2ATmf4ENiL-6RShyNpajtkjZKD6TUD0FKl1yu9EdA/http%3A%2F%2Fwww.massgeneralbrigham.org%2Fcomplianceline>
>>> . 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.
>>>
>>> Please note that this e-mail is not secure (encrypted). If you do not
>>> wish to continue communication over unencrypted e-mail, please notify the
>>> sender of this message immediately. Continuing to send or respond to
>>> e-mail after receiving this message means you understand and accept this
>>> risk and wish to continue to communicate over unencrypted e-mail.
>>> _______________________________________________
>>> Loris-dev mailing list
>>> Loris-dev at bic.mni.mcgill.ca
>>> https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev
>>> <https://secure-web.cisco.com/1nZGLPRvHAc4QXkbuPkDbTk6X7cLRpZjuKhOBth4NO62r205kfGQbnAX-YD9BjpSJaYX2q-XFXkB_JSF0s5z2ahDn5jCwO30vrTUlIZlEANwK8y3vIbbTS3OKeQl5HWbDL3FviFQTAC2JkKwXTysKFx31cF_fdj3Ldph7SeZSr25P3BOdkNzQM7CwOgGsZ74Icj-bh17DcnTl_TpfPBvtKvWdT9JJgzhO4xgU1diPaWsF1-yCLwXh4xN8u993AJYONV8vaXR3KRoKV8-QxssqZw/https%3A%2F%2Fmailman.bic.mni.mcgill.ca%2Fmailman%2Flistinfo%2Floris-dev>
>>>
>>>
>>> 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 Mass General
>>> Brigham Compliance HelpLine at
>>> http://www.massgeneralbrigham.org/complianceline
>>> <http://secure-web.cisco.com/1AhAU1QrkHn5uAqLbnmi1HyXx_kpI9yR6ZBTDEz2E2EH9ZJ8W5lI94E700CC6tH7ISW-FmwwtetLtDvUs671_9WDXfhJBJZUlAUiC75p9k2iniolB83RMn1vpjTql7mdvGqhQFlpZCisj05nFxy4_7JaawBv-2YfBcGJkgmL4k4UTe3OZ3Q6CU-jPPmqEDNyFt7jVXNncRMqUUg9ZiUWmhABUAHol2wVTYpBugXYIZfYMj79LvUy54oxCyOtX5FCW00-m4IAVrvYB_EhkHxI5Qw/http%3A%2F%2Fwww.massgeneralbrigham.org%2Fcomplianceline>
>>> . 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.
>>>
>>> Please note that this e-mail is not secure (encrypted). If you do not
>>> wish to continue communication over unencrypted e-mail, please notify the
>>> sender of this message immediately. Continuing to send or respond to
>>> e-mail after receiving this message means you understand and accept this
>>> risk and wish to continue to communicate over unencrypted e-mail.
>>>
>>>
>>>
>>> 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 Mass General
>>> Brigham Compliance HelpLine at
>>> http://www.massgeneralbrigham.org/complianceline
>>> <http://secure-web.cisco.com/1Vs76oaBwBuqLoMP4tDeksrqcCgDkogMEbBScJ4ejcwSa6gekqJpFoL6YNIznACwU31BdOoVLyr1lD6sf6FJ0bhDvv_VDNM4ihqPNDRpk_MBie2PPM8xVjhZzqKoCHhcAwaJVO6JrBb8QVg0k78kxRXH7d0wKdNPAHrs292D3K2KcEskKWx2YgQ-McThsXUDOsdj4Y99wDiDj5fzeT-glwFo2ZGa6-7cdKO2jHZVoiG8_XlvkoA76TtLIZxN04JfUn5UFQZ0p3J-jLf5RR8u_7A/http%3A%2F%2Fwww.massgeneralbrigham.org%2Fcomplianceline>
>>> . 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.
>>>
>>> Please note that this e-mail is not secure (encrypted). If you do not
>>> wish to continue communication over unencrypted e-mail, please notify the
>>> sender of this message immediately. Continuing to send or respond to
>>> e-mail after receiving this message means you understand and accept this
>>> risk and wish to continue to communicate over unencrypted e-mail.
>>>
>>
>> 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 Mass General
>> Brigham Compliance HelpLine at
>> http://www.massgeneralbrigham.org/complianceline
>> <http://secure-web.cisco.com/1n2UbpIP1Hiy1wedtWg9s-6NXBNM5GXQsk4yul5KQtRtD-fpCcwhqxfc9xPmkoXTkvQiEilB7x5cMjoMnEfP7sVBe6N4BZFTL6lnTA5ZoU6_eL-QZrxz4bet8uKLeH8lFWIbsg3Tq1FqZpdjEzQ9aSVMRC-CNrE0-CJn7xfPqJefF9I1-_5OZcKb9QkXl2Rg_xjO8CfyirontcnUgEOHlJ5anCG65dp3TNqKwXi_HsVUusIi9c6KJxpEoiY-xH-7k_UAsbpirJkzRosIoJNyevA/http%3A%2F%2Fwww.massgeneralbrigham.org%2Fcomplianceline>
>> . 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.
>>
>> Please note that this e-mail is not secure (encrypted). If you do not
>> wish to continue communication over unencrypted e-mail, please notify the
>> sender of this message immediately. Continuing to send or respond to
>> e-mail after receiving this message means you understand and accept this
>> risk and wish to continue to communicate over unencrypted e-mail.
>>
>
>
> 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 Mass General
> Brigham Compliance HelpLine at
> http://www.massgeneralbrigham.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.
>
> Please note that this e-mail is not secure (encrypted). If you do not
> wish to continue communication over unencrypted e-mail, please notify the
> sender of this message immediately. Continuing to send or respond to
> e-mail after receiving this message means you understand and accept this
> risk and wish to continue to communicate over unencrypted e-mail.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20210607/55e70422/attachment-0001.html>
More information about the Loris-dev
mailing list