MXPA97008955A - Telephone / transaction registry device and system for registering transaction data on bases of da - Google Patents

Abstract

The present invention relates to a system for entering transaction data into a remote database, comprising: a data entry device, an exhibitor, a data transaction terminal including a microprocessor, a shape memory, and a operating system operated in a way that controls the microprocessor to present the display at least one shape stored in the shape memory as data streams; elicitation data input in the form of a desired type of transaction in the data entry device by a user, the at least one form includes at least one personalized suggestion to the type of transaction desired, the data transaction terminal further includes means for structuring at least the entry of data by the user in response to at least one suggestion in the data transaction for transmission to the remote database and a remote database server associated with the database e remote data that receives the data transaction, creating from the data transaction, depending on the type of transaction desired, at least one additional data transaction that contains data for a particular record in the remote database, and stores the at least one additional data transaction in the registry particul

Description

TELEPHONE / TRANSACTION REGISTER DEVICE AND SYSTEM TO REGISTER TRANSACTION DATA IN DATABASES BACKGROUND OF THE I NVENTION FIELD OF THE I NVENTION The present invention relates to a system for automatically capturing data at the point of transaction and storing the data in the appropriate database (s) and, more particularly, to a data transaction processing system that includes a data recording device. transaction that can be operated selectively in a telephone mode and in a transaction registration mode. In telephone mode, the transaction registration device operates like a conventional telephone. However, in the transaction log mode, the user uses menus for forms that make it easier to record data. The registered data and the forms together form the data transactions that are transmitted to one or more databases for processing and storage. The database (s) also "airs" the data transactions in their component parts and transmits those component parts to other databases for processing and storage so that the data in the data transactions are automatically updated all the base items. of current data affected by such data.

DESCRIPTION OF THE PREVIOUS TECHNIQUE The telephone has become an increasingly versatile instrument. The functionality of telephones has been extended by incorporating the functions of answering machines, facsimile machines and the like. Point of entry systems have also been developed which incorporate computational processing capabilities in conventional telephones. For example, in U.S. Patent Nos. 5,195,130, 5,008,927 and 4,991,199 a computer / telephone apparatus is described which configures a telephone as a programmable microcomputer which is operated through the standard 12-key telephone keypad. A programmable bridge layout is reconfigured to accommodate various types of software that require different hardware configurations but without actually reconfiguring the hardware. The reconfiguration data is received from the main network computer and is used by the programmable microcomputer to emulate the hardware of any of a plurality of service offices that connect to the network's primary computer. In this way, the telephone / computer is configured to communicate data to / from any of a number of different service offices by means of conventional telephone lines. However, telephone / computer systems of the type described in the aforementioned patents are typically complicated and expensive and are limited by the types of operating software that can be loaded from the main computer of the network. Likewise, such telephone / computer are relatively slow since the microcomputer must be reconfigured before communication with the requested service office is allowed. Due to these characteristics such telephone / computer systems are typically used in public facilities and are not efficient to create point of entry transactions in typical commercial or private facilities. An entry point transaction system that does not have those limitations and that is independent of the operating system is desired. The elimination of the requirement of a conventional operating system and the associated application programs for the microcomputer of a data recording device would greatly reduce the cost of such a device. However, to date this has not been possible since the operating system is necessary to operate the application programs that control data communications and handle discrete parts of the system together. Unfortunately, such application programs require substantial amounts of local memory and substantial processing power to execute the desired functions. As well, operating systems by themselves tend to be very expensive for their acquisition and maintenance. Accordingly, a data recording system is desired which does not have the inherent imitations of conventional entry point systems such as the requirement of a standard operating system for communication with a remote service office or archive server. A data recording device and associated system which executes a minimum amount of processing in the data recording device is desired so that the data recording device can be as simple and economical as possible, thereby elevating it. the cost of the device at a scale suitable for most commercial and private uses. It is also preferable that the data recording device provides a wide range of functionality in requiring a local operating system program and a plurality of application programs to implement each function. The present invention has been designed to meet those needs.

BRIEF DESCRIPTION OF THE INVENTION The system that meets the aforementioned needs in the art includes a transaction registration device that allows the user to organize and control all aspects of their personal transactions as well as any transactions that may occur in an office facility. In its simplest terms, the transaction registration device formats the input data in a data transaction having content that is dependent on the type of application to which the associated data belongs. These data transactions are then transferred to a local or remote database server that "airs" each data transaction into its component parts to update all the databases that contain the data for which the data in the component parts belong. . In this "transaction registration modes" the transaction registration device of the invention functions as a multi-purpose workstation. However, since data transactions are created without the use of an operating system or application programs, the transaction registration device is very simple and inexpensive and can be easily integrated with the client's desk phone or portable telephone . The present invention combines computer technology and telephone technology to allow transaction data to be captured at the starting point of the transaction. The transaction registration device is integrated into a conventional telephone that acts as either a normal telephone in the telephone mode or as a transaction registration device in a transaction registration mode. When in phone mode, the phone operates in a conventional manner. However, when in the transaction log mode, the transaction log device is driven by a microprocessor which is, in turn, driven by a transaction assembly server independent of the operating system (or application) (TAS) comprised of data streams stored in a fast PROM. The TAS is absolutely self-contained in its relation to the physical equipment of the transaction registration device and generally executes the two basic functions of (1) generating a template or form from a data stream and (2) developing a transaction of data with form the user activates the data in response to indications visible in the template or form. The template is a series of data streams read from a local fast memory or transmitted directly from an external source such as a database file server. During the operation, the data recorded by the user in response to the visual indications in the template are accumulated within the data transactions that are immediately transmitted to an external database server. Unlike typical prior art systems, data transactions are not stored locally for processing by the local microprocessor once the data transaction has been completed. Conversely, the only storage required in the transaction registration device is a fast PROM to store the fixed program of the TAS, a fast memory to store the data streams used by the fixed program TAS to complete a form and the numbers of modulator for the remote database servers and a small RAM that operates as a temporary input / output transaction memory to store the data streams of the template and the responses of the users to the visual indications in the template during the assembly of a data transaction. Transaction time memories only need to be as large as the largest data transaction since they only store the form until the complete data transaction is completed. In this sense, the transaction log device serves as an assembly point for specific transactions until they are ready for transmission to an external database server for processing and storage. The data transaction formed by the transaction registration device is transmitted by means of the modulator to a local or remote database server for processing and storage. The data transaction is received by means of standard protocols in the database server which, depending on the application, stores the complete data transaction, ventilates the data transaction to produce auxiliary records that are then stored, and / or they advance the data transaction or some or all of its auxiliary records to other database servers to update other databases associated with those database servers. Also, in response to requests from the transaction registration device, any of the database servers may send data streams to the transaction registration device for use in terminating the fields in the data transaction or in the display of new forms or menus for selection.

In this way, the data transaction system of the invention comprises at least three rows: a first row to capture the transaction of data from the user, where the data transaction has a one-to-many relationship towards archival structures; a second row to ventilate the data transaction in its component parts on a specific system basis so that part of the component has a one-to-one correspondence with a file; and a stubborn row to provide additional ventilations of data transactions on a specific application basis so that each application has its own set of data transactions. A preferred embodiment of the transaction recording device of the invention resembles a conventional telephone except that it includes a touch screen and an optional keypad for data recording in addition to the digital key and conventional function inputs. A telephone microphone or helmet with headphones is optional and can be replaced by a microphone and a speaker. The transaction registration device of the invention also includes RS-232 and other input / output ports to accommodate other options such as the wireless (RF) receiver, a magnetic card and / or smart card reader. , a video camera and video screen, infrared controllers and if my home. The phone preferably has normal key phone functions as well as mobile and cell phone options. Preferably, the transaction registration device contains a microprocessor such as an Intel 80386SX or higher, one megabyte of fast memory for dynamic storage of the data streams of the seedlings, one megabyte of rapid PROM for storage. TAS fixed program and a 128 kB RAM which functions as a temporary transaction memory to store the plant data streams and user responses until the end of the data transaction. A graphic display screen is also provided to display the templates to the user for the registration of the data that will form the data transactions. Preferably, the graphics display screen is of the order of 24 lines per 40 characters for a desk unit and 1 2 lines per 40 characters for a cell unit. The transaction assembly server (application) (TAS) guides the user to the desired plant by means of the menu selections, where the menus and seedlings are stored in the fast memory according to the data streams and they are called by the fixed program TAS when it is selected by the user. Generally, menus are treated as a special type of template or form. The templates stored in the fast memory can be updated at any time to handle particular applications by reading in a new data set that has been created offline and downloaded by means of the modulator or direct connection to the fast memory of the registration device of transaction. Alternatively, the data can be downloaded to an RS-232 input. The same connections can be used to provide automatic reading from a remote database or automatic writing to a remote database. New applications can be added simply by adding additional quick memory elements that contain the necessary templates for the new application. The telephone / transaction device and the associated system for storing transaction data according to the invention is unique in that it separates the user from the database and provides a user-friendly and simple way to record transaction data without requiring a local operating system to operate different application programs. Since all data is recorded as data transactions determined by the template adjusted for particular applications, user applications can be generated so that unique user application programs are not necessary to be written when a new application is added. However, if the code is necessary or if a multimedia item is included in the data transaction, it can be added to a data transaction as an additional parameter stream in the data stream that forms the data transaction. Likewise due to the nature of the data in the respective fields of the templates for particular applications that are known in advance, the interface for a database server to allow the storage of the data transactions and their component parts in the appropriate databases in the appropriate formats so that each database becomes common. In an alternative implementation of the invention, a process can be selected from the menu of the transaction recording device which creates a "visible" menu corresponding to a voice mail of a remote telephone mail system. When the process is selected, the telephone or modulator interface makes a telephone connection to the remote telephone mail system and, once the connection is made, the data transaction assembler sends a data request for a visual representation of the telephone mail menu of the remote telephone mail system by means of the telephone connection to the remote telephone mail system. A stream of data containing the visual representation of the telephone mail menu from the remote telephone mail system is then returned by means of the telephone connection and stored in a memory of the transaction registration device for presentation to the telephone screen. display of the transaction log device 12. When the desired phone mail menu option is selected from the "visible" voice mail menu, the data of the transaction builder creates a data transaction that indicates which menu item was selected and sends the data transaction to the remote telephone mail system by means of the telephone connection. Based on the menu selection, the remote telephone mail system then returns a stream of data containing a visual representation of the following telephone mail menu to a telephone connection for storage and display. This process is repeated until the calling party is required to leave a message to the called party or the called party is reached.

BRIEF DESCRIPTION OF THE DIAMETERS The above features of the invention will become more apparent to those skilled in the art in view of the following detailed description of the invention, of which: Figure 1 is a schematic diagram of a system for recording data transactions within databases of data according to the invention. Figure 2 illustrates a generic template for use in creating a data transaction according to the invention. Figure 3 illustrates a "ventilated" data transaction in which the component parts of a data transaction are stored in specific database and file specific locations. Figure 4 illustrates the "ventilated" transaction of Figure 3 in the context of the system illustrated in Figure 1. Figures 5 (a) and 5 (b) illustrate together a preferred embodiment of a transaction registration device according to the invention. Figure 6 is a schematic diagram of the electronic components of the transaction registration device illustrated in Figures 5 (a) and 5 (b). Figure 7 is a flowchart of a menu driven (application) transaction (TAS) assembly server according to the invention.

Figure 8 is a flow chart illustrating a technique for processing a form used to form a data transaction according to the invention. Figures 9 (a) and 9 (b) together illustrate a flow diagram of a technique for completing and editing a data transaction according to the invention. Figure 10 is a flowchart that illustrates how the TAS validates the fields of each data transaction.

DETAILED DESCRIPTION OF CURRENT MODALITY PREFERRED A system and method that meets the aforementioned objects and provides other beneficial features in accordance with the currently preferred exemplary embodiment of the invention will be described with reference to Figures 1-10. Those skilled in the art will readily appreciate that the description given herein with respect to those figures is for purposes of explanation only and is not intended in any way to limit the scope of the invention. For example, those skilled in the art will appreciate that the telephone / transaction registration device and the system for recording data transactions in remote databases according to the invention can be used in numerous installations in numerous applications. Therefore, all questions regarding the scope of the invention must be resolved by reference to claims.

A. DESCRITION OF THE SYSTEM 1 . Review The system of the invention provides automatic capture and computer processing of data associated with data transactions as they are presented. As used herein, a data transaction is the combination of a form or template or a series of forms or templates that contain indications of data recording and data recorded in response to those indications. Throughout the rest of this specification, the words "form" and "templates" will be used interchangeably. The data transactions are generated by a transaction registration device through an interactive process between the user and the form. The data transaction is assembled in a temporary memory in the transaction data between the data transaction registration device and then transmitted to an external database for storage. Local storage for data transactions is not available. The data transaction is defined externally by the database in which all the applications consist of a series of forms adapted to request the registration of the data necessary to update the databases containing the data. related to the particular application. Generally, the data transaction will have a one-to-many relationship to the archival structures of the database that contains the data for that application. The data transactions are recorded using the transaction registration device. Preferably, the transaction registration device is integrated with electronic telephone components so that the resulting device can be operated selectively as a conventional telephone or as a data transaction recording device. The resulting transaction registration device preferably includes a touch screen and / or keyboard that provides input to a transaction assembly (application) server (TAS) which, in turn, presents selection options by means of menus and forms for termination by the user. The selection of menu and form and the form control is done by touch, by selecting the key of the keyboard, moving a cursor to the appropriate selection point and pressing a key or even by voice command. Whenever the data record is desired (different from the mere selection), it is achieved by means of a selection process driven by a menu and / or by direct registration of the data using a keyboard, a numeric keypad, a touch screen and if my home. In the menu-driven case, a set of options is presented on the display screen through the fixed TAS program. If this set of options exceeds the capacity of the display screen, then the list is moved up or down by using the up or down keys on the device, by voice command or by touching the points of movement command. Once the selection is made, the data associated with that selection is automatically recorded in a form from a local or remote database, or the data is entered by the user. In the case of a keyboard registration, the TAS fixed program may present a keyboard in the lower part of the display screen for touch registration; alternatively, an optional keyboard located at the base of the transaction registration device may be used. When the data is recorded independently of a selection process, such data can also be registered using a starter card if the data reside on the starter card or the data can be transferred within the data transaction by means of the modulator from a External source. The data read from the boot card can be used to fill a form or can be transmitted to an external database or computer. The data returned from the database or external computer through the modulator can also be used to fill the fields in the form. As desired, the data in the data transaction can also be written to a boot card or a memory card and the like. The fixed program TAS of the invention stores the options as well as the control programs (micro codes) for the processor for use with the templates in the creation of the data transactions. The fixed program TAS also includes a program that allows the connection by means of a modulator to one or more computers and external databases. Preferably, two modes of operation are available: the transaction registration mode (with or without a modulator connection) and the telephone mode. A selection of the transaction registration mode or telephone mode is made through a switch selection on the transaction registration device.

When the transaction log is placed in the transaction log mode, the fixed TAS program immediately presents selection menu for all the system options programmed for handling. In telephone mode, on the other hand, a dial tone is provided and the telephone keypad is enabled. In telephone mode, one or more lines may be placed to allow simultaneous use of the transaction registration device without interfering with the modulator connection. However, if an individual telephone line is used, telephone capacity is available at all times or intermittently by means of the modulator as specified for the particular application. In intermittent mode, "dialing" the transaction log device will control dialing and data transfer to the remote database server. On the other hand, if you use your phone with an automatic dialing mechanism that uses a phone list, the transaction log device can automatically switch from phone mode to transaction log mode. In this case, a display over the telephone can be used to present a name and a telephone list from which a selection can be made according to the menu selection techniques described below. 2. Data Transaction System (Figures 1-4) Figure 1 is a schematic diagram of a system 10 for recording data transactions in databases according to the invention. As illustrated, the system 10 comprises a first row for capturing the data transaction having a one-to-many relationship for the file structures, a second row for ventilating the data transaction in the component parts that have a one-to-one relationship to file structures and a third row to provide additional ventilation of data transactions for specific applications. The first row comprises a transaction registration device 12 that captures the transaction of data from the user in response to any of a plurality of user inputs. The transaction registration device 1 2 includes conventional telephone electronic components 14 and a loudspeaker 1 6 and a data transaction assembler 18 to create a data transaction according to the invention. An exhibit screen 20 is preferably associated with the data transaction assembler 18 so that the user can monitor the creation of each data transaction. The telephone electronic components 14 are connected to a telephone communication network 22 by means of a conventional voice connection 24 over the telephone lines, while the data transaction assembler 18 is connected by means of a telephone network. telephone lines 26 to one or more database servers 28. As illustrated in Figure 1, telephone lines 24 and 26 may be separate lines, thus allowing the simultaneous use of telephone registration functions and data or the telephone electronic components 14 and the data transaction assembler 18 may be connected to a single line as illustrated in shading in Figure 1. Of course, when the telephone electronic components 14 and the transaction assembler 18 are connected to an individual line, a mode switch will be enabled for its mutually exclusive operation, or alternatively, any of a number of conventional transmission schemes can be used for to allow the simultaneous transmission of the voice from the electronic components 14 and the data from the data transaction assembler 18 on the same line. During the operation in the transaction registration mode, a transaction registration device 12 is sensitive to the user's input devices such as the touch screen, a telephone keypad, a keyboard, a microphone, a boot card, a memory card, video input and the like to form the data transactions using the data transaction assembler 18. Alternatively, the transaction registration device 12 operates in a telephone mode like a conventional telephone and receives inputs from a microphone and / or a handset, a keypad telephone keypad and the like. Further details of the transaction registration device 12 and the data transaction assembler 18 will be provided in the text section with respect to Figures 5-10. The second row comprises one or more database servers 28 and their associated databases 30. In general, each database server 28 receives data transactions from one or more transaction registration devices 12 and "ventilates" the data transactions received in their component parts for storage in the appropriate files of the associated database 30. In other words, the file structure of one to many of the data transactions from one or more transaction registration devices 12 it becomes many one-to-one data transactions for storage in individual files of database 30.

Each database server 28 provides a modulator 32 for transmitting / receiving data from the telephone lines 26, particularly the data transactions from one or more of the transaction registration devices 1 2. Preferably, the transactions of data are transmitted over the telephone lines 26 as data packets having, for example, 128 bytes, where 1 20 bytes contain the information and 8 bytes contains control data. A row of transactions 34 acts as a temporary input memory for the received data transactions and controls the speed of presentation of the data transactions to the transaction controller 36. The transaction controller 36 processes the data transactions received for the transaction. extract the physical file relationships from the component parts of the data transactions and store the component parts and the different combinations thereof in the appropriate files of the associated database 30. Alternatively, the transaction controller 36 may process a requesting data from the data transaction assembler 18 requesting information from the database 30 to complete certain fields of a data transaction that is being processed by the transaction registration device 12. The database 30 then provides the requested information to the database server 28 which, by means of the modulator 32 provides a data stream back to the data transaction assembler 18 for use in terminating data transactions or presenting additional menus and forms according to the invention. Typically a user ID and access words are transmitted to the transaction controller 36 to allow a connection via the data transaction assembler 18. Therefore the transaction controller 36 also checks and stores the installation and shutdown information in addition to store data transactions and direct reconstituted data transactions to other database servers as described herein. In addition, the database server 28 may include a conventional telephone mail system with an associated database for storing the voicemail messages. In this case the data transaction may include voice data for storage in the remote voicemail system. As shown in Figure 1, several database servers 28 may be provided. Preferably each transaction registration device 1 2 has an associated database server 28 to execute any desired processing of its data transactions, although it is preferred that the data transactions be copied to at least one other database server 28 , as shown in Figure 1. This redundancy minimizes the possibility of data loss in the event of a power failure and the like. Preferably, each database server 28 contains essentially the same physical equipment although the modulator 32, the transaction row 34 and the transaction controller 36 have not been shown for all the database servers 28 for ease of illustration. In the transaction registration mode, the data transaction assembler 18 of the transaction registration device 12 creates a data transaction that is transmitted to an associated transaction controller 36 of an associated database server 28. By "associated" "is implied that the data server 28 functions to execute any requested or necessary processing together with the storage of a data transaction from a particular transaction registration device 12. Of course, a particular database server 28 may have several transaction registration devices 12 associated therewith. So that no data is lost, a particular database server 28 can also serve as a backup for another database server 28 in the case of failure of any database server 28.

As will be explained in more detail below with respect to Figures 2-4, the database server 28"airs" the data transactions received from the data transaction assembler 18 and provides the component parts of the data transactions file dependent "ventilated" via modulator 32 to other database servers 28 as necessary to update other databases. Alternatively, as shown by dashed line in Figure 1, the "ventilation" of the data transactions can be retrieved by the data transaction assembler 18 in the transaction registration device 12 and the component parts transmitted to all the bases of appropriate data 28 to update the data in them. For this purpose, the data transaction assembler 18 will also need to know the modulator numbers for all the data servers 28 which are updated by the data transactions 29. However, those skilled in the art will appreciate that this latter alternative will require the access to numerous telephone lines through the transaction registration device and that such telephone lines are not always available to the user. Finally, the third row of the system 10 includes additional database servers 38 and databases 40 that support file dependent data transactions for specific applications. This additional row of database servers 38 and databases 40 allow data in data transactions to be directed to application-specific databases for storage of application-specific data and access by those recording devices of transaction 12 that require data related to that specific application. The creation and storage of a data transaction according to the invention will now be described with respect to Figures 2-4. The data transactions are created by the data transaction assembler 18 as a data stream of a known format. A generic data transaction is illustrated in Figure 2. As defined herein, a data transaction is created using a form that contains one or more of the following: indications, instructions, menu selection options and a template with fields for data recording. Generally, the form of the menu consists of visual indications to select a form, another menu or a process and an individual slot to record a selection, while the form of data recording consists of visual indications and instructions together with fields to record data. as shown in Figure 2. The data record form can have a single or multiple fields to record data. In the transaction log mode, the user navigates through the menus of the data transaction assembler 1 8 until a form related to a particular type of data logging operation is selected. Once selected, the data transaction form 42 is presented to the user in the display device 20. The transaction form 42 is a collection of data defining the visual display on the display device 20 and a list of the fields through which the links to the external database files are defined. As shown in Figure 2, the data transaction form 42 includes a format field 44 that identifies the type of data transaction to which this form belongs, the length of the form, the number of pages in the form, the number of bytes in each field, storage keys, and the like. The body of the data transaction form 42 comprises a predetermined series of visual indications 46 which are provided to the display 20 as a data stream. The visual indications preferably include descriptive data that can be alphanumeric, an icon, or a list that is scanned if necessary. Fields 48 are blanks of a predetermined size provided to accept user input in response to each visual indication. Generally, the size of each field 48 is also stored in the data stream that defines the form of data transaction 42. Since the visual identifications are adapted to produce the data necessary for the application for which the In the form of data transaction 42, the fields 48 will include the user data necessary to process a data transaction for that particular type of application. The user's response becomes part of the data stream that forms the data transaction. Typically the data transaction form 42 also includes a varied processing field 50 that allows the unique processing data for that form to be added to the data transaction for transmission. Such processing data may include, for example, equations that define the relationships of the data in certain fields of the data transaction or audio or video data linked to multi-media data transaction. In addition, the data if n exposure associated with the data recording time, the date of the data recording, the user ID and the like may be stored in the miscellaneous processing field 50. Figures 3 and 4 illustrate the "ventilation" of the data stream that forms the data transaction created using the data transaction form 42 of Figure 2. As shown in Figure 3, each data transaction contains data that is specific to a data base. particular and / or specific data for particular files in one or more databases. The data in the data transaction is "ventilated" accordingly. For example, the complete data transaction from Figure 2 (Form A) is stored in a particular file (file 110) of the database associated with the transaction registration device 12 that created the data transaction (base of data 11 in Figure 1). The storage of the complete data transaction is desirable so that the records can be maintained in the event of system error, power failure and the like. The transaction controller 36 extracts after the data from those fields of the data transaction that it knows to be related in the forms of that particular type. For example, the data in fields 1, 2, 6., 10 and a function of the data in field 11 can be related to a particular application stored in field 111 of database 11. Similarly, data in fields 3, 6, 10, 12 and 14 may be related to an application stored in field 112 of base 11, while data in fields 1, 2, 7, 8, 9 and a function of data in fields 10, 11 and 12 may be related to a stored application of field 1 13 of database 1 1. Those fields are extracted from the data transaction received by the transaction controller 36, reconstituted in a file record of the appropriate format, (as necessary), and stored in the associated database 30. All data in the The data transaction received or a subset thereof may be retransmitted to one or more additional application-specific databases, such as the database 21 or the databases 40 in Figure 3. As illustrated in FIG. Figure 3, the data specific to the database of fields 1, 4, 5, 1 3 and 14, which form the subset (Form B) of the original transaction (Form A) is stored in file 210 of the database of data 21 so that a complete record can be maintained. The subsets of the data in Form B are then stored in specific files of the database as indicated. In this way the data of the original data transaction (Form A) is automatically sent to all databases containing files that must be updated by any or all of the data in Form A. Figure 4 illustrates the ventilation of the data transaction in Figure 3 for the system 10 illustrated in Figure 1. As shown, the data in the data transaction (Form A) is extracted to update files 110-113 of database 11 as well as assets 210-212 of database 21. A redundant copy of Form A is maintained also in the database 12. As will be explained in more detail below, the system of Figures 1-4 is significant in that the data in the data transaction can update one or more databases that they service the file servers operating under the control of numerous types of operating systems without the requirements of a terminal or emulation of the operating system by the device of the transaction register 12. On the contrary, the transaction registration device 12 of the invention allows the capture and storage of data with a minimum amount of data storage with a minimum amount of processing at the transaction registration point (row 1), which, of course, reduces the minimum the cost of the system.

B. Transaction Registration Device 12 (Figures 5-10) As mentioned in the above, the transaction registration device 12 is characterized in particular by the data transaction assembler 18, which controls the different operations of the transaction registration device 12 in its transaction registration mode. Preferably the data transaction assembler 18 uses simple menu structures and predetermined forms stored as data streams in a fast memory to facilitate data recording. Menus are treated as a special type of form and are used to call other forms, menus or processes. The forms, on the other hand, are used to create data transactions that are sent to one or more file servers operating under different operating systems, where the data transaction is "ventilated" into its component parts for storage in a structure of single file to update all the records affected by the data in that data transaction. In turn, "ventilated" data transactions can be transmitted to another application-specific database (row 3) for storage. The processes, on the other hand, are selected to execute the limited processing of the values in the fields of the forms. Such processing may be performed locally although it is preferably executed by the associated database server 28. 1 . Hardware A preferred embodiment of a transaction registration device 12 incorporated within a conventional telephone is illustrated in Figures 5 and 6. As shown in Figures 5a, a preferred desktop mode of a transaction registration device 12 includes a housing 52 of the order of 20.32 cm (8 inches) wide by 30.48 cm (12 inches) long to house the telephone electronic components 14 and the hardware of the data transaction assembler 18. The transaction registration device 12 includes a microphone additional (or case with headphones) 54, support 56 (Figure 5b), numeric keypad 58, telephone function keys / line 60, microphone 62, and loudspeaker 16, which facilitates the operation of the transaction registration device in the mode of phone. As is known to those skilled in the art, telephone functions accessed by telephone function keys 60 may include muffler, loudspeaker, line selection, conference, hold, transfer, volume control and the like. However, the transaction registration device 12 is further characterized by the display 20 with touch screen 64, switch / computer mode 66 function keys, optional retractable keyboard 68 and optional magnetic / boot card reader 70, which facilitates the operation of the transaction registration device 12 in the transaction registration mode. A memory card reader can also be accessed by means of a gate (not shown) as in laptops. Preferably, the screen 20 is a reflecting liquid crystal display, high contrast, which can be rotated (LCD) with a minimum of 20 characters per line and 16 lines (preferably 40 columns by 24 lines), while the touch screen 64 is preferably a pressure-sensitive keyboard made of 224 keys (16 rows of 14 keys) attached to the face of the LCD. Preferably, the LCD is also available as a back lighting unit. Of course, the touch screen 64 is not necessary if the optional keyboard 68 is provided. In addition, a battery backup 71 (Figure 6) can also be provided; alternatively, the battery 71 may be the primary energy source for a portable (cellular) mode of the transaction registration device 12 according to the invention. Figure 5b illustrates several of the connections to the transaction registration device 12. Typically, the transaction registration device 12 includes a headphone jack (headset) 72 for connecting the optional headset (hearing aid) 54 to the telephone electronic components 14 when it is desired to communicate more privately than when only the microphone 62 is used and the loudspeaker 16. A video input port 74 is also provided for connecting the conventional data compression circuit 75 within the transaction registration device 12 (Figure 6) to an optional video camera that provides vi o of the telephone type with image or for a facsimile device or electronic scanner. Such video data may be added to a frame at a time at the end of a data transaction in the diverse processing field 50 to create a multimedia data transaction as described above with respect to Figure 2. A port of video output 76 is also provided to provide decompressed video or facsimile data from the data decompression circuit 77 (Figure 6) to a video receiver, a high quality computer monitor, a facsimile device and the like. Such data may also be provided to a printer port 82 or 84 as desired. A multi-line telephone socket (modulator interface) 78 is also provided. Preferably, the interface of the modulator 78 provides separate modulator connections for the telephone electronic components 14 and the data transaction assembler 18, although only a single connection is necessary. modulator An optional infrared transceiver 80 is further provided to allow operation of remote control of television and video equipment and the like in response to data transactions transmitted / received by the transaction registration device 12. Infrared transceiver 80 includes a generator microcircuit of internal signal that reads the parameters stored in the transaction assembler 18 to determine the appropriate transmission frequencies for the infrared signals. The control of the infrared devices is provided through menus on the screen 20. Additional infrared transceivers 80 may also be provided at each corner of the housing 52 so that the infrared signal will cover more area (each transmitter typically covers a circumference of about 60 °). All such devices are known to those skilled in the art and will therefore not be described in detail herein. A serial port 82 (RS-232) of computer interface and parallel port 84 are also provided to transmit / receive data to or from another computing device and to provide output from a printer. A power input port 86 and a keyboard input 88 are also provided. The keyboard input 88 accepts a connection from a standard keyboard or a folding type keyboard (not shown) that can be used in addition to or instead of the retractable keypad 68. An optional removable PCMCIA memory card interface 89 (FIG. ) to update the operation instructions of the data transaction assembler 1 8 and an optional RF transceiver 90 (Figure 6) for network operation to other electronic equipment may also be provided on the transaction registration device 1 2 as appropriate. want. Figure 6 is a schematic diagram of the electronic components of the transaction registration device 1 used in Figures 5 (a) and 5 (b). Corresponding reference numerals for corresponding elements are used in Figures 5 (a), 5 (b) and 6. As shown in Figure 6, in addition to the elements described above with respect to Figures 5 (a) and 5 (b), the transaction registration device 1 2 may include an indvidual voice recognition circuit 91 which allows voice selection of menu options and the like. In the "voice selection" mode, the user would say "1", "2" or "3" depending on the desired menu selection, and the voice would be picked up by the microphone 62 on the housing 52 of the transaction registration device 12 and recognized by the circuit voice recognition 91. The appropriate selection signal would then be sent to the data transaction assembler 18. Similarly, the data transaction assembler 18 can provide the audible output using a conventional speech synthesizer 92, which provides the audio output to the user or via loudspeaker 16 and to a caller via the modulator / telephone interface line connection 78. The voice synthesizer 92 can, for example, allow certain data transactions to be provided. audio for a blind person who can not make selections from a conventional video screen. In addition, a voice recorder 93 may also be provided for recording portions of telephone calls, portions of data transactions with voice, or messages from the caller when a conventional digital answering machine is used. On the other hand, the speech recorder 93 can be provided in the database server 28 for use in the storage / advance of audible messages for the databases 30. As noted in the above, the transaction registration device 12 it is characterized by the data transaction assembler 18, which controls the creation of the data transactions in the transaction register mode. As shown in Figure 6, the data transaction assembler 18 is implemented in the physical equipment using a conventional microprocessor 94 such as an Intel 80386SX (20 MHz or higher) or equivalent, a TAS PROM 95, a shape memory / menu 96 and a temporary transaction memory (RAM) 97. In a preferred embodiment, the TAS PROM 95 is a fast PROM that maintains 1 MB of control (fixed program) for the microprocessor 94 (such as the microcode for the algorithms of the Figures 7-10 below), while the form memory / menu 96 is a fast memory that holds 1 MB of menus and data transaction forms.

The temporary transaction memory 97, on the other hand, only needs to be as large as the largest data transaction, and can maintain, for example, up to 128 kB of transaction data including the application and operating system variables. Preferably, the TAS PROM 95 and the form memory / menu 96 are updated by transferring data streams containing new instructions and / or forms and menus on a conventional data link 98 by means of the modulator 78, the card interface. magnetic 70, or by means of a removable memory card read by the memory card interface 89 as necessary. Alternatively, the additional fast memory elements can be added as additional applications, are added to the transaction registration device 12. The temporary transaction memory 97 can also be expanded to handle transactions of any type or size, including multimedia applications in which they are added video and / or audio data to data transactions.

Those skilled in the art will appreciate that the transaction registration device 12 can be coupled to a network docking station. The RF transceiver 90 can be used for wireless communications in such an environment. In addition, those with experience in the art will appreciate that the transaction registration device 12 can be implemented as a portable battery-operated device that is a link between a portable computer and a cell phone of the type illustrated by Paajanen et al. In U.S. Patent No. 5, 189,632, for example. In such a mode, a helmet could be provided, as well as a microphone and loudspeaker arrangement in removable top cover. Of course the liquid crystal display 20 would typically reduce in size up to, for example, 40 columns by 12 rows, and the touch screen 64 can be eliminated. However, most other options of the embodiment of Figures 5a and 5b would preferably remain so that the portable unit could be used on a desk as desired. The electronic components of the transaction registration device 12 would be illustrated otherwise in Figure 6 except for certain considerations of size and shape within the skill of those skilled in the art. 2. software As will be apparent from the following description, the data transaction assembler 1 8 does not use a conventional operating system to control the operation of a microprocessor 94. In contrast, the TAS PROM 95 stores simple fixed program algorithms. (Figures 7-1 0) operating in a kernel mode to navigate the user through the menus and forms provided from the form memory / menu 96 for particular applications and are the resulting data streams that control the microprocessor 94 at any point in time. In other words, the data streams from the TAS PROM 95 and the data streams from the shape / menu memory 96 reconfigure the microprocessor 94 into a special purpose processor for each application specified by the forms, the TAS PROM microcode. 95 and the parameter streams from the form memory / menu 96 therefore operate as a simple operating system for the microprocessor 94 for all applications and is the only code used to control the microprocessor 94 ( that is, no conventional operating system or application programs are provided). As a result of the microprocessor 94 it can be reconfigured in a new special purpose computer with each new form read from the form memory / menu 96 and such forms / menus can be added at any time by reading the appropriate data streams from a memory card or from a database server 28 or by adding an additional PROM. A specific implementation of the fixed program or TAS stored in TAS PROM 95 will be described below with respect to Figures 7-10. Thus, the TAS P ROM 95 contains control data (fixed program) for the microprocessor 94 and resides in each transaction register device 1 2 to generate a template for a data transaction from a data stream stored in the form memory / menu 96 (or received directly from a memory card or external database server) and from data entry by a user or retrieved from the external database or magnetic card, boot card and the like. The fixed program TAS and the planti l selected control the behavior of the microprocessor 94 by defining a table of menu options and / or database interfaces that are navigated by a user. As noted in the above, the user navigates through a series of selected menu selections another menu, a form, or a process. Once the data transaction for a desired application is completed, it is transmitted outside for "venti lation" within all its component parts for storage. In this form, the fixed program TAS from TAS PROM 95 and the menus and forms from the form memory / menu 96 of the invention replace a conventional operating system and the individual application programs. In fact, the invention allows the transaction registration device 1 2 to be completely independent of the operative system. The data transaction assembler 1 8 of the invention is connected by means of a predetermined protocol to the storage as instructions within the TAS P ROM 95 to a database server 28 and its associated database 30. As noted in the foregoing, the database server 28 associated with a particular transaction logging device 1 2 operates as a store of the data transactions created by the transaction logging device 12 and as an initializer. data for the transaction registration device 12 to complete the forms and provide the forms, menus, additional processes and the like. Since the operating system is independent of the operating system, there are no hardware or software limitations on the characteristics of the database server 28.

The setting of the parameter to conform the individual forms that are typically provided by the database server 28 as a data stream by means of the modulator and stored in the form memory / menu 96, while any transferred instructions are stored. in the TAS PROM 95. The link between the data transaction assembler 18 and its database server 28 is preferably provided by means of a specific dictionary program for each database server 28. This dictionary program knows the characteristics of each field of data for each data transaction and is used by the database server 28 to "ventilate" the data transactions received in its component parts. Preferably, upon power-up, the data transaction assembler 18 automatically identifies the user with a command of "Transfer Parameter Corridors" so that the user can load the memory / form (quick memory) 96 from an external source, the desired currents of menu and shape data for the desired application. The process of "transfer parameter" will then be initiated by dialing the external database server 28 which initiates the connection via the interface of the modulator 78. Once connected, the transaction controller 36 of the server database 28 will transmit the parameter stream solidated. The data transaction assembler 18 will load the received data stream into the form memory / menu 96, and upon termination, the indication "Executive Menu Ready" will be displayed on the display screen 20. The menu executive will automatically present the user for the desired menu section, form or process. At the initiation of the transaction registration mode by the user, the data transaction assembler 1 8 calls a set of panel parameters from the shape / menu memory 96 and s a shape on the display screen 20 Those forms are menus to navigate to particular forms or a form within which the data is recorded by the user. As will be explained below, the menus provide the functionality through the simple menu selection. The form on the display screen 20 is completed by the user by recording the appropriate data using the touch screen 64 or the optional keyboard 68. Alternatively, the solved data can be read from a memory card by means of the memory card interface 90, from a magnetic stripe or a smart card or card by means of the magnetic card interface 70 or the memory card interface 89, or the voice input by means of the recognition circuit. my voice 91 A request may be sent to the database server 28 associated with the transaction input device 1 2 for the data necessary to populate the various fields in the present form. The type of data record is requested from a subset of options presented to the user or by pressing a "?" or a "Request for More Information" button. This request will give the user several options to select, so that the data record that uses the keyboard 68, the touch screen 64, the start card by means of the magnetic card interface 70, the memory card by means of of the memory card interface 89, by voice announcing the item number in the menu by means of the speech recognition circuit 91 or by means of the modulator from a database 30. Thus, the data transaction created by the data transaction assembler 18 may or may not make use of the stored data to reduce the amount of data registration required of the user. When a data recording option is selected, the data transaction assembler 1 8 executes one of the following: another set of parameters is called and another form is n, the correction of the selection is verified and a set of options for selections is presented based on the interactions with the stored data, the data transaction completed and transferred by means of the modulator to the database server 28 for storage in the database 30 or, the data values are requested from the database 30 for incorporation into the temporary transaction memory 97. In a preferred embodiment, the selections from the menu are made by touching the appropriate place on the menu using the touch screen 64; by voice announcing the number of the menu item via microphone 62 and speech recognition circuit 91; using one of the function keys of the computer 66 to operate a cursor up the menu, another key to operate the cursor down the menu and a third key to make a selection in a conventional manner; or by means of using the keyboard 68 as a selection device. When the keyboard 68 is used, the keys of the keyboard can be used to control a cursor, with an "input" key that is used to make the selection; alternatively, the number of the selected article can be registered and press the "entry" key to make the selection. Once the selection is made, the appropriate form is extracted from the form memory / menu 96 as a data stream.

Alternatively, in addition to presenting a menu for selecting or terminating a form, the data transaction assembler 18 may present a menu selection to initiate a process such as the calculation of an interest rate that uses one or more fields in the form , finding a mean, searching for a name, or searching for records for a particular date. Those processes can be stored in the TAS PROM, the form memory / menu 96, in an offline server when they are started, or any other place when they can be loaded to the operative portion of the transaction registration device 12. In a preferred mode, the processes are generally initiated at the database server 28 by sending a data request to the database server 28, processing the data on the database server 28 and returning the response as a stream of data. data or report to the transaction log device 12. A process typically initiates a data chain that calls a process on an external machine. For example, the transaction registration device 12 can be used to transfer and store the infrared control signals of various devices using the infrared transceiver 80 (Figures 5 and 6). The shape of the control signals will depend on the storage of signal in an optional infrared microcu rce, which can be loaded by the data transaction assembler 18 or by an out-of-line device by means of the modulator or through the air using the RF transceiver 90 for the direct digital transfer in wireless form. In addition, in the case where the transaction registration device 1 2 is used in a medical office, for example, the process can be used to transmit a prescription to a pharmacy or to send an order to a house that uses it. Make pre-stored modulator numbers or you can call the doctor to call a list of phone calls you have to make during the day or a list of follow-up appointments for a particular date. In other words, the fixed program TAS can also "ventilate" the data transaction in all its auxiliary parts for transmission to numerous registers in one or more databases. A preferred embodiment of the fixed program TAS will now be described with respect to Figures 7-1 0. As noted above, the transaction assembly server (application) (TAS) is a data stream stored in the PROM. 95 together with the forms from the form memory / menu 96 creates an operating system operated in a simple manner which provides the necessary control data (fixed program) for the microprocessor 94 in such a way that the conventional operating system is not necessary. Figure 7 is a flow diagram of a menu-driven TAS in accordance with a preferred embodiment of the invention. As illustrated, the fixed program TAS initiates a step 100 and extracts an initial menu from the form memory / menu 96 in step 102. The initial menu is indicated within a few seconds after the start of the fixed program TAS after turning on of the system. The initial menu typically presents the options for transferring a stream of parameters from the database server 28 to allow the additional or printing functions of an executive menu. If the executive menu is selected, the executive menu is retrieved from the form memory / menu 96. The executive menu contains numerous user application options, namely, the selection of a form, another menu, a process or an automatic switchover to the telephone mode, one of which is selected in step 104. The data streams in form memory / menu 96 can be distinguished by type (form, menu, or process) by adding a code such as "F" for form, "M" for menu, and "P" for process and for number by adding a form, menu or process number at the beginning of the next data stream. These codes are recognized by the fixed program TAS and act accordingly.

If the option selected in step 104 is a form, the appropriate form (data stream for form Fxy) is extracted from the form memory / menu 96 in step 106, a temporary transaction memory 97 of equal length to the size of the register associated with the form Fxy is formed in the RAM, the form is stored in the temporary transaction memory 97 and a connection is made to the appropriate database server 28. The data stream for the selected form will consist of visual indications, print locations for the indication, data recording points, print locations for the start of the data record, the length of the data record and a code for the nature of the data record. This code may be numeric, alphanumeric, a cross-reference to the stored data or the previously recorded data, a formula for the internal creation for the data transaction assembler 18 of the result from the previous data records or an external data request, help, or reformulated values. The data stream registered within the fields of the form will not only indicate the location of the printing of the visual indication and the field for the data recording, but also the size of the field and storage, a starting point where the memory temporary transaction for the stored item and the data type: alphanumeric, numeric (floating point or integer), date and the like. If it is determined in step 1 08 that the request form is actually a menu (Mxy) a hidden set of codes that signal to the Fxy form that the selection will guide to be read and the control branches return to stage 1 04 for the selection of another menu or form. When a menu is selected, each item has a sequence number, its descriptor and a code by which "llama" is read (another menu, form or process). In other words, each selection has associated with it a series of article codes that branch to another form, menu or series of tests up to the recorded data. A menu also has a numeric code for each of the storage series and a special code that includes a security code for certain menu items, process codes or forms within the menu, or a pointer to the process code. A pointer can also be provided in the menu for processes that are executed offline (that is, in an associated database server 28). If a process (Pxy) is selected in step 1 04, the database server 28 is notified that something is being requested from the database 30 or that some data processing is requested. For example, the data transaction assembler 1 8 can send a request to the user "?" to the database server 28 so that the options can be returned to the data transaction assembler 1 8 for presentation to the user for selection. The process triggers an external processor of the database server 30 with a stream of parameters and the control is returned to the data transaction assembler 1 8 or the control is maintained until the process is completed, in which case a message back to the data transaction assembler 18. This message can be a report, selected data, a value resulting from a calculation and if milar. The processing of such verification and similar detectors can also be executed locally by means of the data transaction assembler 18. Once the desired form is selected for the user's application, the form is processed in step 110. according to the steps delineated in Figures 8-1 0. As a record is made in each field, it is automatically stored within the temporary memory area of the temporary transaction memory 97 in its assigned location and in the format determined. At any time, the complete form can be taken with the automatic return to the menu that called it or the form can be used for data registration. Once the form has been processed and transmitted to the appropriate database server 28, the database server connection is terminated and the user is presented in step 112 with the last menu from which the user made his selection. Alternatively, the executive menu will be called as a default menu. If the user indicates in step 114 that he wishes to continue to finish a new form, the control is derived to step 104 for the menu section and a new database server connection is made as appropriate. This process is repeated for each form. When additional selections are no longer desired, the fixed program TAS is terminated in step 116. Figure 8 is a flow chart illustrating the technique for processing a form (step 110) to create a data transaction according to the invention . As illustrated, the process of Figure 8 begins at step 118 and initializes a temporary transaction memory 97 at step 120 for storage of the data transaction as it is created. In other words, if a form for the required application exists, it moves from the form memory / menu 96 to the temporary transaction memory 97. If the required form is not present in the form memory / menu 96, a error message or a request can be sent to a database server 28 for a transfer of a data stream containing the parameters for the requested form. Preferably, the transactional temp memory 97 is at least as large as the largest data transaction and serves as an assembly area for the data transaction. Preferably the read and write temporary memories are formed to transmit and receive the temporary memories to / from the modulator interface 78 that are available. Of course, the temporary transaction memory 97 may be larger for this purpose. Once the temporary transaction memory 97 is initialized in step 120, the display screen 120 is disabled and the selected form is initialized to its first page in step 1 22. The first page is presented then to the display screen 20 in step 124. In step 126, the user completes the page on a field by means of the field base using any of the data recording techniques described above and the Field of Figures 9 and 1 0. The temporary transaction memory 97 collects the data associated with the form presented to the user on the display screen 20 and contains the appropriate locations for each separate data element. At the termination of the data transaction, the contents of the temporary transaction memory 97 are transferred to the appropriate database server (s) 28 by means of the modulator or by wireless means, preceded by a set of codes (field 44, Figure 2) which identifies the type of data transaction and followed by a chain of process identifiers for the server or data servers 28 to be used in its programs in the creation of additional transactions and in the storage of the data and all the auxiliary data transactions in the regular file format of the database 30 associated with the database servers 28. As a result, the data transaction created in the temporary transaction memory 97 has a ratio of one to many towards the data stored in the database 30. If the user decides to abort the processing of a form at any time (step 128), the process In this way, step 1 is determined if the user wishes to return a page (for a multiple form is pages) to correct a data record. If so, the control returns to step 1 24 for the presentation of the first page. If the user does not wish to examine or edit a previous page, it is determined in step 1 32 if the current form has another page that has not been exhi bted for termination by the user. If the form has more pages, the routine moves to the next page in stage 1 34 and stage 1 33 is determined if the movement to the next page was successful. If so, the control returns to step 124 for the presentation of the next page. Of course, the process of calling a subsequent page in one form or another until the termination of a form may depend on an automatic call of that page or sequence of form or skill for the jump sequence (ie page skip ) depending on a value in one or any of the fields that has been registered. In any case, if there are no more pages in the form or if the movement to the next page was not successful, the end of the form is marked with a code and the transaction is saved in stage 1 38 by sending the data transaction to appropriate database server 28 for storage in its associated database 30 and "ventilation" for storage of the data in other databases 40. If it is determined in step 140 that the saved was not successful due to an error of the modulator and the like, the control returns to step 122 and the process is repeated. If the data transaction was successfully saved, the shape processing routine is terminated in step 129 and the last used menu is presented (step 1 12). Optionally, the stored procedures within any form of data transaction (field 50, Figure 2) are executed at the appropriate time within the flow of the processing routine before it is completed. However, those processes may be postponed and executed by the database server 28 if necessary. Figures 9 (a) and 9 (b) illustrate a flow chart of a technique for terminating and editing fields in one way (step 126 of Figure 8). The field termination routine begins in step 142 and first determines in step 144 whether a request for valid page movement or abortion is pending. If so, the field termination routine is terminated in step 146. If, however, there is a request for page movement or pending abortion, the field data for the first field of the temporary transaction memory 97 are recorded in step 148. As noted above, these field data can be recorded by means of the key 68 or the touch screen 64, initiated by means of the magnetic card interface 70, read from a card of memory by means of the memory card interface 89, read on the modulator interface 78 from the database server 28 or designated by the voice register. The pre-editing processing of the field data is then executed in step 1 50. The pre-editing processing may include, for example, setting default values, executing calculations, establishing links to the data in other files, searching and write data to the files already linked for the present form, produce another form, execute special updates of the display screen 20, hide fields from the user's view and the like. Such pre-editing processing can also be used to determine whether modifications or actions in the present field can invalidate a record in another interrelated field. If this is the case, appropriate measures are taken to update all affected fields to avoid such problems by setting the appropriate default values. The field termination routine then verifies the field errors in step 1 52 based on the default and similar values established in step 1 50. If there are no field errors in step 152, it is determined in ia. stage 1 54 if the operator will allow the field to be edited in the absence of a field error. If so, or if a field error was found in step 1 52, the operator edits the field in step 1 56. If the operator's edit is deviated, the control proceeds directly to the subsequent editing processing in step 1 58, which essentially performs the same functions as the previous edition processing step 1 50 except that the data can be validated in a special way. The field is still verified again in step 160 for a field error. If the field error is in step 160, the control returns to step 144 to process the next field or exit, as appropriate. If no field error is found in step 160, step 162 is determined if the generic field validation routine of step 164 (Figure 10) will be omitted. If so, the control proceeds to step 166, where the field is verified once again for field error. However, if the generic field validations are desired, control passes to the routine of step 164 (Figure 10). If no field error is found in step 166, the field is saved for the temporary transaction memory 97 in step 168 and the updated field value is drawn on the display screen 20 in step 1 70. If the user it then wishes to verify a previous field in step 1 72, the control goes to a previous field in step 1 74 and the field termination routine is repeated for the previous field. However, if there is no previous field to be checked and if step 1 76 is determined that an additional field is present, the control goes to the next field in step 1 78 and the field termination routine is repeated for the next field. This process is repeated until the last field is completed and the routine ends in step 180. The control then returns to Figure 8 to process a different page of the form.

Each form can be processed in one or more modes in the input mode, described above, the data transaction is created and transmitted to the database server 28. However, in the edit mode, when registering the ID of a particular record, that record is read from an external database 30 or 40 within the temporary transaction memory 97 for editing. Preferably, a record of the edits is maintained to provide an audit trail. In the observation mode, to the I D register of a particular register, that register is read in a similar manner from an external database 30 or 40 in the temporary transaction memory but only for display. Finally, in the delete mode, a complete record can be deleted from the database 140 if the user has the appropriate security permission. Figure 10 illustrates how the fixed program TAS validates the fields of each data transaction. As shown, the field validation routine starts in step 182 and first determines in step 184 what type of field is present. If the present field is an alphanumeric field, the control goes to step 186 where the field omissions are processed. It is then determined in step 188 whether the user knows the allowed values for this field. If not, and the data is implemented in this field, an im- plantation table is searched in step 190. A "?" Can be used. by the operator to indicate that he does not know the allowed values for that field and wants to look for the implementation table. A list of possible values are called to match the data recorded so far. From that list, the operator can scroll through the list and select the value that the data record will complete. However, if the value is not in the list, a field error is generated in step 192 and the field validation routine is terminated in step 194. If the value is in the list, the control goes to step 200. On the other hand, if in step 188 it determines that the data are not added (implanted) within the present field, the control jumps to step 196, where it is determined whether the field type present is a field that establishes an event in which the present field (together with its form) can be linked to any record of any file or files (one or more) of any database for the purpose of data verification and / or extraction of data. If so, control goes to step 198, where the data from the present field and other previously gathered data are used to make the desired link. As in the aforementioned data implant step 188, the user registers a "?" to obtain the necessary information to make this link. If the data for the link is not found, a field message error is issued in step 192 and the field validation routine is terminated in step 194. However, if the data for the link is found, the field it is verified for the spaces in step 200 and the field error is issued in step 192 if there are blank spaces present in the field even though they are not allowed. If no blank spaces are found in the present field, or if the blanks are found even though they are allowed, the field validation routine is terminated in step 102. If step 184 is determined, the present field is a field numerically, the field is verified in step 204 to determine if the character set is valid. If so, the precision of the numbers is adjusted in step 206, as necessary, and the scale and scope of the numbers are verified in step 208 to ensure that the field records satisfy the boundary conditions (for example without division between zero). If the character set is not valid in step 204 or the scale or scope of the numbers is not valid in step 208 an error message is issued in step 210 and the data validation routine is terminated in step 212 Otherwise, the field validation routine is completed in step 214.

If it is determined in step 184 that the present field is a date / time field, the field is verified in step 216 to determine if the character set is valid. Otherwise, an error message is issued in step 210 and the field validation routine is terminated in step 212. Otherwise, a routine of the fixed program TAS verifies the data record / date in step 218 to determine if it has the correct format by executing scale verification and the like. If the data record / date does not have the correct format, a field error is issued in step 210 and the field validation routine is terminated in step 212. Otherwise it is determined in step 210 whether the field present contains a date Otherwise, the data validation routine is terminated in step 221. If so, the date is verified in step 222 to see if it contains a weekend and, if so, verifies in step 224 whether a weekend date is an acceptable response for this field. The calendar file to be verified is then determined in step 226 and if so, the calendar file is verified in step 228 to verify if the dates are valid (for example, not February 30 or the like). . Finally, it is determined in step 230 if a warning date has been exceeded and if so, a field error message is issued in step 210 before the field validation routine is terminated in step 212. another way, the field validation routine is terminated in step 221. Those of skill in the art will appreciate that, in order to maintain security, the fixed TAS program may also present a form of security for the registration of the user's password. The security form and the ID of the transaction registration device 12 is encoded and transmitted to the database server 28 associated with the particular data transaction assembler 18. The transaction driver 36 of the database server 28 will act then as the transaction controller for that data transaction assembler 18 and will verify the access keys and the like operation to ensure that the data security has not ramified. The data servers 28 can disable a data transaction assembler 18 if unauthorized use is intended. In this way, only the right person can observe each menu. Of course, a number different to security levels and different executive menus can be presented as desired, all under the control of the transaction controller 36.

C. Database Server 28 As noted above, the database server 28 acts as a vehicle to separate the data transactions created by the data transaction assembler 18 from the component parts thereof. they can be stored directly in one or more databases 30 and 40. In other words, the database server ventilates the initial data transaction in the data transactions for many different files to update the records in the files and the like. Also, the database server 28 can be virtual as well as real, it exists in an individual machine or in multiple machines, in whole or in part. Generally, the database server 28 handles any and all received data transactions, manipulates data in the data transactions, produces or initiates processes or reports requested by a data transaction and ventilates the data transactions received in all classes. of data transactions that were produced by the initial data transaction. The database server 28 can also update the values in the existing registers and can switch to a process for processing values in the registers as necessary. In this way, a single data transaction can define actions that cause multiple files to be updated. The database server 30 also handles the requests from the data transaction assembler 18 and processes them as necessary. Such requests may include requests for data entry / exit, data closure and data opening, reporting processes and requests for new forms or menus. Those skilled in the art will appreciate that the database server 28 maintains the one-to-many relationships that exist between the user and the system of the invention, the one-to-many presentations for the user and the files in the databases. data 30 and 40, and one-to-many data transactions and auxiliary records, updates and registrations as may be required for various computer files of numerous databases 40, the transaction registration device 12 and the servers of database 28. As noted above, the temporary transaction memory 97 collects the transaction data associated with the form presented to the user by means of the display screen 20. The temporary transaction memory 97 is the image of the data transaction with the appropriate locations for each separate data item. The contents of the temporary transaction memory 97 are transferred to the database server 28 by means of the interface of the modulator 78 or by means of the RF transceiver 90 preceded by a set of codes 44 (Figure 2) that identifies the type of transaction. followed by a chain of process identifiers for the database server 28 to be used in its programs, in the creation of additional data transactions and in the storage of the data and all the auxiliary transactions within the database 30 in the regular file format of the database 30. In other words, the database server 28 determines what type of action to take based on the type of data transaction received, "airs" a transaction data in a plurality of other data transactions in a plurality of other data transactions for transmission to other databases, as appropriate, and converts the data to your database. e associated data 30 in the appropriate file format. Of course, each database server 28 is different from another database server 28 since they handle different types of data transactions, have different operating system characteristics and different file conversions to do according to the file formats of its associated database 30. For example, the database server 28 can operate under an operating system such as Unix, Windows or DOS, where the operating system provides the database server 28 with links to the functions of the database. Normal physical body managed by an operating system.

Preferably, the database server 28 also operates with menus, forms, and the like in the same way as the data transaction assembler 18 except that it stores the data transactions in its associated databases 30 as transaction files. As noted, the purpose of the database server 28 is to process the data transaction from the data transaction assembler 18 and to ventilate the data transaction in all its related components for storage, to handle the storage of items from the data processing process. ventilation, to store the same data transaction for reference purposes, and to act as an information provider for the data transaction assembler 18 in response to the requests during creation during the data transaction and during the transfer of parameters for menus and forms to the data transaction assembler 18. If desired, the database server 28 may also provide information to the data transaction assembler 18 and after a data transaction has been received or may initiate a process that leads to the supply of a report, data, or menus to the assembler of tr Data acquisition 18. In addition, the database server 28 and the data transaction assembler 18 can receive on the same machine as long as the database server operating system recognizes the fixed program TAS or the fixed program. TAS is modified for use with the database server operating system 28.

D. Applications of the I nvention As determined in the foregoing, the present invention includes a transaction device point that presents a menu to a user from which an option is selected. A form adapted for the selected option appears to guide the user through the data record. The full details of the data transaction are captured as data that is recorded by the user. The interaction of the modulator with a central database or user database allows the interaction to help and verify the recorded data. The terminal transaction is then transmitted to the central or user database for further processing and storage. The data input can also be provided by means of a smart card or boot card, based on the data received from any accessible database through the modulator interface or other known methods.

A data transaction system of this type can be used for many applications. For example, in a first currently preferred application, the transaction registration device 12 is located in a medical office for the registration of patient data. In this application, a startup card identifies the patient, a smart card identifies the doctor, and the modulator connection allows the complete claim transaction to be recorded and transmitted to the insurance companies for processing. Patient records can also be updated automatically and the prescriptions created, delivered to the patient, transmitted to the pharmacy and transmitted to the payer and the patient's registry. Patient instructions such as special diets, exercises, treatments, appointments and the like can be printed from the data transaction form on the physician's central computer. In addition, a video image or pattern provided by means of the video input 74 and compressed by the data compression circuit 75 allows an image of a medical condition such as a rash to be added to the data transaction (in the field). of various processing 50 of Figure 2) for transmission with the patient's name, the date, a description of the patient's symptoms and the like. Similarly, a recorded heart rate may be added at the end of the data transaction for transmission with patient data. The data transaction recording system of the invention has numerous domestic uses. In a preferred domestic use, the transaction registration device is used to execute banking transactions from home. In this case, the forms would be made available by the bank for different types of banking transactions. Those forms would be transferred to the user's home transaction log device and used in the creation and transmission of data transactions to the bank's computer for off-line processing. As another example, the user can dial up to 900 numbers to obtain an interface to the central database that will transfer the codes in the TAS PROM 95 or the form memory / menu 96 that allows the generation of infrared signals at certain frequencies. The user only needs to specify the type, make and model of any electronic device that will be controlled to obtain the desired code. Then to operate any electronic device in the home, the user would be guided by the menu indications. The transaction registration device 12 will emit an infrared signal by means of the infrared transceiver 80 to operate the electronic device, initiate a call by means of the modulator for a transmission program, or initiate the time requests for the video recording, the ignition of video recording or power off and simile. For other domestic uses, the transaction recording device 12 can also initiate, by means of menu indications, the sequences for switching on and off various domestic devices including alarm systems, coffee machines and the like. In this mode, the transaction registration device 1 2 may receive an RF or infrared signal that indicates that a burglary or fire alarm has been triggered and a form of calling the police or fire department called. as appropriate. A call to the transaction registration device 1 2 can be used to turn off the burglary or fire alarm by changing a field in a way that instructs the infrared transceiver 80 or the RF 90 transceiver to send an appropriate control signal to the alarm device . This feature can also be made from the telephone of a car by means of the remote initialization of the execution of the form of this function. The transaction registration device 12 can also control all domestic telephone usage as well as control of the answering machine and maintain a telephone transaction log. The user can also pay the domestic bills by completing an appropriate form and transmitting the form to a payer such as a credit card company, a bank and if my home. In summary, the transaction registration device will allow the owner to connect to a remote database without possessing a conventional computer system with an operating system and the like. For personal applications, the transaction registration device 12 can not be used to initiate a facsimile transmission to provide telephone numbers with automatic dialing to the selection, to provide expense accounts, personal hours, to maintain the region of taxes and the like and to provide direct access to travel information. For example, the database server 28 may be an airline reservation system. In this application, the data transaction assembler 1 8 marks the modulator of the airline reservation system when the user requests the registration of data within the form of airline reservations available in the user's transaction recording device. The data transaction device 18 modulates the database server 28, and the operating system of the database server 28 selects the interface programs for the airline reservation system. The interface program calls the database servers 38 of the airlines, retrieves the appropriate menu from the database 40, and modulates the menu to the data transaction assembler 18. The data transaction assembler 18 then displays the airline reservation menu on the display screen 20 for completion and Transmission to the airline database reservation server for processing. The starter card can be used to provide the credit card payment information and can be updated by allowing the data transaction assembler 18 to write to the starter card. The user can also access the frequent flyer club and mileage data, special offers in hotels, cruises and other trips and the like. In another domestic (or commercial) use the transaction registration device 12 can be used to eliminate conventional telephone greetings by allowing the caller's transaction log device 12 to read in a set of menus visible from the sender's menu. Call start voice so that the call party can select the desired options using a visible menu instead of a voice menu. In other words, the caller will not have to wait through the sequence of voicemail options before making a selection and could make the desired selection immediately from their own screen. This would be achieved by selecting a process from the menu of the transaction log device 12 that would create a "visible" menu. When such a process is selected, the electronic components of the telephone 14 or the modulator interface 78 make a telephone connection to a remote telephone sending system. Once the connection is made, the data transaction assembler 18 sends a data request from a visual representation of the telephone mail menu of the remote telephone delivery system via the telephone connection to the remote telephone sending system. A data stream containing the visual representation of the telephone sending menu from the remote telephone sending system is returned by means of the telephone connection and stored in the form / menu memory 96 and presented to a display screen 20 of the device. transaction log 12 for selection using the techniques described herein. When the menu items are selected from the "visible" voice sending menu, the data transaction assembler 18 creates a data transaction that indicates which menu item was selected and sends the data transaction to the telephone delivery system remote through the telephone connection. Based on the menu selection, the remote telephone sending system returns a stream of data containing a visual representation of the following telephone delivery menu via the telephone connection for storage in form memory / menu 96 and displays it on the display screen 20. This process is repeated until the calling party is requested to leave a message or the called party is located. Such a system would be particularly useful for interacting with voice delivery systems such as those of government offices, where numerous selection options are presented. Those skilled in the art will appreciate that the invention is unique in virtue of its ability to generate applications to the forms so that the code to be written to implement a particular function is not necessary. However, if the code is necessary or if the multimedia data is part of a data transaction, it may be attached to a form that is stored as a stream of parameters in a data stream. Also, although the transaction registration device 12 has been described as a computing station, it can be used in conjunction with an optional off-line storage device such as a self-contained work station and a database-based unit independent of the systems traditional operatives.

The transaction registration device 12 can also be used with an additional optional plug in a network server or as a user interface in a network docking station. Those skilled in the art will also appreciate that the foregoing has established the presently preferred embodiments of the invention although numerous alternative embodiments are possible without departing from the teachings and novel advantages of the invention. Accordingly, all such modifications are intended to be included within the scope of the appended claims.

Claims (14)

1. REVIVALATION IS 1 . A System for recording transaction data within a database, characterized in that it comprises: a data entry device; a screen; a data transaction terminal presenting to the screen a template including a plurality of visual indications adapted to a particular type of transaction to produce data entry into the data entry device by a user and format the template and the input data from the user within a data transaction for transmission; and a database server associated with the database receiving the data transaction, created from the data transaction, depending on the particular transaction type by at least one additional data transaction containing data for a particular record in the database and, stored in at least one additional data transaction in the particular registry.
2. 2. The system according to claim 1, characterized in that it comprises a plurality of databases, in which the database server also creates from the data transaction, depending on the particular transaction type, at least one transaction of data. auxiliary data that contains data for a particular record in one of the plurality of databases in addition to the database and stores at least one auxiliary data transaction in the particular record.
3. 3. The system according to claim 2, characterized in that the data transaction terminal includes means for sending a data request to the database server, the database server that accesses the data corresponding to the data request. in at least one of the databases and that returns a data response to the data request, a list of options for the section by the user, a value calculated from the data contained in the data request and a report of data.
4. 4. The system according to claim 1, characterized in that the data transaction terminal comprises a microprocessor, a transaction assembly server (TAS) for providing data control to the microprocessor, a memory for storing a plurality of templates including the template and a temporary transaction memory for storing the template and data entry within the data entry device by the user in response to the visual indications until the data transaction is completed for transmission to the database server .
5. 5. The system according to claim 4, characterized in that the control data provided to the microprocessor by the TAS comprises data streams in the template and data streams from the TAS.
6. 6. The system according to claim 4, characterized in that the data transaction terminal further comprises a modulator, a telephone and two telephone line connections, one for connecting the telephone to a telephone network, and one for providing a modulator connection between the modulator, the TAS and the database server.
7. 7. The system according to claim 6, characterized in that the data transaction terminal comprises a mode switch for selecting a mode of the telephone in which the data transaction terminal operates exclusively from the TAS or a transaction registration mode in the which the TAS operates exclusively from the telephone.
8. 8. The system according to claim 4, characterized in that the data transaction terminal further comprises a modulator, a telephone, a telephone line connection and means for selectively connecting the telephone to the telephone network and the TAS to the server. database through the telephone line connection.
9. 9. The system according to claim 8, characterized in that the selective connection means comprise a switch mode for selecting a telephone mode in which the data transaction terminal operates from the TAS excise or a transaction registration mode in the that the TAS operates exclusively on the telephone.
10. 10. The system in accordance with the claim 1, characterized in that the database server comprises a modulator, a data transaction row to store data transactions received from the data transaction terminal, and a transaction controller that processes the received data transactions to extract the data transactions. physical relationships of data from data transactions with records in the database. eleven .
11. The system according to claim 1, characterized in that the data transaction terminal includes a memory that stores a plurality of menus and templates for presentation to the user, the user who selects the template from one of the menus using the data entry device.
12. The system according to claim 1, characterized in that the menu provides the user with an option to select the plant, another menu and a process to process data in a data transaction.
13. 13. The system according to claim 12, characterized in that when the user selects the process of a menu, the database server transfers the data stream to the memory of the data transaction terminal to update the menus and the data. templates according to the types of transaction requested by the user.
14. 14. The system according to claim 1 2, characterized in that, when the user selects the process from a menu, the database server transfers the data streams to the memory of the data transaction terminal containing the data. control data to implement the functions designated by the selected process.