1.4.4 Receipt
of Outgoing Contractor’s Shipment of History Updates and Dual Operations
1.4.4.1 Beginning with the 120th calendar
day prior to the start of services delivery and continuing after
the start of services delivery until all pertinent claims received
by the outgoing contractor have been processed, the incoming contractor
shall convert the weekly shipment of the beneficiary history and
deductible file updates from the outgoing contractor files within
two business days following receipt. These The
contractor shall validate these files shall
be validated by the incoming contractor before use. Tests The
contractor shall perform tests for claims, update of
catastrophic cap, and duplicate claims shall be performed within
two business days following conversion. Any issues
identified by the The incoming
contractor shall be resolved with the outgoing contractor and inform the
DHA COR shall be kept informed of all
issues identified within two business days and provide the problem
resolution. Following the start of services delivery, these
files shall be loaded to history and used the incoming
contractor shall load these files to history and use them for
claims processing on the first processing cycle following the check
for duplicate claims.
1.4.4.2 During the period after the start
of services delivery when the incoming contractor and the outgoing contractor
are processing claims, both contractors shall maintain close interface
on history update exchanges and provider file maintenance. During
the first 60 calendar days of dual operations, the both contractors
shall exchange beneficiary history updates with each contractor’s
claims processing cycle run. Thereafter, the exchange
shall not be both contractors shall ensure
the exchange is not less than twice per week until the
end of dual processing period.
1.4.6 Duplicate
Claims System (DCS)
Incoming and Outgoing Contractor
Requirements1.4.6.1 Incoming
and Outgoing Contractor Requirements
1.4.6.1 The incoming contractor shall
access the web-based DCS via the Patient Encounter Processing and Reporting
(PEPR) Portal in accordance with the TSM,
Chapter
4 and ensure the connection has been tested and is accessible.
1.4.6.2 The contractor shall
participate in Government furnished DCS training and schedule training
per the IMP/IMS.
1.4.6.3 The incoming contractor shall
ensure all users have fulfilled security and access requirements
for the web-based DCS no later than 60 calendar days prior to the
start of services delivery. This includes:
• Identifying a Security Manager
to be responsible for overseeing the DCS registration process.
• Submission of a completed and
signed security document for each user to DHA.
• Obtaining/receiving from DHA
User IDs and initial passwords following receipt and processing
of properly completed registration and security documents by DHA.
1.4.6.4 The Government and
incoming contractor shall determine together the date
when the incoming contractor will shall assume
full responsibility for resolving all existing potential duplicate
claim sets from the outgoing contractor (including completing existing
recoupments), and for all new potential duplicate claim sets, shall
be determined during transition meetings. and
be established in The contractor shall
add the date to the transition plan/schedule.
1.4.6.5 During transition the Government
will provide DCS training to the incoming contractor. Training may occur
120 calendar days prior to the start of services delivery, but no
later than 60 calendar days following the start of services delivery.
The incoming contractor shall coordinate training needs in accordance
with the transition plan/schedule. All The
contractor shall meet all user access requirements shall
be met prior to the initiation of training.
1.4.6.6 The incoming contractor shall
begin using the DCS to resolve identified potential duplicate claim
sets “owned” by the incoming contractor 120 calendar days following
the start of services delivery.
1.4.6.7 The incoming contractor shall
begin processing potential duplicate claim sets transferred from
the outgoing contractor 150 calendar days following the start of
services delivery.
1.4.6.8 The incoming contractor is
required to shall identify
at least one individual to serve as the DCS POC. The contractor’s DCS
POCs must shall be an individuals who is are,
or will be, trained in the use of the DCS, and who is able to perform
the required research and determine whether a particular claim is
within their processing jurisdiction. The contractor shall provide
the name(s), title(s), business address(es), and business telephone number(s)
of their DCS POCs to the PCO, with
courtesy copies to the COR and to the DHA DCS Program Representative.
The contractor shall provide DCS POCs shall
be provided to the PCO
no later than two weeks prior to the implementation of the DCS.
1.4.6.9 DHA will provide each contractor
with the list of all DCS POCs. Whenever a new contract is awarded, DHA
will notify all contractors of the new contractor’s DCS POC. Once
the initial listing is provided to the contractors, it
is the responsibility of each contractor to shall maintain
the listing and keep DHA and the other contractors informed of any
changes.
1.4.6.10 In accordance with the Financial
Procedures in the Transition Plan, the contract, and the TRICARE Operations
Manual (TOM), the outgoing contractor shall package and forward
to the incoming contractor, refund checks received and offsets taken
for recoupments associated with duplicate claims payments and recoupment files
associated with in progress duplicate claim recoupment 120 calendar
days following the start of services delivery.
1.4.6.11 On the last day of the fourth
month following the start of services delivery, or upon direction
of the Government, the outgoing contractor
shall cease researching Open claim sets and initiating
new recoupments associated with duplicate claim payments. The outgoing
contractor shall also cease entering refund data and linking adjustment
date in the DCS for Pending and Validate claim
sets.
1.4.6.12 The outgoing contractor shall
move all Open DCS claim sets to a Pending, Validate,
or Closed status by the last day of TED submissions
(as defined by the transition plan).
1.4.6.13 When the outgoing contractor
has ceased entering refund and adjustment date on the DCS, refunds may
be received and/or TED adjustments may still be submitted for claims
in Open and Pending sets. In this
case, the incoming contractor may be required to resolve the set
without knowing the amount of the refund received by the outgoing
contractor.
1.4.6.14 If the actual recoupment amount
was zero when the set was transferred from the outgoing contractor,
the incoming contractor may apply the adjustment to the set while
leaving the actual recoupment amount as zero dollars. Resolution would will result
in a Validate status, requiring an
explanation by and the incoming
contractor shall explain that the outgoing
contractor did not enter the actual recoupment amount.
1.4.6.15 Following the start of services
delivery, the DCS will begin displaying identified potential duplicate claim
sets for which the incoming contractor
has responsibility
for resolving shall resolve.
The incoming contractor shall begin using the DCS to resolve potential
duplicate claim sets in accordance with the TSM,
Chapter
4 and the IMP/IMS requirements.
1.4.6.16 The incoming contractor shall
assume full responsibility for resolving all existing potential
duplicate claim sets from the outgoing contractor (including completing
existing recoupments) and for all new potential duplicate claim
sets as agreed upon during the transition meeting.