nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-23 08:55:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fixing Code blocks

Browse Source
This commit is contained in:
Vitor Pamplona 2023-03-12 20:52:13 -04:00
parent 84df78894e
commit e4f9ba4883
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
82.md
View File

@ -71,6 +71,7 @@ The `d` tag must be equal to the FHIR resource id and the author of the event mu
A 5th parameter per `e` tag contains the secret to decode the `.content`, encrypted to the pubkey of each `e` hex. By default, the contents of a resource are available to all cited in the FHIR resource. From the sender's perspective, the secret is stored in an `e` tag with the sender's public key. Secrets are thus not saved anywhere else but in the message itself.
```json
{
"kind": 32225,
"created_at": 1675642635,
@ -85,6 +86,7 @@ A 5th parameter per `e` tag contains the secret to decode the `.content`, encryp
"pubkey": "...",
"id": "..."
}
```
The collection of such event kinds will assemble a medical record.
@ -94,6 +96,7 @@ If the patient wishes to share it's record with another Nostr user (say another
The `.content` of the secret sharing event is the encrypted secret using the public key of the receiver. The `a` references the resource the receiver is obtaining access to and the `e` tag contains the receiver's public key.
```json
{
"kind": 32226,
"created_at": 1675642635,
@ -106,6 +109,7 @@ The `.content` of the secret sharing event is the encrypted secret using the pub
"pubkey": "...",
"id": "..."
}
```
### Security