This continuation-in-part application claims the benefit of the utility application entitled “SYSTEM AND METHOD FOR COLLECTING DATA FROM DATA SOURCES USING DATA COLLECTION TOOLS” (Ser. No. 10/989,989) filed on Nov. 16, 2004, which is hereby incorporated by reference in its entirely.
This invention relates generally to the field of data collection, and more specifically to a new and useful system and method for collecting data from data sources using data collection tools that function through either an automated interface or a human operator.
Specific information relevant to the health of a patient may be stored in files, records, and other data sources located in many different medical facilities such as physician offices, hospitals, skilled nursing facilities, medical laboratories, free standing radiology clinics and other health care providers. Patient information is often required by organizations that are authorized to receive such information, such as medical service provider plans, governmental agencies, including Medicare and Medicaid, and other authorized organizations. The specific information may be found in many locations, on various media, in numerous formats and amid a considerable amount of non-relevant data. For example, data collection may take the form of extracting data from electronic or paper files and records or collecting data visually by inspection during an on-site audit of a medical facility. Selecting, collecting, abstracting, and organizing the relevant data into a format that is readily analyzed by the resources of a medical service provider plan or other authorized organization is a complex and time consuming task. Thus, authorized organizations have a need for new and efficient systems and methods for selecting, collecting, abstracting and organizing specific medical information from the files of their participating medical and healthcare service providers.
In one aspect of the invention, a system is provided for collecting data from a data source and creating data records that includes a database containing tools for collecting the data from the data sources and creating data records. A tool selector in communication with the database is also provided for selecting a tool from the database, and a tool processor for executing the tool. A communication channel communicates between the database and the tool processor enabling a tool to be selected by a tool selector program running on an application processor and transmitted to the tool processor for use in creating a data record, which is transmitted to the database via the communication channel.
In another aspect of the invention, a method is described in which a tool is selected from a database and transmitted from the database to a tool processor by way of a communication channel for use by either a human operator or by an application interface program to facilitate the collection of data from a data source and the creation of a data record, which is transmitted from the tool processor to the database via the communication channel.
BRIEF DESCRIPTION OF THE DRAWINGS
These and other aspects and advantages of the present invention will become apparent upon reading the following detailed description of the invention in combination with the accompanying drawings.
FIG. 1 is a block diagram showing the architecture and functional entities of a first embodiment of the invention having a human operator.
FIG. 2 is a flow chart showing the process flow of the first embodiment of the invention.
FIG. 3 is a flow chart showing the process flow for building a tool set.
FIG. 4 is a block diagram showing the architecture and functional entities of a second embodiment of the invention in which the human operator is replaced by an interface application program.
DESCRIPTION OF THE PREFERRED EMBODIMENT
FIG. 5 is a flow chart showing the process flow of an alternative embodiment of the invention in which the human operator has been replaced by an interface application program that directly monitors a data input channel.
The following description of the preferred embodiment of the invention is not intended to limit the invention to this preferred embodiment, but rather to enable any person skilled in the art of data collection to make and use this invention.
As shown in FIG. 1, the first preferred embodiment of the system 10 for collecting data from a data source includes a server 20 linked to a communication system 30. The server 20 contains a database 22 in communication with an application processor 27. The application processor 27 has a tool selector functionality 28 for selecting tools appropriate for a given data collection assignment and an authentication functionality 29 to identify particular operators 60 who operate or interface with the tool processors 50. The authentication functionality 29 enables the particular data collection assignments that have been assigned to the operators 60 to be correlated with the correct operator 60.
The application processor 27 may be resident on the same physical machine or server 20 as the database 22 or could be physically separated from the database 22 and residing on a separate machine. The database 22 contains a data collection 24 and a tool collection 23. The tool collection 23 contains at least one data tool 25, but could contain a suite of diverse data tools 25 for collecting data, each data tool 25 being linked or associated with a data set 26. Each data set 26 contains parameters and other information and data that are useful in the execution of the associated or linked data tool 25.
The communication system 30 contains a tool transmitter 32 for transmitting the data tools 25 and data sets 26 to the tool processor 50 and a data receiver 34 for receiving data records created by the operator 60 based on information contained in the source files 70. The data records are stored in the data collection 24 residing on the server 20. The communication system 30 allows a remote server 27 to communicate through a communication channel 40 with the tool processor 50. The tool processor 50 includes a data store 52, in which the data records 56 and data tools 58 are stored. Also included within the tool processor 50 is a tool parsing engine 54 for parsing and executing instructions that form the code or script of the data tools 25 and a local communication system 55 for establishing communication between the operator 60 and the application processor 27 through the communication channel 40. The communication channel 40 and the other links between the various components of the system 10 may be dedicated facilities, a Wide Area Network (WAN), a Virtual Private Network (VPN), a local area network, the internet or any number of other land based, terrestrial based or wireless communication facilities, networks or resources.
The tool processor 50 is utilized by an operator 60 that has access to source files 70. The tool processor 50 may be a PDA, workstation, laptop computer, desktop computer or any other of various platforms containing processing units capable of executing the data tool 25 to create data records 56. In the preferred embodiment depicted in FIG. 1, the operator 60 is a human agent who may be assigned to read through source files 70 that are paper and/or electronic files in a physician's office, hospital, skilled nursing facility, medical laboratory, free standing radiology clinic or other health care provider at any other location or facility of an entity that participates in the medical service provider plan. Alternatively, the system 10 may be configured to function in a more automated way by replacing the human operator 60 with an automated interface application 61, as described below in reference to FIGS. 4 and 5.
The specific information or data that the operator 60 is assigned to collect may be found in source files 70 that are of various media and in numerous formats. The sources files 70 from which the operator 60 may extract the information or data may be electronic or paper files and records or the operator may collect the data or information source files 70 that are the physical locations or facilities themselves by inspecting or auditing the premises.
Referring now to FIG. 2, the method 100 for collecting data from a data source file 70 begins in step 102 when the operator 60 logs onto an application program containing functionality to authenticate the identity of the operator 60. The application program may reside on the tool processor 50 or on the application processor 27 of a remote server 20, or a combination of both of these configurations with some functions of the application program residing locally on the tool processor 50 and some functions of the application program residing remotely on a server 20. The application program authenticates the operator in step 104 allowing the operator in step 106 to request the appropriate tools for a particular data collection assignment. In step 108 the application program fetches the assignment for the operator 60 and begins in step 110 to build a tool set that will enable the operator 60 to collect the information or data of interest to the organization that has been authorized to receive the patient's information, such as a medical service provider plan.
In step 112, the tool set is transmitted by the tool transmitter 32 within communication system 30 from the tool collection 23 within the database 22 to the tool processor 50 via the communication channel 40. The tool set is stored in the tool store 58 within the data store 52 resident on the tool processor 50. The tools are executed by the tool parsing engine 54 within the tool processor 50 in step 114 enabling the operator 60 create data records 56 in step 118 from the relevant data collected from the source files 70. The data records 56 are stored within the data store 52 of tool processor 50. The record store 56 and the tool store 58 resident on tool processor 50 may be contained with the same or different devices.
In step 120, the data record or records 56 are transmitted from the tool processor 50 through its communication system 55 via the communication channel 40 to the data receiver 34 to a remote communication system 30 that provides a communication interface for the server 20. The data records 56 are stored in the data collection 24 residing on the server 20.
The process of building the tool set for the operator's data collection assignment in step 110 is outlined in more detail in FIG. 3 beginning in step 200 in which the application program identifies a tool 25 that is needed for the operator 60 to perform his or her data collection assignment. The identity of the operator 60 may be used to determine the data collection assignment and thus serve as the basis for selecting the component tools that will comprise a tool set, although other criteria such as date, time, location and/or other relevant factors may also be used by the application program in determining the tools that will comprise the tool set to compete any particular data collection assignment. The application program fetches the tool 25 script in step 202 and the data set 26 that is linked or associated with the identified tool 25 script. In step 204 the fetched tool 25 script and data set 26 are added to a tool set for the operator's 60 assignment.
In step 206, the application program decides whether or not all of the tools 25 and linked or associated data sets 26 that are required for the operator 60 to compete the assignment have been accumulated in the tool set and returns to step 200 if all of the tools 25 and linked or associated data sets 26 have not been accumulated to complete the assignment. If all of the tools 25 and linked or associated data sets 26 required by the operator to complete the assignment have been accumulated the process continues to step 112 in which the tool set is transmitted via the communication channel 40 to the communication system 55 in the tool processor 50 as described above.
Referring now to FIG. 4, a second preferred embodiment of the invention is depicted in which the human operator 60 has been replaced in the system 10 by an interface application program 61 running on the tool processor 50 as the interface between the tool processor 50 and the sources files 70. Like the human operator 60 in the first preferred embodiment described above, the interface application 61 searches through the source files 70 stored on a client database 72 to extract data in accordance with directions in the tool set and data set. For example, the tools set may contain instructions to collect a patient's birth date, the date of an office visit, or particular codes that indicate diagnoses or events such as doctor office or hospital visits. The interface application 61 may also be resident on the same machine as the data the tool selector function 28, the authentication function 29 and/or the database 22, or could physically reside on a separate machine that is interconnected with the system 10.
The interface application 61 can be configured such that some functions reside locally on the tool processor 50 and some functions reside remotely on a server 20. The interface application program 61 may also be part of a larger data management system that has a data collection function. The data management system can be configured to reside centrally either on the tool processor 50 or a remote server 20. The data management system can also be a distributed architecture system with some functions residing on the tool processor 50 and some functions residing remotely on a server 20. Alternatively, the interface application 61 can be configured to monitor one or more data input channels 76 between an end user 78 and an electronic medical records system 74 to extract data in real time and deliver information in smaller data packets. The interface application 61 transmits a data packet when a particular detail specified by the data set and data tools is recognized on the data input channel 76. The data tool and data set may request information related to a particular code 9999, for example, which may represent that a certain lab test has been ordered by a doctor. The interface application 61 can be configured to continuously monitor for the code 9999 and extract in real-time the fact that this test has been ordered at the same time that doctor's assistant inputs this data into the computer resident at the doctor's office. In this embodiment, the interface application 61 can be resident on a tool processor 50, a remote server 20 or on a server or workstation connected directly to a client's network with a communication channel back to the system 10.
The interface application 61 supplies the search, recognition and extraction skills that are necessary to generate the data records 56 that are supplied by the human operator 60 in the first preferred embodiment depicted in FIG. 1. The interface application 61 is a computer program that may incorporate expert systems, artificial intelligence and/or other embedded intelligence technologies for the purpose of supplying or approximating the human operator's 60 expertise, and may be written in software languages that afford learning capabilities such as 4GL. The interface application 61 may utilize any interface protocol, such as by way of example, HL7, ODBC, XML or a proprietary interface, suitable to interact with the source files 70. The interface application 61 may interact with the source files 70 through one or more computers, devices, and/or interfaces in any manner known in the art, including the Internet, intranets and through various server protocols and devices. The data may be extracted and transmitted from the device on which the source files 70 are resident and received by the interface application 61 on the remote server 20 or on the tool processor 50 in any number of ways, including, but not limited to, any data or signal discernable by the application interface 61 as a data record 56, such as a message in any format of any computer protocol.
The second preferred embodiment of the invention described above with reference to FIG. 4 for collecting data from data source files 70 utilizing the interface application 61 instead of a human operator 60 performs the method set forth in FIGS. 2 and 3 in a manner similar to collection by a human operator. The method begins in step 102 when the interface application 61 logs onto the system 100. The interface application 61 may logon to application program in response to polling that occurs at predetermined intervals established during initialization of the interface application 61.
In step 104, the application authenticates the interface application 61 based on information contained in a transmission from the interface application 61. The authentication function 29 may reside of the tool processor 50 or on a remote server 20. In step 106, the interface application 61 requests the appropriate tools for a particular data collection assignment. In step 108, the application program fetches the assignment for the application interface 61 and begins in step 110 to build a tool set in the manner set forth in FIG. 3 and described above that enables the interface application 61 to collect the information or data of interest. Once the tool set has been assembled, the tool set is sent in step 112 to the tool processor 50 and tool parsing engine 54 resident on the tool processor 50 begins in step 114 executing or parsing the script of each of the tools 25 in the tool set to collect the relevant data from the source files 70.
As the interface application 61 collects the data in step 116 from the source files 70 under the control of the tool processor 50, a data record 56 is created in step 118 and stored in the data store 52 of the tool processor 50. Once all of the instructions in the tool set have been executed and the data is completely collected in step 118 the tool processor 50 then uploads data records 56 in step 120 from the local data store 52 to the data receiver 34 and on to the data collection 24 in the database 22. Alternatively, the submission of data to the database 22 could occur in real-time as it is being collected from the source files 70 through the application interface 61. It should be noted that the functions of the interface application 61 in this process 100 could also be performed remotely by a data application program resident on a remote server 20.
Referring now to FIG. 5, the second alternative method 300 for collecting data from a data source file 70 without the aid of a human operator 60 begins in step 302 as the tools and data are loaded onto the tool processor 50 and begin to execute. In step 304, the application interface monitors traffic 76 on the data input channel 76 between an end user 78 and a medical records system 74 or other type of data storage system. In step 306, the sampled data is compared to the particular criteria requested by the tool set and data set. If the sampled data does not meet the particular criteria specified by the tool set and data set, the process returns to step 304 and continues monitoring the data input line 76. If the sampled data in step 306 does meet a particular criterion specified in the tool set and data set, the data is collected in step 308. A data record is created in step 310 and the collected data transmitted to the data base 22 in step 312.
The foregoing description of the preferred embodiment is not intended to limit the invention to this preferred embodiment, but rather to enable any person skilled in the art of data collection to make and use this invention. As any person skilled in the art of data collection will recognize from the foregoing description and from the figures and claims, modifications and changes can be made to this preferred embodiment of the invention without departing from the scope of this invention defined in the following claims.