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
{{ message }}
This repository has been archived by the owner on Oct 27, 2021. It is now read-only.
The weaknesses of the pure API approach include things like not knowing who has permission to data at any given time (without maintaining state somewhere externally), and easily providing a unified composition of health data from across sources. We should highlight (and build if not productized) our ability to show these things to reinforce our differentiation.
We should consider providing support for this approach within DHP, since I believe it can be compatible with a blockchain-based approach (the comparison, I think, will be primarily DID vs Blockchain, and since DID is not a finalized standard, we have a bit of a lead)
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The weaknesses of the pure API approach include things like not knowing who has permission to data at any given time (without maintaining state somewhere externally), and easily providing a unified composition of health data from across sources. We should highlight (and build if not productized) our ability to show these things to reinforce our differentiation.
We should consider providing support for this approach within DHP, since I believe it can be compatible with a blockchain-based approach (the comparison, I think, will be primarily DID vs Blockchain, and since DID is not a finalized standard, we have a bit of a lead)
The text was updated successfully, but these errors were encountered: