XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive
    • US Quality Measures (FHIR)
    • 2.1.0
    • Clinical Quality Information
    • Quality Measure Implementation Guide Homepage
    • Hide

      Agreed, add a section (3.7) to the eCQMs page providing Must Support conformance expectations:

      Must Support:

      Conformance Requirement 3.17: Must Support Elements:

      For resource instances claiming to conform to Quality Measure IG profiles, Must Support on any profile data element SHALL be interpreted as follows:

      • Authoring systems and knowledge repositories SHALL be capable of populating all Must Support data elements.
      • Evaluating systems SHALL be capable of processing resource instances containing Must Support data elements without generating an error or causing the evaluation to fail.
      • In situations where information on a particular data element is not present and the reason for absence is unknown, authoring and repository systems SHALL NOT include the data elements in the resource instance.
        • For example, for systems using '9999' to indicate unknown data values, do not include '9999' in the resource instance.
      • When consuming resource instances, evaluating systems SHALL interpret missing data elements within resource instances as data not present for the artifact.
      • Submitting and receiving systems using Quality Measure artifacts to perform data exchange or artifact evaluation operations SHALL respect the must support requirements of the profiles used by the artifact to describe the data involved in the operation.
      Show
      Agreed, add a section (3.7) to the eCQMs page providing Must Support conformance expectations: Must Support: Conformance Requirement 3.17: Must Support Elements: For resource instances claiming to conform to Quality Measure IG profiles, Must Support on any profile data element SHALL be interpreted as follows: Authoring systems and knowledge repositories SHALL be capable of populating all Must Support data elements. Evaluating systems SHALL be capable of processing resource instances containing Must Support data elements without generating an error or causing the evaluation to fail. In situations where information on a particular data element is not present and the reason for absence is unknown, authoring and repository systems SHALL NOT include the data elements in the resource instance. For example, for systems using '9999' to indicate unknown data values, do not include '9999' in the resource instance. When consuming resource instances, evaluating systems SHALL interpret missing data elements within resource instances as data not present for the artifact. Submitting and receiving systems using Quality Measure artifacts to perform data exchange or artifact evaluation operations SHALL respect the must support requirements of the profiles used by the artifact to describe the data involved in the operation.
    • Bryn RHodes/ Anne Smith: 15-0-0
    • Clarification
    • Non-substantive

    Description

      The implementation guide does not discuss the meaning of the Must Support element in profile definitions. The guide should define must support for artifacts, as well as how must support for profiles used by measure specifications should be interpreted.

      Attachments

        Issue Links

          Activity

            People

              bryn.rhodes Bryn Rhodes
              bryn.rhodes Bryn Rhodes
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: