Practice systems

A tenant can link its participants to their records in the practice management system its clinics run on, and file a PDF of a sequence response (a questionnaire, a signed form) to that record. It is turned on with the platform admin's practice.system configuration, naming the vendor, the clinics whose appointments may be read, and which sequences are filed as which of the system's file types.

• A participant is linked from their own appointment, never by searching the system by name. A participant linked to a different record is not re-linked: the conflict becomes a task.
• Nothing identifying comes back in. The system's names and contact details never leave the adapter, and its ids are kept but never returned by the API or a webhook.
• A response is filed only for a linked participant whose consent stands, as a PDF with no name or contact details, labelled as patient-reported. It counts as filed only once it reads back identical; a failure is retried with backoff, and one that finally fails raises a task.
• Each link and upload is a record of its own (userPracticeRecords, userPracticeUploads), and every step is written to the audit trail.