Distributed healthcare records management
US-2017300627-A1 · Oct 19, 2017 · US
US10735202B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10735202-B2 |
| Application number | US-201715657597-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 24, 2017 |
| Priority date | Jul 24, 2017 |
| Publication date | Aug 4, 2020 |
| Grant date | Aug 4, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An example operation may include one or more of storing a user profile in a blockchain by an authorized member of the blockchain, receiving a request by another authorized member of the blockchain to access the user profile, identifying the request for the user profile is from the another authorized member of the blockchain, creating a signed message that includes consent to share the user profile with the another authorized member of the blockchain, and transmitting the signed message to the another authorized member of the blockchain, and wherein an exchange of the user profile between the blockchain members is performed without revealing blockchain member identities of the authorized member of the blockchain and the another authorized member of the blockchain to any of the blockchain members.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: sending, via a device associated with a first authorized user of a blockchain, a request to a second authorized member of the blockchain to access an encrypted user profile stored on the blockchain, wherein both the first authorized user and the second authorized user use corresponding transaction certificates providing corresponding pseudo-identities that are different than corresponding actual identifies of the first authorized user and the second authorized member, so that an exchange of information associated with the encrypted user profile does not reveal the actual identifies of the first authorized user and the second authorized member to other members of the blockchain, except for auditor blockchain members, and wherein the request includes the corresponding single use identity of the first authorized member and proof that the first authorized member owns the corresponding single use identity; receiving, via the device, and in response to an identification by the second authorized member that the request is from the first authorized member, a signed consent to share the user profile with the first authorized member of the blockchain based on the corresponding single use identity, and the signed message further including a key of the corresponding transaction certificate of the first authorized member; sending, via the device, the signed consent to the blockchain for verification by the blockchain; receiving, via the device, encrypted information associated with the encrypted user profile and an encrypted decryption key in response to verification by the blockchain; decrypting, via the device, the encrypted decryption key to access the encrypted information using the key of the corresponding transaction certificate. 2. The method of claim 1 , wherein the first authorized member of the blockchain and the second authorized member of the blockchain use the pseudo-identities while performing one or more of submitting, requesting, consenting and accessing the user profile. 3. The method of claim 1 , wherein the consent comprises read and write access to the user profile. 4. The method of claim 1 , wherein the second authorized member of the blockchain is different from an authorized member of the blockchain that created the user profile. 5. A device associated with a first authorized user of a blockchain, the device comprising: a processor configured to: send a request to a second authorized member of the blockchain to access an encrypted user profile stored on the blockchain, wherein both the first authorized user and the second authorized user use corresponding transaction certificates providing corresponding pseudo-identities that are different than corresponding actual identifies of the first authorized user and the second authorized member, so that an exchange of information associated with the encrypted user profile does not reveal the actual identifies of the first authorized user and the second authorized member to other members of the blockchain, except for auditor blockchain members, and wherein the request includes the corresponding single use identity of the first authorized member and proof that the first authorized member owns the corresponding single use identity; receive, via a receiver of the device, and in response to an identification by the second authorized member that the request is from the first authorized member, a signed consent to share the user profile with the first authorized member of the blockchain based on the corresponding single use identity, and the signed message further including a key of the corresponding transaction certificate of the first authorized member; send, via a transmitter of the device, the signed consent to the blockchain for verification by the blockchain; receive, via the receiver, encrypted information associated with the encrypted user profile and an encrypted decryption key in response to verification by the blockchain; decrypt the encrypted decryption key to access the encrypted information using the key of the corresponding transaction certificate. 6. The apparatus of claim 5 , wherein the first authorized member of the blockchain and the second authorized member of the blockchain use the pseudo-identities while performing one or more of submitting, requesting, consenting and accessing the user profile. 7. The apparatus of claim 5 , wherein the consent comprises read and write access to the user profile. 8. The apparatus of claim 5 , wherein second authorized member of the blockchain is different from an authorized member of the blockchain that created the user profile. 9. A non-transitory computer readable storage medium configured to store one or more instructions that when executed by a processor cause the processor to perform: sending, via a device associated with a first authorized user of a blockchain, a request to a second authorized member of the blockchain to access an encrypted user profile stored on the blockchain, wherein both the first authorized user and the second authorized user use corresponding transaction certificates providing corresponding pseudo-identities that are different than corresponding actual identifies of the first authorized user and the second authorized member, so that an exchange of information associated with the encrypted user profile does not reveal the actual identifies of the first authorized user and the second authorized member to other members of the blockchain, except for auditor blockchain members, and wherein the request includes the corresponding single use identity of the first authorized member and proof that the first authorized member owns the corresponding single use identity; receiving, via the device, and in response to an identification by the second authorized member that the request is from the first authorized member, a signed consent to share the user profile with the first authorized member of the blockchain based on the corresponding single use identity, and the signed message further including a key of the corresponding transaction certificate of the first authorized member; sending, via the device, the signed consent to the blockchain for verification by the blockchain; receiving, via the device, encrypted information associated with the encrypted user profile and an encrypted decryption key in response to verification by the blockchain; decrypting, via the device, the encrypted decryption key to access the encrypted information using the key of the corresponding transaction certificate. 10. The non-transitory computer readable storage medium of claim 9 , wherein the first authorized member of the blockchain and the second authorized member of the blockchain use the pseudo-identities while performing one or more of submitting, requesting, consenting and accessing the user profile. 11. The non-transitory computer readable storage medium of claim 9 , wherein the consent comprises read and write access to the user profile. 12. The non-transitory computer readable storage medium of claim 9 , wherein the second authorized member of the blockchain is different from an authorized member of the blockchain that created the user profile.
using hash chains, e.g. blockchains or hash trees · CPC title
Anonymization, e.g. involving pseudonyms · CPC title
involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title
involving digital signatures · CPC title
Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.