Aircraft medical management system

A method and system for providing medical assistance onboard an aircraft is provided. A number of secure wireless connections are established between an onboard device located on the aircraft and a remote device located remotely with respect to the aircraft, to enable communications between a device operator using the onboard device and a medical professional using the remote device. Information about a medical event that occurs onboard the aircraft is sent from the onboard device to the remote device using the number of secure wireless connections. A medical assessment of the medical event by the medical professional is received at the onboard device from the remote device over the number of secure wireless connections.

BACKGROUND INFORMATION

The present disclosure relates generally to providing medical care and, in particular, to providing medical care to people onboard an aircraft. Still more particularly, the present disclosure relates to a method and apparatus for evaluating and managing medical events that occur onboard an aircraft during flight.

During flight, any number of passengers, crew members, pilots, co-pilots, officers, or other persons may be onboard an aircraft. As one example, during the flight of a commercial aircraft, any number of passengers may be present onboard the aircraft, in addition to at least one pilot and at least one crew member. A possibility of a medical event occurring during the flight of an aircraft may increase with the number of people onboard the aircraft and may depend on the medical histories of these people. A medical event may include one or more people experiencing any number of symptoms.

Currently available measures for providing medical assistance to a person experiencing symptoms onboard an aircraft during flight include, for example, treating the person with a medical kit on the aircraft, turning an aircraft around and flying back to the departure point, diverting the aircraft to an alternate destination, or proceeding to the original destination depending on the distance to the original destination and the severity of the symptoms.

However, some currently available medical kits require that a trained emergency physician or other type of trained medical professional use these kits. Having a trained medical professional onboard the aircraft during flight may not always be feasible. Further, measures such as turning an aircraft around and flying back to the departure point or diverting the aircraft to an alternate destination may be expensive or problematic due to factors such as, for example, without limitation, fuel consumption. In some cases, these measures may take more time than desired to provide medical care to a person and may result in the medical condition of the person worsening.

Thus, it may be desirable to provide medical assistance onboard an aircraft, while reducing the expenses associated with managing medical emergencies onboard the aircraft. Therefore, it would be desirable to have a method and apparatus that take into account at least some of the issues related to providing flight safety and managing medical events onboard aircraft, as well as other possible issues.

SUMMARY

In one illustrative embodiment, a method for providing medical assistance onboard an aircraft is provided. A number of secure wireless connections are established between an onboard device located on the aircraft and a remote device located remotely with respect to the aircraft to enable communications between a device operator using the onboard device and a medical professional using the remote device. Information about a medical event that occurs onboard the aircraft is sent from the onboard device to the remote device using the number of secure wireless connections. A medical assessment of the medical event by the medical professional is received at the onboard device from the remote device over the number of secure wireless connections.

In another illustrative embodiment, a method for providing medical assistance onboard an aircraft during flight is provided. Physiological data is generated about a person experiencing a set of symptoms during the flight using a number of medical devices in communication with an onboard device located on the aircraft. A number of secure wireless connections are established between the onboard device and a remote device to enable communications between a device operator using the onboard device and a medical professional using the remote device during the flight. The physiological data is sent from the onboard device to the remote device during the flight. A medical assessment formulated by the medical professional using the physiological data is received at the onboard device from the remote device over the number of secure wireless connections. A number of actions are performed to medically assist the person onboard the aircraft during the flight based on the medical assessment.

In yet another illustrative embodiment, an aircraft medical management system comprises an onboard device located on an aircraft. The onboard device comprises a connection manager and an interactive interface. The connection manager establishes a number of secure wireless connections between the onboard device and a remote device to enable communications between a device operator using the onboard device and a medical professional using the remote device during flight of the aircraft. The interactive interface receives a medical assessment of a person experiencing a set of symptoms during the flight from the medical professional over the number of secure wireless connections.

DETAILED DESCRIPTION

The illustrative embodiments recognize and take into account different considerations. For example, the illustrative embodiments recognize and take into account that it may be desirable to provide live medical assistance onboard an aircraft. In particular, the illustrative embodiments recognize and take into account that it may be desirable to provide live, real-time medical assistance onboard an aircraft during flight to passengers onboard the aircraft experiencing symptoms during the flight. By providing this type of medical assistance, the period of time between the time at which a passenger experiencing symptoms onboard the aircraft is observed and the time at which medical care for the passenger is initiated may be significantly reduced.

The illustrative embodiments also recognize and take into account that it may be desirable to provide the airlines with a means of remote diagnostics with the goal of accessing the risk and stability of passengers onboard an aircraft. In particular, it may be desirable to provide the airlines with the means for making an educated decision as to whether to divert an aircraft to an alternate destination, turn the aircraft back around to the departure point, or continue on the predetermined flight route for the aircraft.

Thus, the illustrative embodiments provide an aircraft medical management system that provides an additional layer of passenger safety during flight by providing a means for providing live medical assistance onboard an aircraft during the flight. In one illustrative example, a number of secure wireless connections may be established between an onboard device located on the aircraft and a remote device located remotely with respect to the aircraft to enable communications between a device operator using the onboard device and a medical professional using the remote device. Information about a medical event that occurs onboard the aircraft may be sent from the onboard device to the remote device using the number of secure wireless connections. A medical assessment of the medical event by the medical professional may be received at the onboard device from the remote device over the number of secure wireless connections. A number of actions may be performed onboard the aircraft to manage the medical event based on the medical assessment.

As used herein, a “number of” items may include one or more items. In this manner, the number of secure wireless connections established between the onboard device and the remote device may include one or more secure wireless connections. Similarly, the number of actions performed onboard the aircraft may include one or more actions.

Referring now to the figures and, in particular, with reference toFIG. 1, an illustration of an aircraft is depicted in accordance with an illustrative embodiment. In this illustrative example, aircraft100may be an example of one type of aircraft with which aircraft medical management system101may be used. Aircraft100is a passenger aircraft in this illustrative example.

As depicted, aircraft100includes fuselage102. Passenger cabin104is located within fuselage102. Passengers106are present in passenger cabin104during flight of aircraft100. During flight, one of passengers106may begin experiencing one or more symptoms.

For example, without limitation, passenger108may experience a fever, shortness of breath, pain, or some combination thereof. Aircraft medical management system101may be used to provide medical assistance to passenger108.

As depicted, aircraft medical management system101includes onboard device110. InFIG. 1, only a portion of aircraft medical management system101is shown. In other words, aircraft medical management system101may include other components in addition to onboard device110.

Onboard device110takes the form of a computer tablet in this illustrative example. In other illustrative examples, onboard device110may take the form of a laptop, a tablet-laptop hybrid, a smartphone, a computer station onboard aircraft100, or some other type of computing system. Onboard device110is used by device operator112to provide medical assistance to passenger108. In this illustrative example, device operator112is a crew member of aircraft102who has a selected level of medical training and who has authorization to use onboard device110.

However, in other illustrative examples, device operator112may be a medical professional, such as a physician, a nurse, a physician's assistant, or some other type of medical professional. In still other illustrative examples, device operator112may be any crew member with authorization to use onboard device110, a pilot of aircraft100, a co-pilot of aircraft100, a passenger onboard aircraft100, or some other person onboard aircraft100.

Device operator112may use onboard device110to communicate with a medical professional (not shown) located on the ground. In particular, device operator112uses onboard device110to send information about passenger108to the physician. This information may include, for example, without limitation, personal data about passenger108, medical history information for passenger108, family history information for passenger108, physiological data generated for passenger108using one or more medical devices onboard aircraft100, medical permissions, medical directives, other types of information, or some combination thereof.

In some illustrative examples, device operator112may participate in a video conference session with the medical professional using onboard device110. The video conference session may include audio capabilities. In some cases, this video conference session may also be used to allow the medical professional to observe passenger108. In this manner, additional information about passenger108may be provided to the medical professional using onboard device110.

The medical professional uses the information obtained about passenger108to provide a medical assessment of the symptoms being experienced by passenger108. In one illustrative example, the medical professional communicates this medical assessment to device operator112through the video conference session. In another illustrative example, the medical professional may communicate the medical assessment to device operator112through an audio conference session that does not include video capabilities. In yet another illustrative example, the medical professional may communicate the medical assessment to device operator112by sending a report of the medical assessment to onboard device110.

In still another illustrative example, the medical professional may communicate the medical assessment to passenger108directly. For example, the medical professional may verbally report the medical assessment to passenger108through the video conference session. In some cases, the medical professional may provide medical assistance directly to passenger108through the video conference session in the form of instructions.

In some illustrative examples, device operator112may use the medical assessment of passenger108by the medical professional to assist passenger108. In particular, device operator112may perform one or more actions to assist passenger108based on the medical assessment.

With reference now toFIG. 2, an illustration of aircraft medical management system101fromFIG. 1is depicted in accordance with an illustrative embodiment. As depicted inFIG. 2, aircraft medical management system101includes onboard device110located onboard aircraft100. In this illustrative example, aircraft medical management system101also includes remote device202, airline computer system204, medical data storage infrastructure206, and conference server system208.

Remote device202may take a number of different forms. In one illustrative example, remote device202takes the form of a computer system. In other illustrative examples, remote device202may take the form of a laptop, a tablet, a tablet-laptop hybrid, a smartphone, an on-ground computer station, or some other type of computing system. Remote device202may be used by medical professional210as needed to provide medical assistance to one or more of passenger106inFIG. 1onboard aircraft100.

As one illustrative example, when device operator112inFIG. 1becomes aware of the symptoms of passenger108onboard aircraft100inFIG. 1, device operator112may use onboard device110to communicate with medical professional210, who may use remote device202to communicate with device operator112inFIG. 1.

In this illustrative example, device operator112fromFIG. 1first establishes secure wireless connection212between onboard device110and airline computer system204. Airline computer system204may be comprised of one or more computers, servers, or some combination thereof.

Secure wireless connection212may take the form of one or more wireless communications links that allow the secure exchange of data between onboard device110and airline computer system204. Airline computer system204may have any number of safeguards in place to ensure that any wireless connection established with airline computer system204is with an authorized device. For example, airline computer system204may have a security system that includes at least one of a firewall, an intrusion prevention system, anti-virus software, or some other type of protection for preventing unauthorized devices from wirelessly connecting to airline computer system204. Establishing secure wireless connection222may include being authorized by the security system of airline computer system204to do so.

As used herein, the phrase “at least one of,” when used with a list of items, means different combinations of one or more of the listed items may be used and only one of the items in the list may be needed. The item may be a particular object, thing, step in a process, or category. In these illustrative examples, “at least one of” means any combination of items or number of items may be used from the list, but not all of the items in the list may be required.

For example, “at least one of item A, item B, and item C” may mean item A; item A and item B; item B; item A, item B, and item C; or item B and item C. In some cases, “at least one of item A, item B, and item C” may mean, for example, without limitation, two of item A, one of item B, and ten of item C; four of item B and seven of item C; or some other suitable combination.

Once secure wireless connection212has been established, security measure214may need to be satisfied. Satisfying security measure214may include, for example, without limitation, authenticating the identify of at least one of device operator112, onboard device110, or aircraft100; confirming a tail identifier for aircraft100; authenticating aircraft100based on at least a portion of Out, Off, On, In (OOOI) data for aircraft100; confirming that aircraft100is in-flight or in some other phase of flight; or some combination thereof.

In this illustrative example, security measure214is encountered and handled after secure wireless connection212has been established. In this manner, security measure214may be an additional level of security. However, in other illustrative examples, passing security measure214may be considered part of the process of establishing secure wireless connection212. Thus, until security measure214is satisfied, onboard device110may be prevented from being able to access medical data storage infrastructure206.

Medical data storage infrastructure206may be implemented using at least one of cloud storage, a server system comprised of one or more servers, a database, or some other type of data storage. In this illustrative example, medical data storage infrastructure206may only be accessible by the airline that owns and operates aircraft100. However, in other illustrative examples, medical data storage infrastructure206may be accessible by a selected group of airlines.

Medical data storage infrastructure206stores medical data for any persons who have previously opted to have their medical data transferred to and stored in medical data storage infrastructure206. Depending on the implementation, a person may need to opt into using medical data storage infrastructure206for a minimum amount of time before the scheduled departure time of the flight to allow sufficient time for the transfer of their medical data into medical data storage infrastructure206.

As one illustrative example, the airline may request that each of passengers106inFIG. 1decide whether to opt into using medical data storage infrastructure206at the time they book the flight. In other illustrative examples, the airline may request that each of passengers106decide whether to opt into using medical data storage infrastructure206before some selected number of days before the flight. For example, the decision may need to be made by two, three, four, ten, or some other number of days before the flight. In some cases, the decision may need to be made at least one or more weeks before the flight.

For example, passengers106inFIG. 1may opt to authorize the transfer of and storage of medically relevant data in medical data storage infrastructure206, the transfer of medical data from medical data storage infrastructure206to a remote device such as remote device202, the transfer of medical data from medical data storage infrastructure206to an authenticated onboard device such as onboard device210, the transfer of medical data from medical data storage infrastructure206to one or more on-ground medical centers, or some combination thereof. In this manner, a passenger may determine whether medical professional210, a device operator using onboard device such as device operator112inFIG. 1, or both may be allowed to access the medical data of the passenger from medical data storage infrastructure206.

The medical data stored in medical data storage infrastructure206may include, for example, without limitation, at least one of medical history information, medication information, previously recorded physiological data, health insurance information, family history information, mental health information, or some other type of medically relevant information. In some cases, medical data storage infrastructure206may include additional personal data, such as, for example, without limitation, personal contact information, emergency contact information, dietary restrictions information, dietary preference information, exercise information, other types of personal information, or some combination thereof.

In this illustrative example, once onboard device110establishes secure wireless connection216with medical data storage infrastructure206and security measure218has been satisfied, onboard device110may be able to access medical data storage infrastructure206. Depending on the implementation, secure wireless connection216may be established and security measure218satisfied in a manner similar to or different from secure wireless connection212and security measure214, respectively. Further, depending on the implementation, satisfying security measure218may be considered part of or separate from the process of establishing secure wireless connection216.

In some illustrative examples, satisfying security measure218may include mutual authentication between onboard device110and medical data storage infrastructure206. For example, satisfying security measure218may include validating a certificate for medical data storage infrastructure206at onboard device110and validating a certificate for onboard device110at medical data storage infrastructure206. The request for mutual authentication may be initiated by onboard device110in these illustrative examples. Once security measure218has been satisfied, onboard device110may be capable of accessing medical data for passenger108fromFIG. 1who is experiencing symptoms.

Device operator112inFIG. 1may use onboard device110to hold a video conference session with medical professional210. As one illustrative example, secure wireless connection220is established between onboard device110and conference server system208. Further, secure wireless connection222is established between remote device202and conference server system208.

In this illustrative example, both security measure224and security measure226need to be passed in order for a video conference session to be set up through conference server system208. Satisfying security measure224may include mutual authentication between conference server system208and onboard device110. Satisfying security measure226may include mutual authentication between conference server system208and remote device202.

Depending on the implementation, secure wireless connection220and secure wireless connection222may be established in a manner similar to or different from secure wireless connection212and secure wireless connection216, respectively. Further, depending on the implementation, satisfying security measure224and security measure226may be considered part of or separate from the process of establishing secure wireless connection220and secure wireless connection222, respectively.

Once security measure224and security measure226have been satisfied, device operator112inFIG. 1may participate in a video conference session through conference server system208with medical professional210who is using remote device202. Through the video conference session, device operator112inFIG. 1can communicate with medical professional210, explain the symptoms of passenger108inFIG. 1to medical professional210, send medical data retrieved from medical data storage infrastructure206for passenger108from onboard device110to remote device202, or some combination thereof.

In some illustrative examples, medical data storage infrastructure206may be accessible by remote device202. For example, without limitation, secure wireless connection228may be established between remote device202and medical data storage infrastructure206. Once security measure230is satisfied, remote device202can access medical data storage infrastructure206. In this manner, medical professional210may be able to retrieve medical data for passenger108directly from medical data storage infrastructure206.

Depending on the implementation, secure wireless connection228may be established and security measure230satisfied in a manner similar to or different from secure wireless connection216and security measure218, respectively. Further, depending on the implementation, satisfying security measure230may be considered part of or separate from the process of establishing secure wireless connection228.

Medical professional210provides a medical assessment of passenger108through the video conference session. The medical assessment may include different types of information. For example, without limitation, the medical assessment may include at least one of a medical diagnosis for the symptoms experienced by passenger108inFIG. 1, instructions for isolating passenger108from the rest of passengers106, instructions for treating passenger108, instructions for communicating at least a portion of the content of the medical assessment of passenger108to passenger108, an indication of the severity of the medical condition of passenger108, an indication as to whether aircraft100needs to be diverted to an alternate destination, an indication of whether a medical specialist having more specialized training than the medical professional needs to be contacted, or some other type of information.

In this manner, aircraft medical management system101may be used to provide medical assistance to a passenger onboard aircraft100during any phase of flight. Aircraft medical management system101ensures that passengers106onboard aircraft100inFIG. 1will have access to prompt medical assistance from a medical professional even when aircraft100is thousands of miles in the air.

With reference now toFIG. 3, an illustration of a process for communicating with a medical professional using an onboard device is depicted in accordance with an illustrative embodiment. In this illustrative example, onboard device300takes the form of a smartphone having display302.

Onboard device300may be used onboard an aircraft, such as aircraft100inFIGS. 1-2, as part of an aircraft medical management system. In this illustrative example, a device operator may use onboard device300to communicate with a medical professional who is using a remote device on the ground. For example, device operator112inFIG. 1may use onboard device300, instead of onboard device110inFIGS. 1-2, to communicate with medical professional210inFIG. 2.

In one illustrative example, providing medical assistance to a passenger, such as passenger108inFIG. 1, onboard an aircraft during flight using onboard device300may include performing multiple steps. These steps may include, for example, but are not limited to, device authentication304, passenger identification306, conference session creation308, and medical discussion310. The results of these steps may be used to provide medical care to the passenger. For example, instructions provided by the remotely located medical professional210during medical discussion310may be used to administer treatment to or otherwise medically care for a passenger.

Device authentication304is performed to authenticate and validate onboard device300such that onboard device300can receive data from a medical data storage infrastructure, such as medical data storage infrastructure206inFIG. 2. In one illustrative example, prompt312is displayed on display302of onboard device300. Prompt312is a request for a passphrase that can be used to authenticate onboard device300. Device operator112enters passphrase314such that onboard device300can be authenticated. Once onboard device300is authenticated, onboard device300may be able to access medical data storage infrastructure206.

Next, passenger identification306is performed. In one illustrative example, prompt316is displayed in display302of onboard device300. Prompt316is a request for a passenger identifier that can be used to access the medical data specific to passenger108. The device operator enters passenger identifier318. Passenger identifier318is used to retrieve the medical data stored in medical data storage infrastructure206for the corresponding passenger108.

Thereafter, conference session creation308is performed. This step may be performed in any number of ways. Performing conference session creation308may require, for example, without limitation, that a conference server system, such as conference server system208inFIG. 2, authenticate both onboard device300and remote device202being used by medical professional210. The conference session may include audio, video, or both, depending on the implementation.

Once a conference session has been created such that device operator112fromFIG. 1using onboard device300can communicate with medical professional210using remote device202, medical discussion310may ensue. Further, during the conference session, some portion of the medical data for passenger108retrieved from medical data storage infrastructure206may be sent from onboard device300to remote device202being used by medical professional210. Medical professional210and device operator112using onboard device300may discuss the symptoms being experienced by passenger108, the medical data about passenger108, and other relevant information regarding passenger108. In this manner, medical professional210may provide a medical assessment of passenger108.

With reference now toFIG. 4, an illustration of medical devices for use with onboard device300fromFIG. 3is depicted in accordance with an illustrative embodiment. In this illustrative example, each of medical devices400may be connected to onboard device300and used to generate physiological data for a person.

In this illustrative example, attachment element402is shown connected to onboard device300. Each of medical devices400may be capable of being connected to onboard device300through attachment element402. As depicted, medical devices400may include, but are not limited to, electrocardiogram (EKG) machine404, otoscope406, ophthalmoscope408, digital thermometer410, and tympanometric instrument412.

The illustration of aircraft100inFIG. 1, aircraft medical management system101inFIGS. 1-2, onboard device300inFIGS. 3-4, and medical devices400inFIG. 4is not meant to imply physical, functional, logical, or architectural limitations to the manner in which an illustrative embodiment may be implemented. Other components in addition to or in place of the ones illustrated may be used. Some components may be optional.

With reference now toFIG. 5, an illustration of an aircraft medical management system is depicted in the form of a block diagram in accordance with an illustrative embodiment. In this illustrative example, aircraft medical management system500is an example of a system that may be used to provide medical assistance onboard aircraft501. Aircraft501may take the form of a passenger aircraft, a transportation aircraft, a medical evacuation aircraft, or some other type of aircraft.

Aircraft medical management system101described inFIGS. 1-2is an example of one implementation for aircraft medical management system500inFIG. 5. Aircraft100inFIGS. 1-2is an example of one implementation for aircraft501inFIG. 5.

In this illustrative example, aircraft medical management system500may be used to provide medical assistance to any number of people onboard aircraft501in response to medical event502. Medical event502may occur during any one of the phases of flight503of aircraft501. Aircraft medical management system500enables medical assistance to be provided in response to medical event504during taxiing, take-off, ascent, cruise, descent, landing, final approach, or some other phase of flight503.

In one illustrative example, medical event502is person504experiencing set of symptoms505while person504is onboard aircraft501. Person504may take the form of a passenger, a crew member, a pilot, a co-pilot, or some other person onboard aircraft501. Set of symptoms505may include, for example, without limitation, fever, shortness of breath, pain, a headache, nausea, vomiting, skin discoloration, hearing impairment, vision impairment, tachycardia, an arrhythmia, a weakened pulse, one or more other types of symptoms, or some combination thereof. In some illustrative examples, medical event502may be more than one person experiencing one or more same or different symptoms.

As depicted, aircraft medical management system500includes onboard device506, remote device508, medical data storage infrastructure510, and number of server systems512. Onboard device506is located on aircraft501, while remote device508is located off-board. For example, remote device508may be located on the ground. Depending on the implementation, medical data storage infrastructure510may be located onboard, off-board, or both.

Onboard device506may take a number of different forms. In one illustrative example, onboard device506takes the form of mobile computer system514. Mobile computer system514may take the form of a tablet, a laptop, a tablet-laptop hybrid, a smartphone, or some other type of mobile computer system514. In other illustrative examples, onboard device506may take the form of a computer system that is located in a fixed location onboard aircraft501. For example, without limitation, onboard device506may be a computer system that is in a fixed location onboard aircraft501in an area designated for medically attending to persons onboard aircraft501.

Similarly, remote device508may take a number of different forms. In one illustrative example, remote device508takes the form of remote computer system516. Remote computer system516may take the form of a tablet, a laptop, a tablet-laptop hybrid, a smartphone, a desktop computer system, or some other type of computer system located remotely.

Device operator518may use onboard device506to communicate with medical professional520who uses remote device508. Device operator518may be, for example, without limitation, a crew member onboard aircraft501who has a selected level of medical training and who has authorization to use onboard device506. However, in other illustrative examples, device operator518may be a medical professional, such as a physician, a nurse, a physician's assistant, or some other type of medical professional.

In still other illustrative examples, device operator518may be any crew member with authorization to use onboard device506, a pilot of aircraft501, a co-pilot of aircraft501, a passenger onboard aircraft501, or some other person onboard aircraft501. For example, when medical event502is an emergency medical event, a passenger may use onboard device506to communicate with medical professional520when crew member availability is limited and time is of the essence.

Device operator518and medical professional520communicate with each other through onboard device506and remote device508, respectively, using one or more number of communications links. For example, number of secure wireless connections522may be established between onboard device506and remote device508. Each secure wireless connection in number of secure wireless connections522may include one or more wireless communications links that allow the secure exchange of data.

In one illustrative example, number of secure wireless connections522may be established between onboard device506located onboard aircraft501and remote device508located remotely with respect to aircraft501to enable communications between device operator518using onboard device506and medical professional520using remote device508. Information524related to medical event502is sent from onboard device506to remote device508using number of secure wireless connections522. Medical professional520uses information524received at remote device508to formulate medical assessment526of medical event504. Medical assessment526of medical event502by medical professional520is received at onboard device506over number of secure wireless connections522from remote device508.

Medical assessment526may include different types of information. For example, without limitation, medical assessment526may include at least one of an overall medical evaluation of medical event502, a medical diagnosis for set of symptoms505experienced by person504, a number of isolation instructions for isolating person504from other persons onboard aircraft501, a number of treatment instructions for treating person504, a number of advising instructions for communicating at least a portion of the content of medical assessment526to person504, an indication of the severity of the medical condition of person504, an indication as to whether aircraft501needs to be diverted to an alternate destination, an indication of whether a specialist having more specialized training and expertise than medical professional520needs to be contacted, or some other type of information.

In response to receiving medical assessment526, number of actions528may be performed based on medical assessment526to manage medical event502onboard aircraft501. Number of actions528may be performed by at least one of device operator518or some other person onboard aircraft501.

For example, without limitation, device operator518may perform number of actions528to assist person504onboard aircraft501experiencing set of symptoms505. Number of actions528may be performed to at least one of isolate, treat, or advise person504. Advising person504may include, for example, without limitation, communicating at least a portion of the content of medical assessment526to person504, explaining other actions being performed by device operator518to assist person504, providing other information to person504based on medical assessment526, or some combination thereof.

In some illustrative examples, number of actions528may include changing a flight route of aircraft501. For example, flight503of aircraft501may be diverted from a current destination of flight505to an alternate destination. In one illustrative example, the alternative destination is selected based on proximity to an on-ground medical center that has been selected for person504. The alternate destination may be an airport near the on-ground medical center, an airfield or other suitable landing area near the on-ground medical center, the on-ground medical center itself, or some other type of destination. The on-ground medical center may be a hospital, a clinic, a medical facility located at an airport, or some other type of medical center.

Communications between device operator518using onboard device506and medical professional520using remote device508may be implemented in a number of different ways. In one illustrative example, information524related to medical event502may be sent directly from onboard device506to remote device508over number of secure wireless connections522.

Information524may include different types of information. In some illustrative examples, information524may include information about aircraft501, flight505, onboard device506, device operator518, or a combination thereof. In other illustrative examples, information524may include physiological data530generated for person504.

Physiological data530may be generated onboard aircraft501using number of medical devices531in communication with onboard device506. In one illustrative example, a medical device in number of medical devices531may be capable of being directly connected to onboard device506such that data generated by the medical device is sent to onboard device506. In other illustrative examples, a medical device in number of medical devices531may be used to generate data and may then wirelessly send this data to onboard device506. In some illustrative examples, a medical device in number of medical devices531is used to collect physiological information about person504. This physiological information is then manually input by device operator518into onboard device506.

In these illustrative examples, number of medical devices531may be considered part of aircraft medical management system500. Number of medical devices531may include at least one of, for example, without limitation, a digital thermometer, an electronic stethoscope, an electrocardiogram machine, a tympanometric instrument, a sphygmomanometer, an otoscope, an ophthalmoscope, a pulse oximeter, a vital signs monitor, a laryngoscope, a penlight, a diagnostic station, an x-ray machine, an ultrasound device, or some other type of medical device or instrument.

In some cases, information524may include corresponding medical data532for person504retrieved from medical data storage infrastructure510. Medical data storage infrastructure510may be implemented using any number of different types of data storage infrastructures. In one illustrative example, medical data storage infrastructure510takes the form of medical data cloud storage534. In other illustrative examples, medical data storage infrastructure510may be comprised of at least one of cloud storage, a database, a server system that includes one or more servers, or some other type of data storage.

As depicted, data535is stored in medical data storage infrastructure510. Data535may include medical data536for one or more persons who opt to authorize the storage of medically relevant data in medical data storage infrastructure510.

As one illustrative example, when booking a flight, registering with an airline, or registering with a medical service associated with an airline, the customers of the airline may be given the option to authorize the transfer of their medical data to medical data storage infrastructure510, the transfer of this medical data from medical data storage infrastructure510to an authenticated onboard device such as onboard device506, the transfer of this medical data from medical data storage infrastructure510to an authenticated remote device such as remote device508, or some combination thereof. In this manner, a customer may determine whether medical professional520, device operator518, or both may be allowed to access the medical data of the customer from medical data storage infrastructure510. Any transfer of medical data between devices and storage infrastructures is performed in accordance with federal regulations and guidelines, including, but not limited to the Health Insurance Portability and Accountability Act (HIPAA).

In this illustrative example, medical data536may include, but is not limited to, at least one of medical history information, medication information, previously recorded physiological data, health insurance information, family history information, or some other type of medically relevant information. In some cases, medical data storage infrastructure510may store additional personal data538. Additional personal data538may include, for example, without limitation, at least one of personal contact information, emergency contact information, dietary restrictions information, dietary preference information, exercise information, or some other type of additional information.

In response to person504experiencing set of symptoms505onboard aircraft501, device operator518may establish secure wireless connection540between onboard device506and medical data storage infrastructure510. Secure wireless connection540may include one or more wireless communications links. In one illustrative example, device operator518uses onboard device506to retrieve corresponding medical data532from medical data storage infrastructure510over secure wireless connection540. Corresponding medical data532may include at least a portion of medical data536stored in medical data storage infrastructure510for person504.

In some illustrative examples, remote device508may have the capability of accessing medical data storage infrastructure510directly. For example, medical professional520may establish secure wireless connection542between remote device508and medical data storage infrastructure510. Secure wireless connection542may include one or more wireless communications links. Medical professional520may access corresponding medical data532for person504directly from medical data storage infrastructure510in this illustrative example.

In some cases, set of policies541may be stored in medical data storage infrastructure510. Each of set of policies541may be for a person who has opted for storing their medical data in medical data storage infrastructure510.

For example, policy543in set of policies541may be associated with person504. Policy543may include at least one of a set of rules, a set of guidelines, a set of restrictions, a set of authorizations, a set of criteria, or other information. Policy543may take the form of at least one of a report, a spreadsheet, a database, a document, some other type of file, or some other type of computer resource. Policy543may determine which data stored in medical data storage infrastructure510may be accessible by an onboard device, such as onboard device506, and which data stored in medical data storage infrastructure510may be accessible by a remote device, such as remote device508.

In some illustrative example, policy543may determine whether any of information524about person504can be forwarded from onboard device506or medical data storage infrastructure510to an on-ground medical center selected for person504. For example, when flight503has been diverted such that person504may be taken to a selected on-ground medical center, policy543may determine whether any of information524about person504may be forwarded to the selected on-ground medical center.

Person504may choose to provide a general authorization that allows all physiological data530and corresponding medical data532for person504to be forwarded to any on-ground medical center. In another example, person504may provide a specific authorization for which on-ground medical centers may receive this data.

In this manner, policy543may determine which data stored in medical data storage infrastructure510may be viewed by a device operator, such as device operator518, and which data stored in medical data storage infrastructure510may be viewed by a medical professional, such as medical professional520. Further, policy543may determine what types of information524about person504may be forwarded to on-ground medical centers.

In some illustrative examples, at least a portion of information524may be sent from onboard device506to remote device508through a conference session. For example, number of server systems512may be used to establish interactive interface547between onboard device506and remote device508. In particular, secure wireless connection544may be established between onboard device506and number of server systems512. Secure wireless connection546may be established between remote device508and number of server systems512.

Secure wireless connection544and secure wireless connection546may each be comprised of one or more wireless communications links. Further, secure wireless connection544and secure wireless connection546may be included as part of number of secure wireless connections522. In this manner, number of secure wireless connections522may enable communications between onboard device506and remote device508directly, indirectly, or both.

Interactive interface547enables communications between device operator518using onboard device506and medical professional520using remote device508. Interactive interface547may take the form of conference session548in one illustrative example. In this example, conference server system550in number of server systems512is used to establish conference session548. Conference session548may include video capabilities, audio capabilities, chat capabilities, or a combination thereof, depending on the implementation.

For example, conference session548may be a video conference session that enables device operator518to communicate directly with medical professional520. Device operator518may communicate at least a portion of information524to medical professional520through conference session548. Further, depending on the circumstances, the video conference session may also allow medical professional520to remotely observe person504experiencing set of symptoms505.

In some illustrative examples, medical assessment526of medical event502may be communicated by medical professional520to device operator518through conference session548. In other illustrative examples, medical professional520may send medical assessment526from remote device508to onboard device506directly over number of secure wireless connections522in the form of a report.

In these illustrative examples, each of the different secure wireless connections described above may be established using any of a number of different means. Further, any number of security measures may be implemented in association with any one of these secure wireless connections. As one illustrative example, a security measure may be implemented in association with secure wireless connection540. This security measure may be considered separate from or part of the process of establishing secure wireless connection540.

The security measure may include, for example, without limitation, at least one of a firewall, an intrusion prevention system, anti-virus software, authentication requirements, certificate validation requirements, or some other type security system. Depending on the implementation, satisfying the security measure may include, but is not limited to, certificate validation; key authentication; authentication of the identify of at least one of device operator518, onboard device506, or aircraft501; confirmation of a tail identifier for aircraft501; authentication of aircraft501based on at least a portion of Out, Off, On, In (OOOI) data for aircraft501; conformation that aircraft501is in a phase of flight503; or some type action.

In some illustrative examples, secure wireless connection540may be unable to be established between onboard device506and medical data storage infrastructure510until at least one of device operator518, onboard device506, or aircraft501has been authenticated by authenticating system552. Authenticating system552may be, for example, a back-office server system, an airline computer system, or some other type of system. Airline computer system204inFIG. 2may be an example of one implementation for this type of authenticating system552.

As one illustrative example, device operator518may use a security token to establish secure wireless connection540between onboard device506and authenticating system552. The security token may take the form of a hardware security token or a software security token, depending on the implementation.

For example, the security token may include, without limitation, a Universal Serial Bus (USB) token, a key fob, an authentication token, a cryptographic token, a virtual token, a cryptographic key, a digital signature, biometric data, some other type of hardware device, some other type of software component, or some combination thereof. In one illustrative example, the security taken may take the form of a Universal Serial Bus (USB) token that generates a revolving random key that may be used to authenticate onboard device506. In this illustrative example, secure wireless connection540may only be established after onboard device506has been authenticated by authenticating system552.

In this manner, aircraft medical management system500may be implemented in any number of different ways to provide medical assistance to persons onboard an aircraft, such as aircraft501. Depending on the implementation, aircraft medical management system500may include multiple onboard devices for use with multiple aircraft, multiple remote devices for use by multiple medical professionals, or some combination thereof.

Aircraft medical management system500may reduce the time needed to medically attend to persons experiencing symptoms onboard an aircraft. Further, aircraft medical management system500may improve the decision-making that is performed onboard an aircraft in response to medical events. For example, the decision-making with respect to when aircraft501is to be diverted or when aircraft501is to turn back around and return to a starting point may be improved. With this improved decision-making, the medical care provided to persons onboard an aircraft may be improved. Further, with this improved decision-making, cost savings for the airline may be achieved.

In some cases, person504may not have previously opted to have their medical data transferred to and stored in medical data storage infrastructure510. Further, person504may not have previously authorized that certain actions be allowed to be taken by device operator518or some other crew member onboard aircraft501. In these types of situations, default procedures may be put in place for providing medical assistance to person504.

For example, when medical event502that occurs onboard aircraft501is an emergency medical event involving person504or some other type of life-threatening or severe medical event involving person504, device operator518may implement default procedures for communicating with medical professional520using onboard device506, diverting aircraft501to an alternate destination in proximity to a nearest on-ground medical center, or both. In this manner, onboard device506may be used to provide medical care to person504even if person504has not opted into the usage of medical data storage infrastructure510.

The illustration of aircraft medical management system500inFIG. 5is not meant to imply physical or architectural limitations to the manner in which an illustrative embodiment may be implemented. Other components in addition to or in place of the ones illustrated may be used. Some components may be optional. Also, the blocks are presented to illustrate some functional components. One or more of these blocks may be combined, divided, or combined and divided into different blocks when implemented in an illustrative embodiment.

For example, conference session548may not be needed in some cases. In some illustrative examples, onboard device506may have connection manger554that is used to manage any secure wireless connections established between onboard device506and devices or systems. Connection manager554may be implemented using hardware, software, firmware, or some combination thereof, depending on the implementation.

In other illustrative examples, conference session548may be established through cloud computing. For example, a conference cloud may serve as a relay point for conference session548between onboard device506and remote device508.

In some illustrative examples, data535stored in medical data storage infrastructure510may be updated over time. For example, medical data536and additional personal data538for person504may be updated as this data changes for person504over time.

In some illustrative examples, data535stored in medical data storage infrastructure510may include data about medical events that occurred on the various aircraft belonging to an airline or multiple airlines. For example, when person504is involved in medical event502that occurs onboard aircraft501, information about medical event502, the handling of medical event502, and the resolution of medical event502may be recorded and stored in medical data storage infrastructure510. This type of data may be available for future use in improving the manner in which medical care is provided to persons.

With reference now toFIG. 6, an illustration of a process for providing medical assistance onboard an aircraft is depicted in the form of a flowchart in accordance with an illustrative embodiment. The process illustrated inFIG. 6may be implemented using aircraft medical management system500described inFIG. 5.

The process begins by establishing a number of secure wireless connections between an onboard device located on the aircraft and a remote device located remotely with respect to the aircraft, to enable communications between a device operator using the onboard device and a medical professional using the remote device (operation600). Next, information about a medical event that occurs onboard the aircraft is sent from the onboard device to the remote device using the number of secure wireless communications links (operation602).

A medical assessment of the medical event by a medical professional is received at the onboard device from the remote device over the number of secure wireless connections (operation604). A number of actions may then be performed to manage the medical event based on the medical assessment (operation606), with the process terminating thereafter.

With reference now toFIG. 7, an illustration of a process for providing medical assistance to a person onboard an aircraft is depicted in the form of a flowchart in accordance with an illustrative embodiment. The process illustrated inFIG. 7may be implemented using aircraft medical management system500described inFIG. 5.

The process begins by observing a person experiencing a set of symptoms onboard an aircraft during flight (operation700). In response to this observation, a secure wireless connection is established between an onboard device and a medical data storage infrastructure (operation702). Corresponding medical data for the person is retrieved from the medical data storage infrastructure over the secure wireless connection (operation704).

Next, physiological data is collected for the person using a number of medical devices (operation706). In operation706, the physiological data may include, for example, without limitation, a temperature of the person, blood pressure information, hearing test data, eye test data, electrocardiogram data, other types of physiological data, or some combination thereof.

Thereafter, a secure wireless connection is established between the onboard device and a conference server system (operation708). A conference session is created between the onboard device and a remote device that has also established a secure wireless connection with the conference server system (operation710).

Information relating to the person experiencing the set of symptoms is sent from the onboard device to the remote device through the conference session by a device operator using the onboard device (operation712). In one illustrative example, operation712, the information may be communicated by the device operator to the medical professional through the conference session in verbal form, visual form, or both. In operation712, this information may include at least a portion of the corresponding medical data retrieved from the medical data storage infrastructure, at least a portion of the physiological data collected using the number of onboard devices, other information about the person, or some combination thereof.

In response to receiving this information, a medical assessment of the person experiencing the set of symptoms made by the medical profession based on the information is received through the conference session at the onboard device (operation714). In operation714, the medical assessment may be communicated to the device operator by the medical operator through the conference session in verbal form, visual form, or both. A number of actions may then be performed based on the medical assessment to medically assist the person experiencing the set of symptoms (operation716), with the process terminating thereafter.

With reference now toFIG. 8, an illustration of a process for determining whether a flight route for an aircraft needs to be changed for a person experiencing a set of symptoms onboard an aircraft is depicted in the form of a flowchart in accordance with an illustrative embodiment. The process illustrated inFIG. 8may be an example one manner in which operation716inFIG. 7may be performed.

The process begins by determining whether a person experiencing a set of symptoms onboard the aircraft should be treated on-ground before the aircraft will reach a current destination of the aircraft based on a medical assessment of the set of symptoms received from a medical professional (operation800). The medical assessment described inFIG. 8may be, for example, the medical assessment received in operation714inFIG. 7.

If the person does not need to be treated on-ground before the aircraft will reach the current destination, the flight route for the aircraft does not need to be changed and the determination process terminates. Otherwise, in response to a determination that the person should be treated on-ground before the aircraft will reach the current destination, an on-ground medical center is selected from a plurality of on-ground medical centers based on the medical assessment (operation802). The plurality of on-ground medical centers may include a list of hospitals, clinics, emergency clinics, other types of medical centers, or some combination thereof.

The selection of an on-ground medical center in operation802may be performed in any number of ways. In one illustrative example, the on-ground medical center is selected based on at least one of a current position of the aircraft and proximity of the on-ground medical center to the current position of the aircraft, a heading of the aircraft, an altitude of the aircraft, a fuel status of the aircraft, an approved route structure for the aircraft, a passenger manifest, an airport or other suitable landing area in proximity to the on-ground medical center, or a number of aircraft capability factors. In some cases, health insurance information for the person may be used to select an on-ground medical center. For example, when the medical condition of the person is not life-threatening, a choice may be made to select an in-network on-ground medical center that may be located farther away than an out-of-network on-ground medical center.

Next, a flight route of the aircraft is changed by selecting a new destination for the aircraft based on the on-ground medical center selected (operation804). The new destination may be the on-ground medical center, an airport near the on-ground medical center, an airfield near the on-ground medical center, or some other area near the on-ground medical center.

Thereafter, a determination may be made as to whether the person has authorized the forwarding of data about the person to the on-ground medical center (operation806). For example, the person may have authorized that their medical data be forwarded to any on-ground medical center as needed, only specifically identified on-ground medical centers, or the closest on-ground medical center upon arrival at any authorized destination. In some illustrative examples, a record of this authorization may be stored in the medical data storage infrastructure from which the medical data for the person was retrieved.

If the person has not authorized forwarding of the data, the process terminates. In this manner, the flight route of the aircraft is changed such that the person can be taken to the on-ground medical center for treatment but their medical data may not be sent to the on-ground medical center prior to their arrival.

With reference again to operation806, if the person has authorized forwarding of the data, the data about the person is sent to the on-ground medical center in response (operation808), with the process terminating thereafter. The data may include at least one of medical data, physiological data, mental health data or other personal data about the person.

With reference now toFIG. 9, an illustration of a process for remotely assessing a person experiencing a set of symptoms onboard an aircraft is depicted in the form of a flowchart in accordance with an illustrative embodiment. The process illustrated inFIG. 9may be implemented using a remote device, such as remote device510inFIG. 5.

The process begins by establishing a secure wireless connection between a remote device being used by a medical professional and a conference server system (operation900). Next, a conference session is created between the remote device and an onboard device being used by a device operator onboard an aircraft (operation902). In operation902, the onboard device is also securely and wirelessly connected to the conference server system. The conference server system serves as a relay point between the onboard device and the remote device.

Next, information about a person experiencing a set of symptoms onboard the aircraft is received through the conference session at the remote device (operation904). Then, a medical assessment of the person experiencing the set of symptoms made by the medical professional is sent from the remote device to the onboard device (operation906). The conference session is then terminated when the expertise of the medical professional is no longer needed (operation908), with the process terminating thereafter.

For example, in some cases, operation708and operation710inFIG. 7may be performed prior to operation706inFIG. 7such that the conference session is created before physiological data is collected for the person. In some cases, establishing the conference session first may enable the medical professional to instruct the device operator with respect to what types of physiological data need to be collected and how to collect the physiological data.

Turning now toFIG. 10, an illustration of a data processing system in the form of a block diagram is depicted in accordance with an illustrative embodiment. Data processing system1000may be used to implement onboard device506, remote device508, or both inFIG. 5. As depicted, data processing system1000includes communications framework1002, which provides communications between processor unit1004, storage devices1006, communications unit1008, input/output unit1010, and display1012. In some cases, communications framework1002may be implemented as a bus system.

Processor unit1004is configured to execute instructions for software to perform a number of operations. Processor unit1004may comprise a number of processors, a multi-processor core, and/or some other type of processor, depending on the implementation. In some cases, processor unit1004may take the form of a hardware unit, such as a circuit system, an application specific integrated circuit (ASIC), a programmable logic device, or some other suitable type of hardware unit.

Instructions for the operating system, applications, and/or programs run by processor unit1004may be located in storage devices1006. Storage devices1006may be in communication with processor unit1004through communications framework1002. As used herein, a storage device, also referred to as a computer readable storage device, is any piece of hardware capable of storing information on a temporary and/or permanent basis. This information may include, but is not limited to, data, program code, and/or other information.

Memory1014and persistent storage1016are examples of storage devices1006. Memory1014may take the form of, for example, a random access memory or some type of volatile or non-volatile storage device. Persistent storage1016may comprise any number of components or devices. For example, persistent storage1016may comprise a hard drive, a flash memory, a rewritable optical disk, a rewritable magnetic tape, or some combination of the above. The media used by persistent storage1016may or may not be removable.

Communications unit1008allows data processing system1000to communicate with other data processing systems and/or devices. Communications unit1008may provide communications using physical and/or wireless communications links.

Input/output unit1010allows input to be received from and output to be sent to other devices connected to data processing system1000. For example, input/output unit1010may allow user input to be received through a keyboard, a mouse, and/or some other type of input device. As another example, input/output unit1010may allow output to be sent to a printer connected to data processing system1000.

Display1012is configured to display information to a user. Display1012may comprise, for example, without limitation, a monitor, a touch screen, a laser display, a holographic display, a virtual display device, and/or some other type of display device.

In this illustrative example, the processes of the different illustrative embodiments may be performed by processor unit1004using computer-implemented instructions. These instructions may be referred to as program code, computer usable program code, or computer readable program code and may be read and executed by one or more processors in processor unit1004.

In these examples, program code1018is located in a functional form on computer readable media1020, which is selectively removable, and may be loaded onto or transferred to data processing system1000for execution by processor unit1004. Program code1018and computer readable media1020together form computer program product1022. In this illustrative example, computer readable media1020may be computer readable storage media1024or computer readable signal media1026.

Computer readable storage media1024is a physical or tangible storage device used to store program code1018rather than a medium that propagates or transmits program code1018. Computer readable storage media1024may be, for example, without limitation, an optical or magnetic disk or a persistent storage device that is connected to data processing system1000.

Alternatively, program code1018may be transferred to data processing system1000using computer readable signal media1026. Computer readable signal media1026may be, for example, a propagated data signal containing program code1018. This data signal may be an electromagnetic signal, an optical signal, and/or some other type of signal that can be transmitted over physical and/or wireless communications links.

The illustration of data processing system1000inFIG. 10is not meant to provide architectural limitations to the manner in which the illustrative embodiments may be implemented. The different illustrative embodiments may be implemented in a data processing system that includes components in addition to or in place of those illustrated for data processing system10. Further, components shown inFIG. 10may be varied from the illustrative examples shown.

Thus, the illustrative embodiments provide an aircraft medical management system for providing in-flight medical assistance. In particular, the illustrative embodiments provide a method and system for providing live, substantially real-time medical assistance to one or more persons experiencing symptoms onboard an aircraft during flight.

In one illustrative example, this live medical assistance is provided onboard an aircraft via a secure video conference link between an onboard device located on the aircraft and a remote device located off-board. All communications between the onboard device and the remote device may be secure. In this manner, confidentiality of medical data may be maintained during communications between the device operator using the onboard device and the medical professional using the remote device.

In some illustrative examples, persons onboard an aircraft may have had the option to opt-in to have their medical history uploaded to secure medical data cloud storage. Access to this medical data storage cloud may require satisfying any number of security measures. For example, an out of band two-factor authentication may be required before medical data can be retrieved from the medical data storage cloud. Further, a similar type of two-factor authentication may be required to send this medical data from an onboard device to a remote device being used by a medical professional.

In one illustrative example, a medical data storage infrastructure that stores medical data about individuals is provided. The medical data storage infrastructure may be capable of securely and wirelessly connecting to an onboard device located on an aircraft or other airborne vehicle.

For example, a secure wireless connection may be established between the onboard device and the medical data storage infrastructure to enable retrieval, by the onboard device, of medical data about an individual from the medical data storage infrastructure. In some cases, a secure wireless connection may be established between the medical data storage infrastructure and a remote device located off-board with respect to an aircraft to enable retrieval, by the remote device, of medical data about an individual located onboard the aircraft from the medical data storage infrastructure for use in providing medical assistance to the individual.