METHOD AND SYSTEM FOR AUTOMATED DIFFERENTIAL MEDICAL DIAGNOSIS ASSESMENT

A method and system for automated differential medical diagnosis. Final diagnosis information including a final diagnosis for one or more patient complaints for a specific patient at a medical facility and differential diagnosis information including one or more likely differential diagnoses and one or more critical differential diagnoses associated with the final diagnosis for the specific patient at the medical facility, a visit summary, a medical record and a treatment plan or the specific patient at the medical facility are determined. Plural different types of complexities and plural types of risks associated with determining the final diagnosis, the one or more differential diagnoses, the one or more critical diagnosis associated with the final diagnosis, the visit summary, the medical record and the treatment plan for the one or more patient complaints for the specific patient at the medical facility are reduced.

CROSS REFERENCES TO RELATED APPLICATIONS

Not Applicable.

COPYRIGHT NOTICE

Pursuant to 37 C.F.R. 1.71(e), applicants note that a portion of this disclosure contains material that is subject to, for which is claimed copyright protection, such as, but not limited to, copies of screen shots and other aspects of this submission for which copyright protection is or may be available in any jurisdiction. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or patent disclosure, as it appears in the Patent Office patent file or records. All other rights are reserved, and all other reproduction, distribution, creation of derivative works based on the contents, public display, and public performance of this patent application, any issued patent resulting from this patent application or any part thereof, are prohibited by applicable copyright law.

FIELD OF INVENTION

This invention relates to medical diagnosis. More specifically, it relates to a method and system for providing automated differential medical diagnosis assessment.

BACKGROUND OF THE INVENTION

There are many different types of medical information that are routinely collected when a patient has an emergency or non-emergency medical problem, or visit a provider for a routine visit or annual physical. The medical information includes such information as a patient history including current symptoms the patient is feeling, any medication the patient is currently taking, any past medical problems or surgeries the patient has, known allergies, other family history, prescribed medications, etc. The patient history is used to determine a final diagnosis and one or more differential diagnoses for one or more patient complaints.

In medicine, a “differential diagnosis” is a method of analysis that distinguishes a particular disease or condition from others that present with similar clinical features.

Determining a final diagnosis and one or more differential diagnoses from a patient encounter is complex and presents many risks, even for an experienced medical doctor. There is a significant risk of complications, morbidity, mortality, associated with the patient's complaints due to misdiagnoses of medical problems associated with the patient complaints. A patient risk diagnosis is based on the patient's current health status, past health history, and other risk factors that may increase the patient's likelihood of experiencing a health problem.

Patient morbidity is defined as a patient having a disease or a symptom of a disease. Patient mortality is defined as a death rate, or a number of deaths in a certain group of people in a certain period of time.

According the American College of Cardiology, a number of possible diagnoses and differential diagnoses that must be considered is based on a number and types of patient complaints addressed during a patient encounter significantly increases a complexity of establishing a correct medical diagnosis, and treatment plan decisions that are made by the medical doctor.

According to WEBMD, an estimated 795,000 people in the U.S. die or are permanently disabled each year due to misdiagnoses of medical problems. Strokes top the list of misdiagnosed medical problems that cause serious harm in a patient. On average, medical researchers estimate that 11% of patient complaints result in a misdiagnosis, although the error rate varies widely depending on a disease. It has been estimated that reducing diagnostic errors by 50% for stroke, sepsis, other infections, pneumonia, pulmonary embolism and lung cancer could cut permanent disabilities and deaths by 150,000 per year.

There have been a number of automated solutions to evaluate patient complaints in medical facilities and determine medical diagnoses.

For example, U.S. Pat. No. 7,624,027, that issued to Stern, et. al. teaches “a method and system for automated medical records processing. The method and system includes plural paper and electronic templates specifically designed such that they reduce the complexity of collecting patient encounter information and help generate the appropriate number and type medical codes for a specific type of medical practice when processed. The method and system also includes processing applications that allow easy and automated collection, processing, displaying and recording of medical codes (e.g., diagnosis codes, billing codes, insurance codes, etc.). The medical codes and other types of processed patient encounter information are displayed in real-time on electronic templates immediately after a patient encounter.”

U.S. Pat. No. 8,606,594, that issued to Stern, et al. teaches “A method and system for automated medical records processing. The method and system includes plural electronic medical templates specifically designed such that they reduce the complexity and risk associated with collecting patient encounter information, creating a medical diagnosis and help generate the appropriate number and type medical codes for a specific type of medical practice when processed. The medical codes and other types of processed patient encounter information are displayed in real-time on electronic medical records and invoices immediately after a patient encounter.”

U.S. Pat. No. 9,842,188, that issued to Stern teaches “A method and system for automated medical records processing with cloud computing. The method and system includes plural electronic medical templates specifically designed such that they reduce the complexity and risk associated with collecting patient encounter information, creating a medical diagnosis and help generate the appropriate number and type medical codes for a specific type of medical practice when processed. The medical codes and other types of processed patient encounter information are displayed in real-time on electronic medical records and invoices immediately after a patient encounter via a cloud computing network.”

U.S. Pat. No. 10,714,213, that issued to Stern, teaches “A method and system for automated medical records processing with cloud computing including patient tracking for actual and virtual encounters. The method and system includes plural electronic medical templates specifically designed such that they reduce the complexity and risk associated with collecting patient encounter information, creating a medical diagnosis, tracking the patient through the medical processes at the medical facility and generate the appropriate number and type medical codes for a specific type of medical practice when processed. The medical codes and other types of processed actual or virtual patient encounter information are displayed in real-time on electronic medical records and invoices immediately after an actual or virtual patient encounter via a cloud computing network.

U.S. Pat. No. 11,861,353, that issued to Stern, teaches “A method and system for automated medical records processing with telemedicine is presented. The method and system includes plural electronic medical templates specifically designed such that they reduce the complexity and risk associated with collecting virtual patient encounter information, creating a medical diagnosis, tracking the patient through the medical processes during a telemedicine session and generate the appropriate number and type medical codes for a specific type of medical practice when processed. The medical codes and other types of processed virtual patient encounter information are displayed in real-time on electronic medical records and invoices immediately after a virtual patient encounter from a telemedicine visit.

However, none of these solutions solve all of the problems associated with differential medical diagnosis assessment. Thus, it is desirable to solve some of problems associated with automated differential medical diagnosis assessment.

SUMMARY OF THE INVENTION

In accordance with preferred embodiments of the present invention, some of the problems associated with automated differential medical diagnosis are overcome. A method and system for automated differential medical diagnosis assessment is presented.

Final diagnosis information including a final diagnosis for one or more patient complaints for a specific patient at a medical facility and plural differential diagnosis information including one or more likely differential diagnoses and one or more critical differential diagnoses associated with the final diagnosis for the specific patient at the medical facility, a visit summary, a medical record and a treatment plan or the specific patient at the medical facility are automatically determined. Plural different types of complexities and plural types of risks associated with determining the final diagnosis, the one or more differential diagnoses, the one or more critical diagnosis associated with the final diagnosis, the visit summary, the medical record and the treatment plan for the one or more patient complaints for the specific patient at the medical facility are reduced.

The foregoing and other features and advantages of preferred embodiments of the present invention will be more readily apparent from the following detailed description. The detailed description proceeds with references to the accompanying drawings.

DETAILED DESCRIPTION OF THE INVENTION

Exemplary Electronic Automated Differential Medical Diagnosis Assessment Processing and Display System

FIG.1is a block diagram illustrating an exemplary electronic automated differential medical diagnosis assessment processing and display system10. The exemplary electronic system10includes, but is not limited to, one or more target network devices12,14,16, etc. each with one or more processors and each with a non-transitory computer readable medium.

The one or more target network devices12,14,16,31,33and/or wearable network devices98-104(FIG.6), are used by a medical doctor17and/or other medical professional (e.g., nurse, nurse practitioner, physician assistant, etc.) to collect medical information including one or more complaints13for a specific patent19at a medical facility21.

In one embodiment, the specific patient19is physically located at the medical facility21with the medical doctor17(or other medical personnel, etc.). In another embodiment, the specific patient19is not physically located at the medical facility21, but is in contact with the medical doctor17(or other medical personnel, etc.) who are at the medical facility21via the communications network18,18′ (e.g., via telephone, video conference, email, text, etc.). In another embodiment, the medical doctor17(or other medical personnel, etc.) is remote to the medical facility21and the specific patient19is physically located the medical facility21. In other embodiment, both the medical doctor17(or other medical personnel, etc.) are both remote to the medical facility21(e.g., telemedicine, etc.). However, the present is not limited to such embodiments and other embodiments may be used to practice the invention.

The one or more target network devices12,14,16(illustrated inFIG.1only as a tablet and two smart phones for simplicity) also include, but are not limited to, desktop and laptop computers, tablet computers, smart phones, Internet phones, Internet appliances, personal digital/data assistants (PDA), cable television (CATV), satellite television (SATV) and Internet television set-top boxes, digital televisions including high definition television (HDTV), three-dimensional (3DTV) televisions, Internet of Things (IOT) devices,31, smart speakers33, wearable network devices98-104(FIG.6) and/or other types of target network devices. However, more, fewer and/or types of target network devices can be use to practice the invention.

A “smart phone” is a mobile phone14that offers more advanced computing ability and connectivity than a contemporary basic feature phone. Smart phones and feature phones may be thought of as handheld computers integrated with a mobile telephone, but while most feature phones are able to run applications based on platforms such as JAVA ME, a smart phone usually allows the user to install and run more advanced applications. Smart phones and/or tablet computers run complete operating system software providing a platform for application developers.

The tablet computers12,12′ include, but are not limited to, tablet computers such as the IPAD, by APPLE, Inc., the HP Tablet, by HEWLETT PACKARD, Inc., the PLAYBOOK, by RIM, Inc., the TABLET, by SONY, Inc., etc.

A “smart speaker”33is a type of wireless speaker and voice command device with an integrated virtual assistant that offers interactive actions and hands-free activation with the help of one “hot word” (or several “hot words”). Some smart speakers can also act as a smart device that utilizes Wi-Fi, BLUETOOTH and other wireless protocol standards to extend usage beyond audio playback, such as to control home automation devices. This can include, but is not be limited to, features such as compatibility across a number of services and platforms, peer-to-peer connection through mesh networking, virtual assistants, and others. Each can have its own designated interface and features in-house, usually launched or controlled via application or home automation software. Some smart speakers also include a screen to show the user a visual response.

The target network devices12,14,16,31,33,98-104are in communications with a cloud communications network18or a non-cloud computing network18′ via one or more wired and/or wireless communications interfaces. The cloud communications network18, is also called a “cloud computing network” herein and the terms may be used interchangeably.

The cloud communications network18and non-cloud communications network18′ includes, but is not limited to, communications over a wire connected to the target network devices, wireless communications, and other types of communications using one or more communications and/or networking protocols.

Plural server network devices20,22,24,26(only four of which are illustrated for simplicity) each with one or more processors and a non-transitory computer readable medium include one or more associated databases20′,22′,24′,26′. The plural network devices20,22,24,26are in communications with the one or more target devices12,14,16,31,33,98-104via the cloud communications network18and non-cloud communications network18′.

Plural server network devices20,22,24,26(only four of which are illustrated for simplicity) are physically located on one more public networks76(SeeFIG.4), private networks72, community networks74and/or hybrid networks78comprising the cloud network18.

One or more server network devices (e.g.,20,22,24,26, etc.) store portions of the electronic content13,13a,15(e.g., SMS, MMS, RCS messages, etc.) as cloud storage objects82(FIG.5) as is described herein.

The plural server network devices20,22,2426, may be connected to, but are not limited to, World Wide Web servers, Internet servers, search engine servers, vertical search engine servers, social networking site servers, file servers, other types of electronic information servers, and other types of server network devices (e.g., edge servers, firewalls, routers, gateways, etc.).

The plural server network devices20,22,24,26also include, but are not limited to, network servers used for cloud computing18providers, etc.

The cloud communications network18and non-cloud communications network18′ includes, but is not limited to, a wired and/or wireless communications network comprising one or more portions of: the Internet, an intranet, a Local Area Network (LAN), a wireless LAN (WiLAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a Public Switched Telephone Network (PSTN), a Wireless Personal Area Network (WPAN) and other types of wired and/or wireless communications networks18.

The cloud communications network18and non-cloud communications network18′ includes one or more gateways, routers, bridges and/or switches. A gateway connects computer networks using different network protocols and/or operating at different transmission capacities. A router receives transmitted messages and forwards them to their correct destinations over the most efficient available route. A bridge is a device that connects networks using the same communications protocols so that information can be passed from one network device to another. A switch is a device that filters and forwards packets between network segments based on some pre-determined sequence (e.g., timing, sequence number, etc.).

An operating environment for the network devices of the exemplary electronic information display system10include a processing system with one or more high speed Central Processing Unit(s) (CPU), processors, non-transitory computer readable mediums, and/or one or other types of memories. In accordance with the practices of persons skilled in the art of computer programming, the present invention is described below with reference to acts and symbolic representations of operations or instructions that are performed by the processing system, unless indicated otherwise. Such acts and operations or instructions are referred to as being “computer-executed,” “CPU-executed,” or “processor-executed.”

It will be appreciated that acts and symbolically represented operations or instructions include the manipulation of electrical information by the CPU or processor. An electrical system represents data bits which cause a resulting transformation or reduction of the electrical information, biological information, quantum information and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's or processor's operation, as well as other processing of information. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, organic quantum properties corresponding to the data bits.

The data bits may also be maintained on a non-transitory computer readable medium including magnetic disks, optical disks, organic memory, quantum memory and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM), flash memory, etc.) mass storage system readable by the CPU. The non-transitory computer readable medium includes cooperating or interconnected computer readable medium, which exist exclusively on the processing system or can be distributed among multiple interconnected processing systems that may be local or remote to the processing system.

Exemplary Electronic Content Display System

FIG.2is a block diagram illustrating an exemplary electronic automated differential medical diagnosis assessment display system28. The exemplary electronic message information display system12′ includes, but is not limited to a target network device (e.g.,12, etc.) with an application30and a display component32. The applications30,30apresents a graphical user interface (GUI)34on the display32component. The GUI32presents a multi-window36,36′, etc. (only two of which are illustrated) interface to a user (e.g., medical doctor17, etc.).FIG.2illustrates a graphical electronic patient intake form35. In one embodiment, patient intake form35, includes those provided by U.S. Pat. No. 9,142,988, that issued to Stern. However, the present invention is not limited to such an embodiment and other embodiments can be used to practice the invention.

In one embodiment of the invention, the application30,30ais a software application. However, the present invention is not limited to this embodiment and the application30,30acan be hardware, firmware, hardware and/or any combination thereof. In one embodiment, the application30,30aincludes a mobile application for a smart phone, electronic tablet and/or other network device. In one embodiment, the application30,30aincludes web-browser based application. In one embodiment, the application30,30aincludes a web-chat client application. In another embodiment, the application30a,30b,30c,30d,30e,30fincludes a cloud application used on a cloud communications network18as a Software as a Service (SaaS). However, the present invention is not limited these embodiments and other embodiments can be used to practice the invention

In another embodiment, a portion of the application30is executing on the target network devices12,14,16,31,33,98-104and another portion of the application30a,30b,30c,30d,30e,30fis executing on the server network devices20,22,24,26. The applications also include one or more library applications (e.g., Application Programming Interface (API), etc.) However, the present invention is not limited these embodiments and other embodiments can be used to practice the invention.

Exemplary Networking Protocol Stack

FIG.3a block diagram illustrating a layered protocol stack38for network devices in the electronic message information display system10. The layered protocol stack38is described with respect to Internet Protocol (IP) suites comprising in general from lowest-to-highest, a link42, network44, transport48and application56layers. However, more or fewer layers could also be used, and different layer designations could also be used for the layers in the protocol stack38(e.g., layering based on the Open Systems Interconnection (OSI) model including from lowest-to-highest, a physical, data-link, network, transport, session, presentation and application layer.).

The network devices12,14,16,20,22,24,26,31,98-104are connected to the communication network18with Network Interface Card (NIC) cards including device drivers40in a link layer42for the actual hardware connecting the network devices12,14,16,20,22,24,26,31,98-104to the cloud communications network18. For example, the NIC device drivers40may include a serial port device driver, a digital subscriber line (DSL) device driver, an Ethernet device driver, a wireless device driver, a wired device driver, etc. The device driver interface with the actual hardware being used to connect the network devices to the cloud communications network18. The NIC cards have a medium access control (MAC) address that is unique to each NIC and unique across the whole cloud network18. The Medium Access Control (MAC) protocol is used to provide a data link layer of an Ethernet LAN system and for other network systems.

Above the link layer42is a network layer44(also called the Internet Layer for Internet Protocol (IP) suites). The network layer44includes, but is not limited to, an IP layer46.

IP46is an addressing protocol designed to route traffic within a network or between networks. However, more, fewer or other protocols can also be used in the network layer44, and the present invention is not limited to IP46. For more information on IP46see IETF RFC-791, incorporated herein by reference.

Above network layer44is a transport layer48. The transport layer48includes, but is not limited to, an optional Internet Group Management Protocol (IGMP) layer50, a Internet Control Message Protocol (ICMP) layer52, a Transmission Control Protocol (TCP) layer52and a User Datagram Protocol (UDP) layer54. However, more, fewer or other protocols could also be used in the transport layer48.

Optional IGMP layer50, hereinafter IGMP50, is responsible for multicasting. For more information on IGMP50see RFC-1112, incorporated herein by reference. ICMP layer52, hereinafter ICMP52is used for IP46control. The main functions of ICMP52include error reporting, reachability testing (e.g., pinging, etc.), route-change notification, performance, subnet addressing and other maintenance. For more information on ICMP52see RFC-792, incorporated herein by reference. Both IGMP50and ICMP52are not required in the protocol stack38. ICMP52can be used alone without optional IGMP layer50.

TCP layer54, hereinafter TCP54, provides a connection-oriented, end-to-end reliable protocol designed to fit into a layered hierarchy of protocols which support multi-network applications. TCP54provides for reliable inter-process communication between pairs of processes in network devices attached to distinct but interconnected networks. For more information on TCP54see RFC-793, incorporated herein by reference.

UDP layer56, hereinafter UDP56, provides a connectionless mode of communications with datagrams in an interconnected set of computer networks. UDP56provides a transaction-oriented datagram protocol, where delivery and duplicate packet protection are not guaranteed. For more information on UDP56see RFC-768, incorporated herein by reference. Both TCP54and UDP56are not required in protocol stack38. Either TCP54or UDP56can be used without the other.

Above transport layer48is an application layer57where application programs58(e.g.,30,30a,30b,30c,30d,30e,30f, etc.) to carry out desired functionality for a network device reside. For example, the application programs58for the client network devices12,14,16,27,31,33,98-104may include web-browsers or other application programs, application program30, while application programs for the server network devices20,22,24,26may include other application programs (e.g.,30a,30b,30c,30d,30e,30f, etc.).

In one embodiment, application program30includes an automated differential medical diagnosis assessment display system message application30on the target network devices12,14,16,31,33,106-112, and/or a medical diagnosis assessment display system message application30a, an Artificial Intelligence (AI) application30b, Big Data application30c, Security application30dand/or other applications30e,30f, executing on the server network devices20,22,24,26. However, the present invention is not limited to such an embodiment and more, fewer and/or other types applications can be used to practice the invention.

However, the protocol stack38is not limited to the protocol layers illustrated and more, fewer or other layers and protocols can also be used in protocol stack38. In addition, other protocols from the Internet Protocol suites (e.g., Simple Mail Transfer Protocol, (SMTP), Hyper Text Transfer Protocol (HTTP), File Transfer Protocol (FTP), Dynamic Host Configuration Protocol (DHCP), DNS, etc.), Short Message Peer-to-Peer (SMPP), and/or other protocols from other protocol suites may also be used in protocol stack38.

In addition, markup languages such as HyperText Markup Language (HTML), Extensible Markup Language (XML) and others are used.

HyperText Markup Language (HTML) is a markup language for creating web pages and other information that can be displayed in a web browser.

HTML is written in the form of HTML elements consisting of tags enclosed in angle brackets within the web page content. HTML tags most commonly come in pairs although some tags represent empty elements and so are unpaired. The first tag in a pair is the start tag, and the second tag is the end tag (they are also called opening tags and closing tags). In between these tags web designers can add text, further tags, comments and other types of text-based content.

The purpose of a web browser is to read HTML documents and compose them into visible or audible web pages. The browser does not display the HTML tags, but uses the tags to interpret the content of the page.

HTML elements form the building blocks of all websites. HTML allows images and objects to be embedded and can be used to create interactive forms. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It can embed scripts written in languages such as JavaScript which affect the behavior of HTML web pages.

Extensible Markup Language (XML) is another markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. It is defined in the XML 1.0 Specification produced by the W3C, the contents of which are incorporated by reference and several other related specifications, all free open standards.

XML a textual data format with strong support via Unicode for the languages of the world. Although the design of XML focuses on documents, it is widely used for the representation of arbitrary data structures, for example in web services. The oldest schema language for XML is the Document Type Definition (DTD). DTDs within XML documents define entities, which are arbitrary fragments of text and/or markup tags that the XML processor inserts in the DTD itself and in the XML document wherever they are referenced, like character escapes.

The Short Message Peer-to-Peer (SMPP) protocol in the telecommunications industry is an open, industry standard protocol designed to provide a flexible data communication interface for the transfer of short message data between External Short Messaging Entities, Routing Entities (ESME) and Short Message Service Center (SMSC).

Preferred embodiments of the present invention include network devices and wired and wireless interfaces that are compliant with all or part of standards proposed by the Institute of Electrical and Electronic Engineers (IEEE), International Telecommunications Union-Telecommunication Standardization Sector (ITU), European Telecommunications Standards Institute (ETSI), Internet Engineering Task Force (IETF), U.S. National Institute of Security Technology (NIST), American National Standard Institute (ANSI), Wireless Application Protocol (WAP) Forum, Bluetooth Forum, or the ADSL Forum.

Wireless Interfaces

In one embodiment of the present invention, the wireless interfaces on network devices12,14,16,20,22,24,26,31,98-104include but are not limited to, IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.15.4 (ZigBee), “Wireless Fidelity” (Wi-Fi), “Worldwide Interoperability for Microwave Access” (WiMAX), ETSI High Performance Radio Metropolitan Area Network (HIPERMAN) or “RF Home” wireless interfaces. In another embodiment of the present invention, the wireless sensor device may include an integral or separate Bluetooth and/or infra data association (IrDA) module for wireless BLUETOOTH or wireless infrared communications. However, the present invention is not limited to such an embodiment and other 802.11xx and other types of wireless interfaces can also be used.

802.11b is a short-range wireless network standard. The IEEE 802.11b standard defines wireless interfaces that provide up to 11 Mbps wireless data transmission to and from wireless devices over short ranges. 802.11a is an extension of the 802.11b and can deliver speeds up to 54 Mbps. 802.11g deliver speeds on par with 802.11a. However, other 802.11XX interfaces can also be used and the present invention is not limited to the 802.11 protocols defined. The IEEE 802.11a, 802.11b and 802.11g standards are incorporated herein by reference.

Wi-Fi is a type of 802.11xx interface, whether 802.11b, 802.11a, dual-band, etc. Wi-Fi devices include an RF interfaces such as 2.4 GHz for 802.11b or 802.11g and 5 GHz for 802.11a.

802.15.4 (Zigbee) is low data rate network standard used for mesh network devices such as sensors, interactive toys, smart badges, remote controls, and home automation. The 802.15.4 standard provides data rates of 250 kbps, 40 kbps, and 20 kbps., two addressing modes; 16-bit short and 64-bit IEEE addressing, support for critical latency devices, such as joysticks, Carrier Sense Multiple Access/Collision Avoidance, (CSMA-CA) channel access, automatic network establishment by a coordinator, a full handshake protocol for transfer reliability, power management to ensure low power consumption for multi-month to multi-year battery usage and up to 16 channels in the 2.4 GHz Industrial, Scientific and Medical (ISM) band (Worldwide), 10 channels in the 915 MHz (US) and one channel in the 868 MHz band (Europe). The IEEE 802.15.4-2003 standard is incorporated herein by reference.

WiMAX is an industry trade organization formed by leading communications component and equipment companies to promote and certify compatibility and interoperability of broadband wireless access equipment that conforms to the IEEE 802.16XX and ETSI HIPERMAN. HIPERMAN is the European standard for metropolitan area networks (MAN).

The IEEE The 802.16a and 802.16g standards are wireless MAN technology standard that provides a wireless alternative to cable, DSL and T1/E1 for last mile broadband access. It is also used as complimentary technology to connect IEEE 802.11XX hot spots to the Internet.

The IEEE 802.16a standard for 2-11 GHz is a wireless MAN technology that provides broadband wireless connectivity to fixed, portable and nomadic devices. It provides up to 50-kilometers of service area range, allows users to get broadband connectivity without needing direct line of sight with the base station, and provides total data rates of up to 280 Mbps per base station, which is enough bandwidth to simultaneously support hundreds of businesses with T1/E1-type connectivity and thousands of homes with DSL-type connectivity with a single base station. The IEEE 802.16g provides up to 100 Mbps.

The IEEE 802.16e standard is an extension to the approved IEEE 802.16/16a/16g standard. The purpose of 802.16e is to add limited mobility to the current standard which is designed for fixed operation.

The ESTI HIPERMAN standard is an interoperable broadband fixed wireless access standard for systems operating at radio frequencies between 2 GHz and 11 GHz.

The IEEE 802.16a, 802.16e and 802.16g standards are incorporated herein by reference. WiMAX can be used to provide a WLP.

In one embodiment, the plural server network devices20,22,24,26include a connection to plural network interface cards (NICs) in a backplane connected to a communications bus. The NIC cards provide gigabit/second (1×109bits/second) or greater communications speed of electronic information. This allows “scaling out” for fast electronic content retrieval. The NICs are connected to the plural server network devices20,22,24,26and the cloud communications network18. However, the present invention is not limited to the NICs described and other types of NICs in other configurations and connections with and/or without buses can also be used to practice the invention.

In one embodiment, of the invention, the wireless interfaces also include wireless personal area network (WPAN) interfaces. As is known in the art, a WPAN is a personal area network for interconnecting devices centered around an individual person's devices in which the connections are wireless. A WPAN interconnects all the ordinary computing and communicating devices that a person has on their desk (e.g. computer, etc.) or carry with them (e.g., PDA, mobile phone, smart phone, table computer two-way pager, etc.)

A key concept in WPAN technology is known as “plugging in.” In the ideal scenario, when any two WPAN-equipped devices come into close proximity (within several meters and/or feet of each other) or within a few miles and/or kilometers of a central server (not illustrated), they can communicate via wireless communications as if connected by a cable. WPAN devices can also lock out other devices selectively, preventing needless interference or unauthorized access to secure information. Zigbee is one wireless protocol used on WPAN networks such as cloud communications network18or non-cloud communications network18′.

The one or more target network devices12,14,16,20,22,24,26,31,98-104and one or more server network devices20,22,24,26communicate with each other and other network devices with near field communications (NFC) and/or machine-to-machine (M2M) communications.

“Near field communication (NFC)” is a set of standards for smartphones and similar network devices to establish radio communication with each other by touching them together or bringing them into close proximity, usually no more than a few centimeters. Present applications include contactless transactions, data exchange, and simplified setup of more complex communications such as Wi-Fi. Communication is also possible between an NFC device and an unpowered NFC chip, called a “tag” including radio frequency identifier (RFID) tags99and/or sensor.

NFC standards cover communications protocols and data exchange formats, and are based on existing radio-frequency identification (RFID) standards including ISO/IEC 14443 and FeliCa. These standards include ISO/IEC 1809 and those defined by the NFC Forum, all of which are incorporated by reference.

An “RFID tag” is an object that can be applied to or incorporated into a product, animal, or person for the purpose of identification and/or tracking using RF signals.

An “RFID sensor” is a device that measures a physical quantity and converts it into an RF signal which can be read by an observer or by an instrument (e.g., target network devices12,14,16,20,22,24,26,31,98-104, server network devices20,22,24,26, etc.)

“Machine to machine (M2M)” refers to technologies that allow both wireless and wired systems to communicate with other devices of the same ability. M2M uses a device to capture an event (such as option purchase, etc.), which is relayed through a network (wireless, wired cloud, etc.) to an application (software program), that translates the captured event into meaningful information. Such communication was originally accomplished by having a remote network of machines relay information back to a central hub for analysis, which would then be rerouted into a system like a personal computer.

However, modern M2M communication has expanded beyond a one-to-one connection and changed into a system of networks that transmits data many-to-one and many-to-many to plural different types of devices and appliances. The expansion of IP networks across the world has made it far easier for M2M communication to take place and has lessened the amount of power and time necessary for information to be communicated between machines.

However, the present invention is not limited to such wireless interfaces and wireless networks and more, fewer and/or other wireless interfaces can be used to practice the invention.

Wired Interfaces

In I one embodiment of the present invention, the wired interfaces include wired interfaces and corresponding networking protocols for wired connections to the Public Switched Telephone Network (PSTN) and/or a cable television network (CATV) and/or satellite television networks (SATV) and/or three-dimensional television (3DTV), including HDTV that connect the network devices12,14,16,20,22,24,26,31,33,98-104via one or more twisted pairs of copper wires, digital subscriber lines (e.g. DSL, ADSL, VDSL, etc.) coaxial cable, fiber optic cable, other connection media or other connection interfaces. The PSTN is any public switched telephone network provided by AT&T, GTE, SPRINT, MCI, SBC, VERIZON and others. The CATV is any cable television network provided by the COMCAST, TIME WARNER, etc. However, the present invention is not limited to such wired interfaces and more, fewer and/or other wired interfaces can be used to practice the invention.

Television Services

In one embodiment, the cloud applications30,30a,30b,30c,30d,30e,30fprovide cloud SaaS64services and/or non-cloud application services from television services over the cloud communications network18or application services over the non-cloud communications network18′. The television services include digital television services, including, but not limited to, cable television, satellite television, high-definition television, three-dimensional, televisions and other types of network devices.

However, the present invention is not limited to such television services and more, fewer and/or other television services can be used to practice the invention.

Internet Television Services

In one embodiment, the cloud applications30,30a,30b,30c,30d,30e,30fprovide cloud SaaS64services and/or non-cloud application services from Internet television services over the cloud communications network18or non-cloud communications network18′ The television services include Internet television, Web-TV, and/or Internet Protocol Television (IPtv) and/or other broadcast television services.

“Internet television” allows users to choose a program or the television show they want to watch from an archive of programs or from a channel directory. The two forms of viewing Internet television are streaming content directly to a media player or simply downloading a program to a viewer's set-top box, game console, computer, or other network device.

“Web-TV” delivers digital content via broadband and mobile networks. The digital content is streamed to a viewer's set-top box, game console, computer, or other network device.

“Internet Protocol television (IPtv)” is a system through which Internet television services are delivered using the architecture and networking methods of the Internet Protocol Suite over a packet-switched network infrastructure, e.g., the Internet and broadband Internet access networks, instead of being delivered through traditional radio frequency broadcast, satellite signal, and cable television formats.

However, the present invention is not limited to such Internet Television services and more, fewer and/or other Internet Television services can be used to practice the invention.

General Search Engine Services

In one embodiment, the cloud applications30,30a,30b,30c,30d,30e,30fprovide cloud SaaS64services and/or non-cloud application services from general search engine services. A search engine is designed to search for information on a cloud communications network18or non-cloud communications network18′ such as the Internet including World Wide Web servers, HTTP, FTP servers etc. The search results are generally presented in a list of electronic results. The information may consist of web pages, images, electronic information, multimedia information, and other types of files. Some search engines also mine data available in databases or open directories. Unlike web directories, which are maintained by human editors, search engines typically operate algorithmically and/or are a mixture of algorithmic and human input.

In one embodiment, the cloud applications30,30a,30b,30c,30d,30e,30fprovide cloud SaaS64services and/or non-cloud application services from general search engine services. In another embodiment, the cloud applications30,30a,30b,30c,30d,30e,30fprovide general search engine services by interacting with one or more other public search engines (e.g., GOOGLE, BING, YAHOO, etc.) and/or private search engine services.

In another embodiment, the cloud applications30,30a,30b,30c,30d,30e,30fprovide cloud SaaS64services and/or non-cloud application services from specialized search engine services, such as vertical search engine services by interacting with one or more other public vertical search engines, and/or private search engine services.

However, the present invention is not limited to such general and/or vertical search engine services and more, fewer and/or other general search engine services can be used to practice the invention.

Social Networking Services

In one embodiment, the cloud applications30,30a,30b,30c,30d,30e,30fprovide cloud SaaS64services and/or non-cloud application services from one more social networking services including to/from one or more social networking web-sites (e.g., FACEBOOK, YOUTUBE, TWITTER, INSTAGRAM, etc.). The social networking web-sites also include, but are not limited to, social couponing sites, dating web-sites, blogs, RSS feeds, and other types of information web-sites in which messages can be left or posted for a variety of social activities.

However, the present invention is not limited to the social networking services described and other public and private social networking services can also be used to practice the invention.

Security and Encryption

Network devices12,14,16,20,22,24,26,31,33,98-104with wired and/or wireless interfaces of the present invention include one or more of the security and encryptions techniques via Security application30e, discussed herein for secure communications on the cloud communications network18or non-cloud communications network18′.

Secure connections23on used the on the communications network18,18′ for communications to and/or from network devices12,14,16,20,22,24,26,31,33,98-104with wired and/or wireless interfaces, and/or secure storage in databases20′,22′,24′,26′ and/or secure storage in cloud databases and cloud storage objects82, to comply with Health Insurance Portability and Accountability Act (HIPAA) rules and protect the privacy of patent information sent over the communications network18,18′.

Health Insurance Portability and Accountability Act (HIPAA) is a U.S. federal law passed in 1996 that sets a national standard to protect medical records and other personal health information. The rule defines “protected health information” as health information that: (1) Identifies an individual patient, and (2) is maintained or exchanged electronically and/or in hard copy. If the i medical records and other personal health information has any components that could be used to identify a person, it is protected by HIPAA. The protection would stay with the information as long as the information is in the hands of a covered entity (e.g., a medical facility, doctors office, etc.) and/or a business associate (e.g., insurance company, billing company, etc.). The protections apply to individually identifiable information in any form, electronic or non-electronic. The paper progeny of electronic information is covered (i.e., the information would not lose its protections simply because it is printed out of a computer), and oral communications are also covered.

Application programs58(FIG.2) include security and/or encryption application programs30eintegral to and/or separate from the applications30,30a,30b,30c,30d. Security and/or encryption programs and/or applications30emay also exist in hardware components on the network devices (12,14,16,20,22,24,26,31,98-104) described herein and/or exist in a combination of hardware, software and/or firmware.

Wireless Encryption Protocol (WEP) (also called “Wired Equivalent Privacy) is a security protocol for WiLANs defined in the IEEE 802.11b standard. WEP is cryptographic privacy algorithm, based on the Rivest Cipher 4 (RC4) encryption engine, used to provide confidentiality for 802.11b wireless data.

RC4 is cipher designed by RSA Data Security, Inc. of Bedford, Massachusetts, which can accept encryption keys of arbitrary length, and is essentially a pseudo random number generator with an output of the generator being XORed with a data stream to produce encrypted data.

One problem with WEP is that it is used at the two lowest layers of the OSI model, the physical layer and the data link layer, therefore, it does not offer end-to-end security. One another problem with WEP is that its encryption keys are static rather than dynamic. To update WEP encryption keys, an individual has to manually update a WEP key. WEP also typically uses 40-bit static keys for encryption and thus provides “weak encryption,” making a WEP device a target of hackers.

The IEEE 802.11 Working Group has a security upgrade for the 802.11 standard called “802.11i.” This supplemental draft standard is intended to improve WiLAN security. It describes the encrypted transmission of data between systems 802.11X WiLANs. It also defines new encryption key protocols including the Temporal Key Integrity Protocol (TKIP). The IEEE 802.11i draft standard, version 4, completed Jun. 6, 2003, is incorporated herein by reference.

The 802.11i standard is based on 802.1x port-based authentication for user and device authentication. The 802.11i standard includes two main developments: Wi-Fi Protected Access (WPA) and Robust Security Network (RSN).

WPA uses the same RC4 underlying encryption algorithm as WEP. However, WPA uses TKIP to improve security of keys used with WEP. WPA keys are derived and rotated more often than WEP keys and thus provide additional security. WPA also adds a message-integrity-check function to prevent packet forgeries.

RSN uses dynamic negotiation of authentication and selectable encryption algorithms between wireless access points and wireless devices. The authentication schemes proposed in the draft standard include Extensible Authentication Protocol (EAP). One proposed encryption algorithm is an Advanced Encryption Standard (AES) encryption algorithm.

Dynamic negotiation of authentication and encryption algorithms lets RSN evolve with the state of the art in security, adding algorithms to address new threats and continuing to provide the security necessary to protect information that WiLANs carry.

The NIST developed a new encryption standard, the Advanced Encryption Standard (AES) to keep government information secure. AES is intended to be a stronger, more efficient successor to Triple Data Encryption Standard (3DES).

DES is a popular symmetric-key encryption method developed in 1975 and standardized by ANSI in 1981 as ANSI X.3.92, the contents of which are incorporated herein by reference. As is known in the art, 3DES is the encrypt-decrypt-encrypt (EDE) mode of the DES cipher algorithm. 3DES is defined in the ANSI standard, ANSI X9.52-1998, the contents of which are incorporated herein by reference. DES modes of operation are used in conjunction with the NIST Federal Information Processing Standard (FIPS) for data encryption (FIPS 46-3, October 1999), the contents of which are incorporated herein by reference.

The NIST approved a FIPS for the AES, FIPS-197. This standard specified “Rijndael” encryption as a FIPS-approved symmetric encryption algorithm that may be used by U.S. Government organizations (and others) to protect sensitive information. The NIST FIPS-197 standard (AES FIPS PUB 197, November 2001) is incorporated herein by reference.

The NIST approved a FIPS for U.S. Federal Government requirements for information technology products for sensitive but unclassified (SBU) communications. The NIST FIPS Security Requirements for Cryptographic Modules (FIPS PUB 140-2, May 2001) is incorporated herein by reference.

RSA is a public key encryption system which can be used both for encrypting messages and making digital signatures. The letters RSA stand for the names of the inventors: Rivest, Shamir and Adleman. For more information on RSA, see U.S. Pat. No. 4,405,829, now expired and incorporated herein by reference.

“Hashing” is the transformation of a string of characters into a usually shorter fixed-length value or key that represents the original string. Hashing is used to index and retrieve items in a database because it is faster to find the item using the shorter hashed key than to find it using the original value. It is also used in many encryption algorithms.

Secure Hash Algorithm (SHA), is used for computing a secure condensed representation of a data message or a data file. When a message of any length<264bits is input, the SHA-1 produces a 160-bit output called a “message digest.” The message digest can then be input to other security techniques such as encryption, a Digital Signature Algorithm (DSA) and others which generates or verifies a security mechanism for the message. SHA-512 outputs a 512-bit message digest. The Secure Hash Standard, FIPS PUB 180-1, Apr. 17, 1995, is incorporated herein by reference.

Message Digest-5 (MD-5) takes as input a message of arbitrary length and produces as output a 128-bit “message digest” of the input. The MD5 algorithm is intended for digital signature applications, where a large file must be “compressed” in a secure manner before being encrypted with a private (secret) key under a public-key cryptosystem such as RSA. The IETF RFC-1321, entitled “The MD5 Message-Digest Algorithm” is incorporated here by reference.

Providing a way to check the integrity of information transmitted over or stored in an unreliable medium such as a wireless network is a prime necessity in the world of open computing and communications. Mechanisms that provide such integrity check based on a secret key are called “message authentication codes” (MAC). Typically, message authentication codes are used between two parties that share a secret key in order to validate information transmitted between these parties.

Keyed Hashing for Message Authentication Codes (HMAC), is a mechanism for message authentication using cryptographic hash functions. HMAC is used with any iterative cryptographic hash function, e.g., MD5, SHA-1, SHA-512, etc. in combination with a secret shared key. The cryptographic strength of HMAC depends on the properties of the underlying hash function. The IETF RFC-2101, entitled “HMAC: Keyed-Hashing for Message Authentication” is incorporated here by reference.

An Electronic Code Book (ECB) is a mode of operation for a “block cipher,” with the characteristic that each possible block of plaintext has a defined corresponding cipher text value and vice versa. In other words, the same plaintext value will always result in the same cipher text value. Electronic Code Book is used when a volume of plaintext is separated into several blocks of data, each of which is then encrypted independently of other blocks. The Electronic Code Book has the ability to support a separate encryption key for each block type.

Diffie and Hellman (DH) describe several different group methods for two parties to agree upon a shared secret in such a way that the secret will be unavailable to eavesdroppers. This secret is then converted into various types of cryptographic keys. A large number of the variants of the DH method exist including ANSI X9.42. The IETF RFC-2631, entitled “Diffie-Hellman Key Agreement Method” is incorporated here by reference.

The HyperText Transport Protocol (HTTP) Secure (HTTPs), is a standard for encrypted communications on the World Wide Web. HTTPs is actually just HTTP over a Secure Sockets Layer (SSL). For more information on HTTP, see IETF RFC-2616 incorporated herein by reference.

The SSL protocol is a protocol layer which may be placed between a reliable connection-oriented network layer protocol (e.g. TCP/IP) and the application protocol layer (e.g. HTTP). SSL provides for secure communication between a source and destination by allowing mutual authentication, the use of digital signatures for integrity, and encryption for privacy.

The SSL protocol is designed to support a range of choices for specific security methods used for cryptography, message digests, and digital signatures. The security methods are negotiated between the source and destination at the start of establishing a protocol session. The SSL 2.0 protocol specification, by Kipp E. B. Hickman, 1995 is incorporated herein by reference. More information on SSL is available at the domain name See “netscape.com/eng/security/SSL_2.html.”

Transport Layer Security (TLS) provides communications privacy over the Internet. The protocol allows client/server applications to communicate over a transport layer (e.g., TCP) in a way that is designed to prevent eavesdropping, tampering, or message forgery. For more information on TLS see IETF RFC-2246, incorporated herein by reference.

In one embodiment, the security functionality includes Cisco Compatible EXtensions (CCX). CCX includes security specifications for makers of 802.11xx wireless LAN chips for ensuring compliance with Cisco's proprietary wireless security LAN protocols. As is known in the art, Cisco Systems, Inc. of San Jose, California is supplier of networking hardware and software, including router and security products.

However, the present invention is not limited to such security and encryption methods described herein and more, fewer and/or other types of security and encryption methods can be used to practice the invention. The security and encryption methods described herein can also be used in various combinations and/or in different layers of the protocol stack38with each other.

Cloud Computing Networks

FIG.4is a block diagram60illustrating an exemplary cloud computing network18. The cloud computing network18is also referred to as a “cloud communications network”18. However, the present invention is not limited to this cloud computing model and other cloud computing models can also be used to practice the invention. The exemplary cloud communications network includes both wired and/or wireless components of public and private networks.

In one embodiment, the cloud computing network18includes a cloud communications network18comprising plural different cloud component networks72,74,76,78. “Cloud computing” is a model for enabling, on-demand network access to a shared pool of configurable computing resources (e.g., public and private networks, servers, storage, applications, and services) that are shared, rapidly provisioned and released with minimal management effort or service provider interaction.

This exemplary cloud computing model for electronic information retrieval promotes availability for shared resources and comprises: (1) cloud computing essential characteristics; (2) cloud computing service models; and (3) cloud computing deployment models. However, the present invention is not limited to this cloud computing model and other cloud computing models can also be used to practice the invention.

Exemplary cloud computing essential characteristics appear in Table 1. However, the present invention is not limited to these essential characteristics and more, fewer or other characteristics can also be used to practice the invention.

TABLE 11. On-demand automated differential medical diagnosis services. Automaticdifferential medical diagnosis services can unilaterally provision computingcapabilities, such as server time and network storage, as needed automaticallywithout requiring human interaction with each network server on the cloudcommunications network 18, 18′.2. Broadband network access. Automatic automated differential medical diagnosisservices capabilities are available over plural broadband communicationsnetworks and accessed through standard mechanisms that promote use byheterogeneous thin or thick client platforms (e.g., mobile phones, smart phones14, tablet computers 12, laptops, PDAs, etc.). The broadband network accessincludes high speed network access such as 5G wireless and/or wired andbroadband and/or ultra-broad band (e.g., WiMAX, etc.) network access.3. Resource pooling. Automatic automated differential medical diagnosis servicesresources are pooled to serve multiple requesters using a multi-tenant model,with different physical and virtual resources dynamically assigned andreassigned according to demand. There is location independence in that arequester of services has no control and/or knowledge over the exact locationof the provided by the automated differential medical diagnosis serviceresources but may be able to specify location at a higher level of abstraction(e.g., country, state, or data center). Examples of pooled resources includestorage, processing, memory, network bandwidth, virtual server networkdevice and virtual target network devices.4. Rapid elasticity. Capabilities can be rapidly and elastically provisioned, in somecases automatically, to quickly scale out and rapidly released to quickly scalefor automated differential medical diagnosis service collaboration. Forautomated differential medical diagnosis services, multi-media collaborationconverters, the automatic automated differential medical diagnosis servicescollaboration and analytic conversion capabilities available for provisioningappear to be unlimited and can be used in any quantity at any time.5. Measured Services. Cloud computing systems automatically control and optimizeresource use by leveraging a metering capability at some level of abstractionappropriate to the type of automated differential medical diagnosis (e.g.,storage, processing, bandwidth, custom electronic content retrievalapplications, etc.). Electronic automated differential medical diagnosiscollaboration conversion usage is monitored, controlled, and reportedproviding transparency for both the automated differential medical diagnosisservices provider and automated differential medical diagnosis requester of theutilized electronic content storage retrieval service.

Exemplary cloud computing service models illustrated inFIG.4appear in Table 2. However, the present invention is not limited to these service models and more, fewer or other service models can also be used to practice the invention.

TABLE 21. Cloud Computing Software Applications 62 for automated differential medicaldiagnosis services. (CCSA, SaaS 64). The capability to use the provider'sapplications 30, 30a, 30b, 30c, 30d, 30e, 30f running on a cloud infrastructure66. The cloud computing applications 62, are accessible from the servernetwork device 20 from various client devices 12, 14, 16 through a thin clientinterface such as a web browser, etc. The user does not manage or control theunderlying cloud infrastructure 66 including network, servers, operatingsystems, storage, or even individual application 30, 30a, 30b, 30c, 30d, 30e,30f capabilities, with the possible exception of limited user-specificapplication configuration settings.2. Cloud Computing Infrastructure 66 for automated differential medical diagnosis.services (CCI 68). The capability provided to the user is to provisionprocessing, storage and retrieval, networks 18, 72, 74, 76, 78 and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems and applications30, 30a, 30b, 30c, 30d, 30e, 30f. The user does not manage or control theunderlying cloud infrastructure 66 but has control over operating systems,storage, deployed applications, and possibly limited control of selectnetworking components (e.g., host firewalls, etc.).3. Cloud Computing Platform 70 for automated differential medical diagnosisservices. (CCP 71). The capability provided to the user to deploy onto thecloud infrastructure 66 created or acquired applications created usingprogramming languages and tools supported servers 20, 22, 24, 26, etc. Theuser not manage or control the underlying cloud infrastructure 66 includingnetwork, servers, operating systems, or storage, but has control over thedeployed applications 30a, 30b, 30c, 30d, 30e, 30f and possibly applicationhosting environment configurations.

Exemplary cloud computing deployment models appear in Table 3. However, the present invention is not limited to these deployment models and more, fewer or other deployment models can also be used to practice the invention.

TABLE 31. Private cloud network 72. The cloud network infrastructure is operated solely forautomated differential medical diagnosis. It may be managed by the electroniccontent retrieval or a third party and may exist on premise or off premise.2. Community cloud network 74. The cloud network infrastructure is shared byseveral different organizations and supports a specific electronic contentstorage and retrieval community that has shared concerns (e.g., mission,security requirements, policy, compliance considerations, etc.). It may bemanaged by the different organizations or a third party and may exist onpremise or off premise.3. Public cloud network 76. The cloud network infrastructure such as the Internet,PSTN, SATV, CATV, Internet TV, etc. is made available to the general publicor a large industry group and is owned by one or more organizations sellingcloud services.4. Hybrid cloud network 78. The cloud network infrastructure 66 is a composition oftwo and/or more cloud networks 18 (e.g., private 72, community 74, and/orpublic 76, etc.) and/or other types of public and/or private networks (e.g.,intranets, etc.) that remain unique entities but are bound together bystandardized or proprietary technology that enables data and applicationportability (e.g., cloud bursting for load-balancing between clouds, etc.)

Cloud software64for electronic content retrieval takes full advantage of the cloud paradigm by being service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability for electronic content retrieval. However, cloud software services64can include various states.

Cloud storage of desired electronic content on a cloud computing network includes agility, scalability, elasticity and multi-tenancy. Although a storage foundation may be comprised of block storage or file storage such as that exists on conventional networks, cloud storage is typically exposed to requesters of desired electronic content as cloud objects.

In one exemplary embodiment, the cloud application30,30b,30c,30d,30e,30f, offers cloud services for automated differential medical diagnosis. The application30,30a,30b,30c,30d,30e,30foffers the cloud computing Infrastructure66,68as a Service62(IaaS), including a cloud software infrastructure service62, the cloud Platform70,71as a Service62(PaaS) including a cloud software platform service62and/or offers Specific cloud software services as a Service64(SaaS) including a specific cloud software service64for automated differential medical diagnosis. The IaaS, PaaS and SaaS include one or more of cloud services62comprising networking, storage, server network device, virtualization, operating system, middleware, run-time, data and/or application services, or plural combinations thereof, on the cloud communications network18.

FIG.5is a block diagram80illustrating an exemplary cloud storage object82. One or more server network devices (e.g.,20,22,24,26, etc.) store portions13,13a,15of the electronic message content13,13a,15(e.g., SMS, MMS, RCS, etc.) as cloud storage objects82(FIG.5) as is described herein.

The cloud storage object82includes an envelope portion84, with a header portion86, and a body portion88. However, the present invention is not limited to such a cloud storage object82and other cloud storage objects and other cloud storage objects with more, fewer or other portions can also be used to practice the invention.

The envelope portion84uses unique namespace Uniform Resource Identifiers (URIs) and/or Uniform Resource Names (URNs), and/or Uniform Resource Locators (URLs) unique across the cloud communications network18to uniquely specify, location and version information and encoding rules used by the cloud storage object82across the whole cloud communications network18. For more information, see IETF RFC-3305, Uniform Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs), the contents of which are incorporated by reference.

The envelope portion84of the cloud storage object82is followed by a header portion86. The header portion86includes extended information about the cloud storage objects such as authorization and/or transaction information, etc.

The body portion88includes methods90(i.e., a sequence of instructions, etc.) for using embedded application-specific data in data elements92. The body portion88typically includes only one portion of plural portions of application-specific data92and independent data94so the cloud storage object82can provide distributed, redundant fault tolerant, security and privacy features described herein.

Cloud storage objects82have proven experimentally to be a highly scalable, available and reliable layer of abstraction that also minimizes the limitations of common file systems. Cloud storage objects82also provide low latency and low storage and transmission costs.

Cloud storage objects82are comprised of many distributed resources, but function as a single storage object, are highly fault tolerant through redundancy and provide distribution of desired electronic content across public communication networks76, and one or more private networks72, community networks74and hybrid networks78of the cloud communications network18. Cloud storage objects82are also highly durable because of creation of copies of portions of desired electronic content across such networks72,74,76,78of the cloud communications network18. Cloud storage objects82includes one or more portions of desired electronic content and can be stored on any of the72,74,76,78networks of the cloud communications network18. Cloud storage objects82are transparent to a requester of desired electronic content and are managed by cloud applications30,30a,30b,30c,30d,30e,30f.

In one embodiment, cloud storage objects82are configurable arbitrary objects with a size up to hundreds of terabytes, each accompanied by with a few kilobytes of metadata. Cloud objects are organized into and identified by a unique identifier unique across the whole cloud communications network18. However, the present invention is not limited to the cloud storage objects described, and more fewer and other types of cloud storage objects can be used to practice the invention.

Cloud storage objects82present a single unified namespace or object-space and manages desired electronic content by user or administrator-defined policies storage and retrieval policies. Cloud storage objects includes Representational state transfer (REST), Simple Object Access Protocol (SOAP), Lightweight Directory Access Protocol (LDAP) and/or Application Programming Interface (API) objects and/or other types of cloud storage objects. However, the present invention is not limited to the cloud storage objects described, and more fewer and other types of cloud storage objects can be used to practice the invention.

REST is a protocol specification that characterizes and constrains macro-interactions storage objects of the four components of a cloud communications network18, namely origin servers, gateways, proxies and clients, without imposing limitations on the individual participants.

SOAP is a protocol specification for exchanging structured information in the implementation of cloud services with storage objects. SOAP has at least three major characteristics: (1) Extensibility (including security/encryption, routing, etc.); (2) Neutrality (SOAP can be used over any transport protocol such as HTTP, SMTP or even TCP, etc.), and (3) Independence (SOAP allows for almost any programming model to be used, etc.)

LDAP is a software protocol for enabling storage and retrieval of electronic content and other resources such as files and devices on the cloud communications network18. LDAP is a “lightweight” version of Directory Access Protocol (DAP), which is part of X.500, a standard for directory services in a network. LDAP may be used with X.509 security and other security methods for secure storage and retrieval. X.509 is public key digital certificate standard developed as part of the X.500 directory specification. X.509 is used for secure management and distribution of digitally signed certificates across networks.

An API is a particular set of rules and specifications that software programs can follow to communicate with each other. It serves as an interface between different software programs and facilitates their interaction and provides access to automatic automated differential medical diagnosis in a cloud or non-cloud environment. In one embodiment, the API for automated differential medical diagnosis is available to network devices12,14,16,20,22,24,26,31,98-104and networks18,18′. However, the present invention is not limited to such an embodiment and other embodiments can be used to practice the invention.

Wearable Devices

Wearable technology” and/or “wearable devices” are clothing and accessories incorporating computer and advanced electronic technologies. Wearable network devices provide several advantages including, but not limited to: (1) Quicker access to notifications. Important and/or summary notifications are sent to alert a user to view the whole message. (2) Heads-up information. Digital eye wear allows users to display relevant information like directions without having to constantly glance down; (3) Always-on Searches. Wearable devices provide always-on, hands-free searches; and (4) Recorded data and feedback. Wearable devices take telemetric data recordings and providing useful feedback for users for exercise, health, fitness, etc. activities.

FIG.6is a block diagram with 96 illustrating wearable devices. The wearable devices include one or more processors and include, but are not limited to, wearable digital glasses98, clothing100, jewelry102(e.g., smart rings, smart earrings, etc.) and/or watches104. However, the present invention is not limited to such embodiments and more, fewer and other types of wearable devices can also be used to practice the invention.

In one specific embodiment, the application30,30a,30b,30c,30d,30e,30finteracts with wearable devices98-104automatic automated differential medical diagnosis the methods described herein. However, the present invention is not limited this embodiment and other embodiments can also be used to practice the invention.

Artificial Intelligence (AI) and Big Data

“Artificial intelligence” (AI), also known as machine intelligence (MI), is intelligence demonstrated by machines, in contrast to the natural intelligence (NI) displayed by humans and other animals. AI research is defined as the study of “intelligent agents.” Intelligent agents are any software application or hardware device that perceives its environment and takes actions that maximize its chance of successfully achieving its goals. Colloquially, the term “artificial intelligence” is applied when a machine mimics “cognitive” functions that humans associate with human brains, such as learning, problem solving and comparing large number of data points.

In one embodiment, the present invention uses one or more AI methods including, but are not limited to, AI knowledge-based methods30bfor automated differential medical diagnosis. However, the present invention is not limited to such an embodiment and more, fewer and/or other AI methods can be used to practice the invention.

In one embodiment, the medical diagnosis application30aincludes an integral AI application30band a Big Data set application30c. In another embodiment, the medical diagnosis application30aincludes separate AI application30band a Big Data set application30c. However, the present invention is not limited to such an embodiment and more, fewer and/or other combinations can be used to practice the invention.

In one embodiment, SaaS64includes an AI application30bwith the AI methods described herein. In another embodiment, the AI application30bis a standalone application. However, the present invention is not limited to such an embodiment, and the AI application30bcan be provided in other than the SaaS64. However, the present invention is not limited to such an embodiment and more, fewer and/or other combinations can be used to practice the invention.

“Big Data” refers to the use of predictive analytic methods that extract value from data, and to a particular size of data set. The quantities of data used are very large, at least 100,000 data points and more typically 500,000 to one Million+ data points. Analysis of Big Data sets are used to find new correlations and to spot trends. In one embodiment, the AI application30bincludes a Big Data set application30cwith the Big Data set described herein. In one embodiment, SaaS64includes and Big Data application30dwith the Big Data described herein. However, the present invention is not limited to such an embodiment and more, fewer and/or other combinations can be used to practice the invention.

In one embodiment, the AI methods described herein collect data information to create and store (e.g., in cloud storage object82, etc.) a Big Data that is used to analyze trends find new correlations and to spot trends. However, the present invention is not limited to such an embodiment and the AI methods described herein can be used without Big Data sets.

Short Message Service (SMS) Messaging

Short Message Service (SMS) is an electronic text messaging service component of phone, Web, or mobile communication systems. It uses standardized communications protocols to allow fixed line or mobile phone devices to exchange short text messages.

SMS messages were defined in 1985 as part of the Global System for Mobile Communications (GSM) series of standards as a means of sending messages of up to 160 characters to and from GSM mobile handsets. Though most SMS messages are mobile-to-mobile text messages, support for the service has expanded to include other mobile technologies as well as satellite and landline networks.

The SMS Internet Engineering Task Force (IETF) Request for Comments (RFC) 5724, ISSN: 2070-1721, 2010, is incorporated herein by reference.

Direct and Instant Messages

A “direct message” (DM) is a private form of communication between social media users that is only visible to the sender and recipient(s). INSTAGRAM, TWITTER, FACEBOOK and other platforms, allow for direct messages between their users, with varying restrictions by platform.

An “instant message” (IM) is a type of online chat allowing real-time text transmission over the Internet or another computer network. Messages are typically transmitted between two or more parties, when each user inputs text and triggers a transmission to the recipient, who are all connected on a common network

Multimedia Messaging Service (MMS)

Multimedia Messaging Service (MMS) is a standard way to send messages that include multimedia content to and from a mobile phone over a cellular network. Users and providers may refer to such a message as a PXT, a picture message, and/or a multimedia message.

The MMS Internet Engineering Task Force (IETF) Request for Comments (RFC) 4355 and 4356, are incorporated herein by reference.

Rich Communication Suite (RCS)

Rich Communications Suite/Rich Communications System (RCS) is a communication protocol between mobile telephone carriers, between phones and carriers, and between individual devices aiming at replacing SMS messages with a message system that is richer, provides phonebook polling (e.g., for service discovery, etc.), and can transmit in-call multimedia. It is also marketed under the names of Advanced Messaging, Advanced Communications, Chat, joyn, Message+ and SMS+. RCS is also a communication protocol available for device-to-device (D2D) exchanges without using a telecommunications carrier for devices that are in close physical proximity (e.g., between two IoT devices, smart phones, smart phone and electronic tablet, etc.)

One advantage RCS Messaging has over SMS is that RCS enables users to send rich, verified messages including photos, videos and audio messages, group messages, read receipts, indicators to show other users are typing a message, carousel messages, suggested chips, chat bots, barcodes, location integration, calendar integration, dialer integration, and other RCS messaging features. RCS messaging includes person-to-person (P2P), application-to-person (A2P), application-to-application (A2A), application-to-device (A2D) and/or device-to-device (D2D) messaging.

The RCS Interworking Guidelines Version 14.0, 13 Oct. 2017, GSM Association, Rich Communication Suite RCS API Detailed Requirements, version 3.0, Oct. 19, 2017, Rich Communication Suite 8.0 Advanced Communications Services and Client Specification Version 9.0, 16 May 2018, RCS Universal Profile Service Definition Document Version 2.2, 16 May 2018, and Rich Communication Suite Endorsement of OMA CPM 2.2 Conversation Functions Version 9.0, 16 Oct. 2019, are all incorporated herein by reference.

The Rich Communication Suite-Enhanced (RCS-e) includes methods of providing first stage interoperability among Mobile Network Operators (MNOs). RCS-e is a later version of RCS which enables mobile phone end users to use instant messaging (IM), live video sharing and file transfer across any device on any MNO.

The RCS functionality of the present invention includes, but is not limited to, one and two-way, rich, verified, multimedia messages including photos, videos and audio messages, group messages, read receipts, indicators to show other users are typing a message, predefined quick-reply suggestions, rich cards, carousels, action buttons, maps, click-to-call, calendar integration, geo-location, etc. The RCS functionality also includes RCS emulators and/or thin RCS applications that provide full and/or selected features of available RCS functionality.

Complaints of a Specific Patient at a Medical Facility

One or more patient complaints are collected for a patient19at a medical facility21by collecting patient history (HX) information with medical doctors, nursing staff, nurse practitioners, medical assistants, and/or other medical staff. The one or more patient complaints are used by a medical diagnosis application30ausing one or more automated diagnosis methods to determine a final diagnosis13′, one or more differential diagnoses13dand/or one or more critical differential diagnoses and a final treatment plan for the specific patient19at the medical facility21. However, the present invention is not limited to such an embodiment and other embodiments and other HX information can be used to practice the invention.

The HX information typically includes, but is not limited to appropriate history of present illness (“HPI”), review of systems (“ROS”), past medical family social history (“PMSFH”), review of system (“ROS”) information allergies, medications, vital signs, etc. This information may or may not be modified by or for the medical facility that collected the patient encounter information.

Table 4 illustrates exemplary HX information collected. However, the present invention is not limited to this HX information, more, less and other types of HX information can also be collected from the patient encounter information.

TABLE 4HX InformationChief Complaint (CC):Description of one or more problems (e.g., sore throat,chest pains, trouble breathing, fever, etc.)History of Present Illness (HPI):Location; quality; severity; duration; timing; context;modifying factors; associated signs and symptoms.Past medical, family, social history (PFMSH):Medical History - the patient's past experiences withillnesses, operations, injuries and treatments.Family History - a review of medical events in the patient'sfamily, including diseases which may be hereditary or placethe patient at risk.Social History - an age appropriate review of past andcurrent activities.Review of Systems (ROS):Constitutional; eyes, ears, nose, mouth, throat; cardio-vascular;respiratory; GI; GU; muscular; neurological; psychological;immune; etc.

Another set of patient encounter information physical examination information (“PX”) obtained from the patient encounter. Table 5 illustrates where body areas and organ systems from which PX information is collected. However, the present invention is not limited to this PX information, more, less and other types of PX information can also be collected from the patient encounter information.

Table 6 illustrates possible levels of the physical exam types of PX information determined. This example uses one specific set of guidelines commonly referred to and published by the Centers for Medicare & Medicaid Services (“CMS”) as Documentation Guidelines for Evaluation and Management Services, but can utilize other methods or guidelines as determined by the type of exam or by changes in prescribed or allowable guidelines. In addition, the PX information is exemplary only, and the present invention is not limited to such PX information.

TABLE 6PX TypesPFOne to five elements identified (e.g., one tofive body areas or organs)EXPFAt least six elements identified (e.g., up to atotal of six organ systems)DETAt least twelve items identified from 2 (ormore) PX areasCOMPTwo or more elements identified in nine ormore organ systems.

The PX types include, but are not limited to: a problem focused (“PF”) exam that includes 1-5 specific exam elements identified; an expanded problem focused exam (“EXPF”) that includes at least 6 specific exam elements; Detailed exam (“DET”) that includes at least 12 elements in two or more areas/systems, and a comprehensive exam (“COMP”) that includes documentation of at least two elements from each of nine areas/systems.

Another set of patient encounter information used is complexity of medical decision-making information (“CX”) obtained from the patient encounter. The CX information includes a number of diagnosis (“DX”) or treatment options and risk (“RISK”) information. However, the present invention is not limited to this embodiment and other types of extracted complexity information can be used to practice the invention.

Table 7 illustrates exemplary CX information. However, the present invention is not limited to this embodiment and other embodiments can also be used to practice the invention.

TABLE 7CX TypesDXRISKstraight forward (“SF”) number ofstraight forward risk (“SF”),diagnosis, <= one.includes a self-limited orminor problem.low number of diagnoseslow risk (“LOW”), includes(“LOW”), minimal.two or more minor problems,one stable chronic illness or anacute uncomplicated illness orinjury.moderate number of diagnosesmoderate (“MOD”) includes(“MOD”), multiple.one or more chronic illnesseswith mild exacerbation,progression, or side effecttreatment, two or more stablechronic illnesses, anundiagnosed new problemwith uncertain prognosis or anacute illness with systemicsymptoms or an acutecomplicated injury.high number of possiblehigh risk (“HIGH”), includesdiagnoses (“HIGH”), extensive.one or more chronic illnesseswith severe exacerbation,progression or side effects oftreatment, or acute or chronicillnesses or injuries that maypose a threat to life or bodilyfunction or an abrupt changein neurological status.

The DX information includes, but is not limited to: straight forward (“SF”) diagnosis; a low number of diagnoses (“LOW”); a moderate number of diagnoses (“MOD”); and a high number of possible diagnoses (“HIGH”). This DX scoring can be performed using an objective scoring system. A unique aspect of this invention includes (but is not limited to) presentation of these choices in check-box form with each of a maximum number of choices in each category represented by a check-box. Scoring of the DX section can then be performed by adding a point value of each box to obtain the total score in the DX section. Although, scoring of the DX section is not limited to this method, if it is used the following scores correlate with the various levels of DX: (≤1) minimal; (2) limited; (3) multiple; or (4) extensive.

The RISK information includes: minimal or straight forward (“SF”) risk in which the medical problem is self-limited or a minor problem (e.g., cold, insect bite, etc.); low risk (“LOW”) in which the medical problem includes two or more minor problems, one stable chronic illness (e.g., well controlled hypertension or non-insulin dependent diabetes, cataract, etc.) or an acute uncomplicated illness or injury (allergic reaction, simple sprain); moderate risk (“MOD”) in which the medical problem includes one or more chronic illnesses with mild exacerbation, progression, or side effect treatment, two or more stable chronic illnesses, an undiagnosed new problem with uncertain prognosis (e.g., lump in breast or prostrate, etc.) an acute illness with systemic symptoms (e.g., pneumonitis, colitis, etc.) or an acute complicated injury (e.g., head injury with brief loss of consciousness): and high risk (“HIGH”) in which the medical problem includes one or more chronic illnesses with severe exacerbation, progression or side effects of treatment, or acute or chronic illnesses or injuries that may pose a threat to life or bodily function (e.g., multiple trauma, acute MI, pulmonary embolus, severe respiratory distress, progressive severe rheumatoid arthritis, psychiatric illness with potential threat to self or others, acute renal failure, etc.) or an abrupt change in neurological status (e.g., seizure, TIA, weakness or sensory loss, etc.).

Automated Differential Medical Diagnosis

Determining a final diagnosis and one or more differential diagnoses from a patient encounter is complex and presents many risks, even for an experienced medical doctor. There is a significant risk of complications, morbidity, mortality, and/or comorbidity associated with the patient's complaints due to misdiagnoses of medical problems associated with the patient complaints. A patient risk diagnosis is based on the patient's current health status, past health history, and other risk factors that may increase the patient's likelihood of experiencing a health problem. Patient complications are defined as unsuspected medical conditions that arise during the treatment of a patient. Patient morbidity is defined as a patient having a disease or a symptom of a disease. Comorbidity occurs when a person has more than one disease or condition at the same time and are often chronic or long-term conditions considered pre-existing conditions.

The present invention significantly reduces a complexity and risk at plural different levels associated with determining a final diagnosis and one or more differential diagnoses from a from a patient encounter.

FIGS.7A,7B,7C and7Dare a flow diagram illustrating a Method106for providing automated differential medical diagnosis.

InFIG.7Aat Step108, displaying from a medical diagnosis application on a server network device with one or more processors, a list of plural patient complaints from a database for one or more patient complaints received at a medical facility, on a network device with one or more processors via a communications network on a secure connection. At Step110, receiving a first message on the medical diagnosis application on the server network device including the one or more patient complaints for a specific patient at the medical facility from the network device with via the communications network on the secure connection. At Step112, displaying from the medical diagnosis application on the server network device, a list of a possible diagnoses related to the one or more patient complaints for the specific patient on the network device via the communication network on the secure connection, the list of possible diagnoses related to the one or more patient complaints including: (1) a check box to include differential diagnoses for the one or more patient complaints including a differential name and differential diagnosis description, (2) a diagnosis code (Dx), (3) a delete diagnosis icon to remove a diagnosis that does not apply to the specific patient from the list, and (4) an add diagnosis link including a link to a list of additional related diagnoses that could apply to the specific patient including one or more electronic links to add additional diagnoses to the list of plural patient complaints displayed for the one or more patient complaints received in the first message. The list of possible differential diagnoses reducing a first complexity level and a first risk level associated with determining a primary diagnosis and one or more differential diagnoses related to the one or more patient complaints for the specific patient.

InFIG.7Bat Step114, receiving a second message on the medical diagnosis application on server network device including one or more selection inputs with diagnosis information selected for the one or more patient complaints for the specific patient at the medical facility from the network device with via the communications network on the secure connection. At Step116, displaying from the medical diagnosis application on server network device, diagnosis information and differential diagnosis information related to the one or more patient complaints for the specific patient on the network device via the communication network on the secure connection; the diagnosis and differential diagnosis information including: (1) a determined diagnosis section including a graphical checkbox to add the determined diagnosis as a final diagnosis for the one or more patient complaints for the specific patient at the medical facility, (2) a differential diagnosis section including a graphical checkbox to add one or more differential diagnoses for the specific patient at the medical facility, (3) a diagnosis name including a diagnosis description and an International Classification of Diseases (ICD) diagnostic code, (4) a list of evaluation methods used to include and rule out one or more differential diagnoses and select a final diagnosis, (5) a diagnosis (Dx) morbidity threat including plural of morbidity threat levels for the one or more differential diagnoses, and (6) a graphical search electronic link to search for additional diagnoses to add to the likely differential diagnosis list.

InFIG.7Cat Step118, receiving a third message on the medical diagnosis application on server network device including one or more selection inputs with differential diagnosis information selected for the one or more patient complaints for the specific patient at the medical facility from the network device with via the communications network on the secure connection. At Step120, determining on the medical diagnosis application on server network device with one or more diagnosis methods with information from the first message, second message and third message: (1) final diagnosis information including a final diagnosis for the one or more patient complaints for the specific patient at the medical facility, and (2) differential diagnosis information including one or more likely differential diagnoses and one or more critical differential diagnoses for the specific patient at the medical facility. At Step122, creating on the medical diagnosis application on server network device with the one or more diagnosis methods with information from the first message, second message and third message: (1) an electronic visit summary for the specific patient at the medical facility supplied to the specific patent at the medical facility including the determined final diagnosis information and differential diagnosis information, (2) a new medical record for the specific patient at the medical facility including the determined final diagnosis information and differential diagnosis information, and (3) a treatment plan for the specific patent at the medical facility including the determined final diagnosis information and differential diagnosis information. The created electronic visit summary, the created new medical record and the created treatment plan, reducing a second complexity level and a second risk level associated with determining a final diagnosis, one or more differential diagnoses created for the one or more patient complaints for the specific patient at the medical facility.

InFIG.7Dat Step124, storing from the medical diagnosis application on server network device the determined final diagnosis information and differential diagnosis information, the created electronic visit summary, the new medical record and the created treatment plan for the specific patent at the medical facility in the database. At Step126, displaying from the medical diagnosis application on server network device, diagnosis summary information related to the one on more patient complaints for the specific patient at medical facility on the network device via the communication network on the secure connection. The diagnosis summary information including: final diagnosis information including: (1) the final diagnosis for the one or more patient complaints for the specific patient at the medical facility, (2) the differential diagnosis information including one or more likely differential diagnoses and critical differential diagnoses for the specific patient at the medical facility. (3) the created electronic visit summary for the specific patient at the medical facility supplied to the specific patent at the medical facility, (4) the created new medical record for the specific patient at the medical facility supplied to the specific patent at the medical facility, and (5) the created treatment plan for the specific patient. At step128, sending a fourth message from the medical diagnosis application on server network device to the server network device via the communication network on the secure connection. The fourth message including the created electronic visit summary, the created new medical record and the created treatment plan for the specific patient at the medical facility.

Method106is illustrated with an exemplary embodiment. However, the present invention is not limited to such an embodiment and other embodiments may be used to practice the invention.

In such an exemplary embodiment inFIG.7Aat Step108, displaying from a medical diagnosis application30aon a server network device20,22,24,26with one or more processors, a list of plural patient complaints from a database20′,22′,24′,26′ for one or more patient complaints13received at a medical facility21, on a network device12,14,16,20,22,24,26,31,33,98-104with one or more processors via a communications network18,18′ on a secure connection23.

In one embodiment, the medical facility21, includes, but is not limited to, an emergency room at a hospital, an urgent care facility, a medical clinic, a doctor's office, a telemedicine connection over the communications network18,18′ and/or other type of medical facilities. However, the present invention is not limited to such an embodiment and more, fewer and/other types of medical facilities21may be used to practice the invention.

In one embodiment, the plural patient complaints include, but are not limited to, coughs, fevers, pains in various parts of the body, shortness of breath, dizziness, broken bones, sprains, cuts, puncture wounds, comorbidity (e.g., pre-existing conditions, such as diabetes, heart disease, cancer, etc.). However, the present invention is not limited to such an embodiment and more, fewer and/other types of patient complaints, may be used to practice the invention.

In one embodiment, the server network device20,22,24,26is replaced with a target network device12,14,16,31,33,98-104including a medical diagnosis application30and/or30a. However, the present invention is not limited to such an embodiment and other embodiments can be used to practice the invention.

In one embodiment, network device includes target network devices12,14,16,31,33,98-104and/or another server network device20,22,24,26. However, the present invention is not limited to such an embodiment and other embodiments can be used to practice the invention.

In one embodiment, medical diagnosis application30acomprises a cloud communications network18SaaS64on a cloud server network device. However, the present invention is not limited to such an embodiment and other embodiments can be used to practice the invention.

At Step110, receiving a first message on the medical diagnosis application30aon server network device20,22,24,26including the one or more patient complaints13for the specific patient19at the medical facility21from the network device12,14,16,20,22,24,26,31,33,98-104with via the communications network18,18′ on the secure connection23.

In one embodiment, the one or more patient complaints13for the specific patients include the HX and other information described in Tables 4-7 above. However, the present invention is not limited to such an embodiment and other embodiments can be used to practice the invention.

FIG.8a block diagram132illustrating an exemplary chief complaint display screen134.

FIG.8illustrates (1) a patient complaint136(e.g., cough, with fever, dizziness, may be abnormal blood sugar level, etc.), plural check boxes138to include a differential diagnosis for the patient complaint136with a list for pre-selected likely differential diagnoses140for the patient complaint136including a diagnosis description142, (2) a diagnosis code (Dx)144, (3) a delete diagnosis icon146to remove a diagnosis that does not apply to the specific patient19from the list, and (4) an add diagnosis link148including a link to a list of additional related diagnoses that could apply to the specific patient19including one or more electronic links to add additional diagnoses to the list of plural patient complaints136displayed for the one or more patient complaints13received in the first message. However, the present invention is not limited to such an embodiment, and other embodiments, with more, fewer and other display screen items134can be used to practice the invention.

Returning toFIG.7Aat Step110, displaying from the medical diagnosis application30aon the server network device20,22,24,26, a list of a possible diagnoses related to the one or more patient complaints13for the specific patient19on the network device12,14,16,20,22,24,26,31,33,98-104via the communication network18,18′ on the secure connection23, the list of possible diagnoses136related to the one or more patient complaints13including plural check boxes to select relevant differential diagnosis, including: (1) a check box138to include differential diagnoses for the one or more patient complaints140(e.g., e.g., cough, with fever, dizziness, may be abnormal blood sugar level, etc.) including a differential diagnosis name142and differential diagnosis description144, (2) a diagnosis code (Dx)144, (3) a delete diagnosis icon146to remove a diagnosis that does not apply to the specific patient from the list, and (4) an add diagnosis link148including a link to a list of additional related diagnoses that could apply to the specific patient19including one or more electronic links to add additional differential diagnoses to the list of a plural patient complaints136displayed for the one or more patient complaints13received in the first message. The list of possible differential diagnoses140reducing a first complexity level and a first risk level associated with determining a primary diagnosis and one or more differential diagnoses related to the one or more patient complaints13for the specific patient19.

On average, medical researchers estimate that 11% of patient complaints13result in a misdiagnosis. Medical diagnosis application30ahelps reduce this 11% risk. Since the medical diagnosis application30aon the server network device20,22,24,26provides a list a list of a possible diagnoses136and related possible differential diagnoses140related to the one or more patient complaints13for the specific patient19, a first complexity level and a first risk level is significantly reduced because a medical doctor17trying to determine a diagnosis for the specific patient19is presented with a comprehensive, integrated interface with the medical diagnosis application30athat helps prevent the medical doctor19from missing and/or not considering important and relevant possible diagnoses and related possible differential diagnoses related to the one or more patient complaints13for the specific patient19.

InFIG.7Bat Step114, receiving a second message on the medical diagnosis application30aon server network device20,22,24,26including one or more selection inputs with diagnosis information selected for the one or more patient complaints13for the specific patient19at the medical facility21from the network device12,14,16,20,22,24,26,31,33,98-104with via the communications network18,18′ on the secure connection23.

FIG.9is a block diagram150illustrating an exemplary differential diagnosis display screen152.

FIG.9illustrates diagnosis154and differential diagnosis information156is displayed including: (1) a determined diagnosis section158(e.g., fever, abnormal blood sugar, etc.) including a graphical checkbox160to add the determined diagnosis as a final diagnosis13′ for the one or more patient complaints13for the specific patient19at the medical facility21, (2) a differential diagnosis section162including a graphical checkbox164to add one or more differential diagnoses for the specific patient19at the medical facility21. (3) a diagnosis name166including a diagnosis description168and an International Classification of Diseases (ICD) diagnostic code170, (4) a list of evaluation methods172used to include and rule out one or more differential diagnoses162and select a final diagnosis. (5) a diagnosis (Dx) morbidity threat174including plural morbidity threat levels for the diagnosis, and (6) a graphical search electronic link176to search for additional diagnoses to add to the likely differential diagnosis list.

Returning toFIG.7Bat Step116, displaying from the medical diagnosis application30aon server network device20,22,24,26, diagnosis information154and differential diagnosis information156related to the one or more patient complaints13for the specific patient19on the network device12,14,16,20,22,24,26,31,33,98-104via the communication network18,18′ on the secure connection23; the diagnosis and differential diagnosis information including: (1) a determined diagnosis section158(e.g., fever, abnormal blood sugar, etc.) including a graphical checkbox160to add the determined diagnosis as a final diagnosis for the one or more patient complaints13for the specific patient19at the medical facility21, (2) a differential diagnosis section162including a graphical checkbox164to add one or more differential diagnoses for the specific patient19at the medical facility21, (3) a diagnosis name166including a diagnosis description168and an International Classification of Diseases (ICD) diagnostic code170(e.g., 834.9, etc.) (4) a list of evaluation methods172used to include and rule out one or more differential diagnoses162and select a final diagnosis, (5) a diagnosis (Dx) morbidity threat174including plural morbidity threat levels for the differential diagnosis (e.g., low for viral infection unspecified166), and (6) a graphical search electronic link176to search for additional diagnoses to add to the likely differential diagnosis list.

In one embodiment, the International Classification of Diseases (ICD) diagnostic codes, include, but are not limited to, The International Classification of Diseases (ICD), Tenth Revision (ICD-10) and/or ICD Revision 11 (ICD-11), both of which are incorporated herein by reference. ICD-10 and ICD-11 ire designed to promote international comparability in the collection, processing, classification, and presentation of mortality statistics. This includes providing a format for reporting causes of death on the death certificate. In such and embodiment, the ICD-10 and/or ICD-11 information is stored in the databases20′,22′,24′,26′ and/or in one or more cloud storage objects82in one or more cloud databases and/or obtained directly when needed from web-sites on the communications network18,18′. In another embodiment, the ICD-10 and/or ICD-11 information is stored remotely on other network devices and is accessible to the medical diagnosis application30aon server network device20,22,24,26via the communications network18,18′. However, the present invention is not limited to using ICD-10 and other embodiments with other classification of diseases can be used to practice the invention.

In one embodiment, the list of evaluation methods172used to include and rule out one or more differential diagnoses162and select a final diagnosis13′ includes, but is not limited to using one or more of, and/or a combination of: a prior and/or current medical history of the patient19, a prior and/or current physical exam of the patent19, prior and/or current diagnostic testing (e.g., blood, urine, etc.) conducted on the patient19, and/or prior and/or current imaging of the patient19(e.g., Magnetic resonance imaging (MRI), Computed tomography scans (CAT), Positron emission tomography (PET), x-rays, ultra-sound, etc.). However, the present invention is not limited to such embodiments and more, fewer and/or other evaluation methods can be used to practice the invention.

Magnetic resonance imaging (MRI) is a medical imaging technique used in radiology to form pictures of the anatomy and the physiological processes inside the body. MRI scanners use strong magnetic fields, magnetic field gradients, and radio waves to generate images of the organs in the body. A computed tomography (CAT) scan is a medical imaging technique used to obtain detailed internal images of the body. Positron emission tomography (PET) is a functional imaging technique that uses radioactive substances known as radiotracers to visualize and measure changes in metabolic processes, and in other physiological activities including blood flow, regional chemical composition, and absorption. However, the present invention is not limited to such embodiments and more, fewer and/or other imaging methods can be used to practice the invention.

In one embodiment, morbidity is defined as a patient having a disease or a symptom of a disease. The morbidity threat level, includes, but is not limited to, an external cause of morbidity, that is, how an injury or health condition happened and/or its root cause (e.g., new condition, old chronic condition, etc.). Morbidity threat levels also include: (1) an intent: unintentional or accidental; or intentional, like suicide or assault or accident; and (2) a place where an event occurred; and/or (3) an activity of the patient at the time of the event. The actual morbidity threat level used include, but is not limited to, a minimum, low, moderate and high, morbidity threat level, as defined by the ICD. However, the present invention is not limited to such embodiments and more, fewer and/or other morbidity threat levels, with other levels and definitions can be used to practice the invention.

InFIG.7Cat Step118, receiving a third message on the medical diagnosis application30aon server network device20,22,24,26including one or more selection inputs with differential diagnosis information selected for the one or more patient complaints13for the specific patient19at the medical facility21from the network device12,14,16,20,22,24,26,31,33,98-104with via the communications network on the secure connection23.

FIG.10is a block diagram178illustrating an exemplary visit summary screen180.

FIG.10illustrates final diagnosis information13′ including a final diagnosis182(e.g., COVID 19, etc.) for the one or more patient complaints13(e.g., fever, etc.) for the specific patient19at the medical facility21, and (2) differential diagnosis information13dincluding one or more likely differential diagnoses184(acute sinusitis, acute tonsillitis, etc.) and one or more critical differential diagnoses186(e.g., bacterial meningitis, etc.) for the specific patient19at the medical facility21. However, the present invention is not limited to such an embodiment and more, fewer and/or other fields can be used on the visit summary screen to practice the invention.

Returning toFIG.7Cat Step120, determining on the medical diagnosis application30aon server network device20,22,24,26, with one or more diagnosis methods with information from the first message, second message and third message; (1) final diagnosis information13′ including a final diagnosis182for the one or more patient complaints13for the specific patient19at the medical facility21, and (2) differential diagnosis information13dincluding one or more likely differential diagnoses184and one or more critical differential diagnoses186for the specific patient19at the medical facility21. The created electronic visit summary25, the created new medical record27and the created treatment plan29reducing a second complexity level and a second risk level associated with determining a final diagnosis13′, one or more differential diagnoses13drelated to the final diagnosis for the one or more patient complaints13for the specific patient19at the medical facility21.

In one embodiment, the final diagnosis information13′ and the differential diagnosis information13dare determined using one or more diagnosis methods include using the HX, CX, DX, PX and/or RISK information described in Table 4-7 above. However, the present invention is not limited to such an embodiment and other embodiments without using this information may be used to practice the invention.

In one embodiment, the final diagnosis information13′ and the differential diagnosis information13dare determined using the one or more diagnosis methods without AI. In such an embodiment, the one or more diagnostic methods compare the one or more patient complaints13for the specific patient19at the medical facility21to plural diagnostic items and combinations thereof, including but not limited to, a using a current version of the ICD, a prior and/or current medical history of the patient19, prior and/or current physical exam of the patent19, prior and/or current diagnostic testing (e.g., blood, urine, etc.) conducted on the patient19, and/or prior and/or current imaging of the patient19(e.g., Magnetic resonance imaging (MRI), Computed tomography scans (CAT), Positron emission tomography (PET), x-rays, ultra-sound, etc.), and/or one or more prior and/or current differential diagnoses for the patient19. However, the present invention is not limited to such an embodiment and other embodiments including other diagnosis methods can be used to practice the invention.

In another embodiment, the final diagnosis information13′ and the differential diagnosis information13dare determined using one or more diagnosis methods including, but not limited to, one or more AI methods30bincluding a Big Data set30c. In such an embodiment, the one or more AI methods30bcompares the one or more patient complaints13for the specific patient19at the medical facility21to plural diagnostic items and combinations thereof, including but not limited to, prior and current versions of the ICD, electronic versions of medical text books, electronic versions of medical disease references, online medical reference sources (e.g., Centers for Disease Control and Prevention (CDC), MEDSCAPE, MEDLINE, PUBMED, etc.) a prior and/or current medical history of the patient19and medical histories of similar patients (e.g., similar age, race, pre-existing conditions, medications, surgeries, etc.) in the Big Data set30c, a prior and/or current physical exam of the patent19, and/or physical exams of similar patients in the Big Data set30c, prior and/or current diagnostic testing (e.g., blood, urine, etc.) conducted on the patient19and diagnostic testing for similar patients in the Big Data set30cand/or prior and/or current imaging of the patient19(e.g., Magnetic resonance imaging (MRI), Computed tomography scans (CAT), Positron emission tomography (PET), x-rays, ultra-sound, etc.) and imaging for similar patients in the Big Data set30c, one or more prior and/or current diagnoses and/or differential diagnoses for the patient19and prior current diagnoses and/or differential diagnoses for similar patients in the Big Data set30c. However, the present invention is not limited to such an embodiment and other AI methods30b, with more, fewer and/or other method items and/or with and/or without use of a Big Data set30c, to determine the final diagnosis information13′ and the differential diagnosis information13d. However, the present invention is not limited to such an embodiment and other embodiments including other AI diagnosis methods can be used to practice the invention.

In one embodiment, the medical diagnosis application30aon server network device20,22,24,26periodically (e.g., one a month, quarter, year, etc.) updates137(FIG.8) the one or more diagnosis methods and the database20′,22′,24′,26′ to include new and/or updated disease diagnoses and/or differential diagnoses information. However, the present invention is not limited to such an embodiment and other embodiments including other AI diagnosis methods can be used to practice the invention.

Returning toFIG.7Cat Step122, creating on the medical diagnosis application30aon server network device20,22,24,24with the one or more diagnosis methods with information from the first message, second message and third message (1) an electronic visit summary25(FIG.1) for the specific patient19at the medical facility21supplied to the specific patent19at the medical facility21including the determined final diagnosis information13′ and differential diagnosis information13d, (2) a new medical record27for the specific patient19at the medical facility21including the determined final diagnosis information13′ and differential diagnosis information13d, and (3) a treatment plan29for the specific patent at the medical facility including the determined final diagnosis information and differential diagnosis information. The created electronic visit summary25, the created new medical record27and the created treatment plan29reducing a second complexity level and a second risk level associated with determining a final diagnosis13′, one or more differential diagnoses13drelated to the final diagnosis13′ created for the one or more patient complaints13for the specific patient19at the medical facility21.

The medical diagnosis application30aon the server network device20,22,24,26creates the final diagnosis information13′ including a final diagnosis182for the one or more patient complaints13for the specific patient19at the medical facility21, differential diagnosis information13dincluding one or more likely differential diagnoses184and one or more critical differential diagnoses186, the created visit summary25, the created medical record27and the created treatment plan29for the specific patient19at the medical facility21with the one or more diagnosis methods.

Therefore, a second complexity level and a second risk level are significantly reduced because a medical doctor17trying to determine a final diagnosis13′ and one or more differential diagnoses13dfor the specific patient19is presented with a comprehensive, integrated interface medical diagnosis application30athat helps prevent the medical doctor19from missing and/or not considering important and relevant possible diagnoses and related possible differential diagnoses related to the one or more patient complaints13for the specific patient19and/or not considering and/or missing important and relevant possible actions for the specific patient19, the created visit summary25, the created medical record27and the created treatment plan29for the specific patient19at the medical facility21.

InFIG.7Dat Step124, storing from the medical diagnosis application30aon server network device20,22,24,26the determined final diagnosis information13′ and final differential diagnosis information13d, the created electronic visit summary25, the new medical record27and treatment plan29for the specific patent19at the medical facility21in the database20′,22′,24′,26′.

In one embodiment, the determined final diagnosis information13′ and final differential diagnosis information13d, electronic visit summary25, the new medical record27and treatment plan29for the specific patent19at the medical facility21are stored in one or more cloud storage object82in a cloud database20′,22′,24′,26′ on a cloud communications network18. However, the present invention is not limited to such an embodiment and other embodiments can be used to practice the invention with and/or without a cloud communications network18.

At Step126, displaying from the medical diagnosis application30aon server network device,20,22,24,24, diagnosis summary information13′ related to the one on more patient complaints13for the specific patient19at medical facility21on the network device12,14,16,20,22,24,26,31,33,98-104via the communication network18,18′ on the secure connection23. The diagnosis summary information13′ including: final diagnosis information including: (1) the final diagnosis182for the one or more patient complaints13for the specific patient19at the medical facility21, (2) the differential diagnosis information13dincluding one or more likely differential diagnoses184and critical differential diagnoses186for the specific patient19at the medical facility21, (3) the created electronic visit summary25for the specific patient19at the medical facility21supplied to the specific patent19at the medical facility21, (4) the created new medical record27for the specific patient19at the medical facility19and (5) the created treatment plan for the specific patient19supplied to the specific patent19at the medical facility21.

FIG.11is a block diagram188illustrating an exemplary patient medical record screen190.

FIG.11illustrates the created electronic visit summary25, the created new medical record27, and the created treatment plan29for the specific patient19at the medical facility21on one screen190. However, the present invention is not limited to such an embodiment and other embodiments can be used to practice the invention.

Returning toFIG.7Dat step128, sending a fourth message from the medical diagnosis application30aon server network device20,22,24,26to the server network device12,14,16,20,22,24,26,31,33,98-104via the communication network18,18′ on the secure connection23. The fourth message including the created electronic visit summary25, the created new medical record27, and the created treatment plan29for the specific patient19at the medical facility21.

In one embodiment, created electronic visit summary25, the created new medical record27, and the created treatment plan29for the specific patient19at the medical facility21are sent in one electronic document (as illustrated inFIG.11) in the fourth message. In another embodiment, the created electronic visit summary25, the created new medical record27, and the created treatment plan29for the specific patient19at the medical facility21are sent in separate documents. However, the present invention is not limited to such embodiments and other embodiments can be used to practice the invention.

In one embodiment, adding from medical diagnosis application30aon server network device an electronic signature187(FIG.10),191(FIG.11) for a medical professional (e.g., medical doctor17, etc.) who reviewed: (1) the final diagnosis182for the one or more patient complaints13for the specific patient19at the medical facility19, (2) the differential diagnosis information13dincluding one or more likely differential diagnoses184and critical differential diagnoses186for the specific patient19at the medical facility21, (3) the created electronic visit summary25for the specific patient19at the medical facility21supplied to the specific patent19at the medical facility21, (4) the created new medical record27for the specific patient19at the medical facility21supplied to the specific patent19at the medical facility21and (5) the created treatment plan29for the specific patient19. However, the present invention is not limited to such an embodiment and other embodiments with and/or without an electronic signature of a medical professional. The electronic signatures187,191identifies the medical professional and prevents tampering and/or altering of the final diagnosis information13′ and differential diagnosis information13d, the visit summary25, new medical record27and treatment plan29, after it is created.

FIG.12is a block diagram192illustrating an exemplary data flow194for the Method106ofFIG.7.

InFIG.12, the one or more patient complaints13received for the patent19at a medical facility21, are sent over the secure connection23. The one or more patient complaints13are encrypted196with one or more encryption and/or security methods described herein to transform the one or more patient complaints13in their original plaintext format into an encrypted document198to protect the patent19data based on HIPAA security and encryption requirements. The medical diagnosis application30aon server network device20,22,24,26decrypts200the encrypted document198back into the original plaintext format13. The medical doctor17uses the medical diagnosis application30aon server network device20,22,24,26to process202the one or more patient complaints13using Method106to create204,206the final diagnosis information13′, the final differential diagnosis information13d, the electronic visit summary25, the new medical record27and the treatment plan29for the specific patent19at the medical facility21.FIG.12illustrates the data flow194from the patent19to the medical doctor17using the medical diagnosis application30aon server network device20,22,24,26only. A data flow from the medical diagnosis application30aon server network device20,22,24,26back to a network device12,14,16,20,22,24,26,31,33,98-104at the medical facility21or a network device12,14,16,20,22,24,26,31,33,98-104accessible by the specific patent19(e.g., for telemedicine, etc.) would follow a similar pathway of encryption of plain text patent information25,27,29and description over the secure connection23. However, the present invention is not limited to such an embodiment and other data flows can be used to practice the invention.

FIG.13is a flow diagram illustrating a Method208for providing automated differential medical diagnosis assessment.

InFIG.13at Step210, determining on a medical diagnosis application on a server network device with one or more processors: (1) final diagnosis information including a final diagnosis for one or more patient complaints for a specific patient at a medical facility, (2) differential diagnosis information including one or more likely differential diagnoses and one or more critical differential diagnoses associated with the final diagnosis for the specific patient at the medical facility and (3) a treatment plan or the specific patient at the medical facility. At Step212, reducing plural complexities and plural risks associated with determining the final diagnosis, the one or more differential diagnoses, the one or more critical diagnosis associated with the final diagnosis and the treatment plan for the one or more patient complaints for the specific patient at the medical facility.

Method208is illustrated with an exemplary embodiment. However, the present invention is not limited to such an embodiment and other embodiments may be used to practice the invention.

In such an exemplary embodiment inFIG.13at Step210, determining on a medical diagnosis application30aon server network device20,22,24,26with one or more processors: (1) final diagnosis information13′ including a final diagnosis182for one or more patient complaints13for the specific patient19at the medical facility21, (2) differential diagnosis information13dincluding one or more likely differential diagnoses184and one or more critical differential diagnoses186associated with the final diagnosis184for the specific patient19at the medical facility21and (3) a treatment plan29for the specific patient19at the medical facility21.

At Step212, reducing plural complexities and plural risks associated with determining the final diagnosis182, one or more differential diagnoses184and one or more critical diagnoses186associated with the final diagnosis182and the treatment plan29for the one or more patient complaints13for the specific patient19at the medical facility21.

With Method208, a first and second complexity level and a first and second risk level are significantly reduced because a medical doctor17trying to determine a final diagnosis and one or more differential diagnoses for the specific patient19is presented with a comprehensive, integrated interface that helps prevent the medical doctor19from missing and/or not considering important and relevant possible diagnoses and related possible differential diagnoses related to the one or more patient complaints13for the specific patient19and/or not considering and/or missing important and relevant possible actions for the specific patient19treatment plan29.

FIG.14is a flow diagram illustrating a Method214for providing automated differential medical diagnosis assessment.

InFIG.14at Step216, determining on a medical diagnosis application on server network device differential diagnosis information including one or more likely differential diagnoses and one or more critical differential diagnoses associated including determining plural morbidity threat levels for the one or more likely differential diagnoses and the one or more critical differential diagnoses for the specific patient at the medical facility. At Step218, reducing plural complexities and plural risks associated with the determined one or more differential diagnoses and the determined one or more critical diagnoses for the specific patient at the medical facility with the determined plural morbidity threat levels for the specific patient at the medical facility.

Method214is illustrated with an exemplary embodiment. However, the present invention is not limited to such an embodiment and other embodiments may be used to practice the invention.

In such an exemplary embodiment inFIG.14at Step216, determining on a medical diagnosis application30aon server network device20,22,24,26, differential diagnosis information13dincluding one or more likely differential diagnoses184and one or more critical differential diagnoses186associated including determining plural morbidity threat levels174for the one or more likely differential diagnoses184and the one or more critical differential diagnoses186for the specific patient19at the medical facility21.

At Step218, reducing plural complexities and plural risks associated with the determined one or more differential diagnoses184and the determined one or more critical diagnoses186for the specific patient19at the medical facility21with the determined plural morbidity threat levels174for the specific patient19at the medical facility21.

With Method214, a first and second complexity level and a first and second risk level are significantly reduced because a medical doctor17trying to determine a final diagnosis and one or more differential diagnoses for the specific patient19is presented with a comprehensive, integrated interface via the medical diagnosis application30athat helps prevent the medical doctor19from missing and/or not considering important and relevant possible diagnoses and related possible differential diagnoses related to the one or more patient complaints13for the specific patient19and/or not considering and/or missing important and relevant possible actions for the specific patient19treatment plan29.

With Method214, third complexity level and a third risk level is significantly reduced because a medical doctor17trying to determine a diagnosis for the specific patient19is presented with a comprehensive, integrated interface via the medical diagnosis application30athat helps prevent the medical doctor19from missing and/or not considering important and relevant plural morbidity threat levels174for the one or more likely differential diagnoses184and the one or more critical differential diagnoses186for the specific patient19at the medical facility related to the one or more patient complaints13for the specific patient19.

All of the drawings included here do not include any actual data for any actual patents and not violate the Health Insurance Portability and Accountability Act (HIPAA) rules that protect the privacy of patent information.FIGS.8-11are included for illustrative purposes for virtual patient that is not a real person.

A method and system for automated differential medical diagnosis is presented herein. Final diagnosis information including a final diagnosis for one or more patient complaints for a specific patient at a medical facility and differential diagnosis information including one or more likely differential diagnoses and one or more critical differential diagnoses associated with the final diagnosis for the specific patient at the medical facility, a visit summary, a medical record and a treatment plan or the specific patient at the medical facility are determined. Plural different types of complexities and plural types of risks associated with determining the final diagnosis, the one or more differential diagnoses, the one or more critical diagnosis associated with the final diagnosis, the visit summary, the medical record and the treatment plan for the one or more patient complaints for the specific patient at the medical facility are reduced.

It should be understood that the architecture, programs, processes, methods and systems described herein are not related or limited to any particular type of computer or network system (hardware or software), unless indicated otherwise. Various types of specialized computer systems may be used with or perform operations in accordance with the teachings described herein.

While various elements of the preferred embodiments have been described as being implemented in software, in other embodiments hardware or firmware implementations may alternatively be used, and vice-versa.

The claims should not be read as limited to the described order or elements unless stated to that effect. In addition, use of the term “means” in any claim is intended to invoke 35 U.S.C. § 112, paragraph 6, and any claim without the word “means” is not so intended. Therefore, all embodiments that come within the scope and spirit of the following claims and equivalents thereto are claimed as the invention.

Therefore, all embodiments that come within the scope and spirit of the proceeding described and equivalents thereto are identified and claimed as the invention.