Skip to content

Commit

Permalink
Update Readme with Technical Instructions
Browse files Browse the repository at this point in the history
  • Loading branch information
PARENCHIMA authored Jul 12, 2019
1 parent 94a5767 commit ca7b3a2
Showing 1 changed file with 29 additions and 2 deletions.
31 changes: 29 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# Renal MRI protocols
# Purpose

This repository holds a collection of renal MRI acquisition protocols that are compliant with the PARENCHIMA technical recommendations for clinical renal MRI put forward by Task force 1.2:

Expand All @@ -10,4 +10,31 @@ The published papers will list the recommendations in vendor-neutral language, a

The list of protocols in this respository is dynamic and will be updated as and when the recommendations are revised.

If you have protocols that are compliant with the recommendations and that you would like to share, please create a pull request. They will be revised by the chairs of the expert panels for compliance with the recommendations before merging with the master repository.
# Contribute

If you have protocols that are compliant with the recommendations and that you would like to share, please contact Dr. Pim Pullens (Pim.Pullens@uzgent.be, University Hospital Ghent, Belgium). He will collate the data and forward to the expert panels who will check for compliance with the recommendations before merging with the master repository.

The following data and materials must be provided for each protocol:

1. An ordered list of protocol authors for credit
2. A reference to the paper (or study) where the protocol is applied
3. Scanner type, software version and coil info

For Siemens:

1. PDF output of the protocol (mandatory)
2. If possible, edx/exar1 files
3. At least one DICOM file for each protocol step if possible

For Philips:

1. Text output of each sequence in the protocol (mandatory)
2. ExamCard if possible
3. At least one DICOM file for each protocol step if possible

For GE:

1. PDF file of the protocol (mandatory)
2. At least one DICOM file of each sequence in the protocol (mandatory)
3. Protocol Exchange files if possible
(Note: We need DICOM and/or Protocol Exchange files, because the information in the PDF is limited)

0 comments on commit ca7b3a2

Please sign in to comment.