reidsomethings on Nostr: My Nostr EHR has relied on a consistent websocket connection but if the connection is ...
My Nostr EHR has relied on a consistent websocket connection but if the connection is lost the EHR disconnects and becomes useless until it reconnects. Today I added a caching systeming that allows the FHIR condition resources like labs, imaging, problem list, etc. to load immediately by pulling locally from an indexed database. Modified the connection indicator to show whether the EHR is caching or connected. Then did some bug fixes. Tonight phase 2, will be working on the write queue, that will queue outbound events (like encounter records) to be indexed while offline. To then eventually flush the queue when back online.
Published at
2026-02-26 01:36:00 UTCEvent JSON
{
"id": "df81833f5b106d7c40d18b81872e779c4dff3a4343f253a596f74dff1be810fa",
"pubkey": "f20e14c6717638aafefc4d1cd52b0bab170ec56186c5e9e37a3bf80356d7008b",
"created_at": 1772069760,
"kind": 1,
"tags": [],
"content": "My Nostr EHR has relied on a consistent websocket connection but if the connection is lost the EHR disconnects and becomes useless until it reconnects. Today I added a caching systeming that allows the FHIR condition resources like labs, imaging, problem list, etc. to load immediately by pulling locally from an indexed database. Modified the connection indicator to show whether the EHR is caching or connected. Then did some bug fixes. Tonight phase 2, will be working on the write queue, that will queue outbound events (like encounter records) to be indexed while offline. To then eventually flush the queue when back online.",
"sig": "9562c8428b9fd4711eec494980dbea338bb5f0b3e3d7ad4be4eb379c2a2f445a0be59f5b8ae74f4376136c5a02b4642ae6c4074a776116e34ce568b17856876e"
}
