Versions Compared

Old Version 5

changes.mady.by.user Matthew Tiller

Saved on

compared with

New Version Current

changes.mady.by.user Elizabeth So

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Test Case 1 – Medications Administered Section
    1. The <id/@root> in the Indication template of the Medications Activity #1 (gemcitabine 38 MG/ML injectable solution) must be the same as the <id/@root> for the breast cancer Problem Observation (Malignant neoplasm of breast upper outer quadrant).
  2. Test Case 3 – Cancer Diagnosis Section
    1. The <id/@root> in the Reference Entry Relationship (CONF:1169-33192) of Cancer Diagnosis Observation # 1 (Lentigo Maligna/Hutchinson’s Melanotic Freckle) must be the same as the <id/@root> of Problem Observation #1 (Lentigo Maligna/Melanoma in situ of left upper limb/Malignant Melanoma of upper limb).
    2. The <id/@root> in the Reference Entry Relationship (CONF:1169-33192) of Cancer Diagnosis Observation # 2 (Nodular Melanoma) must be the same as the <id/@root> of Problem Observation #2 (Malignant melanoma of skin of scalp and neck).
  3. Test Case 3 – Procedures Section
    1. The <id/@root> in the Indication template of the Procedure Activity Procedure #1 (Excision of malignant neoplastic lesion of skin of extremities/Excision, malignant lesion including margins, trunk, arms, or leg/Excision of Left Upper Arm Skin) must be the same as the <id/@root> of Problem Observation #1 (Lentigo Maligna/Melanoma in situ of left upper limb/Malignant Melanoma of upper limb).
    2. The <id/@root> in the Indication template of the Procedure Activity Procedure #2 (Excision of malignant lesion of scalp and neck/Excision, malignant lesion including margins, scalp, neck, hands, feet, genitalia/Excision of Neck Skin, External Approach) must be the same as the <id/@root> of Problem Observation #2 (Malignant melanoma of skin of scalp and neck).

Test Case Details

Please see the Test Data Documentation for more details regarding the test cases.

Results

The results of each cancer event report submission are displayed in an accordion-style collapsible panel where a summary is displayed in a color-coded rectangular bar and more detailed results are displayed within the panel in several tabs. In the right-hand corner of the rectangular bar, the user can click on the X to remove the results for an entire submission.

...

The IG Conformance Events tab includes a summary of the IG conformance validation events above a table containing a row for each validation event.

Info

IG conformance events will be displayed/activation of the Schematron validation will occur only when a ClinicalDocument root element is present in the cancer event report at a minimum, as indicated below. Additional namespaces can be declared at the root element or in a child element elsewhere in the cancer event report.

Code Block
languagebash
<ClinicalDocument xmlns="urn:hl7-org:v3">
</ClinicalDocument>

Summary Statistics

The statistics represent the number of IG conformance validation events that fall into one of the following categories:

...

Column NameDescriptionFiltering Options
Status

Indicates the status of the validation event

  • Match: the value in the cancer event report submission for a data element matches the expected value specified in the test data
  • Mismatch: the value in the cancer event report submission for a data element does not match the expected value specified in the test data
Mismatch or Match
Actual ResultThe value found in the submitted report at the location specified in the "Location" column.ID 
Expected Result(s)The possible value(s) that could be used in the submitted report, as specified in the test data.ID 
Location Indicates the location in the submitted report where a data element corresponding to the test data can be found in terms of
  • Node Expression: an XPath expression
  • Line #
  • Column #
 Line #
Messages

Additional messages that the user may want to look at, which further explain the status and/or result of the validation event (i.e. why there is a mismatch).

Examples include:

  • "Mismatch is part of a group of XPath expressions, in which one must be satisfied for the event to be considered a match."

  • "Actual result matches expected result, but is not found in the expected location."

 
IDValidation event id, which users can provide in support requests when they have questions regarding a particular test data match or mismatch. The same validation id will correspond to the same match or mismatch tested for a given cancer event report submission.