MEDICAL TRANSACTION SYSTEM

FIELD OF THE INVENTION

This invention is related to computer systems used in the medical health industry, and more particularly, to computer systems used to communicate medical insurance claims. BACKGROUND OF THE INVENTION

Computer systems have been used for a variety of functions within the medical health industry. For example, computer

systems have been used to submit, adjudicate, and process medical

insurance claims. Another example is the use of a computer system to provide medical history information to a healthcare provider so the

provider can make an informed diagnosis or prognosis.

The medical claim processing systems typically include a

plurality of computer stations coupled to a central processing computer.

The computer stations are typically located at a healthcare provider's facility, an insurance carrier, or medical laboratory. The computer stations generate a request for medical information or a medical claim

for processing. The central processing computer couples the computer stations together and verifies the communication with the stations, processes the requests for data, and communicates the requested information back to the computer stations.

Several limitations exist for this type of computer system.

First, these systems require that the plurality of computer stations communicating with the central processing system communicate in a particular communication protocol and that all of the messages

communicated with the central processing system have the same

predefined format. The requirement that the computer stations all

communicate in the same format with the same protocol does not permit expansion of the system to users that are currently using other programs in their computer stations that format data messages differently or that use communication protocols other than the one used by the central processing system. Modifications must be made to the programs of the new users so they may communicate with the

central processing system correctly. What is needed is a medical computer system that can communicate with a plurality of data

message formats and communication protocols. A second limitation of a typical medical transaction system

is a requirement that the central processing system validate and process all the data messages received from the computer stations. In order to do so, the central processing system must be able to compare

the received data messages against known acceptable data. For

example, U.S. Patent No. 4,858,121 to Barber et al., discloses a central processing system that interfaces with a plurality of physician

office terminals, financial institutions, and insurance companies. The information required to validate and format the flow of data from a

standardized physician's terminal to the central processing system of this patent is provided in the claims, insured, physician, insurance

company, zip code, bad credit card, and insurance check files

associated with a variety of databases at the central processing

system. The information in these files must be provided by a plurality of insurance carriers and employers that receive electronic claims from the central processing computer. As a consequence, the maintenance and updating of these databases with information from the insurance carriers and employers must be performed at the central processing system. What is needed is a system that does not require a centralized database for validating and formatting an electronic medical claim that must be maintained with insurance carrier data.

Another limitation of systems previously known include the requirement that the central processing system transmit medical claims to insurance carriers and receive remittance data from insurance carriers in the same communication format and protocol used by the

computer stations at the insurance carriers. In an effort to standardize both forms of communication, ANSI (American National Standards Institute) has generated an ANSI 837 standard for medical claims and

an ANSI 835 for remittance data that specifies the format for a variety

of message types that contain the various types of information to be

exchanged among the central processing system and the computer

stations within a typical computer system used in the healthcare

industry. One limitation of the ANSI standards, however, is that a

number of data fields in the data messages specified by the standard

are optional and may or may not be used by one or more of the

insurance carriers that are members of a medical claim processing

system. Typically, insurance carriers, sometimes called trading

partners, contract with a business partner who runs a central

processing system to provide the carrier with the electronic medical

claims from the healthcare providers. Although the optional data fields

provided in the message formats specified by the ANSI standards support different variations within the standard, the ANSI 837 data message format in previously known systems are set by the business

partner so all computer stations communicate with the central

processing system in the same data message format. What is needed

is a system that can communicate with a plurality of trading partners

that supply data messages in different formats and in different

communication protocols.

In previously known systems, the insurance carriers may

or may not provide remittance information to the central processing

system so the central processing system can generate electronic funds

transfer messages to financial institutions. Instead, the insurance

carriers may generate hard copy checks that are mailed to the financial

institutions or may adjudicate the claim and transmit the remittance of the claim to the central processing system which in turn generates

electronic funds transfer messages in the same format for the financial institutions. As a consequence, only the insurance carrier has access

to all of the remittance data that may be used to generate a database of remittance information regarding the payment of the medical claims

by the insurance carrier. Periodically, an insurance carrier may provide the database of remittance information to a third party for statistical analysis to determine data such as the most frequent type of treatment for a particular demographic group or geographical location. Such statistical information is useful to the insurance carrier for identifying growing healthcare costs which may need addressing. Currently, each insurance carrier must generate its own remittance database and the statistical analysis of the database is performed off-line in a non-real time manner. What is needed is a system that can generate a remittance database for all of the claims adjudicated by all of the

insurance carriers within a medical computer system and analyze that information.

All previously known medical computer systems are dedicated to a single function such as providing medical healthcare data records such as treatments and diagnosis to healthcare providers or submitting and adjudicating medical healthcare claims. What is needed

is a medical transaction computer system that is capable of integrating

the functions of obtaining medical data records with the function of

medical healthcare claim processing.

The present invention provides a medical transaction

system that overcomes the problems noted with the previously known

medical computer systems.

SUMMARY OF THE INVENTION

The above-identified problems for previously known

medical computer systems are solved by a unique medical transaction

system that communicates with a plurality of healthcare provider

computer stations and a plurality of insurance carrier and financial

institution (trading partner) computer stations in a variety of

communication protocols and data message formats. One embodiment

of the inventive medical transaction system includes a communication

receiver capable of communication with the plurality of healthcare provider computer stations using a variety of communication protocols

and data message formats, a compiler for compiling information from

the data messages transmitted by the healthcare provider computer

stations, the compiled information being put in generic records having

a format that is independent of the communication protocol and format

of the data messages, an extractor for extracting some of the generic

records associated with a trading partner computer station

identification code, a formatter for formatting message information

from the extracted generic records in a format corresponding to the

trading partner computer station identification code, and a

communications transmitter for transmitting the formatted message

information to a trading partner in a communication protocol and data message format recognized by the trading partner.

Such a transaction system is capable of communicating with the healthcare provider, insurance carrier, and financial institution computer stations in any one of a variety of communication protocols and data message formats. For example, doctors and hospitals may

submit medical claims to the transaction system without the claims having to be communicated in the same data message format or transmitted in the same communication protocol. Accordingly, there is no need for a healthcare provider station desiring to become a member of the medical transaction system to modify any of its hardware or software to communicate with the medical transaction system of the present invention.

Similarly, the medical transaction system of the present invention may communicate data messages containing claim information to a variety of insurance carriers without the insurance

carriers ail using the same data message formats and communication protocols. This advantage permits the operator of the medical

transaction system to contract with any financial institution or insurance carrier for a format predetermined by a trading partner

agreement that meets the needs of one trading partner without impacting communication or data format requirements for another trading partner. Thus, any financial institution or insurance carrier

signing a trading partner agreement with the operator of the medical

transaction system need not modify the format of its existing data

messages or communication protocols.

In the above-identified system, the data files and databases required to adjudicate medical claims are kept at each of the respective insurance companies. Thus, there is no need for a centralized database having specific insurance carrier information at the medical transaction system for processing a medical claim. One advantage of moving this function to the trading partner computer

stations is that the medical transaction system can quickly and

efficiently verify the data fields within the data messages

communicated to it without requiring the extensive information and overhead processing required to adjudicate and process medical claims. Another advantage is that information to maintain a centralized database for validating claims is not required from the insurance carriers.

Another embodiment of the unique medical transaction

system of the invention includes the capability of receiving data messages which include adjudicated claim and remittance information

from the computer stations at the insurance carriers. The medical transaction system of this embodiment further includes a financial transactor that processes the remittance information to generate electronic funds transfer messages that may be transmitted to the financial institutions to transfer money from an insurance carrier

account to a healthcare provider account. The compiler of this

embodiment further includes the capability to compile information from the remittance and electronic funds transfer messages and associate the compiled information with the generic records in the database generated from the medical data requests. Thus, the medical

transaction system can generate a database from the medical

transaction requests, the remittance messages, and the electronic funds transfer messages. This database may be statistically analyzed off-line or in a real time manner.

Another embodiment of the medical transaction system includes the capability of healthcare providers to communicate with other healthcare providers as well as the trading partners. In this type of system, the healthcare provider may request medical data records of a patient in order to properly diagnose or prescribe a treatment for a patient's condition. The transaction request for medical data records is routed through the medical transaction system to the appropriate medical data record source, such as another healthcare provider. The

medical data record source, in response, provides medical data records to the requesting healthcare provider station through the medical transaction system. This embodiment of the medical transaction system handles this type of medical data record transactions along with

the medical claim transactions previously discussed. Thus, this embodiment of the invention provides a medical transaction system

that integrates the function of providing medical data records with the

function of processing medical healthcare claims.

Other advantages of the present invention will become apparent to those of ordinary skill in the art upon reading and understanding the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may take form in various components and arrangement of components and in various steps and arrangement of steps. The drawings are only for purposes of illustrating a preferred embodiment and alternative embodiments and

are not to be construed as limiting the invention.

Fig. 1 is a block diagram of an alternative embodiment of the inventive medical transaction system;

Fig. 2 is a block diagram of another alternative embodiment of the inventive medical transaction system;

Fig. 3 is a block diagram of a preferred embodiment of the medical transaction system;

Fig. 4 is a diagram of the software functions of the

medical transaction system;

Fig. 5 is a block diagram showing the structure of the input process of the medical transaction system shown in Fig. 3; Fig. 6 is a flowchart of the processing within the receiver

portion of the transaction manager of Fig. 5;

Fig. 7 is a flowchart of the processing within the service

routine shown in Fig. 5;

Fig. 8 is a flowchart of the processing of the compiler of

Fig. 5;

Fig. 9 is a flowchart of the processing of the verifier

shown in Fig. 5;

Fig. 10 is a flowchart of the processing of the response

generator shown in Fig. 5;

Fig. 1 1 is a block diagram of the output process of the

inventive medical transaction system shown in Fig. 3;

Fig. 1 2 is a flowchart of the processing of the extractor of Fig. 1 1 ;

Fig. 1 3 is a flowchart of the processing of the formatter

shown in Fig. 1 1 ;

Fig. 14 is a flowchart of the processing of the transmitter

portion of the transaction manager shown in Fig. 1 1 ;

Fig. 1 5 is a flowchart of the processing of the financial

transactor shown in Fig. 5.

DETAILED DESCRIPTION

The medical transaction system 10 of Fig. 1 shows an

embodiment of the invention that interfaces with a plurality of

healthcare provider computer stations, P., through P _N , and a plurality of

trading partner computer stations, TP, through TP _N . Each of the

healthcare provider terminal stations are located in a doctor's office,

hospital, or the like and is typically used to generate medical claims for

the treatment of patients. Computer stations P., through P _N may also

be located at submitter or biller sites where medicai claims are typically

collected and submitted to the system 10 in batch form or in real time.

The claims are submitted to payors such as insurance carriers and

governmental agencies that comprise a subset of the computer stations

TP-, through TP _N . The healthcare provider stations do not provide the

claim information to the medical transaction system 10 in the same

data message format nor do all of the healthcare provider stations

communicate with the medical transaction system in the same

communication protocol. Likewise, the medical transaction system 10

does not communicate with all of the trading partner computer stations

in the same data message format nor in the same communication

protocol. A communication receiver and transmitter are provided within

medical transaction system 10 to support the plurality of data message formats and communication protocols needed to communicate with the

healthcare provider and trading partner computer stations. The

communication transmitter and receiver are discussed in more detail

below.

In response to receipt of a medical claim from a healthcare

provider station, medical transaction system 10 reorganizes the

information from the received medical claim into a generic medical

claim record format. These generic medical records may be stored in

the memory of the medical transaction system or organized in a generic

transaction database 1 2 associated with the system. The medical

transaction system 10 may periodically extract generic medical records

that correspond to one of the trading partners. These extracted data records are formatted in a format that corresponds to a computer identification code that corresponds to a trading partner. Typically, the data message format for the formatted generic records are stipulated in a contractual agreement between the operator of the medical transaction system and each of the trading partners. The

communication transmitter of the system 10 transmits, in the

communication protocol recognized by that trading partner, the

formatted data messages to the trading partner corresponding to the computer station identification code. For example, system 10 may, at

10:00 p.m. each evening, extract all the generic medical records received for a day that represent claims for a particular insurance company, such as a Blue Cross/Blue Shield affiliate, format the records and send them to the Blue Cross/Blue Shield affiliate for adjudication. The system of Fig. 1 provides several advantages over the previously known medical computer systems. Firstly, medical

transaction system 10 is capable of receiving a medical claim from a plurality of healthcare providers or subscriber sites that use computer stations supporting different medical claim formats and different communication protocols. For example, a doctor may submit a claim for a patient's visit and a hospital may submit a claim for extended care at its facility, even though the hospital and doctor use different

computers that format data messages differently and communicate in

different protocols. The submission of the medical claims may also be

done in batch form or in a real time manner. Secondly, medical transaction system 10 not only receives the medical claim information

in a multitude of formats and protocols but also organizes the data in the received data messages to create generic records which contain the medical claim information. These generic records facilitate the organization of a generic transaction database 12 and the extraction of the generic records for transmission to a trading partner. Thirdly, each of the insurance carrier trading partners maintains its own databases

for adjudicating the claims it receives from system 10. Thus, there is

no requirement for system 10 to have a centralized database having

specific insurance carrier information for processing or adjudicating medical claims.

Another embodiment of the medical transaction system 10 is shown in Fig. 2. This medical transaction system 14 includes the capabilities of the system shown in Fig. 1 and preferably includes a generic transaction database 16. Additionally, the medical transaction

system of Fig. 2 includes a verifier to verify the type of data within the data fields of the data messages received from the healthcare provider

computer stations. This verification preferably includes confirming whether the type of data within a data field of the received message is correct. For example, the verifier may check whether the data in a

particular data field is character or numeric data. Other simplistic

verification of the data that does not require historical information is

also contemplated. For example, the verifier may determine that a

hysterectomy for a male patient is an erroneous claim. If an erroneous claim is received, an error message may be generated that is supplied to the communication transmitter of system 14 which in turn transmits the error message to the healthcare provider station that sent the erroneous claim. The error message is formatted in the data message format corresponding to the computer station identification code for the

station that sent the erroneous claim. The communication transmitter transmits the formatted error message in the correct communication protocol for the healthcare provider station. The system of Fig. 2 provides the advantage of informing a healthcare provider that a medical claim has not been received correctly.

The medical transaction system of Fig. 2 also includes a compiler that generates a generic record that contains identifying information regarding a data message received from a healthcare

provider that failed verification testing. The system of Fig. 2 also includes an analyzer that generates statistical data from the data in the generic records of the database 16. This statistical data may include which healthcare providers are submitting the most claims, the types of claims being submitted, and the average dollar amount of the submitted claims. Of course, other types of statistical information could be determined from the data in generic transaction database 16.

A medical computer system that uses a preferred

embodiment of the medical transaction system 10 is shown in Fig. 3.

System 18 includes the ability to bidirectionally communicate with the

healthcare provider stations, P-. through P _N , like the system in Fig. 2, as

well as a bidirectional communication capability with the trading

partners, TP-* through TP _N . The medical transaction system 1 8 shown

in Fig. 3 further provides communication from one healthcare provider

to another. Thus, system 1 8 may be used to communicate medical

data records from one healthcare provider station in response to a

request from another healthcare provider station in the respective

formats corresponding to the computer station identification codes for

the healthcare proviαers.

The capability of the system 1 8 to bidirectionally

communicate with the trading partners permits the medical transaction

system 1 8 to receive data messages in the format specified for each

trading partner and in accordance with the communication protocol for that trading partner. The data messages from the trading partners to

the medical transaction system 1 8 include remittance and claim

adjudication information from payors, electronic funds transfer

messages to financial institutions, and medical data records from

insurance carriers and medical service sites such as laboratories and the

like. As explained in more detail below, the medical transaction system

1 8 uses the remittance and claim adjudication information from payors

to generate the electronic fund transfer messages for debiting and

crediting accounts at the financial institutions.

As explained in more detail below, the compiler of medical transaction system 18 also compiles remittance, payment, and medical history data from the data messages received from the healthcare providers and trading partners, and preferably organizes the compiled

data in generic record formats for inclusion in a generic transaction database 20. The generic database 20 of the system 18 may provide a history of a claim submission, adjudication, and payment as well as a repository for medical data records which are transmitted through the

medical transaction system. Preferably, an anaiyzer may be included in the medicai transaction system 18 to statistically analyze the data within generic transaction database 20. The analyzer may provide additional statistical information such as which healthcare providers are being reimbursed for the full amount of their claims, which healthcare providers are having a significant number of claims rejected, and other financial information. Additionally, the claims and medical data records stored in the generic transaction database 20 may be analyzed to determine what demographic group requires the most medical visits, the most expensive treatments, or the like.

One advantage of the system 18 shown in Fig. 3 is that full communication is possible between healthcare providers, P, through

P _N , and trading partners, TP-, through TP _N , that have completely different data message formats and communication protocols. Another advantage of such a system 18 is that the information passing through

the system can be organized in generic data records independent of the

data message formats which are being received by and transmitted

from the medicai transaction system. These generic data records

include claim information, financial information, and medical history

information, all of which are a valuable source of data for statistical

analysis that may be used to improve the healthcare supplied by the

providers and for which the insurance carriers pay.

Another advantage of the medical transaction system 18

of Fig. 3 is that there is no requirement for imposing a uniform claim

format ana uniform processing of the claim within the system. The

medical transaction system of Fig. 3 is capable of communicating with

a variety of data message formats and communication protocols. Such a system is capable of remedying an ill recently noted by the President

of the United States that there is complete lack of a uniform medical claim in the United States. A system incorporating the present

invention provides uniformity without imposing the costs of requiring

the insurance carriers and the healthcare providers to use the same

data format. Another advantage of the medical transaction system of

Fig. 3 is the ability to provide a credit line for medical care at a financial

institution that may be used by a patient to pay for those portions of

a medical claim that are not covered by an insurance carrier's payment.

The medical transaction systems shown in Figs 1 through

3 are preferably performed by software executing on a Tandem CLX/R

or Cyclone/R computer controlled by a GUARDIAN C30 operating

system, Release Level 5. Such a computer and operating system are

available from Tandem Computers Incorporated of Cupertino, California. As described in more detail below, the components of the medical transaction systems of Figs. 1 through 3 include custom written

software programs, discussed in more detail below, and commercially available programs that execute on the preferred computer running the preferred operating system. Preferably, the commercially available software is sold under the commercial name Engin by Muscato Corporation of Orlando, Florida, although other commercially available

programs may be used. While the preferred embodiment 18 executes on a single computer running a single operating system, the communication function could be segregated in one computer system that handles the communication protocol processing for the reception and transmission of data messages. After the communication protocol processing is completed, the communication computer could then transfer the data messages to another computer system executing a compiler program to compile information from the data messages and create the generic records, and an extractor program could extract selected ones of the

generic records, format them to particular data formats and provide the formatted data messages to the communication computer for transmission to a healthcare provider or trading partner computer station.

The commercial and customized software of the preferred embodiment that executes on the computer platform for the medical transaction system 18 provides a medical transaction processing kernel 22 surrounded by a layer of communication software 24 as shown in Fig. 4. The communication layer 24 includes receiver and transmitter software that receives and transmits the data messages, recognizes the protocols by which the messages are received by and sent to the medical transaction system and handles the handshaking signals required to receive and send the data messages respectively. For received messages, the receiver of the communication layer 24 strips off the protocol specific elements and provides the data message in the format in which it was received to the medical transaction processing

kernel 22. For transmitted messages, the kernel 22 provides formatted data messages to the transmitter of the communication layer 24 which supplies the protocol specific elements for a particular computer station and then transmits the data message to the computer station in the communication protocol that corresponds to that computer station.

The medical transaction processing kernel 22 of Fig. 4 processes a data message received from the communication layer 24 and organizes the data from the received data messages into records

having a generic format. Periodically, the kernel 22 extracts the generic data records corresponding to a particular computer station,

formats the information in the generic records into the data message format recognized by the computer station and supplies the formatted

messages to the communication layer for transmission.

The software components that accomplish the receipt of data messages from a computer station are shown in Fig. 5. Two of the components, the transaction manager receiver 26 and portions of

the service routine 28, are associated with the communications layer

24 while the remaining portions of the service routine 28, disc scanner

32, compiler 34, verifier 36, response generator 38 and financial transactor 52 are associated with the medical transaction processing

kernel 22. The service routine 28, compiler 34, verifier 36, response generator 38, and financial transactor 52 are preferably, custom software routines, preferably written in COBOL.

Broadly, the transaction manager receiver 26 handles the communication protocol and handshaking to receive a data message from a computer station and the service routine 28 performs a security function to determine whether the computer station communicating with the transaction manager receiver is an authorized station. After

confirming the station is authorized, the transaction manager receiver 26 preferably stores the received data messages in a transmission file 30. Other functions needed to facilitate communication with the computer stations may be incorporated in service routine 28. Thus,

portions of service routine are part of the communications layer 24 while other portions are part of the processing kernel 22.

Periodically, a disc scanner 32 reviews the transmission file to locate any received data messages that have not been processed by the compiler 34. Upon finding such received data messages, the disc scanner 32 collects them from the transmission file 30 and supplies them to the compiler 34. The compiler retrieves the data from the data fields of the received data messages and organizes the data into a generic data record format. A verifier 36 checks the data fields within each generic data record to determine that the proper type of

data is in each data field. If the verifier 36 locates a generic data record that does not contain the proper type data within a data field, an error record is provided to a response generator 38 which converts the error record to a error message for transmission to the computer station that sent the erroneous message. Thus, a computer station may be informed that an improper data message has been received. The error message is stored in a response file 40 for later transmission. The verifier 36 also provides the verified generic data records and sufficient information to identify a data message that failed verification to the generic transaction database 20. If a verified generic record contains remittance information, verifier 36 collects the generic records necessary for the financial transaction to pay a provider and passes the records to the financial transactor 52 for processing which is discussed

in more detail below.

A review of the input process of Fig. 5 shows the components that permit the medical transaction system to communicate with a plurality of computer systems that support different data message formats and different communication protocols.

Such a system permits each healthcare provider and insurance carrier

to use any of the data fields available in the ANSI 837 standard for

medical claims. The system also permits the insurance carriers to utilize any of the data fields available in the ANSI 835 standard for remittance information. This latter capability provides the operator of such a system enormous flexibility in accommodating computer stations that utilize variations of the ANSI standards. Additionally, ail the data from the differently formatted messages are compiled into generic data records to facilitate the retrieval and use of information within the received data messages. In more detail, the receiver 26 portion of the transaction manager is capable of communicating with a computer station that

utilizes any of the more commonly known communication protocols such as ASYNC, BISYNC, X.25, as well as other known protocols.

Additionally, the transaction manager receiver 26 may be modified to

include software and hardware that communicates with a proprietary communication protocol utilized by a computer station. Such modification is capable of being performed by one of ordinary skill in

the art knowledgeable about the particular communication protocol.

The processing performed by the transaction manager receiver 26 is shown in flow chart form in Fig. 6. The transaction manager receiver 26 begins by monitoring the status of the input lines to the medical transaction system. (Box 100). Once the transaction manager recognizes that a computer station is attempting to send data, the transaction manager identifies the hardware interface and the corresponding communication protocol being used to send the data message. (Box 102). Transaction manager receiver 26 continues by performing the requisite handshaking to communicate with the sending computer station. (Box 104). Should there be a loss of the

handshaking signals, (decision box 106), transaction manager receiver 26 determines whether a retransmission should be requested. The retransmission request decision is based upon the retransmission parameters as defined by the protocol. For example, the number of retransmission requests may be compared to a predetermined limit and if the limit has been reached, communication is terminated, (Box 108),

and receiver 26 returns to monitoring the input lines. (Box 100). Otherwise, a retransmission request is transmitted, (Box 109), to the station via the transmitter 46 and the response is awaited. Having established the communication link with the computer station, the transaction manager receiver 26 inputs data from

the computer station, (Box 1 10), and builds a received data message,

(Box 1 10), until a complete data message has been received. (Box

1 14). If an insufficient amount of data is received to form a complete

data message, (Box 1 12), communication is terminated, (Box 108), or

a retransmission requested. (Box 109). Once a complete data message

has been received, the transaction manager receiver 26 passes it to the service routine 28. (Box 1 16). Transaction manager receiver 26

determines if the service routine 28 is processing a security or data message, (for example, by checking the data and security message

flags), and writes a complete data message to transmission file 30, (Box 1 19), or returns to monitoring the input lines for data messages,

(Box 100). Both the data message and station identification code are preferably written to the transmission file 30. (Box 1 19).

The processing performed by the service routine 28 is shown in the flow chart of Fig. 7. After the data message received from the computer station is provided to service routine 28 by the transaction manager receiver 26, the service routine 28 examines the

received data message, (Box 120), and, if the received data message is the initial one from a station, (Decision Box 122), routine 28

identifies the computer station from a computer station identification code within the received data message. (Box 124). For the initial message, service routine 28 formats a data message or messages, (Box

126), that request additional security information from the computer

station. Alternatively, the initial message may contain security information which is processed to determine whether the station is

authorized. The messages are provided to the transmitter 46 (Fig. 1 1 )

of the transaction manager, (Box 128), discussed in more detail below,

which transmits the security message to the identified computer station. Service routine 28 then waits for the next message. (Box 130).

After the transaction manager receiver 26 has received the

response to the security message and provided it to the service routine

28, routine 28 determines if the message is a security message response. (Decision Box 132). If it is, the security message is analyzed to determine if the identified computer station is an authorized computer station. (Box 134). If it is not, communication is terminated.

(Box 136). If the station is authorized, the service routine 28 sets the security flag for the station, (Box 135), and waits for the next data message from the computer station. (Box 130). For a data message, service routine 28 sets a data flag, (Box 138), to indicate the message contains data (not security information) and returns the data message to the transaction manager receiver 26. (Box 140). Data messages are routed through the service routine 28 to provide the service routine with the opportunity to provide other generic communication functions, if any are needed.

In further detail, the transmission file 30 and disc scanner

32 utilized in the preferred embodiment of the medical transaction system form a data message buffer for the received data messages that are processed by the medical transaction processing kernel 22.

Alternatively, the service routine 28 may provide the received data messages in real time to the compiler 34 and the transmission file 30

and disc scanner 32 may be eliminated from the input process. Such

a process, however, requires that the compiler 34 be able to receive

and compile information from the received data messages as quickly as

they are produced by the service routine 28. The transmission file 30

and disc scanner 32 reduce the rate at which the compiler must

process the data messages below the rate at which the service routine

28 may provide them.

In more detail, the compiler processing is shown in the

flow chart of Fig. 8. The compiler 34 initiates its processing by taking

a received data message and station identifier from the disc scanner

32, (Box 1 50), and retrieves the data message format for the received

message by using the computer station identification code. (Box 1 52).

The format is used to extract data from the received data message,

(Box 1 54), and the extracted data is inserted into a generic data record that corresponds to the station identification code, (Box 1 56), which is passed to the verifier. (Box 1 58). The compiler 34 checks to see if

there are any other data messages to process, (Decision Box 1 60), and

if there are, the processing continues. If there are no other data

messages to process, the compiler 34 terminates its processing.

The formats for the generic records preferably differ for

the types of computer stations. That is, one type of generic format is

used for a healthcare provider, such as a doctor, while another type of

generic record format is used for another type of healthcare provider,

such as a hospital. Likewise, the generic record formats for the various

types of trading partners may also vary. Appendix A is attached hereto

and is explicitly incorporated into this specification by reference.

Appendix A shows the preferred generic record formats for the medical

claim generic records and error records stored within the generic

transaction database of the preferred embodiment. Appendix A also

shows that the generic record formats contain some data fields that are

common to all of the data message formats received by the system.

These common data fields are organized in the generic records to

facilitate the use of the records within the database. Preferably, the

generic transaction database is written in SQL (Structured Query

Language) which provides a generic structure for a relational database.

With further reference to Appendix A, the tables identified

as AAO, BAO, BA1 , CAO, CBO, DAO, DA1 , DA2, EAO, EA1 , 121 , I34,

I40, 141 , I44, I50, I60, 161 , I7A, I7B, 171 , I72, I73, I74, I80, 181 , FAO,

FBO, FB1 , GAO, GCO, GDO, GD1 , GEO, GPO, GXO, GX1 , GX2, and

HAO are record formats for data that may be within a data message

containing a medical claim. Additionally, some of the data record

formats are primarily used for data within a medical claim from an

institution, such as a hospital, although a doctor may include such data

within a medical claim. Record formats AAORESP, BAORESP,

CAORESP, and DAORESP are the error record formats preferably used

that contain the identifying information for an erroneous message.

Comparing these record formats with those defined in tables AAO,

BAO, CAO, and DAO shows that most of the message identifying

information comes from these four generic record formats. The generic

record formats for the remittance records are preferably defined by the

ANSI 835 standard as specified by the Health Care Financing

Administration (HCFA) for Medicare claims. This specification is set

forth in Implementation Manual For The 835 Health Care Claim

Pa vmen t/A dvice by James Moynihan, printed by Healthcare Financial

Management Association (HFMA) of Westchester, Illinois 601 54.

The processing of the verifier 38 of the preferred

embodiment is shown in further detaii in the flow chart of Fig. 9.

Verifier 36 begins by initializing a generic record pointer to the first data

field of the generic record received from compiler 34. (Box 1 64).

Verifier 36 determines the type of generic record being examined, (Box

1 66), so the data types for the fields may be checked. If the data type

within the field to which the generic record pointer points is correct,

(Decision Box 1 68), the generic record pointer is incremented so it

points to the next data field in the record. (Box 1 70). If the end of the

record has been reached, (Decision Box 172), the generic record is

preferably written to the generic transaction database 20. (Box 174).

Verifier 36 determines if the generic record contains remittance

information from a trading partner station, (Decision Box 1 76), and if

it does, verifier 36 collects the generic records necessary to pay a

provider and passes the records to financial transactor 52 for

processing. (Box 1 78). Verifier 36 then determines if there are more

records to verify, (Decision Box 1 80), and if there are, processing

continues. Otherwise, processing is terminated.

If an erroneous data type is detected, i.e., a character field has numeric data or vice versa, (Decision Box 168), an error flag is set, (Box 181 ), and the processing continues. (Box 170). At the end of the record, (Decision Box 172), verifier 38 determines if the error flag is set. (Decision Box 173). If it is, the verifier 36 extracts information from the record to identify the record for error logging purposes. (Box 182). The message identifying information is placed in an error record that is written to the generic transaction database 20. (Box 184). The error record is also passed to response generator 38. (Box 186).

Alternatively, verifier 38 may not pass the error record to response generator 38, but instead let response generator 38 retrieve them from the database 20. The verifier 36 determines whether the compiler 34 has another generic record for it to process, (Decision Box 180), and if it does, the data field testing is performed on the record. Otherwise, the verifier terminates its processing.

The processing of the response generator 38 is shown in the flowchart of Fig. 10. Response generator 38 begins by determining if there are any error records from verifier 36. (Decisions Box 190). If there are, the error records are converted to error messages, each with

a format corresponding to the computer station identifier, (Box 192), which are written to the response file 40. (Box 194). Processing

continues by checking for more error messages. (Decision Box 190).

If there are no error messages to process, response

generator 38 determines if it is time to collect error messages for transmission to computer stations. (Decision Box 196). If it is, a

computer station identifier is selected, (Box 198), and the formatted error messages corresponding to the station identifier are collected from

response file 40. (Box 200). The collected error messages are provided to transaction manager transmitter 46 (Fig. 1 1 ) for transmission to the

computer station. (Box 202). If there are more station identifiers, (Decision Box 204), error message collecting continues. Otherwise,

processing terminates. Alternatively, response generator 38 may periodically retrieve error records for a predetermined computer station identification code or series of such codes, convert the records to error messages, and supply the messages to the transmitter 46 for transmission to the corresponding station(s).

The remaining components of the medical transaction process kernel are shown in Fig. 1 1 . These components include an extractor 42 for extracting generic data records from the generic transaction database 20, a formatter 44 for reorganizing the data from the generic data records into a format specific to a computer station, and the transmitter 46 portion of the transaction manager which

provides the protocol specific elements for transmitting the formatted

records to the computer station. The receiver 26 and transmitter 46

of the transaction manager form the communications layer 24,

discussed above. The extractor 42 and formatter 44 are custom

written software routines, preferably written in COBOL with embedded

SQL commands. The extractor 42 and formatter 44 are components of the medical transaction processing kernel 22. Preferably, statistical analyzer 48, also a custom written SQL program is included to perform statistical analysis on generic transaction database 20, as discussed in

more detail below, to produce a statistical database or report 50.

Additionally, statistical analyzer 48 may be supplemented for more rigorous analysis, such as correlation, with commercially available statistical software.

The processing of the extractor 42 is shown in more detail in Fig. 12, The extractor routine is activated by receipt of an extract

command that identifies a computer station. Preferably, the operating system activates the extractor routine at a predetermined time. Alternatively, a user at the medical transaction system could submit a request for generic data records corresponding to a particular computer station or a batch job could be submitted that is executed in due course by the operating system to activate the extractor routine. Once

activated, the extractor 42 either retrieves the computer station identification code from the activation command or sequences through a predetermined set of station identification codes to extract records. Once the extractor retrieves a computer station

identification code, (Box 210), the generic records to be sent to that computer station are extracted from the generic transaction database

20. (Box 212). The extracted records are put in a data message block,

(Box 214), to be sent to the computer station and the data message

block is provided to the formatter 44. (Box 216). The extractor 42 determines whether another computer station identification code is available for processing, (Decision Box 218), and if it is, processing continues with the retrieval of the identification code for that station.

Otherwise, the extractor 42 terminates its processing.

The processing of the formatter 44 is shown in more detail

in the flow chart of Fig. 13. The formatter 44 first initializes a block pointer to the location of the first message in a data block passed by extractor 42. (Box 224). Formatter 44 retrieves the station identifier from the message. (Box 226). After extracting information from the data message, (Box 228), the information is formatted in a format that corresponds to the computer station identifier, (Box 230), and is written to a station message block. (Box 232). The block pointer is incremented to the next message location, (Box 234), and if the formatter 44 determines that there is another message in the data block to format into the station message format, (Decision Box 236),

processing of the message in the data message block continues. Otherwise, the station message block is provided to the transaction manager transmitter 46 for transmission to the computer station. The

formatter 44 determines whether another data message block is

available from the extractor 42, (Decision Box 240), and if it is, initializes the block pointer to the first message in the block and the

processing continues. Otherwise, processing for the formatter 44

terminates.

The transmitter 46 of the transaction manager is shown

in more detail in Fig. 14. After the formatter 44 provides the station

message block to the transaction manager 46, the transaction manager

initializes a transmitter pointer to the first message in a station message

block, (Box 246), and retrieves the station identification code, (Box

248), to determine the communication protocol for the computer

station. Any protocol specific elements that must be added to the data

message block for transmission to the computer station are inserted in

the station message block. (Box 250) . The transaction manager

transmitter 46 selects the hardware interface for transmission of the

data block to the computer station and transfers the protocol organized

message block to the hardware interface for the protocol corresponding

to the computer station. (Box 252) . The transaction manager

transmitter 46 determines whether another station block is available for

transmission, (Decision Box 254), and if it is, processing of the next

station message block continues. Otherwise, the transaction manager

transmitter 46 terminates processing.

Preferably, the processing components of Fig. 1 1 also

include a statistical analyzer 48. This analyzer, either periodically or

under explicit command from a terminal associated with the computer

platform executing the medical transaction system 1 8, performs

statistical data analysis on the information within the generic data

records of the generic transaction database 20. Preferably, the

statistical analyzer 48 uses the information in the generic data records

to produce reports containing information such as the outcomes for

particular types of diagnosis, identification of particular medical

protocols prescribed for particular conditions, analysis of medical treatment by demographic or by geographical constraints, or analysis of financial data such as the costs charged for a particular medical protocol or the like. Other types of statistical analysis of such a

database would be apparent to one of ordinary skill in the art.

In the preferred embodiment of the medical transaction

system 18, the receiver 26 of the transaction manager includes the protocol information corresponding to the trading partners. This information is used to perform the handshaking and security functions with the trading partners so messages may be received from the trading partners. Thus, the computer stations referenced in the processing blocks of Fig. 7 include the computer stations associated with the trading partners.

The compiler 34 of the preferred embodiment also includes

data message format information regarding the data messages transmitted by the trading partners. Particularly, the compiler 34

includes information regarding the parsing of the remittance information provided in such data messages. This remittance and claim adjudication information is organized into a generic data record format for a trading partner station that is preferably included in the generic

transaction database 20. Likewise, verifier 36 identifies the generic

records for each type of computer station and verifies the data fields

for each type of record. Similarly, response generator 38 generates error messages for data messages received from trading partners that are stored in the response file and the error messages for the trading partners are periodically collected for transmission to inform them of

erroneously transmitted messages.

The extractor 42 of the preferred embodiment further includes the retrieval of computer station identification codes for healthcare providers so generic data records corresponding to the healthcare provider stations may be extracted . The formatter 44 of the

preferred embodiment further includes the message data formats for data messages that contain information about the adjudication of a submitted claim. With this information, the formatter 44 formats message data blocks for a healthcare provider that is transmitted by the transaction manager transmitter to the computer station of a healthcare provider. Thus, the preferred embodiment provides a complete data communication path from the healthcare providers to the trading

partners and from the trading partners to the healthcare providers.

One of ordinary skill in the art understands the

communication path provided through the preferred embodiment of the medical transaction system 18 also permits one healthcare provider to

communicate with another healthcare provider. Such a communication

path would permit a healthcare provider to retrieve medical history from

another healthcare provider, such as a referring physician. Thus, the

preferred embodiment of the system is capable of providing medical

data information in a system that is also capable of processing medical claims.

The preferred embodiment of the medical transaction system may also include the financial transactor 52 as shown in Fig.

5. Once, a data message containing remittance information is received

from a trading partner, the verifier 36 provides the generic data record to the financial transactor 52. The financial transactor 52 processes the remittance information to generate electronic funds transfer messages that are put in a message data block along with a computer station identification code that identifies a financial institution. The formatter 44 formats the message data block into a station message block for the trading partner as discussed previously. The station message block is provided to the transaction manager which transmits the messages to the specified trading partner. In this manner, the

financial transactor 52 generates the data messages that are transmitted to the financial institutions for crediting and debiting

accounts in accordance with the claim adjudication and remittance information provided by the trading partners that are insurance carriers.

The processing of the financial transactor 52 is shown in Fig. 15. Transactor 52 begins by extracting remittance information

from the generic record(s) passed to it by verifier 36. (Box 260). The

remittance information is used to generate the electronic funds transfer

messages (EFTs), (Box 262), that result in accounts being credited and debited at the financial institutions that are trading partners so the

claims are paid. Additionally, any other messages responsive to remittance information or financial institution information received from

a trading partner are generated. The EFTs and related messages are provided to formatter 44, (Box 264), for formatting in the data

message format that corresponds to the computer station identification codes for the computer stations at the financial institutions designated for the EFTs and related messages. Currently, the data message format for the messages to the financial institutions are the same since the financial institutions communicate with each other through a computer system called a clearinghouse that imposes the same format on all of its users. However, the system of the present invention contemplates formatting data messages to the financial institutions as

they differ from one another. If there are no other generic records to process, (Decision Box 266), processing terminates. Otherwise, financial transactor 52 continues processing the records.

As can be understood from the operation of the preferred

embodiment of the medical transaction system 18, the invention couples a plurality of healthcare providers to a plurality of payors and

financial institutions. The system 18 provides communication paths to the computer station of each of these various parties. This

communication capability is achieved by the system's capability to translate between the data message formats and communication

protocols of the trading partners and healthcare providers.

A further advantage of the medical transaction system 18

is its capability of extracting information from the data messages passing through it and accumulating this information in generic data message formats. The storage of these generic data message records in the generic transaction database 20 permits a statistical analyzer to

generate statistical information that is not insurance carrier specific.

Rather, the statistical analysis can cut across a number or selected

subgroup of the payors or healthcare providers. The information from such a statistical analyzer is extremely beneficial in understanding healthcare costs and developing ways to contain such costs. One of ordinary skill in the art is capable of developing such a statistical

analyzer.

The ability of the medical transaction system to communicate with financial institutions provides a further advantage to the medical transaction system 18 of Fig. 5. In a more preferred embodiment of the invention, one or more of the financial institutions extends credit lines solely for the purpose of medical claims to the patients of the healthcare providers. When such a credit line is

available at one of the trading partners, the financial transactor 52 of the preferred embodiment further determines whether the remittance

information from a payor fully covers a submitted medical claim. If it

does not, the financial transactor 52 generates the credit authorization messages that are transmitted to a trading partner station located at a

credit processor or financial institution, where the medical credit line is

managed and processed, to determine whether the credit line has the remaining amount of the ciaim available. The credit processor or financial institution responds with data messages that indicate whether the credit is available for the remainder of the claim, and, in response, the financial transactor 52 generates the credit and debit messages that cover the remainder of the medical claim.

While the present invention has been illustrated by description of several embodiments and while the illustrative embodiments have been described in considerable detail, it is not the intention of applicants to restrict or in any way limit the scope of the appended claims to such detail. Additional advantages and modifications will readily appear to those skilled in the art. For example, verifier 36 may test certain data fields to determine if the data within the field is accurate as long as the test does not require the use of historical data, e.e., eligibility files or the like. The invention in its broader aspects is therefore not limited to the specific details, repre¬

sentative apparatus and methods, and illustrative examples shown and described. Accordingly, departures may be made from such details without departing from the spirit or scope of applicants' general

inventive concept.

Having described our invention, we claim:

MEDICAL TRANSACTION SYSTEM

APPENDIX A

SQL Conversational Interface - T9191 C30 - (12FEB92) COPYRIGHT TANDEM COMPUTERS INCORPORATED 1987-1992

> > INVOKE = ALARM;

-- Definition of table \EDI.$DATA1.MMRPRDAT.ALARM -- Definition current at 16:17:31 - 10/19/93

(

CO ALARM DATE DATETIME YEAR TO DAY DEFAULT SYSTEM NOT NULL HEADING 'Date'

CO , ALARM Jϊ ME DATETIME HOUR TO SECOND DEFAULT SYSTEM NOT NULL HEADING 'Time'

, ALARM_PROCESS CHAR! 8 ) DEFAULT SYSTEM NOT NULL HEADING 'Process' m , ALARM JOBID CHAR! 10 ) DEFAULT SYSTEM NOT NULL HEADING 'Job ID' O

_E , ALARM_TYPE CHAR( 2 ) DEFAULT SYSTEM NOT NULL HEADING 'Error Type'

, ALARM SQLCODE NUMERIC! 4, 0) DEFAULT SYSTEM NOT NULL HEADING 'SQL/Error'

, ALARM_FSCODE NUMERIC! 4, 0) DEFAULT SYSTEM NOT NULL HEADING 'Guardian/Error' r - , ALARM TEXT CHAR! 160 ) DEFAULT SYSTEM NOT NULL HEADING 'Error Description'

> > INVOKE =AA0;

-- Definition of table \EDI.$DATA1.MMRPRDAT.AA0

- Definition current at 16:17:31 - 10/19/93

<

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL

, SUBMIS_TS DATETIME YEAR TO FRACTION^) NO DEFAULT NOT NULL

, SUBMIS NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL

, RECEIVER_CODE CHAR! 3 ) NO DEFAULT NOT NULL

, EXTRACT_TS DATETIME YEAR TO FRACTION^) NO DEFAULT NOT NULL

, AAO_SUBMIT_ID CHAR! 16 ) NO DEFAULT NOT NULL

, AAO_SUBMIS_TYPE CHAR! 6 ) NO DEFAULT NOT NULL

, AAO_SUB_NAME CHAR! 33 ) NO DEFAULT NOT NULL

, AA0_SUB_ADDR1 CHAR! 30 ) NO DEFAULT NOT NULL

, AA0_SUB_ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL

, AAO_SUB_CITY CHAR! 20 ) NO DEFAULT NOT NULL

CO , AAO_SUB_STATE CHAR! 2 ) NO DEFAULT NOT NULL e

CΛ , AAO_SUB_ZIP CHAR! 9 ) NO DEFAULT NOT NULL

, AAO_SUB_REGION CHAR! 5 ) NO DEFAULT NOT NULL

, AA0_SUB_CONTACT CHAR! 33 ) NO DEFAULT NOT NULL O c , AA0_SUB_PHONE CHAR! 10 ) NO DEFAULT NOT NULL

, AAO_CREATE_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL 3 , AAO_SUBMIS_TIME CHAR! 6 ) NO DEFAULT NOT NULL _

, AAO_RECEIVER_ID CHAR! 16 ) NO DEFAULT NOT NULL * . , AAO_RECEIVER_TYPE CHAR! 1 ) NO DEFAULT NOT NULL

, AA0_VERSION_NCODE DECIMAL! 5, 0 ) UNSIGNED NO DEFAULT NOT NULL

, AA0_VERSION_LCODE DECIMAL! 5, 0 ) UNSIGNED NO DEFAULT NOT NULL

, AA0_TP_FLAG CHAR! 4 ) NO DEFAULT NOT NULL

, AA0_PASSWORD CHAR! 8 ) NO DEFAULT NOT NULL

, AAO_RETRANS_STATUS CHAR! 1 I NO DEFAULT NOT NULL

, AAO_MULT_BILL_IND DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL

, AA0_CNTL_FILE_NO CHAR! 16 ) NO DEFAULT NOT NULL

, AAO INST PROF IND CHAR! 1 ) NO DEFAULT NOT NULL

, AAO_RECEIVER_SUB_ID CHAR! 4 ) NO DEFAULT NOT NULL

, AAO_FILE_LINE_COUNT DECIMAL! 7, 0 ) NO DEFAULT NOT NULL

, AAO_FILE_REC_COUNT DECIMAL! 7, 0 ) NO DEFAULT NOT NULL

, AA0_FILE_CLAIM_COUNT DECIMAL! 7, 0 ) NO DEFAULT NOT NULL

, AAO_BATCH_COUNT DECIMAL! 4, 0 ) NO DEFAULT NOT NULL

. AA0_FILE_TOT_CHGS DECIMAL! 9, 2 ) NO DEFAULT NOT NULL

, AA0_ACCOM_TOT_CHGS DECIMAL! 11 , 2 ) NO DEFAULT NOT NULL

, AA0_ACCOM_NCOV_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

(/) , AAO_ANCIL_TOT_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

__ O CO , AAO_ANCIL_NCOV_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, AAO_SUB_ID_NO CHAR! 10 ) NO DEFAULT NOT NULL m , AAO_FILE_REC_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL co r , TOT_RECS DECIMAL! 7, 0 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL 3 , TOT_CHGS_G00D DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_ACCOM_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL n , TOT_ACC0M_CHGS_G00D DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_NC0V_ACC0M_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_NCOV_ACCOM_CHGS_GOOD DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_ANCIL_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_ANCIL_CHGS_G00D DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_NCOV_ANCIL_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_NC0V_ANCIL_CHGS_G00D DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_CLAIMS_IN_BATCH DECIMAL! 5, 0 ) UNSIGNED NO DEFAULT NOT NULL

, TOT CLAIMS IN BATCH GOOD DECIMAL! 5, 0 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_BATCHES_IN_SUB DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_BATCHES_IN_SUB_GOOD DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, INT_ERR_TYPE CHAR! 2 ) NO DEFAULT NOT NULL

, INT_REC_TYPE CHAR! 3 > NO DEFAULT NOT NULL

, INT_ERR_CODE CHAR! 4 ) NO DEFAULT NOT NULL

, INP_REC_TYPE CHAR! 3 ) NO DEFAULT NOT NULL

, INP_ERR_CODE CHAR! 4 ) NO DEFAULT NOT NULL

, FIELD_CONTENT CHAR! 30 ) NO DEFAULT NOT NULL O ) = D O > > INVOKE = BA0;

^« Definition of table \EDI.$DATA1 .MMRPRDAT.BAO

-- Definition current at 16:17:35 - 10/19/93 O c

(

SUBMITTER_CODE CHAR! 3 » NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONI6) NO DEFAULT NOT NULL - n , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , BA0_EMC_PROV_ID CHAR! 15 ) NO DEFAULT NOT NULL , BAO_BATCH_TYPE CHAR! 3 ) NO DEFAULT NOT NULL , BA0_BATCH_NO CHAR! 4 ) NO DEFAULT NOT NULL , BAO_BATCH_ID CHAR! 6 ) NO DEFAULT NOT NULL , BA0_PROV_TAXID CHAR! 9 ) NO DEFAULT NOT NULL , BAO_PROV_TAXID_TYPE CHAR! 1 ) NO DEFAULT NOT NULL , BAO PROV MEDICARE NO CHAR! 15 ) NO DEFAULT NOT NULL

BA0_PROV_UPIN_USIN_ID CHAR! 6 » NO DEFAULT NOT NULL

BA0_PROV_MEDICAID_NO CHAR! 15 ) NO DEFAULT NOT NULL

BA0_PROV_CHAMPUS_NO CHAR! 15 ) NO DEFAULT NOT NULL

BA0_PROV_BCBS_NO CHAR! 15 ) NO DEFAULT NOT NULL

BA0_PROV_COMM_NO CHAR! 15 ) NO DEFAULT NOT NULL

BA0_PROV_NO_1 CHAR! 15 ) NO DEFAULT NOT NULL

BA0_PROV_NO_2 CHAR! 15 ) NO DEFAULT NOT NULL

BA0_PROV_ORG_NAME CHAR! 33 ) NO DEFAULT NOT NULL > BA0_PROV_LAST_NAME CHAR! 20 ) NO DEFAULT NOT NULL _ O BA0_PROV_FIRST_NAME CHAR! 12 ) NO DEFAULT NOT NULL

BA0_PROV_MI CHAR! 1 ) NO DEFAULT NOT NULL

BA0_PROV_SPECIALTY CHAR! 3 ) NO DEFAULT NOT NULL O BA0_SPECIALTY_LI_NO CHAR! 15 ) NO DEFAULT NOT NULL C

BA0_STATE_LI_NO CHAR! 15 ) NO DEFAULT NOT NULL

BA0_DENTIST_LI_NO CHAR! 15 ) NO DEFAULT NOT NULL

BA0_ANESTHESIA_LI_NO CHAR! 15 ) NO DEFAULT NOT NULL

BA0_CNTL_BATCH_NO CHAR! 20 ) NO DEFAULT NOT NULL

BA0_BATCH_LINE_COUNT DECIMAL! 7, 0 ) NO DEFAULT NOT NULL

BA0_BATCH_REC_COUNT DECIMAL! 7, 0 ) NO DEFAULT NOT NULL

BAO_BATCH_CLAIM_COUNT DECIMAL! 7, 0 ) NO DEFAULT NOT NULL

BA0_BATCH_TOT_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

BA0_ACCOM_TOT_CHGS DECIMAL! 12, 2 ) NO DEFAULT NOT NULL

BA0_ACCOM_NCOV_CHGS DECIMAL! 12, 2 ) NO DEFAULT NOT NULL

BA0_ANCIL_TOT_CHGS DECIMAL! 12, 2 ) NO DEFAULT NOT NULL

BAO ANCIL NCOV CHGS DECIMAL! 12, 2 ) NO DEFAULT NOT NULL

, BA0_PROVIDER_SUB_ID CHAR! 10 I NO DEFAULT NOT NULL

, TOT_RECS DECIMAL! 5, 0 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_CHGS DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_CHGS_GOOD DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_ACCOM_CHGS DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_ACCOM_CHGS_GOOD DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_NCOV_ACCOM_CHGS DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_NCOV_ACCOM_CHGS_GOOD DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL O , TOT_ANCIL_CHGS DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL _ α o , TOT_ANCIL_CHGS_GOOD DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_NCOV_ANCIL_CHGS DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_NCOV_ANCIL_CHGS_GOOD DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL o π , TOT_CLAIMS_IN_BATCH DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_CLAIMS_IN_BATCH_G00D DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL 3 , INT_ERR_TYPE CHAR! 2 ) NO DEFAULT NOT NULL _

, INT_REC_TYPE CHAR! 3 I NO DEFAULT NOT NULL _ . , INT_ERR_CODE CHAR! 4 ) NO DEFAULT NOT NULL

, INP_REC_TYPE CHAR! 3 ) NO DEFAULT NOT NULL

, INP_ERR_CODE CHAR! 4 ) NO DEFAULT NOT NULL

, FIELD_CONTENT CHAR! 30 ) NO DEFAULT NOT NULL

)

> > I VOKE = BA1 ;

-- Definition of table \EDI.$DATA1 .MMRPRDAT.BA1

-- Definition current at 16:17:38 - 10/19/93

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS JO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , BA1_PR0V_0RG_TYPE CHAR! 3 ) NO DEFAULT NOT NULL , BA1_PR0V_SVC_ADDR1 CHAR! 30 ) NO DEFAULT NOT NULL , BA1_PR0V_SVC_ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL

CO , BA1_PR0V_SVC_CITY CHAR! 20 » NO DEFAULT NOT NULL O O , BA1_PR0V_SVC_STATE CHAR! 2 ) NO DEFAULT NOT NULL , BA1_PR0V_SVC_ZIP CHAR! 9 ) NO DEFAULT NOT NULL m , BA1_PR0V_SVC_PH0NE CHAR! 10 ) NO DEFAULT NOT NULL co , BA1_PR0V_PAYT0_ADDR1 CHAR! 30 » NO DEFAULT NOT NULL , BA1_PR0V_PAYT0_ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL , BA1_PR0V_PAYT0_CITY CHAR! 20 ) NO DEFAULT NOT NULL rπ , BA1_PR0V_PAYT0_STATE CHAR! 2 ) NO DEFAULT NOT NULL rvj , BA1_PR0V_PAYT0_ZIP CHAR! 9 ) NO DEFAULT NOT NULL , BA1_PR0V_PAYT0_PH0NE CHAR! 10 ) NO DEFAULT NOT NULL ) > > INVOKE =CA0; - Definition of table \EDI.$DATA1 ■ MMRPRDAT.CAO -- Definition current at 16:17:40 - 10/19/93

SUBMITTER CODE CHAR! 3 ) NO DEFAULT NOT NULL

SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL

SUBMIS_N0 DECIMAL! 6, 0 I NO DEFAULT NOT NULL

BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

PAT_CNTL_N0 CHAR! 20 ) NO DEFAULT NOT NULL

CLAIM_SEQ_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

CAO_PAT_LAST_NAME CHAR! 20 ) NO DEFAULT NOT NULL

CAO_PAT_FIRST_NAME CHAR! 12 ) NO DEFAULT NOT NULL

CA0_PAT_M I DDLEJNIT CHAR! 1 ) NO DEFAULT NOT NULL

CA0_PAT_GENERATION CHAR! 3 ) NO DEFAULT NOT NULL σ CA0_PAT_DOB DATETIME YEAR TO DAY NO DEFAULT NOT NULL 0

CAO_PAT_SEX CHAR! 1 ) NO DEFAULT NOT NULL

CAO_PAT_RES_TYPE CHAR! 1 ) NO DEFAULT NOT NULL o CA0_PAT_ADDR1 CHAR! 30 ) NO DEFAULT NOT NULL c

CA0_PAT_ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL

CAO_PAT_CITY CHAR! 20 ) NO DEFAULT NOT NULL

CAO_PAT_STATE CHAR! 2 ) NO DEFAULT NOT NULL

CA0_PAT_ZIP_C0DE CHAR! 9 ) NO DEFAULT NOT NULL

CA0_PAT_PHONE CHAR! 10 ) NO DEFAULT NOT NULL

CAO_PAT_MARTIAL_STAT CHAR! 1 ) NO DEFAULT NOT NULL

CAO_PAT_STUDENT_STAT CHAR! 1 ) NO DEFAULT NOT NULL

CA0_PAT_EMPLOY_STAT CHAR! 1 > NO DEFAULT NOT NULL

CAO_PAT_DEATH_IN CHAR! 1 ) NO DEFAULT NOT NULL

CA0_PAT_DOD DATETIME YEAR TO DAY NO DEFAULT NOT NULL

CA0_OTHER_INSU_IN CHAR! 1 ) NO DEFAULT NOT NULL

CAO CLAIM_EDIT_IN CHAR! 1 ) NO DEFAULT NOT NULL

, CAO_CLAIM_TYPE_IN CHAR! 2 ) NO DEFAULT NOT NULL , CAO_LEGAL_REP_IN CHAR! 1 ) NO DEFAULT NOT NULL , CA0_ORIGIN_CODE CHAR! 9 ) NO DEFAULT NOT NULL , CA0_PAYOR_CNTL_NO CHAR! 17 ) NO DEFAULT NOT NULL , CA0_PROV_N UMBER CHAR! 15 ) NO DEFAULT NOT NULL , CAO_CLAIM_ID_NUMBER CHAR! 6 ) NO DEFAULT NOT NULL , CA0_SUB_CLM_CNTL_NO CHAR( 30 ) NO DEFAULT NOT NULL , CA0_ADMISSION_TYPE CHAR! 1 ) NO DEFAULT NOT NULL

CO , CA0_ADMISSION_SOURCE CHAR! 1 ) NO DEFAULT NOT NULL

GO CO , CA0_ACCIDENT_HOUR CHAR! 2 ) NO DEFAULT NOT NULL , CAO_ADMIT_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL

-H m , CA0_ADMIT_HOUR DECIMAL! 2, 0 ) NO DEFAULT NOT NULL co x . CA0_STMT_PERIOD_FROM DATETIME YEAR TO DAY NO DEFAULT NOT NULL m rπ , CA0_STMT_PERIOD_THRU DATETIME YEAR TO DAY NO DEFAULT NOT NULL , CAO_PATIENT_STATUS CHAR! 2 ) NO DEFAULT NOT NULL m , CAO_DISCHARGE_HOUR DECIMAL! 2, 0 ) NO DEFAULT NOT NULL en , CAO_MED_REC_NUM CHAR! 18 ) NO DEFAULT NOT NULL , CA0_TYPE_C_2_C0UNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CA0_TYPE_D_3_COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CA0_TYPE_E_4_COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CA0_TYPE_F_5_COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CA0_TYPE_G_6_COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CA0_TYPE_H_7_COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CA0_TYPE_l_8_COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CAO CLAIM REC COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL

, CA0_CLAIM_TOT_CHGS DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_DIS_CONTAIN_CHGS DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_DIS_OTHER_CHGS DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_TOTAL_ALLOW_AMT DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CAO_TOTAL_DEDUCT_AMT DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_TOTAL_COINSUR_AMT DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_TOTAL_PAYOR_AMT_PD DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_TOTAL_PAT_AMT_PD DECIMAL! 7, 2 ) NO DEFAULT NOT NULL O , CAO_TOTAL_SER_CHGS DECIMAL! 1, 2 ) NO DEFAULT NOT NULL 3 O . CA0_PROV_DISCOUNT_INFO CHAR! 16 ) NO DEFAULT NOT NULL I , CAO_REMARKS CHAR! 103 ) NO DEFAULT NOT NULL _

, CAO_ACCOM_TOT_CHGS DECIMAL! 10, 2 ) NO DEFAULT NOT NULL O π , CA0_ACCOM_NCOV_CHGS DECIMAL! 10, 2 ) NO DEFAULT NOT NULL

, CA0_ANCIL_TOT_CHGS DECIMAL! 10. 2 ) NO DEFAULT NOT NULL 3 , CA0_ANCIL_NCOV_CHGS DECIMAL! 10, 2 ) NO DEFAULT NOT NULL

, TOT_RECS DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL _ . , TOT_CHGS DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_CHGS_GOOD DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_ACC0M_CHGS DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_ACCOM_CHGS_GOOD DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_NCOV_ACCOM_CHGS DECIMAL! 7, 2 1 UNSIGNED NO DEFAULT NOT NULL

, TOT_NCOV_ACCOM_CHGS_GOOD DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_ANCIL_CHGS DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_ANCIL_CHGS_GOOD DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT NCOV ANCIL CHGS DECIMAL! 7, 2 > UNSIGNED NO DEFAULT NOT NULL

, TOT_NCOV_ANCIL_CHGS_GOOD DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, INT_ERR_TYPE CHAR! 2 ) NO DEFAULT NOT NULL

, INT_REC_TYPE CHAR! 3 ) NO DEFAULT NOT NULL

, INT_ERR_CODE CHAR! 4 ) NO DEFAULT NOT NULL

, INP_REC_TYPE CHAR! 3 ) NO DEFAULT NOT NULL

, INP_ERR_CODE CHAR! 4 ) NO DEFAULT NOT NULL

, FIELD_CONTENT CHAR! 30 ) NO DEFAULT NOT NULL

)

CO > > INVOKE =CB0;

__: O CO -- Definition of table \EDI.$DATA1.MMRPRDAT.CB0

- Definition current at 16:17:44 - 10/19/93

O

_E » m SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL m , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL * , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , CBO_REP_LAST_NAME CHAR! 20 ) NO DEFAULT NOT NULL , CBO_REP_FIRST_NAME CHAR! 12 ) NO DEFAULT NOT NULL , CBO_REP_MIDDLE_INIT CHAR! 1 ) NO DEFAULT NOT NULL , CB0_REP_ADDR1 CHAR! 30 ) NO DEFAULT NOT NULL , CB0_REP_ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL , CBO REP CITY CHAR! 20 ) NO DEFAULT NOT NULL

, CBO_REP_STATE CHAR! 2 ) NO DEFAULT NOT NULL , CB0_REP_ZIP_CODE CHAR! 9 ) NO DEFAULT NOT NULL , CB0_REP_PHONE CHAR! 10 ) NO DEFAULT NOT NULL )

> > INVOKE = DAO;

-- Definition of table \EDI.$DATA1.MMRPRDAT.DA0

- Definition current at 16:17:45 - 10/19/93

O O O SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTION^) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL O , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 . NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , DA0_OCCURS_NO DECIMAL! 2, 0 . UNSIGNED NO DEFAULT NOT NULL o , DA0_SEQ_NO CHAR! 2 ) NO DEFAULT NOT NULL , DAO_CLAIM_FILE_IN CHAR! 1 ) NO DEFAULT NOT NULL , DA0_PAY_SOURCE CHAR! 1 ) NO DEFAULT NOT NULL , DAO_INSURE_TYPE CHAR! 2 ) NO DEFAULT NOT NULL , DA0_PAYOR_ORG_ID CHAR! 5 1 NO DEFAULT NOT NULL , DA0_PAYOR_OFF_NO CHAR! 4 ) NO DEFAULT NOT NULL , DA0_PAY0R_NAME CHAR! 33 ) NO DEFAULT NOT NULL , DA0_GROUP_NO CHAR! 20 ) NO DEFAULT NOT NULL , DAO GROUP NAME CHAR! 33 ) NO DEFAULT NOT NULL

, DA0_PPO_HMO_IN CHAR! 1 ) NO DEFAULT NOT NULL

, DA0_PPO_ID CHAR! 15 ) NO DEFAULT NOT NULL

, DA0_PRIOR_AUTH_NO CHAR! 15 ) NO DEFAULT NOT NULL

, DAO_ASSIGN_BEN_IN CHAR! 1 ) NO DEFAULT NOT NULL

, DA0_PAT_SIGN_SOURCE CHAR! 1 ) NO DEFAULT NOT NULL

, DAO_PAT_INSURED_REL DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL

, DA0_INSURED_ID_NO CHAR! 25 ) NO DEFAULT NOT NULL

, DAO_INSURED_LAST_NAME CHAR! 20 ) NO DEFAULT NOT NULL O , DAO_INSURED_FIRST_NAME CHAR! 12 ) NO DEFAULT NOT NULL r¬ _¬ n , DAO_INSURED_MI CHAR! 1 ) NO DEFAULT NOT NULL

, DA0_INSURED_GENERATION CHAR! 3 ) NO DEFAULT NOT NULL

, DAO_INSURED_SEX CHAR! 1 ) NO DEFAULT NOT NULL O , DA0_INSURED_DOB DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, DAO_INSURED_EMP_STATUS CHAR! 1 ) NO DEFAULT NOT NULL 3 , DAO_SUPLEMENT_INS_IN CHAR! 1 ) NO DEFAULT NOT NULL

, DAO_TITLE_XIX_IN CHAR! 7 ) NO DEFAULT NOT NULL n , DA0_PRIMARY_PAYER_CODE CHAR! 1 ) NO DEFAULT NOT NULL

, DA0_REL_INFO_CERT_IND CHAR! 1 ) NO DEFAULT NOT NULL

, DA0_EMPLOY_STATUS_CODE CHAR! 1 ) NO DEFAULT NOT NULL

, DA0_COVERED_DAYS DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, DA0_NON_COVERED_DAYS DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, DAO_COINSURANCE_DAYS DECIMAL! 3. 0 ) UNSIGNED NO DEFAULT NOT NULL

, DAO_LIFETIME_RESV_DAYS DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, DA0_PROV_ID_NUM CHAR! 13 ) NO DEFAULT NOT NULL

)

> > INVOKE = DA1 ;

-- Definition of table \EDI.$DATA1 .MMRPRDAT.DA1

-- Definition current at 16: 17:47 - 10/19/93

(

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_N0 DECIMAL! 6, 0 ) NO DEFAULT NOT NULL O , BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL O 0 , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , DA1_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL o , DA1_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL , DA1_PAY0R_ADDR1 CHAR! 30 ) NO DEFAULT NOT NULL , DA1_PAY0R_ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL , DA1_PAY0R_CITY CHAR! 20 ) NO DEFAULT NOT NULL i , DA1_PAY0R_STATE CHAR! 2 ) NO DEFAULT NOT NULL , DA1_PAYOR_ZIP CHAR! 9 ) NO DEFAULT NOT NULL , DA1_DIS_C0ST_C0NTAIN DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL , DA1_DIS_0THER DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL , DA1_ALL0WED_AMT DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL , DA1_DEDUCT_AMT DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL , DA1_C0INSURE_AMT DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL , DA1_PAY0R_AMT_PAID DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL , DA1 ZERO PAY IN CHAR! 1 ) NO DEFAULT NOT NULL

, DA1_ADJUD_IN_1 CHAR! 2 ) NO DEFAULT NOT NULL , DA1_ADJUD_IN_2 CHAR! 2 ) NO DEFAULT NOT NULL . DA1_ADJUD_IN_3 CHAR! 2 ) NO DEFAULT NOT NULL , DA1_CHAMP_SP0N_BRAN CHAR! 1 ) NO DEFAULT NOT NULL , DA1_CHAMP_SP0N_GRADE CHAR! 2 ) NO DEFAULT NOT NULL , DA1_CHAMP_SP0N_STATS CHAR! 1 ) NO DEFAULT NOT NULL , DA1_INS_CRD_EFF_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL , DA1_INS_CRD_TERM_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL

<s> , DA1_BAL_DUE DECIMAL! 7, 2 » UNSIGNED NO DEFAULT NOT NULL e__

03 CO ) > > INVOKE = DA2; ~ Definition of table \EDI.$DATA1 .MMRPRDAT.DA2 o - Definition current at 16:17:49 - 10/19/93

3 ! __

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL n , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_N0 DECIMAL! 4, 0 . UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , DA2_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , DA2_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL , DA2_INSURED_ADDR1 CHAR! 30 ) NO DEFAULT NOT NULL , DA2 INSURED ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL

, DA2_INSURED_CITY CHAR! 20 ) NO DEFAULT NOT NULL , DA2_INSURED_STATE CHAR! 2 ) NO DEFAULT NOT NULL , DA2_INSURED_ZIP CHAR! 9 ) NO DEFAULT NOT NULL , DA2_INSURED_PH0NE CHAR! 10 ) NO DEFAULT NOT NULL , DA2_INSURED_RET_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL , DA2_INSURED_SP0_RET_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL , DA2_INSURED_EMPL_NAME CHAR! 33 ) NO DEFAULT NOT NULL , DA2_INSURED_EMPL_ADDR1 CHAR! 30 ) NO DEFAULT NOT NULL , DA2_INSURED_EMPL_ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL _ o O , DA2_INSURED_EMPL_CITY CHAR! 20 ) NO DEFAULT NOT NULL , DA2_INSURED_EMPL_STATE CHAR! 2 ) NO DEFAULT NOT NULL , DA2_INSURED_EMPL_ZIP CHAR! 9 ) NO DEFAULT NOT NULL O , DA2_EMPL0YER_ID_N0 CHAR! 12 ) NO DEFAULT NOT NULL n . DA2_SPI CHAR! 2 ) NO DEFAULT NOT NULL 3 ) _ > > INVOKE = EAO; ~ Definition of table \EDI.$DATA1 .MMRPRDAT.EAO -- Definition current at 16:17:57 - 10/19/93

(

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 . UNSIGNED NO DEFAULT NOT NULL , PAT CNTL NO CHAR! 20 ) NO DEFAULT NOT NULL

, CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , EA0_0CCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , EA0_SEQ_NO CHAR! 2 ) NO DEFAULT NOT NULL . EAO_EMP_REL_IN CHAR! 1 ) NO DEFAULT NOT NULL , EAO_ACCIDENTJN CHAR! 1 ) NO DEFAULT NOT NULL , EA0_SYMPTOM_IN CHAR! 1 ) NO DEFAULT NOT NULL , EAO_ACC_SYMP_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL , EAO_EXT_ACC_CAUSEC CHAR! 5 ) NO DEFAULT NOT NULL co , EAO RESPONJN CHAR! 1 ) NO DEFAULT NOT NULL

03 CO , EAO_ACC_STATE CHAR! 2 ) NO DEFAULT NOT NULL , EA0_ACC_HOUR CHAR! 2 ) NO DEFAULT NOT NULL , EAO_ABUSE_IN CHAR! 1 ) NO DEFAULT NOT NULL

CO , EA0_INFO_RELEASE_IN CHAR! 1 ) NO DEFAULT NOT NULL , EA0_INFO_RELEASE_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL

73 , EAO_SAME_SYMP_IN CHAR! 1 ) NO DEFAULT NOT NULL , EAO_SAME_SYMP_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL r- en , EAO_DISABLE_TYPE CHAR! 1 > NO DEFAULT NOT NULL , EAO_DISABLE_FROM_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL , EAO_DISABLE_TO_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL . EA0_REFER_PR0_ID_NO CHAR! 15 ) NO DEFAULT NOT NULL , EAO_REFER_PRO_LAST CHAR! 20 » NO DEFAULT NOT NULL , EA0_REFER_PRO_FIRST CHAR! 12 ) NO DEFAULT NOT NULL , EAO_REFER_PRO_MI CHAR! 1 ) NO DEFAULT NOT NULL , EA0_REFER_PRO_ST CHAR! 2 ) NO DEFAULT NOT NULL , EAO_ADM_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, EAO_DIS_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, EA0_LAB_IN CHAR! 1 ) NO DEFAULT NOT NULL

. EAO_LAB_CHARGES DECIMAL! 5, 2 ) UNSIGNED NO DEFAULT NOT NULL

, EA0_DIAGNOSIS_CODE1 CHAR! 5 ) NO DEFAULT NOT NULL

, EA0_DIAGNOSIS_CODE2 CHAR! 5 ) NO DEFAULT NOT NULL

, EA0_DIAGNOSIS_CODE3 CHAR! 5 ) NO DEFAULT NOT NULL

, EA0_DIAGN0SIS_C0DE4 CHAR! 5 ) NO DEFAULT NOT NULL

, EA0_PRO_ASSIGN_IN CHAR! 1 ) NO DEFAULT NOT NULL > , EA0_PR0_SIGN_FILED CHAR! 1 ) NO DEFAULT NOT NULL r 0 0 , EA0_PRO_SIGN_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, EAO_FAC_LAB_NAME CHAR! 33 ) NO DEFAULT NOT NULL

, EA0_D0CUMENT_IN CHAR! 1 ) NO DEFAULT NOT NULL O , EA0_DOCUMENT_TYPE CHAR! 1 ) NO DEFAULT NOT NULL

, EA0_FUNC_STAT_CODE CHAR! 2 ) NO DEFAULT NOT NULL 3 , EA0_SPECIAL_PR0G_IN CHAR! 2 . NO DEFAULT NOT NULL

, EA0_CHAMP_NOAVAIL_IN CHAR! 1 ) NO DEFAULT NOT NULL _ n , EA0_SUPV_PR0V_IN CHAR! 1 ) NO DEFAULT NOT NULL

, EA0_RESUB_CODE CHAR! 2 ) NO DEFAULT NOT NULL

, EA0_RESUB_REF_NO CHAR! 15 ) NO DEFAULT NOT NULL

, EAO_DATE_LAST_SEEN DATETIME YEAR TO DAY NO DEFAULT NOT NULL

. > > INVOKE = EA1 ;

-- Definition of table \EDI.$DATA1.MMRPRDAT.EA1 - Definition current at 16:17:53 - 10/19/93

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTION^) NO DEFAULT NOT NULL , SUBMIS_N0 DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL . EA1_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL

CO , EA1_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL

00 CO , EA1_FAC_LAB_ID_N0 CHAR! 15 ) NO DEFAULT NOT NULL , EA1_FAC_LAB_ADDR1 CHAR! 30 ) NO DEFAULT NOT NULL , EA1_FAC_LAB_ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL O , EA1_FAC_LAB_CITY CHAR! 20 ) NO DEFAULT NOT NULL , EA1_FAC_LAB_STATE CHAR! 2 ) NO DEFAULT NOT NULL 3 , EA1_FAC_LAB_ZIP CHAR! 9 ) NO DEFAULT NOT NULL _ , EA1_MEDICAL_REC_N0 CHAR! 17 ) NO DEFAULT NOT NULL n . EA1_RETURN_T0_W0RK_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL , EA1_FIRST_C0NSULT_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL , EA1_ADM_DATE 2 DATETIME YEAR TO DAY NO DEFAULT NOT NULL , EA1_DISH_DATE_2 DATETIME YEAR TO DAY NO DEFAULT NOT NULL , EA1_SUPV_PR0V_ID_N0 CHAR! 15 ) NO DEFAULT NOT NULL , EA1_SUPV_PR0V_LNAME CHAR! 20 ) NO DEFAULT NOT NULL , EA1_SUPV_PR0V_FNAME CHAR! 12 ) NO DEFAULT NOT NULL , EA1_SUPV_PR0V_MI CHAR! 1 ) NO DEFAULT NOT NULL , EA1 SUPV PROV STATE CHAR! 2 ) NO DEFAULT NOT NULL

)

> > INVOKE =121 ;

-- Definition of table \EDI.$DATA1.MMRPRDAT.I21

-- Definition current at 16:17:56 - 10/19/93

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL

, SUBMIS_TS DATETIME YEAR TO FRACTION^) NO DEFAULT NOT NULL O , SUBMIS_N0 DECIMAL! 6, 0 | NO DEFAULT NOT NULL z 3 O , BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

, PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL

, CLAIM_SEQ_NO DECIMAL! 4, 0 . UNSIGNED NO DEFAULT NOT NULL o , I21_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL

, I21_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL 3 , I21_EMPL0YER_NAME CHAR! 18 . NO DEFAULT NOT NULL _

, I21_EMPL0YER_ADDR CHAR! 18 ) NO DEFAULT NOT NULL

, I21_EMPL0YER_CITY CHAR! 15 ) NO DEFAULT NOT NULL

, I21_EMPL0YER_STATE CHAR! 2 ) NO DEFAULT NOT NULL

, I21_EMPL0YER_ZIP CHAR! 9 ) NO DEFAULT NOT NULL

, I21_EMPL0YEE_ID_NUM CHAR! 12 ) NO DEFAULT NOT NULL

, I21_EMPL0Y_INF0_DATA CHAR! 1 ) NO DEFAULT NOT NULL

, I21_EMPL0Y_STATUS CHAR! 1 ) NO DEFAULT NOT NULL

) > > INVOKE = 134; - Definition of table \EDI.$DATA1.MMRPRDAT.I34

Definition current at 16: 17:58 - 10/19/93

( SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL

, SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL

, SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL

, BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

, PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL o , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

03 O , I34_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL

, I34_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL

, I34_AUTH_TYPE CHAR! 2 ) NO DEFAULT NOT NULL O , I34_AUTH_NUM CHAR! 18 ) NO DEFAULT NOT NULL

, I34_AUTH_DATE_FR0M DATETIME YEAR TO DAY NO DEFAULT NOT NULL 3 , I34_AUTH_DATE_THRU DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I34_AUTH_REC_NUM DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL ^* n , I34_AUTH_SEQ_NUM DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL

, I34_AUTH_FLD_ITER DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL

) > > INVOKE = 140;

-- Definition of table \EDI.$DATA1 .MMRPRDAT.I40 - Definition current at 16: 17:59 - 10/19/93

SUBMITTER CODE CHAR! 3 ) NO DEFAULT NOT NULL

, SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL

, SUBMIS_N0 DECIMAL! 6, 0 ) NO DEFAULT NOT NULL

, BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

. PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL

, CLAIM_SEQ_NO DECIMAL! 4, 0 . UNSIGNED NO DEFAULT NOT NULL

, I40_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL

, I40_SEQ_NO CHAR! 2 ) NO DEFAULT NOT NULL

, I40_BILL_TYPE CHAR! 3 ) NO DEFAULT NOT NULL O , I40_PRO_APRVJND CHAR! 1 ) NO DEFAULT NOT NULL r 0 O , I40_PRO_STAY_DT_FROM DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I40_PR0_STAY_DT_THRU DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I40_NUM_GRACE_DAYS DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL O , I40_TREAT_AUTH_CD_A CHAR! 18 . NO DEFAULT NOT NULL π , I40_TREAT_AUTH_CD_B CHAR! 18 ) NO DEFAULT NOT NULL

, I40_TREAT_AUTH_CD_C CHAR! 18 ) NO DEFAULT NOT NULL

, I40_BLOOD_PT_FURN DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL n , I40_BLOOD_PT_REPL DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, I40_BLOOD_PT_UNRPL DECIMAL! 3, 0 I UNSIGNED NO DEFAULT NOT NULL

, I40_BLOOD_PT_DED DECIMAL! 3, 0 . UNSIGNED NO DEFAULT NOT NULL

, I40_OCC_CODE_1 CHAR! 2 ) NO DEFAULT NOT NULL

, I40_OCC_DATE_1 DATETIME YEAR TO DAY NO DEFAULT NOT NULL

. I40_OCC_CODE_2 CHAR! 2 ) NO DEFAULT NOT NULL

, I40_OCC_DATE_2 DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I40_OCC_CODE_3 CHAR! 2 ) NO DEFAULT NOT NULL

, I40 OCC DATE 3 DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I40_OCC_CODE_4 CHAR! 2 _. NO DEFAULT NOT NULL

, I40_0CC_DATE_4 DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I40_OCC_CODE_5 CHAR! 2 ) NO DEFAULT NOT NULL

, I40_OCC_DATE_5 DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I40_0CC_C0DE_6 CHAR! 2 ) NO DEFAULT NOT NULL

, I40_0CC_DATE_6 DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I40_0CC_C0DE_7 CHAR! 2 ) NO DEFAULT NOT NULL

, I40_0CC_DATE_7 DATETIME YEAR TO DAY NO DEFAULT NOT NULL 0 , I40_0CC_C0DE_8 CHAR! 2 ) NO DEFAULT NOT NULL 3 O , I40_OCC_DATE_8 DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I40_0CC_C0DE_9 CHAR! 2 _. NO DEFAULT NOT NULL

, I40_OCC_DATE_9 DATETIME YEAR TO DAY NO DEFAULT NOT NULL O , I40_OCC_CODE_10 CHAR! 2 ) NO DEFAULT NOT NULL

, I40_OCC_DATE_10 DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I40_OCC_SPAN_CODE_1 CHAR! 2 . NO DEFAULT NOT NULL

, I40_0CC_DATE_FR0M_1 DATETIME YEAR TO DAY NO DEFAULT NOT NULL i , I40_OCC_DATE_THRU_1 DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I40_0CC_SPAN_C0DE_2 CHAR! 2 ) NO DEFAULT NOT NULL

, I40_0CC_DATE_FR0M_2 DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I40_OCC_DATE_THRU_2 DATETIME YEAR TO DAY NO DEFAULT NOT NULL

) > > INVOKE = 141 ;

-- Definition of table \EDI.$DATA1.MMRPRDAT.I41 -- Definition current at 16: 18:02 - 10/19/93

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_N0 DECIMAL! 6, 0 I NO DEFAULT NOT NULL , BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT CNTL NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , I41_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL O , I41_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL 0 0 , I41_C0ND_C0DE_1 CHAR! 2 ) NO DEFAULT NOT NULL , I41_C0ND_C0DE_2 CHAR! 2 ) NO DEFAULT NOT NULL , I41_C0ND_C0DE_3 CHAR! 2 ) NO DEFAULT NOT NULL , I41_C0ND_C0DE_4 CHAR! 2 ) NO DEFAULT NOT NULL , I41_C0ND_C0DE_5 CHAR! 2 ) NO DEFAULT NOT NULL , I41_C0ND_C0DE_6 CHAR! 2 ) NO DEFAULT NOT NULL , I41_C0ND_C0DE_7 CHAR! 2 ) NO DEFAULT NOT NULL , I41_C0ND_C0DE_8 CHAR! 2 ) NO DEFAULT NOT NULL , I41_C0ND_C0DE_9 CHAR! 2 ) NO DEFAULT NOT NULL , I41_C0ND_C0DE_10 CHAR! 2 ) NO DEFAULT NOT NULL , I41_VALUE_C0DE_1 CHAR! 2 ) NO DEFAULT NOT NULL , I41_VALUE_AMT_1 DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL , I41_VALUE_C0DE_2 CHAR! 2 ) NO DEFAULT NOT NULL , I41_VALUE_AMT_2 DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL , I41_VALUE_C0DE_3 CHAR! 2 ) NO DEFAULT NOT NULL , 141 VALUE AMT 3 DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, I41_VALUE_C0DE_4 CHAR! 2 ) NO DEFAULT NOT NULL , I41_VALUE_AMT_4 DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL , I41_VALUE_C0DE_5 CHAR! 2 ) NO DEFAULT NOT NULL , I41_VALUE_AMT_5 DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL , I41_VALUE_C0DE_6 CHAR! 2 ) NO DEFAULT NOT NULL , I41_VALUE_AMT_6 DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL , I41_VALUE_C0DE_7 CHAR! 2 ) NO DEFAULT NOT NULL , I41_VALUE_AMT_7 DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL , I41_VALUE_C0DE_8 CHAR! 2 ) NO DEFAULT NOT NULL 0 O , I41_VALUE_AMT_8 DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL O , I41_VALUE_C0DE_9 CHAR! 2 ) NO DEFAULT NOT NULL , I41_VALUE_AMT_9 DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL o , I41_VALUE_CODE_10 CHAR! 2 ) NO DEFAULT NOT NULL π , I41_VALUE_AMT_10 DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL , I41_VALUE_C0DE_1 1 CHAR! 2 ) NO DEFAULT NOT NULL , I41_VALUE_AMT_1 1 DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL y _¬ , I41_VALUE_C0DE_12 CHAR! 2 ) NO DEFAULT NOT NULL t , I41_VALUE_AMT_12 DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL ) > > INVOKE = 144;

- Definition of table \EDI. $DATA1 .MMRPRDAT.I44

- Definition current at 16: 18:04 - 10/19/93

SUBMITTER CODE CHAR! 3 ) NO DEFAULT NOT NULL

, SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL

, SUBMIS .0 DECIMAL! 6, 0 I NO DEFAULT NOT NULL

, BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

, PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL

, CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

, I44_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL

, I44_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL

, I44_0RIG_ICN_PAYER CHAR! 20 ) NO DEFAULT NOT NULL O , I44_0RIG_REAS0N_C0DE CHAR! 3 ) NO DEFAULT NOT NULL 3 O ) > > INVOKE =150;

-- Definition of table \EDI.$DATA1.MMRPRDAT.I50 . -- Definition current at 16:18:06 - 10/19/93

< π SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL n , SUBMIS_TS DATETIME YEAR TO FRACTION^) NO DEFAULT NOT NULL , SUBMIS JO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , I50_OCCURS_NO DECIMAL! 2, 0 } UNSIGNED NO DEFAULT NOT NULL , I50_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL , I50_ACCOM_REV_CODE CHAR! 4 ) NO DEFAULT NOT NULL , I50 ACCOM RATE DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

. I50_ACC0M_DAYS DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

, I50_ACC0M_T0T_CLM_CHGS DECIMAL! 10, 2 ) NO DEFAULT NOT NULL

, I50_ACC0M_NC0V_CLM_CHGS DECIMAL! 10, 2 ) NO DEFAULT NOT NULL

) > > INVOKE = 160;

-- Definition of table \EDI.$DATA1 .MMRPRDAT.I60 - Definition current at 16:18:07 - 10/19/93

O < = 0 O SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL O , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 > UNSIGNED NO DEFAULT NOT NULL , I60_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , I60_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL , I60_IP_ANCIL_RC0DE CHAR! 4 ) NO DEFAULT NOT NULL , I60_IP_ANCIL_HCPCS CHAR! 5 ) NO DEFAULT NOT NULL , I60_IP_ANCIL_M0D_1 CHAR! 2 ) NO DEFAULT NOT NULL , I60_IP_ANCIL_M0D_2 CHAR! 2 I NO DEFAULT NOT NULL , I60_IP_ANCIL_UNITS DECIMAL! 7, 0 ) UNSIGNED NO DEFAULT NOT NULL , I60_IP_ANCIL_T0T_CHG DECIMAL! 10, 2 ) NO DEFAULT NOT NULL , I60_IP_ANCIL_NCV_CHG DECIMAL! 10, 2 ) NO DEFAULT NOT NULL )

> > INVOKE = 161 ;

- Definition of table \EDI.$DATA1.MMRPRDAT.I61

-- Definition current at 16:18:08 - 10/19/93

< SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL

, SUBMIS_TS DATETIME YEAR TO FRACTION^) NO DEFAULT NOT NULL

, SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL . , BATCHJ.0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL _: 3 0 . PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL

, CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

, I61_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL 0 , I61_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL

, I61_REV_CTR_C0DE CHAR! 3 ) NO DEFAULT NOT NULL 3 , I61_REV_CTR_HCPCS CHAR! 5 ) NO DEFAULT NOT NULL

, I61_REV_CTR_M0D_1 CHAR! 2 ) NO DEFAULT NOT NULL n , I61_REV_CTR_M0D_2 CHAR! 2 ) NO DEFAULT NOT NULL

, I61_REV_CTR_UNITS DECIMAL! 7, 0 ) UNSIGNED NO DEFAULT NOT NULL

, I61_REV_CTR_SER DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I61_REV_CTR_T0T_CHGS DECIMAL! 10, 2 ) NO DEFAULT NOT NULL

, I61_REV_CTR_NCV_CHGS DECIMAL! 10, 2 ) NO DEFAULT NOT NULL

) > > INVOKE =I7A;

-- Definition of table \EDI.$DATA1.MMRPRDAT.I7A -- Definition current at 16:18:10 - 10/19/93

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTION^) NO DEFAULT NOT NULL , SUBMIS_N0 DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , I7A_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL

CO , I7A_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL c=

00 00 , I7A_PRIN_DIAG_C0DE CHAR! 6 ) NO DEFAULT NOT NULL , I7A_0TH_DIAG_C0DE_1 CHAR! 6 ) NO DEFAULT NOT NULL , I7A_0TH_DIAG_C0DE_2 CHAR! 6 ) NO DEFAULT NOT NULL O , I7A_0TH_DIAG_C0DE_3 CHAR! 6 ) NO DEFAULT NOT NULL , I7A_0TH_DIAG_C0DE_4 CHAR! 6 ) NO DEFAULT NOT NULL 3 , I7A_PRIN_PR0C_C0DE CHAR! 7 ) NO DEFAULT NOT NULL , I7A_PRIN_PR0C_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL S. n , I7A_0TH_PR0C_C0DE_1 CHAR! 7 ) NO DEFAULT NOT NULL , I7A_0TH_PR0C_DATE_1 DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I7A_0TH_PR0C_C0DE_2 CHAR! 7 ) NO DEFAULT NOT NULL , I7A_0TH_PR0C_DATE_2 DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I7A_ADMIT_DIAG_C0DE CHAR! 6 ) NO DEFAULT NOT NULL , I7A_EXT_CAUSE_INJ CHAR! 6 ) NO DEFAULT NOT NULL , I7A_PR0C_C0DE_METH CHAR! 1 ) NO DEFAULT NOT NULL ) > > INVOKE = I7B;

-- Definition of table .EDI.ΦDATA1.MMRPRDAT.I7B -- Definition current at 16:18:12 - 10/19/93

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTI0NI6) NO DEFAULT NOT NULL , SUBMIS_N0 DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

CO , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL c=

03 00 , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , I7B_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , I7B_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL O , I7B_0TH _IAG_C0DE_5 CHAR! 6 ) NO DEFAULT NOT NULL , I7B_0TH_DIAG_C0DE_6 CHAR! 6 ) NO DEFAULT NOT NULL 3 , I7B_0TH_DIAG_C0DE_7 CHAR! 6 . NO DEFAULT NOT NULL , I7B_0TH_DIAG_C0DE_8 CHAR! 6 . NO DEFAULT NOT NULL \_ l , I7B_0TH_DIAG_C0DE_9 CHAR! 6 ) NO DEFAULT NOT NULL , I7B_PR0C_C0DE_3 CHAR! 7 ) NO DEFAULT NOT NULL , I7B_PR0C_DATE_3 DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I7B_PR0C_C0DE_4 CHAR! 7 ) NO DEFAULT NOT NULL , I7B_PR0C_DATE_4 DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I7B_PR0C_C0DE_5 CHAR! 7 ) NO DEFAULT NOT NULL , I7B_PR0C_DATE_5 DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I7B_PR0C_C0DE_6 CHAR! 7 ) NO DEFAULT NOT NULL , I7B PROC DATE 6 DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I7B_PR0C_C0DE_7 CHAR! 7 ) NO DEFAULT NOT NULL , I7B_PR0C_DATE_7 DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I7B_PR0C_C0DE_8 CHAR! 7 ) NO DEFAULT NOT NULL , I7B_PR0C_DATE_8 DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I7B_PR0C_C0DE_9 CHAR! 7 ) NO DEFAULT NOT NULL , I7B_PR0C_DATE_9 DATETIME YEAR TO DAY NO DEFAULT NOT NULL )

O O O

> > INVOKE = 171;

-- Definition of table \EDI.$DATA1 .MMRPRDAT.I71 O - Definition current at 16:18:14 - 10/19/93

3 ! _

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL - n , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL . CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , I71_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , I71_DATA_ID CHAR! 1 ) NO DEFAULT NOT NULL , I71_S0C_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL , 171 CERT DATE FROM DATETIME YEAR TO DAY NO DEFAULT NOT NULL

. I71_CERT_DATE_T0 DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I71_PRIN_DIAG_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I71_SURG_PR0C_C0DE CHAR! 7 ) NO DEFAULT NOT NULL , I71_SURG_PERF_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I71_2ND_DIAG_DATE_ DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I71_2ND_DIAG_DATE_2 DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I71_2ND_DIAG_DATE_3 DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I71_2ND_DIAG_DATE_4 DATETIME YEAR TO DAY NO DEFAULT NOT NULL O , I71_FUNC_LIM_C0DE_1 CHAR! 1 ) NO DEFAULT NOT NULL _ 3 0 , I71_FUNC_LIM_C0DE_2 CHAR! 1 ) NO DEFAULT NOT NULL , I71_FUNC_LIM_C0DE_3 CHAR! 1 ) NO DEFAULT NOT NULL , I71_FUNC_UM_C0DE_4 CHAR! 1 ) NO DEFAULT NOT NULL O , I71_FUNC_LIM_C0DE_5 CHAR! 1 ) NO DEFAULT NOT NULL , I71_FUNC_LIM_C0DE_6 CHAR! 1 ) NO DEFAULT NOT NULL , I71_FUNC_LIM_C0DE_7 CHAR! 1 ) NO DEFAULT NOT NULL , I71_FUNC_LIM_C0DE_8 CHAR! 1 ) NO DEFAULT NOT NULL -i , I71_FUNC_LIM_C0DE_9 CHAR! 1 ) NO DEFAULT NOT NULL , I71_FUNC_LIM_CODE_10 CHAR! 1 ) NO DEFAULT NOT NULL , I71_FUNC_LIM_C0DE_11 CHAR! 1 ) NO DEFAULT NOT NULL , I71_FUNC_LIM_C0DE_12 CHAR! 1 ) NO DEFAULT NOT NULL , I71_FUNC_LIM_C0DE_13 CHAR! 1 ) NO DEFAULT NOT NULL , I71_ACT_PERM_C0DE_1 CHAR! 1 ) NO DEFAULT NOT NULL , I71_ACT_PERM_C0DE_2 CHAR! 1 ) NO DEFAULT NOT NULL , I71_ACT_PERM_C0DE_3 CHAR! 1 ) NO DEFAULT NOT NULL , 171 ACT PERM CODE 4 CHAR! 1 ) NO DEFAULT NOT NULL

, I71_ACT_PERM_C0DE_5 CHAR! 1 I NO DEFAULT NOT NULL , I71_ACT_PERM_C0DE_6 CHAR! 1 ) NO DEFAULT NOT NULL , I71_ACT_PERM_C0DE_7 CHAR! 1 ) NO DEFAULT NOT NULL , I71_ACT_PERM_C0DE_8 CHAR! 1 ) NO DEFAULT NOT NULL , I71_ACT_PERM_C0DE_9 CHAR! 1 ) NO DEFAULT NOT NULL . I71_ACT_PERM_CODE_10 CHAR! 1 ) NO DEFAULT NOT NULL , I71_ACT_PERM_C0DE_1 1 CHAR! 1 ) NO DEFAULT NOT NULL , I71_ACT_PERM_C0DE_12 CHAR! 1 ) NO DEFAULT NOT NULL O , I71_ACT_PERM_C0DE_13 CHAR! 1 ) NO DEFAULT NOT NULL _ 0 O , I71_MENTL_ST_C0DE_1 CHAR! 1 ) NO DEFAULT NOT NULL , I71_MENTL_ST_C0DE_2 CHAR! 1 ) NO DEFAULT NOT NULL , I71_MENTL_ST_C0DE_3 CHAR! 1 ) NO DEFAULT NOT NULL O , I71_MENTL_ST_C0DE_4 CHAR! 1 ) NO DEFAULT NOT NULL , I71_MENTL_ST_C0DE_5 CHAR! 1 ) NO DEFAULT NOT NULL , I71_MENTL_ST_C0DE_6 CHAR! 1 ) NO DEFAULT NOT NULL , I71_MENTL_ST_C0DE_7 CHAR! 1 ) NO DEFAULT NOT NULL υ n , I71_MENTL_ST_C0DE_8 CHAR! 1 I NO DEFAULT NOT NULL , I71_PR0GN0SIS_IND CHAR! 1 ) NO DEFAULT NOT NULL , I71_VERBAL_S0C_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I71_PHYS_NAME_LAST CHAR! 15 ) NO DEFAULT NOT NULL , I71_PHYS_NAME_FIRST CHAR! 10 ) NO DEFAULT NOT NULL , I71_PHYS_NAME_MI CHAR! 1 ) NO DEFAULT NOT NULL , I71_PHYS_ZIP_C0DE CHAR! 9 ) NO DEFAULT NOT NULL , I71_MEDICARE_C0VD CHAR! 1 ) NO DEFAULT NOT NULL , 171 PAT LAST DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I71_LAST_C0NT_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I71_PAT_1861J_FACIL CHAR! 1 ) NO DEFAULT NOT NULL

, I71_CERT_RECERT_M0D CHAR! 1 ) NO DEFAULT NOT NULL

, I71_ADMIT_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I71_DISCHARGE_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, I71_FACILITY_TYPE CHAR! 1 ) NO DEFAULT NOT NULL

)

__ 3 o > > INVOKE =172;

-- Definition of table \EDI.$DATA1.MMRPRDAT.I72

-- Definition current at 16:18:17 - 10/19/93 O n

3 SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL ^* _ - , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL n . SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , I72_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , I72_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL . I72_DISCIPLINE CHAR! 2 ) NO DEFAULT NOT NULL , I72_VISITS_PR_CERT DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , 112 FREQ NUMBER 1 DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL

I72_FREQ PERIODJ CHAR! 2 ) NO DEFAULT NOT NULL

I72_FREQ DURATIONJ CHAR! 3 ) NO DEFAULT NOT NULL

I72_FREQ NUMBER_2 DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL

I72_FREQ _PERI0D_2 CHAR! 2 ) NO DEFAULT NOT NULL

I72_FREQ _DURATI0N_2 CHAR! 3 ) NO DEFAULT NOT NULL

I72_FREQ NUMBER 3 DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL

I72_FREQ. _PERI0D_3 CHAR! 2 ) NO DEFAULT NOT NULL

I72_FREQ_ DURATIONJ. CHAR! 3 ) NO DEFAULT NOT NULL 0 I72_FREQ NUMBER_4 DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL O 0 I72_FREQ PERI0D_4 CHAR! 2 ) NO DEFAULT NOT NULL

I72_FREQ. DURATIONJ. CHAR! 3 ) NO DEFAULT NOT NULL

I72_FREQ NUMBER_5 DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL o I72_FREQ_ _PERI0D_5 CHAR! 2 ) NO DEFAULT NOT NULL

I72_FREQ. DURATI0N_5 CHAR! 3 ) NO DEFAULT NOT NULL

I72_FREQ NUMBER_6 DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL π I72_FREQ. PERI0D_6 CHAR! 2 ) NO DEFAULT NOT NULL M I72_FREQ_ DURATI0N_6 CHAR! 3 ) NO DEFAULT NOT NULL

I72_FREQ. NUMBER_7 DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL

I72_FREQ_ PERI0D_7 CHAR! 2 ) NO DEFAULT NOT NULL

I72_FREQ. DURATI0N_7 CHAR! 3 ) NO DEFAULT NOT NULL

I72_FREQ. NUMBER_8 DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL

I72_FREQ_ PERI0D_8 CHAR! 2 ) NO DEFAULT NOT NULL

I72_FREQ. DURATI0N_8 CHAR! 3 ) NO DEFAULT NOT NULL

I72_FREQ NUMBER_9 DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL

172 FREQ PERIOD 9 CHAR! 2 ) NO DEFAULT NOT NULL

, I72_FREQ_DURATI0N_9 CHAR! 3 ) NO DEFAULT NOT NULL , I72_FREQ_NUMBER_10 DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL , I72_FREQ_PERIOD_10 CHAR! 2 ) NO DEFAULT NOT NULL , I72_FREQ_DURATI0N_10 CHAR! 3 > NO DEFAULT NOT NULL , I72_FREQ_NUMBER_1 1 DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL , I72_FREQ_PERI0D_1 1 CHAR! 2 ) NO DEFAULT NOT NULL , I72_FREQ_DURATI0N_1 1 CHAR! 3 ) NO DEFAULT NOT NULL , I72_FREQ_NUMBER_12 DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL , I72_FREQ_PERI0D_12 CHAR! 2 ) NO DEFAULT NOT NULL O = 0 , I72_FREQ_DURATI0N_12 CHAR! 3 ) NO DEFAULT NOT NULL 0 , I72_TREAT_C0DE_1 CHAR! 3 ) NO DEFAULT NOT NULL , I72_TREAT_C0DE_2 CHAR! 3 ) NO DEFAULT NOT NULL 0 , I72_TREAT_C0DE_3 CHAR! 3 ) NO DEFAULT NOT NULL π , I72_TREAT_C0DE_4 CHAR! 3 ) NO DEFAULT NOT NULL , I72_TREAT_C0DE_5 CHAR! 3 ) NO DEFAULT NOT NULL 3 _ — , I72_TREAT_C0DE_6 CHAR! 3 ) NO DEFAULT NOT NULL -υ , I72_TREAT_C0DE_7 CHAR! 3 ) NO DEFAULT NOT NULL , I72_TREAT_C0DE_8 CHAR! 3 ) NO DEFAULT NOT NULL . I72_TREAT_C0DE_9 CHAR! 3 ) NO DEFAULT NOT NULL , I72_TREAT_CODE_10 CHAR! 3 ) NO DEFAULT NOT NULL , I72_TREAT_C0DE_1 1 CHAR! 3 ) NO DEFAULT NOT NULL , I72_TREAT_C0DE_12 CHAR! 3 ) NO DEFAULT NOT NULL , I72_TREAT_C0DE_13 CHAR! 3 ) NO DEFAULT NOT NULL , I72_TREAT_C0DE_14 CHAR! 3 ) NO DEFAULT NOT NULL , 172 TREAT CODE 15 CHAR! 3 ) NO DEFAULT NOT NULL

, I72_TREAT_C0DE_16 CHAR! 3 ) NO DEFAULT NOT NULL

, I72_TREAT_C0DE_17 CHAR! 3 ) NO DEFAULT NOT NULL

, I72_TREAT_C0DE_18 CHAR! 3 ) NO DEFAULT NOT NULL

, I72_TREAT_C0DE_19 CHAR! 3 ) NO DEFAULT NOT NULL

. I72_TREAT_CODE_20 CHAR! 3 > NO DEFAULT NOT NULL

, I72_TREAT_C0DE_21 CHAR! 3 ) NO DEFAULT NOT NULL

, I72_TREAT_C0DE_22 CHAR! 3 ) NO DEFAULT NOT NULL

, I72_TREAT_C0DE_23 CHAR! 3 ) NO DEFAULT NOT NULL O , I72_TREAT_C0DE_24 CHAR! 3 ) NO DEFAULT NOT NULL = 3 0 , I72_TREAT_C0DE_25 CHAR! 3 ) NO DEFAULT NOT NULL

, I72_T0T_PR0J_VISITS DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL

) 0 > > INVOKE = 173; π n -- Definition of table \EDI.$DATA1 .MMRPRDAT.I73 -- Definition current at 16: 18:20 - 10/19/93

SUBMITTER CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , I73_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , I73 SEQ NO CHAR! 3 ) NO DEFAULT NOT NULL

, I73_DATA_ID_NUM CHAR! 5 ) NO DEFAULT NOT NULL

, I73_C0RRESP_DATA CHAR! 164 ) NO DEFAULT NOT NULL

) > > INVOKE =174;

-- Definition of table \EDI.$DATA1.MMRPRDAT.I74 - Definition current at 16:18:21 - 10/19/93

O SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL = 0 O , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL 0 , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL . CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , I74_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , I74_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL . , I74_HICN CHAR! 19 ) NO DEFAULT NOT NULL , I74_MED_REC_NUM CHAR! 18 ) NO DEFAULT NOT NULL , I74_PAT_NAME_LAST CHAR! 20 ) NO DEFAULT NOT NULL , I74_PAT_NAME_FIRST CHAR! 10 ) NO DEFAULT NOT NULL , I74_PAT_NAME_MI CHAR! 1 ) NO DEFAULT NOT NULL , I74_PAT_D0B DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I74_PAT_SEX CHAR! 1 ) NO DEFAULT NOT NULL , I74_PRIN_DIAG_C0DE CHAR! 6 ) NO DEFAULT NOT NULL , I74 2ND DIAG CODE 1 CHAR! 6 ) NO DEFAULT NOT NULL

, I74_2ND_DIAG_C0DE_2 CHAR! 6 ) NO DEFAULT NOT NULL

, I74_2ND_DIAG_C0DE_3 CHAR! 6 ) NO DEFAULT NOT NULL

, I74_2ND_DIAG_C0DE_4 CHAR! 6 ) NO DEFAULT NOT NULL

) > > INVOKE = 180;

-- Definition of table \EDI.$DATA1.MMRPRDAT.I80 - Definition current at 16:18:23 - 10/19/93

O ! _ 3 0 SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL o , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , I80_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL υ ^* , I80_ATTEND_PHYS_NUM CHAR! 16 ) NO DEFAULT NOT NULL , I80_0PER_PHYS_NUM CHAR! 16 ) NO DEFAULT NOT NULL , I80_OTH_PHYS_NUM_1 CHAR! 16 ) NO DEFAULT NOT NULL , I80_0TH_PHYS_NUM_2 CHAR! 16 ) NO DEFAULT NOT NULL , I80_ATND_PHYS_NAME_L CHAR! 20 ) NO DEFAULT NOT NULL , I80_ATND_PHYS_NAME_F CHAR! 10 ) NO DEFAULT NOT NULL , I80_ATND_PHYS_NAME_M CHAR! 1 ) NO DEFAULT NOT NULL , I80_OPER_PHYS_NAME_L CHAR! 20 ) NO DEFAULT NOT NULL , I80 OPER PHYS NAME F CHAR! 10 ) NO DEFAULT NOT NULL

, I80_0PER_PHYS_NAME_M CHAR! 1 ) NO DEFAULT NOT NULL

, I80_OTH_PHYS1_NAME_L CHAR! 20 ) NO DEFAULT NOT NULL

, I80_0TH_PHYS1_NAME_F CHAR! 10 ) NO DEFAULT NOT NULL

, I80_0TH_PHYS1_NAME_M CHAR! 1 ) NO DEFAULT NOT NULL

, I80_0TH_PHYS2_NAME_L CHAR! 20 ) NO DEFAULT NOT NULL

, I80_0TH_PHYS2_NAME_F CHAR! 10 ) NO DEFAULT NOT NULL

, I80_OTH_PHYS2_NAME_M CHAR! 1 ) NO DEFAULT NOT NULL

) 0 > > INV0KE =181 ; 0 0 -- Definition of table \EDI.$DATA1 .MMRPRDAT.I81 -- Definition current at 16:18:26 - 10/19/93

o <

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL n , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , I81_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , I81_0RD_PHYS_NUM CHAR! 16 ) NO DEFAULT NOT NULL , I81_0RD_PHYS_NAME_L CHAR! 20 ) NO DEFAULT NOT NULL , I81 _0RD_PHYS_NAME_F CHAR! 10 ) NO DEFAULT NOT NULL , I81_0RD_PHYS_NAME_M CHAR! 1 ) NO DEFAULT NOT NULL , I81_0PER_PHYS_NUM CHAR! 16 ) NO DEFAULT NOT NULL

, I81_0PER_PHYS_NAME_L CHAR! 20 ) NO DEFAULT NOT NULL , I81_0PER_PHYS_NAME_F CHAR! 10 ) NO DEFAULT NOT NULL , I81_0PER_PHYS_NAME_M CHAR! 1 ) NO DEFAULT NOT NULL , I81_REC0RD_ID_C0DE CHAR! 1 ) NO DEFAULT NOT NULL , I81_MANUF_ID CHAR! 3 ) NO DEFAULT NOT NULL , I81_M0DEL_NUM CHAR! 15 ) NO DEFAULT NOT NULL , I81_SERIAL_NUM CHAR! 20 ) NO DEFAULT NOT NULL , I81_WARNTY_EXP_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL , I81_IMPLANT_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL O

__ 3 , I81_LEADS_IN_PATIENT CHAR! 1 ) NO DEFAULT NOT NULL o , I81_RETURN_T0_MANUF CHAR! 1 ) NO DEFAULT NOT NULL ) o > > INVOKE =FAO;

- Definition of table \EDI.$DATA1 .MMRPRDAT.FA0

- Definition current at 16:18:27 - 10/19/93

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , FA0_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , FAO SEQ NO CHAR! 2 ) NO DEFAULT NOT NULL

■ FA0_L_ITEM_CNTL_NO CHAR! 17 ) NO DEFAULT NOT NULL , FA0_SVC_FROM_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL , FA0_SVC_TO_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL , FA0_PLACE_SVC_CODE CHAR! 2 ) NO DEFAULT NOT NULL . FA0_TYPE_SVC_CODE CHAR! 2 ) NO DEFAULT NOT NULL , FAO_HCPCS_PROC_CODE CHAR! 5 > NO DEFAULT NOT NULL , FA0_HCPCS_M0DIFIER_1 CHAR! 2 ) NO DEFAULT NOT NULL , FA0_HCPCS_M0DIFIER_2 CHAR! 2 ) NO DEFAULT NOT NULL O , FA0_HCPCS_M0DIFIER_3 CHAR! 2 ) NO DEFAULT NOT NULL _ 3 O , FAO_LINE_CHARGES DECIMAL! 5, 2 ) UNSIGNED NO DEFAULT NOT NULL , FA0_DIAG_CODE_PTR1 CHAR! 1 ) NO DEFAULT NOT NULL , FA0_DIAG_C0DE_PTR2 CHAR! 1 ) NO DEFAULT NOT NULL o , FA0_DIAG_CODE_PTR3 CHAR! 1 ) NO DEFAULT NOT NULL , FA0_DIAG_CODE_PTR4 CHAR! 1 ) NO DEFAULT NOT NULL , FAO_UNIT_OF_SVC DECIMAL! 3, 1 ) UNSIGNED NO DEFAULT NOT NULL , FA0_ANEST_OXY_MIN DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL 0 , FAO_EMERGENCY_IN CHAR! 1 ) NO DEFAULT NOT NULL , FA0_COB_IN CHAR! 1 ) NO DEFAULT NOT NULL , FAO_HMSA_IN CHAR! 1 ) NO DEFAULT NOT NULL , FA0_REND_PROV_ID CHAR! 15 ) NO DEFAULT NOT NULL , FA0_REFER_PROV_ID CHAR! 15 ) NO DEFAULT NOT NULL , FA0_REFER_PROV_ST CHAR! 2 ) NO DEFAULT NOT NULL , FAO_PUR_SVC_IN CHAR! 1 ) NO DEFAULT NOT NULL , FA0_DIS_COST_CANTAIN DECIMAL! 5, 2 ) UNSIGNED NO DEFAULT NOT NULL , FAO DIS OTHER DECIMAL! 5, 2 ) UNSIGNED NO DEFAULT NOT NULL

, FA0_REV_CODE_IN CHAR! 1 ) NO DEFAULT NOT NULL

, FA0_MULTI_PROC_IN CHAR! 1 ) NO DEFAULT NOT NULL

, FA0_MAMM_CERT_NO CHAR! 10 ) NO DEFAULT NOT NULL

, FAO_CLASS_FINDINGS CHAR! 9 ) NO DEFAULT NOT NULL

, FA0_SYSTEMIC_COND CHAR! 3 ) NO DEFAULT NOT NULL

, FA0_CLIA_ID_NO CHAR! 15 ) NO DEFAULT NOT NULL

) > > INVOKE = FB0; O -- Definition of table \EDI.$DATA1.MMRPRDAT.FB0 0 O - Definition current at 16:18:29 - 10/19/93

_ I < o SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL i , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , FB0_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , FB0_L_ITEM_CNTL_NO CHAR! 17 ) NO DEFAULT NOT NULL , FBO_PUR_SVR_CHARGE DECIMAL! 5, 2 ) UNSIGNED NO DEFAULT NOT NULL , FBO_ALLOWED_AMT DECIMAL! 5, 2 ) UNSIGNED NO DEFAULT NOT NULL , FBO_DEDUCTIBLE_AMT DECIMAL! 5, 2 ) UNSIGNED NO DEFAULT NOT NULL , FB0_COINSURE_AMT DECIMAL! 5, 2 ) UNSIGNED NO DEFAULT NOT NULL , FBO ORDER PROV ID CHAR! 15 ) NO DEFAULT NOT NULL

CHAR! 2 ) NO DEFAULT NOT NULL

CHAR! 15 ) NO DEFAULT NOT NULL

CHAR! 2 ) NO DEFAULT NOT NULL

DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

CHAR! 1 1 ) NO DEFAULT NOT NULL

DECIMAL! 7, 0 ) UNSIGNED NO DEFAULT NOT NULL

CHAR! 15 ) NO DEFAULT NOT NULL

DATETIME YEAR TO DAY NO DEFAULT NOT NULL O 3 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL O

CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL O CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 15 ) NO DEFAULT NOT NULL _ CHAR! 9 ) NO DEFAULT NOT NULL

CHAR! 33 ) NO DEFAULT NOT NULL

CHAR! 30 ) NO DEFAULT NOT NULL

CHAR! 30 ) NO DEFAULT NOT NULL

CHAR! 20 ) NO DEFAULT NOT NULL

CHAR! 9 ) NO DEFAULT NOT NULL CHAR! 10 ) NO DEFAULT NOT NULL

> > INVOKE = FB1 ;

-- Definition of table \EDI.$DATA1 .MMRPRDAT.FB1 - Definition current at 16:18:31 - 10/19/93

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_N0 DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL O , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL _ 0 o , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , FB1_0CCURS_N0 DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , FB1_SEQ_N0 CHAR! 2 ) NO DEFAULT NOT NULL > , FB1_L_ITEM_CNTL_N0 CHAR! 17 ) NO DEFAULT NOT NULL , FB1_PLACE_SVC_NAME CHAR! 33 ) NO DEFAULT NOT NULL , FB1_0RDER_PR0V_LAST CHAR! 20 ) NO DEFAULT NOT NULL , FB1_0RDER_PR0V_FIRST CHAR! 12 ) NO DEFAULT NOT NULL , FB1_0RDER_PR0V_MI CHAR! 1 ) NO DEFAULT NOT NULL , FB1_0RDER_PR0V_UPIN CHAR! 15 ) NO DEFAULT NOT NULL , FB1_REFER_PR0V_LAST CHAR! 20 ) NO DEFAULT NOT NULL , FB1_REFER_PR0V_FIRST CHAR! 12 ) NO DEFAULT NOT NULL , FB1_REFER_PR0V_MI CHAR! 1 ) NO DEFAULT NOT NULL , FB1_REFER_PR0V_UPIN CHAR! 15 ) NO DEFAULT NOT NULL , FB1_REND_PR0V_LAST CHAR! 20 ) NO DEFAULT NOT NULL , FB1_REND_PR0V_FIRST CHAR! 12 ) NO DEFAULT NOT NULL , FB1 REND PROV Ml CHAR! 1 ) NO DEFAULT NOT NULL

. FB1_REND_PR0V_UPIN CHAR! 15 ) NO DEFAULT NOT NULL , FB1_SUPER_PR0V_LAST CHAR! 20 ) NO DEFAULT NOT NULL , FB1_SUPER_PR0V_FIRST CHAR! 12 ) NO DEFAULT NOT NULL , FB1_SUPER_PR0V_MI CHAR! 1 ) NO DEFAULT NOT NULL , FB1_SUPER_PR0V_UPIN CHAR! 15 ) NO DEFAULT NOT NULL ) > > INVOKE = GAO;

- Definition of table \EDI.$DATA1 .MMRPRDAT.GA0 O - Definition current at 16: 18:33 - 10/19/93 : 0 O

<

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL o . SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL π , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL . , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , GA0_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , GA0_SEQ_NO CHAR! 2 > NO DEFAULT NOT NULL , GAO_PAT_WEIGHT CHAR! 3 ) NO DEFAULT NOT NULL , GA0_HOSP_ADM CHAR! 1 ) NO DEFAULT NOT NULL , GA0_TRANSPORT_TYPE CHAR! 1 ) NO DEFAULT NOT NULL , GAO_BEDCONF_BEFORE CHAR! 1 ) NO DEFAULT NOT NULL , GA0_BEDCONF_AFTER CHAR! 1 ) NO DEFAULT NOT NULL , GAO MOVE BY STRETCH CHAR! 1 ) NO DEFAULT NOT NULL

, GA0_UNCONS_SHOCK CHAR! 1 ) NO DEFAULT NOT NULL

, GA0_EMERG_SITUATION CHAR! 1 ) NO DEFAULT NOT NULL

. GAO_PHY_RESTRAINTS CHAR! 1 ) NO DEFAULT NOT NULL

, GA0_VIS_HEMORRHAGE CHAR! 1 I NO DEFAULT NOT NULL

, GA0_TRANSPORT_TO_FOR CHAR! 1 ) NO DEFAULT NOT NULL

, GAO_MED_NECESSARY CHAR! 1 ) NO DEFAULT NOT NULL

, GAO_MILES CHAR! 4 ) NO DEFAULT NOT NULL

, GA0_ORIGIN_INFO CHAR! 40 ) NO DEFAULT NOT NULL Λ , GA0_DEST_INFO CHAR! 40 ) NO DEFAULT NOT NULL = 3 O , GAO_PURPOSE_RND_TRIP CHAR! 80 ) NO DEFAULT NOT NULL

, GA0_PURPOSE_STRETCH CHAR! 80 ) NO DEFAULT NOT NULL

) O > > INVOKE =GCO;

-- Definition of table \EDI.$DATA1 .MMRPRDAT.GC0 -- Definition current at 16:1 8:35 - 10/19/93

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , GCO_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , GCO INIT TREAT DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, GCO_LAST_XRAY_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL , GC0_NO_IN_SERIES CHAR! 7 ) NO DEFAULT NOT NULL , GCO_LEV_SUBLUX CHAR! 7 ) NO DEFAULT NOT NULL , GC0_TREAT_MON_YRS CHAR! 3 ) NO DEFAULT NOT NULL . GC0_NO_TREAT_MON CHAR! 2 ) NO DEFAULT NOT NULL , GC0_NATURE_CONDITION CHAR! 1 ) NO DEFAULT NOT NULL , GCO_MANIFEST_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL , GC0_COMPLICATE_IN CHAR! 1 ) NO DEFAULT NOT NULL O , GCO SYMP DESCRIP CHAR! 160 ) NO DEFAULT NOT NULL ) > > INVOKE =GDO; π - Definition of table \EDI.$DATA1.MMRPRDAT.GDO -- Definition current at 16: 18:37 - 10/19/93

3 ! _ SUBMITTER CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL "' , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL

, BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

, PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL

, CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

, GD0_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL

, GD0_SEQ_NO CHAR! 2 ) NO DEFAULT NOT NULL

, GDO — CERT — TYPE CHAR! 1 ) NO DEFAULT NOT NULL

, GDO MED_NECESSITY CHAR! 2 ) NO DEFAULT NOT NULL

3 I I 1 1 I I I I I I I I I I 1 I I I I I ■ I I I

Z 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 -. Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z

Oz - l- H I- H- l- l- l- l- l- l- l- l- H h- ol- o f z o- l- l- - H H I- ^ oz oz oz oz oz oz oz oz oz oz oz oz oz oz oz z z oz oz oz oz oz oz

____J» Hi HI HI I-I (-I l-f HI I-I HI HI HI HI Hi I-I l-I l-I f-I l-I l-I l-I l-I l-I HI I-I

< 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

LU LL LL LL Ii- LL LL LL U- LL LL LL LL LL LL LL LL LL LL LL LL LL LL LL LL .— i ill in in in |ι| HI -j) in in in i nl nl HI in nl III '" I III 'I ¹ '" III "'

- Q O Q Q O Q Q O O Q Q Q Q Q Q Q Q Q O Q Q O Q O z o o o o o o o o o o o o o o o o o o o o o o o o

_^ Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z Z

_{0 ^} __-. _« ____ ___ __-_ ___ ____ _« ____ __. __. __. __. _-- -_ ___ ___ ___ ___ _-_ _-_ -__ --

N lfi - t- - ι- t- -- *- - -- ι- -- *- - r r ι- - *- ι- *- . . ι-

-C -π -π -E _c _c D_ _π _π c c cc c c c c c κ c c c c c __: -_: <x x< <x <x x< <x <x x< x< <x <x x< <x x< x< <x x< < CJ O U CJ U O CJ CJ O U U O CJ U O xU x< U x< < x< x< <

O O O xO x< U O U xU

C ^■■ - ^* >

i

§ 0 S cc Q. o I

O _i (_) _

DATETIME YEAR TO DAY NO DEFAULT NOT NULL

DATETIME YEAR TO DAY NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 20 ) NO DEFAULT NOT NULL

CHAR! 12 ) NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 15 ) NO DEFAULT NOT NULL

CHAR! 10 ) NO DEFAULT NOT NULL

CO DATETIME YEAR TO DAY NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 5 ) NO DEFAULT NOT NULL

CHAR! 5 ) NO DEFAULT NOT NULL o CHAR! 5 ) NO DEFAULT NOT NULL

CHAR! 5 ) NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL

DATETIME YEAR TO DAY NO DEFAULT NOT NULL

DATETIME YEAR TO DAY NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 1 ) NO DEFAULT NOT NULL CHAR! 1 ) NO DEFAULT NOT NULL

)

> > INVOKE =GD1 ;

-- Definition of table \EDI.$DATA1.MMRPRDAT.GD1

Definition current at 16:18:39 - 10/19/93

!

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL O , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL 3 o , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL _ I , CLAIM SEQ NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , GD1_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , GD1 SEQ NO CHAR! 2 ) NO DEFAULT NOT NULL 3 , GD1_DME_NARRATIVE CHAR! 250 ) NO DEFAULT NOT NULL

) . > > INVOKE =GE0;

- Definition of table \EDI. $DATA1 .MMRPRDAT.GE0

- Definition current at 16: 18:41 - 10/19/93

< SUBMITTER CODE CHAR! 3 ) NO DEFAULT NOT NULL

, SUBMISJTS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL

, SUBMIS NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL

, BATCH NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

, PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , GE0_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , GEO_CERT_TYPE CHAR! 1 ) NO DEFAULT NOT NULL , GE0_ONSET_DT_THERAPY DATETIME YEAR TO DAY NO DEFAULT NOT NULL , GEOJΗERAPY_DURATION CHAR! 2 ) NO DEFAULT NOT NULL , GEO_LAST_CERT_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL , GE0_NO_MNTHS_CERT CHAR! 2 ) NO DEFAULT NOT NULL O , GEO_DT_LAST_SEEN_PHY DATETIME YEAR TO DAY NO DEFAULT NOT NULL Λ , GE0_NON_VISIT_IN CHAR! 1 ) NO DEFAULT NOT NULL , GEO_PAT_AGE CHAR! 3 ) NO DEFAULT NOT NULL , GEO_PAT_HEIGHT CHAR! 3 ) NO DEFAULT NOT NULL . E , GEO_PAT_WEIGHT CHAR! 3 ) NO DEFAULT NOT NULL π , GE0_LEV_CONS_IND CHAR! 1 ) NO DEFAULT NOT NULL , GE0_AMBULATORY_IN CHAR! 1 ) NO DEFAULT NOT NULL , GEO_OTHR_NUTR_IN CHAR! 1 J NO DEFAULT NOT NULL 3 n , GEO_METH_ADMIN_IN CHAR! 1 ) NO DEFAULT NOT NULL , GEO_ADMIN_TECH_IN CHAR! 1 ) NO DEFAULT NOT NULL , GE0_TOT_CALL_PER_DAY DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , GE0_PRODUCT_NAME_1 CHAR! 15 ) NO DEFAULT NOT NULL , GEO_CAL_PER_PRODJ CHAR! 4 ) NO DEFAULT NOT NULL , GE0_HCPCS_PRO_CODE CHAR! 5 ) NO DEFAULT NOT NULL , GE0_HCPCS_M0D_1 CHAR! 2 ) NO DEFAULT NOT NULL , GE0JHCPCS_MOD_2 CHAR! 2 ) NO DEFAULT NOT NULL , GEO ENT FREQ FED 1 CHAR! 3 ) NO DEFAULT NOT NULL

, GEO_ENT_NARRATIVE CHAR! 100 ) NO DEFAULT NOT NULL

, GE0_PRODUCT_NAME_2 CHAR! 15 ) NO DEFAULT NOT NULL

, GE0_CAL_PER_PROD_2 CHAR! 4 ) NO DEFAULT NOT NULL

, GE0_ENT_FREQ_FED_2 CHAR! 3 ) NO DEFAULT NOT NULL

) > > INVOKE =GPO;

-- Definition of table \EDI. $DATA1 .MMRPRDAT.GP0 - Definition current at 16: 18:42 - 10/19/93 O σ o !

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL o E , SUBMIS_N0 DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL π , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL 3 n , GP0_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , GPO_CERT_TYPE CHAR! 1 ) NO DEFAULT NOT NULL , GP0_ONSET_DT_THERAPY DATETIME YEAR TO DAY NO DEFAULT NOT NULL , GP0_THERAPY_DURATION CHAR! 2 ) NO DEFAULT NOT NULL , GPO_LAST_CERT_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL , GP0_NO_MNTHS_CERT CHAR! 2 ) NO DEFAULT NOT NULL , GPO_DT_LAST_SEEN_PHY DATETIME YEAR TO DAY NO DEFAULT NOT NULL , GP0_NON_VISIT_IN CHAR! 1 ) NO DEFAULT NOT NULL , GPO PAT AGE CHAR! 3 ) NO DEFAULT NOT NULL

, GPO_PAT_H EIGHT CHAR! 3 ) NO DEFAULT NOT NULL

, GPO_PAT_WEIGHT CHAR! 3 ) NO DEFAULT NOT NULL

. GP0_LEV_CONS_IND CHAR! 1 ) NO DEFAULT NOT NULL

, GP0_AMBULATORY_IN CHAR! 1 ) NO DEFAULT NOT NULL

, GP0_OTHR_NUTR_IN CHAR! 1 ) NO DEFAULT NOT NULL

, GP0_TYPE_OF_MIX_IN CHAR! 1 ) NO DEFAULT NOT NULL

, GPO_PARENT_FREQ_FED CHAR! 3 ) NO DEFAULT NOT NULL

, GP0JHCPCS_PRO_CODE CHAR! 5 ) NO DEFAULT NOT NULL O , GP0_HCPCS_MOD_1 CHAR! 2 ) NO DEFAULT NOT NULL 3 O , GP0_HCPCS_MOD_2 CHAR! 2 ) NO DEFAULT NOT NULL

, GPO_AMINO_ACID_NAME CHAR! 15 ) NO DEFAULT NOT NULL _

, GP0_AMINO_ACID_VOL DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL o c , GP0_AMINO_ACID_CONC CHAR! 5 ) NO DEFAULT NOT NULL

, GP0_AMINO_ACID_WGHT DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

, GP0_DEXTROSE_VOL DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

, GP0_DEXTR0SE_CONC CHAR! 5 ) NO DEFAULT NOT NULL

, GP0JJPIDS_VOLUME DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL

, GP0_LIPIDS_CONC CHAR! 5 ) NO DEFAULT NOT NULL

, GPO_LIPIDS_FREQ DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, GPO_PNT_NARRATIVE CHAR! 100 ) NO DEFAULT NOT NULL

, GPO_ADMIN_TECH_IN CHAR! 1 ) NO DEFAULT NOT NULL

) > > INVOKE = GXO;

- Definition of table \EDI.$DATA1 .MMRPRDAT.GXO -- Definition current at 16: 18:44 - 10/19/93

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTION(δ) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , GX0_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL O , GXO_CERT_TYPE CHAR! 1 ) NO DEFAULT NOT NULL D O , GXO_OXYGEN_SYS CHAR! 1 ) NO DEFAULT NOT NULL , GX0_LENGTH_OF_NEED CHAR! 2 ) NO DEFAULT NOT NULL . GX0_EQUIP_TYPE_1 CHAR! 1 ) NO DEFAULT NOT NULL o , GX0_EQUIP_TYPE_2 CHAR! 1 ) NO DEFAULT NOT NULL π , GX0_EQUIP_REASON CHAR! 64 ) NO DEFAULT NOT NULL , GX0_PRES_FROM_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL , GXO_PRES_TO_DT DATETIME YEAR TO DAY NO DEFAULT NOT NULL » , GXO_DT_PRESCRIBED DATETIME YEAR TO DAY NO DEFAULT NOT NULL , GXO_DT_EVALUATED DATETIME YEAR TO DAY NO DEFAULT NOT NULL , GX0_OXY_FLO_RATE CHAR! 3 ) NO DEFAULT NOT NULL , GX0_FREQ_OF_USE CHAR! 2 ) NO DEFAULT NOT NULL , GX0_DURATION CHAR! 2 ) NO DEFAULT NOT NULL , GX0_OTHER CHAR! 80 ) NO DEFAULT NOT NULL , GX0_ART_BLOOD_GAS CHAR! 3 ) NO DEFAULT NOT NULL , GX0_OXIMETRY CHAR! 3 ) NO DEFAULT NOT NULL , GXO DATE_TESTED DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, GXO_TEST_FAC_NAME CHAR! 33 ) NO DEFAULT NOT NULL

, GX0_TEST_CONDITIONS CHAR! 1 ) NO DEFAULT NOT NULL

, GXO_CLINIC_FINDINGS CHAR! 3 ) NO DEFAULT NOT NULL

, GX0_PORT_OXYFLO_RATE CHAR! 3 ) NO DEFAULT NOT NULL

, GX0_ORD_PROV_ID CHAR! 15 ) NO DEFAULT NOT NULL

, GX0_ORD_PROV_PHONE CHAR! 10 ) NO DEFAULT NOT NULL

, GX0_DIAG_CODE1 CHAR! 5 ) NO DEFAULT NOT NULL

, GX0_DIAG_CODE2 CHAR! 5 ) NO DEFAULT NOT NULL O , GX0_DIAG_CODE3 CHAR! 5 ) NO DEFAULT NOT NULL 3 O , GX0_DIAG_CODE4 CHAR! 5 ) NO DEFAULT NOT NULL

. GX0_CERT_0N_FILE CHAR! 1 ) NO DEFAULT NOT NULL

, GXO_DELIVER_SYS_TAPE CHAR! 1 ) NO DEFAULT NOT NULL

) > > INVOKE =GX1 ;

-- Definition of table \EDI.$DATA1 .MMRPRDAT.GX1 -- Definition current at 16:18:46 - 10/19/93

(

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_N0 DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , GX1 OCCURS NO DECIMAL! 2, 0 > UNSIGNED NO DEFAULT NOT NULL

, GX1_TEST_RESULTS CHAR! 90 ) NO DEFAULT NOT NULL

, GX1_MEDICAL_FINDINGS CHAR! 90 ) NO DEFAULT NOT NULL

, GX1_EXERCISE_R0UTINE CHAR! 90 ) NO DEFAULT NOT NULL

) > > INVOKE =GX2;

-- Definition of table \EDI.$DATA1.MMRPRDAT.GX2 - Definition current at 16:18:48 - 10/19/93

co <

03 CO SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL o , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL E , PAT_CNTL_NO CHAR! 20 > NO DEFAULT NOT NULL 3 , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , GX2_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL n , GX2_TEST_FAC_ADDR1 CHAR! 30 ) NO DEFAULT NOT NULL , GX2_TEST_FAC_ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL , GX2_TEST_FAC_CITY CHAR! 20 ) NO DEFAULT NOT NULL , GX2_TEST_FAC_ST CHAR! 2 ) NO DEFAULT NOT NULL , GX2_TEST_FAC_ZIP CHAR! 9 ) NO DEFAULT NOT NULL , GX2_PAT_FAC_NAME CHAR! 33 ) NO DEFAULT NOT NULL , GX2_PAT_FAC_ADDR1 CHAR! 30 ) NO DEFAULT NOT NULL , GX2_PAT_FAC_ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL . GX2 PAT FAC CITY CHAR! 20 ) NO DEFAULT NOT NULL

, GX2_PAT_FAC_ST CHAR! 2 ) NO DEFAULT NOT NULL

, GX2_PAT_FAC_ZIP CHAR! 9 ) NO DEFAULT NOT NULL

) > > INVOKE =HAO;

- Definition of table .EDI.tDATAI . MMRPRDAT.HAO -- Definition current at 16:18:49 - 10/19/93

< O SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL _ _ O , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL O C , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL π , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , HA0_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , HA0_L_ITEM_CNTL_NO CHAR! 17 ) NO DEFAULT NOT NULL , HAO_EXTRA_NARRATIVE CHAR! 160 ) NO DEFAULT NOT NULL )

> > INVOKE =AAORESP;

- Definition of table \EDI.$DATA1 .MMRPRDAT.AAORESP

- Definition current at 16:18:51 - 10/19/93

«

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL

, SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL

, RECEIVER_CODE CHAR! 3 ) NO DEFAULT NOT NULL

, EXTRACT_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL

, AAO_SUBMIT_ID CHAR! 16 ) NO DEFAULT NOT NULL

, AAO_SUBMIS_TYPE CHAR! 6 ) NO DEFAULT NOT NULL

, AAO_SUB_NAME CHAR! 33 ) NO DEFAULT NOT NULL

, AA0_SUB_ADDR1 CHAR! 30 ) NO DEFAULT NOT NULL

, AA0_SUB_ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL O , AAO_SUB_CITY CHAR! 20 ) NO DEFAULT NOT NULL O O , AAO_SUB_STATE CHAR! 2 ) NO DEFAULT NOT NULL

, AAO_SUB_ZIP CHAR! 9 ) NO DEFAULT NOT NULL _

, AAO_SUB_REGION CHAR! 5 ) NO DEFAULT NOT NULL

, AA0_SUB_CONTACT CHAR! 33 ) NO DEFAULT NOT NULL

, AAO_SUB_PHONE CHAR! 10 ) NO DEFAULT NOT NULL

, AAO_CREATE_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, AAO_SUBMIS_TIME CHAR! 6 ) NO DEFAULT NOT NULL *. , AAO_RECEIVER_ID CHAR! 16 ) NO DEFAULT NOT NULL

, AAO_RECEIVER_TYPE CHAR! 1 ) NO DEFAULT NOT NULL

, AA0_VERSION_NCODE DECIMAL! 5, 0 ) UNSIGNED NO DEFAULT NOT NULL

, AA0_VERSION_LCODE DECIMAL! 5, 0 ) UNSIGNED NO DEFAULT NOT NULL

, AAO_TP_FLAG CHAR! 4 ) NO DEFAULT NOT NULL

, AA0_PASSWORD CHAR! 8 ) NO DEFAULT NOT NULL

, AAO_RETRANS_STATUS CHAR! 1 ) NO DEFAULT NOT NULL

, AAO_MULT_BILL_IND DECIMAL! 1 , 0 ) UNSIGNED NO DEFAULT NOT NULL

, AAO CNTL FILE NO CHAR! 16 ) NO DEFAULT NOT NULL

, AA0_INST_PROF_IND CHAR! 1 ) NO DEFAULT NOT NULL

, AAO_RECEIVER_SUB_ID CHAR! 4 ) NO DEFAULT NOT NULL

, AA0_FILE_LINE_COUNT DECIMAL! 7, 0 ) NO DEFAULT NOT NULL

, AA0_FILE_REC_COUNT DECIMAL! 7, 0 ) NO DEFAULT NOT NULL

, AA0_FILE_CLAIM_COUNT DECIMAL! 7, 0 ) NO DEFAULT NOT NULL

, AA0_BATCH_COUNT DECIMAL! 4, 0 ) NO DEFAULT NOT NULL

, AA0_FILE_TOT_CHGS DECIMAL! 9, 2 ) NO DEFAULT NOT NULL

, AA0_ACCOM_TOT_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL O , AA0_ACCOM_NCOV_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL O O , AA0_ANCIL_TOT_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, AA0_ANCIL_NCOV_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL π , AA0_SUB_ID_NO CHAR! 10 ) NO DEFAULT NOT NULL

, AAO_FILE_REC_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL

, TOT_RECS DECIMAL! 7, 0 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_CHGS_GOOD DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL ^* , TOT_ACCOM_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_ACCOM_CHGS_GOOD DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_NCOV_ACCOM_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_NCOV_ACCOM_CHGS_GOOD DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_ANCIL_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_ANCIL_CHGS_GOOD DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_NCOV_ANCIL_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_NCOV_ANCIL_CHGS_GOOD DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL

, TOT_CLAIMS_IN_BATCH DECIMAL! 5, 0 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_CLAIMS_IN_BATCH_GOOD DECIMAL! 5, 0 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_BATCHES_IN_SUB DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_BATCHES_IN_SUB_GOOD DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, INT_ERR_TYPE CHAR! 2 ) NO DEFAULT NOT NULL

, INT_REC_TYPE CHAR! 3 ) NO DEFAULT NOT NULL

, INT_ERR_CODE CHAR! 4 ) NO DEFAULT NOT NULL

, INP_RECJYPE CHAR! 3 ) NO DEFAULT NOT NULL

, INP_ERR_CODE CHAR! 4 ) NO DEFAULT NOT NULL O , FIELD_CONTENT CHAR! 30 ) NO DEFAULT NOT NULL O O )

> > INVOKE = BA0RESP;

- Definition of table \EDI.$DATA1 .MMRPRDAT.BAORESP o E - Definition current at 16: 18:54 - 10/19/93

! π SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL o n , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , BA0_EMC_PROV_ID CHAR! 15 ) NO DEFAULT NOT NULL , BAO_BATCH_TYPE CHAR! 3 ) NO DEFAULT NOT NULL , BAO_BATCH_NO CHAR! 4 ) NO DEFAULT NOT NULL , BAO_BATCH_ID CHAR! 6 ) NO DEFAULT NOT NULL , BA0_PROV_TAXID CHAR! 9 ) NO DEFAULT NOT NULL , BAO PROV TAXID TYPE CHAR! 1 ) NO DEFAULT NOT NULL

, BA0_PROV_MEDICARE_N0 CHAR! 15 ) NO DEFAULT NOT NULL , BAO_PROV_UPIN_USIN_ID CHAR! 6 ) NO DEFAULT NOT NULL , BA0_PROV_MEDICAID_NO CHAR! 15 ) NO DEFAULT NOT NULL , BA0_PROV_CHAMPUS_NO CHAR! 15 ) NO DEFAULT NOT NULL , BA0_PROV_BCBS_N0 CHAR! 15 ) NO DEFAULT NOT NULL , BAO_PROV_COMM_NO CHAR! 15 ) NO DEFAULT NOT NULL , BA0_PROV_NO_1 CHAR! 15 ) NO DEFAULT NOT NULL , BA0_PROV_NO_2 CHAR! 15 ) NO DEFAULT NOT NULL O , BA0_PROV_ORG_NAME CHAR! 33 ) NO DEFAULT NOT NULL = o o , BA0_PROV_LAST_NAME CHAR! 20 ) NO DEFAULT NOT NULL , BAO_PROV_FIRST_NAME CHAR! 12 ) NO DEFAULT NOT NULL , BAO_PROV_MI CHAR! 1 ) NO DEFAULT NOT NULL o , BAO_PROV_SPECIALTY CHAR! 3 ) NO DEFAULT NOT NULL , BAO_SPECIALTY_LI_NO CHAR! 15 ) NO DEFAULT NOT NULL , BAO_STATE_LI_NO CHAR! 15 ) NO DEFAULT NOT NULL , BAO_DENTIST_LI_NO CHAR! 15 ) NO DEFAULT NOT NULL o n , BA0_ANESTHESIA_LI_NO CHAR! 15 ) NO DEFAULT NOT NULL , BAO_CNTL_BATCH_NO CHAR! 20 ) NO DEFAULT NOT NULL , BAO_BATCH_LINE_COUNT DECIMAL! 7, 0 ) NO DEFAULT NOT NULL , BAO_BATCH_REC_COUNT DECIMAL! 7, 0 ) NO DEFAULT NOT NULL , BAO_BATCH_CLAIM_COUNT DECIMAL! 7, 0 ) NO DEFAULT NOT NULL , BA0_BATCH_TOT_CHGS DECIMAL! 1 1 , 2 ) NO DEFAULT NOT NULL , BAO_ACCOM_TOT_CHGS DECIMAL! 12, 2 ) NO DEFAULT NOT NULL , BA0_ACCOM_NCOV_CHGS DECIMAL! 12, 2 ) NO DEFAULT NOT NULL , BAO ANCIL TOT CHGS DECIMAL! 12, 2 ) NO DEFAULT NOT NULL

, BA0_ANCIL_NCOV_CHGS DECIMAL! 12, 2 ) NO DEFAULT NOT NULL

, BA0_PROVIDER_SUBJD CHAR! 10 ) NO DEFAULT NOT NULL

, T0T_RECS DECIMAL! 5, 0 ) UNSIGNED NO DEFAULT NOT NULL

, T0T_CHGS DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, T0T_CHGS_G00D DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, T0T_ACC0M_CHGS DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_ACC0M_CHGS_G00D DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_NC0V_ACC0M_CHGS DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL

, T0T_NC0V_ACC0M_CHGS_G00D DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL O 3 , T0T_ANCIL_CHGS DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL O

, T0T_ANCIL_CHGS_G00D DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL _ I , T0T_NC0V_ANCIL_CHGS DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL o , T0T_NC0V_ANCIL_CHGS_G00D DECIMAL! 9, 2 ) UNSIGNED NO DEFAULT NOT NULL E

, T0T_CLAIMS_IN_BATCH DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, T0T_CLAIMS_IN_BATCH_G00D DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL 3

, INT_ERR_TYPE CHAR! 2 ) NO DEFAULT NOT NULL

, INT_REC_TYPE CHAR! 3 ) NO DEFAULT NOT NULL

, INT_ERR_CODE CHAR! 4 ) NO DEFAULT NOT NULL

, INP_REC_TYPE CHAR! 3 ) NO DEFAULT NOT NULL

, INP_ERR_CODE CHAR! 4 ) NO DEFAULT NOT NULL

, FIELD_CONTENT CHAR! 30 ) NO DEFAULT NOT NULL

)

> > INVOKE = CAORESP;

-** Definition of table \EDI.$DATA1 .MMRPRDAT.CA0RESP

-- Definition current at 16: 18:57 - 10/19/93

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL , SUBMIS TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_N0 DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_N0 DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , CAO_PAT_LAST_NAME CHAR! 20 ) NO DEFAULT NOT NULL

CO , CAO_PAT_FIRST_NAME CHAR! 12 ) NO DEFAULT NOT NULL c_

03 CO , CAO_PAT_MIDDLE_INIT CHAR! 1 ) NO DEFAULT NOT NULL , CA0_PAT_GENERATION CHAR! 3 ) NO DEFAULT NOT NULL m , CA0_PAT_DOB DATETIME YEAR TO DAY NO DEFAULT NOT NULL co

_E , CAO_PAT_SEX CHAR! 1 ) NO DEFAULT NOT NULL m rπ , CAO_PAT_RES_TYPE CHAR! 1 ) NO DEFAULT NOT NULL

73 , CA0_PAT_ADDR1 CHAR! 30 ) NO DEFAULT NOT NULL rπ , CA0_PAT_ADDR2 CHAR! 30 ) NO DEFAULT NOT NULL ro en , CAO_PAT_CITY CHAR! 20 ) NO DEFAULT NOT NULL , CAO_PAT_STATE CHAR! 2 ) NO DEFAULT NOT NULL , CA0_PAT_ZIP_CODE CHAR! 9 ) NO DEFAULT NOT NULL , CA0_PAT_PHONE CHAR! 10 ) NO DEFAULT NOT NULL , CAO_PAT_MARTIAL_STAT CHAR! 1 ) NO DEFAULT NOT NULL , CAO_PAT_STUDENT_STAT CHAR! 1 ) NO DEFAULT NOT NULL , CA0_PAT_EMPLOY_STAT CHAR! 1 ) NO DEFAULT NOT NULL , CAO_PAT_DEATH_IN CHAR! 1 ) NO DEFAULT NOT NULL , CAO PAT DOD DATETIME YEAR TO DAY NO DEFAULT NOT NULL

, CA0_OTHER_INSU_IN CHAR! 1 ) NO DEFAULT NOT NULL , CAO_CLAIM_EDIT_IN CHAR! 1 ) NO DEFAULT NOT NULL , CAO_CLAIM_TYPE_IN CHAR! 2 ) NO DEFAULT NOT NULL , CAO_LEGAL_REP_IN CHAR! 1 ) NO DEFAULT NOT NULL , CA0_ORIGIN_CODE CHAR! 9 ) NO DEFAULT NOT NULL , CA0_PAYOR_CNTL_NO CHAR! 17 ) NO DEFAULT NOT NULL , CAO_PROV_NUMBER CHAR! 1 5 ) NO DEFAULT NOT NULL , CAO_CLAIM_ID_NUMBER CHAR! 6 ) NO DEFAULT NOT NULL O , CAO_SUB_CLM_CNTL_NO CHAR! 30 ) NO DEFAULT NOT NULL 3 O , CAO_ADMISSION_TYPE CHAR! 1 ) NO DEFAULT NOT NULL , CA0_ADMISSION_SOURCE CHAR! 1 ) NO DEFAULT NOT NULL r πI , CA0_ACCIDENT_HOUR CHAR! 2 ) NO DEFAULT NOT NULL o C , CAO_ADMIT_DATE DATETIME YEAR TO DAY NO DEFAULT NOT NULL , CA0_ADMIT_HOUR DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CA0_STMT_PERIOD_FROM DATETIME YEAR TO DAY NO DEFAULT NOT NULL , CAO_STMT_PERIOD_THRU DATETIME YEAR TO DAY NO DEFAULT NOT NULL o n , CAO_PATIENT_STATUS CHAR! 2 ) NO DEFAULT NOT NULL , CA0_DISCHARGE_HOUR DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CAO_MED_REC_NUM CHAR! 18 ) NO DEFAULT NOT NULL , CA0_TYPE_C_2_COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CA0_TYPE_D_3_COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CA0_TYPE_E_4_COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CA0_TYPE_F_5_COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL , CA0_TYPE_G_6_COUNT DECIMAL! 2. 0 ) NO DEFAULT NOT NULL , CAO TYPE H 7 COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL

, CA0_TYPE_I_8_C0UNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL

, CAO_CLAIM_REC_COUNT DECIMAL! 2, 0 ) NO DEFAULT NOT NULL

, CAO_CLAIM_TOT_CHGS DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_DIS_CONTAIN_CHGS DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_DIS_OTHER_CHGS DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_TOTAL_ALLOW_AMT DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_TOTAL_DEDUCT_AMT DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_T0TAL_COINSUR_AMT DECIMAL! 7, 2 ) NO DEFAULT NOT NULL O , CA0_TOTAL_PAYOR_AMT_PD DECIMAL! 7, 2 ) NO DEFAULT NOT NULL D O , CA0_TOTAL_PAT_AMT_PD DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_TOTAL_SER_CHGS DECIMAL! 7, 2 ) NO DEFAULT NOT NULL

, CA0_PROV_DISCOUNT_INFO CHAR! 16 ) NO DEFAULT NOT NULL o E , CAO_REMARKS CHAR! 103 ) NO DEFAULT NOT NULL

, CA0_ACCOM_TOT_CHGS DECIMAL! 10, 2 ) NO DEFAULT NOT NULL

, CA0_ACCOM_NCOV_CHGS DECIMAL! 10, 2 ) NO DEFAULT NOT NULL

, CA0_ANCIL_TOT_CHGS DECIMAL! 10, 2 ) NO DEFAULT NOT NULL o n . CA0_ANCIL_NCOV_CHGS DECIMAL! 10, 2 ) NO DEFAULT NOT NULL

, TOT_RECS DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_CHGS DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_CHGS_GOOD DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_ACCOM_CHGS DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_ACCOM_CHGS_GOOD DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_NCOV_ACCOM_CHGS DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_NCOV_ACCOM_CHGS_GOOD DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT ANCIL CHGS DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_ANCIL_CHGS_GOOD DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_NCOV_ANCIL_CHGS DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, TOT_NCOV_ANCIL .HGS_G00D DECIMAL! 7, 2 ) UNSIGNED NO DEFAULT NOT NULL

, INT_ERR_TYPE CHAR! 2 ) NO DEFAULT NOT NULL

, INT_REC_TYPE CHAR! 3 ) NO DEFAULT NOT NULL

, INT_ERR_CODE CHAR! 4 ) NO DEFAULT NOT NULL

, INP_REC_TYPE CHAR! 3 ) NO DEFAULT NOT NULL

. INP_ERR_CODE CHAR! 4 ) NO DEFAULT NOT NULL

CO , FIELD_CONTENT CHAR! 30 ) NO DEFAULT NOT NULL O O )

> > INVOKE = DA0RESP;

- Definition of table \EDI.$DATA1 .MMRPRDAT.DAORESP o - Definition current at 16: 19:00 - 10/19/93 π

(

SUBMITTER_CODE CHAR! 3 ) NO DEFAULT NOT NULL o ^* , SUBMIS_TS DATETIME YEAR TO FRACTIONS) NO DEFAULT NOT NULL , SUBMIS_NO DECIMAL! 6, 0 ) NO DEFAULT NOT NULL , BATCH_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , PAT_CNTL_NO CHAR! 20 ) NO DEFAULT NOT NULL , CLAIM_SEQ_NO DECIMAL! 4, 0 ) UNSIGNED NO DEFAULT NOT NULL , DA0_OCCURS_NO DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL , DA0_SEQ_NO CHAR! 2 ) NO DEFAULT NOT NULL , DAO_CLAIM_FILE_IN CHAR! 1 ) NO DEFAULT NOT NULL , DAO PAY SOURCE CHAR! 1 ) NO DEFAULT NOT NULL

CHAR! 2 ) NO DEFAULT NOT NULL CHAR! 5 ) NO DEFAULT NOT NULL CHAR! 4 ) NO DEFAULT NOT NULL CHAR! 33 ) NO DEFAULT NOT NULL CHAR! 20 ) NO DEFAULT NOT NULL CHAR! 33 ) NO DEFAULT NOT NULL CHAR! 1 ) NO DEFAULT NOT NULL CHAR! 15 ) NO DEFAULT NOT NULL

CO CHAR! 15 ) NO DEFAULT NOT NULL

03 CO CHAR! 1 ) NO DEFAULT NOT NULL CHAR! 1 ) NO DEFAULT NOT NULL DECIMAL! 2, 0 ) UNSIGNED NO DEFAULT NOT NULL

CO

_c CHAR! 25 ) NO DEFAULT NOT NULL m m CHAR! 20 ) NO DEFAULT NOT NULL

73 CHAR! 12 ) NO DEFAULT NOT NULL

C_ CHAR! 1 ) NO DEFAULT NOT NULL o n CHAR! 3 ) NO DEFAULT NOT NULL CHAR! 1 ) NO DEFAULT NOT NULL DATETIME YEAR TO DAY NO DEFAULT NOT NULL CHAR! 1 ) NO DEFAULT NOT NULL CHAR! 1 ) NO DEFAULT NOT NULL CHAR! 7 ) NO DEFAULT NOT NULL CHAR! 1 ) NO DEFAULT NOT NULL CHAR! 1 ) NO DEFAULT NOT NULL CHAR! 1 ) NO DEFAULT NOT NULL

, DAO_COVERED_DAYS DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, DA0_NON_COVERED_DAYS DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, DA0_COINSURANCE_DAYS DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, DAO_LIFETIME_RESV_DAYS DECIMAL! 3, 0 ) UNSIGNED NO DEFAULT NOT NULL

, DAO_PROV_ID_NUM CHAR! 13 ) NO DEFAULT NOT NULL

)

End of SQLCI Session o O CO

O c

3

o n