From e4f9ba4883fcdfc2fe9644cc140f7460796f1568 Mon Sep 17 00:00:00 2001 From: Vitor Pamplona Date: Sun, 12 Mar 2023 20:52:13 -0400 Subject: [PATCH] Fixing Code blocks --- 82.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/82.md b/82.md index 9bf48c0..b336922 100644 --- a/82.md +++ b/82.md @@ -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