1 / 67

Fox Systems Inc.

Fox Systems Inc. National Provider Identifier (NPI) Presentation to Arizona Chapter of HIMSS. Agenda. Introduction to Fox Systems Inc. Current Status of NPI Enumeration What is the NPI, and What is it Not? Need for Compliance NPI Compliance Timelines Benefits of NPI

ivanbritt
Download Presentation

Fox Systems Inc.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Fox Systems Inc. National Provider Identifier (NPI) Presentation to Arizona Chapter of HIMSS

  2. Agenda • Introduction to Fox Systems Inc. • Current Status of NPI Enumeration • What is the NPI, and What is it Not? • Need for Compliance • NPI Compliance Timelines • Benefits of NPI • Who Can and Cannot Get an NPI? • Provider Subparts • Applying for an NPI

  3. Agenda • Applying for an NPI • Provider Subparts • Provider Taxonomy • NPI Impact • Compliance Strategies and Issues • Next Steps • How FOX can Help your Organization

  4. Fox Systems Inc. • Founded in 1987, FOX is a women-owned, business headquartered in Scottsdale, AZ which specializes in healthcare management and system consulting and solution services • FOX has provided system, management and HIPAA consulting and integration services to CMS and to more than 30 state Medicaid, public health, and behavioral health programs as well as other payers, providers, and MCOs

  5. Fox Systems Inc. • Our customers are large and diverse, and include CMS, public and private sector payers, providers, managed care organizations, and Native tribes including. • DHHS Office for Civil Rights • CMSO - Medicaid • SAMHSA • Veterans Administration • Blue Cross and Blue Shield plans • Delta Dental Plans • Medicaid state agencies • Medicaid contractors • Hospitals, clinics, and other providers • Managed care organizations

  6. Fox Systems Inc. • We have strong systems, business process, and operations expertise in all areas of healthcare operations including the following: • Claims processing • Beneficiary eligibility • Provider enrollment/certification/credentialing • Benefit plan management • Pharmacy benefits management • Managed care • Case management/disease management • Utilization review • Fraud and abuse detection • Data warehouse/decision support • Client registries

  7. Fox Systems Inc. • Examples of large, complex healthcare clients served by FOX include: • State of Arizona – developed 1st Medicaid managed care system (PMMIS) • State of Florida Medicaid Program – Medicaid contractor and system procurement and QA • County of Los Angeles enterprise-wide HIPAA Security assessment • County of Los Angeles Department of Health Services – HIPAA TCS and Security assessment and gap analysis • LA Care Health Plan - implementation of HIPAA translator, system integration, and system maintenance • State of Oregon Medicaid – implementation of HIPAA translator, system integration and maintenance • TennCare Program – Medicaid contractor and system procurement and QA • County HIPAA assessments in Hillsborough (FL), Broward (FL), Henrico (VA), Montgomery (MD) and San Diego (CA)

  8. Fox Systems Inc. • FOX has been providing services to CMS (formerly HCFA) since the early 1990s. Previous CMS projects included: • Development of Medicaid national fraud and abuse Best Practices Guides (SURS Best Practices) • Development of the national Early, Periodic Screening, Diagnosis and Treatment (EPSDT) system design for Medicaid • Performed Y2K risk assessment and remediation monitoring for Medicaid systems nationally • Performed HIPAA impact analysis for Medicaid systems nationally including development of the Medicaid HIPAA Compliance Concept Model (MHCCM) and supporting software • Provided support to DHHS Office for Civil Rights in responding to emailed HIPAA questions (AskHIPAA FAQs) from providers and other HIPAA entities

  9. Fox Systems Inc. • Currently, FOX is assisting CMS in: • The development of the new Medicaid Information Technology Architecture (MITA) for future Medicaid systems • The development of new system certification criteria (qualifying for enhanced FFP) for Medicaid systems nationally including HIPAA and NPI compliance

  10. Fox Systems Inc. • Fox Systems was selected by CMS to be the NPI Enumerator through May 23, 2010 and has the responsibility for: • Performing the functions required to carry out the basic operations of assigning National Provider Identifiers (NPIs) to health care providers • Using the National Plan and Provider Enumeration System (NPPES), developed and maintained by CGI-AMS, as the basic tool • Performing activities including: • Providing paper applications • Data entry of applications • Notifying providers about new NPIs issued • Resolution of pended applications • Mailing and correspondence • Call center-based customer service

  11. Fox Systems Inc. • As NPI Enumerator, FOX is also tasked to work with provider organizations and other qualified entities that wish to submit files through Electronic File Interchange (EFI) • Validate the organization’s identity and establish accounts • Work with organizations to determine if their providers have NPIs • Reset web users’ passwords and user IDs • Maintain a call center for providers • EFI was originally scheduled for implementation during the Summer of 2005 but has been delayed

  12. Fox Systems Inc. • As Enumerator, FOX is not responsible for: • NPI provider outreach and training (CMS) • Operating or maintaining the NPPES or the NPI Website (other CMS contractor) • Determining the establishment of subparts (provider responsibility) • Determining provider taxonomies (provider responsibility) • Answering policy questions (CMS)

  13. Current Enumeration Status • Over 113,000 providers enumerated through August 2005 • Estimated 3-4 million providers will eventually be enumerated (rough guess because depends on provider designation of subparts)

  14. What is the NPI? • The NPI is one of the required HIPAA identifiers to be used in “standard” electronic health care transactions. • It is a unique and permanent healthcare provider identifier consisting of 10 numeric positions, preceded with “80840,” per the National Committee for Information Technology Standards .284 standard • An NPI is inactivated only upon death or dissolution of the health care provider.

  15. What is the NPI? • NPI will replace existing legacy provider numbers used for billing, servicing, referring, etc. including: • UPIN • Medicaid Provider Number • Medicare Provider Number • Blue Cross and Blue Shield Numbers • Other internal proprietary healthplan provider numbers

  16. Need for Compliance • Required whenever the HIPAA Implementation Guides require a provider identifier in a transaction, i.e., needed in order to continue to conduct Electronic Data Interchange involving: • Claims and encounters • Claim status and inquiry • Payments • COB • Remittances • Eligibility inquiries • Prior authorizations and referrals • Evolving new HIPAA transactions (e.g.., X12 855 provider enrollment) and updates of current transactions will also require use of the NPI. • Failure to abide by the rules set forth in the HIPAA NPI Final Rule will lead to various sanctions.

  17. What the NPI is NOT • An NPI will not: • Guarantee reimbursement by health plans • Enroll providers in health plans • Make providers covered entities • Require providers to conduct electronic transactions • While it is required for HIPAA EDI, it is not required for internal use within a healthcare organization as long as it is able to be mapped to internally used legacy identifiers but relationships must be “one to one”, “one to many”, or “many to one”. Not “many to many”.

  18. NPI Compliance Timelines • January 23, 2004 – Final Rule published • May 23, 2005 – Health care providers (HCPs) can begin applying for NPIs • Compliance dates: • May 23, 2007 – all covered entities including payers except for small health plans • May 23, 2008 – small health plans

  19. Benefits of NPI • Simplify healthcare transaction processing including claims and COB, patient eligibility and enrollment functions, provider enrollment, etc., and eventually reduce healthcare administrative costs • Improve the quality of care • Improve UM, UR and fraud and abuse detection

  20. Who Can Get an NPI? • Any “health care provider” • Both covered and noncovered (per HIPAA definition) entity providers • Individuals: Physicians, dentists, nurses, chiropractors, others • Organizations: Hospitals, ambulatory care facilities, laboratories, HMOs, group practices, others • Subparts of providers

  21. Who Can Get an NPI? • Noncovered healthcare providers may also apply for NPIs: • Being assigned NPIs does not make providers covered entities • There is no requirement for noncovered providers to obtain or use NPIs • NPIs can be used on paper transactions

  22. Who Cannot Get an NPI? • Non-healthcare providers such as: • Social service providers under a Medicaid Waiver program • Housekeepers • Non-medical transportation. • This means that many providers (non-healthcare) on payer and other healthplan networks will not require an NPI

  23. Provider Subparts • A provider is a distinct legal entity • Subpart is not another legal entity; it furnishes health care, e.g.. hospital unit, member of chain • A provider’s subparts does not necessarily correlate to a hybrid entity, a health care component, or an organized health care arrangement • An individual is not a provider subpart

  24. Provider Subparts • Covered provider is responsible for determining subpart’s need for NPI and applying for subpart NPI applications • Covered provider is responsible for all enumerated subparts’ compliance with NPI Rule

  25. NPI Applications • The Current NPI Enumeration Process • Provider completes application form to apply for NPI: • Can file electronically through Web or on paper to NPI Enumerator (FOX) • Application is processed by NPPES with: -- Data editing -- Data validation -- Duplicate application detection • Provider receives notification of NPI • Provider responsible for notifying health plans and other trading partners

  26. NPI Applications • Information collected on application for NPI used for assignment of NPI is matched against previously submitted NPI applications • Different information required for individuals and organizations • Limited to minimum information necessary for unique identification and communication

  27. NPI Applications - Individuals • Required: name, gender, address/telephone, Taxonomy Code(s), date of birth, State/country of birth, contact person’s name/telephone • Situational: license number(s)/State(s) (required for certain Taxonomy Codes) • Optional: SSN/ITIN, name prefix/suffix, other name(s), credential(s), other identifiers

  28. NPI Applications - Organizations • Required: name, address/telephone, Taxonomy Code, authorized official’s name/telephone, contact person’s name/telephone • Situational: EIN (required if provider has one), license number(s)/State(s)(required for certain Taxonomy Codes) • Optional: other name(s), other identifiers

  29. NPI Data Validation • Key NPI Application Data is not validated by the NPPES: • That the submitted address belongs to the individual • Situationally required state license number(s) is valid and belongs to the applying provider • Optional legacy provider IDs for other health plans and regulatory agencies including: • Medicaid ID(s) and associated states • Medicare UPIN • BCBS #s • NCPDP # • DEA # • CLIA # • Etc.

  30. Provider Taxonomy • Provider Taxonomy is a unique ten character, alphanumeric code which defines a provider’s scope of practice for use in HIPAA standard electronic transactions. • Developed and maintained by the National Uniform Claim Committee (NUCC). • The Provider Taxonomy code has three hierarchical “levels“: • Provider Type • Classification • Area of Specialization.

  31. Provider Taxonomy • Used by a provider (individual, group, or institution) to identify and self declare with the NPI Enumerator their specialty category(ies) as associated with a single NPI, i.e., providers may have one or more than one taxonomy associated to them. • When determining what taxonomy code or codes to associate with a provider, need to review the requirements of all the trading partners with which the code(s) are being used.

  32. Provider Taxonomy • The “Individual Category” of providers includes: • Physicians • Behavioral Health and Social Service Providers • Chiropractic Providers • Dental Providers • Dietary and Nutritional Service Providers • Emergency Medical Service Providers • Eye and Vision Service Providers • Nursing Service Providers • Nursing Service Related Providers • Other Service Providers • Pharmacy Service Providers • Physician Assistants and Advanced Practice Nursing Providers • Podiatric Medicine and Surgery Providers

  33. Provider Taxonomy • Respiratory, Rehabilitative and Restorative Providers • Speech, Language and Hearing Providers • Student, Health Care • Technologist, Technician, and Other Technical Service Providers • The Group (of Individuals) category includes: • Multi-Specialty • Single Specialty

  34. Provider Taxonomy • Organizational/Non-individual Providers include: • Agencies • Ambulatory Health Care Facilities • Hospital Units • Hospitals • Laboratories • Managed Care Organizations • Nursing and Custodial Care Facilities • Residential Treatment Facilities • Respite Care Facilities • Suppliers • Transportation Services

  35. Provider Taxonomy • Provider Type (1st level) • A major grouping of service(s) or occupation(s) of health care providers. Examples include: • Allopathic & Osteopathic Physicians • Dental Providers • Hospitals • Etc.

  36. Provider Taxonomy • Classification (2nd level) • A more specific service or occupation related to the Provider Type, often based upon the General Specialty Certificates as issued by the appropriate national boards, e.g.., within Allopathic & Osteopathic Physicians, Classifications would include: • Allergy and Immunology • Anesthesiology • Dermatology • General Practice • Internal Medicine • Obstetrics and Gynecology • Etc

  37. Provider Taxonomy • Classification (2nd level) • Within Provider Type “Hospitals”, Classifications would include: • Christian Science Sanitarium • Chronic Disease Hospital • General Acute Care Hospital • Military Hospital • Psych Hospital • Rehab Hospital

  38. Provider Taxonomy • Area of Specialization (3rd level) • A more specialized area of the Classification in which a provider chooses to practice or make services available. For example, the Area of Specialization for provider type Allopathic & Osteopathic Physicians is based upon the Subspecialty Certificates as issued by the appropriate national boards, e.g., for OB-GYN. • Gynecologic oncology • Maternal and Fetal medicine • Obstetrics • Reproductive endocrinology

  39. Provider Taxonomy • Area of Specialization (3rd level) • For the Classification General Acute Hospital, Areas of Specialization include: • Children • Critical Access • Rural • Women

  40. NPI Impacts • NPI affects all healthcare organizations but health plan and clearinghouse impacts are much greater than provider impacts • Health plan impacts include 2 major risks: • Risk of not obtaining NPI timely and accurate data from provider is significant • Legacy claims, provider and other systems will not support use of NPI

  41. NPI Impacts • Under the current process, health plans are at great risk that their providers: • will not apply for NPIs on a timely basis • will apply for Subpart NPIs and taxonomy codes which are in conflict with health plans’ internal credentialing and scope of service data • will not disseminate assigned NPIs to health plans either: • on a timely basis, or • accurately

  42. NPI Impacts • Until CMS’ Electronic File Interchange (EFI) for batch enumeration is implemented, only individual providers can apply for an NPI • When EFI is implemented, only select, designated organizations will be able to submit in behalf of their providers • In the absence of strong health plan support, providers will have transition issues which require: • Development of health plan policies and procedures concerning NPI application • Education of providers concerning how to apply • In the absence of such measures, there could be major disruption of provider cash flow, disruption of services to clients, and negative publicity

  43. NPI Impacts • Impact on Health Plan Systems • Need to assess and remediate legacy health plan automated systems for NPI compliance • Existing health plan claims, credentialing and other legacy systems are not NPI-compliant and may result in non-payment, incorrect, late, fraudulent or otherwise inappropriate payments to their network

  44. NPI Impacts • Impact on Health Plan Systems • Legacy and health plan-assigned provider identifiers will not be permitted in standard transactions, and the NPI is “non-intelligent”, hence matching NPIs against legacy provider credentialing and enrollment data will be difficult

  45. NPI Impacts • Changes required to Health Plan Systems could include: • Accommodating NPI field size and format • Remediating all code based on intelligence in legacy numbers • Creating cross-references between legacy provider numbers and NPI’s • Supporting both NPI and non-NPI (for providers not eligible for NPI) provider IDs • Converting claims history for reporting and other processes based on provider IDs

  46. NPI Impacts • Systems will need to map NPI and any Subpart NPIs to legacy IDs • Systems will need to map taxonomy codes to legacy system methods of defining allowable and reimbursable scope of service, e.g., Category of Service

  47. NPI Impacts • Changes to Health Plan Processes: • Credentialing and provider enrollment • Ensure NPI subtypes and taxonomies are consistent with health plan processes including contracting • Add one-time, re-enrollment process to ensure collection of initial NPIs • Add ongoing process for collection of new NPIs and NPI record updates • Reconcile NPI data against provider enrollment and credentialing databases • Provider contracting and reimbursement • Ensure contracts and reimbursement aligned to appropriate NPI-compatible provider logical designation, e.g., taxonomy maps to COS

  48. NPI Impacts • Changes to Health Plan Processes: • Health plans will need to capture NPI for enrolled providers – either manually or through automated interface, e.g., EFI. Also impacts provider enrollment workflow. • It will be difficult for health plans to link NPIs of their providers and subparts with known provider affiliations because no links between covered organization healthcare providers and their subparts are captured within the NPPES. There is nothing on the NPI application update form that denotes an applicant as a subpart.

  49. NPI Impacts • Compliance Issues • Extensive provider education required • Obtaining an NPI, Subpart NPI, and taxonomy codes • Working with health plan and system vendor for changes • Possible new transaction requirements • Testing / implementing with multiple payers • Migration guidance • Paper vs. electronic transactions • Covered vs. Noncovered providers • Require NPI on both? • How to handle non-healthcare providers?

  50. NPI Impacts • Compliance Issues • How does implementation strategy align with other health plans and CMS? • Transition planning • How best to transition providers in an orderly manner by May 23, 2007 • Contingency planning

More Related