System and method to access casualty health information in an emergency situation

Abstract

A system, method, and computer program product for automatically identifying a casualty and matching an electronic health record (EHR) to the casualty. A casualty identification is determined by matching a presenting image of the casualty with one of a master image or a social media profile image of the casualty. A recognized patient messaging system (RPMS) is configured to query one or more electronic health records (EHR) service providers for the existence of an EHR corresponding the identified casualty and automatically communicate the existence of the EHR to the EMS provider. A blockchain trusted identification module (BTIM) is configured to establish a trust relationship between the EMS provider and the one or more EHR service providers to establish a trusted pathway for delivery of the casualty's EHR to the EMS provider. With the casualty's EHR emergency responders can provide better care for the casualty in an emergency.

What is claimed is: 
     
         1 . A system for automatically determining an existence of an electronic health record corresponding to an identified casualty across one or more electronic health records (EHR) providers, comprising:
 a server hosting a casualty identification and EHR matching service, the server comprising:
 a patient identification module configured to identify a casualty based on an identification of the casualty received from a mobile computing device operated by an emergency medical service (EMS) provider; 
 a recognized patient messaging system (RPMS) configured to query one or more electronic health records (EHR) service providers for the existence of a corresponding EHR belonging to the identified casualty upon receipt of the identification; and 
 a blockchain trusted identification module (BTIM) configured to establish a consensus between the identified casualty, the one or more EHR service providers, and the EMS provider. 
   
     
     
         2 . The system of  claim 1 , wherein the consensus comprises:
 a first blockchain trust contract between the identified casualty and the casualty identification and EHR matching service; and   a second blockchain trust contract between the one or more EHR service providers and the casualty identification and EHR matching service.   
     
     
         3 . The system of  claim 2 , further comprising:
 a blockchain enabled trust pathway established directly between the one or more EHR service providers and the mobile computing device of the EMS provider when the consensus of the identified casualty, the one or more EHR service providers, and the EMS provider are established.   
     
     
         4 . The system of  claim 3 , wherein the blockchain enabled trust pathway is configured to transmit the corresponding EHR from the one or more EHR service providers to the mobile computing device of the EMS provider. 
     
     
         5 . The system of  claim 1 , wherein the consensus comprises:
 an emergency condition exemption received from the EMS provider.   
     
     
         6 . The system of  claim 5 , further comprising:
 a blockchain enabled trust pathway established between the EHR service provider, the casualty identification and EHR matching service, and the mobile computing device of the EMS provider.   
     
     
         7 . The system of  claim 6 , wherein the blockchain enabled trust pathway is configured to transmit the corresponding EHR from the one or more EHR service providers to the mobile computing device of the EMS provider. 
     
     
         8 . The system of  claim 1 , wherein the RPMS is configured to utilize a webhook, that, upon receipt of the identification, pushes a notification to the one or more EHR service providers, broadcasting a user defined callback to communicate one or more of a push notification, a query, or a request, to a server of the one or more EHR service providers. 
     
     
         9 . The system of  claim 8 , further comprising:
 a database repository containing a plurality of EHR records, the database repository affiliated with the one or more EHR service providers; and   responsive to the webhook, the one or more servers of the EHR service providers initiate a query of the database repository to determine the existence the corresponding EHR.   
     
     
         10 . The system of  claim 9 , wherein the webhook broadcasts a patient identifier corresponding to the identified casualty. 
     
     
         11 . The system of  claim 1 , further comprising:
 an application program interface (API) on the server hosting the casualty identification and EHR matching service configured to receive a POST request from the server of the one or more EHR service providers, the POST request providing an indication of the existence of the corresponding EHR, wherein   when a corresponding EHR exists, the POST request provides information to request the corresponding EHR from a custodian of the EHR; and   when a corresponding EHR does not exist, the POST request returns a null result.   
     
     
         12 . A computer program product stored on a non-transitory computer storage medium comprising machine-readable program code for causing, when executed, a computer to perform the following process steps:
 receiving an identification of a casualty, at a first server hosting a casualty identification and electronic health record (EHR) matching service;   automatically querying a second server hosted by one or more electronic health record (EHR) service providers to determine an existence of a corresponding EHR matching the casualty; and   determining, via a blockchain trusted identification module (BTIM), a consensus between the casualty, an emergency medical services (EMS) provider, and the one or more EHR service providers.   
     
     
         13 . The computer program product of  claim 12 , the process steps further comprising:
 establishing a blockchain enabled trust pathway between the one or more EHR service providers and the EMS provider when the consensus is established.   
     
     
         14 . The computer program product of  claim 13 , the process steps further comprising:
 transmitting the corresponding EHR from the one or more EHR service providers to the EMS provider via the blockchain enabled trust pathway.   
     
     
         15 . The computer program product of  claim 14 , the process steps further comprising:
 when the consensus comprises:
 a first blockchain trust contract between the casualty and the casualty identification and EHR matching service; and 
 a second blockchain trust contract between the one or more EHR service providers and the casualty identification and EHR matching service; 
 establishing the blockchain enabled trust pathway directly between the EHR service provider and the EMS provider; and 
   when the consensus comprises:
 an emergency condition exemption received from the EMS provider, 
 establishing the blockchain enabled trust pathway between the EHR service provider, the casualty identification and EHR matching service, and the EMS provider. 
   
     
     
         16 . A method of automatically matching an electronic health record (EHR) to an identified casualty, comprising:
 receiving an identification of a casualty, at a first server hosting a casualty identification and electronic health record (EHR) matching service;   automatically querying a second server hosted by one or more electronic health record (EHR) service providers to determine an existence of a corresponding EHR matching the casualty; and   determining, via a blockchain trusted identification module (BTIM), a consensus between the casualty, an emergency medical services (EMS) provider, and the one or more EHR service providers.   
     
     
         17 . The method of  claim 16 , the process steps further comprising:
 establishing a blockchain enabled trust pathway between the one or more EHR service providers and a mobile computing device of the EMS provider when the consensus is established.   
     
     
         18 . The method of  claim 17 , further comprising:
 transmitting the corresponding EHR from the one or more EHR service providers to the mobile computing device of the EMS provider via the blockchain enabled trust pathway.   
     
     
         19 . The method of  claim 17 , the process steps further comprising:
 when the consensus comprises:
 a first blockchain trust contract between the casualty and the casualty identification and EHR matching service; and 
 a second blockchain trust contract between the one or more EHR service providers and the casualty identification and EHR matching service; 
 establishing the blockchain enabled trust pathway directly between the EHR service provider and the EMS provider; and 
   when the consensus comprises:
 an emergency condition exemption received from the EMS provider, 
 establishing the blockchain enabled trust pathway between the EHR service provider, the casualty identification and EHR matching service, and the mobile computing device of the EMS provider.