System, Method, and Apparatus for Universally Accessible Personal Medical Records

Abstract

A system, method, and apparatus for universally accessible personal medical records may provide for encrypted storage of patient-specific data within a personal medical record linked to a personal medical record chain of personal medical records, wherein the personal medical records are stored as a personal medical record chain of connected personal medical records, and wherein the personal medical record chains are stored in immutable form across a plurality of nodes that collectively function as a dispersed, redundant personal medical record chain data storage system. In some embodiments, the present invention may provide that a secure QR code may act as a patient's private key or password, and may be scanned by any medical professional in the world who has access to the present invention. When scanned, the present invention may decrypt the patient-specific data and provide a portion or all of the same to the medical professional. The present invention may record the fact of the medical professional's access to the patient-specific data along with any changes to the patient-specific data within a new personal medical record personal medical record, and may provide that the new personal medical record may chain to the previous personal medical record, and may also provide that multiple such copies and chains of personal medical records are stored across more than one node.

Claims

1. A non-transitory, tangible computer-readable medium having stored thereon computer-executable instructions, which, when executed by a computer processor, enable one or more computers coupled to a network to execute a computer implemented method for universally accessible personal medical records, the method comprising: configuring, by a computing system, at least one personal medical record chain-configured data bank distributed across a plurality of computer networking systems, wherein the plurality of computer networking systems comprises at least one node; receiving, by the computing system, at least one item of patient-specific data, wherein the at least one item of patient-specific data pertains to a patient; encrypting, by the computing system, the at least one item of patient-specific data into at least one item of encrypted patient-specific data; creating, by the computing system, a first personal medical record, comprising: (a) a first personal medical record hash at least comprising the first personal medical record's time and date of creation; (b) the at least one first item of encrypted patient-specific identification; and (c) at least one computer system-implementable instruction for linking a second personal medical record to the first personal medical record; storing, by the computing system, the first personal medical record on at least one node; generating, by the computing system, at least one matrix barcode, wherein the at least one matrix barcode is unique; assigning, by the computing system, one matrix barcode to one encrypted personal medical record, wherein the matrix barcode operates as a private key; assigning, by the computing system, the matrix barcode to a first electronic device associated with the patient; scanning, by at least one second electronic device, the matrix barcode; generating, by the at least one second electronic device, the authorization request to the computing system; sending, by the at least one second electronic device, the authorization request to the computing system; converting, by the computing system, the authorization request to an activation of the private key; decrypting, by the computing system, the at least one item of first encrypted patient-specific identification within the first personal medical record into at least one unencrypted item of patient-specific data; transmitting, by the computing system, at least one unencrypted item of patient-specific data to the at least one second electronic device; accessing, by the at least one second electronic device, the at least one unencrypted item o patient specific data; generating, by the at least one second electronic device, an update to the at least one unencrypted item of patient-specific data, wherein the update comprises a change to the unencrypted patient-specific data; sending, by the at least one second electronic device, the update to the computing system; receiving, by the computing system, the update; solving, by at least one node, the at least one computer system-implementable instruction for linking a second personal medical record to the first personal medical record as at least one solution; securely sharing, by the at least one node, the solution with at least one other node; combining, by the computing system, the update with the unencrypted patient-specific data into at least one item of unencrypted updated patient-specific data; encrypting, by the computing system, the at least one item of unencrypted updated patient specific data into at least one item of encrypted updated patient-specific data; creating, by the computing system, a second personal medical record, comprising: (a) a second personal medical record hash indicating, at least, the second personal medical record's time and date of creation; (b) the first personal medical record hash; (c) at least one item of encrypted updated patient-specific identification; and (d) at least one computer system-implementable instruction for linking another personal medical record to the current personal medical record; storing, by the computing system, the second personal medical record on at least one node.

2. The computer implemented method of claim 1, wherein the at least one unencrypted item of patient-specific data may only be accessed by one second electronic device at a time.

3. The computer implemented method of claim 1, wherein the at least one unencrypted item of patient-specific data may be accessed by more than one at least one second electronic device at a time.

4. The computer implemented method of claim 1, wherein the at least one second electronic device is configured to translate the at least one unencrypted item of patient-specific data into a specified language at the time of access.

5. The computer implemented method of claim 1, wherein: (a) the authorization request contains a language translation specification; (b) the computing system is configured to decrypt the at least one item of first encrypted patient-specific identification within the first personal medical record into at least one unencrypted item of translated patient-specific data, wherein the at least one unencrypted item of translated patient-specific data conforms to the language translation specification; (c) the computing system is configured to transmit the at least one unencrypted item of translated patient-specific data to the at least one second electronic device; and (d) the at least one second electronic device is configured to access the at least one unencrypted item of translated patient-specific data.

6. The computer implemented method of claim 1, wherein the update records access, but not alterations of, to the at least one unencrypted item of patient-specific data.

7. The computer implemented method of claim 1, wherein the update records access and alterations to the at least one unencrypted item of patient-specific data.

8. The computer implemented method of claim 1, wherein the at least one item of encrypted updated patient-specific data, when viewed by a node, is presented as deidentified patient-specific data.

9. The computer implemented method of claim 1, wherein the at least one item of encrypted updated patient-specific data, when viewed by a node is presented as unreadable patient-specific data.

10. A system for universally accessible personal medical records, comprising: at least one computing system distributed across a plurality of computer networking systems, wherein the plurality of computer networking systems comprises at least one node, wherein the at least one computing system is configured to: (a) receive at least one item of patient-specific data, wherein the at least one item of patient-specific data pertains to a patient; (b) encrypt the at least one item of patient-specific data into at least one item of encrypted patient-specific data; (c) create a first personal medical record, comprising: i. a first personal medical record hash comprising at least the first personal medical record's time and date of creation; ii. the at least one first item of encrypted patient-specific identification; and iii. at least one computer system-implementable instruction for linking a second personal medical record to the first personal medical record; (d) store the first personal medical record on at least one node; (e) generate at least one matrix barcode, wherein the at least one matrix barcode is unique; (f) assign one matrix barcode to one encrypted personal medical record, wherein the matrix barcode operates as a private key; (g) assign the matrix barcode to a first electronic device associated with the patient; (h) receive an authorization request from at least one second electronic device; (i) convert the authorization request to an activation of the private key; (j) decrypt the at least one item of first encrypted patient-specific identification within the first personal medical record into at least one unencrypted item of patient-specific data; (k) transmit the at least one unencrypted item of patient-specific data to the at least one second electronic device; (l) receive an update from the at least one second electronic device; (m) solve the at least one computer system-implementable instruction for linking a second personal medical record to the first personal medical record as at least one solution; (n) securely share the solution with at least one node of the computer networking system; (o) combine the update with the unencrypted patient-specific data into at least one item of unencrypted updated patient-specific data; (p) encrypt the at least one item of unencrypted updated patient-specific data into at least one item of encrypted updated patient-specific data; (q) create a second personal medical record, comprising: i. a second personal medical record hash comprising at least the second personal medical record's time and date of creation; ii. the first personal medical record hash; iii. at least one item of encrypted updated patient-specific identification; and iv. at least one computer system-implementable instruction for linking another personal medical record to the current personal medical record; and (r) store the second personal medical record on at least one node; wherein the first electronic device is configured to: (a) receive and store the matrix barcode; (b) associate the matrix barcode with the patient; and (c) display the matrix barcode on a screen; wherein the at least one second electronic device is configured to: (a) scan the matrix barcode from the screen; (b) generate the authorization request; (c) send the authorization request to the computing system; (d) access the at least one unencrypted item of patient-specific data; (e) generate the update to the at least one unencrypted item of patient-specific data, wherein the update comprises a change to the unencrypted patient-specific data; and (f) send the update to the computing system.

11. The system of claim 10, wherein the at least one unencrypted item of patient-specific data may only be accessed by one electronic device at a time.

12. The system of claim 10, wherein the at least one unencrypted item of patient-specific data may be accessed by more than one electronic device at a time.

13. The system of claim 10, wherein the at least one second electronic device is configured to translate the at least one unencrypted item of patient-specific data into a language at the time of access.

14. The system of claim 10, wherein: (a) the authorization request contains a language translation specification; (b) the at least one computing system is configured to decrypt the at least one item of first encrypted patient-specific identification within the first personal medical record into at least one unencrypted item of translated patient-specific data, wherein the at least one unencrypted item of translated patient-specific data conforms to the language translation specification; (c) the at least one computing system is configured to transmit the at least one unencrypted item of translated patient-specific data to the at least one second electronic device; and (d) the at least one second electronic device is configured to access the at least one unencrypted item of translated patient-specific data.

15. The system of claim 10, wherein the update records access to, but not alterations of, to the at least one unencrypted item of patient-specific data.

16. The system of claim 10, wherein the update records access and alterations to the at least one unencrypted item of patient-specific data.

17. The system of claim 10, wherein the at least one item of encrypted updated patient-specific data, when viewed by a node, is presented as deidentified patient-specific data.

18. The system of claim 10, wherein the at least one item of encrypted updated patient-specific data, when viewed by a node, is presented as unreadable patient-specific data.

19. An apparatus for universally accessible personal medical records, comprising: at least one computing system distributed across a decentralized electronic database, wherein the decentralized electronic database comprises at least one node, and wherein the at least one computing system is configured to: (a) receive at least one item of patient-specific data, wherein the at least one item of patient-specific data pertains to a patient; (b) encrypt the at least one item of patient-specific data into at least one item of encrypted patient-specific data; (c) create a first personal medical record, comprising: (i) at least one first storage instruction, wherein the at least one first storage instruction contains creation information for the first personal medical record and instructions for linking a second personal medical record to the first personal medical record; and (ii) the at least one first item of encrypted patient-specific identification; (d) store the first personal medical record on at least one node; (e) generate at least one matrix barcode, wherein the at least one matrix barcode is unique; (f) assign one matrix barcode to one encrypted personal medical record, wherein the matrix barcode operates as a private key; (g) assign the matrix barcode to a first electronic device associated with the patient; (h) receive an authorization request from at least one second electronic device; (i) convert the authorization request to an activation of the private key; (j) decrypt the at least one item of first encrypted patient-specific identification within the first personal medical record into at least one unencrypted item of patient-specific data; (k) transmit the at least one unencrypted item of patient-specific data to the at least one second electronic device; (l) receive an update from the at least one second electronic device; (m) combine the update with the unencrypted patient-specific data into at least one item of unencrypted updated patient-specific data; (n) encrypt the at least one item of unencrypted updated patient-specific data into at least one item of encrypted updated patient-specific data; (o) create a second personal medical record, comprising: (i) the at least one item of encrypted updated patient-specific identification; (ii) the creation information for the first personal medical record; and (iii) at least one second storage instruction, wherein the at least one second storage instruction contains creation information for the second personal medical record and instructions for linking a third personal medical record to the second personal medical record; (p) store the second personal medical record on at least one node; and (q) share the second personal medical record on at least one other node; wherein the first electronic device is configured to: (a) receive and store the matrix barcode; (b) associate the matrix barcode with the patient; and (c) display the matrix barcode on a screen; wherein the at least one second electronic device is configured to: (a) scan the matrix barcode from the screen; (b) generate the authorization request; (c) send the authorization request to the computing system; (d) access the at least one unencrypted item of patient-specific data; (e) generate the update to the at least one unencrypted item of patient-specific data, wherein the update comprises a change to the unencrypted patient-specific data; and (f) send the update to the computing system.

20. The apparatus of claim 19, wherein the creation information for the first personal medical record is a first hash and the creation information for the second personal medical record is a second hash.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0036] FIG. 1 is a block diagram of a networked environment in which an exemplary embodiment of a system for universally accessible personal medical records is implemented.

[0037] FIG. 2 illustrates an exemplary embodiment of a mobile device shown in FIG. 1.

[0038] FIG. 3 is a flowchart depicting an exemplary embodiment of a system for universally accessible personal medical records.

[0039] One embodiment of the invention is implemented as a program product for use with a computer system. The program(s) of the program product defines functions of the embodiments (including the methods described herein) and can be contained on a variety of computer-readable storage media. Illustrative computer-readable storage media include, but are not limited to: (i) non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM disks readable by a CD-ROM drive) on which information is permanently stored; (ii) writable storage media (e.g., floppy disks within a diskette drive or hard-disk drive) on which alterable information is stored. Such computer-readable storage media, when carrying computer-readable instructions that direct the functions of the present invention, are embodiments of the present invention. Other media include communications media through which information is conveyed to a computer, such as through a computer or telephone network, including wireless communications networks. The latter embodiment specifically includes transmitting information to/from the Internet and other networks. Such communications media, when carrying computer-readable instructions that direct the functions of the present invention, are embodiments of the present invention. Broadly, computer-readable storage media and communications media may be referred to herein as computer-readable media.

[0040] In general, the routines executed to implement the embodiments of the invention, may be part of an operating system or a specific application, component, program, module, object, or sequence of instructions. The computer program of the present invention typically is comprised of a multitude of instructions that will be translated by the native computer into a machine-readable format and hence executable instructions. Also, programs are comprised of variables and data structures that either reside locally to the program or are found in memory or on storage devices. In addition, various programs described hereinafter may be identified based upon the application for which they are implemented in a specific embodiment of the invention. However, it should be appreciated that any particular program nomenclature that follows is used merely for convenience, and thus the invention should not be limited to use solely in any specific application identified and/or implied by such nomenclature.

[0041] For simplicity and clarity of illustration, the drawing figures illustrate the general manner of construction, and descriptions and details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the invention. Additionally, elements in the drawing figures are not necessarily drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help improve understanding of embodiments of the present invention. The same reference numerals in different figures denote the same elements.

[0042] The terms first, second, third, fourth, and the like in the description and in the claims, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms include, and have, and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, device, or apparatus that comprises a list of elements is not necessarily limited to those elements, but may include other elements not expressly listed or inherent to such process, method, system, article, device, or apparatus.

[0043] The terms couple, coupled, couples, coupling, and the like should be broadly understood and refer to connecting two or more elements or signals, electrically, mechanically or otherwise. Two or more electrical elements may be electrically coupled, but not mechanically or otherwise coupled; two or more mechanical elements may be mechanically coupled, but not electrically or otherwise coupled; two or more electrical elements may be mechanically coupled, but not electrically or otherwise coupled. Coupling (whether mechanical, electrical, or otherwise) may be for any length of time, e.g., permanent or semi-permanent or only for an instant.

DETAILED DESCRIPTION

[0044] Having summarized various aspects of the present disclosure, reference will now be made in detail to that which is illustrated in the drawings. While the disclosure will be described in connection with these drawings, there is no intent to limit it to the embodiment or embodiments disclosed herein. Rather, the intent is to cover all alternatives, modifications and equivalents included within the spirit and scope of the disclosure as defined by the appended claims.

[0045] Because each PMR is an immutable copy stored in redundant form across the present invention's decentralized electronic database, neither the patient nor anyone else may easily alter the PMR's contents, including the electronic medical record within the PMR. As such, the present invention provides for a reliable, secure, patient-controlled, patient-managed electronic medical record and dossier that the authorized user may share with any medical professional(s) simply by allowing the medical professional(s) to scan the patient's QR code. The present invention also, in some embodiments, provides for the authorized user to be the caretaker of the PMR's contents, which enables universal access unrestricted by differences in electronic medical records software programs.

[0046] The present invention may provide for a system, method, and apparatus wherein a patient's medical history may begin at the patient's first medical visit, which could be while the patient was an infant. The present invention may provide that the patient's parents may monitor and control the PMR until the patient is eighteen years of age. At a typical medical visit, the present invention may provide that a medical professional may scan the patient's QR code and the patient may then share the PMR's contents with the medical professional(s). With each medical visit, the present invention may provide that the person in charge of the patient's PMR (either the patient or the patient's parents, if the patient is under eighteen years of age, collectively, the authorized user) may receive an updated electronic medical record from the medical provider, whereupon the authorized user may upload the updated electronic medical record into the PMR. At the next medical visit, or at any time the authorized user may choose, the authorized user may allow the next medical professional to access the PMR by allowing the medical professional to scan the patient's QR code and access the PMR's contents. The doctor may then update the electronic medical record, or provide other content, and the present invention may provide that the authorized user may receive the updated electronic medical record and other information, if applicable. As before, the authorized user may include the new information, including the updated electronic medical record, into the PMR. The next time the patient goes for another medical visit, the authorized user may allow the medical professional(s) access again, new patient-specific information may be created and shared with the authorized user, and the authorized user may cause a new PMR to be created as described elsewhere herein.

[0047] The present invention contemplates, in some embodiments, storage of patient-specific data, including but not limited to medical records, in a block chain-like system wherein a series of immutable records are stored across a variety of nodes that act as a cloud-like storage system. In some embodiments, the present invention may differ from some, but not all, block chain programs in that some embodiments may provide that the patient-specific medical data may be encrypted and may not be viewed by the public, the nodes, or persons with access to the nodes. In some embodiments, some but not all of the patient-specific data may be encrypted and subject to the viewing restrictions detailed herein. In some embodiments, the present invention may provide that a secure QR code may act as a patient's private key or password, and may be scanned by any medical professional in the world who has access to the present invention. When properly scanned, the present invention may provide some or all of the encrypted information to the medical professional from the authorized personal medical record, which may be the most recent personal medical record, the most recent personal medical record on the longest chain, or other personal medical record having the indicia of paramount reliability within the system and method. Once accessed, the present invention may provide that the medical professional or other person or entity having accessed the patient-specific data may be enabled to make one or more changes to the data, such as an update to the patient's record.

[0048] The present invention may comprise a system for universally accessible personal medical records. More specifically, in some embodiments, the present invention may provide for a non-transitory, tangible computer-readable medium having stored thereon computer-executable instructions, which, when executed by a computer processor, enable one or more computers coupled to a network to execute a system for universally accessible personal medical records, the method comprising configuring, by a computing system, at least one personal medical record chain-configured data bank distributed across a plurality of computer networking systems, wherein the plurality of computer networking systems comprises at least one node; receiving, by the computing system, at least one item of patient-specific data, wherein the at least one item of patient-specific data pertains to a patient; encrypting, by the computing system, the at least one item of patient-specific data into at least one item of encrypted patient-specific data; creating, by the computing system, a first personal medical record, comprising: (a) a first personal medical record hash at least comprising the first personal medical record's time and date of creation, (b) the at least one first item of encrypted patient-specific identification, and (c) at least one computer system-implementable instruction for linking a second personal medical record to the first personal medical record; storing, by the computing system, the first personal medical record on at least one node.

[0049] The method may further comprise the steps of generating, by the computing system, at least one matrix barcode, wherein the at least one matrix barcode is unique; assigning, by the computing system, one matrix barcode to one encrypted personal medical record, wherein the matrix barcode operates as a private key; assigning, by the computing system, the matrix barcode to a first electronic device associated with the patient; scanning, by at least one second electronic device, the matrix barcode; generating, by the at least one second electronic device, an authorization request; sending, by the at least one second electronic device, the authorization request to the computing system; converting, by the computing system, the authorization request to an activation of the private key; decrypting, by the computing system, the at least one item of first encrypted patient-specific identification within the first personal medical record into at least one unencrypted item of patient-specific data; transmitting, by the computing system, at least one unencrypted item of patient-specific data to the at least one second electronic device.

[0050] The method may further comprise the steps of accessing, by the at least one second electronic device, the at least one unencrypted item of patient-specific data; generating, by the at least one second electronic device, an update to the at least one unencrypted item of patient-specific data, wherein the update comprises a change to the unencrypted patient-specific data; sending, by the at least one second electronic device, the update to the computing system; receiving, by the computing system, the update; solving, by at least one node, the at least one computer system-implementable instruction for linking a second personal medical record to the first personal medical record as at least one solution; securely sharing, by the at least one node, the solution with at least one other node; combining, by the computing system, the update with the unencrypted patient-specific data into at least one item of unencrypted updated patient-specific data; encrypting, by the computing system, the at least one item of unencrypted updated patient-specific data into at least one item of encrypted updated patient-specific data.

[0051] The method may further comprise the steps of creating, by the computing system, a second personal medical record, comprising: (a) second personal medical record hash indicating, at least, the second personal medical record's time and date of creation, (b) the first personal medical record hash, (c) at least one item of encrypted updated patient-specific identification, and (d) at least one computer system-implementable instruction for linking another personal medical record to the current personal medical record; and storing, by the computing system, the second personal medical record on at least one node.

[0052] With continued respect to the method, in some embodiments the at least one unencrypted item of patient-specific data may only be accessed by one second electronic device at a time. In some embodiments, the at least one unencrypted item of patient-specific data may be accessed by more than one at least one second electronic device at a time.

[0053] With continued respect to the method, in at least one embodiment, the at least one second electronic device may be configured to translate the at least one unencrypted item of patient-specific data into a specified language at the time of access. In some embodiments, (a) the authorization request may contain a language translation specification; (b) the computing system may be configured to decrypt the at least one item of first encrypted patient-specific identification within the first personal medical record into at least one unencrypted item of translated patient-specific data, wherein the at least one unencrypted item of translated patient-specific data conforms to the language translation specification; (c) the computing system may be configured to transmit the at least one unencrypted item of translated patient-specific data to the at least one second electronic device; and (d) the at least one second electronic device may be configured to access the at least one unencrypted item of translated patient-specific data.

[0054] With continued respect to the method, in at least one embodiment, the update may record access to, but not alterations of, to the at least one unencrypted item of patient-specific data. In some embodiments, the update may record access and alterations to the at least one unencrypted item of patient-specific data.

[0055] With continued respect to the method, in at least one embodiment, the at least one item of encrypted updated patient-specific data, when viewed by a node, may be presented as deidentified patient-specific data. In some embodiments, the at least one item of encrypted updated patient-specific data, when viewed by a node, may be presented as anonymous patient-specific data.

[0056] The present invention may comprise a system for universally accessible personal medical records. In some embodiments, the system may comprise at least one computing system distributed across a plurality of computer networking systems, wherein the plurality of computer networking systems comprises at least one node, wherein the at least one computing system is configured to (a) receive at least one item of patient-specific data, wherein the at least one item of patient-specific data pertains to a patient; (b) encrypt the at least one item of patient-specific data into at least one item of encrypted patient-specific data; (c) create a first personal medical record, comprising: (i) a first personal medical record hash comprising at least the first personal medical record's time and date of creation, (ii) the at least one first item of encrypted patient-specific identification, and (iii) at least one computer system-implementable instruction for linking a second personal medical record to the first personal medical record; (d) store the first personal medical record on at least one node; (e) generate at least one matrix barcode, wherein the at least one matrix barcode is unique; (f) assign one matrix barcode to one encrypted personal medical record, wherein the matrix barcode operates as a private key; (g) assign the matrix barcode to a first electronic device associated with the patient; (h) receive an authorization request from at least one second electronic device; (I) convert the authorization request to an activation of the private key; (j) decrypt the at least one item of first encrypted patient-specific identification within the first personal medical record into at least one unencrypted item of patient-specific data; (k) transmit the at least one unencrypted item of patient-specific data to the at least one second electronic device; (l) receive an update from the at least one second electronic device; (m) solve the at least one computer system-implementable instruction for linking a second personal medical record to the first personal medical record as at least one solution; (n) securely share the solution with at least one node of the computer networking system; (o) combine the update with the unencrypted patient-specific data into at least one item of unencrypted updated patient-specific data; (p) encrypt the at least one item of unencrypted updated patient-specific data into at least one item of encrypted updated patient-specific data; (q) create a second personal medical record, comprising (i) a second personal medical record hash comprising at least the second personal medical record's time and date of creation, (ii) the first personal medical record hash, (iii) at least one item of encrypted updated patient-specific identification, and (iv) at least one computer system-implementable instruction for linking another personal medical record to the current personal medical record; and (r) store, by the computing system, the second personal medical record on at least one node

[0057] In some embodiments, the system may provide that the first electronic device may be configured to, at least, (a) receive and store the matrix barcode; (b) associate the matrix barcode with the patient; and (c) display the matrix barcode on a screen;

[0058] In some embodiments, the system may provide that the at least one second electronic device may be configured to: (a) scan the matrix barcode from the screen; (b) generate the authorization request; (c) send the authorization request to the computing system; (d) access the at least one unencrypted item of patient-specific data; (e) generate the update to the at least one unencrypted item of patient-specific data, wherein the update comprises a change to the unencrypted patient-specific data; and (f) send the update to the computing system.

[0059] With continued respect to the system, in some embodiments the at least one unencrypted item of patient-specific data may only be accessed by one electronic device at a time. In some embodiments, the at least one unencrypted item of patient-specific data may be accessed by more than one electronic device at a time.

[0060] With continued respect to the system, in some embodiments the at least one second electronic device may be configured to translate the at least one unencrypted item of patient-specific data into a specified language at the time of access. In some embodiments (a) the authorization request may contain a language translation specification, (b) the at least one computing system may be configured to decrypt the at least one item of first encrypted patient-specific identification within the first personal medical record into at least one unencrypted item of translated patient-specific data, wherein the at least one unencrypted item of translated patient-specific data conforms to the language translation specification, (c) the at least one computing system may be configured to transmit the at least one unencrypted item of translated patient-specific data to the at least one second electronic device; and (d) the at least one second electronic device may be configured to access the at least one unencrypted item of translated patient-specific data.

[0061] With continued respect to the system, in some embodiments the update may record access to, but not alterations of, to the at least one unencrypted item of patient-specific data. In some embodiments, the update may record access and alterations to the at least one unencrypted item of patient-specific data.

[0062] With continued respect to the system, in some embodiments the at least one item of encrypted updated patient-specific data, when viewed by a node, may be presented as deidentified patient-specific data. In some embodiments, the at least one item of encrypted updated patient-specific data, when viewed by a node, may be presented as anonymous patient-specific data.

[0063] The present invention may comprise an apparatus for universally accessible personal medical records. In some embodiments, the apparatus may comprise at least one computing system distributed across a decentralized electronic database, wherein the decentralized electronic database comprises at least one node, and wherein the at least one computing system is configured to: a) receive at least one item of patient-specific data, wherein the at least one item of patient-specific data pertains to a patient; b) encrypt the at least one item of patient-specific data into at least one item of encrypted patient-specific data; c) create a first personal medical record, comprising i) at least one first storage instruction, wherein the at least one first storage instruction contains creation information for the first personal medical record and instructions for linking a second personal medical record to the first personal medical record; and ii) the at least one first item of encrypted patient-specific identification; d) store the first personal medical record on at least one node; e) generate at least one matrix barcode, wherein the at least one matrix barcode is unique; f) assign one matrix barcode to one encrypted personal medical record, wherein the matrix barcode operates as a private key; g) assign the matrix barcode to a first electronic device associated with the patient; h) receive an authorization request from at least one second electronic device; i) convert the authorization request to an activation of the private key; j) decrypt the at least one item of first encrypted patient-specific identification within the first personal medical record into at least one unencrypted item of patient-specific data; k) transmit the at least one unencrypted item of patient-specific data to the at least one second electronic device; l) receive an update from the at least one second electronic device; m) combine the update with the unencrypted patient-specific data into at least one item of unencrypted updated patient-specific data; n) encrypt the at least one item of unencrypted updated patient-specific data into at least one item of encrypted updated patient-specific data; o) create a second personal medical record, comprising: i) the at least one item of encrypted updated patient-specific identification; ii) the creation information for the first personal medical record; and iii) at least one second storage instruction, wherein the at least one second storage instruction contains creation information for the second personal medical record and instructions for linking a third personal medical record to the second personal medical record; p) store the second personal medical record on at least one node; and q) share the second personal medical record on at least one other node.

[0064] With continued respect to the apparatus, the first electronic device may be configured to: a) receive and store the matrix barcode; b) associate the matrix barcode with the patient; and c) display the matrix barcode on a screen.

[0065] With continued respect to the apparatus, the at least one second electronic device may be configured to: a) scan the matrix barcode from the screen; b) generate the authorization request; c) send the authorization request to the computing system; d) access the at least one unencrypted item of patient-specific data; e) generate the update to the at least one unencrypted item of patient-specific data, wherein the update comprises a change to the unencrypted patient specific data; and f) send the update to the computing system.

[0066] FIG. 1 illustrates an exemplary embodiment of the present invention which includes a plurality of electronic devices communicatively coupled to one another. By way of example, and not limitation, FIG. 1 illustrates mobile devices 102, 104, and 106, and desktop computer 103 that incorporate a system for universally accessible personal medical records 101 and are communicatively coupled via a personal medical record chain-configured database 108. Each of the mobile devices may be embodied as a mobile computing device such as, for example and without limitation, a smartphone or tablet computer that incorporates cellular telephone functionality. Notably, the communications network can use one or more of various communications types such as, for example and without limitation, cellular and Wi-Fi communications. In some embodiments, one or more nodes (not pictured) may take the place of one or more of mobile devices 102, 104, and 106, and desktop computer 103.

[0067] Users of desktop computer 103 and mobile devices 102, 104, and 106 may be users of at least one network 110 known to those skilled in the art. For instance, as noted above, network 110 may comprise a peer-to-peer network, a cloud-based computing network, a fog computing network, a blockcloud computing network, or any other network 110 known in the art capable of secure data transfer. In some embodiments, network 110 may be facilitated by a website that may require a registration and login prior to use.

[0068] In one embodiment, a PMR may be stored in multiple copies across personal medical record chain-configured database 108 on one or more nodes (not pictured). In some embodiments, each node may contain and run the software, hardware, firmware, or any other component necessary, to run the present invention. More specifically, each node may provide for a computer system that can run the program of the present invention, create, store, and link (or chain) PMRs to other PMRs. Each node may also provide for computational power sufficient to perform hash functions, other one-way encryption functions, two-way encryption functions, public key encryption functions and programs, symmetric encryption and symmetric key encryption functions and programs, along with any other function that may be used or provided for by the present invention.

[0069] In brief, the original or genesis PMR may comprise, at least, a hash that records a timestamp representing the PMR's creation date and time (along with, in some embodiments, other information), encrypted patient-specific data, and instructions for the linking of the second PMR to the present PMR. In some embodiments, the instructions may comprise a mathematical problem to be solved. In some embodiments, system for universally accessible personal medical records 101 may provide that the solution is provided to one or more nodes in personal medical record chain-configured database 108. In some embodiments, some or all of the nodes in personal medical record chain-configured database 108 may be equally able to solve the instructions, and therefore some or all of the nodes may discover the solution at roughly the same time, thus ensuring uniformity of record-keeping across personal medical record chain-configured database 108. Additional PMRs may be linked to the genesis personal medical record, and may comprise a new timestamp hash unique to that personal medical record, the previous personal medical record's hash, encrypted updated patient-specific data, and instructions for the next personal medical record as detailed above.

[0070] As described elsewhere in more detail herein, personal medical record chain-configured database 108 may be configured to associate a PMR, and the patient-specific data within the PMR, with a QR code. In some embodiments, the QR code may be stored on any or several of desktop computer 103 and mobile devices 102, 104, and 106. In some embodiments, the QR code may be displayed on at least one of desktop computer 103 and mobile devices 102, 104, and 106. The QR code thus displayed may be scanned by at least one of desktop computer 103 and mobile devices 102, 104, and 106, or by a different scanning device such as a hand-held scanner configured to work with the present invention (not pictured).

[0071] In some embodiments, the present invention may provide that one or more of desktop computer 103 and mobile devices 102, 104, and 106 may serve as a first electronic device. In such a configuration, one or more of desktop computer 103 and/or mobile devices 102, 104, and 106 may be configured to display a QR code (or matrix code elsewhere herein). The QR code may, in some embodiments, be used as a patient's private key and may, when scanned from the display of the first electronic device, cause the present invention to unlock, decrypt, or otherwise permit access to one or more items of patient-specific data.

[0072] FIG. 2 illustrates at least one node 201, wherein each node 201 may, in some embodiments, comprise a networked computer system within personal medical record chain-configured database 108. In some embodiments, mobile devices 102, 104, and 106, and desktop computer 103 may, in addition to their roles as either a first electronic device or a second electronic device, may alternatively or simultaneously comprise at least one node 201.

[0073] In the embodiment depicted in FIG. 2, node 201 may comprise, at least, at least one processing device (processor) 202, at least one input/output interface 204, at least one display 206, at least one user interface 208, at least one network interface 210, at least one memory 212, at least one operating system 214, at least one mass storage 216 and at least one GPS 218, with each communicating across a local data bus 232. Additionally, at least one node 201 may create and store at least one patient medical record (PMR) 226 that may comprise, at least, one or more hash(s) 220, one or more items of patient-specific data 222, and at least one element of storage information 224. In some embodiments, node 201 may communicate with other node(s) 228 via one or more networks (not shown in FIG. 2). Additionally, an individual QR code 230 may act as a private key that may enable one or more nodes 201 to access patient-specific data 222 in an unencrypted or deidentified, or both, form.

[0074] FIG. 2 also discloses additional roles of QR code 230. In some embodiments, a user may select, using sequences described elsewhere herein, whether QR code 230 will act as the key for PMR 226, social security number (SSN) 232, or Universal Patient ID (UPID) 234. As noted in FIG. 2, these operations are contemplated to be distinct function such that if QR code 230 is accessed in relationship to SSN 232, for example, the user is not inadvertently also decrypting or displaying PMR 226 or UPID 234. In some embodiments, the security of QR code 230 itself together with the fact that the decryption sequences of QR code 230 and PMR 226, SSN 232, and UPID 234 are separate, reflects one of many sources of data security in the present invention. Additionally, in some embodiments and as described above, QR code 230 may itself be or substitute for an individual's SSN 230.

[0075] As the present invention contemplated a distributed personal medical record chain computer system wherein each node 201 may communicate with one or more nodes 102, and in some embodiments all other nodes 102, one or more elements of node 201 may be absent in any particular node 201 or shared across one or more nodes 102. In some embodiments, while it is contemplated that, generally although not required in every case, each node 201 may store a copy of all PMR 226 chains across the entire present invention, thereby creating a network of nearly-unhackable computing systems and complete redundancy, one or more other elements may be partially stored on one or more nodes 102, or stored on one node 201 but accessed by another node 201. By way of illustration and not limitation, memory 212 and/or operating system 214 may be partially stored across several nodes 102 but accessed by multiple nodes 102, or may be stored on one or more nodes 102 and accessed by nodes 102 that do not have their own memory 212 and/or operating system 214.

[0076] The processing device 202 may include any custom made or commercially available processor, a central processing unit (CPU) or an auxiliary processor among several processors associated with node 201, a semiconductor based microprocessor (in the form of a microchip), a macroprocessor, one or more application specific integrated circuits (ASICs), a plurality of suitably configured digital logic gates, and other electrical configurations comprising discrete elements both individually and in various combinations to coordinate the overall operation of the system.

[0077] The memory 212 can include any one of a combination of volatile memory elements (e.g., random-access memory (RAM, such as DRAM, and SRAM, etc.)) and nonvolatile memory elements. The memory typically comprises native operating system 214, one or more native applications, emulation systems, or emulated applications for any of a variety of operating systems and/or emulated hardware platforms, emulated operating systems, etc. For example, the applications may include application specific software which may comprise some or all the components of node 201. In accordance with such embodiments, the components are stored in memory and executed by the processing device. Note that although depicted separately in FIG. 2, the system, method, and apparatus for universally accessible personal medical records 100 may be resident in memory such as memory 212. As mentioned above, in some embodiments, one or more nodes 102 may not have their own memory 212 and/or operating system 214 or may store incomplete memory 212 and/or operating system 214, and may therefore draw upon other nodes 102 for use of one or more memory units 212 and/or operating system elements 214 via node 201 to node 201 communication 228, as discussed herein.

[0078] User interface 208 may be configured to detect contact within the display area of the display 206 and may provide such functionality as on-screen buttons, menus, keyboards, etc. that allows users to navigate user interfaces by touch. User interface 208 may also be a keyboard, a mouse, a microphone, a vision tracking system, a motion-capture system, a trackball, or any other known interface with a computing system. For some embodiments, node 201 may also comprise GPS 218 or other means to determine the location of the node 201.

[0079] One of ordinary skill in the art will appreciate that the operating system 214 can, and typically will, comprise other components which have been omitted for purposes of brevity. Note that in the context of this disclosure, a non-transitory computer-readable medium stores one or more programs for use by or in connection with an instruction execution system, apparatus, or device. With further reference to FIG. 2, network interface device 210 comprises various components used to transmit and/or receive data over a networked environment such as depicted in FIG. 1. When such components are embodied as an application, the one or more components may be stored on a non-transitory computer-readable medium and executed by the processing device.

[0080] As discussed elsewhere in the present disclosure, patient-specific data 222 may be viewed by a user, the node 201, or other nodes 102 in several forms, among them an unencrypted form, an encrypted but readable form having patient-identifying information, an encrypted but readable form displaying deidentified patient-specific data, encrypted and unintelligible patient-specific data 222, or any other form or copy of patient-specific data 222. By way of illustration and not limitation, in some embodiments, an unencrypted copy of patient-specific data 222 may be available to a user who has accessed the patient's QR code 230 or other private key interface. When existing on the present invention's personal medical record chain database 108, patient-specific data 222 may exist in any form discussed herein or known in the art, including any level of encryption or deidentification, or no encryption or deidentification.

[0081] In some embodiments, patient-specific data 222 may be stored in one language, generally the patient's native language. In some embodiments, however, the present invention may provide, through memory 212 or any other element of the present invention including elements known to the art but not disclosed in FIG. 2, that the patient-specific data 222 may be translated into a selected language by the end user, such as by way of illustration and not limitation, a healthcare provider. For example, the present invention may provide that patient-specific data 222 may be stored in English, but when accessed by a user, by using one or more of mobile device(s) 102, 104, 106 or desktop computer 103 to access patient-specific data 222 via QR code 230, the patient-specific data 222 may be translated into the language of the accessing device, here mobile device(s) 102, 104, 106 or desktop computer 103. This change may be automated in some embodiments, and may save users such as healthcare professionals valuable time.

[0082] Storage information 224, as discussed in more detail herein, are generally contemplated to comprise a mathematical problem to be solved. Once a node 201 has reached the solution, the next block may be linked or chained to the present PMR 226, creating the personal medical record chain known in the art. Such chaining may comprise, in some embodiments, recording the hash of a first PMR 226 in or on a second PMR 226. In some embodiments, therefore, the chain may be traced by examining the corresponding hashes of each PMR 226 to make sure that they match as intended.

[0083] Continuing with FIG. 2, the genesis PMR 226 may provide for only one hash(s) 220 that may comprise a timestamp (at least) hash of its creation. For all other PMRs 226, hash(s) 220 may comprise a timestamp (at least) hash 220 of the creation of the present PMR 226 as well as the hash 220 of the previous PMR 226.

[0084] As discussed elsewhere herein, each PMR 226 may comprise, at least, one or more hash(s) 220, one or more items of patient-specific data 222, and one or more storage information 224. In some embodiments, an identical copy of each PMR 226 may be stored on one or more nodes 201. In some embodiments, an identical copy of each PMR 226 may be stored on each node 201.

[0085] Remaining with FIG. 2, the present invention may be, and is contemplated generally to be, configured such that one or more nodes 201 may communicate with each other 228. The node 201 to node 201 communication system 228 provides for and enables one or more redundancy and/or data security protections of the present invention. Using node 201 to node 201 communication system 228, one or more nodes 201 of the present invention may all update one or more PMRs 226 and PMR 226 chains, hashes 220, copies of patient-specific data 222, and any other element that the present invention may store on a node 201. One or more nodes 201 may utilize node 201 to node 201 communication system 228 to share one or more storage information 224, thereby enabling one or more nodes to chain a new PMR 226 to a previous PMR 226. Additionally, one or more nodes 201 may utilize node 201 to node 201 communication system 228 to share one or more node 201 elements, such as but not limited to, part or all of a node's 201 at least one processing device (processor) 202, at least one input/output interface 204, at least one display 206, at least one user interface 208, at least one network interface 210, at least one memory 212, at least one operating system 214, at least one mass storage 216, at least one GPS 218, and/or at least one local data bus 232.

[0086] In some embodiments, a QR code 230 may be used by the present invention as a private key. In some embodiments, when a healthcare provider scans a patient's QR code 230, such as by way of illustration by using one or more of mobile devices 102, 104, 106 and/or desktop computer 103, the present invention may provide one or more items of patient-specific data 222 to the healthcare professional in an unencrypted form, or a form having a mixture of encrypted and intelligible patient-specific data 222. In some embodiments, the health care provider may access the full PMR 226 and a fully unencrypted or fully intelligible record of the patient-specific data 222. In some embodiments, only one QR code 230 may be used at a time, and in some embodiments, only by the authorized user of mobile device(s) 102, 104, 106 or desktop computer 103 who initiated access via the QR code 230 in the first place. In some embodiments, the patient's QR code 230 may be used by more than one mobile device 102, 104, 106 or desktop computer 103 at a time. It is contemplated that the patient may be able to set preferences within the present invention, or utilize a secondary document such as a wallet card, to determine who or what may utilize the patient's QR code 230, in what manner, and to what extent.

[0087] The present invention may provide that when a QR code 230 is utilized to access a patient's PMR 226, the present invention initiate storage information 224 to create a new hash 220 within a new PMR 226 that links to the accessed PMR 226, in the manner known in the block chain database art and generally described herein. By creating a linked series of chained PMRs 226, it is contemplated that the present invention may provide a secure chain of medical history information.

[0088] In FIG. 2, data is shown progressing both directions between data bus 232 and PMR 226 through QR code 230. In some embodiments, this bidirectional arrow is meant not to connote that the QR code 230 itself transfers data back and forth, but rather that, generally, PMR 226 may in some embodiments be stored within node 201 and may communicate with data bus 232. In some embodiments, the role of QR code 230 is one-directional, wherein a user via mobile device(s) 102, 104, 106 or desktop computer 103 may utilize QR code 230 to access PMR 226, whereupon data bus 232 or any other element of node 201 may transfer one or more elements of patient-specific data 222 from PMR 226 to the user's electronic device, such as but not limited to mobile device(s) 102, 104, 106 or desktop computer 103.

[0089] In order to facilitate the aforementioned functionality, various aspects may be performed by one or more of desktop computer 103 and/or mobile devices 102, 104, and 106, or any node 201 which may be but is not limited to desktop computer 103 and/or mobile devices 102, 104, and 106. In one embodiment, the desktop 103, mobile devices 102, 104, and 106, and/or any node 201 are operative to perform, at least in part, the method depicted in the flowchart of FIG. 3 and described above.

[0090] Turning attention to FIG. 3, an exemplary system for universally accessible personal medical records is disclosed. First, a user may scan a QR code 301 that has been keyed to an individual's PMR 226 as disclosed elsewhere herein. Next, the present invention may generate an authorization request and may send the authorization request to at least one node 302. The at least one node may evaluate whether the QR code associated with the authorization request matches the PMR 226 as the PMR's 226 private key 303.

[0091] If the authorization request and the QR code associated with the authorization request do not match with the PMR 226, the present invention may deny access 304 to the PMR 226. If the authorization request does match with the PMR 226 in question, the present invention may transmit either partially or entirely unencrypted patient-specific data to the user 305.

[0092] The present invention may then analyze whether the patient-specific data is merely viewed, or if it has been changed 306 by the user. If the patient-specific data was only viewed, or if the only change was that the patient-specific data was viewed, the present invention may create a new PMR 226 recording that the patient-specific data was viewed and not altered 307, and may do so via at least one sequence described elsewhere herein. In some embodiments, the patient or authorized user may control if and when a new PMR 226 is created recording the view-only action. The PMR 226 recording access-only may include chaining instructions for the next PMR 226.

[0093] If, however, the user does change or alter one or more item of patient-specific data 308 in the PMR 226, the present invention may update and store the new patient-specific data 308, in some embodiments, as an updated complete record of the patient-specific data 308. The present invention may also create a new PMR 226, wherein the PMR 226 records updated patient-specific data 309, and in some embodiments, also records the fact that a change was made to the patient-specific data the changes to the patient-specific data. In some embodiments, the patient or authorized user may control if and when a new PMR 226 is created recording the viewing and changes to patient-specific data 308. The PMR 226 containing the updated patient-specific data and the fact of the changes may include chaining instructions for the next PMR 226.

[0094] The present invention may also provide that the new PMR 226 of either scenario (the viewed but not changed PMR 226 of step 307 or the PMR 226 including the updated patient-specific data of step 309) may be stored in identical copies across at least one more node 310 as described in more detail elsewhere herein. It is contemplated that, in some embodiments, the above-described method may be performed on any node. In other embodiments, one or more nodes may perform the method and share 310 the new PMR 226 with nodes not designated to perform the above-described method, but are configured to house, chain, and store one or more PMRs 226.

[0095] If embodied in software, it should be noted that each block depicted in the accompanying flowcharts represents a module, segment, or portion of code that comprises program instructions stored on a non-transitory computer readable medium to implement the specified logical function(s). In this regard, the program instructions may be embodied in the form of source code that comprises statements written in a programming language or machine code that comprises numerical instructions recognizable by a suitable execution system such as desktop 103, mobile devices 102, 104, and 106, and/or any node 201. The machine code may be converted from the source code, etc. If embodied in hardware, each block may represent a circuit or a number of interconnected circuits to implement the specified logical function(s).

[0096] It should be emphasized that the above-described embodiments are merely examples of possible implementations. Many variations and modifications may be made to the above-described embodiments without departing from the principles of the present disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.

[0097] Moreover, embodiments and limitations disclosed herein are not dedicated to the public under the doctrine of dedication if the embodiments and/or limitations: (1) are not expressly claimed in the claims; and (2) are or are potentially equivalents of express elements and/or limitations in the claims under the doctrine of equivalents.

CONCLUSIONS, RAMIFICATIONS, AND SCOPE

[0098] While certain embodiments of the invention have been illustrated and described, various modifications are contemplated and can be made without departing from the spirit and scope of the invention. Accordingly, it is intended that the invention not be limited, except as by the appended claim(s).

[0099] The teachings disclosed herein may be applied to other systems, and may not necessarily be limited to any described herein. The elements and acts of the various embodiments described above can be combined to provide further embodiments. All of the above patents and applications and other references, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions and concepts of the various references described above to provide yet further embodiments of the invention.

[0100] Particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being refined herein to be restricted to any specific characteristics, features, or aspects of the present invention with which that terminology is associated. In general, the terms used in the following claims should not be constructed to limit the present invention to the specific embodiments disclosed in the specification unless the above description section explicitly define such terms. Accordingly, the actual scope encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosed present invention. The above description of embodiments of the present invention is not intended to be exhaustive or limited to the precise form disclosed above or to a particular field of usage.

[0101] While specific embodiments of, and examples for, the present invention are described above for illustrative purposes, various equivalent modifications are possible for which those skilled in the relevant art will recognize.

[0102] While certain aspects of the present invention are presented below in particular claim forms, various aspects of the present invention are contemplated in any number of claim forms. Thus, the inventor reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the present invention.