decisionhealth Newsletters, Answer Books - 2006 Issue 3 (March)
Program_Memos / 2001 / B-01-22
Subscribe or sign in to view the full article.
Article Overview
This article covers a 2001 Medicare program memorandum focused on VMS system changes for separating ownership, access, and update authority across multiple subsystems. It is relevant to Medicare claims processing, system analysts, implementation teams, and coding/support staff who need to understand the scope of the operational and reporting updates described in the memo.
Why This Topic Matters
It documents planned system changes that affect how ownership, access, reporting, and subsystem interactions are handled across a large Medicare processing environment, making it important for implementation review and historical reference.
Article Sections
-
Attachment 2 - From PM B-01-12
Background material outlining the documentation context and the VMS requirements issue addressed by the memorandum.
-
Description of Limitation/Solutions
A high-level explanation of the system limitation and the general approach taken to address ownership segregation across subsystems.
-
Segregation of Ownership Assumptions
A set of planning assumptions used to guide the system analysis, implementation scope, and ownership decisions.
-
System Changes
An overview of broad system-wide changes and the organization of the subsystem-specific updates that follow.
-
System-Wide Changes to Resolve Segregation of Ownership Limitations
General changes intended to apply across multiple VMS subsystems, including record handling, access control, and ownership tracking.
-
Changes Required for Specific Subsystems
A structured list of subsystem-level updates covering multiple VMS components and their related ownership-handling changes.
-
A. Area Prevailing Provider Look-Up (APPL) Changes
Updates specific to the APPL subsystem, including record structure and copy-function behavior.
-
B. VIPS Medicare Online Claims (VMON) System Changes
Changes for the VMON claims environment, including edit handling and ownership-related claim processing updates.
-
C. Interactive Correspondence (ICOR) Changes
Correspondence-system updates involving external letter handling, parameter tables, reporting, and ownership tracking.
-
D. DMERC Specific Changes
Adjustments for DMERC-related areas, including edit tables, status management, and CMN processing support.
-
E. VMS Accounting System - Money Online Notification and Inquiry (MONI)
Accounting-system updates related to source tracking and report enhancements within the MONI subsystem.
-
F. Parameter Table (VMAP) Changes
Changes to parameter and alert tables, including ownership indicators, status structures, and consistency edits.
-
G. VMS Suspense Subsystem Changes - Automated Paperless Exceptions (APEX) and VIPS CMN Automated Exception Processing (VCAP)
Suspense-processing updates affecting claim and CMN handling, visibility, and location/status usage.
-
H. VMS Mass Adjustment System (MADS)
Mass-adjustment updates addressing suspense assignment and related ownership alignment.
-
I. VMS Online Quality Control (OQC) System Changes
Quality-control selection logic and location/status handling changes tied to ownership and operator setup.
-
J. VMS Online Documentation System (OLDS) Changes
Documentation-system updates involving ownership lookups from related subsystems and non-updateable ownership fields.
-
K. VMS Automated Development System (ADST)
Development-system security, text listing, and consistency-check updates related to ownership across letters and claim paths.
-
L. VMS Letter Writer System (LTRO)
Letter-writer updates focused on ownership consistency across letter setup components.
What You Will Learn
- What the memorandum is addressing at a system and subsystem level
- Which VMS components are included in the scope of the update
- What kinds of ownership, access, and reporting changes are being planned
- How the article organizes implementation considerations across multiple operational areas
- Which dates govern the memorandum’s effect, implementation, and discard period
Who Should Read This
- Medicare systems analysts
- Claims processing operations staff
- Implementation and maintenance teams
- Revenue cycle and Medicare contractor personnel
- Medical coding support and compliance staff
Subscribe or sign in to view the full article.


Quick, Current, Complete - www.findacode.com