[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

GB2628334A - A method of storing and retrieving information - Google Patents

A method of storing and retrieving information Download PDF

Info

Publication number
GB2628334A
GB2628334A GB2302665.1A GB202302665A GB2628334A GB 2628334 A GB2628334 A GB 2628334A GB 202302665 A GB202302665 A GB 202302665A GB 2628334 A GB2628334 A GB 2628334A
Authority
GB
United Kingdom
Prior art keywords
data
user
identifier
medical
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
GB2302665.1A
Other versions
GB202302665D0 (en
Inventor
Lawrence Davison Mark
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Id Band Co Ltd
Original Assignee
Id Band Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Id Band Co Ltd filed Critical Id Band Co Ltd
Priority to GB2302665.1A priority Critical patent/GB2628334A/en
Publication of GB202302665D0 publication Critical patent/GB202302665D0/en
Publication of GB2628334A publication Critical patent/GB2628334A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245Protecting personal data, e.g. for financial or medical purposes

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Medical Informatics (AREA)
  • Storage Device Security (AREA)

Abstract

A method of storing and retrieving information used to separate data on a first user 18 into categories with protected data 26 restricted so that only authorised access is allowed, and minimal data is much more easily available to anyone. Data is stored and categorised, with an identifier 10 generated for each person with stored data. When a request is made using the identifier and with a recognised permission key 32 of a second user 34, protected data 26 is sent. Whereas if only the identifier is used only the minimal data is sent. The data stored may be personal or medical data, with the different categories of data relevant to different levels of medical personnel. The identifier may be stored as part of a web address which contains the minimal data whereas access to protected data is only possible for authorised users through an application.

Description

A Method of Storing and Retrieving Information The present invention relates to a method of storing and retrieving information and relates particularly, but not 5 exclusively, to a wearable device including a QR code for retrieving stored information.
In case of emergency, or ICE, was a program originally designed to enable first responders such as paramedics, police or firefighters to easily access the next-of-kin contact details about a person involved in an accident. Originally, the program would encourage the public to add their next-of-kin contacts into their phone under ICE contact 1, ICE contact 2 etc. With the emergence of smart phones, first responders in some cases can quickly access a person's emergency contacts with a press of a button. An example of this is the Emergency Medical ID feature displayed on the front of an iPhone display. Unfortunately, this feature (observed on many different smart phones) only gives the receiver minimal information regarding the person concerned. In other cases, first responders may not have the time or knowledge to access an ICE app on a phone they are unfamiliar with.
Other ICE approaches include wearing a medical ID bracelet or necklace. These wearable IDs can include engravings located on the bracelet or locket that inform a first responder of important details. These details can include name, ICE contact and if the person suffers from any medical conditions. Other wearable IDs have a front clasp that can be opened to reveal a slip of paper. The paper would also include important information about the wearer. In general, these types of wearable IDs are small and only allow the wearer to input limited information about themselves. This can be problematic if the wearer has multiple medical conditions. Furthermore, the information included on the wearable ID is accessible to all who see it leading to concerns of privacy. A further disadvantage -2 -to the wearable TD is the difficulty to update the engraving or paper with new or updated information. Any updates to the wearable IDs may cost the user more money and may not have been updated or validated by a medical professional, leading to 5 questions over the accuracy of the information.
Preferred embodiments of the present invention seek to overcome or alleviate the above described disadvantages of the prior art.
According to the present invention there is provided a 10 method of storing and retrieving information comprising the steps: storing data relating to a first user; classifying the data into categories including a minimal data category; generating an identifier associated with said data of said first user; registering a plurality of second users and allocating said second users with a permission key; receiving a data retrieval request including said identifier; 20 and if said request includes data indicating the request is made by a second user returning data from categories associated with said permission key of said second user otherwise returning data from said minimal data category.
Classifying the data into categories, including a minimal data category, organises the data in an optimal way suitable for transmitting. The categories make it easier for a user or system to navigate the different types of data and therefore distinguish between accessible data (with permission) and non-accessible data. When a request is sent, if a permission key has been sent with it a decision can be made instantly as to -3 -which categories or subsets thereof can be returned. If a request is sent without the permission key only the minimal data is returned. Having the minimal data inclusion is important and beneficial to both the first user and the user sending the request. The first user has the choice of which data is allowed to be shown (within the minimal data category) to anyone who sends a request, and the requestee is given enough information to identify and assist the first user.
Registering second users is beneficial for the first user as the first user will be assured that any sensitive data about themselves is secured and only people with the correct permission key can access the information. The permission key is also a security feature and enables the second users to obtain the information that they require about the first user quickly.
In a preferred embodiment the data is arranged in a hierarchy of data categories and said second user's permission key allows them access to different data categories.
By including a hierarchy of data categories, medical information about the first user that is specific and potentially important to the second user's fulfilling their role becomes easily and immediately accessible to them. For example, a cardiologist may require access to a first user's scans, test results and medications that are related to the first user's circulatory system. However, a paramedic would not require the same level of information about the patient's heart. A paramedic would require different medical information such as, the first user's diabetic status, if they have allergies to commonly used medications or their primary medical condition or the like.
In a preferred embodiment, the data comprises medical 30 information.
By using the present invention with medical information for the data, the advantage is provided that the minimal data can be medical information which is important for any first aider -4 -to know when treating the first person if they were found, for example, unconscious. Information such as allergies and suitable remedies or other medical conditions which are important for anyone administering first aid can be easily 5 obtained without the need for being registered as someone who should have access to more detailed medical information. In particular, this can allow access to the minimal data via a web-browser and only allow access to more detailed medical information via a secure app.
In another preferred embodiment, the data is stored on a server.
In a further preferred embodiment, the second user accesses said data through an app.
In another preferred embodiment the minimal data is 15 retrieved in response to said data request via a website.
The method may further comprise generating a visual representation of the identifier.
In a further preferred embodiment, the visual representation comprises a string of characters linked to said 20 identifier.
In an additional preferred embodiment, the visual representation further comprises a web address including said string of characters.
In another preferred embodiment, the visual representation 25 comprises at least one graphic encoding including said identifier.
In an additional preferred embodiment, the graphic encoding further comprises encoding of a web address.
In a further preferred embodiment, the graphic encoding 30 comprises a QR code. -5 -
The ability for anyone to scan the QR code and see the minimal data is a benefit as that information can be rapidly relayed to the emergency services and help guide their response. Furthermore, there is no particular limit to the amount of data that can be displayed and the data can be up to date giving greater confidence in the information provided.
The method may further comprise storing the identifier on a wirelessly readable chip and said chip is a near-field communication chip.
The NFC chip enables fast access to the first user's data without risk that the identifier is being incorrectly entered. If an identifier is simply written there is a risk of incorrect data entry by the second user. If the identifier is represented visually there is a slight risk of it being incorrectly read, either by a person or a machine, due to interference of that visual representation by damage or being obscured by dirt. Where a chip is being used together with a visual representation, there are two methods of access to the same data meaning that if one method is unsuccessful another can be tried decreasing the likelihood of failure.
In another preferred embodiment, said visual representation is applied to an object.
In a further preferred embodiment, the object is a wearable object, and the wearable object is a wearable wrist band.
Having a wearable wrist band enables the second user to find and scan the identifier in a quick and efficient manner. The wrist band is worn in an obvious place at a pulse point which would normally be checked by a first responder in an emergency and is easier to see and access when there is an emergency.
The method may further comprise notifying a recipient when said database is accessed. -6 -
By notifying a recipient, any family members or friends of the first user can be alerted to a potential emergency quickly. Any medical practitioners, such as a GP, who have an interest in their patient's wellbeing and care, may also want to know if the first user has been involved in an incident.
In an additional preferred embodiment, the medical information comprises medical records.
Preferred embodiments of the present invention will now be described, by way of example only, and not in any limitative 10 sense with reference to the accompanying drawings in which:-Figures la to ld are front and back views of the wearable device of the present invention; Figures 2a and 2b show an example scenario of the method of the present invention; Figures 3a and 3b show another example scenario method of the present invention; and Figures 4 to 12 are flowcharts depicting the method of storing and retrieving information of the present invention.
Referring initially to figure 1, a method of storing and receiving information includes using a wearable wrist band which is in the form of an ID band 10 having a graphical encoding, in the form of QR code 12, printed on it. The ID band 10 includes a front face 14 and a back face 16. The front face 14 is the visible area of the ID band when worn by a first user 18, whilst the back face lies adjacent to the first user's wrist. The QR code 12 is located on the front face 14, along with an internationally recognised medical symbol such as the stake of Asclepius within the six-pointed star of life and a logo, as shown in figure lc. Also on the front face 14 is a basic information box 20 containing information relating to the first user as shown in figure ld. Other such symbols or information could also be represented on the ID band 10 or the QR code 12 could be on its own. Figure lb also shows that the basic information box 20 could be located on the back face 14 of the ID band 10. The basic information box 20 can include the first user's name, an ICE (In-case-of emergency) number and medical information. For example, the medical information could show that the first user has a nut allergy, and the use of epinephrine is recommended.
The ID band 10 also includes a series of small apertures 22 at one end and a pin 24 at the opposing end. The apertures 22 and pin 24 are used the secure the ID band onto the first user's wrist when being worn. Other clasps or securing methods such as a pin buckle could be used. To ensure the ID band 10 is flexible to wrap around the first user's wrist the ID band is formed of silicone. Other flexible materials such as leather, rubber or plastic could be used.
In the examples shown in figures la to ld, the ID bands 10 are 261mm in length, 26.7mm at their widest point and the opening is _ram wide.
The QR code 12 on the ID band 10 is a graphical encoding of a visual representation of the first user's identifier. The identifier includes, but is not limited to, a web address and a string of characters associated with the first user 18. The web address or characters are used to locate a first user's data 26 within a server 28. The QR code 12 could be replaced by another suitable visual representation of the identifier such as the actual string of characters/numbers associated with the first user written on the ID band 10, the web address and string of characters or a barcode. In the embodiment shown in the figures the QR converts on scanning into a web address including a domain and a file path. The domain (or more specifically protocol and domain) is, for example, hi. lit -diancom. The file path is then preferably the identifier and most preferably each path and identifier is a Globally Unique Identifier (GUID). -8 -
By using a GUTD it makes it extremely difficult for the first user's data that is in the minimal data category to be scraped from the data available over the internet without the need for the use of the app and permission key 32.
Furthermore, as shown in Figures lc and ld the QR code 12 is applied to (printed on or engraved onto) a wrist band 10. The wrist band could also be replaced by a ring, necklace or other suitable wearable piece of jewellery. Other suitable replacements could be an object the user would carry around such 10 as a card inside a wallet, a sticker on the back of a phone or helmet or a keyring. Lastly, the identifier could be electronically sent to the first user 18 and used in a tattoo or written in a conveniently found place.
Referring now to figures 2 and 3, the first user's data 26 is stored within the server 28 and is separated into an array of categories. These categories include a minimal data category 30 and additional and generally more sensitive information such as medical information, police records, additional information, home addresses and contacts of friends and family. However, it should be noted that some of this information, such as contact information, can be included in the minimal data category. The medical information could include the first user's medical records provided by a hospital or medical information added or updated by a medical practitioner directly to the server 28. To ensure the integrity, quality and relevance of the medical data it is ideally entered by a medical professional. However, in principle other suitable data entry personnel could be used to populate the database. All the data in the categories, except the minimal data category 30, are secured in a secure database 30 which requires a permission key 32 and can only be accessed if the permission key sent by a second user 34 matches the permission key on the category. When the second user 34 is registered they are allocated their permission key 32 depending _ 9 _ on who they are and what position they hold. For example, when a member of the first user's medical care team registers they would be given permission to access the first user's medical information and when a paramedic registers they would only be given a permission key to access the first user's medical data set flagged as relevant to paramedics. A further example could include a police officer registering as a second user. They would be given permission to access the first user's police records. Other examples of second users 34 include paramedics, 10 ambulance services, fire services, A&F departments, GPs, A&F department personnel, social workers etc. The minimal data category 30 is also stored on the web address and therefore can be accessed freely without the permission key 32, after scanning the QR code 12.
As an absolute minimum, the categories are the minimal data category and a protected category. In this example, the minimal category contains the data that is available to anyone using the identifier (the QR code) to access the data via the website. At the same time, the protected category data is the more detailed medical data which might be of use to all medical personnel.
The web address and the server 28 may also have a further level of security such as firewall and CAPTCHA test to make it harder for automated systems to access the first user's data 26 including the minimal data category 30.
Figures 2 and 3 depict two different scenarios including an emergency event in which the first user 18 is unable to respond. The second user 34 is represented in figure 2 as a registered user (typically a first responder such as a paramedic or police officer) and therefore has been allocated the permission key 32. In figure 3 a third user 36, is a user who is not a registered user and therefore has not been allocated the permission key 32.
-10 -Figure 2a shows the second user 34 approaching the first user 18 and scanning the QR code 12 on the ID band 10 using a device such as a mobile phone 38. As the second user 34 is a registered user they use an app (not shown) on their phone to scan the QR code and receive information about the first user 18 (depending on their permission key level). The QR code is a visual encoding of a web address including a domain and a GUID. Because the app is accessing data in the database beyond the minimal data category, it does not use all of the web address and extracts the GUID to use as the identifier for the first user. In other words, the app reads the QR code, converts it to a string of characters of the web address including domain and file path, parses the character string into these two parts, discards the domain part of the converted QR code and only uses the identifier contained in the file path. When the second user 34 scans the QR code 12 using the app, a signal 40, including the identifier, is sent to the server 28 requesting information about the first user 18.
The signal 40 includes the identifier of the first user 18 and the permission key 32 of the second user 34. Both are used in combination to locate and request access to the first user's data 26 within the server. Once the first user's data has been located using the identifier and the permission key 32 has been established, the second user 34 receives the relevant information which is displayed on a screen of their device 38 as seen in figure 2b.
Figures 3a and 3b show the process of retrieving the first user's data 26 by the non-registered third user 36. In this instance, when the third user approaches the first user 18, they use the camera on their device 38 to scan the QR code 12. Since the third user 36 does not have the associated app on their device to scan the QR code 12 they therefore use their device's camera. Once the QR code 12 is scanned, most modern smart devices automatically suggest the web address associated with the identifier and direct the third user 36 to the web address for the first user 18. As the third user has not been allocated the permission key 32 they would not be able to gain access to 5 the user's data 26 stored on the server 28. The webpage contains the minimal category data 30 allowing the third user to receive that information displayed as a web page in a browser on their phone. The third user is able to use the minimal dana category information when calling the emergency services and telling the 10 handler who the first user is, any relevant medical information and where they are.
Referring now to figures 4 to 12, the process of the present invention is explained in more detail below. Figures 4 and 5 highlight a medical organisation (in figure 4) and responder organisation (in figure 5), such as a hospital, registering medical partners (for example doctors) and responder partners (for example paramedics) as second users 34. Details such as the name, address, contact details and email addresses of the second users 34 are provided (illustrated in steps Sla and Slb).
The details are used to create second user IDs (steps S2a and S2b) and are added to the app and database (S3a and Sib) . A link is then sent to each of the second users 34 so they can download the associated app (S4a/b and S5a/b). Once the second users 34 have downloaded the app they are prompted to create a secure login and are finally registered as second users 34 (S6a and S6b). Lastly, in the case of medical responders, the second users 34 login to the app using their login details at the start of every shift (S7b).
Figure 6 shows an example of a medical partner such as a 30 GP (the second user 34) ordering an ID band for his patient (the first user 18). The second user 34 orders the ID band 10 (referred to as ultraband in the figures) for the first user 18 either in the app or online. They input the first user's data -12 -such as name, primary ICE, primary medical condition, patient address and delivery address (Sic). The first user's data 26 is then stored in the server 28 (database) and a unique QR code 12 is generated representing a web address including a domain and file path with the latter including the identifier for the first user (step S2c). The status of this QR code 12 is automatically set to "locked" to protect the first user's privacy and will not unlock until the first user receives it. If the QR code 12 is scanned before the first user 18 receives the ID band 10 it will direct the user to a URL showing "Access Denied" (S3c). An ID band 10 is then customised to include the first user's QR code, name, primary medical condition and ICE number engraved or printed on it (S4c). The ID band 10 is then shipped to the first user 18 and an email including instructions on how to download the app is sent (S5c and S6c). Once the first user 18 has installed the app they can create secure login details (S7c and S8c).
Figure 7 is a flowchart of the first user 18 receiving the ID band 10. Once the first user 18 has obtained the ID band 10 20 they scan the QR code using the app (S1d and S2d). The app asks the first user 18 to confirm that they have received the correct ID band 10 (S3d). If the user selects no they are asked to contact the associated company for assistance (S4d). If the user selects "yes", the QR code is unlocked and the user is prompted to enter a photo of themselves along with additional identification details (55d and S6d). If the user decides to upload a photo, the photo forms part of the minimal data and will become a useful aid for verifying the wearer's identification and the appropriate treatment whether accessed through the minimal data web address or using the app thereby reducing the likelihood of mistaken identity. The first user 18 is then offered the option to generate an automated SMS to any ICE contacts in the event that their QR code is scanned when in an emergency (S7d -S9d). Finally, the app will tell the -13 -first user 18 that the following has been or will be input by the patient's medical partner (second user 34): Primary medical condition; medical alerts; medications; and medical history (S10d).
Figure 8a highlights an example of what the first user sees on the screen of their app. Feature buttons such as view or edit my information, scan logs, medical partner details, lost or stolen band and FAQs are included. Figure 8b highlights the information the first user 18 can view or edit. The first user 18 can view (but not edit) their primary medical condition, medical alerts, medications and medical history (Sle). If the user wishes to edit any information, they will be able to update their primary ICE contacts, add more ICE contacts or include any additional notes (S2e). If the user has chosen to update their primary ICE contact, an in app warning appears letting the first user know that the updated ICE contact telephone number in the database may not match the telephone number engraved on their ID band. From here the first user has a choice to confirm the update and confirm or amend which ICE contacts will receive automated messages or revert to the original number (S3e to S9e). Finally, any updated information is added to the server 32 (database) (S10e).
Figure 8c highlights what occurs if the user presses the lost or stolen button in the app. The user is first asked if their ID band 10 has been either lost or stolen (SU.). If the user presses lost the ID band 10 is temporarily disabled and the QR code is temporarily locked (S2f and Sf3). If the user presses stolen their ID band is permanently disabled and the QR code is permanently deactivated (S4f and S5f). In both cases an in app alert is sent to the relevant second user 34 (S6f).
In figure 9 step Slg highlights that second users with the appropriate permission key can view specific data details for first users. Also in figure 9, steps S2g to S5g further -14 -highlight the alerts that are shown in the app (or on the secure website) to second users 34 with the appropriate permission key to receive such alerts in the event that the first user's data has been updated, not completed or if the QR code 12 has been scanned in an emergency.
Figure 10 shows an example of the steps taken if a first responder (registered second user 34) scans a QR code 12 of a first user 18 in an emergency. When using the app, the second user 34 enters the scan screen to scan the QR code on the ID band 10 (Slh). If the first user has chosen to notify a recipient in an emergency, the app sends an automated SMS of the first user's name, time, date and a link to a mobile website showing the geographical position where the emergency scan has occurred to the recipient (S2h and S3h). The app then receives and shows the information relevant to the corresponding second user (S4h). If the first user has an additional "More info" alert option included in their medical information data to provide additional emergency treatment information relating to, for example, a rare disease, the second user will be alerted, and shown a "More info" option to obtain the additional information (S5h). If the second user selects the "More info" option, the second user is sent to a dedicated webpage with specific guidance on treatment of first users with a particular medical condition e.g., a rare disease that a first responder would not be expected to be aware of or a clinical trial (S6h). Finally, an in app alert of the emergency scan that has taken place of the first user will be sent to the corresponding medical partner. By notifying the originating medical partner of all emergency scans, the clinical team can monitor the first user's emergency scans and make an early intervention when appropriate saving time, resources and ultimately improving the efficacy of treatment.
-15 -Figure 11 represents an example flow chart in the event that the third user 36 (a member of the public) scans the QR code. Once the third user scans the QR code 12 on their smart device 38, a check is performed to determine if the QR code is locked or unlocked (Sli and S2i) (this would be activated if the ID band 10 has been lost or stolen, figure 8c). If the QR code is locked the third user is taken to a URL saying, "Access Denied" (S3i). If the QR code is not locked the third user is asked if they want to report an emergency (S4i). If they choose no, no further action is taken (S5i). If they choose yes, a unique code is then generated by the server and the following message is displayed as part of the webpage, "Please tell 999/111 that [name] is wearing a Life Guardian ultraband (ID band 10) and give them this code". The webpage also shows a button to dial 999. The receiving emergency service call handler inputs the code on their emergency screen in the app and the app then displays the first user's data associated with the permission key for that second user type in this case an emergency services call handler (S6i to S10i).
Figure 12 shows the process of the first user 18 attending a medical partner clinic as part of the data input process (as opposed to data recovery, see figure 11 and associated text above). At the clinic the second user (for example, a medical professional) scans the QR code 12 on their app or logs into the secure database and is shown the first user's information, date of last check and date of last updates added (S1j -S3j). The app lets the medical partner know if any of the following are incomplete: primary medical condition, medical alerts, medications, or medical history. If the second user 34 can see that all the information is correct and no updates are needed, the server 34 updates the app to show that the medical information has been checked and verified (S4j -S7j). However, if the second user 34 notices or decides that updates or changes need to be made, they follow the next steps. The second user -16 -accesses the server 28 (database) using their secure login and updates any relevant fields (according to their permission key hierarchy) within the first user's categories (S8j). The server 32 updates the first user data 28 and the app and a date stamp of when the update was processed is included (S9j and (S10j).
Another example of the use of the present invention is the inclusion of an embedded NFC chip in the wearable band. The NFC chip enables short range, wireless communication between the wearable ID band 10 and the device 38. The second user 34 (or third user 36) would position their device 38, with its NFC function turned on, a short distance from the ID band 10, and therefore near the NFC chip, and receive a notification. The notification would prompt the second user 34 to click on the website shown (for example, eFauaz.x. ,com) on their device 38, allowing access to the first user's 18 data. As described above, as the third user is working outside of the app then they would be simply directed to the file path for the website containing the minimal data. The second user, working from within the app, would receive data relevant to their permission with the identifier being stripped from the file path of the web address as read from the NFC chip. The NFC chip could be used alongside the QR code 12 with both systems providing the same data input of the web address including the identifier. This enables a dual method of retrieving the first user's data further allowing people whose devices cannot read NFC chips to still gain access the first user's data or providing a backup system in case of damage to the QR code or chip.
A further example of the use of the present invention is the use of the band and QR code/NFC chip at outdoor sporting events, such as open water swimming, where the participants are first users and the venue or event staff or organisers are second users. The user of the wearable ID band would arrive at a venue where the event was taking place and scan in, acknowledging -17 -their enrolment to the event. This would involve the participant having the QR code or NFC chip on their band scanned in the app by the event organisers or venue staff. By scanning all the participants' wearable bands the event organisers will know how many people have attended and therefore how many people they have to account for. In the event that an accident has occurred to an individual who has enrolled, a registered second user would be able to access all the medical information that has been uploaded on the individual. As set out above, third users would also be able to access minimal data via the web address. Once the event has finished all the participants who have enrolled would be delisted and their medical information would no longer be attainable, even to the registered second users. That is, access to their medical information would only be temporarily available for the duration of the event. It will be appreciated by persons skilled in the art that the above embodiments have been described by way of example only and not in any limitative sense, and that various alterations and modifications are possible without departure from the scope of the protection which is defined by the appended claims. For example, the second user 34 could further access the first user's data 28 using a login and password via the web address. The file path part of the converted QR code may only indirectly linked to the identifier and a conversion step may take place within the app to produce a secondary identifier which then retrieves the data from the database.
The relationship between the identifier and the visual representation of the identifier, as set out in the claims below, can be in several different forms. For example, in the main example set out above, the QR code is a visual representation of a web address that can be converted, by a QR code reader, into text that includes a domain and the identifier. Equally, the visual representation can be the text that includes the domain and the identifier printed onto the ID band and thus used -18 -by entering the domain and identifier into a web browser. However, the visual representation could also be the digits of the identifier written out perhaps with an image indicating the digits are for use in the retrieval of (medical or other) data relating to the person they are associated with. In this last example, if it sufficiently well known, the image is used as a shorthand known to mean "to retrieve the minimal category data access the medical information website and enter this identifier or access more information as a registered user use the app".
A further example is although the user's medical information is added to or updated by medical practitioners this is not essential. The medical information could be updated automatically by computer software, by the first user or by an authorised non-medical staff member.
Another example is the NFC chip could include an RFID chip.
The RFID chip would also be embedded in the wearable ID band or used alongside the QR code as a dual method for retrieving the first user's medical data.

Claims (19)

  1. -19 -Claims 1. A method of storing and retrieving information comprising the steps: storing data relating to a first user; classifying said data into categories including a minimal data category; generating an identifier associated with said data of said first user; registering a plurality of second users and allocating said 10 second users with a permission key; receiving a data retrieval request including said identifier; and if said request includes data indicating the request is made by a second user returning data from categories associated with 15 said permission key of said second user otherwise returning data from said minimal data category.
  2. 2. A method according to claim 1 wherein, said data is arranged in a hierarchy of data categories and said second user's permission key allows them access to different data categories.
  3. A method according to claim 1 or 2, wherein said data comprises medical information.
  4. 4. A method according to any preceding claim wherein said data is stored on a server.
  5. 5. A method according to any preceding claim wherein said second user accesses said data through an app.
  6. 6. A method according to any preceding claim wherein said minimal data is retrieved in response to said data request via a website.
  7. -20 - 7. A method according to any preceding claim further comprising generating a visual representation of said identifier.
  8. 8. A method according to claim 7 wherein said visual 5 representation comprises a string of characters linked to said identifier.
  9. 9. A method according to claim 8 wherein said visual representation further comprises a web address including said string of characters.
  10. 10. A method according to claim 7 wherein said visual representation comprises at least one graphic encoding including said identifier.
  11. 11. A method according to claim 10 wherein said graphic encoding further comprises encoding of a web address.
  12. 12. A method according to claims 10 or 11 wherein said graphic encoding comprises a QR code.
  13. 13. A method according to any preceding claim further comprising storing said identifier on a wirelessly readable chip.
  14. 14. A method according to any preceding claim wherein said chip is a near-field communication chip.
  15. 15. A method according to claim 6 to 14 wherein said visual representation is applied to an object.
  16. 16. A method according to claim 15 wherein said object is a 25 wearable object.
  17. 17. A method according to claim 16 wherein said object is a wearable wrist band.
  18. 18. A method according to any preceding claim further comprising notifying at least one recipient when said data base is accessed.-21 -
  19. 19. A method according to any preceding claim wherein said medical information comprises medical records.
GB2302665.1A 2023-02-24 2023-02-24 A method of storing and retrieving information Pending GB2628334A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
GB2302665.1A GB2628334A (en) 2023-02-24 2023-02-24 A method of storing and retrieving information

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
GB2302665.1A GB2628334A (en) 2023-02-24 2023-02-24 A method of storing and retrieving information

Publications (2)

Publication Number Publication Date
GB202302665D0 GB202302665D0 (en) 2023-04-12
GB2628334A true GB2628334A (en) 2024-09-25

Family

ID=85794134

Family Applications (1)

Application Number Title Priority Date Filing Date
GB2302665.1A Pending GB2628334A (en) 2023-02-24 2023-02-24 A method of storing and retrieving information

Country Status (1)

Country Link
GB (1) GB2628334A (en)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
GB202302665D0 (en) 2023-04-12

Similar Documents

Publication Publication Date Title
US9824186B2 (en) Medical and personal data retrieval system
US9491277B2 (en) Computerized method and system for global health, personal safety and emergency response
US7619533B2 (en) Method and apparatus for monitoring persons
US10204704B1 (en) Systems and methods for biometrically retrieving medical information
US20180332162A1 (en) Mobile application for personal safety
US20140142979A1 (en) Medical Quick Response Codes and Information Storage and Retrieval System
US4557693A (en) Human identification system
US20070046476A1 (en) System providing medical personnel with immediate critical data for emergency treatments
US20120050046A1 (en) Systems and methods for monitoring physical, biological and chemical characteristics of a person, animal, object and/or surrounding environment
US20100117799A1 (en) Secure personal information and notification network for electronic health records systems
US20120278865A1 (en) Method, system and apparatus for identification
US9990828B2 (en) Rescue method, rescue system, wandering person care method, and wandering person care system
WO2019198358A1 (en) Personal medical information collecting system
US20080288540A1 (en) Method of Access to Personal Information
US20160232416A1 (en) Vital Data Assistant
US9105072B2 (en) Method and apparatus for automated multi-user multi-duration access to emergency medical records
US20110040578A1 (en) Device, system and method of displaying and improving the access to disclosed medical data
GB2628334A (en) A method of storing and retrieving information
US20170083667A1 (en) Emergency service provider monitoring and rehabilitation methods and devices
US11776670B1 (en) System and method for facilitating employee health screening using an application on a mobile computing device
KR102283682B1 (en) Emergency Management System For Chronic Disease Patient And Management Method For The Same
JP2007034798A (en) Rescue information system, rescue information communication terminal, rescue information server, rescue information communication method, and communication method on rescue information server
US20160224736A1 (en) Portable healthcare information readable device and methods of using such a device
NL2012301C2 (en) Digital care communication and information system.
KR101678902B1 (en) System for verifying person identifiaction and securing safety