Login
Toggle sidebar

Lint: mri-nomenclature-guidelines

Strong List Colon Position
error

"These should be bold and use accepted acronyms (e.g. T1). If there is a single feature, the acronym should be followed by a colon, which should also be emboldened (e.g. T1: some feature). If there are multiple features or points to be made about a single sequence, then no colon should follow the acronym and instead then they should be listed as separate lines below the acronym. These should otherwise follow standard bulleted and numbered list guidelines. Below is an example which includes a number of additional style guides."

Line 6:57 · When enboldening an intro, the colon should not be bold. '<strong>T1</strong>). If there is a single feature, the acronym should be followed by a colon, which should also be emboldened (e.g. <strong>T1:</strong> some'

"T1: single feature in line with emboldened colon"

Line 9:1 · When enboldening an intro, the colon should not be bold. '<strong>T1: </strong>single'

"IP/OP: in-phase and out-of-phase"

Line 23:1 · When enboldening an intro, the colon should not be bold. '<strong>IP/OP:</strong> in'

"FLAIR: should be assumed to be T2-weighted and sometimes needs to be listed separately"

Line 25:1 · When enboldening an intro, the colon should not be bold. '<strong>FLAIR:</strong> should'

"GRE/SWI: often these can be included together"

Line 27:1 · When enboldening an intro, the colon should not be bold. '<strong>GRE/SWI:</strong> often'

"DWI/ADC: usually as a single heading, even if features are non-congruent"

Line 29:1 · When enboldening an intro, the colon should not be bold. '<strong>DWI/ADC:</strong> usually'

"MR spectroscopy: usually multiple lines, for each peak"

Line 31:1 · When enboldening an intro, the colon should not be bold. '<strong>MR spectroscopy: </strong>usually'

"MR perfusion: usually multiple lines, for each parameter"

Line 33:1 · When enboldening an intro, the colon should not be bold. '<strong>MR perfusion:</strong> usually'
List Punctuation
error

"if standard gadolinium then it may be omitted, or abbreviated to "Gd"."

Line 18:70 · Do not put full stops at the end of a list item.

"the field strength to be expressed in teslas, and usually abbreviated as 1.5 T, 3 T, etc. Note the space between the quantity and the letter."

Line 40:146 · Do not put full stops at the end of a list item.
Strong
warning

"These should be bold and use accepted acronyms (e.g. T1). If there is a single feature, the acronym should be followed by a colon, which should also be emboldened (e.g. T1: some feature). If there are multiple features or points to be made about a single sequence, then no colon should follow the acronym and instead then they should be listed as separate lines below the acronym. These should otherwise follow standard bulleted and numbered list guidelines. Below is an example which includes a number of additional style guides."

Line 6:57 · Generally, don't use bold in text: '<strong>T1</strong>'

"These should be bold and use accepted acronyms (e.g. T1). If there is a single feature, the acronym should be followed by a colon, which should also be emboldened (e.g. T1: some feature). If there are multiple features or points to be made about a single sequence, then no colon should follow the acronym and instead then they should be listed as separate lines below the acronym. These should otherwise follow standard bulleted and numbered list guidelines. Below is an example which includes a number of additional style guides."

Line 6:190 · Generally, don't use bold in text: '<strong>T1:</strong>'

"T1: single feature in line with emboldened colon"

Line 9:1 · Generally, don't use bold in text: '<strong>T1: </strong>'

"T2"

Line 11:1 · Generally, don't use bold in text: '<strong><strong>T2</strong>'

"T1 C+ (agent)"

Line 17:1 · Generally, don't use bold in text: '<strong>T1 C+ (agent)</strong>'

"IP/OP: in-phase and out-of-phase"

Line 23:1 · Generally, don't use bold in text: '<strong>IP/OP:</strong>'

"FLAIR: should be assumed to be T2-weighted and sometimes needs to be listed separately"

Line 25:1 · Generally, don't use bold in text: '<strong>FLAIR:</strong>'

"GRE/SWI: often these can be included together"

Line 27:1 · Generally, don't use bold in text: '<strong>GRE/SWI:</strong>'

"DWI/ADC: usually as a single heading, even if features are non-congruent"

Line 29:1 · Generally, don't use bold in text: '<strong>DWI/ADC:</strong>'

"MR spectroscopy: usually multiple lines, for each peak"

Line 31:1 · Generally, don't use bold in text: '<strong>MR spectroscopy: </strong>'

"MR perfusion: usually multiple lines, for each parameter"

Line 33:1 · Generally, don't use bold in text: '<strong>MR perfusion:</strong>'
Acronyms
warning

"IP/OP: in-phase and out-of-phase"

Line 23:12 · 'OP' has no definition. Spell it out if it's unfamiliar to the audience.

"When providing images in a case, it is acceptable to include the TR and TE values (and flip angle, if appropriate) in the "image/stack specific findings" section of case images. In fact, this may be desirable if the pulse sequence is atypical. Other technical data is also appropriate in this section (such as the phase time of an IP/OP sequence in milliseconds (ms))."

Line 36:69 · 'TR' has no definition. Spell it out if it's unfamiliar to the audience.

"When providing images in a case, it is acceptable to include the TR and TE values (and flip angle, if appropriate) in the "image/stack specific findings" section of case images. In fact, this may be desirable if the pulse sequence is atypical. Other technical data is also appropriate in this section (such as the phase time of an IP/OP sequence in milliseconds (ms))."

Line 36:76 · 'TE' has no definition. Spell it out if it's unfamiliar to the audience.

"When providing images in a case, it is acceptable to include the TR and TE values (and flip angle, if appropriate) in the "image/stack specific findings" section of case images. In fact, this may be desirable if the pulse sequence is atypical. Other technical data is also appropriate in this section (such as the phase time of an IP/OP sequence in milliseconds (ms))."

Line 36:338 · 'OP' has no definition. Spell it out if it's unfamiliar to the audience.

"if providing a zoomed image of an MRI finding, provide the field of view (FOV) and matrix information in "image/stack specific findings""

Line 44:79 · 'FOV' has no definition. Spell it out if it's unfamiliar to the audience.
Headings Valid
warning

Expected headings

  • H1 Terminology
  • H1 Usage
  • H1 Epidemiology
  • H2 Risk factors
  • H2 Associations
  • H1 Clinical presentation
  • H2 Complications
  • H1 Diagnosis
  • H2 Diagnostic criteria
  • H2 Diagnostic clues
  • H1 Pathology
  • H2 Aetiology
  • H2 Location
  • H2 Classification
  • H2 Macroscopic appearance
  • H2 Microscopic appearance
  • H2 Immunophenotype
  • H2 Markers
  • H2 Genetics
  • H1 Radiographic features
  • H2 Plain radiograph
  • H2 Mammography
  • H2 Antenatal ultrasound
  • H2 Transoesophageal echocardiography
  • H2 Ultrasound
  • H2 CT
  • H3 Dual-energy CT
  • H2 Angiography (DSA)
  • H2 MRI
  • H2 CT/MRI
  • H2 Nuclear medicine
  • H3 PET-CT
  • H3 PET-MRI
  • H1 Radiology report
  • H1 Treatment and prognosis
  • H2 Complications
  • H1 History and etymology
  • H1 Differential diagnosis
  • H2 Clinical differential diagnosis
  • H1 Practical points
  • H1 See also

"Articles"

Line 2:1 · "Articles" is not a recognised heading for this article type.

"MRI"

Line 4:1 · "MRI" is under the wrong parent heading (found under "Articles").

"Cases"

Line 35:1 · "Cases" is not a recognised heading for this article type.

"General points"

Line 48:1 · "General points" is not a recognised heading for this article type.