US 7,953,614 B1Grant
Smart placement rules
Issue Date:2011-05-31
•23 Claims
•5 Drawing Sheets
Abstract
A smart placement module determines components of received medial data, such as medical reports and image montages, to forward to one or more secondary location, such as an EMR system, based on smart placement rules that are established by a user that receives the medical data, such as a referring doctor. Thus, the smart placement module decreases or removes the need for the receiving user to manually select and transfer certain medical data for storage at the EMR system. Accordingly, the receiving user, and other authorized EMR system users, may have prompt access to the medical data via their respective connections to the EMR system. In one embodiment, the smart placement module transmits a patient identification file that is usable by the receiving EMR system to allow the EMR system to associate received medical data with other data regarding a respective patient.
Metadata
Assignee
- DR Systems, Inc.
Inventors
- Murray A. Reicher
- Cole A. Genovese
- Carol G. Sloyer
- Thomas J. Edwards
Application Information
Application Number:US 11/942,674
Filing Date:2007-11-19
Priority Date:2006-11-22
Art Unit:3686
Classifications
IPC:
G06Q10/00
Patent Drawings (5 sheets)
Description
Cross-Reference to Related Applications
[0001] This application claims the benefit of U.S. Provisional Application No. 60/867,071, filed Nov. 22, 2006, which is hereby incorporated by reference in its entirety herein.
Background of the Invention
[0002] 1. Field of the Invention
[0003] The invention relates to the management and placement of medical data, and more particularly to the smart placement of received medical data within an Electronic Medical Records (EMR) system, for example.
[0004] 2. Description of the Related Art
[0005] Medical data is increasingly being stored in the form of digital documents that can be electronically transmitted and shared between multiple computing devices. EMR systems store various types of medical data, such as images from x-rays and MRIs, montages of images, voice clips, notes, reports, and other text, audio, and/or video from a wide variety of sources. EMR systems receive medical data from physicians or other medical practitioners, for example, that have generated and/or received the medical data from one or more imaging facilities. This medical data often needs to be viewed, manipulated, interpreted, and/or shared between multiple medical members in the same facility or members in one or more distant facility. Accordingly, there is a need for improved systems and methods for the smart placement of medical records so that collaboration among medical faculty can take place.
Summary of the Invention
[0006] In one embodiment, a method of managing medical data received from at least one medical imaging facility, the medical data comprising medical images and medical reports, comprises receiving data from a user indicating a first storage location of an EMR system for storing medical images and a second storage location of the EMR system for storing medical reports received from the imaging facilities, receiving medical images and medical reports from at least one of the medical imaging facilities via one or more networks, associating each of the received medical images and medical reports with respective patients, and transferring the medical images and the medical reports to the EMR system with information indicating the first and second storage locations for the respective medical images and medical reports.
[0007] In one embodiment, a method of manipulating medical data associated with a patient comprises receiving first information from a user of a first computer specifying medical data to be retrieved by the first computer, receiving instructions comprising an indication of a secondary storage location, receiving medical data associated with a patient in response to matching the first information to certain attributes associated with the medical data, and transferring at least some of the medical data to the secondary storage location, wherein the secondary storage location is configured to associate the transferred medical data with other medical data associated with the patient so that the transferred medical data is accessible by users of the secondary storage system.
[0008] In one embodiment, a medical data management system comprises a storage device for storing received medical data associated with a patient and for storing smart placement rules indicating one or more components of medical data to be transferred to an indicated secondary storage location, and a smart placement module for identifying one or more components of the received medical data that are indicated in the smart placement rules and forwarding a copy of the identified one or more components to the secondary storage location.
[0009] In one embodiment, a method of forwarding medical data to a patient records system, the method comprises receiving rules from a user of a computing system, the rules comprising criteria indicating which components of the medical data should be transmitted from a medical image storage device to the computing system and/or when the components should be transmitted to the computing system, receiving a storage location from the user of the computing system indicating where the medical data is to be stored in a patient records system, attaching information to medical data received from the medical image storage device, the information indicating one or more storage locations in the patient record system so that respective storage locations are associated with different components of the received medical data, and transmitting the received medical data and the attached information to the patient records system.
Brief Description of the Drawings
[0010] FIG. 1A is a block diagram of a computing system comprising a computing device in communication with a network and various networked devices.
[0011] FIG. 1B is a block diagram illustrating one embodiment of a computing system comprising a computing device in communication with the imaging device via the network.
[0012] FIG. 2 is a flowchart illustrating one embodiment of a method of automatically forwarding received medical data to one or more predetermined locations based on smart placement rules.
[0013] FIG. 3 is one embodiment of a graphical user interface that may be used to establish smart placement rules.
Detailed Description of the Certain Embodiments
[0014] Embodiments of the invention 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 invention. Furthermore, embodiments of the invention may include several novel features, no single one of which is solely responsible for its desirable attributes or which is essential to practicing the inventions herein described.
[0015] As used herein, the terms “medical data,” “medical-related data,” and “medical records” are defined to include data in any format that is related to a patient. As non-limiting examples, the terms may include, but are not limited to, medical images, such as radiograph, computed tomography (CT), magnetic resonance imaging (MRI), Ultrasound (US), mammogram, positron emission tomography scan (PET), and nuclear scan (NM) images; montages of medical images; medical reports; voice clips, notes; and medical reports. Medical data may be stored in various formats, such as PDF, JPEG, GIF, PNG, DOC, XLS, PPT, MP3, WAV, HTML, XML, and various other formats.
[0016] A “component” of medical data is a category or type of medical data. For example, components of medical data may include an image component comprising medical images and a report component comprising a written report corresponding to the medical images. Components of medical data may include, for example, images, montages, voice clips, notes, and reports.
[0017] FIG. 1A is a block diagram of a computing system 100A comprising a computing device 105A in communication with a network 160 and various networked devices. The computing system 100A may be used to implement certain systems and methods described herein. Depending on the embodiment, the functionality described below with reference to certain components and modules of the computing system 100A may be combined into fewer components and modules or further separated into additional components or modules.
[0018] The exemplary computing device 105 comprises a memory 130, such as random access memory (“RAM”) for temporary storage of information and a read only memory (“ROM”) for permanent storage of information, and a mass storage device 120, such as a hard drive, diskette, or optical media storage device. The mass storage device 120 may comprise one or more hard disk drive, optical drive, networked drive, or some combination of various digital storage systems. The computing device 105 also comprises a central processing unit (CPU) 150 for computation. Typically, the modules of the computing device 105 are in data communication via one or more standards-based bus system. In different embodiments of the present invention, the standards based bus system could be Peripheral Component Interconnect (PCI), Microchannel, SCSI, Industrial Standard Architecture (ISA) and Extended ISA (EISA) architectures, for example.
[0019] The computing device 105 is generally controlled and coordinated by operating system software, such as the Windows 95, 98, NT, 2000, XP, Vista, or other compatible operating systems. In Macintosh systems, the operating system may be any available operating system, such as Mac OS X. In other embodiments, the computing device 105 may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, and I/O services, and provide a user interface, such as a graphical user interface (“GUI”), among other things.
[0020] The exemplary computing device 105A includes one or more of commonly available input/output (I/O) devices and interfaces 110, such as a keyboard, mouse, touchpad, and printer. In one embodiment, the I/O devices and interfaces 110 include one or more display devices, such as a monitor, that allows the visual presentation of data to a user. More particularly, display devices provide for the presentation of GUIs, application software data, and multimedia presentations, for example. According to the systems and methods described below, medical images may be stored on the computing device 105A and automatically transmitted to one or more EMR systems manipulated by the smart placement module 145 based on one or more placement rules established by a user of the computing device 105A. The computing device 105 may also include one or more multimedia devices 140, such as speakers, video cards, graphics accelerators, and microphones, for example.
[0021] In the embodiment of FIG. 1A , the I/O devices and interfaces 110 provide a communication interface to various external devices. In the embodiment of FIG. 1A , the computing device 105A is in data communication with a network 160, such as a LAN, WAN, or the Internet, for example, via a communication link 115. The network 160 may be coupled to various computing devices and/or other electronic devices. In the exemplary embodiment of FIG. 1A , the network 160 is in data communication with an imaging device 170, an Electronic Medical Record (EMR) system 180, a mass storage device 185, and a medical facility 190. Depending on the embodiment, the EMR system 180 may comprise proprietary medical record management software and/or one or more of various available third-party EMR systems. In addition to the devices that are illustrated in FIG. 1A , the network 160 may facilitate communications with other computing, imaging, and storage devices.
[0022] The imaging device 170 may be any type of device that is capable of acquiring medical images, such as MRI, x-ray, mammography, or CT scan systems. In one embodiment, the imaging device 170 is configured to store images and data associated with images. In one embodiment, the imaging device 170 communicates with the computing device 105 via the network 160, or one or more other wired and/or wireless networks, such as a secure LAN, for example. In one embodiment, the image data is stored in Digital Imaging and Communications in Medicine (“DICOM”) format. The complete DICOM specifications, which may be found on the National Electrical Manufactures Association Website at <medical.nema.org>. Also, NEMA PS 3—Digital Imaging and Communications in Medicine, 2004 ed., Global Engineering Documents, Englewood Colo., 2004, is hereby incorporated by reference in its entirety.
[0023] The exemplary EMR system 180 is configured to store digital medical data so that doctors, medical staff, patients, and/or other authorized personnel can effectively view and share the medical data. The EMR system 180 may provide medical data from multiple sources to the computing device 105 via the network 160. Likewise, medical data from the computing device 105 may be provided to other medical facilities, such as the medical facility 190 of FIG. 1A , via the EMR system 180. Depending on the embodiment, the medical facility 190 may include one or more hospitals, clinics, doctor's offices, or any other facility that generates and/or processes medical data. The medical facility 190 may include one or more imaging devices, such as imaging devices that generate the image types described above in the definition of medical data. In one embodiment, multiple computing devices, such as the computing device 105, may be housed at the medical facility 190.
[0024] In the embodiment of FIG. 1A , the smart placement module 145 is configured to forward medical data received by the computing device 105A, such as from the imaging device 170 or the medical facility 190, to one or more EMR systems according to placement rules established by a user of the computing device 105. In one embodiment, medical data is received at the computing device 105 in response to matching of one or more auto-pull rules with particular medical data and/or components of the medical data. For example, in an auto-pull system, either the computing device 105 or a remote server may be configured to periodically select, based upon a user-defined schedule, medical data satisfying the user-specific rules. The user may be authenticated with the remote server in order to determine the user's rights to receive medical data and the selected medical data may then be transmitted to the computing device 105A so that it is locally available for the viewing physician, technician, or other authorized viewer. U.S. Pub. No. 2006/0095423, published on May 4, 2006 to Reicher et al. titled “Systems and Methods for Retrieval of Medical Data,” which is hereby incorporated by reference in its entirety, describes various systems and methods for establishing auto-pull rules for selectively transferring medical data to a computing device.
[0025] In one embodiment, the smart placement module 145 determines components of received medial data to forward to one or more secondary storage locations, such as the EMR system 180 or a specific directory of a local storage device, based on smart placement rules that are established by an authorized user of the computing device 105. Although the description below refers primarily to an EMR system 180 as the secondary storage device, the systems and methods described herein are operable with any suitable secondary storage device, whether local or remote to the computing device 105.
[0026] Through the automatic application of smart placement rules by the smart placement module 145, the need for a user of the computing device 105 to manually select and transfer components of medical data to one or more secondary locations, such as the EMR system 180, is reduced or removed. Accordingly, the smart placement module 145 allows a user of the computing device 105, and other authorized computer users that are in communication with the EMR system 180, to locate data regarding a patient in the EMR system 180. In one embodiment, the smart placement module 145 provides an interface for an authorized user to establish smart placement rules that indicate what components of medical data should be forwarded to one or more secondary storage locations. In one embodiment, smart placement rules may also indicate storage locations for respective components of medical data, such as a directory on a local storage device, a directory on a shared storage device, or a folder in an EMR system, for example. Depending on the embodiment, the smart placement module 145 may be configured to copy the selected components of medical data (e.g., leaving a copy on the computing device 105) or to move the selected components of medical data (e.g., not leaving a copy on the computing device 105) to the selected secondary storage location. In one embodiment, the mass storage device 120 stores the user-specific rules. A further description of the smart placement module 145 and its processes will be discussed below.
[0027] FIG. 1B is a block diagram illustrating one embodiment of a computing system 100B comprising a computing device 105B in communication with the imaging device 170 via the network 160. In the embodiment of FIG. 1B , the computing device 105B comprises a local version of the EMR system 180. In this embodiment, the EMR system 180 may be used exclusively by the computing device 105B, may be used by other devices coupled to the computing device 105B, such as via a secured local area network, and/or may be accessed by any authorized devices that are in communication with the network 160.
[0028] In the embodiment of FIG. 1B , an exemplary temporal flow of data is indicated by the circled numerals 1-3 and is described in further detail below. Depending on the embodiment, certain steps may be removed and additional steps may be added.
[0029] In step one of FIG. 1B , the imaging device 170 transmits medical data to the network 160, and the medical data, such as medical images, reports, and/or other medical information, is received and stored by the computing device 105B. In one embodiment, medical data is selected for transmission to the computing device 105B as a result of matching one or more auto-pull rules that are established by a user of the computing device 105B.
[0030] In step two, the smart placement module 145 of the computing device 105B applies smart placement rules to the received medical data. In one embodiment, the smart placement rules indicate that certain components of medical data is to be copied and/or moved to a secondary storage location either on the computing device 105B, such as in a folder of the EMR system 180, or to another device across the network 160. For example, smart placement rules may indicate that received medical data is to be transferred to a selected EMR system and associated with respective patient data on the EMR system.
[0031] In one embodiment, the smart placement rules indicate one or more components of medical data that are to be transmitted to a selected one or more destinations. For example, a user can establish placement rules indicating that only textual reports are to be transmitted to a selected EMR system, or the user can establish placement rules indicating that all components of received medical data should be transmitted to the selected EMR.
[0032] In step three of FIG. 1B , the indicated components of the received medical data are transmitted to the EMR system 180. In one embodiment, the transmitted components are associated with other medical data of the respective patient(s) at the EMR system 180. In such an embodiment, an authorized user of the EMR system 180 may access the transmitted components via the respective patient's inbox in the EMR system 180. Thus, in one embodiment the smart placement module 145 advantageously automates a process of selecting medical data for transmission to the EMR system 180 so that the medical data may be associated with other medical data associated with the patient at the EMR system 180. Additionally, the smart placement module 145 may be configured to automatically apply smart placement rules when medical data is received at the computing device 105 so that components of the medical data are quickly availably to authorized users of the EMR system, without any intervention by the user.
[0033] In one embodiment, the smart placement module 145 generates a token comprising information indicating one or more software applications associated with components of medical data that are transmitted to the EMR system 180. In one embodiment, the smart placement module 145 determines the appropriate text, graphic, audio, etc., viewer(s) that may be used to present respective data items that are transmitted to the EMR system 180. For example, if the retrieved medical data includes image files, then the token sent by the smart placement module 145 to the EMR system 180 may indicate a specific third-party software viewing application that the viewing system should launch in order to view the image files. In one embodiment, the tokens may designate a class of software application so that the user's default application of a given type of application may be selected when indicated by a token.
[0034] In one embodiment, the smart placement module 145 generates a patient ID file that is transmitted with the indicated components to the EMR system 180. The patient ID file comprises an indication of a patient name, examination date, medical record number, and/or social security number, for example, of a patient associated with the transmitted medical data components. Thus, the patient ID file is usable by the EMR system 180 to place the medical data components in locations associated with the appropriate patient, such as folders, directories, or inboxes associated with respective patients. In other embodiments, the patient ID file may comprise additional information regarding a patient.
[0035] FIG. 2 is a flowchart 200 illustrating one embodiment of a method of automatically forwarding received medical data to one or more predetermined locations based on smart placement rules. The method of FIG. 2A may be initiated in response to receiving new medical data at the computing device 105, such that the medical data is forwarded based on the smart placement rules substantially immediately after being received at the computing device 105. In other embodiments, the method of FIG. 2A is user initiated and may operate on medical data that has been stored on the computing devices or a networked device for an extended period of time. Depending on the embodiment, the flowchart of FIG. 2 may comprise fewer or more blocks and the blocks may be performed in a different order than illustrated.
[0036] Beginning in block 210, smart placement rules are established for movement or copying of medical data components to one or more secondary storage locations. In one embodiment, the smart placement rules comprise default system rules and/or user-specific rules for each user or group of users. Depending on the embodiment, the smart placement rules may include component criteria that must be matched by received medical data in order to trigger an associated smart placement action. For example, a smart placement rule may specify that only an image and report component of medical data is to be transmitted to a particular EMR system. Thus, when new medical data is received, only the image and report components are transmitted to the EMR system. In one embodiment, the smart placement rules indicated separate storage locations for respective medical data components, such as a first location for medical images and a second location for reports. Additionally, in some embodiments, the smart placement rules indicate a format that medical data components should be in prior to transferring to the EMR system, such as HL-7 text format, or PDF format, for example.
[0037] In one embodiment, the smart placement rules may also include criteria associated with header data of certain medical data components, such as time of day and/or date that a component is received by the computing device 105, a referring physician's name, a radiologist name, an exam type, an exam modality, and various other attributes of a components. In one embodiment, default system rules are applied to received medical data if user-specific rules have not been established. FIG. 3 , which is described in further detail below, illustrates an exemplary user interfaces for establishing smart placement rules.
[0038] Moving to block 215, medical data is received at the computing device 105. As noted above, the medical data may be received from any suitable computing device that is in communication with the computing device 105, such as via the network 160. As defined above, the medical data may comprise one or more of multiple files of various formats and may include various information regarding a patient. In one embodiment, the medical data is stored in the mass storage system 120 of the computing device 105.
[0039] Next, in decision block 220 the computing device 105 applies the smart placement rules to the received medical data in order to determine which components of the medical data, if any, should be copied and/or moved to one or more local or remote secondary storage locations. If a smart placement rule matches one or more components of the medical data, the method continues to block 230. If no smart placement rules match with the medical data, the method returns to block 210 where medical data from another exam, another imaging source, and/or associated with another patient is received.
[0040] At block 230, the components of the medical data indicated by the placement rules are selected for transmission to the location indicated in the matching smart placement rule. As noted above, all components may be transmitted to a single location, e.g., a folder on a local or networked storage device or a local or networked EMR system, or the smart placement rules may indicate separate storage locations for respective components of the medical data.
[0041] Moving to block 240, the computing device 105 transmits the selected components to the location or locations associated with the matched smart placement rules. As noted above, in one embodiment a patient ID file indicating one or more attributes of the patient associated with the medical data components is also transmitted to the indicated secondary location. The patient ID file may be used, for example, by the EMR system in associating the transmitted medical data components with other medical data of respective patients. In this embodiment, the medical data of the patient is quickly made available to authorized users of the EMR system by accessing the patient's records stored by the EMR system.
[0042] In one embodiment, the smart placement module 145 generates one or more tokens that are associated with specific components of the transmitted medical data. The tokens comprise information regarding compatible and/or preferred software applications that may be launched in order to view and/or hear an associated medical data component. For example, if the selected medical data comprises a series of CT scan images, a token may be generated to indicate one or more software applications in which the CT images may be viewed. Likewise, a token indicating one or more software application in which a textual report may be viewed may be associated with a textual report component. In one embodiment, the EMR system 180 may display a link and/or icon associated with a token that may be selected by a user of the EMR system 180 in order to access the corresponding medical data in an appropriate software application. Certain tokens may comprise executable software code that launches a desired software application and opens selected medical data components in the software application. For example, an authorized user of the EMR system 180, such as a user of the computing device 105 or another computing device in communication with the network, may select a link associated with a token in order to invoke execution of the token, and subsequent launching of an indicated software application and opening of the corresponding medical data.
[0043] In one embodiment, the EMR system comprises separate patient inboxes wherein some or all of the patient's medical records are stored. In general, a patient's inbox is a location and/or index of locations where the patient's medical data is stored. This method may increase privacy of the medical data for specific patients by only allowing the patient, the patient's doctor, and/or other authorized users to access the patient's medical data.
[0044] FIG. 3 is one embodiment of a graphical user interface 300 that may be used to establish smart placement rules. Depending on the embodiment, the layout of the graphical user interface, the types of input fields, buttons, and checkboxes may be modified. The exemplary graphical user interface 300 comprises a component selection pane 302 that allows a user of the computing device 105, for example, to indicate which components of received medical data should be forwarded to one or more indicated secondary storage locations. In the embodiment of FIG. 3 , check boxes for component types images, montages, voice clips, notes, and reports are provided, where a particular component is selected for transferring to an indicated secondary location if the corresponding checkbox is selected. In other embodiments, other controls may be used in order to allow a user to select one or more components. In other embodiments, fewer or additional components may be available for selection.
[0045] The exemplary user interface of FIG. 3 also comprises smart placement pane 305 that allow a user to select secondary storage locations for report and/or montage components of medical data. In the embodiment of FIG. 3 , the smart placement pane 305 comprises a report copy button 310 that may be selected to indicate that received medical reports should be automatically transmitted to an EMR system, or other storage location, identified in field 315. Similarly, a montage copy button 320 may be selected in order to indicate that received montages should be automatically transmitted to an EMR system, or other storage location, identified in field 325.
[0046] In one embodiment, the smart placement module detects an EMR system that is used by the computing device and automatically populates fields 315, 325 with an indication of the detected EMR system(s). Where multiple EMR systems are detected, the text display fields 315, 325 may comprise drop-down fields that allow the user to select one or more of the EMR systems to which the medical data should be transmitted. In one embodiment, the user is provided with a directory structure that may be navigated in order to locate and select an EMR system or another storage location. In one embodiment, after establishing the smart placement rules, such as using the interface of FIG. 3 , when medical data is received by the computing device 105, the components of the medical data indicated in the component selection pane 302 are automatically forward to the locations indicated in the smart placement pane 305.
[0047] The exemplary smart placement pane 305 further comprises buttons 332, 334, and 336 that allow the user to select a desired format for the medical data that is transmitted to the indicated EMR system. In the embodiment of FIG. 3A , HL-7 text format may be selected by selecting button 332 and PDF format may be selected by selecting button 334. In one embodiment, when button 332 is selected, medical data is converted into the Health Level 7 standard format, which is a widely known standard and format for medical records, before transmitting to the selected EMR system. Similarly, when button 334 is selected, medical data is converted into one or more Adobe PDFs before transmitting to the selected EMR system. The smart placement pane 305 further comprises an other button 336 that allows the user to select other formats for the medical data. In one embodiment, when the button 336 is selected, another user interface comprising additional data formats, such as DOC or RTF, for example, is presented to the user.
[0048] 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. For example, the above-described auto-retrieve may be performed on other types of images, in addition to medical images. For example, images of circuit boards, airplane wings, and satellite imagery may be analyzed using the described systems. 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. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof.
Claims
What is claimed is:
1. A method of managing medical data received from at least one medical imaging facility, the medical data comprising at least medical images and medical reports, the method comprising:
receiving, from a user computing device operated by a user, user defined rules indicating respective storage locations for different types of medical data, the user defined rules including a first storage location of an Internet-accessible storage system for storing medical images from one or more medical data information sources and a second storage location of the Internet-accessible storage system for storing medical reports from one or more medical data information sources, wherein the medical data information sources include one or more of a medical imaging center, a radiology center, or a hospital and the medical images comprise one or more of radiograph, computed tomography (CT), magnetic resonance imaging (MRI), Ultrasound (US), mammogram, positron emission tomography scan (PET), or nuclear scan (NM) images;
intermittently receiving medical data comprising one or more medical reports and medical images from at least one of the medical data information sources via one or more networks;
applying the user defined rules to the intermittently received medical data, wherein said applying comprises:
identifying, by a computing system, a medical image in the intermittently received medical data;
associating, by the computing system, the identified medical image with a corresponding patient;
associating the identified medical image with the first storage location of the user defined rules;
initiating transmission of the identified medical image to the Internet-accessible storage system with information indicating that the medical image is to be stored at the first storage location;
identifying, by the computing system, a medical report in the intermittently received medical data;
associating, by the computing system, the identified medical report with a corresponding patient;
associating the identified medical report with the second storage location of the user defined rules;
initiating transmission of the identified medical report to the Internet-accessible storage system with information indicating that the medical report is to be stored at the second storage location.
2. The method of claim 1, further comprising transferring a patient identification file to the Internet-accessible storage system, the patient identification file comprising data that is usable by the Internet-accessible storage system to associate the medical images and medical reports of a particular patient with other data associated with the particular patient.
3. The method of claim 2, wherein the Internet-accessible storage system stores the transferred medical images and medical reports in a patient-specific location that is determined based on the patient identification file.
4. The method of claim 3, where the patient-specific location is an in-box associated with the respective patient.
5. The method of claim 2, wherein the patient identification file is formatted according to parameters associated with the Internet-accessible storage system.
6. The method of claim 2, wherein the patient identification file comprises indications of one or more of a last name, a first name, an address, a social security number, an electronic medical records identification number, and a medical record number associated with the patient.
7. The method of claim 1, wherein the medical images and medical reports comprise text and/or audio data.
8. The method of claim 1, wherein the computing system comprises the user computing device.
9. The method of claim 8, wherein said applying is performed by the user computing device.
10. A computer readable medium having instruction encoded thereon, the instruction configured for reading by a computing system in order to cause the computing system to perform operations comprising:
receiving user defined rules indicating respective storage locations for different types of medical data, the user defined rules including a first storage location of an Internet-accessible storage system for storing medical images from one or more medical data information sources and a second storage location of the Internet-accessible storage system for storing medical reports from one or more medical data information sources, wherein the medical data information sources include one or more of a medical imaging center, a radiology center, or a hospital and the medical images comprise one or more of radiograph, computed tomography (CT), magnetic resonance imaging (MRI), Ultrasound (US), mammogram, positron emission tomography scan (PET), or nuclear scan (NM) images;
intermittently receiving medical data comprising one or more medical reports and medical images from at least one of the medical data information sources via one or more networks;
applying the user defined rules to the intermittently received medical data, wherein said applying comprises:
identifying a medical image in the intermittently received medical data;
associating the identified medical image with a corresponding patient;
associating the identified medical image with the first storage location of the user defined rules;
initiating transmission of the identified medical image to the Internet-accessible storage system with information indicating that the medical image is to be stored at the first storage location;
identifying a medical report in the intermittently received medical data;
associating the identified medical report with a corresponding patient;
associating the identified medical report with the second storage location of the user defined rules;
initiating transmission of the identified medical report to the Internet-accessible storage system with information indicating that the medical report is to be stored at the second storage location.
11. The computer readable medium of claim 10, wherein the operations further comprise:
transferring a patient identification file to the Internet-accessible storage system, the patient identification file comprising data that is usable by the Internet-accessible storage system to associate the medical images and medical reports of a particular patient with other data associated with the particular patient.
12. The computer readable medium of claim 11, wherein the Internet-accessible storage system stores the transferred medical images and medical reports in a patient-specific location that is determined based on the patient identification file.
13. The computer readable medium of claim 12, where the patient-specific location is an in-box associated with the respective patient.
14. The computer readable medium of claim 11, wherein the patient identification file is formatted according to parameters associated with the Internet-accessible storage system.
15. The computer readable medium of claim 11, wherein the patient identification file comprises indications of one or more of a last name, a first name, an address, a social security number, an electronic medical records identification number, and a medical record number associated with the patient.
16. The computer readable medium of claim 10, wherein the medical images and medical reports comprise text and/or audio data.
17. A computing system comprising:
one or more hardware processors configured to execute software code;
one or more computer readable medium storing software code for execution by the one or more processors in order to cause the computing system to:
access user defined rules indicating respective storage locations for different types of medical data, the user defined rules including a first storage location of an Internet-accessible storage system for storing medical images from one or more medical data information sources and a second storage location of the Internet-accessible storage system for storing medical reports from one or more medical data information sources, wherein the medical data information sources include one or more of a medical imaging center, a radiology center, or a hospital and the medical images comprise one or more of radiograph, computed tomography (CT), magnetic resonance imaging (MRI), Ultrasound (US), mammogram, positron emission tomography scan (PET), or nuclear scan (NM) images;
intermittently identify medical data comprising one or more medical reports and medical images transmitted from at least one of the medical data information sources via one or more networks;
apply the user defined rules to the intermittently identified medical data, wherein said applying comprises:
identifying a medical image in the medical data;
associating the identified medical image with a corresponding patient;
associating the identified medical image with the first storage location of the user defined rules;
initiating transmission of the identified medical image to the Internet-accessible storage system with information indicating that the medical image is to be stored at the first storage location;
identifying a medical report in the medical data;
associating the identified medical report with a corresponding patient;
associating the identified medical report with the second storage location of the user defined rules;
initiating transmission of the identified medical report to the Internet-accessible storage system with information indicating that the medical report is to be stored at the second storage location.
18. The computing system of claim 17, further comprising transferring a patient identification file to the Internet-accessible storage system, the patient identification file comprising data that is usable by the Internet-accessible storage system to associate the medical images and medical reports of a particular patient with other data associated with the particular patient.
19. The computing system of claim 18, wherein the Internet-accessible storage system stores the transferred medical images and medical reports in a patient-specific location that is determined based on the patient identification file.
20. The computing system of claim 19, where the patient-specific location is an in-box associated with the respective patient.
21. The computing system of claim 18, wherein the patient identification file is formatted according to parameters associated with the Internet-accessible storage system.
22. The computing system of claim 18, wherein the patient identification file comprises indications of one or more of a last name, a first name, an address, a social security number, an electronic medical records identification number, and a medical record number associated with the patient.
23. The computing system of claim 17, wherein the medical images and medical reports comprise text and/or audio data.
Patent Citations (110)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4672683(A) | 1987-06-01 | Matsueda | Applicant |
| US5123056(A) | 1992-06-01 | Wilson | Applicant |
| US5431161(A) | 1995-07-01 | Ryals et al. | Applicant |
| US5452416(A) | 1995-09-01 | Hilton et al. | Applicant |
| US5734915(A) | 1998-03-01 | Roewer | Applicant |
| US5740267(A) | 1998-04-01 | Echerer et al. | Applicant |
| US5779634(A) | 1998-07-01 | Ema et al. | Applicant |
| US5852646(A) | 1998-12-01 | Klotz et al. | Applicant |
| US5926568(A) | 1999-07-01 | Chaney et al. | Applicant |
| US5954650(A) | 1999-09-01 | Saito et al. | Applicant |
| US5976088(A) | 1999-11-01 | Urbano et al. | Applicant |
| US5987345(A) | 1999-11-01 | Engelmann et al. | Applicant |
| US5995644(A) | 1999-11-01 | Lai et al. | Applicant |
| US6115486(A) | 2000-09-01 | Cantoni | Applicant |
| US6151581(A) | 2000-11-01 | Kraftson et al. | Applicant |
| US6175643(B1) | 2001-01-01 | Lai et al. | Applicant |
| US6185320(B1) | 2001-02-01 | Bick et al. | Applicant |
| US6304667(B1) | 2001-10-01 | Reitano | Applicant |
| US6347329(B1) | 2002-02-01 | Evans | Examiner |
| US6351547(B1) | 2002-02-01 | Johnson et al. | Applicant |
| US6424996(B1) | 2002-07-01 | Killcommons et al. | Applicant |
| US6463169(B1) | 2002-10-01 | Ino et al. | Applicant |
| US6532299(B1) | 2003-03-01 | Sachdeva et al. | Applicant |
| US6532311(B1) | 2003-03-01 | Pritt | Applicant |
| US6556695(B1) | 2003-04-01 | Packer et al. | Applicant |
| US6563950(B1) | 2003-05-01 | Wiskott et al. | Applicant |
| US6574629(B1) | 2003-06-01 | Cooke et al. | Applicant |
| US6577753(B2) | 2003-06-01 | Ogawa | Applicant |
| US6603494(B1) | 2003-08-01 | Banks et al. | Applicant |
| US6630937(B2) | 2003-10-01 | Kallergi et al. | Applicant |
| US6678764(B2) | 2004-01-01 | Parvelescu et al. | Applicant |
| US6697506(B1) | 2004-02-01 | Qian et al. | Applicant |
| US6775402(B2) | 2004-08-01 | Bacus et al. | Applicant |
| US6778689(B1) | 2004-08-01 | Aksit et al. | Applicant |
| US6820100(B2) | 2004-11-01 | Funahashi | Applicant |
| US6829377(B2) | 2004-12-01 | Milioto | Applicant |
| US6864794(B2) | 2005-03-01 | Betz | Applicant |
| US6886133(B2) | 2005-04-01 | Bailey et al. | Applicant |
| US6891920(B1) | 2005-05-01 | Minyard et al. | Applicant |
| US6917696(B2) | 2005-07-01 | Soenksen | Applicant |
| US6996205(B2) | 2006-02-01 | Capolunghi et al. | Applicant |
| US7022073(B2) | 2006-04-01 | Fan et al. | Applicant |
| US7027633(B2) | 2006-04-01 | Foran et al. | Applicant |
| US7031846(B2) | 2006-04-01 | Kaushikkar et al. | Applicant |
| US7043474(B2) | 2006-05-01 | Mojsilovic | Applicant |
| US7050620(B2) | 2006-05-01 | Heckman | Applicant |
| US7092572(B2) | 2006-08-01 | Huang et al. | Applicant |
| US7103205(B2) | 2006-09-01 | Wang et al. | Applicant |
| US7106479(B2) | 2006-09-01 | Roy et al. | Applicant |
| US7110616(B2) | 2006-09-01 | Ditt et al. | Applicant |
| US7155043(B2) | 2006-12-01 | Daw | Applicant |
| US7170532(B2) | 2007-01-01 | Sako | Applicant |
| US7174054(B2) | 2007-02-01 | Manber et al. | Applicant |
| US7209149(B2) | 2007-04-01 | Jogo | Applicant |
| US7212661(B2) | 2007-05-01 | Samara et al. | Applicant |
| US7218763(B2) | 2007-05-01 | Belykh et al. | Applicant |
| US7224852(B2) | 2007-05-01 | Lipton et al. | Applicant |
| US7263710(B1) | 2007-08-01 | Hummell et al. | Applicant |
| US7272610(B2) | 2007-09-01 | Torres | Applicant |
| US7412111(B2) | 2008-08-01 | Battle et al. | Applicant |
| US7450747(B2) | 2008-11-01 | Jabri et al. | Applicant |
| US7526114(B2) | 2009-04-01 | Seul et al. | Applicant |
| US7545965(B2) | 2009-06-01 | Suzuki et al. | Applicant |
| US7583861(B2) | 2009-09-01 | Hanna et al. | Applicant |
| US7613335(B2) | 2009-11-01 | McLennan et al. | Applicant |
| US7634121(B2) | 2009-12-01 | Novatzky et al. | Applicant |
| US7636413(B2) | 2009-12-01 | Toth | Applicant |
| US7660488(B2) | 2010-02-01 | Reicher et al. | Applicant |
| US7787672(B2) | 2010-08-01 | Reicher et al. | Applicant |
| US7885440(B2) | 2011-02-01 | Fram et al. | Applicant |
| US2002/0016718(A1) | 2002-02-01 | Rothschild et al. | Applicant |
| US2002/0021828(A1) | 2002-02-01 | Papier et al. | Applicant |
| US2002/0044696(A1) | 2002-04-01 | Sirohey et al. | Applicant |
| US2002/0091659(A1) | 2002-07-01 | Beaulieu et al. | Applicant |
| US2002/0103827(A1) | 2002-08-01 | Sesek | Applicant |
| US2002/0110285(A1) | 2002-08-01 | Wang et al. | Applicant |
| US2003/0028402(A1) | 2003-02-01 | Ulrich et al. | Applicant |
| US2003/0115083(A1) | 2003-06-01 | Masarie et al. | Applicant |
| US2004/0024303(A1) | 2004-02-01 | Banks et al. | Applicant |
| US2004/0086163(A1) | 2004-05-01 | Moriyama et al. | Applicant |
| US2004/0114714(A1) | 2004-06-01 | Minyard et al. | Applicant |
| US2004/0161164(A1) | 2004-08-01 | Dewaele | Applicant |
| US2004/0165791(A1) | 2004-08-01 | Kaltanji | Applicant |
| US2004/0243435(A1) | 2004-12-01 | Williams | Applicant |
| US2004/0254816(A1) | 2004-12-01 | Myers | Applicant |
| US2005/0027570(A1) | 2005-02-01 | Maier et al. | Applicant |
| US2005/0043970(A1) | 2005-02-01 | Hsieh | Applicant |
| US2005/0065424(A1) | 2005-03-01 | Shah et al. | Applicant |
| US2005/0114178(A1) | 2005-05-01 | Krishnamurthy et al. | Applicant |
| US2005/0114179(A1) | 2005-05-01 | Brackett et al. | Applicant |
| US2005/0114283(A1) | 2005-05-01 | Pearson et al. | Applicant |
| US2005/0184988(A1) | 2005-08-01 | Yanof et al. | Applicant |
| US2005/0197860(A1) | 2005-09-01 | Joffe et al. | Examiner |
| US2005/0273009(A1) | 2005-12-01 | Deischinger et al. | Applicant |
| US2006/0093198(A1) | 2006-05-01 | Fram et al. | Applicant |
| US2006/0093199(A1) | 2006-05-01 | Fram et al. | Applicant |
| US2006/0095423(A1) | 2006-05-01 | Reicher et al. | Applicant |
| US2006/0095426(A1) | 2006-05-01 | Takachio et al. | Applicant |
| US2006/0106642(A1) | 2006-05-01 | Reicher et al. | Applicant |
| US2006/0111941(A1) | 2006-05-01 | Blom | Applicant |
| US2007/0050701(A1) | 2007-03-01 | El Emam et al. | Applicant |
| US2007/0055550(A1) | 2007-03-01 | Courtney et al. | Examiner |
| US2007/0067124(A1) | 2007-03-01 | Kimpe et al. | Applicant |
| US2007/0073556(A1) | 2007-03-01 | Lau et al. | Applicant |
| US2007/0174079(A1) | 2007-07-01 | Kraus | Applicant |
| US2007/0239481(A1) | 2007-10-01 | DiSilvestro et al. | Applicant |
| US2008/0103828(A1) | 2008-05-01 | Squilla et al. | Examiner |
| US2010/0138239(A1) | 2010-06-01 | Reicher et al. | Applicant |
| US2010/0201714(A1) | 2010-08-01 | Reicher | Applicant |
| US2011/0016430(A1) | 2011-01-01 | Fram et al. | Applicant |
Non-Patent Literature (44)
- US 7,801,341, 09/2010, Fram et al. (withdrawn)Applicant
- 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.Applicant
- Non-Final Office Action dated Aug. 28, 2007 in U.S. Appl. No. 11/179,384.Applicant
- Final Office Action dated Jun. 26, 2008 in U.S. Appl. No. 11/179,384.Applicant
- Non-Final Office Action dated Dec. 29, 2008 in U.S. Appl. No. 11/179,384.Applicant
- Final Office Action dated Jul. 24, 2009, in U.S. Appl. No. 11/179,384.Applicant
- Notice of Allowance dated Nov. 3, 2009, in U.S. Appl. No. 11/179,384.Applicant
- Non-Final Office Action dated Oct. 1, 2009, in U.S. Appl. No. 11/268,261.Applicant
- Notice of Allowance dated Feb. 2, 2010, in U.S. Appl. No. 11/268,261.Applicant
- Notice of Allowance dated May 17, 2010, in U.S. Appl. No. 11/268,261.Applicant
- Supplemental Notice of Allowance dated Aug. 6, 2010, in U.S. Appl. No. 11/268,261.Applicant
- Non-Final Office Action dated May 13, 2009, in U.S. Appl. No. 11/265,979.Applicant
- Final Office Action dated Dec. 22, 2009 in U.S. Appl. No. 11/265,979.Applicant
- Non-Final Office Action dated Jul. 8, 2010 in U.S. Appl. No. 11/265,979.Applicant
- Non-Final Office Action dated Aug. 24, 2009 in U.S. Appl. No. 11/268,262.Applicant
- Non-Final Office Action dated Apr. 16, 2010 in U.S. Appl. No. 11/268,262.Applicant
- Non-Final Office Action dated Jul. 27, 2009 in U.S. Appl. No. 11/265,978.Applicant
- Notice of Allowance dated Nov. 19, 2009 in U.S. Appl. No. 11/265,978.Applicant
- Notice of Allowance dated Apr. 19, 2010 in U.S. Appl. No. 11/265,978.Applicant
- Supplemental Notice of Allowance dated May 3, 2010 in U.S. Appl. No. 11/265,978.Applicant
- Supplemental Notice of Allowance dated Aug. 3, 2010 in U.S. Appl. No. 11/265,978.Applicant
- Non-Final Office Action dated Apr. 14, 2010 in U.S. Appl. No. 11/944,027.Applicant
- Interview Summary dated May 14, 2010, in U.S. Appl. No. 11/268,261.Applicant
- Interview Summary dated Mar. 4, 2010 in U.S. Appl. No. 11/265,979.Applicant
- Interview Summary dated Nov. 24, 2009 in U.S. Appl. No. 11/268,262.Applicant
- Interview Summary dated May 12, 2010 in U.S. Appl. No. 11/268,262.Applicant
- Interview Summary dated Jul. 26, 2010 in U.S. Appl. No. 11/942,673.Applicant
- Interview Summary dated May 13, 2010 in U.S. Appl. No. 11/944,027.Applicant
- Non-Final Office Action dated Aug. 18, 2010 in U. S. Appl. No. 12/702,976.Applicant
- NonFinal Office Action dated Sep. 16, 2010 in U.S. Appl. No. 11/942,687.Applicant
- Interview Summary dated Dec. 1, 2010, 2010 in U. S. Appl. No. 12/702,976.Applicant
- Final Office Action dated Feb. 17, 2011 in U.S. Appl. No. 12/702,976.Applicant
- Notice of Allowance dated Oct. 8, 2010, in U.S. Appl. No. 11/268,261.Applicant
- Notice of Allowance dated Dec. 3, 2010, in U.S. Appl. No. 11/268,261.Applicant
- Notice of Allowance dated Jan. 6, 2011, in U.S. Appl. No. 11/268,261.Applicant
- Interview Summary dated Nov. 16, 2010 in U.S. Appl. No. 11/265,979.Applicant
- Final Office Action dated Dec. 23, 2010 in U.S. Appl. No. 11/265,979.Applicant
- Final Office Action dated Oct. 28, 2010 in U.S. Appl. No. 11/268,262.Applicant
- Interview Summary dated Dec. 1, 2010 in U.S. Appl. No. 11/268,262.Applicant
- Notice of Allowance dated Dec. 1, 2010 in U.S. Appl. No. 11/268,262.Applicant
- Notice of Allowance dated Feb. 25, 2011 in U.S. Appl. No. 11/268,262.Applicant
- Interview Summary dated Dec. 3, 2010 in U.S. Appl. No. 11/942,687.Applicant
- Final Office Action dated Dec. 23, 2010 in U.S. Appl. No. 11/944,027.Applicant
- Non-Final Office Action dated Sep. 29, 2010 in U.S. Appl. No. 11/944,000.Applicant