|Publication number||US9268827 B2|
|Application number||US 12/231,176|
|Publication date||23 Feb 2016|
|Filing date||29 Aug 2008|
|Priority date||16 Nov 2004|
|Also published as||US20060106789, US20090006483|
|Publication number||12231176, 231176, US 9268827 B2, US 9268827B2, US-B2-9268827, US9268827 B2, US9268827B2|
|Inventors||Ronald E. Fernandez|
|Original Assignee||Unival, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (16), Non-Patent Citations (1), Classifications (5), Legal Events (1)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a divisional application that claims the benefit of U.S. Ser. No. 11/099,878 filed on Apr. 6, 2005, which is a continuation-in-part application that 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, both of which are hereby incorporated by reference in their 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.
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.
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
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
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
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
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
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
The second preferred embodiment of the invention described above with reference to
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
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
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.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5475742||5 Apr 1993||12 Dec 1995||Euro Cp||System for remote data collection, process for operating this system and associated collection device|
|US5745681||11 Jan 1996||28 Apr 1998||Sun Microsystems, Inc.||Stateless shopping cart for the web|
|US5924074 *||27 Sep 1996||13 Jul 1999||Azron Incorporated||Electronic medical records system|
|US5950010 *||25 Nov 1996||7 Sep 1999||J.D. Edwards World Source Co.||System and method for customized application package building and installation|
|US6006230||29 Jan 1997||21 Dec 1999||Sybase, Inc.||Database application development system with improved methods for distributing and executing objects across multiple tiers|
|US6163276||17 May 1999||19 Dec 2000||Cellnet Data Systems, Inc.||System for remote data collection|
|US6460041||25 Apr 2001||1 Oct 2002||Inshift Technologies, Inc.||Browser-based database-access engine apparatus and method|
|US6691116||31 Oct 2001||10 Feb 2004||Storability, Inc.||Method and system for data collection from remote sources|
|US6751650||29 Jun 2000||15 Jun 2004||Journyx, Inc.||Method and apparatus for monitoring contractor performance|
|US20010016822 *||13 Dec 2000||23 Aug 2001||Luc Bessette||Method and apparatus for the management of data files|
|US20020077849 *||18 Dec 2000||20 Jun 2002||Baruch Howard M.||System and method for improving efficiency of health care|
|US20020128866 *||27 Apr 2001||12 Sep 2002||Goetzke Gary A.||Chronic pain patient care plan|
|US20020194314||17 May 2002||19 Dec 2002||Alexander Kouznetsov||Application generator|
|US20030014282 *||9 Aug 2001||16 Jan 2003||Alan Haaksma||Method and system for creating a conveniently accessible portable medical history|
|US20040153338||28 Mar 2003||5 Aug 2004||Back Kim||Medical information system|
|US20060106787||16 Nov 2004||18 May 2006||Unival, Inc.||System and method for collecting data from data sources using data collection tools|
|1||Notice of Allowance for U.S. Appl. No. 10/989,989 mailed Dec. 12, 2008.|
|International Classification||G06F17/30, G06F19/00|
|Cooperative Classification||G06F17/30563, G06F17/30557, G06F19/322|
|17 Dec 2015||AS||Assignment|
Owner name: UNIVAL, INC., MICHIGAN
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FERNANDEZ, RONALD E.;REEL/FRAME:037317/0205
Effective date: 20050401