MESA/Report Template Creator

From IHEWiki

Jump to: navigation, search

MESA/Report Template Creator


MRRT - Management of Radiology Report Templates profile

This section describes test cases associated with the MRRT Profile.

Test Case 5000: MRRT Sample Report Template

The purpose of this test is for the Report Template Creator to create sample radiology report templates using its application, and then to upload those sample templates into gazelle.

We want you to create templates:

-- that represent the template-creating capabilities of your application

-- that incorporate as many of the template structures defined in the MRRT profile as possible

The better the samples you provide, the better interoperability testing we will have.

We ask you to upload your samples at least 2 weeks prior to the published pre-Connectathon test deadline.


  1. Using your Report Template Creator application, create a template using this guidance:
    1. the report template should contain at least on entry under coded_content
    2. Include at least one TEXT-type field in the report template
    3. Include at least one NUMBER-type field in the report template
    4. Include at least one selection list field in the report template
    5. Include at least one DATE-type field in the report template
    6. Include at least one TIME-type field in the report template
    7. You may optionally include a MERGE-type field in your report template
    8. You may include other content as long as it follows the format specified for MRRT report templates
  2. Finally, upload the report template you created into the samples area of gazelle:
    1. Access gazelle menu Connectathon / List of samples
    2. On the Sample to share tab for your test system, find the MRRT entry
    3. Upload your samples. We encourage you to upload multiple samples
    4. For each uploaded sample, be sure to document value of the template's templateUID within the sample entry.
    5. After you have finished uploading, create a simple text file indicating that the task is complete, and upload that .txt file into gazelle as the test log for this test. This is the signal that you have provided your samples.


Your test partners -- Report Template Managers and Report Creators -- will access your samples in advance of the connectathon and test them in your lab. The goal is to avoid surprises at the connectathon.

Test Case 5002: MRRT Report Template Structure Evaluation

In this test, we manually inspect a report template created by the Report Template Creator using its application in test 5000. See the Instructions in test 5000 for guidance on creating the template.


  1. Read the Instructions for test 5000.
  2. If your report template is ready for evaluation, create another text file (similar to what you created for 5000) and upload that for 5002. This will signal that you are ready for evaluation


We will use the same evaluation that we will perform during the Connectathon using Connectathon test MRRT_Report_Template_Structure"'. This looks for many, but not all, of the requirements in MRRT (RAD TF-3:8.1 Report Template Structure).

The evaluation from the connectathon test is duplicated here:

  1. The report template begins with one [1..1] HTML5 DOCTYPE declaration: <!DOCTYPE html>
  2. The template contains exactly one [1..1] html element
    1. The html element contains exactly one [1..1] head element
      1. The head element contains exactly one [1..1] title element
      2. The head element contains exactly one [1..1] meta element containing the character set used: <meta charset="UTF-8">
      3. The head element contains meta elements containing these Dublin Core a metadata elements:
        1. dcterms:title (required) Note: this title must have the same value as the head/title element
        2. dcterms:identifier containing an OID(required)
        3. dcterms:type (required) with value IMAGE_REPORT_TEMPLATE
        4. dcterms:publisher (required)
        5. dcterms:rights (required)
        6. dcterms:license (required)
        7. dcterms:date (required)
        8. dcterms:creator (required)
        9. dcterms:contributor (optional)
        10. dcterms:relation (optional)
        11. dcterms:language (optional)
      4. The head element may contain a style element for internal CSS style elements and or a link element for CSS files.
      5. The head element contains exactly one [1..1] script element
        1. The script element is assigned a type of "text/xml"
        2. The script element contains exactly one [1..1] template_attributes element
        3. The template_attributes element may contain zero or more of these non-Dublin core metadata elements
          1. top-level-flag (optional)
          2. status (optional) if provided, one of DRAFT, ACTIVE, RETIRED
          3. user-list (optional)
          4. provider-group-list (optional)
        4. The template_attributes element may contain zero or more term elements containing additional coded content applicable to the entire template:
          1. Each term element contains one code_meaning, one code_value, and one coding_scheme_designator. The coding_scheme_designator must be encoded as an OID (not a string).
        5. The template_attributes element contains one coded_content element
          1. The coded content element contains zero or more [0..*] entry elements encoded with code_meaning, code_value, and coding_scheme_designator as described above.
    2. The html element contains exactly one [1..1] body element
      1. The body element contains at least one [1..*] section element
        1. Each section element contains a data-section-name
        2. Each section element contains exactly one [1..1] header element
          1. The header contains a class attribute indicating the section level, eg. <header class="level1">
        3. Each section element contains at least one paragraph <p> element containing the section content.
Personal tools