The line identifier is already in there. It is stored in an REF segment
with a qualifier 6R (Provider Control Number). The guides leave its usage
to the provider, but if one is assigned by the provider in the claim (837),
then the payer is required to return it in the remittance (835).
Bob
William,
At IBC, we will be performing all front-end X12 processing (compliance,
formatting, enveloping, etc.) for one of our subsidiaries. Submissions
will then be routed to them based on GS03, which submitters will be required
to populate with the correct NAIC.
I would be very interested
8/12/02
As idealistic as it surely is, and as jaded as I became about paperless business
absent a TPA in the early EDI days, I am not so
sure a CPP for the healthcare industry is pie in the sky for one reason: volume.
Unsolicited and TPA-less Electronic Business never took off for one reason:
Dave,
I believe that each of your descriptions below represents a specific use
case. Furthermore, each description represents a binary collaboration and
possibly multiparty collaborations. The ebXML BPSS V 1.05 currently out for
draft review addresses these concepts. Here's an excerpt from the
Rachel,
If I'm understanding this correctly, the use-case for the provider is
Payor system accepts my transaction, and for the payor, it would be My
system receives the provider transaction and routes it to the appropriate
application... based on the value in GS03. But there are potentially
Chris,
It appears to me that you may not have a clear conception/understanding of
what a use case is. Thus, I'm inserting here some explanations that are
incorporated into the UN/CEFACT UMM as well as ebXML. Use case analysis is
very commonly used today by all major software developers.
What Is
Keith,
The CPP and CPA are one of several ebXML Framework
specifications. OASIS is the responsible organization for the continued
development and maintenance of these and other ebXML Framework technical
specifications. Complete information about the ebXML Initiative can be found at
