Versions Compared

Old Version 10

changes.mady.by.user Matthew Tiller

Saved on

compared with

New Version 11

changes.mady.by.user Elizabeth So

Saved on

Key

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

...

  • Display names indicated as a WARNING or ERROR during context-free validation, or indicated as a MISMATCH during context-specific validation, need to be evaluated for equivalent text because display names are non-normative.
    • More details: During context-free validation, the CRV checks display name attributes when explicitly defined by the Cancer Reporting IG. Any discrepancies are indicates as an error or warning. During context-specific validation, display names are checked against the test data, and any discrepancies are indicated as a mismatch. Because display names are non-normative, an error or warning may be indicated when in fact the display name in the submitted report has an equivalent meaning. The tester must evaluate the display names in a submitted report whenever a discrepancy is indicated with a display name.
    • If there is an error on the IG Conformance Events Tab or a mismatch on the Test Data Conformance Events tab for the Payer Type display name, the display name should be checked for similar meaning to the one specified in the test data. Since all value sets for Payer Type are not specified, specific codes are not required.
  • Multiple-choice values indicated as a WARNING might actually be valid.
    • More details: The Cancer Reporting IG defines several codes as multiple-choice. Meaning that a single value in a cancer report can come from multiple (usually 3) different code systems or value sets. Many times, two of the code systems/value sets will be bound to SHOULD and the third will be bound to MAY. The test data supplies a code from each code system and/or value set. For example, see "value (Histologic Type)" in the test data and conformance rule 1098-19207 in the IG and Schematron. Any of the provided values are valid. During context-free validation, only the code system/value set choices bound as SHOULD are checked. This means that if a value comes from one of the SHOULD code systems/value sets, then the conformance statement will pass. However, if the value does not come from a code system/value set bound to SHOULD, and even if it does come from a code system/value set bound to MAY, then a warning will be thrown. This warning must checked by the tester.

...

  • If there is a warning for doseQuantity (CONF:1098-7516), then manual inspection is required to verify that units are provided in consumable element itself or in doseQuantity/@unit attribute.
    • From the IG regarding this conformance rule:
      1. Pre-coordinated consumable: If the consumable code is a pre-coordinated unit dose (e.g., "metoprolol 25mg tablet") then doseQuantity is a unitless number that indicates the number of products given per administration (e.g., "2", meaning 2 x "metoprolol 25mg tablet" per administration) (CONF:1098-16878).
      2. Not pre-coordinated consumable: If the consumable code is not pre-coordinated (e.g., is simply "metoprolol"), then doseQuantity must represent a physical quantity with @unit, e.g., "25" and "mg", specifying the amount of product given per administration (CONF:1098-16879). .
  • If there is a mismatch displayed in the Test Data Conformance Events tab related to raceCode or sdtc:raceCode, check to make sure that the values in both the raceCode and sdtc:raceCode elements are not equal.