Consents
Patients decide what data they share, and with which projects. This section explains how to check consent before you use a patient's data, and how to audit the consent process after the fact.
Before you start
Consent calls require an access token. See Authentication, and Key Concepts for how projects and consent types work.
Checking Consent
Always confirm consent before releasing or using a patient's data. Start with a single check, then move to the bulk examples.
- Basic Consent Checking: check whether one patient gave one type of consent to one project
- Consent Checking Examples: common bulk queries, listed below
Auditing Consent
When you need to know more than whether a patient consented, such as when, how, and what they saw.
- About Consent Auditing: when auditing matters and what's available
- Getting Consent Record Details: the record behind a single consent
- Getting Consent Screenshots: exactly what the patient saw when they consented
Looking to send patients back to your app after they finish the consent flow? See Setting Up a Hosted Redirect.