From AMORALESPINZON at BWH.HARVARD.EDU Mon Apr 19 16:38:01 2021 From: AMORALESPINZON at BWH.HARVARD.EDU (Morales Pinzon, Alfredo) Date: Mon, 19 Apr 2021 20:38:01 +0000 Subject: [Loris-dev] Pipeline Launch for BIDS datasets Message-ID: <8F265E9A-3958-4552-A666-50F3B1D927AE@bwh.harvard.edu> Dear LorisDev team, In the section ?5.2 - Pipeline Launch for BIDS datasets? the command line bids_import.py requires the option -p which is defined as -p, --profile : name of the python database config file in dicom-archive/.loris-mri In the example provided this option has the value ?database_config.py?, is this actually a python file? Where can I find it? How can I create it? The only file I have always had in .loris-mri is prod. Thank you in advance for your help. Regards, Alfredo. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cecile.madjar at mcin.ca Mon Apr 19 17:53:15 2021 From: cecile.madjar at mcin.ca (Cecile Madjar) Date: Mon, 19 Apr 2021 17:53:15 -0400 Subject: [Loris-dev] Pipeline Launch for BIDS datasets In-Reply-To: <8F265E9A-3958-4552-A666-50F3B1D927AE@bwh.harvard.edu> References: <8F265E9A-3958-4552-A666-50F3B1D927AE@bwh.harvard.edu> Message-ID: Hi Alfredo, You will find an example of the config file in the following link: https://github.com/aces/Loris-MRI/blob/main/dicom-archive/database_config_template.py Indeed, this is a python-based config file, which is different from the prod file that is perl-based. Hope this helps, C?cile On Mon, Apr 19, 2021 at 4:38 PM Morales Pinzon, Alfredo < AMORALESPINZON at bwh.harvard.edu> wrote: > Dear LorisDev team, > > In the section ?5.2 - Pipeline Launch for BIDS datasets > ? > the command line bids_import.py requires the option -p which is defined as > > -p, --profile : name of the python database config file in dicom-archive/.loris-mri > > In the example provided this option has the value ?database_config.py?, is > this actually a python file? Where can I find it? How can I create it? The > only file I have always had in .loris-mri is prod. > > Thank you in advance for your help. > > Regards, > Alfredo. > _______________________________________________ > 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: From AMORALESPINZON at BWH.HARVARD.EDU Wed Apr 21 12:53:14 2021 From: AMORALESPINZON at BWH.HARVARD.EDU (Morales Pinzon, Alfredo) Date: Wed, 21 Apr 2021 16:53:14 +0000 Subject: [Loris-dev] Pipeline Launch for BIDS datasets In-Reply-To: References: <8F265E9A-3958-4552-A666-50F3B1D927AE@bwh.harvard.edu> Message-ID: <2E5E8867-CA88-4473-8335-2E820B44B88E@bwh.harvard.edu> Hi C?cile, Thank you for pointing me to the template. Is there something else to be changed/set besides the mysql information? Best, Alfredo. On Apr 19, 2021, at 5:53 PM, Cecile Madjar > wrote: External Email - Use Caution Hi Alfredo, You will find an example of the config file in the following link: https://github.com/aces/Loris-MRI/blob/main/dicom-archive/database_config_template.py Indeed, this is a python-based config file, which is different from the prod file that is perl-based. Hope this helps, C?cile On Mon, Apr 19, 2021 at 4:38 PM Morales Pinzon, Alfredo > wrote: Dear LorisDev team, In the section ?5.2 - Pipeline Launch for BIDS datasets? the command line bids_import.py requires the option -p which is defined as -p, --profile : name of the python database config file in dicom-archive/.loris-mri In the example provided this option has the value ?database_config.py?, is this actually a python file? Where can I find it? How can I create it? The only file I have always had in .loris-mri is prod. Thank you in advance for your help. Regards, Alfredo. _______________________________________________ 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: From AMORALESPINZON at BWH.HARVARD.EDU Sat Apr 24 11:10:01 2021 From: AMORALESPINZON at BWH.HARVARD.EDU (Morales Pinzon, Alfredo) Date: Sat, 24 Apr 2021 15:10:01 +0000 Subject: [Loris-dev] BIDS upload in LORIS - Participants file Message-ID: Dear LorisDev team, I am launching the insertion pipeline in LORIS of a dataset in BIDS format. I am getting the following error: === 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... Traceback (most recent call last): File "bids_import.py", line 431, in main() File "bids_import.py", line 75, in main read_and_insert_bids(bids_dir, config_file, verbose, createcand, createvisit) File "bids_import.py", line 157, in read_and_insert_bids bids_reader = BidsReader(bids_dir, verbose) File "/data_/ipmsa/loris_data/IPMSA/bin/mri/python/lib/bidsreader.py", line 62, in __init__ self.participants_info = self.load_candidates_from_bids() File "/data_/ipmsa/loris_data/IPMSA/bin/mri/python/lib/bidsreader.py", line 114, in load_candidates_from_bids self.candidates_list_validation(participants_info) File "/data_/ipmsa/loris_data/IPMSA/bin/mri/python/lib/bidsreader.py", line 142, in candidates_list_validation for row in participants_info: TypeError: 'NoneType' object is not iterable === It looks like the file ?participants.tsv? is required in LORIS, is this correct? In the BIDS specification this file is not required (https://bids-specification.readthedocs.io/en/stable/03-modality-agnostic-files.html#participants-file) and there is no mention in LORIS documentation (https://github.com/aces/Loris-MRI/blob/main/docs/05-PipelineLaunchOptions.md#52---pipeline-launch-for-bids-datasets). Thank you in advance for your help. Best 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 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: From cecile.madjar at mcin.ca Mon Apr 26 09:12:43 2021 From: cecile.madjar at mcin.ca (Cecile Madjar) Date: Mon, 26 Apr 2021 09:12:43 -0400 Subject: [Loris-dev] BIDS upload in LORIS - Participants file In-Reply-To: References: Message-ID: Dear Alfredo, Indeed, the participants.tsv file is required for LORIS since this is the file being read to create participants when they need to be created (this way LORIS can populate some additional information like site, sex, date of birth and age). We thought this file was required in BIDS, which is probably why it was not documented. Ideal structure of the participants.tsv file: participant_id sex date_of_birth site Note: in release 24.0, a 'project' column will be added so that upon creation of a candidate, a project can be associated with it. We will definitely update the documentation. Thank you for letting us know! Hope this helps, C?cile On Sat, Apr 24, 2021 at 11:10 AM Morales Pinzon, Alfredo < AMORALESPINZON at bwh.harvard.edu> wrote: > Dear LorisDev team, > > I am launching the insertion pipeline in LORIS of a dataset in BIDS > format. I am getting the following error: > > === > 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... > Traceback (most recent call last): > File "bids_import.py", line 431, in > main() > File "bids_import.py", line 75, in main > read_and_insert_bids(bids_dir, config_file, verbose, createcand, > createvisit) > File "bids_import.py", line 157, in read_and_insert_bids > bids_reader = BidsReader(bids_dir, verbose) > File "/data_/ipmsa/loris_data/IPMSA/bin/mri/python/lib/bidsreader.py", > line 62, in __init__ > self.participants_info = self.load_candidates_from_bids() > File "/data_/ipmsa/loris_data/IPMSA/bin/mri/python/lib/bidsreader.py", > line 114, in load_candidates_from_bids > self.candidates_list_validation(participants_info) > File "/data_/ipmsa/loris_data/IPMSA/bin/mri/python/lib/bidsreader.py", > line 142, in candidates_list_validation > for row in participants_info: > TypeError: 'NoneType' object is not iterable > === > > It looks like the file ?participants.tsv? is required in LORIS, is this > correct? In the BIDS specification this file is not required ( > https://bids-specification.readthedocs.io/en/stable/03-modality-agnostic-files.html#participants-file) > and there is no mention in LORIS documentation ( > https://github.com/aces/Loris-MRI/blob/main/docs/05-PipelineLaunchOptions.md#52---pipeline-launch-for-bids-datasets > ). > > Thank you in advance for your help. > > Best 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 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. > _______________________________________________ > 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: From AMORALESPINZON at BWH.HARVARD.EDU Mon Apr 26 10:18:09 2021 From: AMORALESPINZON at BWH.HARVARD.EDU (Morales Pinzon, Alfredo) Date: Mon, 26 Apr 2021 14:18:09 +0000 Subject: [Loris-dev] BIDS upload in LORIS - Participants file In-Reply-To: References: Message-ID: <8C29CB41-5EEB-4150-916C-B447066AF593@bwh.harvard.edu> Dear Cecile, I am running Loris 23.0.2. If I upload a BIDS dataset in this version, what project will be used to link the Candidates? I believe a project with the name of the dataset, taken from the ?dataset_description.json?, will be created and the Candidates will be inserted under this project, is this correct? Best regards, Alfredo. On Apr 26, 2021, at 9:12 AM, Cecile Madjar > wrote: External Email - Use Caution Dear Alfredo, Indeed, the participants.tsv file is required for LORIS since this is the file being read to create participants when they need to be created (this way LORIS can populate some additional information like site, sex, date of birth and age). We thought this file was required in BIDS, which is probably why it was not documented. Ideal structure of the participants.tsv file: participant_id sex date_of_birth site Note: in release 24.0, a 'project' column will be added so that upon creation of a candidate, a project can be associated with it. We will definitely update the documentation. Thank you for letting us know! Hope this helps, C?cile On Sat, Apr 24, 2021 at 11:10 AM Morales Pinzon, Alfredo > wrote: Dear LorisDev team, I am launching the insertion pipeline in LORIS of a dataset in BIDS format. I am getting the following error: === 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... Traceback (most recent call last): File "bids_import.py", line 431, in main() File "bids_import.py", line 75, in main read_and_insert_bids(bids_dir, config_file, verbose, createcand, createvisit) File "bids_import.py", line 157, in read_and_insert_bids bids_reader = BidsReader(bids_dir, verbose) File "/data_/ipmsa/loris_data/IPMSA/bin/mri/python/lib/bidsreader.py", line 62, in __init__ self.participants_info = self.load_candidates_from_bids() File "/data_/ipmsa/loris_data/IPMSA/bin/mri/python/lib/bidsreader.py", line 114, in load_candidates_from_bids self.candidates_list_validation(participants_info) File "/data_/ipmsa/loris_data/IPMSA/bin/mri/python/lib/bidsreader.py", line 142, in candidates_list_validation for row in participants_info: TypeError: 'NoneType' object is not iterable === It looks like the file ?participants.tsv? is required in LORIS, is this correct? In the BIDS specification this file is not required (https://bids-specification.readthedocs.io/en/stable/03-modality-agnostic-files.html#participants-file) and there is no mention in LORIS documentation (https://github.com/aces/Loris-MRI/blob/main/docs/05-PipelineLaunchOptions.md#52---pipeline-launch-for-bids-datasets). Thank you in advance for your help. Best 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 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. _______________________________________________ Loris-dev mailing list Loris-dev at bic.mni.mcgill.ca https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-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 . 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: From AMORALESPINZON at BWH.HARVARD.EDU Mon Apr 26 12:39:54 2021 From: AMORALESPINZON at BWH.HARVARD.EDU (Morales Pinzon, Alfredo) Date: Mon, 26 Apr 2021 16:39:54 +0000 Subject: [Loris-dev] BIDS participants tvf and json file Message-ID: Dear LorisDev Team, I have three questions regarding the BIDS participants files for LORIS: 1. What is the format that LORIS will be expecting for the column date_of_birth in the participants.json file? 2. What are the values expected for the column sex in the participants.json file? M,F or Male, Female? 3. Does LORIS need the participants.json file? Best 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 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. From cecile.madjar at mcin.ca Mon Apr 26 13:14:18 2021 From: cecile.madjar at mcin.ca (Cecile Madjar) Date: Mon, 26 Apr 2021 13:14:18 -0400 Subject: [Loris-dev] BIDS participants tvf and json file In-Reply-To: References: Message-ID: Hi Alfredo, we are writing the documentation at the same time we are communicating. I created a PR with a detailed instruction and it contains answers to your questions: https://github.com/aces/Loris-MRI/pull/615/files In short: - for sex: any of M, F, female, male works (case insensitive so m, f, Female and Male works as well) - for date of birth: format = YYYY-MM-DD - for the participants.json, see the example given in the description of https://github.com/aces/Loris-MRI/pull/615/files Note: the support of the project is new and will be part of release LORIS-MRI 24 but there is no release scheduled soon. In the meantime, two solutions: - manually populate the project after the script has been run (not sure how realistic that is depending on your projects' need) - pull the code from this PR: https://github.com/aces/Loris-MRI/pull/558/files that adds the support for the project insertion in the candidate and session tables Hope this helps, C?cile On Mon, Apr 26, 2021 at 12:40 PM Morales Pinzon, Alfredo < AMORALESPINZON at bwh.harvard.edu> wrote: > Dear LorisDev Team, > > I have three questions regarding the BIDS participants files for LORIS: > > 1. What is the format that LORIS will be expecting for the column > date_of_birth in the participants.json file? > > 2. What are the values expected for the column sex in the > participants.json file? M,F or Male, Female? > > 3. Does LORIS need the participants.json file? > > Best 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 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. > > > _______________________________________________ > 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: From AMORALESPINZON at BWH.HARVARD.EDU Tue Apr 27 15:48:31 2021 From: AMORALESPINZON at BWH.HARVARD.EDU (Morales Pinzon, Alfredo) Date: Tue, 27 Apr 2021 19:48:31 +0000 Subject: [Loris-dev] BIDS participants tvf and json file In-Reply-To: References: Message-ID: Hi C?cile, Thank you for your response and the documentation. We are modifying our participants tsv and json file accordingly. I will pull to the PR you sent and test as soon as possible. I?ll keep you posted. In the mean time, I have two questions: 1. I assume that I have to create the sites in advance if I want them to be used in the BIDS importing script, right? 2. Our subject Ids do not follow the CandID of LORIS, for instance one subject folder is named ?sub-CFTY720D2306.0102.00001?, is this okay for LORIS?. I saw in the documentation that the participant ID is the PSCID of the candidate. However having the PSCID here won?t make much sense as that would imply that all the BIDS files having the subjectID will have to be renamed. Best, Alfredo. On Apr 26, 2021, at 1:14 PM, Cecile Madjar > wrote: External Email - Use Caution Hi Alfredo, we are writing the documentation at the same time we are communicating. I created a PR with a detailed instruction and it contains answers to your questions: https://github.com/aces/Loris-MRI/pull/615/files In short: - for sex: any of M, F, female, male works (case insensitive so m, f, Female and Male works as well) - for date of birth: format = YYYY-MM-DD - for the participants.json, see the example given in the description of https://github.com/aces/Loris-MRI/pull/615/files Note: the support of the project is new and will be part of release LORIS-MRI 24 but there is no release scheduled soon. In the meantime, two solutions: - manually populate the project after the script has been run (not sure how realistic that is depending on your projects' need) - pull the code from this PR: https://github.com/aces/Loris-MRI/pull/558/files that adds the support for the project insertion in the candidate and session tables Hope this helps, C?cile On Mon, Apr 26, 2021 at 12:40 PM Morales Pinzon, Alfredo > wrote: Dear LorisDev Team, I have three questions regarding the BIDS participants files for LORIS: 1. What is the format that LORIS will be expecting for the column date_of_birth in the participants.json file? 2. What are the values expected for the column sex in the participants.json file? M,F or Male, Female? 3. Does LORIS need the participants.json file? Best 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 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. _______________________________________________ Loris-dev mailing list Loris-dev at bic.mni.mcgill.ca https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-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 . 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: From cecile.madjar at mcin.ca Tue Apr 27 16:23:30 2021 From: cecile.madjar at mcin.ca (Cecile Madjar) Date: Tue, 27 Apr 2021 16:23:30 -0400 Subject: [Loris-dev] BIDS participants tvf and json file In-Reply-To: References: Message-ID: Hi Alfredo, Indeed, the sites will need to be created in advance. Regarding the BIDS subject ID, they do need to be sub- other LORIS will not know to which subject the images should be attached to. Sorry. C?cile On Tue, Apr 27, 2021 at 3:48 PM Morales Pinzon, Alfredo < AMORALESPINZON at bwh.harvard.edu> wrote: > Hi C?cile, > > Thank you for your response and the documentation. We are modifying our > participants tsv and json file accordingly. I will pull to the PR you sent > and test as soon as possible. I?ll keep you posted. > > In the mean time, I have two questions: > > 1. I assume that I have to create the sites in advance if I want them to > be used in the BIDS importing script, right? > > 2. Our subject Ids do not follow the CandID of LORIS, for instance one > subject folder is named ?sub-CFTY720D2306.0102.00001?, is this okay for > LORIS?. I saw in the documentation that the participant ID is the PSCID of > the candidate. However having the PSCID here won?t make much sense as that > would imply that all the BIDS files having the subjectID will have to be > renamed. > > Best, > Alfredo. > > On Apr 26, 2021, at 1:14 PM, Cecile Madjar wrote: > > External Email - Use Caution > > Hi Alfredo, > > we are writing the documentation at the same time we are communicating. I > created a PR with a detailed instruction and it contains answers to your > questions: https://github.com/aces/Loris-MRI/pull/615/files > > > In short: > - for sex: any of M, F, female, male works (case insensitive so m, f, > Female and Male works as well) > - for date of birth: format = YYYY-MM-DD > - for the participants.json, see the example given in the description of > https://github.com/aces/Loris-MRI/pull/615/files > > > Note: the support of the project is new and will be part of release > LORIS-MRI 24 but there is no release scheduled soon. In the meantime, two > solutions: > - manually populate the project after the script has been run (not sure > how realistic that is depending on your projects' need) > - pull the code from this PR: > https://github.com/aces/Loris-MRI/pull/558/files > > that adds the support for the project insertion in the candidate and > session tables > > Hope this helps, > > C?cile > > On Mon, Apr 26, 2021 at 12:40 PM Morales Pinzon, Alfredo < > AMORALESPINZON at bwh.harvard.edu> wrote: > >> Dear LorisDev Team, >> >> I have three questions regarding the BIDS participants files for LORIS: >> >> 1. What is the format that LORIS will be expecting for the column >> date_of_birth in the participants.json file? >> >> 2. What are the values expected for the column sex in the >> participants.json file? M,F or Male, Female? >> >> 3. Does LORIS need the participants.json file? >> >> Best 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 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. >> >> >> _______________________________________________ >> Loris-dev mailing list >> Loris-dev at bic.mni.mcgill.ca >> https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-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 . 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: From AMORALESPINZON at BWH.HARVARD.EDU Tue Apr 27 16:40:43 2021 From: AMORALESPINZON at BWH.HARVARD.EDU (Morales Pinzon, Alfredo) Date: Tue, 27 Apr 2021 20:40:43 +0000 Subject: [Loris-dev] BIDS participants tvf and json file In-Reply-To: References: Message-ID: Hi Cecile, Regarding the BIDS subject ID, they do need to be sub- other LORIS will not know to which subject the images should be attached to. Sorry. I thought the option ?-c, --createcandidate: to create BIDS candidates in LORIS (optional)? would take care of this. Regarding the visits/sessions, do they need to be created in advance as well? Best, Alfredo. On Apr 27, 2021, at 4:23 PM, Cecile Madjar > wrote: External Email - Use Caution Hi Alfredo, Indeed, the sites will need to be created in advance. Regarding the BIDS subject ID, they do need to be sub- other LORIS will not know to which subject the images should be attached to. Sorry. C?cile On Tue, Apr 27, 2021 at 3:48 PM Morales Pinzon, Alfredo > wrote: Hi C?cile, Thank you for your response and the documentation. We are modifying our participants tsv and json file accordingly. I will pull to the PR you sent and test as soon as possible. I?ll keep you posted. In the mean time, I have two questions: 1. I assume that I have to create the sites in advance if I want them to be used in the BIDS importing script, right? 2. Our subject Ids do not follow the CandID of LORIS, for instance one subject folder is named ?sub-CFTY720D2306.0102.00001?, is this okay for LORIS?. I saw in the documentation that the participant ID is the PSCID of the candidate. However having the PSCID here won?t make much sense as that would imply that all the BIDS files having the subjectID will have to be renamed. Best, Alfredo. On Apr 26, 2021, at 1:14 PM, Cecile Madjar > wrote: External Email - Use Caution Hi Alfredo, we are writing the documentation at the same time we are communicating. I created a PR with a detailed instruction and it contains answers to your questions: https://github.com/aces/Loris-MRI/pull/615/files In short: - for sex: any of M, F, female, male works (case insensitive so m, f, Female and Male works as well) - for date of birth: format = YYYY-MM-DD - for the participants.json, see the example given in the description of https://github.com/aces/Loris-MRI/pull/615/files Note: the support of the project is new and will be part of release LORIS-MRI 24 but there is no release scheduled soon. In the meantime, two solutions: - manually populate the project after the script has been run (not sure how realistic that is depending on your projects' need) - pull the code from this PR: https://github.com/aces/Loris-MRI/pull/558/files that adds the support for the project insertion in the candidate and session tables Hope this helps, C?cile On Mon, Apr 26, 2021 at 12:40 PM Morales Pinzon, Alfredo > wrote: Dear LorisDev Team, I have three questions regarding the BIDS participants files for LORIS: 1. What is the format that LORIS will be expecting for the column date_of_birth in the participants.json file? 2. What are the values expected for the column sex in the participants.json file? M,F or Male, Female? 3. Does LORIS need the participants.json file? Best 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 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. _______________________________________________ Loris-dev mailing list Loris-dev at bic.mni.mcgill.ca https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-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 . 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: From cecile.madjar at mcin.ca Tue Apr 27 17:26:32 2021 From: cecile.madjar at mcin.ca (Cecile Madjar) Date: Tue, 27 Apr 2021 17:26:32 -0400 Subject: [Loris-dev] BIDS participants tvf and json file In-Reply-To: References: Message-ID: Right. But it will use what is in the sub- to create the new PSCID, so in your case, the script will try to create a candidate with PSCID=CFTY720D2306.0102.00001 Sorry for the confusion. C?cile On Tue, Apr 27, 2021 at 4:40 PM Morales Pinzon, Alfredo < AMORALESPINZON at bwh.harvard.edu> wrote: > Hi Cecile, > > Regarding the BIDS subject ID, they do need to be sub- other LORIS > will not know to which subject the images should be attached to. Sorry. > > I thought the option ?-c, --createcandidate: to create BIDS candidates in > LORIS (optional)? would take care of this. > > Regarding the visits/sessions, do they need to be created in advance as > well? > > Best, > Alfredo. > > On Apr 27, 2021, at 4:23 PM, Cecile Madjar wrote: > > External Email - Use Caution > > Hi Alfredo, > > Indeed, the sites will need to be created in advance. > > Regarding the BIDS subject ID, they do need to be sub- other LORIS > will not know to which subject the images should be attached to. Sorry. > > C?cile > > On Tue, Apr 27, 2021 at 3:48 PM Morales Pinzon, Alfredo < > AMORALESPINZON at bwh.harvard.edu> wrote: > >> Hi C?cile, >> >> Thank you for your response and the documentation. We are modifying our >> participants tsv and json file accordingly. I will pull to the PR you sent >> and test as soon as possible. I?ll keep you posted. >> >> In the mean time, I have two questions: >> >> 1. I assume that I have to create the sites in advance if I want them to >> be used in the BIDS importing script, right? >> >> 2. Our subject Ids do not follow the CandID of LORIS, for instance one >> subject folder is named ?sub-CFTY720D2306.0102.00001?, is this okay for >> LORIS?. I saw in the documentation that the participant ID is the PSCID of >> the candidate. However having the PSCID here won?t make much sense as that >> would imply that all the BIDS files having the subjectID will have to be >> renamed. >> >> Best, >> Alfredo. >> >> On Apr 26, 2021, at 1:14 PM, Cecile Madjar wrote: >> >> External Email - Use Caution >> >> Hi Alfredo, >> >> we are writing the documentation at the same time we are communicating. I >> created a PR with a detailed instruction and it contains answers to your >> questions: https://github.com/aces/Loris-MRI/pull/615/files >> >> >> In short: >> - for sex: any of M, F, female, male works (case insensitive so m, f, >> Female and Male works as well) >> - for date of birth: format = YYYY-MM-DD >> - for the participants.json, see the example given in the description of >> https://github.com/aces/Loris-MRI/pull/615/files >> >> >> Note: the support of the project is new and will be part of release >> LORIS-MRI 24 but there is no release scheduled soon. In the meantime, two >> solutions: >> - manually populate the project after the script has been run (not sure >> how realistic that is depending on your projects' need) >> - pull the code from this PR: >> https://github.com/aces/Loris-MRI/pull/558/files >> >> that adds the support for the project insertion in the candidate and >> session tables >> >> Hope this helps, >> >> C?cile >> >> On Mon, Apr 26, 2021 at 12:40 PM Morales Pinzon, Alfredo < >> AMORALESPINZON at bwh.harvard.edu> wrote: >> >>> Dear LorisDev Team, >>> >>> I have three questions regarding the BIDS participants files for LORIS: >>> >>> 1. What is the format that LORIS will be expecting for the column >>> date_of_birth in the participants.json file? >>> >>> 2. What are the values expected for the column sex in the >>> participants.json file? M,F or Male, Female? >>> >>> 3. Does LORIS need the participants.json file? >>> >>> Best 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 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. >>> >>> >>> _______________________________________________ >>> Loris-dev mailing list >>> Loris-dev at bic.mni.mcgill.ca >>> https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-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 >> >> . 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: From AMORALESPINZON at BWH.HARVARD.EDU Tue Apr 27 17:30:27 2021 From: AMORALESPINZON at BWH.HARVARD.EDU (Morales Pinzon, Alfredo) Date: Tue, 27 Apr 2021 21:30:27 +0000 Subject: [Loris-dev] BIDS participants tvf and json file In-Reply-To: References: Message-ID: Hi C?cile, Great! Thank you for the clarification. I guess the same will apply for the visits/sessions. Best, Alfredo. On Apr 27, 2021, at 5:26 PM, Cecile Madjar > wrote: External Email - Use Caution Right. But it will use what is in the sub- to create the new PSCID, so in your case, the script will try to create a candidate with PSCID=CFTY720D2306.0102.00001 Sorry for the confusion. C?cile On Tue, Apr 27, 2021 at 4:40 PM Morales Pinzon, Alfredo > wrote: Hi Cecile, Regarding the BIDS subject ID, they do need to be sub- other LORIS will not know to which subject the images should be attached to. Sorry. I thought the option ?-c, --createcandidate: to create BIDS candidates in LORIS (optional)? would take care of this. Regarding the visits/sessions, do they need to be created in advance as well? Best, Alfredo. On Apr 27, 2021, at 4:23 PM, Cecile Madjar > wrote: External Email - Use Caution Hi Alfredo, Indeed, the sites will need to be created in advance. Regarding the BIDS subject ID, they do need to be sub- other LORIS will not know to which subject the images should be attached to. Sorry. C?cile On Tue, Apr 27, 2021 at 3:48 PM Morales Pinzon, Alfredo > wrote: Hi C?cile, Thank you for your response and the documentation. We are modifying our participants tsv and json file accordingly. I will pull to the PR you sent and test as soon as possible. I?ll keep you posted. In the mean time, I have two questions: 1. I assume that I have to create the sites in advance if I want them to be used in the BIDS importing script, right? 2. Our subject Ids do not follow the CandID of LORIS, for instance one subject folder is named ?sub-CFTY720D2306.0102.00001?, is this okay for LORIS?. I saw in the documentation that the participant ID is the PSCID of the candidate. However having the PSCID here won?t make much sense as that would imply that all the BIDS files having the subjectID will have to be renamed. Best, Alfredo. On Apr 26, 2021, at 1:14 PM, Cecile Madjar > wrote: External Email - Use Caution Hi Alfredo, we are writing the documentation at the same time we are communicating. I created a PR with a detailed instruction and it contains answers to your questions: https://github.com/aces/Loris-MRI/pull/615/files In short: - for sex: any of M, F, female, male works (case insensitive so m, f, Female and Male works as well) - for date of birth: format = YYYY-MM-DD - for the participants.json, see the example given in the description of https://github.com/aces/Loris-MRI/pull/615/files Note: the support of the project is new and will be part of release LORIS-MRI 24 but there is no release scheduled soon. In the meantime, two solutions: - manually populate the project after the script has been run (not sure how realistic that is depending on your projects' need) - pull the code from this PR: https://github.com/aces/Loris-MRI/pull/558/files that adds the support for the project insertion in the candidate and session tables Hope this helps, C?cile On Mon, Apr 26, 2021 at 12:40 PM Morales Pinzon, Alfredo > wrote: Dear LorisDev Team, I have three questions regarding the BIDS participants files for LORIS: 1. What is the format that LORIS will be expecting for the column date_of_birth in the participants.json file? 2. What are the values expected for the column sex in the participants.json file? M,F or Male, Female? 3. Does LORIS need the participants.json file? Best 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 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. _______________________________________________ Loris-dev mailing list Loris-dev at bic.mni.mcgill.ca https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-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 . 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. 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: From cecile.madjar at mcin.ca Wed Apr 28 08:30:38 2021 From: cecile.madjar at mcin.ca (Cecile Madjar) Date: Wed, 28 Apr 2021 08:30:38 -0400 Subject: [Loris-dev] BIDS participants tvf and json file In-Reply-To: References: Message-ID: Hi Alfredo, Exactly. The same will apply for the visits. Best, C?cile On Tue, Apr 27, 2021 at 5:30 PM Morales Pinzon, Alfredo < AMORALESPINZON at bwh.harvard.edu> wrote: > Hi C?cile, > > Great! Thank you for the clarification. > > I guess the same will apply for the visits/sessions. > > Best, > Alfredo. > > On Apr 27, 2021, at 5:26 PM, Cecile Madjar wrote: > > External Email - Use Caution > > Right. But it will use what is in the sub- to create the new PSCID, > so in your case, the script will try to create a candidate with > PSCID=CFTY720D2306.0102.00001 > > Sorry for the confusion. > > C?cile > > On Tue, Apr 27, 2021 at 4:40 PM Morales Pinzon, Alfredo < > AMORALESPINZON at bwh.harvard.edu> wrote: > >> Hi Cecile, >> >> Regarding the BIDS subject ID, they do need to be sub- other LORIS >> will not know to which subject the images should be attached to. Sorry. >> >> I thought the option ?-c, --createcandidate: to create BIDS candidates in >> LORIS (optional)? would take care of this. >> >> Regarding the visits/sessions, do they need to be created in advance as >> well? >> >> Best, >> Alfredo. >> >> On Apr 27, 2021, at 4:23 PM, Cecile Madjar wrote: >> >> External Email - Use Caution >> >> Hi Alfredo, >> >> Indeed, the sites will need to be created in advance. >> >> Regarding the BIDS subject ID, they do need to be sub- other LORIS >> will not know to which subject the images should be attached to. Sorry. >> >> C?cile >> >> On Tue, Apr 27, 2021 at 3:48 PM Morales Pinzon, Alfredo < >> AMORALESPINZON at bwh.harvard.edu> wrote: >> >>> Hi C?cile, >>> >>> Thank you for your response and the documentation. We are modifying our >>> participants tsv and json file accordingly. I will pull to the PR you sent >>> and test as soon as possible. I?ll keep you posted. >>> >>> In the mean time, I have two questions: >>> >>> 1. I assume that I have to create the sites in advance if I want them to >>> be used in the BIDS importing script, right? >>> >>> 2. Our subject Ids do not follow the CandID of LORIS, for instance one >>> subject folder is named ?sub-CFTY720D2306.0102.00001?, is this okay for >>> LORIS?. I saw in the documentation that the participant ID is the PSCID of >>> the candidate. However having the PSCID here won?t make much sense as that >>> would imply that all the BIDS files having the subjectID will have to be >>> renamed. >>> >>> Best, >>> Alfredo. >>> >>> On Apr 26, 2021, at 1:14 PM, Cecile Madjar >>> wrote: >>> >>> External Email - Use Caution >>> >>> Hi Alfredo, >>> >>> we are writing the documentation at the same time we are communicating. >>> I created a PR with a detailed instruction and it contains answers to your >>> questions: https://github.com/aces/Loris-MRI/pull/615/files >>> >>> >>> In short: >>> - for sex: any of M, F, female, male works (case insensitive so m, f, >>> Female and Male works as well) >>> - for date of birth: format = YYYY-MM-DD >>> - for the participants.json, see the example given in the description of >>> https://github.com/aces/Loris-MRI/pull/615/files >>> >>> >>> Note: the support of the project is new and will be part of release >>> LORIS-MRI 24 but there is no release scheduled soon. In the meantime, two >>> solutions: >>> - manually populate the project after the script has been run (not sure >>> how realistic that is depending on your projects' need) >>> - pull the code from this PR: >>> https://github.com/aces/Loris-MRI/pull/558/files >>> >>> that adds the support for the project insertion in the candidate and >>> session tables >>> >>> Hope this helps, >>> >>> C?cile >>> >>> On Mon, Apr 26, 2021 at 12:40 PM Morales Pinzon, Alfredo < >>> AMORALESPINZON at bwh.harvard.edu> wrote: >>> >>>> Dear LorisDev Team, >>>> >>>> I have three questions regarding the BIDS participants files for LORIS: >>>> >>>> 1. What is the format that LORIS will be expecting for the column >>>> date_of_birth in the participants.json file? >>>> >>>> 2. What are the values expected for the column sex in the >>>> participants.json file? M,F or Male, Female? >>>> >>>> 3. Does LORIS need the participants.json file? >>>> >>>> Best 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 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. >>>> >>>> >>>> _______________________________________________ >>>> Loris-dev mailing list >>>> Loris-dev at bic.mni.mcgill.ca >>>> https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-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 >>> >>> . 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. >> > > 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: