Each client needs to agree to a set of (1) Terms and Conditions (T&C) and (2) a Data Privacy agreement when they have a direct interaction with us. This consent is in most cases collected by the chatbot at the beginning of the interaction, for which we create a Consent - FHIR resource relating to the Patient and an specific DocumentReference - FHIR. This last resource. The Document Reference resource captures the exact details of such agreement, normally because as it refers to contains a PDF with the specific terms.
...
to be returned as part of the User Profile? Gaspar to expand
Context:
Project: for query project as per header value
Type: T&C, Data Privacy, etc
Returned Valuevalue: active / | rejected | inactive
Expiration of current consents
...
When an agreement comes to an end, the project will need to run a mass update for all consent by doc ref number an
Set status to: inactive
Set end date: date that the previous agreement was replaced by a new one
Re-consenting
...
When a user revisits a bot, and his/her consent is ‘inactive’ the bot will ask users to agree to the new T&C/data privacy agreement. This new acceptance is to be stored as a new Consent - FHIR
resource, referring to the latest version DocumentReference - FHIR , setting the period/start date set to the date of the interaction.