A system and method of managing journey data

Abstract

A system for managing journey data relating to one or more persons, the system comprising: one or more tags, each tag configured to be attached to a person, wherein each tag is further configured to b

Description

Technical Field

[0001] The present application relates to a system and a method of managing data relating to a person. In particular, the present invention relates to a system and methods of recording data relating to persons and enabling access to that information using codes on bands / tags associated with the person. Background

[0002] In an incident, such as a medical emergency, ambulance personnel or the police are usually the first at the scene of an incident. Upon arrival at the scene of the incident, ambulance personnel or the police may need to execute a variety of tasks to deal with the incident. For example, for ambulance personnel such tasks may include performing basic medical tests on persons involved in the incident and regarded as actual or potential patients (e.g. measuring heart rate, blood pressure etc...), taking pictures ofthe patient and / or the surrounding environment, providing emergency medical drugs to the patient, and also monitoring the patient's health during the transportation ofthe patient to the hospital.

[0003] If the patient requires hospital admission, then the treatment ofthe patient will then continue at the hospital, and sometimes, even after the patient has been discharged from the hospital. In all such cases, information about, for example, the details ofthe original incident and any previous treatments received by the patient before being admitted to the hospital is useful in providing fast and effective medical care in the subsequent stages ofthe patient's journey.

[0004] For example, during transit and eventual handover ofthe patient from the ambulance to the hospital, ambulance personnel need to provide as much information as possible about the patient in to order for the hospital personnel to treat the patient as quickly and as effectively as possible. However, since a lot of this information is often communicated orally, it is inevitable that some information will be lost, and will be unavailable to the medical personnel treating the patient at the hospital. Further, even when information is conveyed to the hospital personnel, whether orally or in writing, in practice it is difficult or impossible to link this data to the patient's formal medical records when the identity ofthe patient has been eventually established.

[0005] Additionally, sometimes the patient may require long term medical care after the incident. For example, the patient may require physiotherapy treatment after being treated by the ambulance personnel or after being discharged from the hospital. In such a case, any previous information about the patient (such as the current treatment(s) the patient is currently receiving or has already received) will be useful will assisting the physiotherapist in providing targeted medical care to the patient.

[0006] Current systems for recording data associated with the journey of the patient generally require the use of bespoke hardware, or bespoke software installed on mobile devices, such as tablets, linked to a healthcare provider record system to allow data associated with the patient and / or patient journey data, that is, data associated with the journey of the patient to be inserted by the appropriate personnel to be recorded in the record system. Such systems have a number of problems in practice. It is costly and inconvenient to issue bespoke hardware to the appropriate personnel or to ensure that all personnel have bespoke software loaded and correctly operating on their mobile devices. Further, record systems are usually healthcare provider specific, so that the issued devices or software to communicate with them can only be used with a specific healthcare provider record system, limiting interoperability of the personnel with different healthcare providers, such as different hospitals, which may be required, particularly in emergencies.

[0007] Further, even when the personnel are equipped with the appropriate bespoke hardware or software, it may be difficult and time consuming to transfer data associated with the patient and / or patient journey data recorded for a patient who's identity is unknown to their patient formal medical record when they are identified.

[0008] The embodiments described below are not limited to implementations which solve any or all of the disadvantages of the known approaches described above. Summary

[0009] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter; variants and alternative features which facilitate the working of the claimed subject matter and / or serve to achieve a substantially similar technical effect should be considered as falling into the scope of the claims.

[0010] The invention is defined as set out in the appended set of claims.

[0011] In a first aspect, there is provided a system for managing data relating to one or more persons, the system comprising: one or more tags, each tag configured to be attached to a person, wherein each tag is further configured to be read by a portable hand-held device to provide one or more unique machine-readable codes, wherein the portable hand-held device is connected to the internet; an online repository for storing, editing and / or accessing data relating to the person, wherein the one or more unique machine-readable codes provided by a tag configured to be attached to the person are used to associate the person with the data relating to the person; and a web portal for providing access to the online repository via the portable hand-held device.

[0012] By providing such a system for recording data relating to persons, a record of incident and the treatment provided to the person is created, even if the identity of the person is not yet known. When the identity of the person is eventually established, the recorded information can be married to the persons formal medical records such that a permanent record of the recoded information is created, leading to the provision of faster and more effective healthcare for the person in the subsequent stages or recovery.

[0013] In a second aspect, there is provided a method of managing data relating to a person, the method comprising: associating a tag to a person, wherein the identity of the person is not yet known; scanning the tag using a portable hand-held device to provide a unique machine-readable code to provide access to an online repository via a web portal, wherein the hand-held device is connected to the internet; storing data relating to the person in the online repository such that all the data relating to the person is linked together, wherein the unique machine-readable code is used to associate the person with the data relating to the person stored in the online repository.

[0014] This application acknowledges that firmware and software can be valuable, separately tradable commodities. It is intended to encompass software, which runs on or controls "dumb" or standard hardware, to carry out the desired functions. It is also intended to encompass software which "describes" or defines the configuration of hardware, such as HDL (hardware description language) software, as is issued for designing silicon chips, or for configuring universal programmable chips, to carry out desired functions.

[0015] The features and embodiments discussed herein may be combined as appropriate, as would be apparent to a person skilled in the art, and may be combined with any of the aspects except where it is expressly provided that such a combination is not possible or the person skilled in the art would understand that such a combination is self-evidently not possible. Brief Description of the Drawings

[0016] Embodiments of the present invention are described below, by way of example, with reference to the following drawings.

[0017] Figure 1 is a schematic showing a system for managing data associated with the patient and / or patient journey data according to one embodiment of the present application.

[0018] Figure 2 is a schematic showing a system for managing data associated with the patient and / or patient journey data according to another embodiment of the present application.

[0019] Figure 3 is a schematic showing a method implemented by the system figures 1 or 2.

[0020] Common reference numerals are used throughout the figures to indicate the same or similar features. Detailed Description

[0021] Embodiments of the present invention are described below by way of example only. These examples represent the best mode of putting the invention into practice that are currently known to the Applicant although they are not the only ways in which this could be achieved, the description sets forth the functions of the example and the sequence of operations for constructing and operating the example. However, the same or equivalent functions and sequences may be accomplished by different examples.

[0022] Figure 1 is a schematic depicting a data management system 100 for a person according to one embodiment of the present application. The double arrows indicate connection between the different entities of the system 100. The connection may be, but not limited to, a wireless connection such as that between a tag ora band and a handheld device (see below).

[0023] The system 100 comprises one or more tags or a bands 105. Each tag is configured to be attached to a different person. For example, each tag 105 is configured to be attached a wrist of a person (not shown). In what follows, although the system 100 comprises one or more tags 105, only a single tag 105 of the system 100 will be referred to. In one example, the tag 105 can be attached to any other part of the person as appropriate, or other attaching means can be used, such as a self-adhesive tag attached to the skin of the person. For example, the tag could be attached to the bed of the person. In the illustrated embodiment, the person is a potential or actual patient who may require monitoring and / or treatment. The patient may, for example, be someone who was involved in an accident or other medical emergency, and the tag 105 may be attached to the patient at the scene of the incident by, for example, ambulance personnel who were called to the scene of the incident, for example by the patient or a bystander. In general, the tag 105 may be attached by any personnel who has access to the tag 105. For example, the tag 105 may be attached by a security guard or police at large scale event (such as a football match), where such tags 105 were distributed to security guards and / orthe police attending the event prior to the event taking place.

[0024] Although the person is a patient in the illustrated embodiment, this is not essential. Although the present invention may be used in medical or emergency situations in which a person may require monitoring ortreatment, and so may be regarded as a patient (or potential patient), the invention is not limited to such situations, and may be used for persons in other situations.

[0025] The tag 105 comprises a unique machine-readable code. The unique machine readable code can be provided by an ID tag 122 located within the tag 105. The word "unique" in the present application means that the code is unique at the system level to avoid duplicate entries (i.e. universal uniqueness is not required). In one example, the ID tag 122 is a Quick Response Code (QR code) or a 3-dimensional (3D) barcode. In an alternative example, the ID tag 122 is an electronic device, such as a radio-frequency identification LC based device (LC RFID), a Near Field communication Device (NFC) device and / or a an Ultra-High Frequency radio-frequency identification device (UHF RFID). In some examples, the tag 105 comprises all the aforementioned electronic devices, where each device provides or represents the same unique machine readable code. Additionally, the tag 105 also may also comprise QR code or a 3D barcode in addition to the one or more of the electronic devices where the QR code or the 3D barcode provides or represents the same unique machine readable code as the one or more of the electronic devices present in the tag 105. In the latter case, the tag 105 comprises an optically readable code, and at least electronically (or radio) readable code.

[0026] In some examples, each device within the tag 105 may represent a different unique machine readable code, where each code associated with same profile of the patient in the system 100. For example, a tag 105 may comprise a QR code and a UHF RFID device, both of which represent a different unique machine readable code, but each code would be associated with the same record in the system 100. In another example, the QR code or the 3D code will represent one unique machine readable code, and all the electronics devices will represent a different unique machine readable butthat is common to or the same for all the electronic devices. In yet another example, the tag 105 may represent any number of different machine readable codes from only one unique machine readable code to a maximum number that is equal to the number of ID tags 122 present in the tag 105. In all of the aforementioned cases, the one or more of the unique machine readable codes provided by the tag 105 is associated with same patient profile.

[0027] By providing multiple types of ID tags 122 within the tag 105 representing same unique machine readable code (or different machine readable codes as explained above), the tag 105 can be made readable by a variety of different portable hand-held devices 110. Such portable held-held devices 100 may include, but are not limited to, mobile phones, tablets, and loop aerial scanners, all of which can be integrated into the healthcare system (for example, by registration of the device). For example, a camera of the mobile phone can be used to scan the ID tag 105 such as a QR code to enable access to the repository 120 via the web-portal 115. Accordingly, no other specialist hardware is required to scan the tag 105 other than those mentioned above.

[0028] Once the tag 105 has been securely attached to the patient, the hand-held device 110 can be used by a user of the hand-held device 110 (e.g. ambulance personnel) to scan and read the code provided by the ID tag 122 to provide access to a web-portal 115 (i.e. a dedicated website) via the hand-held device 110. In one example, the user ofthe hand-held device 110 may not be the same person who attached the tag 105 to the patient in the first place. For example, the tag 105 may be attached by a security guard at the event (e.g. to someone falling unconscious at the event), and then the user ofthe hand-held 110 device any be an ambulance personnel who were called at the scene on the incident.

[0029] The web-portal 115 connected to and provides access to an online repository 120, which comprises a plurality of patient profiles associated with different patients (i.e. patient 1 ...n). Each ofthe profiles will comprise data or information associated with the patient and / or patient journey data, that is, data associated with the journey ofthe patient which begins from the time when the tag 105 is attached to the patient. Such data may include any information that relates to the journey of that patient. For example, the ambulance personnel who attend the scene of the incident may record information any information they feel would be necessary in assisting in treatment of the patient in the future. This includes, for example, information about any third parties involved (e.g. other vehicle involved in an accident, the condition of each vehicle involved in the accident), the weather conditions on the day on the incident, photos ofthe surrounding, details of any witnesses involved, the approximate height and weight of the patient, any drugs that were administrated to the patient, any medical tests the patient may have undergone (e.g. measuring heart rate, blood pressure etc...), any other treatment(s) provided to the patient etc. The data stored in the patient profile may have a retention period and would be deleted in time according to local regulations.

[0030] In one example, the user is able to access the web-portal 115 and the online repository via a Graphical User Interface (GUI) of the hand-the device 110, provided the hand-held device 110 is connect to the Internet. Accordingly, no bespoke hardware or additional or specialist software is required to access the online repository 120 using the hand-held device 110.

[0031] Once the user of the hand-held device 110 is provided with the access to the repository, the user can create a new profile for the patient in the online repository 120, or a new profile can be created automatically. Once a profile is created, data associated with the patient and / or patient journey data (as detailed above) can be entered into the profile. This is the case even if the identity of the patient has not yet been formally established (e.g. at the scene of the incident, where instead the priority is to treat the patient or if the patient is unconscious).

[0032] The patient profile and the data associated with the patient and / or patient journey data stored therein are associated with the patient via the unique machine-readable code provided by the ID tag 122 of the tag 105 attached to the patient. Alternatively, if each tag 105 comprises multiples devices each representing multiple unique machine codes (as mentioned above), each code would be associated with the same patient profile and the data stored therein.

[0033] The information stored in such a profile may not be limited to information gathered only at scene of the incident. For example, the journey of the patient may continue if the patient requires further medical treatment in a hospital, and / or requires long term medical care (e.g. physiotherapy or is scheduled for surgery in the near future). Therefore, information stored in the patient profile can be accessed, stored, and / or edited whenever the patient receives any further treatment. Such information can be entered into the patient profile by any authorised person. For example, this may be the physiotherapist, a surgeon, a General Practitioner (GP), or even the patient. Therefore, the system 100 of the resent applications enables all the data associated with the patient and / or patient journey data to be linked together by storing all the data in single place (i.e. in the patient profile in the online repository 120).

[0034] Having access to the information associated with each event of the journey of the patient is vital in providing fast and effective treatment in the subsequent stages. For example, accessing previous information about the patient is useful when the patient is discharged from the hospital or self-discharges from the hospital (because it appears, or the patient believes, that the patient no longer requires any additional treatment), but is re-admitted to the hospital for further treatment or may require the attention of a GP or a physiotherapist because original injury has become worse after a certain period. Another scenario where it could be useful is where the patient is treated by ambulance personnel for only minor injuries, or may not require any treatment at all, and so is not admitted to the hospital when first examined. In this case, the patient may find that the injury becomes worse after a period of time, so that the patient later requires admission to the hospital or requires the attention of a GP.

[0035] Another advantage ofthe system 100 is that once the identity of the patient is eventually established (e.g. afterthe patient is admitted to the hospital), any relevant data from the data associated with or related to the patient and / or the journey of the patient stored in the online repository 120 can readily be combined with the patient's formal medical record in a straightforward manner, such that a permanent record ofthe data stored in the online repository 120 is created. Such relevant data may include data related to any drugs that were administrated to the patient, any medical tests the patient may have undergone (e.g. measuring heart rate, blood pressure etc...), or any other treatment(s) provided to the patient. Therefore, the data that is combined with the patient's formal medical record from the online repository 120 may be a subset ofthe data stored in the online repository 120.

[0036] Another advantage is that since now the data relating to the patient is being recorded during and afterthe incident, all the information about the data associated with or relating to the journey ofthe patient can be conveyed to the hospital personnel (e.g. results of tests performed, any drugs administered to the patient), because information is not lost or miscommunicated during handover of the patient from the ambulance to the hospital personnel.

[0037] Additionally, associating one or more unique machine codes ofthe tag 105 attached to the patient to the patient profile in the above manner is also useful when multiple users of the handheld device 110 are attending the patient simultaneously. For example, because the tag 105 provides a unique machine code or multiple machine readable codes that are associated with the same patient profile, different medical personnel are able to store, edit and / or access data located in the correct patient profile at the same time.

[0038] In an example, a user of the hand-held device 110 is provided, bythe web-portal 115, with only read-only access to the data relating to the patient stored in the online repository 120. For example, this could be when the user scans tag 105 with a hand-held device 110 that is configured to only read a 3D barcode located within the tag 105. There may be security measures implemented to enable read-only access to the data. For example, the user may be prompted to provide a user PIN to enable access. Additionally, a user of the hand-held device 110 is able to store and / or edit the data relating to the patient in the online repository 120. This could be, for example, when the user scans the tag 105 with a hand-device 110 that is configured read a LC RFID, a NFC device or an UHF RFID located within the tag 105. Like before, there may be security measures implemented to enable the user to store and / or edit the data. The security measures implemented for storing and / editing data may be more than what is required to provide read-only access. For example, the user may be prompted to provide a user PIN and also biometric data to store and / or edit data stored in the online repository 120. Accordingly, the user is provided with different privileges depending on the type of ID tag 122 being scanned. It is understood that any one ofthe different types of codes can be used to provide read-only access, and any one ofthe different types of codes can be used to provide storing and / editing privileges.

[0039] In yet another example, the data being stored and / or edited in the online repository 120 is time-tagged. This enables the anyone accessing the data later to know exactly when a particular incident occurred or when a particular treatment was provided to the patient (e.g was it in a field, ambulance or in a hospital).

[0040] In one example, the hand-held device 110 and the web-portal 115 are configured to enable downloading of the unique machine-readable code associated with the tag 105 into the handheld device 110 itself. The hand-held device 110 and the web-portal 115 are further configured to enable downloading the data relating to the patient into the hand-held device 110, using the unique machine-readable code. This this manner, users can access the data even when the hand-held device 110 is not connected to the internet.

[0041] Figure 2 is a schematic depicting yet another embodiment of the system 200 of the present application. The system 200 comprises all the features of the system 100, but in addition comprises software in the form of a secure application 125 installed within the hand-held device 110. The application 125 is configured to authenticate the identity of the responder attending or providing treatment to the patient, before storing and / or editing the data associated with the patient and / or patient journey data in the online repository 120. Such authentication can be achieved, for example, via a passcode, biometric data, or a certification code using the multi-factor authentication, or a combination thereof. For example, when the data needs to be stored and / or edited in the online repository 120, the tag 105 is scanned by the hand-held device 110, and the application prompts the responder to enter the required details to authenticate the identity of the responder. The responder that can provide the required details (e.g. enter a passcode etc.) to authentic his / her identity. If the correct details are provided, the application 125 provides access to the online repository 120 via the web-portal 115 to enable storing and / or editing the data located therein. In one example, the responder can be a user of the hand-held device 110.

[0042] In one example, the web-portal 115 itself is configured to authenticate the identity of the responder, such that the application 125 does not need to be installed to the hand-held device 110. One advantage of this is that the application 125 enables the first responders to use their personal smartphones as a hand-held device 110. This could be useful when, for example when a major incident has occurred and many medical personnel from different hospitals are required not all of them having access dedicated hand-held device 110 integrated within the system 100 or 200 (i.e. not all of them having access to a work smartphone).

[0043] In another example, the web-portal 120 is configured to store, together with the data associated with the patient and / or the journey of the patient, data associated with the identity of the responder in the online repository 120 (e.g. inside the patient profile of the patient being attended by the responder). The data associated with the identity of the responder can include, for example, the name, registration number and / or other personal details of the userthat can identify the responder. The identity of the responder can be stored in the online repository 120, for example, when storing and / or editing the data associated with patient and / or the journey of the patient. In one example, the data provided by the responder during authentication (i.e. by either using the application 125 or the webportal 115) can be used as a source of the data associated with the identity of the responder.

[0044] In yet another example, the tag 105 also comprises location tracking device 123. The location tracking device may comprise a Global Positioning System (GPS) or Global System for Mobile communications (GSM) 124. The GPS or GSM 124 is configured to generate location data corresponding to the location of the tag 105 attached to the patient. The web-portal 115 is configured to store the location data generated by the GPS or GSM 124, together with the data associated with the patient and / or patient journey data , in the online repository 120 when storing and / or editing the data associated with the patient and / or patient journey data . By combining the location data, the data associated with the identity of the responder, and the data related to time provided by the time-tagging, anyone able to access the data associated with the patient and / or patient journey data in the online repository 120 can identify exactly who provided the treatment to the patient, and at what time and location. Alternatively, the tag 105 may not comprise a GPS or GSM 124, and the location tracking capabilities of the hand-held device 110 may be utilised instead. For example, if the hand-held device 110 is a mobile phone, the GPS system of the mobile phone can be used to generate location data corresponding to the location of the handheld device 110 when the tag 105 is read by the hand-held device 110. In this case, the location data generated by the hand-held device 110 will also correspond to the location of the tag 105 read by the hand-held device 110. The location data from the GPS system of the mobile device can then be stored together with the data related to the patient journey in the patient profile.

[0045] Alternatively, or in addition to the GPS or GSM 124, the tag 105 may comprise a RFID device 125. The RDIF device 125 is configured to work together with RFID scanners that may be located at various positions within the hospital to provide the location data of the patient. For example, when the patient is moved pass one of the scanners, the RFID device 125 on the tag 105 also moves pass the scanner, and so location of the patient is recorded. In this manner, the patient location can be accurately tracked within the hospital, for example, as the patient is moved around the different departments within the hospital. In an example, the RFID device 125 may be the same as the ID tag 122 that provides that unique machine readable code. Such a system of tracking the location of the patient is required when patient location needs to be tracked more accurately than, for example provided by a GPS Alternatively, or in addition to the RFID device 125, the tag 105 may comprise a beacon tracking device 126 fortracking the location of the tag 15 inside the hospital.

[0046] Thus, the combination of the GPS or GSM 124 and the RFID device 125 or the beacon tracing device 126 enables tracking of the location of the tag 105 both within and outside a hospital environment, environment one example, all the data that is stored in the online repository 120 is stored a blog type format, using standard blogging technology. As a result, the web-portal 115 will display the data associated with the patient and / or patient journey data stored in the online repository 120 in reverse chronological order (i.e. newer content / events appear first). Note that the presentation of data in a blog type format only applies to data that is stored via the tag 105 in the online repository 120, and does not apply to the patient's formal medical record.

[0047] Figure 3 illustrates a diagram of an embodiment of a method 300 executed by the systems 100 or 200 of the present application. At operation 305, the tag 105 is associated with a patient involved in the incident. Associating the tag 105 may involve attaching the tag 105 to an arm of a patient. This may be performed, for example, by an ambulance personnel at the scene of the incident. At operation 310, a user of a hand-held device 110 (which may be the ambulance personnel) uses the hand-held device 110 to scan the tag 105 attached to the patient to read a unique machine-readable code provided by the ID tag 122 located within tag 105. As mentioned above, by scanning the tag 105, access is granted to an online repository 120 via the web-portal 115, provided the hand-held device is connected to the internet.

[0048] At operation 315, the user is promoted to provide details to authenticate identify, either through the application 125 or the web-portal 115. The details may include, for example providing a passcode, biometric data, or a certification code using the multi-factor authentication, or a combination thereof, and which may be entered by the user using a Graphical User Interface (GUI) provided by the hand-held device 110.

[0049] At operation 320, and if authentication is required, on the condition that the user has been successfully authenticated, the user stores data relating to the patient into the online repository 120. As mentioned above, the user may need to create a new profile in the online repository 120, or a profile may be created automatically when the user scans the tag 105 using the hand-held device 110 (this is the case when the tag 105 is initially attached to the patient and scanned by the user). The identity of the patient need not be known to store data associated with the patient and / or patient journey data into the online repository, because the data associated with the patient and / or patient journey data is associated with the patient by the unique machine readable code provided by the ID tag 122 of the tag 105. For example, if the user is an ambulance personnel, he or she may store information related to the scene of the incident and related to the patient. For example, as mentioned previously, such information includes information related to any third parties involved (e.g. other vehicle involved in an accident, the condition of each vehicle involved in the accident), the weather conditions on the day on the incident, photos of the surrounding, details of any witnesses involved, the approximate height and weight of the patient, any drugs that were administrated to the patient, any medical tests the patient may have undergone (e.g. measuring heart rate, blood pressure etc...), any other treatment(s) provided to the patient etc

[0050] As also mentioned previously, operations 315 and 320 are not limited to the interaction between an initial user (e.g. ambulance personnel) and the patient. For example, if the patient requires further treatment in a hospital, then a second user may be hospital personnel (e.g. surgeon) who will be able to access the information stored in the patient, store and / or edits data associated with the patient and / or patient journey data into the online repository 120 (e,g, access details about the status of the patient when arriving at the hospital and record information about any treatments undergone by the patient during the stay at the hospital). A third user may be, for example, a physiotherapist who is providing treatment to the patient during or after the stay at the hospital. In some cases, the user may be the patient him / herself, where the patient is able to access the inline repository 120 and update information therein, for example, after receiving treatment. In other words, the operation 320 can include accessing, storing and / or editing data associated with the patient and / or patient journey data by any number of users throughout the journey of the patient, which may last from a few minutes to a period of years. Additionally, any user who wishes to store and / or edit the information in the online repository 120 will require authorisation in the manner shown above.

[0051] In addition, the data associated with patient and / or the journey of the patient may be combined with the location data of the user / tag, the data associated with the identity of the user, and the data related to the time the data associated with the patient and / or patient journey data was stored / edited in the online repository 120.

[0052] The method 300 can further comprise operation 325, where relevant data from the data associated with the patient and / or patient journey data stored in the online repository 120 is combined with the patient's formal medical record when the identity of the patient is eventually established. This can occur, for example, after the patient arrives at the hospital to receive further treatment. As mentioned previously the relevant data associated with the patient and / or patient journey data may include data related to any drugs that were administrated to the patient, any medical tests the patient may have undergone (e.g. measuring heart rate, blood pressure etc...), or any other treatment(s) provided to the patient. Such treatments can be provided by medical personnel at the scene of the incident without the patient needing to be admitted to the hospital, during transit to the hospital, at the hospital itself, or after being discharged from the hospital.

[0053] In the described embodiments the system may be implemented as any form of a computing and / or electronic device. Such a device may comprise one or more processors which may be microprocessors, controllers or any other suitable type of processors for processing computer executable instructions to control the operation of the device in order to gather and record routing information. In some examples, for example where a system on a chip architecture is used, the processors may include one or more fixed function blocks (also referred to as accelerators) which implement a part of the method in hardware (rather than software or firmware). Platform software comprising an operating system or any other suitable platform software may be provided at the computing-based device to enable application software to be executed on the device.

[0054] Various functions described herein can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media may include, for example, computer-readable storage media. Computer-readable storage media may include volatile or non-volatile, removable or non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. A computer-readable storage media can be any available storage media that may be accessed by a computer. By way of example, and not limitation, such computer-readable storage media may comprise RAM, ROM, EEPROM, flash memory or other memory devices, CD-ROM or other optical disc storage, magnetic disc storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Disc and disk, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray (RTM) disc (BD). Further, a propagated signal is not included within the scope of computer-readable storage media. Computer-readable media also includes communication media including any medium that facilitates transfer of a computer program from one place to another. A connection, for instance, can be a communication medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fibre optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of communication medium. Combinations of the above should also be included within the scope of computer-readable media.

[0055] Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, hardware logic components that can be used may include Field-programmable Gate Arrays (FPGAs), Programspecific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs). Complex Programmable Logic Devices (CPLDs), etc.

[0056] It will be understood that the benefits and advantages described above may relate to one embodiment or may relate to several embodiments. The embodiments are not limited to those that solve any or all of the stated problems or those that have any or all of the stated benefits and advantages.

[0057] Any reference to 'an' item refers to one or more of those items. The term 'comprising' is used herein to mean including the method steps or elements identified, but that such steps or elements do not comprise an exclusive list and a method or apparatus may contain additional steps or elements.

[0058] As used herein, the term "system" is intended to encompass computer-readable data storage that is configured with computer-executable instructions that cause certain functionality to be performed when executed by a processor. The computer-executable instructions may include a routine, a function, or the like. It is also to be understood that a component or system may be localized on a single device or distributed across several devices.

[0059] Further, as used herein, the term "example(s)" is intended to mean "serving as an illustration or example of something".

[0060] Further, to the extent that the term "includes" is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term "comprising" as "comprising" is interpreted when employed as a transitional word in a claim.

[0061] Moreover, the acts described herein may comprise computer-executable instructions that can be implemented by one or more processors and / or stored on a computer-readable medium or media. The computer-executable instructions can include routines, sub-routines, programs, threads of execution, and / or the like. Still further, results of acts of the methods can be stored in a computer-readable medium, displayed on a display device, and / or the like.

[0062] The order of the steps of the methods described herein is exemplary, but the steps may be carried out in any suitable order, or simultaneously where appropriate. Additionally, steps may be added or substituted in, or individual steps may be deleted from any of the methods without departing from the scope of the subject matter described herein. Aspects of any of the examples described above may be combined with aspects of any of the other examples described to form further examples without losing the effect sought.

[0063] It will be understood that the above description of a preferred embodiment is given by way of example only and that various modifications may be made by those skilled in the art. What has been described above includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable modification and alteration of the above devices or methods for purposes of describing the aforementioned aspects, but one of ordinary skill in the art can recognize that many further modifications and permutations of various aspects are possible. Accordingly, the described aspects are intended to embrace all such alterations, modifications, and variations that fall within the scope of the appended claims.

Claims

1. A system for managing data relating to one or more persons, the system comprising: one or more tags, each tag configured to be attached to a person, wherein each tag is further configured to be read by a portable hand-held device to provide one or more unique machine-readable codes, wherein the portable hand-held device is connected to the internet;an online repository for storing, editing and / or accessing data related to the person, wherein the one or more unique machine-readable codes provided by a tag that is configured to be attached to the person are used to associate the person with the data related to the person; anda web portal for providing access to the online repository via the portable hand-held device.

2. The system of claim 1, wherein each tag comprises a QR code or a 3D barcode, wherein the QR code or the 3D barcode is configured to provide a unique machine readable code when the tag is read by the portable hand-held device.

3. The system of claim 2, wherein each tag comprises one or more electronic devices, wherein each electronic device is configured to provide a unique machine-readable code when the tag is read by the portable hand-held device, wherein the unique machine readable code provided the one or more electronic devices is the different or identical to the unique machine readable code provided by the QR code or the 3D barcode.

4. The system of claim 2, wherein each tag comprises one or more electronic devices, wherein each electronic device is configured to provide a different unique machine readable code when the tag is read by the portable hand-held device, wherein each unique machine readable code provided by each of the electronics device is different from that provided by the QR code or the 3D barcode.

5. The system of claim 3 or claim 4, wherein each electronic device is any one of: a NFC device, a LC RFID device and / or an a UHF RFID device.

6. The system of claims 3 to 5, wherein the web-portal is configured such that scanning a QR code or a 3D barcode of each tag provides read-only access to the online repository, and wherein the scanning the NFC, LC RFID or the UHF RFID device provides access for storing and / or editing of data relating to the person.

7. The system of any preceding claim, wherein the system further comprises an application, wherein the application is installed on the portable hand-held device.

8. The system of claim 6, wherein the system is configured to authenticate the identity of a responder via a passcode, biometric data, or a certification code using the multi-factor authentication, or a combination thereof, to enable the storing and / or editing of the data relating to the person.

9. The system of claim 8, wherein the authentication is performed via the web portal or the application.

10. The system of claim 8 or claim 9, wherein the system is configured to store, together with the data relating to the person, data identifying the responder in the online repository.

11. The system of any preceding claim, wherein the portable hand-held device is a mobile phone device, a tablet, RFID reader, or an ariel look scanner system.

12. The system of any preceding claim, wherein each tag further comprises a location tracking device configured to generate location data corresponding to the location of the tag attached to the patient.

13. The system of claim 12, wherein the location tracking device comprises one of: Ground Position System or Global System for Mobile communication.

14. The system of claim 13, wherein the location tracking device further comprises a RFID device or a beacon tracing device.

15. The system of any of claims 12 to 14, wherein the system is configured to store, together with the data relating to the person, location data corresponding to the location of each tag attached to the person in the online repository.

16. The system of any of claims 1 to 11, wherein the hand-held device is configured to generate location data corresponding to the location of the portable hand-held device when the tag is read by the handheld device.

17. The system of claim 16, wherein the system is configured to store, together with the data relating to the person, location data corresponding to the location of the portable hand-held device in the online repository.

18. The system of any preceding claim, wherein the web portal is configured to time-tag the data being stored and / or edited in the online repository.

19. The system of any preceding claim, wherein all the data is stored in the online repository in a blog type format.

20. The system of any preceding claim, wherein each tag is attached to a different person.

21. A method of managing data relating to a person, the method comprising:associating a tag to a person, wherein the identity of the person is not yet known;scanning the tag using a portable hand-held device to provide a unique machine-readable code to provide access to an online repository via a web portal, wherein the hand-held device is connected to the internet;storing data relating to the person in the online repository such that all the data relating to the person is linked together, wherein the unique machine-readable code is used to associate the person with the data relating to the person stored in the online repository.

22. The method of claim 21, wherein the method further comprises accessing and / or editing the data relating to the person in the online repository.

23. The method of claim 22, further comprising storing, together with the data relating to the person, location data corresponding to the location of the tag attached to the person or the location data corresponding to the location of the portable hand-held device, wherein the location data is stored during storing and / or editing of the data relating to the person.

24. The method of claim any of claims 22 to 23, further comprising time-tagging the data relating to the person during the storing and / or editing the data relating to the person in the online repository.

25. The method of any of claims 22 to 24, wherein the method further comprises, before the storing and / or editing data relating to the person, the authenticating the identity of a responder via a passcode, biometric data, or a certification code using the multi-factor authentication, or a combination thereof.

26. The method of claim 25, wherein the authentication is performed via the web-portal or an application installed on the hand-held device.

27. The method of claim 25 to 26, wherein the method further comprises storing, together with the data relating to the person, data associated with the identity of the responder during the storing and / or editing the data relating to the person in the online repository.

28. The method of any of claims 21 to 27, wherein the method further comprises combining all or a subset of the relating to the person in the online repository to the persons medical record when the identity of the person is established.

29. The method of any of claims 21 to 28, wherein the associating the tag with the person comprises physically attaching the tag to the person.AMENDMENTS TO THE CLAIMS HAVE BEEN FILED AS FOLLOWS:05 08 24Claims:

1. A system for managing data relating to one or more persons, the system comprising:one or more tags, each tag configured to be attached to a person, wherein each tag is further configured to be read by a portable hand-held device to provide one or more unique machine-readable codes, wherein the portable hand-held device is connected to the internet;an online repository for storing, editing and / or accessing data related to the person, wherein the one or more unique machine-readable codes provided by a tag that is configured to be attached to the person are used to associate the person with the data related to the person; anda web portal for providing access to the online repository via the portable hand-held device, wherein each tag comprises a QR code or a 3D barcode, wherein the QR code or the 3D barcode is configured to provide a unique machine readable code when the tag is read by the portable hand-held device; andwherein each tag comprises one or more electronic devices, wherein each electronic device is configured to provide a unique machine-readable code when the tag is read by the portable hand-held device, wherein the unique machine readable code provided by the one or more electronic devices is different or identical to the unique machine readable code provided by the QR code or the 3D barcode; andwherein the web-portal is configured such that scanning a QR code or a 3D barcode of each tag provides read-only access to the online repository, and wherein the scanning the NFC, LC RFID or the UHF RFID device provides access for storing and / or editing of data relating to the person.

2. The system of claim 1, wherein each tag comprises one or more electronic devices, wherein each electronic device is configured to provide a different unique machine readable code when the tag is read by the portable hand-held device, wherein each unique machine readable code provided by each of the electronics device is different from that provided by the QR code or the 3D barcode.

3. The system of claim 1 or claim 2, wherein each electronic device is any one of: a NFC device, a LC RFID device and / or an a UHF RFID device.

4. The system of any preceding claim, wherein the system further comprises an application, wherein the application is installed on the portable hand-held device.

5. The system of claim 3, wherein the system is configured to authenticate the identity of a responder via a passcode, biometric data, or a certification code using the multi-factor authentication, or a combination thereof, to enable the storing and / or editing of the data relating to the person.05 08 246. The system of claim 5, wherein the authentication is performed via the web portal or the application.

7. The system of claim 5 or claim 6, wherein the system is configured to store, together with the5 data relating to the person, data identifying the responder in the online repository.

8. The system of any preceding claim, wherein the portable hand-held device is a mobile phone device, a tablet, RFID reader, or an ariel look scanner system.10 9. The system of any preceding claim, wherein each tag further comprises a location trackingdevice configured to generate location data corresponding to the location of the tag attached to the patient.

10. The system of claim 9, wherein the location tracking device comprises one of: Ground Position 15 System or Global System for Mobile communication.

11. The system of claim 10, wherein the location tracking device further comprises a RFID device or a beacon tracing device.20 12. The system of any of claims 9 to 11, wherein the system is configured to store, together withthe data relating to the person, location data corresponding to the location of each tag attached to the person in the online repository.

13. The system of any of claims 1 to 8, wherein the hand-held device is configured to generate location 25 data corresponding to the location of the portable hand-held device when the tag is read by the handheld device.

14. The system of claim 13, wherein the system is configured to store, together with the data relating to the person, location data corresponding to the location of the portable hand-held device in the online 30 repository.

15. The system of any preceding claim, wherein the web portal is configured to time-tag the data being stored and / or edited in the online repository.35 16. The system of any preceding claim, wherein all the data is stored in the online repository in ablog type format.

17. The system of any preceding claim, wherein each tag is attached to a different person.40 18. A method of managing data relating to a person, the method comprising:05 08 24associating a tag to a person, wherein the identity of the person is not yet known;scanning the tag using a portable hand-held device to provide a unique machine-readable code to provide access to an online repository via a web portal, wherein the hand-held device is connected to the internet;5storing data relating to the person in the online repository such that all the data relating to the person is linked together, wherein the unique machine-readable code is used to associate the person with the data relating to the person stored in the online repository, wherein each tag comprises a QR code or a 3D barcode, wherein the QR code or the 3D barcode is configured to provide a unique machine 10 readable code when the tag is read by the portable hand-held device; andwherein each tag comprises one or more electronic devices, wherein each electronic device is configured to provide a unique machine-readable code when the tag is read by the portable hand-held device, wherein the unique machine readable code provided by the one or more electronic devices is different or identical to the unique machine readable code provided by the QR code or the 3D barcode;15 andwherein the web-portal is configured such that scanning a QR code or a 3D barcode of each tag provides read-only access to the online repository, and wherein the scanning the NFC, LC RFID or the UHF RFID device provides access for storing and / or editing of data relating to the person.20 19. The method of claim 18, wherein the method further comprises accessing and / or editing the datarelating to the person in the online repository.

20. The method of claim 19, further comprising storing, together with the data relating to the person, location data corresponding to the location of the tag attached to the person or the location data 25 corresponding to the location of the portable hand-held device, wherein the location data is stored during storing and / or editing of the data relating to the person.

21. The method of claim any of claims 19 to 20, further comprising time-tagging the data relating to the person during the storing and / or editing the data relating to the person in the online repository.3022. The method of any of claims 19 to 21, wherein the method further comprises, before the storing and / or editing data relating to the person, the authenticating the identity of a responder via a passcode, biometric data, or a certification code using the multi-factor authentication, or a combination thereof.35 23. The method of claim 22, wherein the authentication is performed via the web-portal or anapplication installed on the hand-held device.

24. The method of claim 22 to 23, wherein the method further comprises storing, together with the data relating to the person, data associated with the identity of the responder during the storing and / or 40 editing the data relating to the person in the online repository.CMOID25. The method of any of claims 18 to 24, wherein the method further comprises combining all or a subset of the relating to the person in the online repository to the persons medical record when the identity of the person is established.

526. The method of any of claims 18 to 25, wherein the associating the tag with the person comprises physically attaching the tag to the person.10

Images