The creation of risk profiles could discriminate against vulnerable patients or lead to barriers to needed patient care. This use case needs the additiona of significant patient protections. - CDex #306

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • US Da Vinci CDex (FHIR)
    • STU3
    • Financial Mgmt
    • (many)
    • CDex Build Accurate
    • Hide

      The goal of this use case is to establish risk adjustment for value base care reimbursement and not to impact the members eligibility for, or cost of, coverage.

      While we understand and agree with your concern, there is no intent in the specific use case cited to use the information to disadvantage the member.

      Show
      The goal of this use case is to establish risk adjustment for value base care reimbursement and not to impact the members eligibility for, or cost of, coverage. While we understand and agree with your concern, there is no intent in the specific use case cited to use the information to disadvantage the member.
    • Robert Dieterle / Jay Lyle: 3-0-2

      Existing Wording: Payers need to create complete, accurate risk profiles for members

      Comment:

      Risk profiles can be used to discriminate against patients or delay care. This use case fails to provide sufficient protections to ensure patient access to care. Profiling is often leveraged to deny claims or patient coverage for services and can increase burdensome prior authorization for a patient's needed medication, services, or devices. The AMA strongly recommends CDex use cases be scoped to accommodate payment, billing, and narrowly defined "health care operations".

      Summary:

      The creation of risk profiles could discriminate against vulnerable patients or lead to barriers to needed patient care. This use case needs the additiona of significant patient protections.

            Assignee:
            Unassigned
            Reporter:
            Terrence Cunningham
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: