Source: http://www.google.com/patents/US20040059714?ie=ISO-8859-1&dq=6,263,507
Timestamp: 2015-05-03 20:39:01
Document Index: 434253252

Matched Legal Cases: ['art 100', 'art 150', 'art 150', 'art 250', 'art 250', 'art 300', 'art 300']

Patent US20040059714 - System and method for providing decision support to appointment schedulers ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA method of providing a healthcare provider the ability to schedule an appointment including receiving a patient's requested appointment from an appointment scheduler; receiving an initial visit type from the appointment scheduler corresponding to the requested appointment; scheduling the requested appointment...http://www.google.com/patents/US20040059714?utm_source=gb-gplus-sharePatent US20040059714 - System and method for providing decision support to appointment schedulers in a healthcare settingAdvanced Patent SearchPublication numberUS20040059714 A1Publication typeApplicationApplication numberUS 10/631,598Publication dateMar 25, 2004Filing dateJul 31, 2003Priority dateJul 31, 2002Also published asUS7979294Publication number10631598, 631598, US 2004/0059714 A1, US 2004/059714 A1, US 20040059714 A1, US 20040059714A1, US 2004059714 A1, US 2004059714A1, US-A1-20040059714, US-A1-2004059714, US2004/0059714A1, US2004/059714A1, US20040059714 A1, US20040059714A1, US2004059714 A1, US2004059714A1InventorsSteven Larsen, Sameer Grover, Marie DeroseOriginal AssigneeLarsen Steven J., Sameer Grover, Derose Marie C.Export CitationBiBTeX, EndNote, RefManReferenced by (9), Classifications (10), Legal Events (2) External Links: USPTO, USPTO Assignment, EspacenetSystem and method for providing decision support to appointment schedulers in a healthcare setting
DETAILED DESCRIPTION [0020]FIG. 1 illustrates an embodiment of an enterprise-wide data network 10 including a first group of healthcare facilities 20 operatively coupled to a network computer (i.e. machine) 30 via a network 32. The plurality of healthcare facilities 20 may be located, by way of example rather than limitation, in separate geographic locations from each other, in different areas of the same city, or in different states. The network 32 may be provided using a wide variety of techniques well known to those skilled in the art for the transfer of electronic data. For example, the network 32 may comprise dedicated access lines, plain ordinary telephone lines, satellite links, combinations of these, etc. Additionally, the network 32 may include a plurality of network computers or server computers (not shown), each of which may be operatively interconnected in a known manner. Where the network 32 comprises the Internet, data communication may take place over the network 32 via an Internet communication protocol. [0021] The network computer 30 may be a server computer of the type commonly employed in networking solutions. The network computer 30 may be used to accumulate, analyze, and download data relating to a healthcare facility's medical records. For example, the network computer 30 may periodically receive data from each of the healthcare facilities 20 indicative of information pertaining to a patient's medical record, billing information, employee data, etc. The healthcare facilities 20 may include one or more facility servers 36 that may be utilized to store information for a plurality of patients/employees/accounts/etc. associated with each facility. [0022] Although the enterprise-wide data network 10 is shown to include one network computer 30 and three healthcare facilities 20, it should be understood that different numbers of computers and healthcare facilities may be utilized. For example, the network 32 may include a plurality of network computers 30 and dozens of healthcare facilities 20, all of which may be interconnected via the network 32. According to the disclosed example, this configuration may provide several advantages, such as, for example, enabling near real time uploads and downloads of information as well as periodic uploads and downloads of information. This provides for a primary backup of all the information generated in the process of updating and accumulating healthcare data. [0023]FIG. 2 is a schematic diagram of one possible embodiment of the network computer 30 shown in FIG. 1. The network computer 30 may have a controller 50 that is operatively connected to a patient health record repository 52 (such as a Universal Patient Record repository) via a link 56. The patient health record repository 52 may include one or more databases or data repositories that store patient healthcare data and related healthcare business data using one or more database management systems that run on one or more computing platforms on one or more computing devices. It should be noted that, while not shown, any additional databases or repositories may be linked to the controller 50 in a similar manner. [0024] The controller 50 may include a program memory 60, a microcontroller or a microprocessor (MP) 62, a random-access memory (RAM) 64, and an input/output (I/O) circuit 66, all of which may be interconnected via an address/data bus 70. It should be appreciated that although only one microprocessor 62 is shown, the controller 50 may include multiple microprocessors 62. Similarly, the memory of the controller 50 may include multiple RAMs 64 and multiple program memories 60. Although the I/O circuit 66 is shown as a single block, it should be appreciated that the I/O circuit 66 may include a number of different types of I/O circuits. The RAM(s) 64 and programs memories 60 may be implemented as semiconductor memories, magnetically readable memories, and/or optically readable memories, for example. The controller 50 may also be operatively connected to the network 32 via a link 72. [0025]FIG. 3 is a schematic diagram of one possible embodiment of several components located in one or more of the healthcare facilities 20 from FIG. 1. Although the following description addresses the design of the healthcare facilities 20, it should be understood that the design of one or more of the healthcare facilities 20 may be different than the design of other healthcare facilities 20. Also, each healthcare facility 20 may have various different structures and methods of operation. It should also be understood that the embodiment shown in FIG. 3 illustrates some of the components and data connections present in a healthcare facility, however it does not illustrate all of the data connections present in a typical healthcare facility. For exemplary purposes, one design of a healthcare facility is described below, but it should be understood that numerous other designs may be utilized. [0026] The healthcare facilities 20 may have a facility server 36, which includes a controller 80, wherein the facility server 36 is operatively connected to a plurality of client device terminals 82 via a network 84. The network 84 may be a wide area network (WAN), a local area network (LAN), or any other type of network readily known to those persons skilled in the art. The client device terminals 82 may also be operatively connected to the network computer 30 from FIG. 1 via the network 32. [0027] Similar to the controller 50 from FIG. 2, the controller 80 may include a program memory 86, a microcontroller or a microprocessor (MP) 88, a random-access memory (RAM) 90, and an input/output (I/O) circuit 92, all of which may be interconnected via an address/data bus 94. As discussed with reference to the controller 50, it should be appreciated that although only one microprocessor 88 is shown, the controller 80 may include multiple microprocessors 88. Similarly, the memory of the controller 80 may include multiple RAMs 90 and multiple programs memories 86. Although the I/O circuit 92 is shown as a single block, the I/O circuit 92 may include a number of different types of I/O circuits. The RAM(s) 90 and programs memories 86 may also be implemented as semiconductor memories, magnetically readable memories, and/or optically readable memories, for example. All of these memories or data repositories may be referred to as machine-accessible mediums. [0028] For the purpose of this description and a briefly discussed above, a machine-accessible medium includes any mechanism that provides (i.e., stores and/or transmits) information in a form accessible by a machine (e.g., a computer, network device, personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.). For example, a machine-accessible medium includes recordable/non-recordable media (e.g., read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; etc.), as well as electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.); etc. [0029] The client device terminals 82 may include a display 96, a controller 97, a keyboard 98 as well as a variety of other input/output devices (not shown) such as a printer, mouse, touch screen, track pad, track ball, isopoint, voice recognition system, etc. Each client device terminal 82 may be signed onto and occupied by a healthcare employee to assist them in performing their duties. Healthcare employees may sign onto a client device terminal 82 using any generically available technique, such as entering a user name and password. If a healthcare employee is required to sign onto a client device terminal 82, this information may be passed via the link 84 to the facility server 36, so that the controller 80 will be able to identify which healthcare employees are signed onto the system and which client device terminals 82 the employees are signed onto. This may be useful in monitoring the healthcare employees' productivity. [0030] Typically, facility servers 36 store a plurality of files, programs, and other data for use by the client device terminals 82 and the network computer 30. One facility server 36 may handle requests for data from a large number of client device terminals 82. Accordingly, each facility server 36 may typically comprise a high end computer with a large storage capacity, one or more fast microprocessors, and one or more high speed network connections. Conversely, relative to a typical facility server 36, each client device terminal 82 may typically include less storage capacity, a single microprocessor, and a single network connection. Overall Operation of the System [0031] One manner in which an exemplary system may operate is described below in connection with a block diagram overview and a number of flow charts which represent a number of portions or routines of one or more computer programs. These computer program portions may be stored in one or more of the memories in the controllers 50 and 80, and may be written at any high level language such as C, C++, or the like, or any low-level, assembly or machine language. By storing the computer program portions therein, various portions of the memories are physically and/or structurally configured in accordance with the computer program instructions. [0032]FIG. 4 is an exemplary flowchart overview 100 of the workflow and interactions between a healthcare information system (HCIS) and a system user, in this case an appointment scheduler. [0033] As shown in the exemplary flowchart 100, a user logs into the HCIS at a block 102. At a block 104, basic user authentication and security validation happens. Additionally, this embodiment provides for automatic loading of typical login contexts, such as department, location, and facility, as well as commonly used workflows, reports, and user interface options. [0034] At a block 106, the system user may open the scheduling module of the HCIS and select a patient at a block 110. Upon patient selection, the embodiment shown in FIG. 1 retains patient preferences, demographic, insurance coverage, primary care provider, referral and past and future appointment information in memory for later use by the scheduling module. [0035] At a block 112, the user elects to make an appointment for the patient by entering an initial visit type into the system. A healthcare organization (HCO) may configure its HCIS in such a way that this initial input, when of a certain type, triggers the decision support mechanisms also built into the HCIS. [0036] At a block 114, the system may evaluate the user's entry and run appropriate validation protocols to determine whether to simply accept the entry or to trigger a decision support mechanism, and if so, which one. Decision support mechanisms could be triggered only by the particular visit type entered by the current system user, by the particular department context that the system user has logged into (irrespective of the visit type being entered until that login context changes), or even system wide, for all users, in all departments, and for all visit types. [0037] At a block 116, depending upon the results of the validation, the HCIS prompts the system user for additional information which the user provides at a block 120. [0038] At a block 122, the HCIS takes the secondary user input at a block 120 and applies custom defined logic to determine appropriate visit type, provider, and department information which it might use to replace the system user's initial visit type input at a block 124. [0039]FIG. 5A is an exemplary flowchart 150 depicting the actions and decisions used in the creation of a questionnaire form, which is one of the types of decision support available. In the flowchart 150 of FIGS. 5A and 5B, the HCO makes decisions about how to configure its HCIS. If the HCO would take advantage of the questionnaire type of decision support, it defines the questions used to prompt the scheduler for the secondary input. [0040] At a block 152, the person configuring the system might create a question record. At a block 154, he decides what the scheduler will ask the patient and enters the text of that question at a block 156. At a block 160, he might enter some comments about that question to provide additional support to the scheduler. [0041] At a block 162, he decides what type of data the question will be. Any given question can be either a date (164), a time (166), a number (170), a database link (172), a yes/no response (174), free text (176), or a list of custom options (180) as defined by the person creating the question record. If the question is to be a database link (172), then the person configuring the system would decide at a block 182 whether it would be a link to the records in a specified database or to a specific data item in a specified database. [0042] At a block 196 from FIG. 5B, the person configuring the system might decide whether the question can have multiple responses recorded for it, and at a block 200 he might decide whether it is a question that requires a response from the scheduler. At a block 202, he may decide whether to put gender requirements on the question. For example, if the question is related to pregnancy, a scheduler would only ask the question of a woman. At a block 206, he might decide whether to place age restrictions on the question. For example, if the question is related to a woman's menstrual cycle, a scheduler might only ask the question of women in a certain age range, which the person configuring the system would enter at a block 210. [0043] At a block 212, the person configuring the system makes some decisions regarding the filing of responses to the question. He might specify a database in which to record the response (block 214), a particular item in that database to store the response (block 216), and/or any special code to be executed when the question is loaded or the response is filed (block 220). [0044] At a block 222, the person configuring the system creates a questionnaire record which is a grouper containing all the question records he wants to display together to the scheduler as specified at a block 224. [0045]FIG. 6 is an exemplary flowchart 250 depicting some of the actions and decisions used in the creation of a Scheduling Codes form, which may be one of the types of decision support available. In the flowchart 250, the HCO makes decisions about how to configure its HCIS. If the HCO takes advantage of the scheduling codes type of decision support, it then defines the code records available to the scheduler when prompting for the secondary input. [0046] At a block 252, the person configuring the system creates a Code record. At a block 254 he might decide what type of code it is. There are no standard code types defined in the exemplary system disclosed in FIG. 6, to provide maximum flexibility to the HCO in configuring its HCIS. The examples shown include Visit Type codes (block 256), Treatment codes (block 260), and Pre-visit Preparation codes (block 262). These examples might greatly aid in visit type selection in an environment such as a cancer treatment center where a facility wants to make certain treatment and treatment preparation codes available to schedulers at the time of secondary input in order to give the system enough information to find an appropriate visit type code which contains the list of visit types used to replace the initial input of the scheduler. [0047] At a block 264, the person configuring the system might specify whether the code is available for selection by the scheduler at the time of secondary input. If it is selectable, the code will appear on the form displayed in the user interface, as shown at a block 266. If it is not selectable, the scheduler will not be able to select it at the time of secondary input, and it may be used behind the scenes by the custom logic used to replace the initial visit type input. This is illustrated at a block 270. In the above example code types, the Treatment and Pre-Visit Preparation codes may be configured as selectable while the Visit Type codes may be non-selectable and only used in the custom logic. [0048] At a block 272, the person configuring the system might give the Code record a code value. This value might be a free text response of any alphanumeric string used to mark up the code in any desired way. The code might then be used by the custom logic in the programming point in replacing the initial visit type input. For example, in the above code type examples, the selectable Treatment and Pre-Visit Preparation codes might have time lengths associated with them which are entered as the code value in each record. The custom logic might then use the code value lengths of each code record selected by the scheduler to determine the appropriate visit type code record by summing them and rounding them to the closest code value as specified in a Visit Type code record. [0049] At a block 274, the person configuring the code record might specify a list of departments. At a block 276, he might indicate for each department specified at the block 274 whether this code is allowed in that department. At a block 280, he might specify which visit types in the system will be used to replace the scheduler's initial input in that department. This way, all departments in a location, which are often organized around specialties, may replace the same �dummy� initial visit type with a new visit type of their own particular needs. In addition, the person configuring the code record might create a parallel list of replacement visit types, or �coordinated� visits. This way, if a scheduler indicates that a visit should be �coordinated� then the system uses an alternate list of replacement visit types for the �dummy� visit type initially entered. [0050]FIG. 7 is an exemplary flowchart 300 depicting some of the actions and decisions used in the creation of a custom form, which may be one of the available types of decision support. In the flowchart 300, the HCO makes decisions about how to configure its HCIS. If the HCO would take advantage of the custom form type of decision support, it might create the items and user controls displayed to the scheduler when prompting for the secondary input. [0051] At a block 302, the person configuring the system might create items to capture data not included as part of a basic HCIS. These captured items might be mapped to data structures in a way similar to that illustrated in FIG. 8. [0052] Whether custom items or standard HCIS items are being used, the HCO might still elect to create a custom form which might be programmed in an object oriented programming language such as Visual Basic, as illustrated at a block 304. After which the user assigns the form a program ID and name to be used as a reference by the HCIS (block 306). [0053]FIG. 8 is a graphic representation of one exemplary way data might be structured within the Patient Health Record (PHR), which is housed in the HCIS. In FIG. 8, there are, essentially, 5 levels at which to access information on the data tree. [0054] Level 1 is the database level. This level represents a collection of like entities within which records can be created and about which data can be collected. For example, FIG. 8 depicts three such databases: Provider database 320, Patient database 322, and Procedure database 324. However, it is to be understood that there could be any number of databases, depending on the implementation of the HCIS. [0055] Level 2 is the record level. This level represents an individual entity within a given database. For example, within the Provider database 320, a record represents an individual physician, nurse, assistant, etc. 326. Within the Patient database 322, a record corresponds to a Patient 330. And within the Procedure database 324, a record corresponds to an individual procedure performed on the patient during his visit. [0056] Level 3 is the item level. This level represents an individual piece of information which is collected for a given record. For example, within a Provider's record, you might want to record his specialty. Within a Patient's record, you might want to record his primary care provider. Within a Procedure record, you might want to record its billing status. [0057] Level 4 is the contact level. This level represents the individual date 340 on which a value is recorded for an item. For example, within a patient's record, you might record the blood pressure every time he comes in to see his physician, and each time, you would record the reading in the same item. [0058] Level 5 is the data item level. This level represents multiple values for a given item, recorded on a given date. For example, in a patient's record you might record all the insurance coverages he currently has whenever he visits his physician. [0059] The embodiment shown in FIG. 8 allows for links between the databases 320, 322, and 324 at the Item level. For example, if you want to record which providers treated a patient when he came in, you might utilize the link between the Provider database 320 and the Treatment Team item 342 in the patient's record. If you wanted to record which procedures a patient was seen for, you might utilize a similar link with the Procedures database 324. This linking ensures cohesion between databases and correct, timely data. [0060] The branching structure of the data allows for any number of different subsets or combinations of data upon retrieval, depending on the parameters specified. For example, you might access a patient record and return all the branches beneath it, thereby providing a complete history of a patient's record within the PHR. Or, by specifying the appropriate Item and Date, you might return the primary care provider for every patient on a certain date. Or, you might simply return a single item for a single patient record on a certain date. [0061]FIG. 9 is an exemplary flowchart representation 350 of some of the actions that may be taken by the HCIS and the decisions made by the scheduler during validation of the initial visit type input and subsequent determination of decision support prompting. [0062] At a block 352, the scheduler would input an initial visit type. This might be any normally scheduled visit type or it might be a visit type set up as a �dummy� visit type which is used to trigger the decision support protocols. [0063] At a block 354, initial input entered by the scheduler is evaluated by the HCIS as a valid entry and the database of visit types is queried for a match at a block 356. If no match is found, the scheduler is notified and may then make another entry. If a matching visit type is found, the HCIS evaluates that visit type record at a block 362 to determine whether decision support has been enabled for it. If not, the HCIS evaluates the login department of the scheduler at a block 364 to determine whether decision support has been enabled for users in that department. If not, the HCIS evaluates the facility record at a block 366 to determine whether decision support has been enabled system wide. If no decision support has been enabled, at any of these levels, the match is accepted at a block 370, no prompting is triggered and the scheduler is allowed to continue making the appointment with the initial input. [0064] If decision support has been enabled, the scheduler will be prompted by the HCIS at a block 372 for further input. Which kind of prompting is displayed to the scheduler is dependant upon which level decision support has been enabled at and which kind of support has been specified there. In the embodiment 350, this would include questionnaire forms 376, scheduling codes forms 380, or custom defined forms 382. [0065] If the type of prompt to be displayed is a questionnaire, the HCIS supplies the questionnaire record specified at the level at which decision support was triggered and displays it on a form to the scheduler in the user interface. [0066] If the type of prompt to be displayed is Scheduling Codes, the system uses a standard HCIS form for display to the scheduler. Before the form is displayed, the records in the scheduling codes database are evaluated to determine whether they are allowed in the current department and any that are not allowed might be filtered out. [0067] If the type of prompt to be displayed is a custom form, the HCIS supplies the program ID of the form from the same level at which decision support was triggered and displays the form to the scheduler in the user interface. [0068]FIG. 10 is an example of some pseudo code representing code a HCO might write into the programming point logic to be applied when the scheduler has supplied the secondary input on the decision support form. [0069] The logic represented in the sample might be used to evaluate the code records selected by a scheduler on the scheduling codes form (for example the selectable Treatment type codes) and sum the lengths in each one in order to determine which non-selectable Visit Type code record to use. The Visit Type code record might then be used to supply the appropriate visit types to the programming point, which sends them back to the user interface to replace the initial �dummy� visit type entered by the user. [0070] It is to be understood that any conceivable logic might be used to instruct the HCIS on how and on which parameters to use to recommend or replace or restrict scheduling. In addition, it is to be understood that any logic used for evaluating custom items or question records and/or their stored responses might perform the same or similar functions to that implemented for code records, while also having their own particular requirements and implementations. [0071]FIG. 11 is an exemplary flowchart representation 400 of some actions taken by the HCIS and the decisions made by the scheduler during secondary user input and subsequent application of custom logic as specified in FIG. 10. [0072] At a block 402, a form is displayed to the scheduler prompting him for further information. If the form being displayed is a questionnaire 404, the HCIS loads the questionnaire record which contains pointers to the question records built by the HCO and displays them on the form at a block 406, disabling or filtering questions based on any age and/or gender restrictions from the question records as applied to the patient currently selected. At a block 410, the scheduler collects the responses from the patient on the form. [0073] If the form being displayed is a scheduling codes form 412, the system has filtered the codes available to the scheduler based on whether they are allowed in the current department, as shown at a block 414. At a block 416, the scheduler might then select the appropriate codes for the current visit based on the treatments required, and at a block 420, he might indicate whether the visit is a coordinated visit, thereby alerting the HCIS as to which list of replacement visit types to use. [0074] At a block 422, the HCIS might display whatever items are specified for the custom form 424. At a block 426, the scheduler supplies responses to those items. [0075] At a block 430, when the scheduler has elected to file the responses to the decision support prompting, any custom logic specified in a programming point will be applied to the responses. As shown at a block 432, depending on what logic is written into the programming point, the HCIS might lock down scheduling of certain visit types, replace certain visit types, recommend visit types, recommend panels of visit types, recommend providers, recommend pools of providers or resources, select pools of providers or resources, initiate medical necessity checking, etc. [0076] Although the technique for providing healthcare organizations the ability to allow for the quick and easy scheduling of basic appointments while also presenting the scheduler with robust decision support tools for more complex visit types and consequently replacing the user's initial visit type choice with a more appropriate system generated choice described herein, is preferably implemented in software, it may be implemented in hardware, firmware, etc., and may be implemented by any other processor associated with a healthcare enterprise. Thus, the routine(s) described herein may be implemented in a standard multi-purpose CPU or on specifically designed hardware or firmware as desired. When implemented in software, the software routine(s) may be stored in any computer readable memory such as on a magnetic disk, a laser disk, or other machine accessible storage medium, in a RAM or ROM of a computer or processor, etc. Likewise, the software may be delivered to a user or process control system via any known or desired delivery method including, for example, on a computer readable disk or other transportable computer storage mechanism or over a communication channel such as a telephone line, the Internet, etc. (which are viewed as being the same as or interchangeable with providing such software via transportable storage medium). [0077] While the present invention has been described with reference to specific examples, which are intended to be illustrative only and not to be limiting of the invention, it will be apparent to those of ordinary skill in the art that changes, additions or deletions may be made to the disclosed embodiments without departing from the spirit and scope of the invention. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8140370 *Apr 5, 2005Mar 20, 2012Epic Systems CorporationSystem and method for reducing the steps involved in searching for available appointment times and scheduling appointments in a health care environmentUS8429547 *Feb 3, 2010Apr 23, 2013Universal Research Solutions, LlcGeneration and data management of a medical study using instruments in an integrated media and medical systemUS8498881Feb 3, 2010Jul 30, 2013Universal Research Solutions, LlcGeneration and data management of a medical study using instruments in an integrated media and medical systemUS8583453Feb 3, 2010Nov 12, 2013Universal Research Solutions, LlcGeneration and data management of a medical study using instruments in an integrated media and medical systemUS8627221 *Apr 22, 2013Jan 7, 2014Universal Research Solutions, LlcGeneration and data management of a medical study using instruments in an integrated media and medical systemUS8756072May 5, 2010Jun 17, 2014Universal Research Solutions, LlcGeneration and data management of a medical study using instruments in an integrated media and medical systemUS8782063May 5, 2010Jul 15, 2014Universal Research Solutions, LlcGeneration and data management of a medical study using instruments in an integrated media and medical systemUS20110093796 *Feb 3, 2010Apr 21, 2011Otho Raymond PlummerGeneration and data management of a medical study using instruments in an integrated media and medical systemWO2011050082A2 *Oct 20, 2010Apr 28, 2011Universal Research Solutions LLCGeneration and data management of a medical study using instruments in an integrated media and medical system* Cited by examinerClassifications U.S. Classification1/1, 707/999.001International ClassificationG06Q10/06, G06Q10/10Cooperative ClassificationG06Q10/1095, G06Q10/109, G06Q10/063116European ClassificationG06Q10/109, G06Q10/1095, G06Q10/06311FLegal EventsDateCodeEventDescriptionJan 8, 2015FPAYFee paymentYear of fee payment: 4Nov 7, 2003ASAssignmentOwner name: EPIC SYSTEMS CORPORATION, WISCONSINFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LARSEN, STEVEN J.;GROVER, SAMEER;DEROSE, MARIE C.;REEL/FRAME:014667/0614Effective date: 20031031RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services