NCPDP
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Electronic Re-Billing Service Assignment
- Launch RxConnect
- RxConnect
Scenario 1: NCPDP - miscellaneous issues include claim rejection information and Medicare Part D re-billing related issues
Specific Setup:
- The Avatar application must be associated with an RxConnect Instance and configured to communicate via HL7.
- There must be active connections between Avatar and RxConnect for "ADT", "ORDERS", "FILL DETAILS", and "BILLING".
- The "ADT" and "ORDERS" connections must have both values selected in the 'Sub System Code Facility ID(s) Supported' field and the 'Include Sub System Code Facility ID in Outbound Message' field in the 'HL7 Connection Manager' form, which is a Netsmart Staff Only form. Please contact your Netsmart Representative.
- CE2000 must be installed and configured on the Database server.
- The 'Avatar PM->Billing->Electronic Billing->NCPDP->->Enable NCPDP Billing' registry setting must be set to "Y".
- The 'Avatar PM->Billing->Electronic Billing->Electronic Re-Billing Service Assignment->->Multiple Claim Original Reference Number/Claim Submission Reason Code' registry setting must be set to "Y".
- The 'RADplus->Database Management->RxConnect->->->Enable RxConnect Facility ID' registry setting must be set to "Y".
- Two inpatient programs must exist. (Program A) (Program B)
- Two sub system codes must exist:
- One associated with "Program A" with a 'Facility ID' of "41". (Sub System Code A)
- One associated with "Program B" with a 'Facility ID' of "42". (Sub System Code B)
- RxConnect must have at least two hospitals.
- One with a 'HL7 ID' of "41" associated to "Sub System Code A". (Hospital A)
- One with a 'HL7 ID' of "42" associated to "Sub System Code B". (Hospital B)
- Please log out of the application and log back in after completing the above configuration.
- Two clients must exist
- One client must have an active episode associated with "Program A". (Client A)
- One client must have an active episode associated with "Program B". (Client B)
- “Client A” and "Client B" must have a ‘Date of Birth’, ‘Sex’ and address on file in the ‘Update Client Data’ form, as well as information filed in the ‘Allergies and Hypersensitivities’ form, ‘Diagnosis’ form, and in the ‘Height’ and ‘Weight’ fields in the ‘Vitals Entry’ form.
- "Client A" and "Client B" must be associated with an NCPDP guarantor in the 'Financial Eligibility' form.
- "Client A" and "Client B" must have active pharmacy-type orders each with a duration of "60 Days" that starts in the past that have been processed in RxConnect. (Order A) (Order B)
- "Order A" and "Order B" must have two active NDC#'s each. (NDC A) (NDC B) for "Order A" and (NDC C) (NDC D) for "Order B".
- "Order A" must be administered for the first seven days using "NDC A", the second seven days using "NDC B", the third set of seven days using "NDC A", and the last set of seven days using "NDC B".
- "Order B" must be administered for the first seven days using "NDC C", the second seven days using "NDC D", the third set of seven days using "NDC C", and the last set of seven days using "NDC D".
- Charges must be batched in RxConnect.
- Charges must be compiled in the 'Compile Inbound HL7 Charge Batch File' form.
- Charges must be posted in the 'Post Inbound HL7 Charge Batch File' form.
- Charges must be rolled up and posted in the 'Compile/Edit/Post/Unpost Roll-Up Services Worklist' form and ensure that "Client A" and "Client B" contain two fills each for fourteen days.
- Charges must be closed for "Client A" and "Client B".
- An NCPDP bill must be created, claimed and a file must exist on the server, this is done in the 'Electronic Billing' form.
- The bill must be processed through CE2000 and be rejected.
- The user must be logged into the Root System Code.
Steps
|
Topics
• NCPDP
• NX
|