decisionhealth Newsletters, Answer Books - 2006 Issue 3 (March)
Program_Memos / 2000 / AB-00-34
Subscribe or sign in to view the full article.
Article Overview
This article explains the scope of HCFA’s Program Integrity Management Reporting (PIMR) system and the types of reporting data it was designed to collect from Medicare contractor and support systems. It is relevant to Medicare program integrity, medical review, fraud, claims processing, and systems/reporting personnel who need to understand the structure of the reporting requirements, interface inputs, and data groupings covered by the memorandum.
Why This Topic Matters
It documents how a major Medicare program integrity reporting framework was organized, including the system-level data elements and source-system interfaces that contractors were expected to support. That makes it useful for analysts, compliance staff, and coding/reporting teams who need historical context for Medicare integrity reporting requirements and data categorization.
Article Sections
-
Program Integrity Management Reporting (PIMR) overview
Introduces the reporting system, its purpose, effective dates, and the contractor reporting environment it was intended to support. Summarizes the broad data categories used throughout the memorandum.
-
General data definitions
Defines the principal reporting concepts used across the system, including units, claims counting, line items, reviews, denials, and referrals. Also distinguishes reporting instructions from operational medical review guidance.
-
General reporting levels
Explains the reporting dimensions used to summarize data and describes how contractor, time, provider, and other structural levels are organized. Includes the treatment of edit-related reporting and standardized identifiers.
-
Activity type categories
Describes the major classes of medical review and related activities tracked in the reporting system. Covers prepayment, postpayment, claims processing, and other activity groupings.
-
Contractor/Standard System Interface
Presents the monthly data elements expected from contractor standard systems and the database structures used for PIMR intake. Includes tables for postpayment review data, prepayment review data, denial reasons, other referrals, claims processing, and related interfaces.
-
CAFM Interface
Describes the effort-related data elements that are transferred from CAFM and the activity structure used for reporting those values. Focuses on system interface requirements and data-level breakdowns.
-
FID Interface
Defines the fraud case and payment suspension data required from FID, including mapping concepts and monthly reporting structure. Also includes the associated source-to-destination table framework.
-
CROWD Interface
Outlines complaint-related data required from CROWD for program integrity reporting. Describes the relevant source records and reporting breakdowns.
-
IRP Interface
Provides the comparable complaint-related interface requirements from IRP. Focuses on the data elements and monthly transfer structure.
-
Attachment 2 – FI Provider Type
Lists provider type categories used in the attachment for fiscal intermediary reporting. Serves as a reference table for the broader reporting framework.
-
Attachment 3 – FI Provider Subtype
Lists provider subtype categories and associated ranges used for intermediary reporting. Includes multiple facility and subtype groupings used for classification.
-
Attachment 4 – Carrier Provider Type and Subtype
Provides carrier specialty and HCPCS-based provider subtype groupings. Serves as a reference for carrier-side provider classification.
What You Will Learn
- How the PIMR reporting system was structured and what it was intended to replace
- What broad categories of medical review, claims processing, fraud, and referral data were included
- How monthly reporting data was organized across contractor and source-system interfaces
- Which interface source systems contributed to the reporting framework
- How provider and specialty classification references were organized in the attachments
Who Should Read This
- Medicare contractor staff
- Medical review and program integrity personnel
- Healthcare compliance and audit teams
- Revenue cycle and coding systems analysts
- Healthcare data/reporting implementers
Subscribe or sign in to view the full article.


Quick, Current, Complete - www.findacode.com