J.6 Assumptions.DOC
DOC document 33 KB Posted
- Attached to
- True Out of Pocket Costs (TrOOP)
- Solicitation number
- APP100533LA
About this file
Assumptions
View the file
Other files
| File | Type | Posted |
|---|---|---|
| CMS Technical Ref Arch_ v 2.0_11124009.pdf | ||
| Q A's.doc | DOC document | |
| CMS TRA Virtualization Supp v 1 1_07282010.pdf | ||
| RFP .doc | DOC document | |
| J.12 Acronyms.docx | DOCX document | |
| J.10 Connectivity request for the MDCN .DOC | DOC document | |
| J.3 Minimum Matching Criteria.DOC | DOC document | |
| SF 33.pdf | ||
| J.2 Medicare eligibility index Record Layout Specifications.DOC | DOC document | |
| J.8 Standard Language TrOOP BAA 07192010.doc | DOC document | |
| J.9 Section C SOW 7-29.docx | DOCX document | |
| J.1 Data Use Agreement.doc | DOC document | |
| J.7 HIPAA Security Compliance Plan.DOC | DOC document | |
| J.5 N1 N2 and N3 Requirement.doc | DOC document |
Show all 14
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment J.6 attachment j.6 Assumptions
· CMS will:
· Provide complete benefit information for Medicare beneficiaries to PDP’s and Eligibility vendors
· Reporting Transactions Standardized
· e.g., On adjustments or reversals the Part D plans will receive the same information that was provided on the secondary or tertiary modified N1 transaction
· Non PDP payers will:
· Provide to CMS a RxBIN, RxPCN, RxGRP, RxID to support creation of enrollment file
· Batch
· If unique RxBIN and RxPCN are not RxBIN/RxGRP
· Non real-time billing claims (batch or paper) will be submitted through TrOOP Facilitation process using Standardized Information Reporting, Information Reporting Reversal, and Information Reporting Re-bill transactions (i.e. NCPDP modified N1, N2 and N3 (optional) transaction format)
· Real-time claims not routed through TrOOP Facilitation Process:
· Create and send Information Reporting, Information Report Reversal, and Information Reporting Rebill transactions to TrOOP Facilitation process, If a unique RxBIN, RxPCN, RxGRP is not established and provided to CMS.
· General:
· All Payers will:
· Resolve rejects generated as a result of incorrect information provided by payer
· The TrOOP Facilitation Process supports:
· Information Reporting, Information Reporting Reversals, and Information Reporting Re-bill transactions (N1, N2, and N3 (optional) transactions.
· Certification with each payer interface
· Eligibility Process supports:
· Standard Eligibility Request, Response, and Messaging
· The NCPDP v5.1 N1 transaction will be modified to include data elements in the Data Element Request Form (DERF) submitted to NCPDP.
· NCPDP and ANSI will manage the uniqueness of the RxBIN/RxPCN that will be used in the header of a Medicare Supplemental Claim
· Pharmacies will place the unique RxBIN and PCN in the headers of Medicare Supplemental Claims they send
TrOOP Facilitation SOW
File details come from the government source that posted it. Updated .