Systems and methods to track entities for reunification using an emergency response system

Abstract

Systems and methods are provided for implementing entity tracking for reunification. One system (100) includes an electronic processor (300) configured to receive a first data packet including a first identifier of a first entity7 involved with the event and a first dataset describing the first entity involved with the event. The electronic processor (300) may be configured to ingest the first data packet into a database (317) specific to the event. The electronic processor (300) may be configured to receive a second data packet including a second identifier of the first entity involved with the event and a second dataset describing the first entity7 involved with the event. The electronic processor (300) may be configured to determine that the second data packet pertains to the first entity of the first entity profile based on a correlation between the first dataset and the second dataset.

Description

Attorney Docket No.182543.00004 SYSTEMS AND METHODS TO TRACK ENTITIES FOR REUNIFICATION USING AN EMERGENCY RESPONSE SYSTEM CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application No. 63 / 553,355, filed February 14, 2024, the entire contents of which is incorporated herein by reference. BACKGROUND

[0002] Occurrences of emergency incidents or events, such as, e.g., shootings, natural disasters, or other mass-casualty events, have increased in recent years. In the aftermath of such events, family members of victims are often left in emotional distress as they attempt to determine the status of individuals that may or not be affected by the incident. This often leads to frantic attempts by families to locate victims through ad-hoc methods, such as, e.g., the posting of photos, phone calls to hospitals, and the like. Victim reunification is a problem not only for victims and their family, but also for first responder agencies. Previous attempts at automating victim tracking and reunification after such an event are unsatisfactory in a number of respects. For example, such systems are generally difficult to navigate and fail to include effective methods for matching individuals at the scene with information provided by families. Furthermore, some systems lack an easy-to-use entry point for families to use after an incident has occurred.

[0003] The discussion above is merely provided for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter. SUMMARY

[0004] Various aspects of the present disclosure relate generally, to emergency response systems and, in some instances, to systems and methods that facilitate reunification of victims and families after, e.g., a mass-casualty event.

[0005] Existing tracking systems used in large scale disasters and mass casualty incidents may be specific to tracking patients for medical treatment. For instance, upon arrival at a hospital, a medical treatment of a victim may be internally tracked, such as, e.g., as a medical treatment record that is maintained and accessible by internal hospital staff. Such internal- hospital “tracking” generally focuses on medical condition tracking, medical treatment tracking, etc. internal to the hospital. Such systems do not include a reunification component such that victims may be reunited with family (or other loved ones). For instance, such systems cannot be implemented to request victim information from the public (e.g., solicit information from family members on missing loved ones). Rather, such systems are generally hospital 1 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 treatment focused and not public facing (e.g., unavailable for public assess, interaction, or inspection) as such information may be considered protected health information (PHI). As such, existing tracking systems are not conducive to reunification of disaster victims with family members. Furter, existing systems are limited in interoperable capabilities, which impact responders, such as, e.g., law enforcement, fire, emergency medical services (EMS), medical examiners, or hospital systems.

[0006] As such, the technology disclosed herein allows victim tracking (or matching) such that victims may be reunited with loved ones in an efficient and effective manner with improved accuracy. In some examples, the technology disclosed here may specifically capture physical traits and photographs of victims, where such physical traits may not necessarily be (or otherwise be related to) medical information of that victim. The technology disclosed herein may implement artificial intelligence (AI) techniques in order to match victims with information provided by family members (e.g., physical traits and photographs of victims provided by family members). Contact information provided by the family members may then be utilized to facilitate the reunification of the victim with the family members.

[0007] In some configurations, the technology disclosed herein provides a system. The system may include one or more electronic processors. The one or more electronic processors may be configured to receive, from a first computing device at a location associated with an event, a first data packet including a first identifier of a first entity involved with the event and a first dataset describing the first entity involved with the event. The one or more electronic processors may be configured to ingest the first data packet into a database specific to the event, the database may include a plurality of entity profiles compiled using information collected at the location associated with the event. The plurality of entity profiles may include a first entity profile based on the first data packet. The one or more electronic processors may be configured to receive, from a second computing device, a second data packet including a second identifier of the first entity involved with the event and a second dataset describing the first entity involved with the event. The one or more electronic processors may be configured to determine that the second data packet pertains to the first entity of the first entity profile based on a correlation between the first dataset and the second dataset. The one or more electronic processors may be configured to retrieve, from the database, at least a portion of the first dataset. The one or more electronic processors may be configured to generate a notification that may include the at least a portion of the first dataset. The one or more electronic processors 2 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 may be configured to transmit the notification to a third computing device based on information included in the second dataset.

[0008] In some examples, the one or more electronic processors may be configured to: generate interactive content related to the event, the interactive content to, when interacted with, facilitate creation of entity profiles associated with the event.

[0009] In some examples, the interactive content may be a quick response (QR) code that, when interacted with, facilitates navigation to a platform, the platform to create entity profiles associated with the event.

[0010] In some examples, the second computing device may be located at a location different than the location of the first computing device.

[0011] In some examples, the at least a portion of the first dataset may include contact information. In some examples, the one or more electronic processors may transmit the notification to the third computing device using the contact information.

[0012] In some examples, the first identifier may include a name of the first entity. In some examples, the first dataset may include at least one of: a health status of the first entity; a present location of the first entity; or a photograph of the first entity captured subsequent to the event.

[0013] In some examples, the second identifier may include a name of the first entity. In some examples, the second dataset may include at least one of: a photograph of the first entity captured prior to the event; one or more health characteristics of the first entity; or one or more physical traits of the first entity.

[0014] In some examples, the one or more electronic processors may be configured to: responsive to a determination that the second data packet pertains to the first entity, update the first entity profile in the database to indicate the correlation between the second data packet and the first entity profile.

[0015] In some examples, the third computing device may be the second computing device.

[0016] In some examples, the at least a portion of the first dataset may include a location of the first entity. The notification may indicate the location of the first entity.

[0017] In some examples, the location of the first entity may be a reunification center located at a different location than the event.

[0018] In some examples, the first dataset may include a first photograph of the first entity captured subsequent to the event and the second dataset may include a second photograph of the first entity captured prior to the event. In some examples, the one or more electronic processors may be configured to: apply a machine learning model to the first photograph and 3 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 the second photograph in order to determine whether the second data packet pertains to the first entity of the first entity profile. The machine learning model may be a facial recognition model.

[0019] In some examples, the first identifier may be a first instance of a name of the first entity and the second identifier may be a second instance of the name of the first entity. In some examples, the one or more electronic processors may be configured to: determine that the second data packet pertains to the first entity when: the first instance of the name is the same as the second instance of the name; or the first instance of the name is a variation of the second instance of the name.

[0020] In some examples, the first dataset may include first biometric data for the first entity and the second dataset may include second biometric data for the first entity. The one or more electronic processors may be configured to: determine that the second data packet pertains to the first entity based on a comparison of the first biometric data and the second biometric data, the comparison may indicate a correlation between the first biometric data and the second biometric data.

[0021] In some configurations, the technology disclosed herein provides a method. The method may include receiving, with one or more electronic processors, from a first computing device at a location associated with an event, a first data packet including a first identifier of a first entity involved with the event and a first dataset describing the first entity involved with the event. The method may include ingesting, with the one or more electronic processors, the first data packet into a database specific to the event, the database may include a plurality of entity profiles compiled using information collected at the location associated with the event. The plurality of entity profiles may include a first entity profile based on the first data packet. The method may include receiving, with the one or more electronic processors, from a second computing device, a second data packet including a second identifier of the first entity involved with the event and a second dataset describing the first entity involved with the event. The method may include determining, with the one or more electronic processors, that the second data packet pertains to the first entity of the first entity profile based on an association between the first dataset and the second dataset. The method may include, responsive to determining that the second data packet pertains to the first entity, updating, with the one or more electronic processors, the first entity profile in the database to indicate the association between the second data packet and the first entity profile.

[0022] In some examples, the method may include: retrieving, with the one or more electronic processors, from the database, at least a portion of the first dataset; generating, with 4 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 the one or more electronic processors, a notification that includes the at least a portion of the first dataset; and transmitting, with the one or more electronic processors, via a communications network, the notification to a third computing device based on information included in the second dataset.

[0023] In some examples, the method may include: generating a second notification, the second notification may facilitate collection of information related to one or more entities involved in the event; and transmitting the second notification to a publicly accessible platform such that the second notification is publicly accessible. The second computing device may be configured to provide the second data packet responsive to the second notification.

[0024] In some configurations, the technology disclosed herein provides a non-transitory computer readable medium storing instructions that, when executed by one or more electronic processors, may cause the one or more electronic processors to perform operations including: receiving, from a first computing device at a location associated with an event, a first data packet including a first identifier of a first entity involved with the event and a first dataset describing the first entity involved with the event; ingesting the first data packet into a database specific to the event, the database to include a plurality of entity profiles compiled using information collected at the location associated with the event, where the plurality of entity profiles may include a first entity profile based on the first data packet; receiving, from a second computing device, a second data packet including a second identifier of the first entity involved with the event and a second dataset describing the first entity involved with the event; determining that the second data packet pertains to the first entity of the first entity profile based on an association between the first dataset and the second dataset; responsive to determining that the second data packet pertains to the first entity, updating the first entity profile in the database to indicate the association between the second data packet and the first entity profile; retrieving, from the database, at least a portion of the first dataset; generating a notification that may include the at least a portion of the first dataset; and transmitting, via a communications network, the notification to a third computing device based on information included in the second dataset.

[0025] In some examples, the non-transitory computer readable medium may store instructions that, when executed by one or more electronic processors, may cause the one or more electronic processors to perform operations including: generating a quick response (QR) code that, when interacted with, facilitates navigation to a platform, the platform to create entity profiles associated with the event. 5 QB\182543.00004\94719804.1Attorney Docket No.182543.00004

[0026] In some examples, determining that the second data packet pertains to the first entity of the first entity profile may include determining that the second data packet pertains to the first entity based on at least one of: a comparison of the first identifier and the second identifier; a correlation between first biometric data of the first dataset and second biometric data of the second dataset; or application of a machine learning model configured to perform facial recognition with respect to a first photograph of the first dataset and a second photograph of the second dataset. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The following drawings are provided to help illustrate various features of examples of the disclosure and are not intended to limit the scope of the disclosure or exclude alternative implementations.

[0028] FIG. 1 schematically illustrates a system for implementing entity tracking for reunification according to some examples.

[0029] FIG. 2 schematically illustrates an example user device according to some examples.

[0030] FIG.3 schematically illustrates an example server according to some examples.

[0031] FIG. 4 is a flowchart illustrating a method implementing entity tracking for reunification according to some examples.

[0032] FIG. 5 illustrates an example user interface that provides an administrative dashboard in accordance with some configurations.

[0033] FIG.6 illustrates an example user interface for creating an incident or event record in accordance with some configurations.

[0034] FIG. 7 illustrates an example user interface that includes interactive content to facilitate collection of contributor-entered information in accordance with some configurations.

[0035] FIG. 8 illustrates an example user interface for collecting contributor-entered information in accordance with some configurations.

[0036] FIG. 9 illustrates an example user interface for collecting agency-related information in accordance with some configurations.

[0037] FIG. 10 illustrates an example user interface for collecting agency-related information in accordance with some configurations.

[0038] FIG. 11 illustrates an example user interface that provides entity profiles based on agency-entered information and contributor-entered information in accordance with some configurations. 6 QB\182543.00004\94719804.1Attorney Docket No.182543.00004

[0039] FIG. 12 illustrates an example user interface that includes an entity match in accordance with some configurations.

[0040] FIG.13 illustrates an example user interface an entity match dashboard that depicts various entity match information in accordance with some configurations.

[0041] FIG.14 illustrates an example user interface that includes a geographical map view of reunification centers and an entity match summary portion in accordance with some configurations.

[0042] FIG. 15 illustrates an example user interface that depicts an interaction with a reunification center included in a geographical map view that results in the display of additional information with respect to the interacted with reunification center.

[0043] FIG.16 illustrates an example user interface that includes a geographical map view of reunification centers and an entity match summary portion in accordance with some configurations. DETAILED DESCRIPTION OF THE PRESENT DISCLOSURE

[0044] The disclosed technology is not limited in its application to the details of construction and the arrangement of components set forth in the following description or illustrated in the following drawings. Other examples of the disclosed technology are possible and examples described and / or illustrated here are capable of being practiced or of being carried out in various ways.

[0045] A plurality of hardware and software-based devices, as well as a plurality of different structural components can be used to implement the disclosed technology. In addition, examples of the disclosed technology can include hardware, software, and electronic components or modules that, for purposes of discussion, can be illustrated and described as if the majority of the components were implemented solely in hardware. However, in at least one example, the electronic based aspects of the disclosed technology can be implemented in software (for example, stored on non-transitory computer-readable medium) executable by at least one processor. Although certain drawings illustrate hardware and software located within particular devices, these depictions are for illustrative purposes only. In some examples, the illustrated components can be combined or divided into separate software, firmware, hardware, or combinations thereof. As one example, instead of being located within and performed by a single electronic processor, logic and processing can be distributed among multiple electronic processors. Regardless of how they are combined or divided, hardware and software 7 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 components can be located on the same computing device or can be distributed among different computing devices connected by at least one network or other suitable communication link.

[0046] FIG. 1 illustrates a system 100 for implementing entity tracking for reunification with an emergency response system according to some examples. As illustrated in the example of FIG.1, the system 100 can include a contributor platform 105, a reunification center platform 110, an agency platform 115, and a reunification system 120. In some examples, the system 100 can include fewer, additional, or different components in different configurations than illustrated in FIG. 1. For example, as illustrated, the system 100 includes one contributor platform 105, one reunification center platform 110, one agency platform 115, and one reunification system 120. However, in some examples, the system 100 can include fewer or additional contributor platforms 105, reunification center platforms 110, agency platforms 115, reunification systems 120, or a combination thereof. As another example, components of the system 100 can be combined into a single device or platform (e.g., the contributor platform 105 and the reunification center platform 110), divided among multiple devices or platforms, or a combination thereof.

[0047] The contributor platform 105, the reunification center platform 110, the agency platform 115, and the reunification system 120 can communicate over wired or wireless communication networks 130. Portions of the communication networks 130 can be implemented using a wide area network, such as the Internet, a local area network, such as a Bluetooth™ network or Wi-Fi, and combinations or derivatives thereof. In some examples, the communication network 130 represents a direct wireless link between two components (or platforms) of the system 100 (e.g., via a Bluetooth™ or Wi-Fi link). Alternatively, or in addition, in some examples, two or more components (or platforms) of the system 100 can communicate through an intermediary device (or platform) of the communication network 130 not illustrated in FIG.1.

[0048] The contributor platform 105 may be associated with one or more contributing entities. As used herein, a contributing entity may include an entity (e.g., an organization or individual) having a relationship or an interest in locating an entity involved in the event (e.g., for reunification with that entity). For example, a contributing entity may be a family member or loved one of an entity involved in the event.

[0049] The contributor platform(s) 105 may include one or more computing devices (also referred to herein as “contributor computing device(s)”). The contributor computing device(s) may be a user device, such as, e.g., a desktop computer, a laptop computer, a tablet computer, 8 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 an all-in-one computer, a notebook computer, a terminal, a smart telephone, a smart television, a smart speaker, a smart imaging device, a communications device, or another suitable computing device that interfaces with a user. In some configurations, the contributor computing device(s) are mobile or portable computing devices, such as, e.g., a cellular phone, a tablet computer, a laptop computer, etc. As described in greater detail herein, the contributor computing devices may be utilized for off-premises (off-site or remote) data collection related to an event (or entity involved therewith). For example, upon being informed as to the occurrence of an event, a contributor entity may utilize a contributor computing device to provide information or data related to an entity involved in the event (e.g., a family member, a loved one, a friend, etc.). Accordingly, in some instances, the contributor platform(s) 105) may be public-input platforms that facilitate the collection of information or data from the public. In some examples, the information collected via the contributor computing device(s) may be referred to as contributor-entered information.

[0050] Contributor-entered information may include information related to an entity involved in the event (e.g., an entity in which the contributor is seeking reunification with). Contributor-entered information may include information related to the contributor, the entity involved in the event, etc. For example, the contributor-entered information may include contact information (e.g., a name, an email address, an address, a home number, a fax number, a social media handle, etc.), a list of family members, a gender, a number of dependents under 18, a date of birth, a list of medical conditions that may involve medical assistance, a list of medications, an indication of housing or shelter information, a list of assistance services (e.g., mental health, spiritual, religious, etc.), long-term assistance information (e.g., financial, clothing, food or dietary, transportation, etc.), disability or access information (e.g., ASL, hearing aids, vision, wheelchair, walker, stimulus, sensory, smell, etc.), animal care information (e.g., type, location, etc.), information regarding whether any family members were involved in the event or are still missing (e.g., number of family members, name(s), age(s), relation, last known location, medical information, photograph(s), etc.), etc.

[0051] The reunification center platform 110 may be associated with (or otherwise include) one or more reunification centers 125. The reunification center(s) 125 may be a designated location at which treatment, reunification, or other actions related to an incident may occur. The reunification center(s) 125 may be remote from a location at which an event occurred. For example, the reunification center(s) 125 may be located at a different location than a location of the event. Alternatively, in some instances, the reunification center(s) 125 may be proximate 9 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 to or at a location at which an event occurred. For example, the reunification center(s) 125 may be located at or nearby the location of the event (e.g., a parking lot of a building, where the event occurred within the building). In some instances, the reunification center(s) 125 may be temporary, such as, e.g., a tent. Alternatively, in some instances, the reunification center(s) 125 may be permanent (or semi-permanent), such as, e.g., a hospital, a park pavilion, a medical clinic, an agency facility (e.g., a police department, a fire department, etc.), etc.

[0052] The reunification center platform(s) 110 may include one or more computing devices (also referred to herein as “reunification center computing device(s)”). The reunification center computing device(s) may be a user device, such as, e.g., a desktop computer, a laptop computer, a tablet computer, an all-in-one computer, a notebook computer, a terminal, a smart telephone, a smart television, a smart speaker, a smart imaging device, a communications device, or another suitable computing device that interfaces with a user. In some configurations, the reunification center computing device(s) are mobile or portable computing devices, such as, e.g., a cellular phone, a tablet computer, a laptop computer, etc. As described in greater detail herein, the reunification center computing device(s) may be utilized for collecting information or data related to the event, an entity involved in the event, or the like at the reunification center(s) 125. In some examples, the information collected via the reunification center computing device(s) may be referred to as reunification center-entered information. The reunification center-entered information may be collected (or otherwise provided) via reunification center entities, such as, e.g., medical personnel, volunteers, contributors, other users located at the reunification center(s) 125, etc.

[0053] The agency platform(s) 115 may be associated with one or more agency entities (or individuals thereof). As used herein, an agency entity may include an entity that responds to (or otherwise services) events or incidents as described herein. An agency entity may be, e.g., a police department, a fire department, an emergency medical service (EMS), the federal bureau of investigation (FBI), another type of law enforcement agency, another type of public safety agency, another type of first responder agency, etc. As used herein, an agency entity may refer to an individual belonging to the agency entity (e.g., a police officer) or may refer to the agency entity as a whole (e.g., the police department).

[0054] The agency platform(s) 115 may include one or more computing devices (also referred to herein as “agency computing device(s)” or “first responder computing device(s)”). The agency computing device(s) may be a user device, such as, e.g., a desktop computer, a laptop computer, a tablet computer, an all-in-one computer, a notebook computer, a terminal, 10 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 a smart telephone, a smart television, a smart speaker, a smart imaging device, a communications device, or another suitable computing device that interfaces with a user. In some configurations, the agency computing device(s) are mobile or portable computing devices, such as, e.g., a cellular phone, a tablet computer, a laptop computer, etc. As described in greater detail herein, the agency computing devices may be utilized for on-premises (or on- site) data collection related to an event. For example, an agency entity (e.g., a first responder entity) may respond to an event with an agency computing device and collect information or data related to the event using the agency computing device. In some examples, the information collected via the agency computing device may be referred to as agency-entered information.

[0055] Agency-entered information may be in various forms or formats, such as, e.g., audio data, image data, text data, etc. For example, the agency-entered information may be text-based (e.g., text), audio-based (e.g., an audio recording), image-based (e.g., a video, an image, etc.), etc. Accordingly, in some configurations, the agency-entered information may include a photograph of an entity involved in the event (e.g., a photograph captured subsequent to the event occurring). Alternatively, or in addition, in some instances, the agency-entered information may include biometric data related to an entity involved in the event, such as, e.g., a DNA sample (e.g., a blood sample, a saliva sample, a hair sample, etc.), a retinal scan, an iris scan, a fingerprint, a voice recording, another type of DNA sample, etc. In some examples, the agency-entered information may include multiple different forms or formats of information. As one example, the agency-entered information may include a photograph of an entity involved in the event (e.g., image data), a blood sample (e.g., biometric data), and an audio recording (e.g., audio data).

[0056] Agency-entered information may include information related to the event itself, an entity involved in the event, etc. An entity involved in the event may include, e.g., a witness to the event, a victim of the event, etc. Agency-entered information may include, e.g., witness statements or interviews, information related to the entity involved in the event, etc. For example, the agency-entered information may include, e.g., a name, a phone number, an email address, an injury query (e.g., “were you injured” query (yes / no)), an assistance services query (e.g., “would you like follow-up victim assistance services, such as mental health, religious, spiritual, etc.” query (yes / no)), a location-based query (e.g., “where were you located during the event” query (text or audio recording options)), an observation query (e.g., “what did you see” query (text and audio recording options)), etc. 11 QB\182543.00004\94719804.1Attorney Docket No.182543.00004

[0057] In some configurations, the agency-entered information may include triage information. An agency entity may flag (or otherwise indicate) a triage classification for an entity involved in the event. A triage classification may rank an importance or relevancy of an entity involved in the event or information related to the entity involved in the event. For example, in some configurations, the triage classification may indicate whether the entity involved in the event is a “key” witness, a “tertiary” witness, a “suspicious” witness, etc. The agency entity collecting the information from the entity involved in the event may determine, based on the provided information, a triage classification for that entity. Accordingly, in some configurations, the agency-entered information may include a triage classification, a reason for the triage classification, etc.

[0058] Agency-entered information may include any relevant information or data determined at the site (or within proximity) of the event by, e.g., a first responder (e.g., an agency entity). In some examples, the agency-entered information may include, e.g., an identity of the agency entity collecting the agency-entered information, a type of event that occurred (e.g., a mass shooting, a natural disaster, a transportation accident, a terrorist attack, a bombing or explosion, a vehicle-ramming attack, an industrial accident, a radiological or nuclear event, etc.), a status of the event (e.g., developing, on-going, contained, neutralized, etc.), etc.

[0059] The reunification system 120 may implement an emergency medical system to track entities involved in an event for reunification according to some configurations. As described in greater detail herein, the reunification system 120 may facilitate the tracking of entities involved in an event such that those entities may be reunited with family members or loved ones (e.g., contributors). As illustrated in FIG. 1, the reunification system 120 may include a server 150, which is described in greater detail herein. Although not illustrated in FIG. 1, in some configurations, the reunification system 120 may include one or more computing devices as described herein (e.g., reunification system computing device(s)). In some examples, the reunification system computing device(s) may be utilized by reunification system entities that manage or maintain the reunification system 120 or services thereof.

[0060] FIG. 2 schematically illustrates an example computing device 200 in accordance with some configurations herein. The computing device 200 of FIG.2 may be an example of the agency computing device(s), the contributor computing device(s), the reunification center computing device(s), the reunification system computing device(s), or another device or component of the system 100. 12 QB\182543.00004\94719804.1Attorney Docket No.182543.00004

[0061] The computing device 200 can include, e.g., a desktop computer, a laptop computer, a tablet computer, an all-in-one computer, a notebook computer, a terminal, a smart telephone, a smart television, a smart speaker, a smart imaging device, a communication device, a smart wearable, or another suitable computing device that interfaces with a user. As described in greater detail herein, the computing device 200 may be used by a user for tracking entities involved in an event, such as, e.g., providing information or data related to the event, one or more entities involved in the event, etc. As one example, when the computing device 200 is utilized by an agency entity (as an agency computing device), the computing device 200 may be used to collect agency-entered information, as described herein. As another example, when the computing device 200 is utilized by a contributor entity (as a contributor computing device), the computing device 200 may be used to collect contributor-entered information, as described herein. As yet another example, when the computing device 200 is utilized by a reunification center entity (as a reunification center computing device), the computing device 200 may be used to collect reunification center-entered information, as described herein.

[0062] As illustrated in FIG.2, the computing device 200 may include a device electronic processor 202, a device memory 205, a device communication interface 210, and a human- machine interface (“HMI”) 215. The device electronic processor 202, the device memory 205, the device communication interface 210, and the HMI 215 can communicate wirelessly, over at least one communication line or bus, or a combination thereof. The computing device 200 can include additional, different, or fewer components than those illustrated in FIG. 2 in various configurations. The computing device 200 can perform additional functionality other than the functionality described herein. Also, the functionality (or a portion thereof) described herein as being performed by the computing device 200 can be performed by another component (e.g., a remote computing device, another computing device, or a combination thereof), distributed among multiple computing devices (e.g., as part of a cloud service or cloud-computing environment), combined with another component (e.g., a remote computing device, another computing device, another component of the system 100, or a combination thereof), or a combination thereof.

[0063] The device communication interface 210 can include a transceiver that communicates with one or more components of the contributor platform(s) 105, the reunification center platform(s) 110, the reunification system 120 (e.g., the server 150), another device of the system 100, another device external or remote to the system 100, or a combination thereof over the communication network 130 and, optionally, at least one other communication 13 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 network or connection. The device electronic processor 202 may include a microprocessor, an application-specific integrated circuit (ASIC), or another suitable electronic device for processing data, and the device memory 205 may include a non-transitory, computer-readable storage medium. The device electronic processor 202 is configured to retrieve instructions and data from the device memory 205 and execute the instructions.

[0064] For example, as illustrated in FIG. 2, the device memory 205 may store a reunification application 230. The reunification application 230 is a software application executable by the device electronic processor 202 in the example illustrated and as specifically discussed herein, although a similarly purposed module can be implemented in other ways in other examples. In some configurations, the reunification application 230 may be a dedicated software application locally stored in the device memory 205 of the computing device 200. The reunification application 230 (when executed by the device electronic processor 202) may enable or facilitate entity tracking for reunification related to an occurrence of an incident or event in accordance with the technology disclosed herein. As one example, the reunification application 230 (when executed by the device electronic processor 202) may facilitate the capture and transmission of information or data related to the event, entities involved in the event, etc. (e.g., the agency-entered information, the reunification center-entered information, the contributor-entered information, etc.). As another example, in some configurations, the reunification application 230 (when executed by the device electronic processor 202) may facilitate generation and transmission of interactive content, alerts, or notifications related to an occurrence of the event, as described in greater detail herein. Accordingly, the reunification application 230 (when executed by the device electronic processor 202) may enable or facilitate functionality (or a portion thereof) described herein as being performed by the computing device 200.

[0065] The device memory 205 may include additional, different, or fewer components in different configurations than illustrated in FIG. 2. Alternatively, or in addition, in some configurations, components of the device memory 205 may be combined into a single component, distributed among multiple components, or the like. Alternatively, or in addition, in some configurations, a component of the device memory 205 may be stored remotely from the computing device 200, or, in a remote database, another server, a remote computing device, an external storage device, or the like.

[0066] As noted herein, in some instances, the functionality (or a portion thereof) described herein as being performed by the computing device 200 can be performed by another 14 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 component (e.g., a remote computing device, another computing device, or a combination thereof), distributed among multiple computing devices (e.g., as part of a cloud service or cloud-computing environment), combined with another component (e.g., a remote computing device, another computing device, another component of the system 100, or a combination thereof), or a combination thereof. For example, in some instances, the reunification application 230 may be stored and executed by another component, distributed among multiple computing devices, combined with another component, or a combination thereof.

[0067] As illustrated in FIG. 2, the computing device 200 can also include the HMI 215 for interacting with a user. The HMI 215 can include at least one input device, at least one output device, or a combination thereof. Accordingly, in some examples, the HMI 215 allows a user to interact with (e.g., provide input to and receive output from) the computing device 200. For example, the HMI 215 can include a keyboard, a cursor-control device (e.g., a mouse), a touch screen, a scroll ball, a mechanical button, a display device (e.g., a liquid crystal display (“LCD”)), a printer, a speaker, a microphone, an image sensor or camera, or a combination thereof.

[0068] In the illustrated example of FIG. 2, the HMI 215 includes at least one display device 240 (referred to herein collectively as “the display devices 240” and individually as “the display device 240”). The display device 240 can provide (or output) a media signal or content to a user. As one example, the display device 240 can display a user interface (e.g., a graphical user interface (GUI)) associated with the reunification application 230. The display device 240 can be included in the same housing as the computing device 200 or can communicate with the computing device 200 over a wired or wireless connection. As one example, the display device 240 can be a touchscreen included in a cellular phone, a smart wearable, a laptop computer, a tablet computer, a smart speaker, another type of portable smart device, etc. As another example, the display device 240 can be a monitor, a television, or a projector coupled to a terminal, desktop computer, or the like via a cable.

[0069] As noted above, with reference to FIG.1, the reunification system 120 may include the server 150. The server 150 may be a computing device, such as computing device 200. The server 150 may host or otherwise provide at least one platform or environment that implements or facilitates entity tracking for reunification related to an occurrence of an event, as described herein. Accordingly, in some examples, the server 150 is associated with an emergency response system or platform that facilitates entity tracking for reunification (e.g., the reunification system 120 or services provided thereby). Alternatively, or in addition, in some 15 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 examples, the functionality (or a portion thereof) described herein as being performed by the computing device 200 may be locally performed by the server 150.

[0070] As illustrated in FIG. 3, the server 150 may include an electronic processor 300, a memory 305, and a communication interface 310. The electronic processor 300, the memory 305, and the communication interface 310 can communicate wirelessly, over a communication line or bus, or a combination thereof. The server 150 can include additional, different, or fewer components than those illustrated in FIG. 3 in various configurations. The server 150 can perform additional functionality other than the functionality described herein. Also, the functionality (or a portion thereof) described herein as being performed by the server 150 can be performed by another component, distributed among multiple computing devices (e.g., as part of a cloud service or cloud-computing environment), combined with another component, or a combination thereof.

[0071] The communication interface 310 can include a transceiver that communicates with one or more computing device(s) (e.g., the computing device 200 of FIG.2) of the contributor platform(s) 105, the reunification center platform(s) 110, the agency platform(s) 115, another component of the system 100, another device external or remote to the system 100, or a combination thereof over the communication network 130 and, optionally, at least one other communication network or connection. The electronic processor 300 may include a microprocessor, an ASIC, or another suitable electronic device for processing data, and the memory 305 may include a non-transitory, computer-readable storage medium. The electronic processor 300 is configured to retrieve instructions and data from the memory 305 and execute the instructions.

[0072] As illustrated in FIG.3, the memory 305 may include an entity tracking application 315 (referred to herein as “the application 315”). The application 315 may be a software application executable by the electronic processor 300 in the example illustrated and as specifically discussed below, although a similarly purposed module can be implemented in other ways in other examples. The electronic processor 300 can execute the application 315 to implement or otherwise facilitate tracking one or more entities involved in an event. In some examples, the electronic processor 300 may track entities based on information or data provided via the contributor platform(s) 105, the reunification center platform(s) 110, the agency platform(s) 115, etc., as described in greater detail herein. Alternatively, or in addition, in some configurations, the electronic processor 300 may execute the application 315 to 16 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 generate and provide a notification regarding an occurrence of an event, as described in greater detail herein.

[0073] In some configurations, the memory 305 may include one or more profile database(s) 317, which may store one or more entity profiles 320. An entity profile 320 may be associated with (or otherwise correspond to) an entity involved in the event. For instance, each entity involved in the event may be associated with a specific entity profile. An entity profile 320 may include an identifier and a dataset. The identifier may identify (or otherwise indicate) an entity associated with the entity profile 320. For example, the identifier may include, e.g., a name, an account number, etc., for the entity associated with the entity profile 320. The dataset may include information or data related to the entity associated with the entity profile 320. In some configurations, the dataset may include (or otherwise be based on), e.g., the agency-entered information, the reunification center-entered information, etc. As one specific example, when an agency entity collects information from an entity involved in the event (as the agency-entered information), the electronic processor 300 may generate an entity profile for that entity, where the entity profile may include a name of the entity as an identifier and the agency-entered information as the dataset.

[0074] In some configurations, the entity profile(s) 320 may be updated or modified such as, e.g., when additional or new information or data is collected for the corresponding entity. As one example, agency-entered information for an entity may be collected at a location of the event by an agency entity and that agency-entered information may be used to generate an entity profile for the entity. Following this example, after the entity is transported to a reunification center 125 (e.g., a hospital), staff at the reunification center 125 may collect additional information related to the entity (e.g., reunification center-entered information). The reunification center-entered information may be added (e.g., augmented or supplemented) to the entity profile for that entity. For instance, in some cases, the entity profile for that entity may be updated to include a present (or current) location of the entity (e.g., the reunification center 125 in which the entity was transported to).

[0075] As illustrated in FIG.3, in some configurations, the memory 305 may also include a learning engine 365. In some configurations, the learning engine 365 develops one or more models using an artificial intelligence (AI) or machine learning function, algorithm, or model. Machine learning functions are generally functions that allow a computer application to learn without being explicitly programmed. In particular, the learning engine 365 is configured to develop a model based on training data. As one example, to perform supervised learning, the 17 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 training data includes example inputs and corresponding desired (for example, actual) outputs, and the learning engine 365 progressively develops a model that maps inputs to the outputs included in the training data. As another example, to perform self-supervised learning (“SSL”), a model is trained on a task using the data itself to generate supervisory signals (e.g., unlabeled training data), rather than relying on, e.g., external labels provided by a user (e.g., labeled training data). As yet another example, to perform semi-supervised learning, the training data may include desired output values for a subset of the training data (e.g., labeled training data) while the remaining training data may be unlabeled or imprecisely labeled (e.g., unlabeled training data). Machine learning performed by the learning engine 365 may be performed using various types of methods and mechanisms including but not limited to decision tree learning, association rule learning, artificial neural networks, inductive logic programming, support vector machines, clustering, Bayesian networks, reinforcement learning, representation learning, similarity and metric learning, sparse dictionary learning, and genetic algorithms. These approaches allow the learning engine 365 to ingest, parse, and understand data and progressively refine models.

[0076] In some configurations, the learning engine 365 may develop one or more models configured to be implemented or otherwise facilitate the entity tracking functionality, as described herein. For instance, in some configurations, the learning engine 365 may develop a profile matching or recognition model that is specifically trained (or developed) to identify entity matches. For instance, the entity profile 320 may include a first entity profile associated with a first entity. Responsive to receipt of a second entity profile, the machine learning model may be configured to determine whether the first entity profile and the second entity profile relate to (or are associated with) the same entity. As one example, the learning engine 365 may develop a facial recognition model that matches entities based on facial features or characteristics. For instance, when the first entity profile includes a photograph of an entity and the second entity profile includes a photograph of an entity, the facial recognition model may determine whether or not the photographs depict the same (or substantially similar) entity, such that, the first entity profile and the second entity profile are likely related to the same entity.

[0077] Accordingly, in some configurations, the learning engine 365 may develop a model, such as, e.g., a convolutional neural network (CNN), that performs feature-based matching using distinctive features extracted from images (or photographs), where matches are determined by matching distinctive features across different images (or photographs). For instance, a feature-based matching model may identify one or more features or points (e.g., 18 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 edges, corners, textures, colors, etc.) in image(s) (e.g., photographs), such that, e.g., a “fingerprint” of each photograph is generated for comparison with other images (or fingerprints thereof) to identify matches.

[0078] As noted herein, the server 150 (or component(s) thereof) can include additional, different, or fewer components than those illustrated in FIG.3 in various configurations. Also, the functionality (or a portion thereof) described herein as being performed by the server 150 (or component(s) thereof) can be performed by another component (e.g., a remote computing device, another computing device, or a combination thereof), distributed among multiple computing devices (e.g., as part of a cloud service or cloud-computing environment), combined with another component (e.g., a remote computing device, another computing device, another component of the system 100, or a combination thereof), or a combination thereof. For example, in some instances, the entity tracking application 315, the profile database 317 (or entity profile(s) 320 thereof), the learning engine 365, the model database 370, or a combination thereof may be stored and executed by another component (e.g., either local to the server 150 or external to the server 150 , such as, e.g., the computing device(s) 200), distributed among multiple computing devices, combined with another component, or a combination thereof.

[0079] FIG.4 is a flowchart illustrating a method 400 for implementing entity tracking for reunification according to some examples. The method 400 is described as being performed by the server 150 and, in particular, the electronic processor(s) 300 executing at least one of the entity tracking application 315, the learning engine 365, the models of the model database 370, etc. However, as noted above, the functionality described with respect to the method 400 can be performed by other devices, such as one or more of the computing devices 200, another remote server or computing device, another component of the system 100, or a combination thereof, or distributed among a plurality of devices, such as a plurality of servers included in a cloud service (e.g., a web-based service executing software or applications). Further, although generally described as being performed by a processor (e.g., the electronic processor 300), this processor may include multiple processors (e.g., as apart of a distributed processor system or group of cooperating processors).

[0080] As illustrated in FIG.4, the method 400 may include receiving, with the electronic processor 300, a first data packet (at block 405). The first data packet may be received from a computing device at a location associated with the event (e.g., an agency computing device). 19 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 The first data packet may include an identifier of the entity involved with the event, a dataset describing the entity involved with the event, or a combination thereof.

[0081] The electronic processor 300 may ingest the first data packet into a database specific to the event (at block 410). In some configurations, the database specific to the event may be the profile database 317. As such, in some instances, the profile database 317 may be specific to an event. The database specific to the event (e.g., the profile database 317) may include one or more entity profiles compiled using information collected at the location associated with the event (e.g., the entity profile(s) 320, as described herein).

[0082] In some configurations, the electronic processor 300 may receive multiple data packets (e.g., as similarly described herein with respect to block 405), each data packet may be specific to a particular entity involved in the event. In such configurations, the electronic processor 300 may ingest each data packet (e.g., as similarly described herein with respect to block 410) into the database specific to the event (e.g., the profile database 317).

[0083] The electronic processor 300 may receive, from a second computing device, a second data packet (at block 415). In some configurations, the second computing device may be at a location different than the location of the first computing device (e.g., the location at which the event occurred). The second computing device may be a contributor computing device, as described herein. As such, in some configurations, the second data packet (e.g., as received at block 415) may be associated with contributor-entered information. For instance, the second data packet may include a dataset specific to an entity involved in the event that the contributor wants to reunite with (or otherwise track). In some instances, data packets received from contributor computing devices may represent a request to match information included in (or otherwise associated with) the data packet to an existing entity profile (e.g., one of the entity profiles 320). As one example, receipt of a data packet from a contributor computing device may represent a request to track an entity associated with the data packet (e.g., as identified by an identifier of the data packet, as described by the dataset of the data packet, or a combination thereof).

[0084] In some configurations, the electronic processor 300 may generate and transmit a public notification regarding the occurrence of the event. Such public notification may inform the public (e.g., the contributor(s)) that the event occurred, facilitate receipt of contributor- entered information, etc. In some examples, the second data packet may be provided responsive to such a public notification. For example, in some configurations, the electronic processor 300 may generate interactive content related to the event. When the interactive content is interacted 20 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 with (e.g., by a contributor computing device) the interactive content may facilitate creation of entity profiles associated with the event (e.g., the receipt or collection of second data packets, or the contributor-entered information). In some configurations, the interactive content may be a quick response (QR) code that, when interacted with, facilitates navigation to a platform (e.g., the reunification application 230) to create entity profiles associated with the event (e.g., to provide contributor-entered information).

[0085] Accordingly, in some configurations, the electronic processor 300 may generate a notification to facilitate collection of information related to one or more entities involved in the event (e.g., the contributor-entered information). The electronic processor 300 may then transmit the notification to a publicly accessible platform (e.g., the reunification application 230, a social media platform, etc.). Alternatively, or in addition, in some configurations, the notification may be published via another approach, such as, e.g., printed flyers, phone calls, etc.

[0086] As illustrated in FIG. 4, the electronic processor 300 may determine whether the second data packet pertains to an entity associated with one of the entity profiles 320. For instance, in some configurations, the electronic processor 300 may attempt to detect (or identify) an entity match between the second data packet and one of the entity profile(s) 320 (e.g., the data packets associated therewith), in order to determine, e.g., whether both the second data packet and one of the entity profile(s) 320 relate to the same entity.

[0087] In some configurations, the electronic processor 300 may determine whether the second data packet pertains to an entity associated with one of the entity profiles 320 using one or more of the models developed by the learning engine 365. For instance, when an entity profile 320 includes a photograph of a corresponding entity and the second data packet includes a photograph of a corresponding entity, the electronic processor 300 may provide the photographs to a facial recognition model in order to determine whether the photographs are of the same (or substantially similar) entity.

[0088] Alternatively, or in addition, in some configurations, the electronic processor 300 may determine whether the second data packet pertains to an entity associated with one of the entity profiles 320 based on an overlap or similarities with respect to the datasets, the identifiers, or a combination thereof. In some instances, the electronic processor 300 may utilize one or more confidence thresholds or criteria when determining an entity match. For example, when an amount or degree of overlap or similarity satisfies a threshold (e.g., five physical features overlap, one type of DNA sample matches, etc.), the electronic processor 300 21 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 may determine an entity match. However, when the amount or degree of overlap does not satisfy a threshold (e.g., one physical feature overlaps), the electronic processor 300 may not determine an entity match.

[0089] As one example, the electronic processor 300 may determine a match between the second data packet and an entity profile based on an overlap or similarities with respect to an identifier of the second data packet and an identifier of the entity profile (e.g., when both identifiers include the same name). As one specific example, when the identifier of the entity profile 320 is a first instance of a name of a first entity and the second identifier of the second data packet is a second instance of a name of the first entity, the electronic processor 300 may determine that the second data packet pertains to the first entity (e.g., an entity match) when the first instance of the name is the same as the second instance of the name or the first instance of the name is a variation of the second instance of the name.

[0090] As another example, the electronic processor 300 may determine a match between the second data packet and an entity profile based on an overlap or similarities with respect to a dataset (or portion thereof) of the second data packet and a dataset (or portion thereof) of the entity profile. As one specific example, when both datasets indicate the same home address and telephone number, the electronic processor 300 may determine a match. As another specific example, when both datasets indicate similar physical features or attributes (e.g., height, weight, gender, eye color, hair color, age, etc.), the electronic processor 300 may determine a match. As yet another example, the electronic processor 300 may determine a match based on a correlation between the biometric data (e.g., fingerprint match, DNA match, etc.).

[0091] Accordingly, the electronic processor 300 may determine whether the second data packet pertains to the same entity as one of the first data packet (e.g., the entity profile based on the first data packet received at block 405). In some configurations, the electronic processor 300 may determine that the second data packet pertains to the same entity as the first data packet (e.g., the entity profile based on the first data packet received at block 405). However, in some configurations, the electronic processor 300 may determine that the second data packet does not pertain to the same entity as the first data packet.

[0092] In some examples, responsive to a determination that the second data packet pertains to the first entity, the electronic processor 300 may update the first entity profile in the profile database 317 to indicate the correlation between the second data packet and the first entity profile (e.g., to link or otherwise indicate the match). 22 QB\182543.00004\94719804.1Attorney Docket No.182543.00004

[0093] In some configurations, when the electronic processor 300 determines a match, the electronic processor 300 may retrieve, from the profile database 317, at least a portion of the first dataset (e.g., of the matching entity profile) (at block 425). In some instances, the electronic processor 300 may retrieve information describing the entity, such as, e.g., a health status, a present (or current) location, or other information as described herein.

[0094] The electronic processor 300 may generate a notification based on the at least a portion of the first dataset (at block 430). In some examples, the notification may include the at least a portion of the first dataset, such as, e.g., a location of the entity, a health status of the entity, etc.

[0095] The electronic processor 300 may transmit the notification (at block 435). In some configurations, the electronic processor 300 may transmit the notification based on the at least a portion of the first dataset, based on at least a portion of the second dataset, or a combination thereof. In some examples, the at least a portion of the first dataset or the second dataset may include contact information for a point of contact related to the entity, the contributor of the second data packet, etc. As such, in some instances, the electronic processor 300 may utilize the contact information when transmitting the notification. The notification may be transmitted to a computing device 200 based on the at least a portion of the first dataset or the second dataset. In some cases, the computing device 200 that receives the notification may be a computing device 200 of the contributor, another entity, or a combination thereof.

[0096] FIGS.5-16 are example user interfaces related to the technology disclosed herein.

[0097] FIG. 5 illustrates an example user interface 500 that provides a dashboard (or landing page) of the reunification application 230. In some configurations the user interface 500 may be generated specific to a role of a user accessing the user interface 500. For exmaple, when a first responder is accessing the user interface 500, the user interface 500 may be different than when an administrative entity of the reunification system 120 (e.g., via a reunification system computing device) is accessing the user interface 500. In some instances, the user interface 500 may include additional, different, or fewer components based on a role (e.g., a first responder, an administrative entity, etc.) of a user accessing the user interface 500.

[0098] As illustrated in FIG. 5, the user interface 500 may include a set of interactive components 505 that, when interacted with, may facilitate various functions. For instance, as illustrated in FIG.5, the user interface 500 may include a “New Incident” component 505A, a “Match Victims” component 505B, a “Connect Victims” component 505C, a “Family Reunification” component 505D, and a “Victim Map” component 505E. A user may interact 23 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 with the “New Incident” component 505A to generate (or otherwise create) a new incident (or event). A user may interact with the “Match Victims” component 505B to review victim matches, as described in greater detail herein. A user may interact with the “Connect Victims” component 505C to connect matched victims with contributors (e.g., family members), as described in greater detail herein. A user may interact with the “Family Reunification” component 505D to review family reunification related information (e.g., whether a victim has been matched, whether a contributor matched with a victim has been contacted, etc.), as described in greater detail herein. A user may interact with the “Victim Map” component 505E to access a victim map, as described in greater detail herein.

[0099] As also illustrated in FIG. 5, the user interface 500 may include a listing of active incidents (represented in FIG. 5 by reference numeral 515). In some instances, each active incident included in the list of active incidents 515 may be interactive such that, when a respective active incident is interacted with by a user (e.g., clicked-on), the user may be navigated to (or otherwise provided with) a user interface specific to the interacted with active incident.

[0100] FIG. 6 illustrates an example user interface 600 for creating an incident or event record (e.g., a new incident or event) in accordance with some configurations. In some configurations, the user interface 600 may be generated (or otherwise provided) responsive to a user interaction with the “New Incident” component 505A of the user interface 500 of FIG. 5. As illustrated in FIG.6, the user interface 600 may prompt a user for information related to the new incident (represented in FIG. 6 by reference numeral 605), such as, e.g., an Incident Name 610, an Incident Address615, an Active status 620, etc. After providing the information related to the new incident, a user may interact with (e.g., click-on or otherwise select) a Save button 625. Interaction with the Save button 625 may save (or otherwise) generate the new incident.

[0101] FIG. 7 illustrates an example user interface 700 that includes interactive content 705 for display on a contributor computing device 710 (e.g., the computing device 200) to facilitate collection of contributor-entered information in accordance with some configurations. As described in greater detail herein, the interactive content 705 may be published (or otherwise provided) to solicit contributor-entered information by facilitating navigation to a platform (e.g., the reunification application 230) to create entity profiles associated with an event (e.g., to provide contributor-entered information). In the example of FIG. 7, the user interface 700 may include a QR code (as the interactive content 705). 24 QB\182543.00004\94719804.1Attorney Docket No.182543.00004

[0102] FIG. 8 illustrates an example user interface 800 for collecting contributor-entered information in accordance with some configurations. In some configurations, the user interface 800 may be provided responsive to interaction with the interactive content 705 of FIG.7. In the example of FIG. 8, the user interface 800 may include one or more input components 805 for providing contributor-entered information. For example, the user interface 800 may include a Primary Language input component 805A that may receive a primary language selection of the contributor. The user interface 800 may include a First Name input component 805B and a Last Name input component 805C that may receive a first name and last name of the contributor, respectively. The user interface 800 may include a Photo input component 805D that may receive a photograph of the contributor. The user interface 800 may include an Email input component 805E that may receive an email of the contributor. The user interface 800 may include a Phone Number input component 805F that may receive a phone number of the contributor.

[0103] FIG. 9 illustrates an example user interface 900 for collecting agency-related information that includes an input field 905 for selecting an incident or event in accordance with some configurations. In some configurations, the user interface 900 may be utilized by an agency entity to provide agency-related information (e.g., as described herein with respect to block 415 of FIG. 4). The agency entity may interact with the input field 905 to select an incident.

[0104] FIG. 10 illustrates an example user interface 1000 for collecting agency-related information in accordance with some configurations. In some configurations, the user interface 1000 may be generated (or otherwise provided) responsive to a selection from the input field 905 of the user interface 900. In the example of FIG.10, the user interface 1000 may include a set of input components 1005 for inputting agency-related information (e.g., victim information), including, e.g., a location address 1010, a victim first name 1015, a victim last name 1020, a victim status 1025, a reunification restriction 1030, a gender 1035, an approximate age 1340, an approximate weight 1345, etc. Responsive to receiving the agency- related information (e.g., using the user interface 1000), an entity profile may be generated based on the agency-related information, as described in greater detail herein.

[0105] FIG.11 illustrates an example user interface 1100 that provides entity profiles based on agency-entered information 1105 and contributor-entered information 1110 in accordance with some configurations. In some configurations, the user interface 1100 may be generated (or otherwise provided) responsive to an interaction with the “Match Victims” component 25 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 505B of the user interface 500 of FIG.5. In some configurations, the user interface 1100 may be utilized by an administrative entity of the reunification system 120 to review entity matches (e.g., as described herein with respect to block 420 of FIG. 4). IN some instances, an administrative entity may review entity matches in order to confirm the entity match, deny the entity match, etc. Alternatively, or in addition, in some configurations, the user interface 1100 may be utilized by an administrative entity of the reunification system 120 to manually identify entity matches. For instance, as illustrated in the example of FIG.11, the user interface 1100 may include a set of filtering components 1120, which enable filtering of entity profiles.

[0106] FIG. 12 illustrates an example user interface 1200 that includes an entity match 1205 in accordance with some configurations. In some configurations, the user interface 1200 may be generated (or otherwise provided) as part of an entity match review process (e.g., as performed by an administrative entity of the reunification system 120). In some configurations, the user interface 1200 may allow the administrative entity to confirm that the contributor associated with the entity match was contacted (represented in FIG. 12 by reference numeral 1210). In some configurations, the user interface 1200 may be generated (or otherwise provided) responsive to an interaction with the “Connect Victims” component 505C.

[0107] FIG.13 illustrates an example user interface 1300 as an entity match dashboard that depicts various entity match information in accordance with some configurations. In some configurations, the user interface 1300 may provide an indication of whether the associated entity profile was matched (represented in FIG. 13 by reference numeral 1305), an indication of whether the associated entity profile was connected with a contributor (represented in FIG. 13 by reference numeral 1310), and an indication of whether the associated entity profile was reunified with the contributor (represented in FIG. 13 by reference numeral 1315). In some configurations, each entity profile may be displayed with a corresponding photograph of the entity profile (represented in FIG.13 by reference numeral 1320). Alternatively, or in addition, in some configurations, each entity profile may be displayed with associated entity information, such as, e.g., a victim name, a gender, a medical status, etc. (represented in FIG.13 by reference numeral 1325).

[0108] FIG.14 illustrates an example user interface 1400 that includes a geographical map view (represented in FIG.14 by reference numeral 1405) of reunification centers (represented in FIG. 14 by reference numeral 1410) and an entity match summary portion 1420 in accordance with some configurations. In some instances, the reunification centers 1410 may be represented by an indicator. The indicator may have one or more properties representative 26 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 of a number of victims at the corresponding reunification center 1410. As one example, the indicator may be displayed in a color based on the number of victims (e.g., a red color, which may indicate a large number of victims, a yellow color, which may indicate a moderate number of victims, or a green color, which may indicate a low number of victims). As another example, a size of the indicator may indicate (or otherwise) represent a number of victims at the corresponding reunification center 1410 (e.g., a larger indicator may indicate a larger number of victims while a smaller indicator may indicate a smaller number of victims). In some configurations, the user interface 1400 may be generated (or otherwise provided) responsive to an interaction with the “Victims Map” component 505C.

[0109] FIG.15 illustrates an example user interface 1500 that depicts an interaction with a reunification center (represented in FIG. 15 by reference numeral 1505) included in a geographical map view 1510 that results in the display of additional information with respect to the interacted with reunification center (represented in FIG.15 by reference numeral 1515). In the example of FIG. 15, the additional information may include a listing of victims at the corresponding reunification center. The listing of victims may include information for each victim, such as, e.g., a name, a health status, a photograph, etc.

[0110] FIG.16 illustrates an example user interface 1600 that includes a geographical map view 1605 of reunification centers 1610 and an entity match summary portion 1615 in accordance with some configurations. In some configurations, the entity match summary portion 1615 may be generated (or otherwise provided) responsive to an interaction with a corresponding reunification center 1610 via the geographical map view 1605.

[0111] In some examples, aspects of the technology, including computerized implementations of methods according to the technology, can be implemented as a system, method, apparatus, or article of manufacture using standard programming or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a processor device (e.g., a serial or parallel processor chip, a single- or multi-core chip, a microprocessor, a field programmable gate array, any variety of combinations of a control unit, arithmetic logic unit, and processor register, and so on), a computer (e.g., a processor device operatively coupled to a memory), or another electronically operated controller to implement aspects detailed herein. Accordingly, for example, examples of the technology can be implemented as a set of instructions, tangibly embodied on a non-transitory computer-readable media, such that a processor device can implement the instructions based upon reading the instructions from the computer-readable media. Some examples of the technology can include 27 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 (or utilize) a control device such as an automation device, a computer including various computer hardware, software, firmware, and so on, consistent with the discussion below. As specific examples, a control device can include a processor, a microcontroller, a field- programmable gate array, a programmable logic controller, logic gates etc., and other typical components that are known in the art for implementation of appropriate functionality (e.g., memory, communication systems, power sources, user interfaces and other inputs, etc.).

[0112] Certain operations of methods according to the technology, or of systems executing those methods, can be represented schematically in the FIGS. or otherwise discussed herein. Unless otherwise specified or limited, representation in the FIGS. of particular operations in particular spatial order can not necessarily require those operations to be executed in a particular sequence corresponding to the particular spatial order. Correspondingly, certain operations represented in the FIGS., or otherwise disclosed herein, can be executed in different orders than are expressly illustrated or described, as appropriate for particular examples of the technology. Further, in some examples, certain operations can be executed in parallel, including by dedicated parallel processing devices, or separate computing devices configured to interoperate as part of a large system.

[0113] As used herein in the context of computer implementation, unless otherwise specified or limited, the terms “component,” “system,” “module,” “block,” and the like are intended to encompass part or all of computer-related systems that include hardware, software, a combination of hardware and software, or software in execution. For example, a component can be, but is not limited to being, a processor device, a process being executed (or executable) by a processor device, an object, an executable, a thread of execution, a computer program, or a computer. By way of illustration, both an application running on a computer and the computer can be a component. A component (or system, module, and so on) can reside within a process or thread of execution, can be localized on one computer, can be distributed between two or more computers or other processor devices, or can be included within another component (or system, module, and so on).

[0114] Also as used herein, unless otherwise limited or defined, “or” indicates a non- exclusive list of components or operations that can be present in any variety of combinations, rather than an exclusive list of components that can be present only as alternatives to each other. For example, a list of “A, B, or C” indicates options of: A; B; C; A and B; A and C; B and C; and A, B, and C. Correspondingly, the term “or” as used herein is intended to indicate exclusive alternatives only when preceded by terms of exclusivity, such as “either,” “one of,” 28 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 “only one of,” or “exactly one of.” Further, a list preceded by “one or more” (and variations thereon) and including “or” to separate listed elements indicates options of one or more of any or all of the listed elements. For example, the phrases “one or more of A, B, or C” and “at least one of A, B, or C” indicate options of: one or more A; one or more B; one or more C; one or more A and one or more B; one or more B and one or more C; one or more A and one or more C; and one or more of each of A, B, and C. Similarly, a list preceded by “a plurality of” (and variations thereon) and including “or” to separate listed elements indicates options of multiple instances of any or all of the listed elements. For example, the phrases “a plurality of A, B, or C” and “two or more of A, B, or C” indicate options of: A and B; B and C; A and C; and A, B, and C. In general, the term “or” as used herein only indicates exclusive alternatives (e.g., “one or the other but not both”) when preceded by terms of exclusivity, such as “either,” “one of,” “only one of,” or “exactly one of.”

[0115] Although the present technology has been described by referring to preferred examples, workers skilled in the art will recognize that changes can be made in form and detail without departing from the scope of the discussion. 29 QB\182543.00004\94719804.1

Claims

Attorney Docket No.182543.00004 CLAIMS What is claimed is:

1. A system (100), the system (100) comprising: one or more electronic processors (300) configured to: receive, from a first computing device (200) at a location associated with an event, a first data packet including a first identifier of a first entity involved with the event and a first dataset describing the first entity involved with the event; ingest the first data packet into a database (317) specific to the event, the database (317) to include a plurality of entity profiles (320) compiled using information collected at the location associated with the event, wherein the plurality of entity profiles (320) includes a first entity profile based on the first data packet; receive, from a second computing device (200), a second data packet including a second identifier of the first entity involved with the event and a second dataset describing the first entity involved with the event; determine that the second data packet pertains to the first entity of the first entity profile based on a correlation between the first dataset and the second dataset; retrieve, from the database (317), at least a portion of the first dataset; generate a notification that includes the at least a portion of the first dataset; and transmit the notification to a third computing device (200) based on information included in the second dataset.

2. The system (100) of claim 1, wherein the one or more electronic processors (300) are configured to: generate interactive content related to the event, the interactive content to, when interacted with, facilitate creation of entity profiles associated with the event.

3. The system (100) of claim 2, wherein the interactive content is a quick response (QR) code (700) that, when interacted with, facilitates navigation to a platform, the platform to create entity profiles associated with the event.

4. The system (100) of claim 1, wherein the second computing device (200) is located at a location different than the location of the first computing device (200). 30 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 5. The system (100) of claim 1, wherein the at least a portion of the first dataset includes contact information, wherein the one or more electronic processors (300) transmit the notification to the third computing device using the contact information.

6. The system (100) of claim 1, wherein the first identifier includes a name of the first entity; and wherein the first dataset includes at least one of: a health status of the first entity; a present location of the first entity; or a photograph of the first entity captured subsequent to the event.

7. The system (100) of claim 1, wherein the second identifier includes a name of the first entity; and wherein the second dataset includes at least one of: a photograph of the first entity captured prior to the event; one or more health characteristics of the first entity; or one or more physical traits of the first entity.

8. The system (100) of claim 1, wherein the one or more electronic processors (300) are configured to: responsive to a determination that the second data packet pertains to the first entity, update the first entity profile in the database (317) to indicate the correlation between the second data packet and the first entity profile.

9. The system (100) of claim 1, wherein the third computing device (200) is the second computing device.

10. The system (100) of claim 1, wherein the at least a portion of the first dataset includes a location of the first entity, and wherein the notification indicates the location of the first entity.

11. The system (100) of claim 10, wherein the location of the first entity is a reunification center (125) located at a different location than the event. 31 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 12. The system (100) of claim 1, wherein the first dataset includes a first photograph of the first entity captured subsequent to the event and the second dataset includes a second photograph of the first entity captured prior to the event; and wherein the one or more electronic processors (300) are configured to: apply a machine learning model to the first photograph and the second photograph in order to determine whether the second data packet pertains to the first entity of the first entity profile, wherein the machine learning model is a facial recognition model.

13. The system (100) of claim 1, wherein the first identifier is a first instance of a name of the first entity and the second identifier is a second instance of the name of the first entity; and wherein the one or more electronic processors (300) are configured to: determine that the second data packet pertains to the first entity when: the first instance of the name is the same as the second instance of the name; or the first instance of the name is a variation of the second instance of the name.

14. The system (100) of claim 1, wherein the first dataset includes first biometric data for the first entity and the second dataset includes second biometric data for the first entity; and wherein the one or more electronic processors (300) are configured to: determine that the second data packet pertains to the first entity based on a comparison of the first biometric data and the second biometric data, the comparison to indicate a correlation between the first biometric data and the second biometric data.

15. A method (400), the method (400) comprising: receiving, with one or more electronic processors (300), from a first computing device (200) at a location associated with an event, a first data packet including a first identifier of a first entity involved with the event and a first dataset describing the first entity involved with the event; 32 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 ingesting, with the one or more electronic processors (300), the first data packet into a database (317) specific to the event, the database (317) to include a plurality of entity profiles (320) compiled using information collected at the location associated with the event, wherein the plurality of entity profiles (320) includes a first entity profile based on the first data packet; receiving, with the one or more electronic processors (300), from a second computing device (200), a second data packet including a second identifier of the first entity involved with the event and a second dataset describing the first entity involved with the event; determining, with the one or more electronic processors (300), that the second data packet pertains to the first entity of the first entity profile based on an association between the first dataset and the second dataset; and responsive to determining that the second data packet pertains to the first entity, updating, with the one or more electronic processors (300), the first entity profile in the database (317) to indicate the association between the second data packet and the first entity profile.

16. The method (400) of claim 15, further comprising: retrieving, with the one or more electronic processors (300), from the database (317), at least a portion of the first dataset; generating, with the one or more electronic processors (300), a notification that includes the at least a portion of the first dataset; and transmitting, with the one or more electronic processors (300), via a communications network, the notification to a third computing device (200) based on information included in the second dataset.

17. The method (400) of claim 15, further comprising: generating, with the one or more electronic processors (300), a second notification, the second notification to facilitate collection of information related to one or more entities involved in the event; and transmitting, with the one or more electronic processors (300), the second notification to a publicly accessible platform such that the second notification is publicly accessible, wherein the second computing device (200) is configured to provide the second data packet responsive to the second notification. 33 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 18. A non-transitory computer-readable medium (305) storing instructions that, when executed by one or more electronic processors, cause the one or more electronic processors (300) to perform operations comprising: receiving, from a first computing device (200) at a location associated with an event, a first data packet including a first identifier of a first entity involved with the event and a first dataset describing the first entity involved with the event; ingesting the first data packet into a database (317) specific to the event, the database (317) to include a plurality of entity profiles (320) compiled using information collected at the location associated with the event, wherein the plurality of entity profiles (320) includes a first entity profile based on the first data packet; receiving, from a second computing device (200), a second data packet including a second identifier of the first entity involved with the event and a second dataset describing the first entity involved with the event; determining that the second data packet pertains to the first entity of the first entity profile based on an association between the first dataset and the second dataset; responsive to determining that the second data packet pertains to the first entity, updating the first entity profile in the database (317) to indicate the association between the second data packet and the first entity profile; retrieving, from the database (317), at least a portion of the first dataset; generating a notification that includes the at least a portion of the first dataset; and transmitting, via a communications network (130), the notification to a third computing device (200) based on information included in the second dataset.

19. The computer-readable medium (305) of claim 18, further comprising: generating a quick response (QR) code (705) that, when interacted with, facilitates navigation to a platform, the platform to create entity profiles associated with the event.

20. The computer-readable medium (305) of claim 18, wherein determining that the second data packet pertains to the first entity of the first entity profile includes determining that the second data packet pertains to the first entity based on at least one of: a comparison of the first identifier and the second identifier; 34 QB\182543.00004\94719804.1Attorney Docket No.182543.00004 a correlation between first biometric data of the first dataset and second biometric data of the second dataset; or application of a machine learning model configured to perform facial recognition with respect to a first photograph of the first dataset and a second photograph of the second dataset. 35 QB\182543.00004\94719804.1

Images