August 15, Re: Patient Relationship Categories and Codes VIA . Dear Acting Administrator Slavitt:

Similar documents
Prior to implementation of the episode groups for use in resource measurement under MACRA, CMS should:

The three proposed options for the use of CEHRT editions are as follows:

Re: CMS Patient Relationship Categories and Codes Second Request for Information

June 12, Dear Dr. McClellan:

CMS-0044-P; Proposed Rule: Medicare and Medicaid Programs; Electronic Health Record Incentive Program Stage 2

Our comments focus on the following components of the proposed rule: - Site Neutral Payments,

March 6, Dear Administrator Verma,

Care Management Framework:

August 25, Dear Ms. Verma:

RE: Request for Information: Centers for Medicare & Medicaid Services, Direct Provider Contracting Models

DA: November 29, Centers for Medicare and Medicaid Services National PACE Association

REPORT OF THE COUNCIL ON MEDICAL SERVICE. Hospital-Based Physicians and the Value-Based Payment Modifier (Resolution 813-I-12)

MEDICARE CCLF ANALYTICS: MEDICARE ANALYTICS DATA ENGINE (MADE)

Submitted electronically: RE: Request for Information Regarding Patient Relationship Categories and Codes

MEDICARE CCLF ANALYTICS: MEDICARE ANALYTICS DATA ENGINE (MADE)

THE ART OF DIAGNOSTIC CODING PART 1

August 25, Dear Acting Administrator Slavitt:

Seema Verma Centers for Medicare & Medicaid Services Department of Health and Human Services Attn: CMS-1696-P P.O. Box 8016 Baltimore, MD

April 26, Ms. Seema Verma, MPH Administrator Centers for Medicare & Medicaid Services. Dear Secretary Price and Administrator Verma:

Chapter 11. Expanding Roles and Functions of the Health Information Management and Health Informatics Professional

January 04, Submitted Electronically

Here is what we know. Here is what you can do. Here is what we are doing.

The Urgent Need for Better Claims Data to Support Value-Based Payment

ICD-10 is Financially Disastrous for Physicians

December 12, [Submitted online at:

Assignment of Medicare Fee-for-Service Beneficiaries

June 25, Dear Administrator Verma,

CMS Meaningful Use Incentives NPRM

Case-mix Analysis Across Patient Populations and Boundaries: A Refined Classification System

June 27, Dear Secretary Burwell and Acting Administrator Slavitt,

CMS-3310-P & CMS-3311-FC,

February 18, Re: Draft Trusted Exchange Framework and Common Agreement

Accountable Care Organizations. What the Nurse Executive Needs to Know. Rebecca F. Cady, Esq., RNC, BSN, JD, CPHRM

Uniform Data System. The Functional Assessment Specialists. June 21, 2011

Sharpen coding skills and reimbursement strategies during ICD-10 delay The Centers for Medicare & Medicaid Services (CMS) once again has extended the

1875 Connecticut Avenue, NW, Suite 650 P Washington, DC F

March 28, Dear Dr. Yong:

June 27, Dear Acting Administrator Slavitt:

May 6, Dear Dr. Blumenthal:

Leverage Information and Technology, Now and in the Future

Medicare Advantage PPO participation Termination - Practice Name (Tax ID #: <TaxID>)

American Health Information Management Association 2008 House of Delegates

August 15, Dear Mr. Slavitt:

Medicare Program; Revisions to Payment Policies Under the Physician Fee Schedule and Other Revisions to Part B for CY 2013 [File Code CMS 1590 P]

Adopting a Care Coordination Strategy

Submitted electronically:

Using Telemedicine to Enhance Meaningful Use Qualification

Re: Payment Policies under the Physician Fee Schedule Proposed Rule for CY 2014; 78 Fed. Reg. 43,281 (July 19, 2013); CMS-1600; RIN 0938-AR56

MACRA Frequently Asked Questions

September 27, RE: Medicaid Primary Care Rate Increase. Dear Administrator Tavenner:

December 3, 2010 BY COURIER AND ELECTRONIC MAIL

Examining the Differences Between Commercial and Medicare ACO Models

June 26, Dear Ms. Verma:

Describe the process for implementing an OP CDI program

CASE-MIX ANALYSIS ACROSS PATIENT POPULATIONS AND BOUNDARIES: A REFINED CLASSIFICATION SYSTEM DESIGNED SPECIFICALLY FOR INTERNATIONAL USE

Legal Issues in Medicare/Medicaid Incentive Programss

Evaluation & Management ( E/M ) Payment and Documentation Requirements

RE: Medicare Program; Request for Information Regarding the Physician Self-Referral Law

RE: CMS-1622-P; Medicare Program - Prospective Payment System and Consolidated Billing for Skilled Nursing Facilities for FY 2016

WHITE PAPER #2: CASE STUDY ON FRONTIER TELEHEALTH

September 8, 2015 EXECUTIVE SUMMARY

PERSONNEL REQUIREMENTS. March 9, 2018

Coding Alert. Michigan State Medical Society. Medicare Consultation Services Payment Policy

CMS Quality Payment Program: Performance and Reporting Requirements

Application of Proposals in Emergency Situations

The Patient Protection and Affordable Care Act Summary of Key Health Information Technology Provisions June 1, 2010

Medicare and Medicaid Programs: Electronic Health Record Incentive Program -- Stage 3 and Modifications to Meaningful Use in 2015 through 2017

September 2, Dear Mr. Slavitt:

Clinically Focused. Outcomes Oriented. Technology Driven. Chronic Care Management. eqguide. (CPT Codes 99490, 99487, 99489)

Outpatient Hospital Facilities

Why ICD-10 Is Worth the Trouble

August 15, Dear Mr. Slavitt:

3M Health Information Systems. The standard for yesterday, today and tomorrow: 3M All Patient Refined DRGs

Emerging Outpatient CDI Drivers and Technologies

Request for Information Regarding Accountable Care Organizations (ACOs) and Medicare Shared Savings Programs (CMS-1345-NC)

Draft for the Medicare Performance Adjustment (MPA) Policy for Rate Year 2021

Organization. Hospital to SNF Communication. Care Coordination Goals. Chasing the Perfect Handoff The Missing Link to Interoperability 7/18/2016

CMS Issues 2018 Proposed Physician Fee Schedule: What Spine Surgeons Should Know

Hospital Inpatient Quality Reporting (IQR) Program

The Patient-Centered Medical Home Model of Care

HHS to Delay Stage 2 of Meaningful Use. A. The Health Information Technology for Economic and Clinical Health Act

The Road to Clinical Transformation

OBSERVATION CARE EVALUATION AND MANAGEMENT CODES POLICY

2017/2018. KPN Health, Inc. Quality Payment Program Solutions Guide. KPN Health, Inc. A CMS Qualified Clinical Data Registry (QCDR) KPN Health, Inc.

Reinventing Health Care: Health System Transformation

Thank CMS for New Process for Evaluation of CPT Codes and Support Proposed Change to Eliminate the Use of Refinement Panels

2018 MIPS Quality Performance Category Measure Information for the 30-Day All-Cause Hospital Readmission Measure

Risk Adjusted Diagnosis Coding:

June 27, Dear Acting Administrator Slavitt:

SUMMARY. Workshop Summary WORKSHOP. Julia Langton, Kim McGrail, Sabrina Wong July 2015

Comments on Request for Information on Specialty Practitioner Payment Model Opportunities

ICD-10 Frequently Asked Questions for Providers Q Updates

DRAFT Complex and Chronic Care Improvement Program Template. (Not approved by CMS subject to continuing review process)

Compliant Documentation for Coding and Billing. Caren Swartz CPC,CPMA,CPC-H,CPC-I

Observation Care Evaluation and Management Codes Policy

LEGISLATIVE REPORT NORTH CAROLINA HEALTH TRANSFORMATION CENTER (TRANSFORMATION INNOVATIONS CENTER) PROGRAM DESIGN AND BUDGET PROPOSAL

July 21, Rayburn House Office Building 2368 Rayburn House Office Building Washington, DC Washington, DC 20515

Outcomes Measurement in Long-Term Care (LTC)

Centers for Medicare & Medicaid Services: Innovation Center New Direction

Our detailed comments and recommendations on the RFI are found on the following pages.

Transcription:

August 15, 2016 Mr. Andy Slavitt Acting Administrator Centers for Medicare & Medicaid Services U.S. Department of Health and Human Services Room 445-G, Hubert H. Humphrey Building 200 Independence Avenue, SW Washington, DC 20201 Re: Patient Relationship Categories and Codes VIA EMAIL Dear Acting Administrator Slavitt: On behalf of the American Health Information Management Association (AHIMA), I am responding to the Centers for Medicare & Medicaid Services (CMS) request for comments on the proposed patient relationship categories and codes. AHIMA is the national non-profit association of health information management (HIM) professionals. Serving 52 affiliated component state associations including the District of Columbia and Puerto Rico, AHIMA represents over 103,000 health information management professionals dedicated to effective health information management, information governance, and applied informatics. AHIMA s credentialed and certified HIM members can be found in more than 40 different employer settings in 120 different job functions consistently ensuring that health information is accurate, timely, complete, and available to patients and providers. AHIMA provides leadership through education and workforce development, as well as thought leadership in continuing HIM research and applied management for health information analytics. General Comments While AHIMA appreciates the goal to improve resource use measurement, this goal can only be achieved if the information collected is accurate and consistent. We do not believe the proposed patient relationship categories are sufficiently well-defined to produce accurate or meaningful data. AHIMA is also concerned that an approach for resource use attribution that involves identification of the relationship between a patient and an individual clinician is not aligned with team-based care. In a team-based environment, determining the relationship between a patient and a given clinician can be very difficult. The complexity of team-based care needs to be captured in any methodology designed to measure resource use.

Page 2 As described in greater detail below, determination of patient relationships will be especially challenging in the hospital inpatient environment, where patients are often being treated for multiple medical conditions, by multiple clinicians. We also believe the value of the information generated by reporting of patient relationship codes should be balanced against the administrative burden of collecting the information. Given the limited information that has been provided, it is not possible to fully understand how the proposed patient relationship categories will work in the real word, how these categories will be used, how they will interact with episode groups, how and where they will be reported on claims, and what the logistical reporting and workflow challenges might be. However, it is apparent that the extent of additional work that will be involved will be significant. It is not as clear whether this patient relationship reporting will provide useful information concerning the attribution of resource use. Operational issues surrounding the reporting of the relationship categories must be addressed well in advance of finalizing patient relationship categories. For example, where on the claim will the relationship codes be reported? Is it expected that one code per claim will be reported, or will relationship codes be reported per line item? Will revisions to the claim form be necessary, and if so, have necessary revisions been requested? Ideally, patient relationship categories and reporting logistics should be addressed in tandem, as the creation of usable categories that produce accurate information depends on an understanding of how and where the patient relationship codes will be reported. Responses to Questions: 1. Are the draft categories clear enough to enable physicians and practitioners to consistently and reliably self-identify an appropriate patient relationship category for a given clinical situation? As clinicians furnishing care to Medicare beneficiaries practice in a wide variety of care settings, do the draft categories capture the majority of patient relationships for clinicians? If not, what is missing? AHIMA believes the draft categories need to be better-defined. The categories are rather ambiguous and overlapping, and terms lack clear definitions. The distinction between acute and chronic is not well-defined. At what point does acute care become chronic care? If an acute condition evolves into a chronic condition during a lengthy hospitalization, would the patient relationship be considered acute or continuing care? We recommend using a different term than primary care provider when describing patient relationship categories, to avoid confusion with the conventional, well-established meaning of a patient s primary care provider. There may be multiple clinicians providing primary health care during an episode, especially in team-based care. In that scenario, will more than one clinician be allowed to report the primary relationship category for the same episode of care? If only one clinician can report category (i) for a given episode, extensive communication among clinicians involved in the patient s care may need to take place in order to determine who will report this category.

Page 3 AHIMA recommends that category (v) be redefined as Clinician who interprets tests ordered by another clinician in order to have an unambiguous definition and be clear and distinct from other relationship categories. Category (v) could potentially be confused with (iv). While non-patient-facing clinician is used in the examples for (v), this description is not included in the definition. The specialties listed in the examples and described as nonpatient-facing clinicians may have direct interaction with the patient in some instances. Also, while telemedicine providers are not face-to-face with the patient, they have direct patient interaction. The relationship categories do not fully capture all types of patient relationships. For example, acute on chronic scenarios are not addressed. There is also no category for a clinician providing preventive services. Post-acute care, such as rehabilitation following treatment of an acute injury, is also not covered. A clinician may fall into multiple categories for the same patient during a single episode (e.g., a physician may interpret a diagnostic test and later perform a procedure on the same patient). How would the relationship category be reported in this situation? How will hospitalists/intensivists determine the appropriate relationship category, since patients are shared during a single hospitalization? Will multiple hospitalists/intensivists be allowed to select the same category? How do telemedicine providers fit within the draft relationship categories? 2. As described above, we believe that there may be some overlap between several of the categories. To distinguish the categories, we are considering the inclusion of a patient relationship category that is specific to non-patient facing clinicians. Is this a useful and helpful distinction, or is this category sufficiently covered by the other existing categories? AHIMA does not believe a relationship category for non-patient-facing clinicians would be a useful distinction. As noted above, a non-patient-facing clinician such as a radiologist interpreting a test may also have direct interaction with a patient during the same episode. Also, a patient-facing clinician may have a similar level of accountability for resource costs to a physician interpreting a test (such as a clinician performing a minor procedure at the bedside). 3. Is the description of an acute episode accurately described? If not, are there alternatives we should consider? No, we do not believe the description of an acute episode is described accurately enough for clear and consistent reporting of the relationship categories. When does acute care become chronic? The line between acute and chronic can be blurred. And during a lengthy hospitalization, an acute condition may become chronic. Many patients, especially Medicare beneficiaries, have multiple medical conditions which may include a mix of acute and chronic conditions. How will the relationship category be

Page 4 determined if both acute and chronic care is provided by the same clinician during a single episode? 4. Is distinguishing relationships by acute care and continuing care the appropriate way to classify relationships? Are these the only two categories of care or would it be appropriate to have a category between acute and continuing care? We are concerned the definitions are ambiguous and distinctions between acute and chronic care are sometimes blurred. Patients might be reasonably categorized in more than one way. Some patient encounters do not clearly fall into acute and chronic categories, such as acute on chronic, post-acute care, and preventive services. Additional categories are needed for these types of care. Also, some medical conditions may not be easily or consistently classified as acute vs. chronic. For example, how would follow-up cancer care be categorized? 5. Are we adequately capturing Post-Acute Care clinicians, such as practitioners in a Skilled Nursing Facility or Long Term Care Hospital? As noted above, post-acute care, such as rehabilitation, is not adequately captured by the draft relationship categories. 6. What type of technical assistance and education would be helpful to clinicians in applying these codes to their claims? Extensive education of both clinicians and coding staff will need to be provided. Numerous clinical examples would be useful in demonstrating the appropriate use of each patient relationship category. 7. The clinicians are responsible for identifying their relationship to the patient. In the case where the clinician does not select the procedure and diagnosis code, who will select the patient relationship code? Are there particular clinician workflow issues involved? AHIMA believes that office staff, such as coding personnel, will primarily be responsible for selecting the patient relationship code. However, the clinician will still be responsible for understanding the distinctions between the relationship categories and providing sufficient documentation that a trained staff member can accurately select the most appropriate code. Both clinicians and the staff charged with selecting the code will require extensive education. To minimize administrative burden and increase accuracy, AHIMA recommends that the patient relationship categorization process be as simple and straightforward as possible, with as few categories as is reasonable to capture significant differences in relationships. Creation of too many categories increases administrative burden as well as the potential for overlap and ambiguity, resulting in inaccurate and useless information. The methodology

Page 5 needs to be simple enough for a non-clinician to be able to review the clinical documentation and assign the appropriate relationship category. Category definitions need to be very clear and distinct to ensure accurate code selection regardless of whether the clinician or an office staff member is selecting the code. Types of necessary workflow adjustments will vary by practice and setting of care. Modifications of electronic health record and practice management software will need to be undertaken, and since such modifications take time, comprehensive information regarding the definitions of the patient relationship categories and reporting logistics is needed as soon as possible. Guidance on the clinical documentation necessary to support the selected relationship category will also be needed. 8. CMS understands that there are often situations when multiple clinicians bill for services on a single claim. What should CMS consider to help clinicians accurately report patient relationships for each individual clinician on that claim? AHIMA recommends that CMS consider the use of modifiers to identify the patient relationship category, which we believe may be the simplest method of addressing the reporting of patient relationship categories when multiple clinicians bill for services on a single claim. The use of modifiers may also mitigate some of the challenges noted in our comments above, such as a single clinician with multiple relationships with the same patient during a single episode or multiple clinicians with the same patient relationship during a single episode. Conclusion AHIMA appreciates the opportunity to comment on the CMS patient relationships categories and codes. If we can provide any further information, or if there are any questions regarding this letter and its recommendations, please contact Sue Bowman, Senior Director of Coding Policy and Compliance at (312) 233-1115 or sue.bowman@ahima.org. In Sue s absence, please feel free to contact AHIMA s Vice President of Policy and Government Relations, Pamela Lane, at (202) 659-9440 or pamela.lane@ahima.org. Sincerely, Lynne Thomas Gordon, MBA, RHIA Chief Executive Officer cc: Sue Bowman, MJ, RHIA, CCS, FAHIMA Pamela Lane, MS, RHIA, CPHIMS