You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Obsidian-copilot is really nice and I would like to use it as part of a healthcare-focused project for advising patients and physicians with a patient's electronic health records as context. Asking a patient or physician to setup obsidian is too much when all they want is to keep a chat record and link their health record as exported by a health records app.
Our demo environment is mostly Vue and everything is licensed as AGPL 3. The local component which includes the health records app and a PouchDB is loaded as a PWA from a community server.
What would be the recommended way to keep most of the goodness and UX of copilot while adding it to the PWA?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Obsidian-copilot is really nice and I would like to use it as part of a healthcare-focused project for advising patients and physicians with a patient's electronic health records as context. Asking a patient or physician to setup obsidian is too much when all they want is to keep a chat record and link their health record as exported by a health records app.
Our demo environment is mostly Vue and everything is licensed as AGPL 3. The local component which includes the health records app and a PouchDB is loaded as a PWA from a community server.
What would be the recommended way to keep most of the goodness and UX of copilot while adding it to the PWA?
Beta Was this translation helpful? Give feedback.
All reactions