In medical imaging, some exams are processed using computerized advanced processing, such as Computer Aided Diagnosis (CAD) systems, quantitative analysis (blood flow, volumetrics, image enhancement, etc.), or other processing systems, for example. With continued progress in the fields of Artificial Intelligence, image processing, and image analysis, it is anticipated that the use of CAD and advanced processing will grow over time and their use will become routine in the future.
The systems, methods, and devices described herein each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of this disclosure, several non-limiting features will now be described briefly.
According to an embodiment, a computing system is disclosed that comprises: one or more hardware computer processors configured to execute software instructions; and one or more electronic storage devices in communication with the one or more hardware computer processors and storing software modules, the software modules comprising software instructions configured for execution by the one or more hardware computer processors in order to cause the computing system to: access, from one or more image storage devices, an image series comprising one or more medical images; determine an exam characteristic associated with the image series, the exam characteristic including a result of a previously run computerized advanced processing technique; access, from a computerized advanced processing data structure, rules for execution of respective computerized advanced processing techniques, the rules indicating: one or more associations between exam characteristics and corresponding computerized advanced processing techniques, the exam characteristics including at least a modality and exam type; and one or more criteria associated with respective computerized advanced processing techniques for automatically initiating execution of corresponding computerized advanced processing techniques; determine, based on the rules, one or more computerized advanced processing techniques associated with the determined exam characteristic of the image series; and for each of the determined computerized advanced processing techniques: in response to determining that criteria associated with the computerized advanced processing technique are satisfied, automatically initiate execution of the computerized advanced processing technique on the image series.
According to another embodiment, a computing system is disclosed that comprises: one or more hardware computer processors configured to execute software instructions; and one or more electronic storage devices in communication with the one or more hardware computer processors and storing software modules, the software modules comprising software instructions configured for execution by the one or more hardware computer processors in order to cause the computing system to: access, from one or more image storage devices, an image series comprising one or more medical images; determine an exam characteristic associated with the image series; access a computerized advanced processing data structure including rules for executing respective computerized advanced processing techniques based on corresponding exam characteristics; identify one or more rules that are matched by the exam characteristic; and initiate execution of computerized advanced processing techniques associated with the identified one or more rules that are matched by the exam characteristic.
According to yet another embodiment, a computing system is disclosed that comprises: one or more hardware computer processors configured to execute software instructions; and one or more electronic storage devices in communication with the one or more hardware computer processors and storing software modules, the software modules comprising software instructions configured for execution by the one or more hardware computer processors in order to cause the computing system to: access, from one or more image storage devices, one or more image series each comprising one or more medical images; access a computerized advanced processing data structure including rules indicating respective computerized advanced processing techniques available for respective subsets of characteristics associated with medical data; identify one or more rules that are matched by characteristics of a particular one or more image series; and generate a user interface for display to a user, the user interface including information regarding computerized advanced processing techniques associated with the identified one or more rules that are matched by characteristics of the particular one or more image series.
According to another embodiment, a computing system is disclosed that comprises: one or more hardware computer processors configured to execute software instructions; and one or more electronic storage devices in communication with the one or more hardware computer processors and storing software modules, the software modules comprising software instructions configured for execution by the one or more hardware computer processors in order to cause the computing system to: access, from one or more image storage devices, an image series comprising one or more medical images; determine a characteristic associated with a first computerized advanced processing technique applied to the image series; access a computerized advanced processing data structure including rules for executing computerized advanced processing techniques based on characteristics of previously applied computerized advanced processing techniques; identify a rule that corresponds to the determined characteristic associated with the first computerized advanced processing technique, the rule indicating execution of a second computerized advanced processing technique; and initiate application of the second computerized advanced processing technique to the image series.
Embodiments of the disclosure will now be described with reference to the accompanying figures, wherein like numerals refer to like elements throughout. The terminology used in the description presented herein is not intended to be interpreted in any limited or restrictive manner, simply because it is being utilized in conjunction with a detailed description of certain specific embodiments of the disclosure. Furthermore, embodiments of the disclosure may include several novel features, no single one of which is solely responsible for its desirable attributes or which is essential to practicing the embodiments of the disclosure herein described.
In various embodiments, systems and methods are disclosed for automatically managing how and when computerized advanced processing techniques (for example, CAD and/or other image processing) are used. In some embodiments, the systems and methods discussed herein allow users, such as radiologists, to efficiently interact with a wide variety of computerized advanced processing (“CAP”) techniques using computing devices ranging from Picture Archiving and Communications System (PACS) workstations to handheld devices such as smartphone, tablets, or even smart watches. Furthermore, the systems and methods may, in various embodiments, automatically manage how data associated with these CAP techniques (for example, results of application of one or more computerized advanced processing techniques) are used, such as how data associated with the computerized analyses is reported, whether comparisons to prior abnormalities should be automatically initiated, whether the radiologist should be alerted of important findings, and the like.
In order to facilitate an understanding of the systems and methods discussed herein, certain terms may be defined in this document. Such terms should be construed to include the provided definitions, the ordinary and customary meaning of the terms, and/or any other implied meaning for the respective terms. Accordingly, any definitions provided herein do not limit the meaning of the defined terms, but only provide exemplary definitions.
The term CAP (computerized advanced processing), as use herein, should be interpreted to cover one or more of the various computerized image analyses, image analysis techniques, and/or image processing techniques discussed herein, and/or any similar computerized processing techniques that are currently or later available. CAP will be described herein with regard to radiology images, but CAP and the systems and methods described herein may be applied in other areas including, but not limited to, other types of medical images (for example, cardiology, dermatology, pathology and/or endoscopy, among others), computer generated images (for example, 3D images from virtual colonoscopy, 3D images of vessels from CTA, and the like), images from other fields (for example, surveillance imaging, satellite imaging, and the like), as well as non-imaging data including audio, text, and numeric data. In some embodiments, CAP may include, but is not limited to, volumetric rendering, multiplanar reconstruction (MPR), maximum intensity projection (MIP), other image processing techniques, and the like.
Example Computing Systems
The computing device 150, also referred to herein as “device 150,” may take various forms. In one embodiment, the computing device 150 may be an information display computing device, and/or a computer workstation having information display software modules 151. In other embodiments, software modules 151 may reside on another computing device, such as a web server or other server, and a user directly interacts with a second computing device that is connected to the web server via a computer network.
In one embodiment, the computing device 150 comprises one or more computing devices, such as a server, a desktop computer, a workstation, a laptop computer, a mobile computer, a smartphone, a tablet computer, a cell phone, a personal digital assistant, a gaming system, a kiosk, an audio player, and/or any other device that utilizes a graphical user interface, such as office equipment, automobiles, airplane cockpits, household appliances, automated teller machines, self-service checkouts at stores, information and other kiosks, ticketing kiosks, vending machines, industrial equipment, and/or a television, for example.
The computing device 150 may run an off-the-shelf operating system 154 such as a Windows, Linux, MacOS, Android, or iOS. The computing device 150 may also run a more specialized operating system which may be designed for the specific tasks performed by the computing device 150.
The computing device 150 may include one or more computer processors 152, for example, hardware computer processors. The computer processors 152 may include central processing units (CPUs), and may further include dedicated processors such as graphics processor chips, or other specialized processors. The processors may be used to execute computer instructions based on the modules 151 to cause the computing device to perform operations as specified by the modules 151. The modules 151 may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. For example, modules may include software code written in a programming language, such as, for example, Java, JavaScript, ActionScript, Visual Basic, HTML, Lua, C, C++, or C#. While “modules” are generally discussed herein with reference to software, any modules may alternatively be represented in hardware or firmware. In various embodiments, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage.
The computing device 150 may also include memory 153. The memory 153 may include volatile data storage such as RAM or SDRAM. The memory 153 may also include more permanent forms of storage such as a hard disk drive, a flash disk, flash memory, a solid state drive, or some other type of non-volatile storage.
The computing device 150 may also include or be interfaced to one or more display devices 155 that provide information to users of the computing device. Display devices 155 may include a video display, such as one or more high-resolution computer monitors, or a display device integrated into or attached to a laptop computer, handheld computer, smartphone, computer tablet device, or medical scanner. In other embodiments, the display device 155 may include an LCD, OLED, or other thin screen display surface, a monitor, television, projector, a display integrated into wearable glasses, or any other device that visually depicts user interfaces and data to viewers.
The computing device 150 may also include or be interfaced to one or more input devices 156 which receive input from users, such as a keyboard, trackball, mouse, 3D mouse, drawing tablet, joystick, game controller, touch sensitive surface (for example, capacitive or resistive touch screen), touchpad, accelerometer, video camera and/or microphone.
The computing device 150 may also include one or more interfaces 157 which allow information exchange between computing device 150 and other computers and input/output devices using systems such as Ethernet, Wi-Fi, Bluetooth, as well as other wired and wireless data communications techniques.
The modules of the computing device 150 may be connected using a standard based bus system. In different embodiments, the standard based bus system could be Peripheral Component Interconnect (“PCI”), PCI Express, Accelerated Graphics Port (“AGP”), Micro channel, Small Computer System Interface (“SCSI”), Industrial Standard Architecture (“ISA”) and Extended ISA (“EISA”) architectures, for example. In addition, the functionality provided for in the components and modules of computing device 150 may be combined into fewer components and modules or further separated into additional components and modules.
The computing device 150 may communicate and/or interface with other systems and/or devices. In one or more embodiments, the computer device 150 may be connected to a computer network 190. The computer network 190 may take various forms. For example, the computer network 190 may be a wired network or a wireless network, or it may be some combination of both. The computer network 190 may be a single computer network, or it may be a combination or collection of different networks and network protocols. Additionally, the computer network 190 may include one or more local area networks (LAN), wide area networks (WAN), personal area networks (PAN), cellular or data networks, and/or the Internet.
Various devices and subsystems may be connected to the network 190. For example, one or more medical scanners may be connected, such as MRI scanners 120. The MRI scanner 120 may be used to acquire MRI images from patients, and may share the acquired images with other devices on the network 190. The network 190 may also include one or more CT scanners 122. The CT scanners 122 may also be used to acquire images and, like the MRI scanner 120, may then store those images and/or share those images with other devices via the network 190. Any other scanner or device capable of inputting or generating information that can be presented to the user as images, graphics, text or sound may be connected to the network 190, including, for example, computing systems used in the fields of ultrasound, angiography, nuclear medicine, radiography, endoscopy, pathology, dermatology, and the like.
Also connected to the network 190 may be a Picture Archiving and Communications System (PACS) 136 and PACS workstation 138. The PACS System 136 may be used for the storage, retrieval, distribution and presentation of images (such as those created and/or generated by the MRI scanner 120 and CT Scanner 122). The medical images may be stored in an independent format, an open source format, or some other proprietary format. A common format for image storage in the PACS system is the Digital Imaging and Communications in Medicine (DICOM) format. In various embodiments, the stored images may be transmitted digitally via the PACS system, often reducing or eliminating the need for manually creating, filing, or transporting film jackets.
The network 190 may also be connected to a Radiology Information System (RIS) 140. In an embodiment, the radiology information system 140 may be a computerized system that is used by radiology departments to store, manipulate and distribute patient radiological information.
Also attached to the network 190 may be an Electronic Medical Record (EMR) system 142. The EMR system 142 may be configured to store and make accessible to a plurality of medical practitioners computerized medical records. Also attached to the network 190 may be a Laboratory Information System 144. In an embodiment, the Laboratory Information System 144 may be a software system which stores information created or generated by clinical laboratories. Also attached to the network 190 may be a Digital Pathology System 146 that may be used to digitally manage and store information related to medical pathology.
Also attached to the network 190 may be one or more Computer Aided Diagnosis Systems (CAD) systems 148 (including CAD systems 148a, 148b, and/or any quantity of CAD systems) that are generally used to perform CAP such as, for example, CAD processes. In one embodiment, the CAD systems 148 functionality may reside in a computing device separate from computing device 150 while in another embodiment the CAD systems 148 functionality may reside within computing device 150.
Also attached to the network 190 may be one or more Processing Systems 149 (including Processing Systems 149a, 149b, and/or any quantity of Processing Systems) that may be used to perform CAP such as, for example, computations on imaging information to create new views of the information, for example, 3D volumetric display, Multiplanar Reconstruction (MPR), and Maximum Intensity Projection reconstruction (MIP), as well as other types of processing, for example image enhancement, volume quantification, blood-flow quantification, and the like. In one embodiment, such processing functionality may reside in a computing device separate from computing device 150 while in another embodiment the Processing functionality may reside within computing device 150.
Also connected to the network 190 may be a Web Server 147.
In the embodiment of
In the embodiment of
In other embodiments, other computing devices that store, provide, acquire, and/or otherwise manipulate medical data may also be coupled to the network 190 and may be in communication with one or more of the devices illustrated in
Depending on the embodiment, devices other than the computing device 150 that are illustrated in
Example Rules for Selection of One or More Computerized Advanced Processing
In some embodiments certain results of a CAP may automatically trigger the scheduling of another CAP (for example, based on the rules in column 408). For example, the modality and exam in rule 410 is associated with Brain MRI exams (as indicated in columns 402 and 404), and the indicated CAP of “MRI brain volumetric analysis” is associated with a rule (column 408) indicating that the CAP is automatically performed when the clinical indication is “dementia.”
In some embodiments, scheduling of a particular CAP, either automatically or manually, may automatically cause one or more other CAP to be scheduled before or after that particular CAP. For example, exam rule 412 indicates that scheduling of “Brain aneurysm detected CAD” should result in the automatic scheduling of “3D Vessel tracking” CAP, and that “3D Vessel tracking” CAP should be run before “Brain aneurysm detected CAD”, for example because “Brain aneurysm detected CAD” involves processing the results of “3D Vessel tracking” CAP.
In another example, the modality and exam in rule 411 is associated with Brain MRI exams (as indicated in columns 402 and 404), and the indicated CAP of “MRI brain CSF analysis” is associated with a rule (column 408) indicating that the CAP is automatically performed when the clinical indication is “hydrocephalus,” “dementia,” or there is an abnormal brain volumetric analysis from another CAP.
Thus, in an embodiment, the first CAP in rule 410 (“MRI Brain volumetric analysis”) may first be automatically performed on a brain MRI, such as in response to an indication of “dementia” in the MRI order from the referring doctor. Once the MRI brain volumetric analysis has been performed, the rules of
In one embodiment, a rules data structure may be used to determine which CAP are compatible and/or available for a particular one or more image series, such as based on various characteristics associated with the one or more image series. For example, a rules data structure comprising modality, exam, and CAD/processing, such as columns 402, 404, and 406 in the example of
In various embodiments, different rules may apply to different users and/or different user groups (for example, based on preferences of the users and/or user groups).
In various embodiments, rules related to CAP may be evaluated automatically, for example when:
In various embodiments, evaluation of rules related to CAP may be performed on one or more computing devices, such as scanners, PACS Systems, PACS Workstations, and the like. Based on the evaluation of rules related to CAP, one or more CAP may be automatically executed.
At block 430, the computing device 150 accesses CAP rules that are usable to determine when CAP are run are retrieved, for example, rules 408 and/or the rules of
At block 432, the computing device 150 evaluates the CAP rules in order to determine if one or more CAP should be executed, for example, based on modality, exam type, clinical indication, ordering physician preference, reading radiologist preference, insurance approval, results of other CAP, and the like.
If the computing device determines, at block 432, that there is no CAP to run automatically, the computing device 150 optionally accepts input from a radiologist, or other user indicating a CAP to be manually run. Such input from the radiologist may be received by the radiologist providing, for example, an input to the device 150 (and/or any other suitable computing device). If the input indicates that no CAP should be run, then no more action occurs within this logic, as indicated by block 442.
At block 434, a CAP is run, either because one was automatically selected at block 432, or because a manual command was received at block 440. In optional block 436, results of the CAP performed may be communicated to other processes. In one embodiment, the CAP results may be automatically communicated to various users. In one embodiment, CAP results may be communicated to a system used to create reports, such as Radiology Information System 140. Example embodiments are discussed herein with reference
At block 436 (or block 434 if block 436 is not included), the logic loops back to block 432 to determine whether additional CAP should be run. As discussed above, CAP rules may cause CAP to run based on the result of one or more other CAP. For example, a rule for executing a particular CAP may not have been met in a first run of blocks 432 and 434, but the rule may be met in a subsequent run of block 432 based on results of a CAP that was performed at block 434 of the first run.
Example User Interfaces
In some instances, users (for example, radiologists) may desire that all applicable CAP are complete before they view an exam. Thus, in some embodiments the modules 151 are configured to generate one or more user interfaces (UIs) that indicate status of various CAP. In the example of
In systems wherein exams are automatically chosen for reading (for example, downloaded to a particular workstation automatically and/or automatically prioritized), either on-the-fly or via building work lists, CAP statuses may be utilized. For example, a PACS workstation or other computing device (for example, computing device 150 or 250) may automatically retrieve exams for the user to read based on a number of factors, such as CAP completion status, exam status (Stat, routine, and the like), exam description, exam date, user's specialty, user preference, and/or any other related criteria. Thus, in some embodiments, the user may have a preference not to have exams still undergoing CAP (for example, status is not complete) included on a worklist for the user. In another embodiment, the completion status of CAP may be ignored for exams that have certain characteristics, such as those marked as STAT, otherwise emergent, and/or have some other characteristic. In another embodiment, a result of CAP, such as a result designated as a critical result, may cause a user to be automatically notified of the result and/or the exam to be prioritized in the reading queue.
In various embodiments, a user interface such as the UI of
Results of one or more CAP may include information that may be important for one or more users (for example, radiologist, referring doctor, and the like) to view. For example, in the case of CAD systems, in various embodiments the results may be one or more indicators that are superimposed on images to indicate to the user one or more of:
In various embodiments, certain CAP may determine one or more sets of indicators that may be superimposed on the images. In the embodiment of
In the example of
The UI further indicates that “3D Registration” is in progress and that the exams being registered are the exams dated Aug. 2, 2012, the current exam being viewed, and the exam of Apr. 5, 2012. In another embodiment, in addition to the dates of the exams being registered, other information about the exams may be displayed, for example, a modality, an exam type, an exam time, and the like. In one embodiment, the user may hover over or click on an item in the status list in order to view other information, for example, exam type, modality, exam type, and/or estimated time for completion of the CAP in progress, among other information. The other information may be displayed, for example, in a popup frame or under the status line.
The UI further indicates that the “Change Detection CAD” has been scheduled, and will be run after another CAP is complete, “3D Registration” in this example. The example UI of
In one embodiment, the user may click or otherwise select a CAP that has not been scheduled to cause it to be scheduled and/or change its priority with reference to other CAP. In one embodiment, additional information may be displayed, e.g., the estimated time for completion of the listed CAP or in indictor showing its completion status, e.g., a bar demonstrating that a cap is 60% completed.
Reporting CAP Results
There is a need to manage how the results of CAP are communicated, for example via reports of exams and/or other means (for example, automatic communication to a doctor interpreting the exam, a doctor who ordered the exam, a doctor providing care for the patient, an electronic medical record, or a database). In one embodiment, the modules 151 (and/or other systems that coordinate selection and initiation of various CAP as discussed above) are configured to automatically put CAP results in a report associated with an exam. The modules 151 may automatically alert a user (for example, a doctor) if a CAP detects a significant abnormality in an exam that has not yet been viewed. In another embodiment, when a CAP detects a result that is designated as significant or emergent (for example, based on rules stored in Computerized Advanced Processing Rules Data Structure 160) the result may be automatically communicated, for example, to one or more of a doctor who ordered the exam, a doctor providing care for the patient, an electronic medical record, a database, and/or the like. In one embodiment, automatic communication of a significant or emergent result detected by a CAP may occur before the exam has been viewed by a user. In one embodiment, automatic communication of a significant or emergent result detected by a CAP may occur after the exam has been viewed by a user.
In one embodiment, alerts and/or other actions to be taken based on results of one or more CAP may be stored in an alert data structure that contains rules for providing alerts and/or taking other actions. For example, rules may indicate that important or other types of results generated by CAP result in automatic action, for example automatic alerting of a user or other communication of results. The alert data structure may include multiple delivery options, such as delivery mediums (for example, email, SMS, phone, etc.), delivery schedules (for example, only certain alerts may be delivered outside of pre-set work hours), destinations (for example, certain alerts may go to an entire medical group, while others only go to a referring physician), and/or other similar alert parameters. In one embodiment, the alert data structure stores results of performed CAP(s) that may be included in alerts, either before or after a report is generated and/or marked as read.
At block 710, results of a CAP and/or an indication that results of the CAP are available are received by the computing device 150.
Next, at block 712 the received CAP results are evaluated in light of CAP processing rules to determine if the CAP results are to be automatically communicated to one or more users, devices, systems, etc. In one example, the CAP processing rules may indicate that only significant results may be communicated automatically (and may include criteria for what qualifies as a significant result), whereas in another example all results may be automatically communicated, depending on rules configured for individuals, groups, and/or sites.
If the computing device 150 determines, at block 712, that the CAP results are to be automatically communicated, the method continues to block 714 wherein CAP communication preferences are retrieved, for example, from CAP Communication Preferences Data Structure 162. For example, CAP communication preferences may indicate that a significant finding detected by CAP, such as detection of a pneumothorax on a chest x-ray or chest CT scan, is to be treated as a significant finding requiring immediate communication. Information in the CAP Communications Preferences Data Structure may indicate that significant findings be communicated automatically to the ordering physician, the hospitalist currently caring for the patient, and/or the radiologist current reading cases or on call. Information in the CAP Communications Preferences Data Structure might also include the preferred method of communication set by each user, for example, text, email, phone call, and/or the like.
Moving to block 716, the CAP results are automatically communicated based on the preceding determinations, such as to one or more users, devices, systems, etc., via one or more communication mediums, and including certain portions of the CAP results possible in custom formats. Thus, CAP results may be sent to two different users via different communication mediums (e.g., one via email and another via text message) including different portions of the CAP results (e.g., all of the report in an email vs. only a summary of the report in a text message). In one embodiment, automated communications are automatically logged. When it is determined that no results to be automatically communicated, the process stops at block 718.
In various embodiments, the modules 151 may further be configured to provide one or more of various alerts as an exam is being viewed. For example, the modules 151 may be configured to initiate alerts to the user in response to one or more of:
Beginning at block 730, results of a CAP and/or an indication that results of the CAP are available are received by the computing device 150.
At block 732, rules are evaluated to determine whether the CAP results should be incorporated into a medical report and/or other document or file. These rules may be stored in CAP Rules Data Structure 160. By way of example, a rule may indicate that only positive CAP results be included in the reports. For example, if significant midline shift is detected by a computer aided diagnosis system, a form of CAP that may be used to evaluate a brain CT, the significant result may be automatically included in the report. In another example, another rule may indicate that all CAP results, or some other subset of results that are selected based on rule criteria, are automatically incorporated into the report, regardless of the result, such as a CSF volumetric assessment of a brain MRI. Rules may incorporate preferences of individual users, groups, and/or sites. For example, one radiologist may configure the system so that the results of a particular CAP are automatically incorporated into his reports, while another might indicate that the CAP results should not be automatically incorporated.
At block 736, the CAP results are incorporated into the report. Alternatively, when it is determined that no CAP results are to be included in the report, the process stops at block 738.
Beginning at block 810, a radiologist or other reader attempts to mark the exam he is reading as “read,” indicating that he has completed his evaluation of the exam and desires to finalize the report on the exam.
At block 812, the system determines whether or not a significant finding was detected by a CAP run on the exam. Rules determining which results are “significant” may be stored in a data structure, such as CAP Rules Data Structure 160. Rules may be set by various users, such as individual radiologists and/or ordering physicians, and/or by groups of users. For example, detection of a subdural hematoma by a CAD processing of a brain CT may be an example of a significant finding.
At block 812, if it is determined that no significant finding was detected by CAP associated with the exam, then the radiologist may mark the exam as read at block 814.
Alternatively, at block 812, if it is determined that a significant finding was detected, then at block 816, the system may determine whether or not the significant finding is documented in the report, for example, because it was automatically added by the system or manually added by the radiologist.
If the significant finding is not in the report, then at block 818 the radiologist is notified that the significant finding is not documented in the report so that he has the opportunity to add the finding to the report. In various embodiments, the radiologist may be notified by, for example, a visual, audible, and/or tactile indicator. For example, the radiologist may be prompted by a message or flashing indicator on the display, or an audible alarm. If, at block 816, it is determined that the significant finding is in the report, the system proceeds to block 820.
At block 820, CAP processing rules are used to determine whether or not the significant finding should be automatically communicated, for example, to the physician caring for the patient and/or the physician who ordered the imaging exam. If it is determined that there are no rules that indicate that the significant finding should be automatically communicated, then at optional block 830 the radiologist is notified that the system is not going to automatically communicate the significant finding. At optional block 832, the radiologist may indicate that he would like the system to communicate the findings, for example, to the physician caring for the patient.
At block 822, performed in preparation for communicating the finding, CAP communications preferences are retrieved, for example, from CAP Communication Preferences Data Structure 162, to determine the mode of automated communication, for example, text, pager, email, phone call, and/or the like.
At block 824, the significant finding is communicated to the designated and/or indicated user. At optional block 826, the results of the automated communication may be automatically documented, for example, in the report and/or another record.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
All of the methods and processes described above may be embodied in, and partially or fully automated via, software code modules executed by one or more general purpose computers. For example, the methods described herein may be performed by an information display computing device and/or any other suitable computing device. The methods may be executed on the computing devices in response to execution of software instructions or other executable code read from a tangible computer readable medium. A tangible computer readable medium is a data storage device that can store data that is readable by a computer system. Examples of computer readable mediums include read-only memory, random-access memory, other volatile or non-volatile memory devices, CD-ROMs, magnetic tape, flash drives, and optical data storage devices.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated.
This application is a divisional of U.S. patent application Ser. No. 14/139,068, filed Dec. 23, 2013, which claims the benefit of priority under 35 U.S.C. § 119(e) of U.S. Provisional Application No. 61/750,662, filed Jan. 9, 2013, the disclosures of which are hereby incorporated by reference herein in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
4672683 | Matsueda | Jun 1987 | A |
5123056 | Wilson | Jun 1992 | A |
5172419 | Manian | Dec 1992 | A |
5179651 | Taaffe et al. | Jan 1993 | A |
5431161 | Ryals et al. | Jul 1995 | A |
5452416 | Hilton et al. | Sep 1995 | A |
5515375 | DeClerck | May 1996 | A |
5542003 | Wofford | Jul 1996 | A |
5734915 | Roewer | Mar 1998 | A |
5740267 | Echerer et al. | Apr 1998 | A |
5779634 | Ema et al. | Jul 1998 | A |
5807256 | Taguchi et al. | Sep 1998 | A |
5835030 | Tsutsui et al. | Nov 1998 | A |
5852646 | Klotz et al. | Dec 1998 | A |
5857030 | Gaborski | Jan 1999 | A |
5926568 | Chaney et al. | Jul 1999 | A |
5954650 | Saito et al. | Sep 1999 | A |
5976088 | Urbano et al. | Nov 1999 | A |
5986662 | Argiro | Nov 1999 | A |
5987345 | Engelmann et al. | Nov 1999 | A |
5995644 | Lai et al. | Nov 1999 | A |
6008813 | Lauer et al. | Dec 1999 | A |
6115486 | Cantoni | Sep 2000 | A |
6128002 | Leiper | Oct 2000 | A |
6130671 | Argiro | Oct 2000 | A |
6151581 | Kraftson et al. | Nov 2000 | A |
6175643 | Lai et al. | Jan 2001 | B1 |
6177937 | Stockham et al. | Jan 2001 | B1 |
6185320 | Bick et al. | Feb 2001 | B1 |
6211795 | Izuta | Apr 2001 | B1 |
6211884 | Knittel et al. | Apr 2001 | B1 |
6219059 | Argiro | Apr 2001 | B1 |
6219061 | Lauer et al. | Apr 2001 | B1 |
6243095 | Shile et al. | Jun 2001 | B1 |
6243098 | Lauer et al. | Jun 2001 | B1 |
6262740 | Lauer et al. | Jul 2001 | B1 |
6266733 | Knittel et al. | Jul 2001 | B1 |
6269379 | Hiyama et al. | Jul 2001 | B1 |
6297799 | Knittel et al. | Oct 2001 | B1 |
6304667 | Reitano | Oct 2001 | B1 |
6310620 | Lauer et al. | Oct 2001 | B1 |
6313841 | Ogata et al. | Nov 2001 | B1 |
6342885 | Knittel et al. | Jan 2002 | B1 |
6347329 | Evans | Feb 2002 | B1 |
6351547 | Johnson et al. | Feb 2002 | B1 |
6356265 | Knittel et al. | Mar 2002 | B1 |
6369816 | Knittel et al. | Apr 2002 | B1 |
6383135 | Chikovani et al. | May 2002 | B1 |
6388687 | Brackett et al. | May 2002 | B1 |
6404429 | Knittel | Jun 2002 | B1 |
6407737 | Zhao et al. | Jun 2002 | B1 |
6411296 | Knittel et al. | Jun 2002 | B1 |
6421057 | Lauer et al. | Jul 2002 | B1 |
6424346 | Correll et al. | Jul 2002 | B1 |
6424996 | Killcommons et al. | Jul 2002 | B1 |
6426749 | Knittel et al. | Jul 2002 | B1 |
6427022 | Craine et al. | Jul 2002 | B1 |
6438533 | Spackman et al. | Aug 2002 | B1 |
6463169 | Ino et al. | Oct 2002 | B1 |
6476810 | Simha et al. | Nov 2002 | B1 |
6512517 | Knittel et al. | Jan 2003 | B1 |
6532299 | Sachdeva et al. | Mar 2003 | B1 |
6532311 | Pritt | Mar 2003 | B1 |
6556695 | Packer et al. | Apr 2003 | B1 |
6556724 | Chang et al. | Apr 2003 | B1 |
6563950 | Wiskott et al. | May 2003 | B1 |
6574629 | Cooke, Jr. et al. | Jun 2003 | B1 |
6577753 | Ogawa | Jun 2003 | B2 |
6603494 | Banks et al. | Aug 2003 | B1 |
6606171 | Renk et al. | Aug 2003 | B1 |
6614447 | Bhatia et al. | Sep 2003 | B1 |
6618060 | Brackett | Sep 2003 | B1 |
6621918 | Hu et al. | Sep 2003 | B1 |
6630937 | Kallergi et al. | Oct 2003 | B2 |
6650766 | Rogers et al. | Nov 2003 | B1 |
6654012 | Lauer et al. | Nov 2003 | B1 |
6678764 | Parvelescu et al. | Jan 2004 | B2 |
6680735 | Seiler et al. | Jan 2004 | B1 |
6683933 | Saito et al. | Jan 2004 | B2 |
6697067 | Callahan et al. | Feb 2004 | B1 |
6697506 | Oian et al. | Feb 2004 | B1 |
6734880 | Chang et al. | May 2004 | B2 |
6760755 | Brackett | Jul 2004 | B1 |
6775402 | Bacus et al. | Aug 2004 | B2 |
6778689 | Aksit et al. | Aug 2004 | B1 |
6820093 | de la Huerga | Nov 2004 | B2 |
6820100 | Funahashi | Nov 2004 | B2 |
6826297 | Saito et al. | Nov 2004 | B2 |
6829377 | Milioto | Dec 2004 | B2 |
6864794 | Betz | Mar 2005 | B2 |
6886133 | Bailey et al. | Apr 2005 | B2 |
6891920 | Minyard et al. | May 2005 | B1 |
6894707 | Nemoto | May 2005 | B2 |
6909436 | Pianykh et al. | Jun 2005 | B1 |
6909795 | Tecotzky et al. | Jun 2005 | B2 |
6917696 | Soenksen | Jul 2005 | B2 |
6988075 | Hacker | Jan 2006 | B1 |
6996205 | Capolunghi et al. | Feb 2006 | B2 |
7016952 | Mullen et al. | Mar 2006 | B2 |
7022073 | Fan et al. | Apr 2006 | B2 |
7027633 | Foran et al. | Apr 2006 | B2 |
7031504 | Argiro et al. | Apr 2006 | B1 |
7031846 | Kaushikkar et al. | Apr 2006 | B2 |
7039723 | Hu et al. | May 2006 | B2 |
7043474 | Mojsilovic | May 2006 | B2 |
7050620 | Heckman | May 2006 | B2 |
7054473 | Roehrig et al. | May 2006 | B1 |
7058901 | Hafey et al. | Jun 2006 | B1 |
7092572 | Huang et al. | Aug 2006 | B2 |
7103205 | Wang et al. | Sep 2006 | B2 |
7106479 | Roy et al. | Sep 2006 | B2 |
7110616 | Ditt et al. | Sep 2006 | B2 |
7113186 | Kim et al. | Sep 2006 | B2 |
7123684 | Jing et al. | Oct 2006 | B2 |
7136064 | Zuiderveld | Nov 2006 | B2 |
7139416 | Vuylsteke | Nov 2006 | B2 |
7149334 | Dehmeshki | Dec 2006 | B2 |
7155043 | Daw | Dec 2006 | B2 |
7162623 | Yngvesson | Jan 2007 | B2 |
7170532 | Sako | Jan 2007 | B2 |
7174054 | Manber et al. | Feb 2007 | B2 |
7209149 | Jogo | Apr 2007 | B2 |
7209578 | Saito et al. | Apr 2007 | B2 |
7212661 | Samara et al. | May 2007 | B2 |
7218763 | Belykh et al. | May 2007 | B2 |
7224852 | Lipton et al. | May 2007 | B2 |
7236558 | Saito et al. | Jun 2007 | B2 |
7260249 | Smith | Aug 2007 | B2 |
7263710 | Hummel et al. | Aug 2007 | B1 |
7272610 | Torres | Sep 2007 | B2 |
7346199 | Pfaff | Mar 2008 | B2 |
7366992 | Thomas, III | Apr 2008 | B2 |
7379578 | Soussaline et al. | May 2008 | B2 |
7412111 | Battle et al. | Aug 2008 | B2 |
7450747 | Jabri et al. | Nov 2008 | B2 |
7492970 | Saito et al. | Feb 2009 | B2 |
7505782 | Chu | Mar 2009 | B2 |
7516417 | Amador et al. | Apr 2009 | B2 |
7525554 | Morita et al. | Apr 2009 | B2 |
7526114 | Xia et al. | Apr 2009 | B2 |
7526132 | Koenig | Apr 2009 | B2 |
7545965 | Suzuki et al. | Jun 2009 | B2 |
7574029 | Peterson et al. | Aug 2009 | B2 |
7583861 | Hanna et al. | Sep 2009 | B2 |
7590272 | Brejl et al. | Sep 2009 | B2 |
7599534 | Krishnan | Oct 2009 | B2 |
7613335 | McLennan et al. | Nov 2009 | B2 |
7634121 | Novatzky et al. | Dec 2009 | B2 |
7636413 | Toth | Dec 2009 | B2 |
7639879 | Goto et al. | Dec 2009 | B2 |
7656543 | Atkins | Feb 2010 | B2 |
7660481 | Schaap et al. | Feb 2010 | B2 |
7660488 | Reicher et al. | Feb 2010 | B2 |
7668352 | Tecotzky et al. | Feb 2010 | B2 |
7683909 | Takekoshi | Mar 2010 | B2 |
7698152 | Reid | Apr 2010 | B2 |
7716277 | Yamatake | May 2010 | B2 |
7787672 | Reicher et al. | Aug 2010 | B2 |
7834891 | Yarger et al. | Nov 2010 | B2 |
7835560 | Vining et al. | Nov 2010 | B2 |
7885440 | Fram et al. | Feb 2011 | B2 |
7885828 | Glaser-Seidnitzer et al. | Feb 2011 | B2 |
7899514 | Kirkland | Mar 2011 | B1 |
7920152 | Fram et al. | Apr 2011 | B2 |
7941462 | Akinyemi et al. | May 2011 | B2 |
7953614 | Reicher | May 2011 | B1 |
7970188 | Mahesh et al. | Jun 2011 | B2 |
7970625 | Reicher et al. | Jun 2011 | B2 |
7991210 | Peterson et al. | Aug 2011 | B2 |
8019138 | Reicher et al. | Sep 2011 | B2 |
8046044 | Stazzone et al. | Oct 2011 | B2 |
8050938 | Green, Jr. et al. | Nov 2011 | B1 |
8065166 | Maresh et al. | Nov 2011 | B2 |
8073225 | Hagen et al. | Dec 2011 | B2 |
8094901 | Reicher et al. | Jan 2012 | B1 |
8150708 | Kotula et al. | Apr 2012 | B2 |
8214756 | Salazar-Ferrer | Jul 2012 | B2 |
8217966 | Fram et al. | Jul 2012 | B2 |
8244014 | Reicher et al. | Aug 2012 | B2 |
8249687 | Peterson et al. | Aug 2012 | B2 |
8262572 | Chono | Sep 2012 | B2 |
8292811 | Relkuntwar et al. | Oct 2012 | B2 |
8298147 | Huennekens et al. | Oct 2012 | B2 |
8370293 | Iwase et al. | Feb 2013 | B2 |
8379051 | Brown | Feb 2013 | B2 |
8380533 | Reicher et al. | Feb 2013 | B2 |
8391643 | Melbourne et al. | Mar 2013 | B2 |
8406491 | Gee et al. | Mar 2013 | B2 |
8452063 | Wojton et al. | May 2013 | B2 |
8457990 | Reicher et al. | Jun 2013 | B1 |
8520978 | Jakobovits | Aug 2013 | B2 |
8554576 | Reicher et al. | Oct 2013 | B1 |
8560050 | Martin et al. | Oct 2013 | B2 |
8610746 | Fram et al. | Dec 2013 | B2 |
8626527 | Reicher et al. | Jan 2014 | B1 |
8693757 | Gundel | Apr 2014 | B2 |
8712120 | Reicher et al. | Apr 2014 | B1 |
8731259 | Reicher et al. | May 2014 | B2 |
8751268 | Reicher et al. | Jun 2014 | B1 |
8797350 | Fram | Aug 2014 | B2 |
8879807 | Fram et al. | Nov 2014 | B2 |
8913808 | Reicher et al. | Dec 2014 | B2 |
8954884 | Barger | Feb 2015 | B1 |
8976190 | Westerhoff et al. | Mar 2015 | B1 |
9042617 | Reicher et al. | May 2015 | B1 |
9075899 | Reicher | Jul 2015 | B1 |
9092551 | Reicher | Jul 2015 | B1 |
9092727 | Reicher | Jul 2015 | B1 |
9324188 | Fram et al. | Apr 2016 | B1 |
9386084 | Reicher et al. | Jul 2016 | B1 |
9471210 | Fram et al. | Oct 2016 | B1 |
9495604 | Fram | Nov 2016 | B1 |
9501617 | Reicher et al. | Nov 2016 | B1 |
9501627 | Reicher et al. | Nov 2016 | B2 |
9501863 | Fram et al. | Nov 2016 | B1 |
9542082 | Reicher et al. | Jan 2017 | B1 |
9672477 | Reicher et al. | Jun 2017 | B1 |
9684762 | Reicher et al. | Jun 2017 | B2 |
9727938 | Reicher et al. | Aug 2017 | B1 |
9734576 | Fram et al. | Aug 2017 | B2 |
9754074 | Reicher et al. | Sep 2017 | B1 |
9836202 | Reicher et al. | Dec 2017 | B1 |
10157686 | Reicher et al. | Dec 2018 | B1 |
10387612 | Wu et al. | Aug 2019 | B2 |
10540763 | Reicher et al. | Jan 2020 | B2 |
10579903 | Reicher | Mar 2020 | B1 |
20010016822 | Bessette | Aug 2001 | A1 |
20010042124 | Barron | Nov 2001 | A1 |
20020016718 | Rothschild et al. | Feb 2002 | A1 |
20020021828 | Papier et al. | Feb 2002 | A1 |
20020039084 | Yamaguchi | Apr 2002 | A1 |
20020044696 | Sirohey et al. | Apr 2002 | A1 |
20020070970 | Wood et al. | Jun 2002 | A1 |
20020073429 | Beane et al. | Jun 2002 | A1 |
20020090118 | Olschewski | Jul 2002 | A1 |
20020090119 | Saito et al. | Jul 2002 | A1 |
20020090124 | Soubelet et al. | Jul 2002 | A1 |
20020091659 | Beaulieu et al. | Jul 2002 | A1 |
20020103673 | Atwood | Aug 2002 | A1 |
20020103827 | Sesek | Aug 2002 | A1 |
20020106119 | Foran et al. | Aug 2002 | A1 |
20020110285 | Wang et al. | Aug 2002 | A1 |
20020144697 | Betz | Oct 2002 | A1 |
20020145941 | Poland et al. | Oct 2002 | A1 |
20020172408 | Saito et al. | Nov 2002 | A1 |
20020172409 | Saito et al. | Nov 2002 | A1 |
20020180883 | Tomizawa et al. | Dec 2002 | A1 |
20020186820 | Saito | Dec 2002 | A1 |
20020190984 | Seiler et al. | Dec 2002 | A1 |
20030005464 | Gropper et al. | Jan 2003 | A1 |
20030013951 | Stefanescu | Jan 2003 | A1 |
20030016850 | Kaufman et al. | Jan 2003 | A1 |
20030028402 | Ulrich et al. | Feb 2003 | A1 |
20030034973 | Zuiderveld | Feb 2003 | A1 |
20030037054 | Dutta et al. | Feb 2003 | A1 |
20030055896 | Hu et al. | Mar 2003 | A1 |
20030065613 | Smith | Apr 2003 | A1 |
20030071829 | Bodicker et al. | Apr 2003 | A1 |
20030101291 | Mussack et al. | May 2003 | A1 |
20030115083 | Masarie et al. | Jun 2003 | A1 |
20030120516 | Perednia | Jun 2003 | A1 |
20030130973 | Sumner, II et al. | Jul 2003 | A1 |
20030140044 | Mok et al. | Jul 2003 | A1 |
20030140141 | Mullen et al. | Jul 2003 | A1 |
20030156745 | Saito et al. | Aug 2003 | A1 |
20030160095 | Segal | Aug 2003 | A1 |
20030164860 | Shen et al. | Sep 2003 | A1 |
20030184778 | Chiba | Oct 2003 | A1 |
20030187689 | Barnes et al. | Oct 2003 | A1 |
20030190062 | Noro et al. | Oct 2003 | A1 |
20030204420 | Wilkes et al. | Oct 2003 | A1 |
20030215120 | Uppaluri et al. | Nov 2003 | A1 |
20030215122 | Tanaka | Nov 2003 | A1 |
20040008900 | Jabri et al. | Jan 2004 | A1 |
20040015703 | Madison et al. | Jan 2004 | A1 |
20040024303 | Banks | Feb 2004 | A1 |
20040027359 | Aharon et al. | Feb 2004 | A1 |
20040061889 | Wood et al. | Apr 2004 | A1 |
20040068170 | Wang et al. | Apr 2004 | A1 |
20040077952 | Rafter et al. | Apr 2004 | A1 |
20040086163 | Moriyama et al. | May 2004 | A1 |
20040088192 | Schmidt et al. | May 2004 | A1 |
20040105030 | Yamane | Jun 2004 | A1 |
20040105574 | Pfaff | Jun 2004 | A1 |
20040114714 | Minyard et al. | Jun 2004 | A1 |
20040122705 | Sabol et al. | Jun 2004 | A1 |
20040122787 | Avinash et al. | Jun 2004 | A1 |
20040143582 | Vu | Jul 2004 | A1 |
20040161164 | Dewaele | Aug 2004 | A1 |
20040165791 | Kaltanji | Aug 2004 | A1 |
20040172306 | Wohl et al. | Sep 2004 | A1 |
20040174429 | Chu | Sep 2004 | A1 |
20040190780 | Shiibashi et al. | Sep 2004 | A1 |
20040202387 | Yngvesson | Oct 2004 | A1 |
20040243435 | Williams | Dec 2004 | A1 |
20040252871 | Tecotzky et al. | Dec 2004 | A1 |
20040254816 | Myers | Dec 2004 | A1 |
20040255252 | Rodriguez et al. | Dec 2004 | A1 |
20050010531 | Kushalnagar et al. | Jan 2005 | A1 |
20050027569 | Gollogly et al. | Feb 2005 | A1 |
20050027570 | Maier et al. | Feb 2005 | A1 |
20050043970 | Hsieh | Feb 2005 | A1 |
20050063575 | Ma et al. | Mar 2005 | A1 |
20050065424 | Shah et al. | Mar 2005 | A1 |
20050074150 | Bruss | Apr 2005 | A1 |
20050074157 | Thomas, III | Apr 2005 | A1 |
20050075544 | Shapiro et al. | Apr 2005 | A1 |
20050088534 | Shen et al. | Apr 2005 | A1 |
20050107689 | Sasano | May 2005 | A1 |
20050108058 | Weidner et al. | May 2005 | A1 |
20050110791 | Krishnamoorthy et al. | May 2005 | A1 |
20050111733 | Fors et al. | May 2005 | A1 |
20050113681 | DeFreitas et al. | May 2005 | A1 |
20050114178 | Krishnamurthy et al. | May 2005 | A1 |
20050114179 | Brackett et al. | May 2005 | A1 |
20050114283 | Pearson et al. | May 2005 | A1 |
20050143654 | Zuiderveld et al. | Jun 2005 | A1 |
20050171818 | McLaughlin | Aug 2005 | A1 |
20050184988 | Yanof et al. | Aug 2005 | A1 |
20050197860 | Joffe et al. | Sep 2005 | A1 |
20050238218 | Nakamura | Oct 2005 | A1 |
20050244041 | Tecotzky et al. | Nov 2005 | A1 |
20050251013 | Krishnan | Nov 2005 | A1 |
20050254729 | Saito et al. | Nov 2005 | A1 |
20050273009 | Deischinger et al. | Dec 2005 | A1 |
20060008181 | Takekoshi | Jan 2006 | A1 |
20060031097 | Lipscher et al. | Feb 2006 | A1 |
20060050152 | Rai et al. | Mar 2006 | A1 |
20060058603 | Dave et al. | Mar 2006 | A1 |
20060061570 | Cheryauka et al. | Mar 2006 | A1 |
20060093139 | Quan | May 2006 | A1 |
20060093198 | Fram et al. | May 2006 | A1 |
20060093207 | Reicher et al. | May 2006 | A1 |
20060095423 | Reicher et al. | May 2006 | A1 |
20060095426 | Takachio et al. | May 2006 | A1 |
20060106642 | Reicher et al. | May 2006 | A1 |
20060111941 | Blom | May 2006 | A1 |
20060122482 | Mariotti et al. | Jun 2006 | A1 |
20060171574 | DelMonego et al. | Aug 2006 | A1 |
20060181548 | Hafey | Aug 2006 | A1 |
20060188134 | Quist | Aug 2006 | A1 |
20060230072 | Partovi et al. | Oct 2006 | A1 |
20060241979 | Sato et al. | Oct 2006 | A1 |
20060267976 | Saito et al. | Nov 2006 | A1 |
20060276708 | Peterson et al. | Dec 2006 | A1 |
20060277075 | Salwan | Dec 2006 | A1 |
20060282408 | Wisely et al. | Dec 2006 | A1 |
20070009078 | Saito et al. | Jan 2007 | A1 |
20070021977 | Elsholz | Jan 2007 | A1 |
20070050701 | El Emam et al. | Mar 2007 | A1 |
20070055550 | Courtney et al. | Mar 2007 | A1 |
20070064984 | Vassa et al. | Mar 2007 | A1 |
20070067124 | Kimpe et al. | Mar 2007 | A1 |
20070073556 | Lau et al. | Mar 2007 | A1 |
20070106535 | Matsunaga | May 2007 | A1 |
20070106633 | Reiner | May 2007 | A1 |
20070109299 | Peterson | May 2007 | A1 |
20070109402 | Niwa | May 2007 | A1 |
20070110294 | Peterson et al. | May 2007 | A1 |
20070116345 | Peterson et al. | May 2007 | A1 |
20070116346 | Peterson et al. | May 2007 | A1 |
20070122016 | Brejl et al. | May 2007 | A1 |
20070124541 | Lang et al. | May 2007 | A1 |
20070140536 | Sehnert | Jun 2007 | A1 |
20070159962 | Mathavu et al. | Jul 2007 | A1 |
20070162308 | Peters | Jul 2007 | A1 |
20070165917 | Cao et al. | Jul 2007 | A1 |
20070174079 | Kraus | Jul 2007 | A1 |
20070192138 | Saito et al. | Aug 2007 | A1 |
20070192140 | Gropper | Aug 2007 | A1 |
20070237380 | Iwase | Oct 2007 | A1 |
20070239481 | DiSilvestro et al. | Oct 2007 | A1 |
20070245308 | Hill et al. | Oct 2007 | A1 |
20080016111 | Keen | Jan 2008 | A1 |
20080019581 | Gkanatsios et al. | Jan 2008 | A1 |
20080021877 | Saito et al. | Jan 2008 | A1 |
20080031507 | Uppaluri et al. | Feb 2008 | A1 |
20080059245 | Sakaida et al. | Mar 2008 | A1 |
20080097186 | Biglieri et al. | Apr 2008 | A1 |
20080100612 | Dastmalchi et al. | May 2008 | A1 |
20080103828 | Squilla et al. | May 2008 | A1 |
20080118120 | Wegenkittl et al. | May 2008 | A1 |
20080125846 | Battle et al. | May 2008 | A1 |
20080126982 | Sadikali et al. | May 2008 | A1 |
20080133526 | Haitani et al. | Jun 2008 | A1 |
20080136838 | Goede et al. | Jun 2008 | A1 |
20080275913 | van Arragon et al. | Nov 2008 | A1 |
20080279439 | Minyard et al. | Nov 2008 | A1 |
20080300484 | Wang et al. | Dec 2008 | A1 |
20090005668 | West et al. | Jan 2009 | A1 |
20090022375 | Fidrich | Jan 2009 | A1 |
20090022386 | Karau et al. | Jan 2009 | A1 |
20090028410 | Shimazaki | Jan 2009 | A1 |
20090080719 | Watt | Mar 2009 | A1 |
20090091566 | Turney et al. | Apr 2009 | A1 |
20090123052 | Ruth et al. | May 2009 | A1 |
20090129643 | Natanzon et al. | May 2009 | A1 |
20090129651 | Zagzebski et al. | May 2009 | A1 |
20090132586 | Napora et al. | May 2009 | A1 |
20090150481 | Garcia et al. | Jun 2009 | A1 |
20090164247 | Dobler et al. | Jun 2009 | A1 |
20090182577 | Squilla et al. | Jul 2009 | A1 |
20090198514 | Rhodes | Aug 2009 | A1 |
20090213034 | Wu et al. | Aug 2009 | A1 |
20090248442 | Pacheco et al. | Oct 2009 | A1 |
20090268986 | Holstein et al. | Oct 2009 | A1 |
20090297013 | Chaudhuri | Dec 2009 | A1 |
20090326373 | Boese et al. | Dec 2009 | A1 |
20100053353 | Hunter et al. | Mar 2010 | A1 |
20100086182 | Luo | Apr 2010 | A1 |
20100131887 | Salazar-Ferrer | May 2010 | A1 |
20100138239 | Reicher et al. | Jun 2010 | A1 |
20100138240 | Leib et al. | Jun 2010 | A1 |
20100198608 | Kaboff et al. | Aug 2010 | A1 |
20100201714 | Reicher et al. | Aug 2010 | A1 |
20100211409 | Kotula et al. | Aug 2010 | A1 |
20100246981 | Hu et al. | Sep 2010 | A1 |
20100299157 | Fram et al. | Nov 2010 | A1 |
20110016430 | Fram et al. | Jan 2011 | A1 |
20110019886 | Mizuno | Jan 2011 | A1 |
20110110572 | Guehring et al. | May 2011 | A1 |
20110267339 | Fram et al. | Nov 2011 | A1 |
20110293162 | Pajeau | Dec 2011 | A1 |
20110316873 | Reicher et al. | Dec 2011 | A1 |
20120070048 | Van Den Brink | Mar 2012 | A1 |
20120130729 | Raizada et al. | May 2012 | A1 |
20120136794 | Kushalnagar et al. | May 2012 | A1 |
20120163684 | Natanzon et al. | Jun 2012 | A1 |
20120183191 | Nakamura | Jul 2012 | A1 |
20120194540 | Reicher et al. | Aug 2012 | A1 |
20120196258 | Geijsen | Aug 2012 | A1 |
20120208592 | Davis et al. | Aug 2012 | A1 |
20120284657 | Hafey et al. | Nov 2012 | A1 |
20120320093 | Zhu et al. | Dec 2012 | A1 |
20120324400 | Caliendo, Jr. et al. | Dec 2012 | A1 |
20130070998 | Shibata | Mar 2013 | A1 |
20130076681 | Sirpal et al. | Mar 2013 | A1 |
20130083023 | Fram et al. | Apr 2013 | A1 |
20130129198 | Sherman | May 2013 | A1 |
20130129231 | Dale et al. | May 2013 | A1 |
20130159019 | Reicher et al. | Jun 2013 | A1 |
20130169661 | Reicher et al. | Jul 2013 | A1 |
20130195329 | Canda et al. | Aug 2013 | A1 |
20130198682 | Matas et al. | Aug 2013 | A1 |
20130297331 | Zuehlsdorff et al. | Nov 2013 | A1 |
20140022194 | Ito | Jan 2014 | A1 |
20140096049 | Vonshak et al. | Apr 2014 | A1 |
20140119514 | Miyazawa | May 2014 | A1 |
20140142983 | Backhaus et al. | May 2014 | A1 |
20140378810 | Davis et al. | Dec 2014 | A1 |
20150046349 | Michael, Jr. et al. | Feb 2015 | A1 |
20150101066 | Fram | Apr 2015 | A1 |
20150363104 | Ichioka | Dec 2015 | A1 |
20160034110 | Edwards | Feb 2016 | A1 |
20160270746 | Foos et al. | Sep 2016 | A1 |
20170038951 | Reicher et al. | Feb 2017 | A1 |
20170039321 | Reicher et al. | Feb 2017 | A1 |
20170039322 | Reicher et al. | Feb 2017 | A1 |
20170039350 | Reicher et al. | Feb 2017 | A1 |
20170039705 | Fram et al. | Feb 2017 | A1 |
20170046483 | Reicher et al. | Feb 2017 | A1 |
20170046485 | Reicher et al. | Feb 2017 | A1 |
20170046495 | Fram | Feb 2017 | A1 |
20170046870 | Fram et al. | Feb 2017 | A1 |
20170053404 | Reicher et al. | Feb 2017 | A1 |
Number | Date | Country |
---|---|---|
WO 2007131157 | Nov 2007 | WO |
Entry |
---|
US 7,801,341 B2, 09/2010, Fram et al. (withdrawn) |
US 8,208,705 B2, 06/2012, Reicher et al. (withdrawn) |
U.S. Appl. No. 15/292,006, Systems and Methods for Viewing Medical 3D Imaging Volumes, filed Oct. 12, 2016. |
U.S. Appl. No. 15/346,530, Systems and Methods for Matching, Naming, and Displaying Medical Images, filed Nov. 8, 2016. |
U.S. Appl. No. 14/043,165, Automated Document Filings, filed Oct. 1, 2013. |
U.S. Appl. No. 15/292,014, System and Method of Providing Dynamic and Customizable Medical Examination for, filed Oct. 12, 2016. |
U.S. Appl. No. 14/792,210, Dynamic Montage Reconstruction, filed Jul. 6, 2015. |
U.S. Appl. No. 15/188,872, Intelligent Management of Computerized Advanced Processing, filed Jun. 21, 2016. |
U.S. Appl. No. 15/140,346, Database Systems and Interactive User Interfaces for Dynamic Interaction With, and Sorting of, Digital Medical Image Data, filed Apr. 27, 2016. |
U.S. Appl. No. 15/140,363, Database Systems and Interactive User Interfaces for Dynamic Interation With, and Comparison of, Digital Medical Image Data, filed Apr. 27, 2016. |
U.S. Appl. No. 15/140,351, Database Systems and Interactive User Interfaces for Dynamic Interaction With, and Review of, Digital Medical Image DA, filed Apr. 27, 2016. |
U.S. Appl. No. 15/140,348, Database Systems and Interactive User Interfaces for Dynamic Interaction With, and Indications of, Digital Medical Image Data, filed Apr. 27, 2016. |
Non-Final Office Action dated Aug. 28, 2007 in U.S. Appl. No. 11/179,384. |
Final Office Action dated Jun. 26, 2008 in U.S. Appl. No. 11/179,384. |
Non-Final Office Action dated Dec. 29, 2008 in U.S. Appl. No. 11/179,384. |
Final Office Action dated Jul. 24, 2009, in U.S. Appl. No. 11/179,384. |
Notice of Allowance dated Nov. 3, 2009, in U.S. Appl. No. 11/179,384. |
Non-Final Office Action dated Aug. 18, 2010 in U.S. Appl. No. 12/702,976. |
Interview Summary dated Dec. 1, 2010, in U.S. Appl. No. 12/702,976. |
Final Office Action dated Feb. 17, 2011 in U.S. Appl. No. 12/702,976. |
Interview Summary dated May 31, 2011 in U.S. Appl. No. 12/702,976. |
Notice of Allowance dated Jul. 20, 2011, in U.S. Appl. No. 12/702,976. |
Office Action dated Dec. 1, 2011, in U.S. Appl. No. 13/228,349. |
Notice of Allowance dated Feb. 6, 2012, in U.S. Appl. No. 13/228,349. |
Notice of Allowance dated Jul. 20, 2012, in U.S. Appl. No. 13/228,349. |
Office Action dated Dec. 11, 2013, in U.S. Appl. No. 13/477,853. |
Interview Summary dated Mar. 14, 2014, in U.S. Appl. No. 13/477,853. |
Final Office Action dated Jun. 13, 2014, in U.S. Appl. No. 13/477,853. |
Notice of Allowance dated Aug. 15, 2014, in U.S. Appl. No. 13/477,853. |
Office Action dated Jan. 17, 2017, in U.S. Appl. No. 14/540,830. |
Non-Final Office Action dated Oct. 1, 2009, in U.S. Appl. No. 11/268,261. |
Notice of Allowance dated Feb. 2, 2010, in U.S. Appl. No. 11/268,261. |
Interview Summary dated Jan. 25, 2010, in U.S. Appl. No. 11/268,261. |
Interview Summary dated May 14, 2010, in U.S. Appl. No. 11/268,261. |
Notice of Allowance dated May 17, 2010, in U.S. Appl. No. 11/268,261. |
Supplemental Notice of Allowance dated Aug. 6, 2010, in U.S. Appl. No. 11/268,261. |
Notice of Allowance dated Oct. 8, 2010, in U.S. Appl. No. 11/268,261. |
Notice of Allowance dated Dec. 3, 2010, in U.S. Appl. No. 11/268,261. |
Notice of Allowance dated Jan. 6, 2011, in U.S. Appl. No. 11/268,261. |
Office Action dated May 16, 2011, in U.S. Appl. No. 12/857,915. |
Interview Summary dated Sep. 6, 2011, in U.S. Appl. No. 12/857,915. |
Final Office Action dated Dec. 15, 2011, in U.S. Appl. No. 12/857,915. |
Office Action dated Jun. 12, 2012, in U.S. Appl. No. 12/857,915. |
Office Action dated Aug. 23, 2013, in U.S. Appl. No. 12/857,915. |
Interview Summary dated Feb. 4, 2014, in U.S. Appl. No. 12/857,915. |
Notice of Allowance dated Jul. 3, 2014, in U.S. Appl. No. 12/857,915. |
“Corrected” Notice of Allowance dated Aug. 15, 2014, in U.S. Appl. No. 12/857,915. |
Non-Final Office Action dated Jan. 20, 2016, in U.S. Appl. No. 14/502,055. |
Interview Summary dated Apr. 14, 2016, in U.S. Appl. No. 14/502,055. |
Notice of Allowance dated Jun. 2, 2016, in U.S. Appl. No. 14/502,055. |
Notice of Corrected Allowability dated Jul. 14, 2016, in U.S. Appl. No. 14/502,055. |
Notice of Corrected Allowability dated Sep. 19, 2016, in U.S. Appl. No. 14/502,055. |
Office Action dated Dec. 12, 2016, in U.S. Appl. No. 15/254,627. |
Non-Final Office Action dated May 13, 2009, in U.S. Appl. No. 11/265,979. |
Final Office Action dated Dec. 22, 2009 in U.S. Appl. No. 11/265,979. |
Non-Final Office Action dated Jul. 8, 2010 in U.S. Appl. No. 11/265,979. |
Interview Summary dated Mar. 4, 2010 in U.S. Appl. No. 11/265,979. |
Interview Summary dated Nov. 16, 2010 in U.S. Appl. No. 11/265,979. |
Final Office Action dated Dec. 23, 2010 in U.S. Appl. No. 11/265,979. |
Interview Summary dated Mar. 17, 2011 in U.S. Appl. No. 11/265,979. |
Notice of Allowance dated May 26, 2011 in U.S. Appl. No. 11/265,979. |
Office Action dated Jun. 8, 2012 in U.S. Appl. No. 13/171,081. |
Interview Summary dated Jul. 31, 2012 in U.S. Appl. No. 13/171,081. |
Final Office Action dated Oct. 12, 2012 in U.S. Appl. No. 13/171,081. |
Interview Summary dated Nov. 6, 2012 in U.S. Appl. No. 13/171,081. |
Notice of Allowance, dated Sep. 4, 2013, in U.S. Appl. No. 13/171,081. |
Office Action dated Mar. 3, 2015 in U.S. Appl. No. 14/095,123. |
Interview Summary dated May 1, 2015 in U.S. Appl. No. 14/095,123. |
Final Office Action dated Jul. 23, 2015 in U.S. Appl. No. 14/095,123. |
Interview Summary dated Aug. 27, 2015 in U.S. Appl. No. 14/095,123. |
Office Action dated Feb. 23, 2016 in U.S. Appl. No. 14/095,123. |
Final Office Action dated Jul. 20, 2016 in U.S. Appl. No. 14/095,123. |
Non-Final Office Action dated Aug. 24, 2009 in U.S. Appl. No. 11/268,262. |
Non-Final Office Action dated Apr. 16, 2010 in U.S. Appl. No. 11/268,262. |
Interview Summary dated Nov. 24, 2009 in U.S. Appl. No. 11/268,262. |
Interview Summary dated May 12, 2010 in U.S. Appl. No. 11/268,262. |
Final Office Action dated Oct. 28, 2010 in U.S. Appl. No. 11/268,262. |
Interview Summary dated Dec. 1, 2010 in U.S. Appl. No. 11/268,262. |
Notice of Allowance dated Dec. 1, 2010 in U.S. Appl. No. 11/268,262. |
Notice of Allowance dated Feb. 25, 2011 in U.S. Appl. No. 11/268,262. |
Non-Final Office Action dated Jan. 11, 2012 in U.S. Appl. No. 13/079,597. |
Notice of Allowance dated Apr. 25, 2012, in U.S. Appl. No. 13/079,597. |
Non-Final Office Action dated Apr. 4, 2013 in U.S. Appl. No. 13/535,758. |
Notice of Allowance, dated Aug. 23, 2013 in U.S. Appl. No. 13/535,758. |
Corrected Notice of Allowance dated Jun. 27, 2016, in U.S. Appl. No. 14/502,055. |
Office Action dated Mar. 10, 2016 in U.S. Appl. No. 14/081,225. |
Notice of Allowance dated Sep. 2, 2016 in U.S. Appl. No. 14/081,225. |
Corrected Notice of Allowance dated Oct. 21, 2016 in U.S. Appl. No. 14/081,225. |
Non-Final Office Action dated Jul. 27, 2009 in U.S. Appl. No. 11/265,978. |
Notice of Allowance dated Nov. 19, 2009 in U.S. Appl. No. 11/265,978. |
Notice of Allowance dated Apr. 19, 2010 in U.S. Appl. No. 11/265,978. |
Supplemental Notice of Allowance dated May 3, 2010 in U.S. Appl. No. 11/265,978. |
Supplemental Notice of Allowance dated Aug. 3, 2010 in U.S. Appl. No. 11/265,978. |
Non-Final Office Action dated May 5, 2011 in U.S. Appl. No. 12/870,645. |
Non-Final Office Action dated May 31, 2013, in U.S. Appl. No. 13/345,606. |
Interview Summary dated Aug. 15, 2013, in U.S. Appl. No. 13/345,606. |
Notice of Allowance, dated Jan. 9, 2014 in U.S. Appl. No. 13/345,606. |
Non-Final Office Action dated Mar. 18, 2016 in U.S. Appl. No. 14/244,431. |
Interview Summary dated Jun. 17, 2016 in U.S. Appl. No. 14/244,431. |
Notice of Allowance dated Aug. 18, 2016 in U.S. Appl. No. 14/244,431. |
Corrected Notice of Allowance dated Nov. 16, 2016 in U.S. Appl. No. 14/244,431. |
Non-Final Office Action dated May 26, 2010 in U.S. Appl. No. 11/942,674. |
Interview Summary dated Jul. 26, 2010 in U.S. Appl. No. 11/942,674. |
Final Office Action dated Nov. 26, 2010 in U.S. Appl. No. 11/942,674. |
Interview Summary dated Mar. 2, 2011 in U.S. Appl. No. 11/942,674. |
Notice of Allowance, dated Apr. 1, 2011 in U.S. Appl. No. 11/942,674. |
Non Final Office Action Dated Nov. 10, 2011 in U.S. Appl. No. 13/118,085. |
Interview Summary, dated Feb. 17, 2012, in U.S. Appl. No. 13/118,085. |
Final Office Action, dated Apr. 13, 2012, in U.S. Appl. No. 13/118,085. |
Notice of Allowance, dated Feb. 6, 2013, in U.S. Appl. No. 13/118,085. |
Non Final Office Action dated Aug. 23, 2013 in U.S. Appl. No. 13/907,128. |
Final Office Action dated Oct. 9, 2013 in U.S. Appl. No. 13/907,128. |
Interview Summary dated Nov. 22, 2013 in U.S. Appl. No. 13/907,128. |
Notice of Allowance dated Jan. 31, 2014 in U.S. Appl. No. 13/907,128. |
Office Action, dated Dec. 29, 2014 in U.S. Appl. No. 14/298,806. |
Interview Summary, dated Mar. 2, 2015 in U.S. Appl. No. 14/298,806. |
Final Office Action, dated Jun. 17, 2015 in U.S. Appl. No. 14/298,806. |
Office Action, dated Feb. 16, 2016 in U.S. Appl. No. 14/298,806. |
Final Office Action, dated Jul. 21, 2016 in U.S. Appl. No. 14/298,806. |
Non Final Office Action dated Sep. 16, 2010 in U.S. Appl. No. 11/942,687. |
Interview Summary dated Dec. 3, 2010 in U.S. Appl. No. 11/942,687. |
Final Office Action, dated Apr. 5, 2011 in U.S. Appl. No. 11/942,687. |
Office Action, dated Mar. 13, 2014 in U.S. Appl. No. 11/942,687. |
Interview Summary, dated Jun. 17, 2014 in U.S. Appl. No. 11/942,687. |
Office Action, dated Jul. 18, 2014 in U.S. Appl. No. 11/942,687. |
Final Office Action, dated Jan. 5, 2015 in U.S. Appl. No. 11/942,687. |
Interview Summary, dated Mar. 4, 2015 in U.S. Appl. No. 11/942,687. |
PTAB Examiner's Answer, dated Feb. 25, 2016 in U.S. Appl. No. 11/942,687. |
Non-Final Office Action dated Apr. 14, 2010 in U.S. Appl. No. 11/944,027. |
Interview Summary dated May 13, 2010 in U.S. Appl. No. 11/944,027. |
Final Office Action dated Dec. 23, 2010 in U.S. Appl. No. 11/944,027. |
Interview Summary dated Mar. 31, 2011 in U.S. Appl. No. 11/944,027. |
Office Action dated Apr. 19, 2012 in U.S. Appl. No. 11/944,027. |
Interview Summary dated Jun. 28, 2012 in U.S. Appl. No. 11/944,027. |
Final Office Action dated Oct. 22, 2012 in U.S. Appl. No. 11/944,027. |
Notice of Allowance dated Jun. 5, 2013 in U.S. Appl. No. 11/944,027. |
Office Action dated Oct. 14, 2014 in U.S. Appl. No. 14/043,165. |
Final Office Action dated Apr. 1, 2015 in U.S. Appl. No. 14/043,165. |
Office Action dated Oct. 2, 2015 in U.S. Appl. No. 14/043,165. |
Interview Summary dated Dec. 21, 2015 in U.S. Appl. No. 14/043,165. |
Final Office Action dated Feb. 17, 2016 in U.S. Appl. No. 14/043,165. |
Appeal Brief dated Jul. 15, 2016 in U.S. Appl. No. 14/043,165. |
Examiner's Answer dated Nov. 14, 2016, in U.S. Appl. No. 14/043,165. |
Non-Final Office Action dated Sep. 29, 2010 in U.S. Appl. No. 11/944,000. |
Final Office Action dated Apr. 20, 2011 in U.S. Appl. No. 11/944,000. |
Interview Summary dated Jun. 7, 2011 in U.S. Appl. No. 11/944,000. |
Appeal Brief dated Mar. 4, 2013 in U.S. Appl. No. 11/944,000. |
Examiner's Answer dated Jun. 26, 2013 in U.S. Appl. No. 11/944,000. |
Board Decision dated Mar. 23, 2016 in U.S. Appl. No. 11/944,000. |
Office Action, dated Jul. 15, 2016 in U.S. Appl. No. 11/944,000. |
Office Action dated Feb. 3, 2012 in U.S. Appl. No. 12/622,404. |
Interview Summary dated May 8, 2012 in U.S. Appl. No. 12/622,404. |
Final Office Action dated Aug. 6, 2012 in U.S. Appl. No. 12/622,404. |
Notice of Allowance dated Oct. 15, 2012 in U.S. Appl. No. 12/622,404. |
Office Action dated Mar. 17, 2015 in U.S. Appl. No. 13/768,765. |
Interview Summary dated Jun. 11, 2015 in U.S. Appl. No. 13/768,765. |
Notice of Allowance dated Aug. 28, 2015 in U.S. Appl. No. 13/768,765. |
Notice of Allowability dated Nov. 20, 2015 in U.S. Appl. No. 13/768,765. |
Notice of Allowability dated Jul. 28, 2016 in U.S. Appl. No. 13/768,765. |
Office Action dated Mar. 4, 2013 in U.S. Appl. No. 12/891,543. |
Interview Summary dated Apr. 5, 2013 in U.S. Appl. No. 12/891,543. |
Notice of Allowance dated Nov. 14, 2013 in U.S. Appl. No. 12/891,543. |
Office Action dated Sep. 11, 2014 in U.S. Appl. No. 14/179,328. |
Notice of Allowance dated Jan. 14, 2015 in U.S. Appl. No. 14/179,328. |
Office Action dated Aug. 13, 2015 in U.S. Appl. No. 14/687,853. |
Notice of Allowance dated Feb. 25, 2016 in U.S. Appl. No. 14/687,853. |
Supplemental Notice of Allowance dated Jun. 2, 2016 in U.S. Appl. No. 14/687,853. |
Notice of Allowance dated Aug. 11, 2016 in U.S. Appl. No. 15/163,600. |
Supplemental Notice of Allowance dated Sep. 14, 2016 in U.S. Appl. No. 15/163,600. |
Office Action, dated Jan. 12, 2017 in U.S. Appl. No. 15/292,023. |
Office Action dated Jun. 27, 2014 in U.S. Appl. No. 13/572,397. |
Final Office Action dated Jan. 13, 2015 in U.S. Appl. No. 13/572,397. |
Notice of Allowance dated Mar. 19, 2015, 2015 in U.S. Appl. No. 13/572,397. |
Office Action dated Aug. 6, 2014 in U.S. Appl. No. 13/572,547. |
Notice of Allowance, dated Mar. 3, 2015 in U.S. Appl. No. 13/572,547. |
Corrected Notice of Allowance, dated Apr. 10, 2015 in U.S. Appl. No. 13/572,547. |
Corrected Notice of Allowance, dated May 21, 2015 in U.S. Appl. No. 13/572,547. |
Office Action dated Jul. 30, 2014 in U.S. Appl. No. 13/572,552. |
Interview Summary dated Sep. 3, 2014 in U.S. Appl. No. 13/572,552. |
Final Office Action dated Jan. 28, 2015 in U.S. Appl. No. 13/572,552. |
Interview Summary dated Apr. 23, 2015 in U.S. Appl. No. 13/572,552. |
Notice of Allowance, dated May 8, 2015 in U.S. Appl. No. 13/572,552. |
Restriction Requirement, dated Jul. 28, 2015 in U.S. Appl. No. 14/139,068. |
Office Action, dated Mar. 11, 2016 in U.S. Appl. No. 14/139,068. |
Notice of Allowance, dated Sep. 21, 2016 in U.S. Appl. No. 14/139,068. |
Crowley, Rebecca et al., Development of Visual Diagnostic Expertise in Pathology: an Information-processing Study, Jan. 2003, Journal of the American medical Informatics Association, vol. 10, No. 1, pp. 39-51. |
Erickson, et al.: “Effect of Automated Image Registration on Radiologist Interpretation,” Journal of Digital Imaging, vol. 20, No. 2 Jun. 2007; pp. 105-113. |
Erickson, et al.: “Image Registration Improves Confidence and Accuracy of Image Interpretation,” Special Issue-Imaging Informatics, Cancer Informatics 2007: 1 19-24. |
Mendelson, et al. “Informatics in Radiology—Image Exchange: IHE and the Evolution of Image Sharing,” RadioGraphics, Nov.-Dec. 2008, vol. 28, No. 7. |
Rosset et al.: “OsiriX: An Open-Source Software for Navigating in Multidimensional DICOM Images,” Journal of digital Imaging, Sep. 2004, pp. 205-216. |
Schellingerhout, Dawid, MD, et al.: “Coregistration of Head CT Comparison Studies: Assessment of Clinical Utility,” Acad Radiol 2003; 10:242-248. |
Sprawls, “Image Characteristics and Quality,” Physical Principles of Medical Imaging, http://www.sprawls.org/resources pp. 1-14. |
Voyager Imaging—Voyager PACS, 3 page color brochure. Downloaded from http://www.intellirad.com.au/index.php/assets/Uploads/Voyager-Pacs3.pdf. Accessed on Feb. 9, 2015. |
Ivetic, D., and Dragan, D., Medical Image on the Go!, 2009, J Med Syst, vol. 35, pp. 499-516. |
Tahmoush, D. and Samet, H., A New Database for Medical Images and Information, 2007, Medical Imaging 2007; PACS and Imaging Informatics, vol. 6516. pp. 1-9. |
AGFA HealthCare, color brochure “IMPAX 6: Digital Image and Information Management,” © 2012 Agfa HealthCare N V. Downloaded from http://www.agfahealthcare.com/global/en/he/library/libaryopen?ID=32882925. Accessed on Feb. 9, 2015. |
AGFA HealthCare, IMPAX 6.5 Datasheet (US)2012. © 2012 Agfa HealthCare N.V. Downloaded from http://www.agfahealthcare.com/global/en/he/library/libraryopen?ID=37459801. Accessed on Feb. 9, 2015. |
AMD Technologies, Inc., Catella PACS 5.0 Viewer User Manual (112 pgs), © 2010, AMD Technologies, Inc. (Doc. 340-3-503 Rev. 01). Downloaded from http://www.amdtechnologies.com/lit/cat5viewer.pdf. Accessed on Feb. 9, 2015. |
ASPYRA's Imaging Solutions, 3 page color print out. Accessed at http://www.aspyra.com/imaging-solutions. Accessed on Feb. 9, 2015. |
AVREO, interWorks—RIS/PACS package, 2 page color brochure, © 2014, Avreo, Inc. (Document MR-5032 Rev. 4). Downloaded from http://www.avreo.com/ProductBrochures/MR- 5032Rev.%204interWORKS%20RISPACSPackage.pdf. Accessed on Feb. 9, 2015. |
BRIT Systems, BRIT PACS View Viewer, 2 page color brochure, (BPB-BPV-0001). Downloaded from http://www.brit.com/pdfs/britpacsview.pdf. Accessed on Feb. 9, 2015. |
BRIT Systems, Roentgen Works—100% Browers-based VNA (Vendor Neutral Archive/PACS), © 2010 BRIT Systems, 1 page color sheet. Accessed at http://www.roentgenworks.com/PACS. Accessed on Feb. 9, 2015. |
BRIT Systems, Vision Multi-modality Viewer—with 3D, 2 page color brochure, (BPB-BVV-0001 REVC). Downloaded from http://brit.com/pdfs/BPB-BVV-001REVC_BRIT_Vision_Viewer.pdf. Accessed on Feb. 9, 2015. |
CANDELiS, ImageGrid™: Image Management Appliance, 6 page color brochure. (AD-012 Rev. F Nov. 2012), © 2012 Candelis, Inc. Downloaded from http://www.candelis.com/images/pdf/Candelis_ImageGrid_Appliance_20111121.pdf. Accessed on Feb. 9, 2015. |
Carestream, Cardiology PACS, 8 page color brochure. (CAT 866 6075 06/12). © Carestream Health, Inc., 2012. Downloaded from http://www.carestrearm.com/cardioPACS_brochure_M1-877.pdf. Accessed on Feb. 9, 2015. |
Carestream, Vue PACS, 8 page color brochure. (CAT 300 1035 05/14). © Carestream Health, Inc., 2014. Downloaded from http://www.carestream.com/csPACS_brochure_M1-876.pdf . Accessed on Feb. 9, 2015. |
Cerner, Radiology—Streamline image management, 2 page color brochure, (fl03_332_10_v3). Downloaded from http://www.cerner.com/uploadedFiles/Clinical_Imaging.pdf. Accessed on Feb. 9, 2015. |
CoActiv, EXAM-PACS, 2 page color brochure, © 2014 CoActiv, LLC. Downloaded from http://coactiv.com/wp-content/uploads/2013/08/EXAM-PACS-BROCHURE-final-web.pdf. Accessed on Feb. 9, 2015. |
DR Systems, Dominator—Guide for Reading Physicians, Release 8.2, 546 pages, (TCP-000260-A), © 1997-2009, DR Systems, Inc. Downloaded from https://resources.dominator.com/assets/004/6999.pdf. Document accessed Feb. 9, 2015. |
DR Systems, DR Scheduler User Guide, Release 8.2, 410 pages, (TCP-000115-A), © 1997-2009, DR Systems, Inc. Downloaded from https://resources.dominator.com/assets/003/6850.pdf. Document accessed Feb. 9, 2015. |
FUJIFILM Medical Systems, SYNAPSE® Product Data, Synapse Release Version 3.2.1, Foundation Technologies, 4 page color brochure, (XBUSSY084) Aug. 2008. Downloaded from http://www.fujifilmusa.com/shared/bin/foundation.pdf. Accessed on Feb. 9, 2015. |
FUJIFILM Medical Systems, SYNAPSE® Product Data, Synapse Release Version 3.2.1, Server Modules and Interfaces, 4 page color brochure, (XBUSSY085) Aug. 2008. Downloaded from http://www.fujifilmusa.com/shared/bin/server-interface.pdf. Accessed on Feb. 9, 2015. |
FUJIFILM Medical Systems, SYNAPSE® Product Data, Synapse Release Version 3.2.1, Workstation Software, 4 page color brochure, (XBUSSY082) Aug. 2008. Downloaded from http://www.fujifilmusa.com/shared/bin/workstation.pdf. Accessed on Feb. 9, 2015. |
GE Healthcare, Centricity PACS, in 8 page printout. Accessed at http://www3.gehealthcare.com/en/products/categories/healthcare_it/medical_imaging_informatics_-_ris-pacs-cvis/centricity_pacs. Accessed on Feb. 9, 2015. |
Handylife.com—Features of Handy Patients Enterprise, in 4 page printout. Accessed from http://www.handylife.com/en/software/features.html. Accessed on Feb. 18, 2015. |
Handylife.com—Overview of Handy Patients Enterprise, in 2 page printout. Accessed from http://www.handylife.com/en/software/overview.html. Accessed on Feb. 18, 2015. |
Handylife.com—Screenshots of Handy Patients Enterprise, in 2 page printout. Accessed from http://www.handylife.com/en/software/screenshots.html. Accessed on Feb. 18, 2015. |
iCRco, I See The Future, in 12 pages color brochure, (BR080809AUS), © 2009 iCRco.ClarityPACS. Downloaded from http://www.claritypacs.com/pdfs/ISeeFuture_26_Web.pdf. Accessed on Feb. 9, 2015. |
Imageanalysis, dynamika, 2 page color brochure. Downloaded from http://www.imageanalysis.org.uk/what-we-do. Accessed on Feb. 9, 2015. |
Imageanalysis, MRI Software, in 5 page printout. Accessed at http://www.imageanalysis.org.uk/mri-software. Accessed on Feb. 9, 2015. |
IMSI, Integrated Modular Systems, Inc., Hosted / Cloud PACS in one page printout. Accessed at http//www.imsimed.com/#lproducts-services/ctnu. Accessed on Feb. 9, 2015. |
Infinitt, PACS, RIS, Mammo PACS, Cardiology Suite and 3D/Advanced Visualization | Infinittna, 2 page printout. Accessed at http://www.infinittna.com/products/radiology/radiology-pacs. Accessed on Feb. 9, 2015. |
Intelerad, IntelePACS, 2 page color brochure, © 2014 Intelerad Medical Systems Incoprorated. Downloaded http://www.intelerad.com/wp-content/uploads/sites/2/2014/08/IntelePACS-brochure.pdf. Accessed on Feb. 9, 2015. |
Intelerad, InteleViewer, 2 page color brochure, © 2014 Intelerad Medical Systems Incoprorated. Downloaded from http://www.intelerad.com/wp-content/uploads/sites/2/2014/09/InteleViewrer-brochure.pdf. Accessed on Feb. 9, 2015. |
Intuitive Imaging Informatics, ImageQube, 1 page in color. Downloaded from http://www.intuitiveimaging.com/2013/pdf/ImageQube%20one-sheet.pdf. Accessed on Feb. 9, 2015. |
Kuhl, Helen: Comparison Chart/PACS, Customers Are Happy, But Looking for More, (color) Imaging Techology News, itnonline.com, May 2012, pp. 24-27. Downloaded from http://www.merge.com/MergeHealthcare/media/company/In%20The%20News/merge-pacs-comparison.pdf. Accessed on Feb. 9, 2015. |
LUMEDX CardioPACS 5.0 Web Viewer, Cardiopacs Module, 2 page color brochure, (506-10011 Rev A). Downloaded from http://cdn.medicexchange.com/images/whitepaper/cardiopacs_web_viewer.pdf?1295436926. Accessed on Feb. 9, 2015. |
LUMEDX Cardiovascular Information System, CardioPACS, one page in color printout. Accessed at http://www.lumedx..com/pacs.aspx. Accessed on Feb. 9, 2015. |
McKesson Enterprise Medical Imagining and PACS | McKesson, 1 page (color) printout. Accessed at http://www.mckesson.com/provides/health-systems/diagnostic-imaging/enterprise-medical-imaging. Accessed on Feb. 9, 2015. |
Medweb Radiology Workflow Solutions, Radiology Workflow Solutions, Complete Workflow & Flexible Turnkey Solutions, Web RIS/PACS with Advanced Viewer, 3 page color brochure, © 2006-2014 Medweb. Downloaded from http://www.medweb.com/docs/rispacs_brochure_2014.pdf. Accessed on Feb. 9, 2015. |
Merge Radiology Solutions, Merge PACS, A real-time picture archiving communication system, (PAX-21990 rev 2.0), 2 page color brochure. Downloaded from http://www.merge.com/MergeHealthcare/media/documents/brochures/Merge_PACS_web.pdf. Accessed on Feb. 9, 2015. |
NOVARAD Enterprise Imaging Solutions, NOVAPACS, 2 page (color) printout. Accessed at http://ww1.novarad.net/novapacs. Accessed on Feb. 9, 2015. |
PACSPLUS, PACSPLUS Server, 1 page (color) printout. Accessed at http://www.pacsplus.com/01_products/products_01.html. Accessed on Feb. 9, 2015. |
PACSPLUS, PACSPLUS Workstation, 3 page (color) printout. Accessed at http://www.pacsplus.com/01_products_01.html. Accessed on Feb. 9, 2015. |
Philips IntelliSpace PACS, in 2 color page printout. Accessed at https://www.healthcare.philips.com/main/products/healthcare_informatics/products/enterprise_imaging_informatics/isite_pacs. Accessed on Feb. 9, 2015. |
Philips, IntelliSpace: Multi-modality tumor tracking application versus manual PACS methods, A time study for Response Evaluation Criteria in Solid Tumors (RECIST). 2012, Koninklijke Philips Electronics N.V., in four pages. |
RamSoft, RIS PACS Teleradiology, PowerServer PACS, Lite PACS, XU PACS Compare RamSoft PACS Products, 2 color page printout. Accessed at http://www.ramsoft.com/products/powerserver-pacs-overvew. Accessed on Feb. 9, 2015. |
Sage Intergy PACS | Product Summary. Enhancing Your Workflow by Delivering Web-based Diagnostic Images When and Where You Need Them, in 2 color pages. (IRV-SS-INTPACS-PSS-031309). © 2009 Sage Software Healcare, Inc. Downloaded from http://www.greenwayhealth.com/solutons/intergy/. Accessed on Feb. 9, 2015. |
ScImage, Cardiology PACS, in 8 color page printout. Accessed at http://www.scimacle.com/solutions/clinical-solutons/cardiology. Accessed on Feb. 9, 2015. |
Sectra RIS PACS, in 2 color page printout. Accessed at http://www.sectra.com/medical/diagnostic_imaging/solutions/ris-pacs/. Accessed on Feb. 9, 2015. |
Siemens syngo.plaza, Features and Benefits, in 2 color page printout. Accessed at http://www.healthcare.siemens.com/medical-imaging-it/imaging/it-radiology-image-management-pacs/syngoplaza/features. Accessed on Feb. 9, 2015. |
Simms | RIS and PACS Medical Imaging Software, in 2 color page printout. http://www.mysimms.com/ris-pacs.php. Accessed on Feb. 9, 2015. |
Stryker, Imaging—OfficePACS Power Digital Imaging, in one color page printout. Accessed from http://www.stryker.com/emea/Solutions/Imaging/Office PACSPowerDigitalImaging/index.htm. Accessed on Feb. 9, 2015. |
Stryker, OfficePACS Power—Digital Imaging, 8 page color brochure, (MPP-022 Rev 4 BC/MP 300 1/07). © 2007 Stryker. Downloaded from http://www.stryker.com/emea/Solutions/Imaging/OfficePACSPowerDigitalImaging/ssLINK/emea/1557/022268. Accessed on Feb. 9, 2015. |
TeraRecon iNtuition—Workflow. <www.terarecon.com/wordpress/our-solutions/intuition-workflow> Last accessed Nov. 8, 2013. 2 pages. |
TeraRecon iNtuition pamphlet in 20 pages, retrieved on Nov. 8, 2013, available at http://int.terarecon.com/wp-content/uploads/2013/11/brochure_english2013.pdf. |
UltraRAD—ultra VISION, 1 page (color). Downloaded from http://www.ultraradcorp.com/pdf/UltraVISION.pdf. Accessed on Feb. 9, 2015. |
VioStream for VitreaView, 2 color pages printout. Accessed at http://www.vitalimages.com/solutions/universal-viewing/viostream-for-vitreaview. Accessed on Feb. 9, 2015. |
Visage Imaging Visage 7, 3 color page printout. Accessed at http://www.visageimaging.com/visage-7. Accessed on Feb. 9, 2015. |
VIZTEK Radiology PACS Software Vixtek Opal-RAD, 4 color page printout. Accessed at http://viztek.net/products/opal-rad. Accessed on Feb. 9, 2015. |
Voyager Imaging—Voyager PACS Radiologist Workstation, 2 page color brochure. Downloaded from http://www.intellirad.com.au/assets/Uploads/Voyager-PacsWorkstations.pdf. Accessed on Feb. 9, 2015. |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/188,872 dated Oct. 19, 2018 (12 pages). |
Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/188,872 dated May 8, 2019 (14 pages). |
Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 12/870,645 dated Jun. 10, 2011 (3 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 12/870,645 dated Sep. 13, 2011 (8 pages). |
Examiner Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 13/768,765 dated Aug. 28, 2015 (1 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 13/768,765 dated Jul. 28, 2016 (9 pages). |
Examiner Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 12/891,543 dated Nov. 14, 2013 (1 pages). |
Applicant-Initiated Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/179,328 dated Dec. 11, 2014 (3 pages). |
Examiner Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/163,600 dated Sep. 14, 2016 (1 pages). |
Corrected Notice of Allowability from the U.S. Patent and Trademark Office for U.S. Appl. No. 13/572,397 dated Jun. 29, 2015 (2 pages). |
Applicant-Initiated Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/540,830 dated Jul. 28, 2017 (6 pages). |
Applicant-Initiated Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/540,830 dated Mar. 24, 2017 (3 pages). |
Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/540,830 dated May 15, 2017 (42 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/540,830 dated Aug. 15, 2017 (8 pages). |
Corrected Notice of Allowability from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/254,627 dated Jul. 13, 2017 (4 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/254,627 dated Apr. 3, 2017 (11 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/095,123 dated Mar. 30, 2017 (10 pages). |
Examiner Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,006 dated Nov. 29, 2018 (1 pages). |
Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,006 dated Oct. 17, 2018 (18 pages). |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,006 dated May 9, 2018 (17 pages). |
Corrected Notice of Allowability from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,006 dated Jan. 28, 2019 (3 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,006 dated Nov. 29, 2018 (12 pages). |
Applicant-Initiated Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/346,530 dated May 17, 2018 (3 pages). |
Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/346,530 dated Sep. 6, 2018 (14 pages). |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/346,530 dated Mar. 26, 2018 (12 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/298,806 dated Apr. 12, 2017 (10 pages). |
Patent Board Decision from the U.S. Patent and Trademark Office for U.S. Appl. No. 11/942,687 dated Dec. 22, 2017 (13 pages). |
Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 11/942,687 dated Jun. 20, 2011 (3 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/043,165 dated Aug. 6, 2018 (11 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/043,165 dated Mar. 19, 2018 (11 pages). |
Patent Board Decision from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/043,165 dated Dec. 20, 2017 (11 pages). |
Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 11/944,000 dated Feb. 4, 2011 (3 pages). |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 11/944,000 dated Oct. 5, 2012 (11 pages). |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,014 dated Jan. 24, 2019 (7 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,023 dated Apr. 11, 2017 (11 pages). |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/792,210 dated Aug. 27, 2018 (15 pages). |
Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/792,210 dated Mar. 5, 2019 (17 pages). |
Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/140,351 dated Dec. 6, 2018 (21 pages). |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/140,351 dated Jul. 30, 2018 (25 pages). |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/140,348 dated Nov. 19, 2018 (33 pages). |
Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 11/179,384 dated Feb. 18, 2009 (2 pages). |
Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 11/179,384 dated Sep. 24, 2008 (4 pages). |
Examiner-Initiated Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 12/857,915 dated Jul. 3, 2014 (1 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/502,055 dated Jun. 2, 2016 (10 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 11/265,979 dated May 13, 2011 (14 pages). |
Examiner-Initiated Interview Summary from the U.S. Patent and Trademark Office for U.S. Appl. No. 13/171,081 dated Sep. 4, 2013 (1 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,006 dated Apr. 10, 2019 (6 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/792,210 dated Jun. 17, 2019 (10 pages). |
Corrected Notice of Allowability from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,006 dated Sep. 4, 2019 (3 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/346,530 dated Aug. 27, 2019 (7 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,014 dated Jul. 11, 2019 (8 pages). |
Corrected Notice of Allowability from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/792,210 dated Sep. 5, 2019 (2 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/188,872 dated Aug. 23, 2019 (10 pages). |
Supplemental Notice of Allowability from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/188,872 dated Oct. 28, 2019 (5 pages). |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/140,346 dated May 28, 2019 (39 pages). |
Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/140,346 dated Oct. 31, 2019 (41 pages). |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/140,363 dated Jun. 3, 2019 (33 pages). |
Advisory Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/140,351 dated Mar. 5, 2019 (4 pages). |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/140,351 dated May 21, 2019 (14 pages). |
Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/140,351 dated Nov. 14, 2019 (14 pages). |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/140,348 dated Jul. 9, 2019 (21 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 14/792,210 dated Oct. 11, 2019 (9 pages). |
Non-Final Office Action from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/140,348 dated Dec. 4, 2019 (21 pages). |
Notice of Allowance from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/188,872 dated Jan. 23, 2020 (9 pages). |
Corrected Notice of Allowability from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,006 dated Feb. 10, 2020 (15 pages). |
Corrected Notice of Allowability from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,006 dated Dec. 12, 2019 (8 pages). |
Corrected Notice of Allowability from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/346,530 dated Dec. 17, 2019 (8 pages). |
Notice of Allowability from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,014 dated Jan. 23, 2020 (4 pages). |
Notice of Allowability from the U.S. Patent and Trademark Office for U.S. Appl. No. 15/292,014 dated Jan. 8, 2020 (4 pages). |
Number | Date | Country | |
---|---|---|---|
20170046014 A1 | Feb 2017 | US |
Number | Date | Country | |
---|---|---|---|
61750662 | Jan 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14139068 | Dec 2013 | US |
Child | 15188819 | US |