Requirement Constraints

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Saturday, 15 September 2012

EDI 5010 Documentation 837 Professional - Loop 2310B Rendering Provider

Posted on 00:01 by Unknown

2310B Rendering Provider

        


I strongly recommend to read this article or download this document to understand the Concept of NPI, Provider billing with Individual NPI and Provider Billing with Group NPI.
You can also look our Billing Provider loop details here.

This loop semantically same as Billing Provider Loop 2010AA. But there are conceptual difference between Billing Provider and Rendering Provider.

FAQ 1 : What is the difference between Billing Provider and Rendering Provider ?
The billing provider may be a practice or individual doctor who owns the business. But the rendering provider is the healthcare provider who actually performed (or rendered) the services. For a solo practice,usually the billing provider and the rendering provider are the same entity.  However,the two providers are still treated separately by the insurance companies when processing your claims.

FAQ 2 : What makes  the difference between Billing Provider and Rendering Provider in paper claims and EDI ?
In the paper filing, the Billing Provider information is found in box 33 of the CMS1500. For electronic filing its located in the 2010AA NM1 record of an 837 file.
In the paper filling, the rendering provider information is found in box 24j of the CMS1500. For electronic filling its located in the 2310B.

FAQ3: What need to be done in each carrier if we bill as part of group NPI ?
If we are billing as part of group, then we should ensure that  provider’s individual NPI is linked to the group NPI with each insurance carrier.
For example, say a provider is in network with their local BCBS but they are set up individually under their ss# and their individual NPI. Then they decide to work part time for another group. The group they are working for cannot simply bill BCBS with that provider’s individual NPI in the rendering provider field and their group NPI in the billing provider field and expect payment to be made to the group. Even if the provider is par with BCBS. The group must notify BCBS that the provider will be working for the group, in addition to their private practice. BCBS will link the provider’s individual NPI to the group’s NPI

If you are billing for a provider or group, and you are not sure if the all of the provider’s NPI’s are set up correctly, you should call the insurance carriers to confirm. It is always better safe than sorry

In this loop, all the information will be taken from Practice Provider Master. Take a look of our sample screen here how  provider information are stored in the system.

Now let’s start the detail implementation.
Loop Seg ID Segment Name Format Length Ref# Req Value
2310B NM1 Rendering Provider Name ID 3 R NM1
Element Separator AN 1 *
NM101 Entity Identifier Code ID 2/3 98 R 82
Element Separator AN 1 *
NM102 Entity Type qualifier ID 1/1 1065 R 1
Element Separator AN 1 *
NM103 Name Last or Organization Name AN 1/60 1035 R Rendering Provider Last Name
Element Separator AN 1 *
NM104 Name First AN 1/35 1036 S Rendering Provider First Name
Element Separator AN 1 *
NM105 Name Middle AN 1/25 1037 S Rendering Provider Middle Name
Element Separator AN 1 *
NM106 Name Prefix AN 1/10 1038 Not used
Element Separator AN 1 *
NM107 Name Suffix AN 1/10 1039 S Rendering Provider Suffix
Element Separator AN 1 *
NM108 Identification code Qualifier ID 1/2 66 R XX
Element Separator AN 1 *
NM109 Identification code AN 2/80 67 R Print NPI Number.
Segment Terminator ~
               
 
 
NM102 - Entity Type Qualifier
Code qualifying the type of entity
Code Definition
1 Person
2 Non-Person Entity
 

2310B Rendering Provider Secondary Identification
Loop Seg ID Segment Name Format Length Ref# Req Value
2310B REF Rendering Provider Secondary Identification ID 3 R REF
Element Separator AN 1 *
REF01 Reference identification ID 2/3 128 R See below for more information
Element Separator AN 1 *
REF02 Reference identification AN 1/50 127 R Print the Reference number
Segment Terminator ~

REF01 - Reference Identification Qualifier

Code qualifying the type of Reference
Code Definition
0B State License Number
1G Provider UPIN Number
G2 Provider Commercial Number
LU Location Number
 
2310B Rendering Provider – Example

NM1*82*1*Sean*Smith*K***XX*7575757575~
REF*0B*0B12853W23~
REF*1B*UA73823~
REF*G2*LM43322~
 
 
        

Questions or feedback are always welcome. You can email me at vbsenthilinnet@gmail.com. You can hire me as consultant for EMR/PMS Domain and Web development on EMR/PMS Product!
Email ThisBlogThis!Share to XShare to Facebook
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • ZK Example for inline Editing with Add New and Delete
    I am quite impressed on this demo from ZK . But adding new record and delete existing record is missing as part of typical CRUD. So i thoug...
  • EDI 5010 Documentation 837 Professional - Loop 2010BB Payer Name
    2010BB Payer Name          In this loop, all the information will be taken from Insurance master screen. Take a look of our sample screen...
  • EDI 5010 Documentation–837 - BHT - Beginning of Hierarchical Transaction
    BHT – Beginning of Hierarchical Transaction Loop Seg ID Segment Name Format Length Ref# Req Value   BHT Beginning of Hier...
  • Hibernate Validator Example 2
    In this example, we will see some more validation constraints such as @email, @past, @length, etc. And also we will also define custom error...
  • ZK Passing Parameter between two files using MVVM–Part 1
    Overview This is the first series of articles about Passing parameter between two zul files using MVVM Design pattern .This article will fo...
  • MVVM Command annotation and Notify change example
    Here is an example, how to pass parameter on a zul through MVVM Command binding annotation. ZK URL http://books.zkoss.org/wiki/ZK%20Develo...
  • History of Present Illness
    HPI - One of the main component of Clinical History. What is an HPI ? The history of present illness (HPI) is a chronological description...
  • Patient Demographics
    Patient browse (search) is the key element for any EMR / PMS Software. In my past 15 years experience, i involved more than 5 times in desig...
  • ViewModel Class Java Annotation @Init, @NotifyChange, @Command
    In following sections we'll list all syntaxes that can be used in implementing a ViewModel and applying ZK bind annotation. The ZK binde...
  • Good Website Design Links
    Form Design Label Placement in Forms International Address Fields in Web Forms 40 Eye-Catching Registration Pages blog-comment-form-...

Categories

  • Billing Process
  • C Workbook
  • C++ Workbook
  • Eclipse Tips
  • EDI 5010
  • EMR Appointment Features
  • EMR Labs Stuff
  • EMR PMS Links
  • EMR Use cases
  • EMR Vital Sign
  • Good Website Design
  • Hibernate Criteria Queries
  • Hibernate Introduction
  • Hibernate Introduction Setup
  • Hibernate Mapping
  • Hibernate POC
  • Hibernate Validator
  • Hibernate–Java Environment setup
  • HPI
  • Java
  • Maven
  • MU Certification
  • NPI
  • PQRS
  • Practice Management System
  • Spring Security
  • Tech Links
  • Today Tech Stuff
  • zk
  • ZK Hibernate
  • ZK 5 Databinding
  • ZK Application
  • ZK Calling Another ZUL
  • ZK CheckBox
  • ZK CreateComponents
  • ZK CSS
  • ZK extended Components
  • ZK Foreach
  • ZK Forum Posts
  • ZK Framework
  • ZK Hibernate Setup
  • ZK ID Space
  • ZK Include
  • ZK Installation
  • ZK iReport
  • ZK Layout
  • ZK Listitem Pagination
  • ZK Message Box
  • ZK MVC
  • ZK MVC Combox Box
  • ZK MVC CRUD Examples
  • ZK MVC Listbox
  • ZK MVVM
  • ZK MVVM Combo
  • ZK MVVM CRUD
  • ZK MVVM ListBox
  • ZK Spring
  • ZK TextBox

Blog Archive

  • ►  2013 (105)
    • ►  December (3)
    • ►  September (7)
    • ►  August (13)
    • ►  July (1)
    • ►  June (11)
    • ►  May (3)
    • ►  April (14)
    • ►  March (19)
    • ►  February (21)
    • ►  January (13)
  • ▼  2012 (177)
    • ►  December (1)
    • ►  November (13)
    • ►  October (19)
    • ▼  September (24)
      • Claims adjudication and payment
      • EDI 5010 Documentation 837 Professional - Loop 240...
      • EDI 5010 Documentation 837 Professional - Loop 233...
      • EDI 5010 Documentation 837 Professional - Loop 231...
      • EDI 5010 Documentation 837 Professional - Loop 231...
      • EDI 5010 Documentation 837 Professional - Loop 231...
      • How to install Maven in the Windows
      • EDI 5010 Documentation 837 Professional - Loop 200...
      • EDI 5010 Documentation 837 Professional - Loop 201...
      • EDI 5010 Documentation – 837 Professional IEA Inte...
      • EDI 5010 Documentation 837 Professional - Loop 201...
      • EDI 5010 Documentation 837 Professional - LOOP 200...
      • Some Important Master screens for PMS
      • EDI 5010 Documentation 837 Professional - Loop 201...
      • EDI 5010 Documentation–837 Loop 2000A - HL–Billing...
      • Physician Quality Reporting System - PQRS
      • EDI 5010 Documentation 837 Health care claim : Pro...
      • EDI 5010 Documentation 837 Professional - Loop 100...
      • EDI 5010 Documentation 837 Professional - Loop 100...
      • EDI 5010 Documentation–837 - BHT - Beginning of Hi...
      • EDI 5010 Documentation–837 ST–Transaction set Header
      • EDI 5010 Documentation–837 GS – Functional Group H...
      • Hibernate Validator - Capture the exception using ...
      • EDI 5010 Documentation–837 Professional - ISA – In...
    • ►  August (26)
    • ►  July (6)
    • ►  June (37)
    • ►  May (30)
    • ►  April (16)
    • ►  March (1)
    • ►  January (4)
  • ►  2011 (5)
    • ►  December (1)
    • ►  November (1)
    • ►  July (1)
    • ►  June (1)
    • ►  April (1)
  • ►  2010 (1)
    • ►  September (1)
Powered by Blogger.

About Me

Unknown
View my complete profile