Versions Compared

Old Version 11

changes.mady.by.user Elizabeth So

Saved on

compared with

New Version Current

changes.mady.by.user Wendy Blumenthal

Saved on

Key

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

...

  • 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.

  • If an EHR does not allow null flavors for Patient’s Address State, Patient’s Address City, and Patient’s Address Zip Code, then valid values are acceptable for these elements instead of null flavors for Test Case 2. This will require manual review for these elements for Test Case 2 if mismatches are seen in the Test Data Conformance Events.