This tutorial explains how to use Chino.io Consent Tracking API to manage a User's consent in your application.
Consent tracking (as described with more legal details here) is a fundamental aspect for health application compliance. This tutorial shows how to use the Chino.io Consent API to store, search, update, and delete consents from your users.
The Consent API is not bound to Users of
Chino.io API (the one that you can create in
you to use also external identifiers as
user_id (the user identifier in the consent).
In fact, the
user_id can be any string that uniquely represents the person
giving their consent, e.g. an email address.
The Chino.io Consent API are designed to keep a history of all the changes over a Consent. In this way if an
update is made on a Consent object, a new Consent is created
(rather than update the existing one). The newly created Consent has the same
consent_id as the previous one and the previous Consent is
stored in the Consent history for that
With the Chino.io Consent API you can:
Create a Consent for any kind of User (Usually done during the Signup process to your app).
Update a Consent for any kind of User
List all the Consents
Filter the list of the Consents
Withdraw a Consent
Delete a Consent (in case of Right to be Forgotten)
In this tutorial we show how to implement the Consent tracking for a user within an application. For clarity we skip the part on the creation of a User (as it's not mandatory to use Chino.io API Users) and we focus only on the creation of the Consent. We added extra-operations that can be performed on the Consent and that may be useful for you in the future.
Learn more about the Chino.io API and how to use it in your application.
Looking for more help?