English:
[0001] The present invention generally relates to electronic document management systems, which are used to manage electronic image files. In particular, the present invention is directed to a system and method for generating tasks related to electronic image files.
[0002] In order to manage the volume of data in integrated delivery networks (IDN), healthcare provider organizations have turned to sophisticated data management systems or applications. Typically, these systems include modules for maintaining or improving the quality of data. By improving the quality of data, i.e., correcting errors and/or omissions in data, the revenue cycle for patient billing may be reduced and the overall service to customers may be improved. Generally, for each healthcare service provider in the IDN, a task list is developed and populated with tasks for improving data specific to that particular provider. A user such as a data clerk is often responsible for working the tasks that populate the task lists.
[0003] For large IDNs, the tasks that populate the task lists may include tasks input by users of the system, tasks input by third party systems, and tasks generated by the data management system itself. Prior art data management systems typically are not capable of integrating tasks that specifically relate to electronic image files, e.g., image files generated by scanning, created using graphics software, or imported from other applications, etc. An example of a task that specifically relates to an electronic image file is a task that is generated when an insurance card is scanned. Typically, a patient insurance card is scanned when a patient checks in for an appointment at a hospital, clinic or doctor's office. However, the electronic image file that contains the insurance card information is typically needed by billers and registration personnel to verify coverage - not usually the person checking in the patient. Prior art data management systems are not capable of generating a task, which typically includes instructions or workflow for working the task and a link to the particular electronic image file. For example, in the case of a scanned insurance card, prior art systems are not capable of generating a task instructing the appropriate personnel to verify the information contained in the patient insurance card and providing a link to the electronic image file of the insurance card.
[0004] In prior art systems, manual processes are typically utilized for notifying the correct personnel when electronic image files become available. Unfortunately, manual processes typically break down and may result in electronic image files not being properly indexed or indexed in a timely manner. The failure to provide the information contained in the electronic image files to the appropriate input points within an organization in a timely manner often results in billing delays, payment delays, and an overall increase in the revenue cycle time.
[0005] The healthcare industry is but one example of where the system and method for generating tasks related to electronic image files of the present invention may be utilized. As those skilled in the art are aware, both electronic document managers and task engines are used in myriad applications and industries.
[0007] Another aspect of the present invention is a method of generating one or more tasks related to one or more electronic image files stored in an electronic document manager. The method includes the following steps: creating one or more electronic image file events related to the electronic image files; providing a predetermined set of rules, each of the rules having at least one predetermined condition; comparing the one or more electronic image file events to the predetermined set of rules; and creating one or more tasks if the one or more electronic image file events meets the at least one predetermined condition.
[0008] Still another aspect of the present invention is a system for generating one or more tasks related to one or more electronic image files. The system includes an electronic document management module including an electronic image file database for storing the electronic image files and an electronic image file event generator submodule for generating electronic image file events related to the electronic image files, and a task engine module in communication with the electronic document management module for generating tasks related to the electronic image files based on the contents of the electronic image file events. The task engine module includes a task generation submodule including an event manager for storing the electronic image file events and a ruleset manager"including at least one predetermined set of rules. Each of the rules has at least one predetermined condition. The task engine module also includes a task generation manager for comparing the electronic image file events to the at least one predetermined set of rules and generating one or more tasks if the electronic image file events meet the at least one predetermined condition.
[0009] Yet another aspect of the present invention is a computer readable medium in which is contained a program generating one or more tasks related to one or more electronic image files stored in an electronic document manager, the program comprising instructions that, when executed by a computer, perform the following steps: creating one or more electronic image file events related to the electronic image files; providing a predetermined set of rules, each of the rules having at least one predetermined condition; comparing the one or more electronic image file events to the predetermined set of rules; and creating one or more tasks if the one or more electronic image file events meets the at least one predetermined condition.
[0011] Referring now to the drawings in which like reference numerals indicate like parts, and in particular to FIG. 1, one aspect of the present invention is a system 20 for generating tasks related to electronic image files. System 20 includes an electronic document manager (EDM) 22 that is in communication with a task engine 24. As one aspect of its functionality, EDM 22 receives electronic image file (EIF) batches 26 generated by a scanning device application 28 and scanning device 30 and/or EIF batches 32 generated by a third-party such as an electronic document clearinghouse. Generally, EIF batches 26 and 32 include one or more electronic image files in a standard EIF format, e.g., jpg, tiff, bmp, gif, pdf, png, xpm. Examples of electronic image files include patient insurance cards, claims forms, billing invoices, clinical records, and test records such as x-rays. As discussed further below, EDM 22 shares information derived from EIF batches 26 and 32 with task engine 24. In turn, task engine 24 generates EIF- related tasks or tasks related to the one or more electronic image files included in batches 26 and 32.
[0012] FIG. 1 illustrates system 20 as being implemented in an appropriate computing' environment. Although not required, the invention will be described generally. in terms of computer-executable instructions, typically included in program modules, that are executed by a conventional, general purpose, digital computer. Typically, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks. The invention may be practiced with a variety of computer system configurations, including networked client-server computing systems, hand-held devices, programmable consumer electronics, minicomputers, mainframe computers, and the like. The invention will typically, but not necessarily, be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network, e.g., a LAN, WAN or an Internet-based network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
[0013] It is contemplated that system 20 of the present invention will operate in a networked computing environment including a personal computer 40 and an Internet server 42. Personal computer 40 may include a computer central processing unit (CPU) 44, a computer memory 46, and input/output devices 48. Input/output devices 48 typically include a storage device 50, such as a hard disk drive, a keyboard 52, a pointing device 54, i.e., a mouse, and a display device 56, such as a monitor.
[0014] Internet server 42 may include a server memory 58 and an Internet server CPU 60. Generally, system 20 includes one or more computer programs 62 that reside in server memory 58 of Internet server 42. Of course, computer programs 62 may reside in the memory of a local or wide area network server or in the memory of an individual desktop computer system.
[0015] In one implementation, system 20 may be accessed via a thin client access program 64 that resides in computer memory 46 of computer system 40. In such a configuration, computer programs 62 may be executed on either or both Internet server CPU 60 and computer CPU 44.
[0016] Referring now to FIG. 2, in one embodiment, EDM 22 may include a user interface 70, a document manager submodule 72, and an EIF event generator 74. User interface 70 allows a user to interact with both document manager submodule 72 and EIF event generator 74. As discussed further below, document manager submodule 72 may include one or more methods 76 for sorting and filtering the electronic image files (not shown) included in EIF batches 26 and 32. As mentioned above, EIF batches 26 and 32 generally include one or more electronic document files. EIF batch 26 includes electronic document files generated by scanning device 30 and scanning device application 28 and electronic document files generated by any third-party source, which may include a second scanning device or an electronic document clearinghouse. As also discussed further below, EIF event generator 74 generates EIF events 78 for each electronic image file based on information included in EIF batches 26 and 32. EDM 22 typically communicates with an EIF database 80 for storing the electronic image files transmitted with batches 26 and 32. EDM 22 may be used to manage all types of electronic files, i.e., both image files and non- image files. As follows, EIF database 80 may also include non-image electronic files such as word processing files or other electronic documents.
[0017] As mentioned above, EDM 22 is in communication with task engine 24. EIF events 78 are transmitted from EDM 22 to task engine 24, requests to view electronic image files or to call methods 76 stored in document manager 72 of the EDM are transmitted from the task engine to the EDM, and electronic image files from EIF database 80 are shared with and viewed within the task engine environment. Task engine 24 typically includes a task generation submodule 82 for creating EIF-related tasks 84 based on the information in EIF events 78. Task engine 24 may include a task manager submodule 88 having a graphical user interface (GUI) 90 for viewing a task list 92 including both EIF-related tasks 84 and non-EIF-related tasks. Task engine 24 typically communicates with a task database 86, which is used to store the tasks that populate task list 92. •
[0018] In use, system 20 typically will work seamlessly to integrate EDM 22 with task engine 24. EDM 22 receives EIF batches 26 that contain one or more electronic image files (not shown) created using scanning device 30 and scanning device application 28 or EIF batches 32 containing one or more electronic image files (not shown) created by a third party such as an electronic document clearinghouse. EDM 22 stores the electronic image files in EIF database 80. EIF event generator 74 generates an EIF event 78 for each electronic image file that is stored in EIF database 80 based on data included in batch 26 or 32. EIF event generator 74 may also generates an EIF event 78 for each existing electronic image file stored in EIF database 80 that is modified. An EIF event 78 is a data file that includes various data regarding the electronic image file such as the image file type, image size, and any pertinent data fields related to the subject of the image file. Each EIF event 78 is forwarded to task engine 24. Within task engine 24, each EIF event 78 is processed by task generator submodule 82 to determine whether a task related to the event should be generated. Although not illustrated in FIG. 2, task engine 24 may include a set of predetermined rules that are compared to each EIF event 78 to determine whether to generate a corresponding task. If it is determined that a task should be generated, EIF task 84 is generated and stored in task database 86. The tasks stored in task database 86 populate task list 92. Users accessing task list 92 in task engine 24 are thus able to both view and work EIF tasks 84. As discussed further below, task engine 24 typically includes links or buttons that call methods 76 from EDM document manager 72. Methods 76 generally sort or filter electronic image files stored in database 80 and return them to GUI 90 for viewing by a user. For example, while working an EIF task 84, a user is typically able to view the electronic image file underlying the task by simply clicking on a link or button with pointing device 54.
[0019] As illustrated in FIG. 3, in one embodiment, task generation submodule 82 of system 20 includes a plurality of manager submodules that interact to generate tasks: an event manager 94 having an event queue 96 for receiving EIF events 78; a ruleset manager 98; a task definitions manager 100; a task generation manager 102 having a system task generation routine 104 and a task duplicate checking routine 106; an agent manager 108; and a templates manager 110. In addition to the disclosure contained herein, pending U.S. Patent Application No. 10/632,328, filed August 1, 2003, which is hereby incorporated by reference in its entirety, further describes the embodiment of task generation submodule 82 illustrated in FIG. 3.
[0020] Ruleset manager 98 supplies task generation rulesets 99 to both event manager 94 and task definitions manager 100. Task definitions manager 100 supplies task definitions 101 to event manager 94. Information is sent from event manager 94 and task definitions manager 100 to task generation manager 102 where system task generation routine 104 generates tasks using data supplied by templates manager 110. Alternatively, information may be sent from agent manager 108 to task generation manager 102 instead of from event manager 94 and task definitions manager 100. In addition, agent manager 108 may place events directly on event queue 96. Before sending tasks to task database 86, tasks generated by system task generation routine 104 are checked by task duplicate checking routine 106 to determine if identical tasks exist in the system. As discussed further below, acceptable tasks are generally stored in task database 86 for viewing in task list 92 via task manager submodule 88 and GUI 90. The data that populates the managers in task generation submodule 82 is typically provided by a task engine database 112, which is generally populated based on setup input from a system administrator. Much of the data stored in task engine database 112 is grouped in dictionaries. For example, one dictionary may exist for task names and another for views.
[0021] A user typically interacts with task manager submodule 88 to view and work EIF-related tasks 84 included on task list 92. As also described above, task list 92 is displayed to a user via GUI 90. Referring now to FIGS. 4-6, in one embodiment, GUI 90 may include a first portion 120 and a second portion 122. First portion 120 includes task list 92. Second portion 122 includes a preview tab 124 and a corresponding preview text box 125 (shown in FIG. 5), and an instructions tab 126 and a corresponding instructions text box 128. Of course, in other embodiments, additional tabs may be included. In addition, any type of data, link, or instruction may be included in each tab. A plurality of buttons facilitates user interaction with task list 92. An edit button 130 allows a user to edit a selected task 132. In FIG. 4, only one task, selected task 132, is selected as denoted by the "X" in task selection column 134 to the left of "Task Name" column 136. However, a user may select a plurality of tasks for viewing and or working by marking the box in task selection column 134 for each task desired. An actions button 138 allows a user to select actions from a dropdown menu (not shown) having predefined actions for working common tasks. Examples of predefined actions include but are not limited to hiding preview or instructions tabs 124 and 126, respectively, viewing selected tasks, manually marking tasks as done, reassigning tasks, and adding notes to tasks. A start task button 139 allows a user to begin working a selected task 132, which may be EIF-related task 84.
[0022] Task list 92 generally includes a plurality of data columns 140 that include data related to a particular task. The particular data columns included in data columns 140 are determined according to a particularly selected view 142 that is selected from a view dropdown box 144. Particularly selected view 142 causes system 20 to run a query against task database 86. The tasks that match the view query are displayed on task list 92. In addition to data from task database 86, data from sources outside of task database 86, e.g., data from a target object, may be included in task list 92. A system administrator, using task engine module 24, creates the views that populate view dropdown box 144. A user may typically access any views included in view dropdown box 144. After selecting a view, a user may alter selected view 142 by selecting a particular column header 146 thereby sorting task list 92 according to the data contained in the column beneath the selected header column.
[0023] Referring now to FIG. 5, preview tab 124 and corresponding preview text box 125 allow a user to view additional data related to any of the tasks in task list 92. Typically, a user highlights a particular task using pointing device 54 to designate it as the presently selected task (not shown). Data related to the presently selected task populates preview text box 125. In this way, a significant amount of data may be displayed with respect to each task in task list 92. In addition to data, preview text box 125 may also include links or buttons that cause additional data or electronic image files related to the presently selected task to be displayed. For example, in the embodiment illustrated in FIG. 5, preview text box 125 includes a documents button 149, which allows a user to cause a list of all electronic image filenames related to the subject of the presently selected task, or the files themselves, to be displayed in either first portion 120 or a pop-up window 150. In FIG. 5, an insurance card 151 of the particular patient, i.e., an electronic image file stored in EIF database 80, is displayed in pop-up window 150.
[0024] As mentioned above, to begin working a task, a user may select start task button 139 or select instructions tab 126. Selection of start task button 139 or instructions tab 126 causes the instructions tab to be selected thereby simultaneously displaying instructions text box 128 (as illustrated in FIG. 4) and hiding preview text box 125. In one embodiment, selection of start task button 139 may also cause the first item in instructions text box 128 to be executed. Instructions text box 128 typically includes a list of options 152 for working the presently selected task. Referring again to FIG. 4, list of options 152 may not be numbered or arranged in a particular order. However, in other embodiments, list of options 152 may be numbered or arranged in a particular order. In addition, in some instances, a task may only be informational and no instructions will be provided. List of options 152 may also include various links or buttons that allow a user to cause additional data or electronic image files to be displayed in first portion 120. For example, in FIG. 4, list of options 152 includes a view link 154. When selected, view link 154 causes an electronic image of the insurance card of the subject of the presently selected task, i.e., a particular patient - "TEST CONTRACT," to be displayed (as illustrated in FIG. 5) in first portion 120. As mentioned above, in one embodiment, selection of start task button 139 may cause view link 154 to be automatically selected.
[0025] Referring now to FIG. 6, as mentioned above with respect to FIG. 5, upon selection of documents button 149, an electronic document list 160 may be displayed in first portion 120. List 160 generally includes a name column 161 with descriptive names of all the electronic image files stored in system EIF database 80 that relate to the subject of the presently selected task, i.e., the patient "TEST CONTRACT," in this example. List 160 may include selection boxes 162 for each electronic image file and a view button 164. A user may view any of the electronic image files from list 160 in first portion 120 by checking any of selection boxes 162 and selecting view button 164.
[0026] As mentioned above, when selecting a button or a link such as documents button 149 or view link 154, a particular one of methods 76 in EDM 22 is called. Generally, each of methods 76 may be a query that sorts or filters the electronic image files stored in EIF database 80 and returns either a list or images of the sorted or filtered files to first portion 120 for display to a user. FIG. 7 illustrates the steps to a particular method 170, which causes a list of documents related to the social security number of a particular patient that is the subject matter of the presently selected task to be generated and displayed. First, at step 172, a user selects documents button 149. Then, at step 174, method 170, which is associated with button 149, is executed. At step 176, a query of EIF database 80 is performed to generate a list of all electronic image files that include a unique patient identifier field having the same unique patient identifier as the patient who is the subject of the presently selected task. Then, at step 178, the list of electronic image files generated in step 176 is returned to task engine 24 for display in first portion 120 of GUI 90. In other embodiments, such as a particular one of methods 76 associated with view link 154, the electronic images, rather than a list of electronic image filenames, are automatically displayed in first portion 120 upon selection of the link or button.
[0027] Another aspect of the present invention is a method 180 of generating tasks related to electronic image files. FIG. 8 illustrates the steps of method 180. First, at step 182, either EIF batch 26 or 32 containing one or more electronic image files is received by EDM 22 or one or more existing EIFs from EIF database 80 that have been modified are received by EDM 22. Then, at step 184, EIF event generator 74 creates an EIF event 78 for each of the electronic image files received either in EIF batch 26 and 32 or from EIF database 80. Next, at step 186, each EIF event 78 created in step 184 is sent to event queue 96 of task engine 24. Then, at step 188, each EIF event 78 in event queue 96 is compared to one or more predetermined rules in ruleset manager 98 of task engine 24. Finally, at step 190, task generation manager 102 and system task generation routine 104 generate tasks related to each EIF event 78 if they meet the conditions of one or more predetermined rules in ruleset manager 98.
[0028] The system and methods of the present invention help reduce the overall revenue cycle for billing processes that include electronic image files. By integrating an EDM to interact with tasking/workflow engines, better workflow capabilities for working tasks related to electronic image files are provided thereby reducing the amount of time it takes to work such tasks. By opening up an EDM to work with a tasking engine, documents are not lost and they are routed to the appropriate users for follow-up.
[0029] In one example of one application of the present invention, the system is used in the healthcare industry in a medical data management system to provide a user the capability to see all electronic image files related to a particular patient, specific types of images for a particular patient, and specific types of images for all patients. This type of functionality enhances the overall flow of information within the system thereby saving both time and money.

中文:
[0001]一般来说,本发明涉及用来管理电子图像文件的电子文档管理系统。具体来说,本发明针对用于生成与电子图像文件相关的任务的系统及方法。
[0002]为了管理综合传递网络(IDN)中的数据量,卫生保健提供组织转向复杂的数据管理系统或应用。这些系统通常包括用于维护或改进数据质量的模块。通过改进数据质量、即校正数据中的错误和/或遗漏,可减小患者计费的收入周期,并且可改进对顾客的整体服务。一般来说,对于IDN中的每个卫生保健服务提供商,任务列表被产生并加入用于改进那个特定提供商特定的数据的任务。诸如数据处理员之类的用户通常负责操作任务列表上的任务。
[0003]对于大IDN,任务列表上的任务可能包括由系统用户输入的任务、由第三方系统输入的任务以及由数据管理系统本身所产生的任务。先有技术的数据管理系统通常不能够结合具体涉及电子图像文件的任务,例如通过扫描产生的、采用图形软件创建的或者从其它应用中导入的图像文件等。具体涉及电子图像文件的任务的一个实例是在扫描保险卡时产生的任务。通常当患者在医院、诊所或医务室登记预约时扫描患者保险卡。但是,记帐员和登记人员通常需要包含保险卡信息的电子图像文件来检验保险项目-通常不是为患者办理登记手续的人员。先有技术的数据管理系统不能够产生通常包含用于操作任务的指示或工作流程以及到特定电子图像文件的链接的任务。例如,在扫描保险卡的情况中,先有技术系统不能够产生指示适当人员检验患者保险卡中包含的信息并提供到保险卡的电子图像文件的链接的任务。
[0004]在先有技术的系统中,手动过程通常用于在电子图像文件变为可用时通知正确的人员。然而,手动过程通常破坏并且可能产生未被正确索引或者没有及时索引的电子图像文件。无法及时向组织内部的适当输入点提供电子图像文件中包含的信息往往产生计费延迟、付费延迟以及收入周期时间的整体增加。
[0005]卫生保健行业只是可利用用于产生与本发明的电子图像文件相关的任务的系统及方法的一个实例。本领域的技术人员知道,电子文档管理器以及任务引擎均用于无数应用和行业中。
[0007]本发明的另一个方面是产生与电子文档管理器中存储的一个或多个电子图像文件相关的一个或多个任务的方法。该方法包括以下步骤:创建与电子图像文件相关的一个或多个电子图像文件事件;提供预定规则集,规则的每一个具有至少一个预定条件;将一个或多个电子图像文件事件与预定规则集进行比较;以及在一个或多个电子图像文件事件满足至少一个预定条件时创建一个或多个任务。
[0008]本发明的又一个方面是用于产生与一个或多个电子图像文件相关的一个或多个任务的系统。系统包括:电子文档管理模块,包含用于存储电子图像文件的电子图像文件数据库和用于产生与电子图像文件相关的电子图像文件事件的电子图像文件事件生成器子模块;以及任务引擎模块,与电子文档管理模块进行通信,用于根据电子图像文件事件的内容来产生与电子图像文件相关的任务。任务引擎模块包括任务生成子模块和规则集管理器,任务生成子模块包括用于存储电子图像文件事件的事件管理器,规则集管理器包括至少一个预定规则集。规则的每一个具有至少一个预定条件。任务引擎模块还包括任务生成管理器,用于将电子图像文件事件与至少一个预定规则集进行比较并且在电子图像文件事件满足至少一个预定条件时产生一个或多个任务。
[0009]本发明的又一个方面是一种计算机可读媒体,其中包含产生与电子文档管理器中存储的一个或多个电子图像文件相关的一个或多个任务的程序,该程序包含在由计算机运行时执行以下步骤的指令:创建与电子图像文件相关的一个或多个电子图像文件事件;提供预定规则集,规则的每一个具有至少一个预定条件;将一个或多个电子图像文件事件与预定规则集进行比较;以及在一个或多个电子图像文件事件满足至少一个预定条件时创建一个或多个任务。
[0011]现在参照附图,其中的相似参考标号表示相似部分,具体参照图1,本发明的一个方面是用于产生与电子图像文件相关的任务的系统20。系统20包括与任务引擎24进行通信的电子文档管理器(EDM)22。作为它的功能性的一个方面,EDM 22接收由扫描装置应用28和扫描装置30所产生的电子图像文件(EIF)批量数据26和/或由诸如电子文档交换所之类的第三方所产生的EIF批量数据32。一般来说,EIF批量数据26和32包含标准EIF格式的一个或多个电子图像文件,例如jpg、tiff、bmp、gif、pdf、png、xpm。电子图像文件的实例包括患者保险卡、催询单、计费发票、临床记录以及例如x光等的检验记录。如下面进一步所述,EDM 22与任务引擎24共享从EIF批量数据26和32中得到的信息。任务引擎24又产生涉及批量数据26和32中包含的一个或多个电子图像文件的EIF相关任务或多个任务。
[0012]图1说明在适当计算环境中实现的系统20。虽然不作要求,但一般将根据通常包含在程序模块中、由传统的通用数字计算机所执行的计算机可执行指令来描述本发明。程序模块通常包括执行特定任务的例程、程序、对象、组件、数据结构等。本发明可采用各种计算机系统配置来实施,其中包括连网客户机-服务器计算系统、手持式装置、可编程消费电子产品、小型计算机、大型计算机等等。本发明通常但不一定在分布式计算环境中实施,在这些环境中,任务由通过例如LAN、WAN或基于因特网的网络之类的通信网络链接的远程处理装置来执行。在分布计算环境中,程序模块可位于本地和远程存储器存储装置中。
[0013]我们考虑,本发明的系统20将在包括个人计算机40和因特网服务器42的联网计算环境中进行操作。个人计算机40可包括计算机中央处理器(CPU)44、计算机存储器46和输入/输出装置48。输入/输出装置48通常包括诸如硬盘驱动器之类的存储装置50、键盘52、指示装置54即鼠标以及诸如监视器之类的显示装置56。
[0014]因特网服务器42可包括服务器存储器58和因特网服务器CPU 60。一般来说,系统20包括驻留在因特网服务器42的服务器存储器58中的一个或多个计算机程序62。计算机程序62无疑可驻留在本地或广域网服务器的存储器中,或者驻留在独立台式计算机系统的存储器中。
[0015]在一种实现中,可经由驻留在计算机系统40的计算机存储器46中的瘦客户机访问程序64来访问系统20。在这样一种配置中,计算机程序62可在因特网服务器CPU 60和计算机CPU 44的任一个或者两个上运行。
[0016]现在参照图2,在一个实施例中,EDM 22可包括用户接口70、文档管理器子模块72和EIF事件生成器74。用户接口70允许用户与文档管理器子模块72以及EIF事件生成器74进行交互。如下面进一步所述,文档管理器子模块72可包括用于分类和过滤EIF批量数据26、32中所包含的电子图像文件(未示出)的一个或多个方法76。如上所述,EIF批量数据26和32一般包含一个或多个电子文档文件。EIF批量数据26包含由扫描装置30和扫描装置应用28所产生的电子文档文件以及由可能包括第二扫描装置或电子文档交换所的任何第三方源所产生的电子文档文件。如下面进一步所述,EIF事件生成器74根据EIF批量数据26和32中所包含的信息为各电子图像文件产生EIF事件78。EDM 22通常与EIF数据库80进行通信,EIF数据库80用于存储随批量数据26和32一起发送的电子图像文件。EDM 22可用来管理所有类型的电子文件,即图像文件以及非图像文件。如以下所述,EIF数据库80还可包括非图像电子文件,例如字处理文件或其它电子文档。
[0017]如上所述,EDM 22与任务引擎24进行通信。EIF事件78从EDM 22发送到任务引擎24,查看电子图像文件或者调用EDM的文档管理器72中所存储的方法76的请求从任务引擎发送到EDM,以及来自EIF数据库80的电子图像文件与任务引擎共享并在其中被查看。任务引擎24通常包括用于根据EIF事件78中的信息来创建EIF相关任务84的任务生成子模块82。任务引擎24可包括任务管理器子模块88,任务管理器子模块88具有图形用户界面(GUI)90,用于查看包含EIF相关任务84以及非EIF相关任务的任务列表92。任务引擎24通常与用于存储任务列表92上的任务的任务数据库86进行通信。
[0018]在使用中,系统20通常将无缝工作以便把EDM 22与任务引擎24相结合。EDM 22接收包含采用扫描装置30和扫描装置应用28所创建的一个或多个电子图像文件(未示出)的EIF批量数据26或者包含由诸如电子文档交换所等的第三方所创建的一个或多个电子图像文件(未示出)的EIF批量数据32。EDM 22把电子图像文件存储在EIF数据库80中。EIF事件生成器74根据批量数据26或32中所包含的数据为存储于EIF数据库80的各电子图像文件产生EIF事件78。EIF事件生成器74还可为存储于EIF数据库80中经过修改的各现有电子图像文件产生EIF事件78。EIF事件78是包含与电子图像文件有关的各种数据、如图像文件类型、图像大小以及与图像文件的主题相关的任何相干数据字段的数据文件。各EIF事件78被转发给任务引擎24。在任务引擎24中,各EIF事件78由任务生成器子模块82进行处理,以便确定是否应当产生与该事件相关的任务。虽然在图2中未示出,但任务引擎24可包括预定规则集,它们与各EIF事件78进行比较以便确定是否产生相应的任务。如果确定应当产生任务,则EIF任务84被产生并存储在任务数据库86中。任务数据库86中存储的任务加入任务列表92。访问任务引擎24中的任务列表92的用户因而能够查看并操作EIF任务84。如下面进一步所述,任务引擎24通常包括从EDM文档管理器72调用方法76的链接或按钮。方法76一般归类或过滤数据库80中所存储的电子图像文件,并将它们返回给GUI 90供用户查看。例如,当操作EIF任务84时,用户通常只要通过用指示装置54点击链接或按钮就能够查看任务之下的电子图像文件。
[0019]如图3所示,在一个实施例中,系统20的任务生成子模块82包括进行交互以产生任务的多个管理器子模块:事件管理器94,具有事件队列96,用于接收EIF事件78;规则集管理器98;任务定义管理器100;任务生成管理器102,具有系统任务生成例程104和任务重复检验例程106;代理管理器108;以及模板管理器110。除了本文所包含的公开之外,2003年8月1日提交的未决美国专利申请No.10/632328还描述了图3所示的任务生成子模块82的实施例,通过引用将它完整地结合于此。
[0020]规则集管理器98把任务生成规则集99提供给事件管理器94以及任务定义管理器100。任务定义管理器100把任务定义101提供给事件管理器94。信息从事件管理器94和任务定义管理器100发送给任务生成管理器102,在其中,系统任务生成例程104利用模板管理器110所提供的数据来产生任务。或者,信息可从代理管理器108发送给任务生成管理器102,而不是从事件管理器94和任务定义管理器100中发送。另外,代理管理器108可把事件直接放入事件队列96。在把任务发送给任务数据库86之前,系统任务生成例程104所产生的任务由任务重复检验例程106进行检验,以便确定系统中是否存在相同的任务。如下面进一步所述,可接受的任务一般存储在任务数据库86中,以便经由任务管理器子模块88和GUI 90在任务列表92中进行查看。任务生成子模块82中的管理器上的数据通常由任务引擎数据库112来提供,它一般根据来自系统管理员的设置输入被加入。任务引擎数据库112中所存储的数据中的许多在词典中被分组。例如,对于任务名称可能存在一个词典,而对于查看则存在另一个词典。
[0021]用户通常与任务管理器子模块88进行交互以查看并操作任务列表92中包含的EIF相关任务84。又如上所述,经由GUI90将任务列表92向用户显示。现在参照图4-6,在一个实施例中,GUI 90可包括第一部分120和第二部分122。第一部分120包括任务列表92。第二部分122包括预览选项卡124和相应的预览文本框125(图5所示)以及指令选项卡126和相应的指令文本框128。在其它实施例中,无疑可包括其它选项卡。另外,任何类型的数据、链接或指令也可包含在各选项卡中。多个按钮帮助与任务列表92的用户交互。编辑按钮130允许用户编辑所选任务132。在图4中,只有一个任务、所选任务132被选取,如“任务名称”栏136的左侧的任务选择栏134中的“X”所示。但是,用户可通过标记预期的各任务的任务选择栏134中的框来选择多个任务用于查看和/或操作。动作按钮138允许用户从具有用于操作通用任务的预定动作的下拉菜单(未示出)中选择动作。预定动作的实例包括但不限于分别隐藏预览或指令选项卡124和126、查看所选任务、手动将任务标记为完成、重新指定任务以及对任务添加注释。开始任务按钮139允许用户开始操作所选任务132,它可能是EIF相关任务84。
[0022]任务列表92一般包括多个数据栏140,数据栏140包含与特定任务相关的数据。数据栏140中包含的具体数据栏根据从视图下拉框144所选的具体选择的视图142来确定。具体选择的视图142使系统20执行对任务数据库86的查询。匹配视图查询的任务在任务列表92上显示。除了来自任务数据库86的数据之外,来自任务数据库86外部的源的数据、例如来自目标对象的数据可包含在任务列表92中。系统管理员使用任务引擎模块24来创建视图下拉框144上的视图。用户通常可访问视图下拉框144中所包含的任何视图。在选择视图之后,用户可通过选择特定栏标题146、从而按照所选标题栏之下的栏中所包含的数据对任务列表92进行分类来改变所选视图142。
[0023]现在参照图5,预览选项卡124和相应的预览文本框125允许用户查看与任务列表92中的任务的任一个相关的附加数据。用户通常使用指示装置54加亮显示特定任务,从而将其指定为当前所选任务(未示出)。与当前所选任务相关的数据加入预览文本框125。这样,相对于任务列表92中的各任务可显示大量数据。除了数据之外,预览文本框125还可包括使涉及当前所选任务的附加数据或电子图像文件被显示的链接或按钮。例如,在图5所示的实施例中,预览文本框125包括文档按钮149,它允许用户使涉及当前所选任务的主题的所有电子图像文件名的列表或文件本身在第一部分120或弹出窗口150中显示。在图5中,特定患者的保险卡151、即EIF数据库80中存储的电子图像文件在弹出窗口150中显示。
[0024]如上所述,为了开始操作某个任务,用户可选择开始任务按钮139或者选择指令选项卡126。开始任务按钮139或指令选项卡126的选择使指令选项卡被选取,从而同时显示指令文本框128(如图4所示)并隐藏预览文本框125。在一个实施例中,开始任务按钮139的选择还可使得执行指令文本框128中的第一项。指令文本框128通常包括用于操作当前所选任务的选项列表152。同样参照图4,选项列表152可能不按照特定顺序来编号或排列。但是,在其它实施例中,选项列表152可能以特定顺序来编号或排列。另外,在一些情况中,任务可能只是信息,而不会提供指令。选项列表152还可包括各种链接或按钮,它们允许用户使附加数据或电子图像文件在第一部分120中显示。例如,在图4中,选项列表152包含查看链接154。在被选取时,查看链接154使当前所述任务的主题、即特定患者-“检验合同”-的保险卡的电子图像在第一部分120中显示(如图5所示)。如上所述,在一个实施例中,开始任务按钮139的选择可使查看链接自动被选取。
[0025]现在参照图6,如以上针对图5所述,在选取文档按钮149时,电子文档列表160可在第一部分120中显示。列表160一般包括名称栏161,其中具有系统EIF数据库80中所存储的涉及当前所选任务的主题、即本例中的患者“检验合同”的所有电子图像文件的描述名称。列表160可包含各电子图像文件的复选框162和查看按钮164。用户可通过选取复选框162的任一个并选取查看按钮164,在第一部分120从列表160中查看电子图像文件的任一个。
[0026]如上所述,当选取按钮或链接、如文档按钮149或查看链接154时,EDM 22中的方法76的一个特定方法被调用。一般来说,方法76的每一个可能是分类或过滤EIF数据库80中所存储的电子图像文件并把已分类或已过滤文件的列表或图像返回给第一部分120以便向用户进行显示的查询。图7说明特定方法170的步骤,它使涉及作为当前所选任务的主题的特定患者的社会保险号的文档列表被产生并显示。首先,在步骤172,用户选择文档按钮149。然后,在步骤174,与按钮149关联的方法170被执行。在步骤176,执行EIF数据库80的查询以便产生所有电子图像文件的列表,电子图像文件包含与作为当前所选任务的主题的患者具有相同的唯一患者标识符的唯一患者标识符字段。然后,在步骤178,在步骤176所产生的电子图像文件的列表被返回给任务引擎24,以便在GUI 90的第一部分120中显示。在其它实施例、例如方法76中与查看链接154关联的一种特定方法中,在选取该链接或按钮时,电子图像而不是电子图像文件名列表自动地在第一部分120中显示。
[0027]本发明的另一个方面是产生与电子图像文件相关的任务的方法180。图8说明方法180的步骤。首先,在步骤182,包含一个或多个电子图像文件的EIF批量数据26或32由EDM 22接收,或者来自EIF数据库80的经过修改的一个或多个现有EIF由EDM 22接收。然后,在步骤184,EIF事件生成器74为在EIF批量数据26、32中所接收或者来自EIF数据库80的电子图像文件的每一个创建EIF事件78。随后,在步骤186,在步骤184所创建的各EIF事件78被发送给任务引擎24的事件队列96。然后,在步骤188,事件队列96中的各EIF事件78与任务引擎24的规则集管理器98中的一个或多个预定规则进行比较。最后,在步骤190,如果它们满足规则集管理器98中的一个或多个预定规则的条件,则任务生成管理器102和系统任务生成例程104产生与各EIF事件78相关的任务。
[0028]本发明的系统及方法帮助减小包括电子图像文件的计费过程的整体收入周期。通过结合EDM以便与任务分配/工作流程引擎进行交互,提供了用于操作与电子图像文件相关的任务的更好的工作流程能力,从而减少操作这类任务所花费的时间量。通过开启EDM以便与任务分配引擎配合工作,文档不会丢失,并且它们被路由到适当的用户以便继续处理。
[0029]在本发明的一个应用的一个实例中,系统用于医疗数据管理系统中的卫生保健行业,以便为用户提供查看与特定患者相关的所有电子图像文件、特定患者的特定类型的图像以及所有患者的特定类型的图像的能力。这种类型的功能性增强了系统中的整体信息流程,从而节省时间和资金。