heliosAtwork
It would be great to see their ducklake fork, their patches and github issues so the community can learn.
Reading the article: it's not so much Epic's MyChart or CareEverywhere but a broken system which makes it hard or impossible to opt-out of institutional defaults. The moment health records are shared via CareEverywhere or IHEs all receivers have a copy under their jurisdiction and it turns into an interaction from 1 to N if you want to opt out.
The data also does not belong to the patient; it belongs to the hospitals and clinics to use for whatever they deem valid business purposes (mostly in good faith, but there are always exceptions and no one looking, no one enforcing).
"By bringing celld and workerd together, we want it to be radically easy to build and operate distributed applications on your own infrastructure."
It does not appear they are close sourcing it. He mentions workerd is open source. Roadmap needs better communication but it appears people will be able to switch to new merged OSS version. It's just not well defined what it looks like yet.
I am writing a rust native UI using GPUI but now I need a markdown viewer and editor and also want diagrams. I might end up embedding a webview (tauri style) after all.
"In the same week that Jev came out, we posted about some experiments [1] we had with our own homegrown decision model."
It's available in antigravity which I started using again (for small things until I can trust gemini for coding again).
https://docs.aveva.com/bundle/pi-server-s-da-admin/page/1022...
Is this approach viable or if it is just marketing:
https://databricks.com/blog/2017/01/19/real-time-streaming-e...
http://www.keycloak.org/ https://github.com/keycloak/keycloak
https://www.postgresql.org/message-id/CAJrrPGdMu8TzxpRZQKK5E...
The PostgreSQL 11 roadmap also mentions "multi-model" database
https://wiki.postgresql.org/wiki/Fujitsu_roadmap#Multi-model...
Any self hosting would need to be fully connected with automated update notifications from the "crowd" of contributors and reviewers.
I guess, it becomes a managed service at that point (since as you point out it should have reliable and secure production characteristics which does require a high level of competency). I am imagining a cloud of one for my passwords (a stateless, secure container, with disabled user access to the OS and which connects to an encrypted simple file store to keep my small sized but precious passwords).
I would host my own in a google app engine or heroku and avoid a 3rd party who is more attractive to hackers due to the number of accounts they host and potential gain to criminals.