Admin-only pilot rule
For simplicity and control during the pilot, all folder creation, master database ownership, uploads, notifications, invoice generation, and Apps Script execution should occur under admin@spectocularhealth.com.
MFA / 2FA requirement: The master database linking patient identifiers to subject IDs must remain accessible only through MFA-protected SpectOcular Workspace access. Do not share the master linkage sheet with OD/site users.
Files included in this package
Deploy these Apps Script files from admin@spectocularhealth.com.
Deployment checklist
- Sign into Google as
admin@spectocularhealth.com. - Confirm the account has MFA/2-Step Verification enabled and Workspace BAA is signed.
- Create a new Apps Script project named
SpectOcular Pilot Workflow Backend. - Paste
Code.gsandappsscript.json. - Run
setupSpectOcularGoogleWorkflow()once. - Approve permissions only from
admin@spectocularhealth.com. - Copy the returned root folder URL, master database URL, and portal token.
- Deploy the script as a Web App executing as
admin@spectocularhealth.com. - Paste the Web App URL and portal token into the Authorized Research Workflow page.
- Create one test subject and confirm the Drive folder + database rows are created.
- Upload a test signed packet PDF and confirm it lands in the correct subject folder.
- Submit one test agreement and confirm the row appears in
Eyecare_Professional_Agreements. - Submit one test monthly attestation and confirm the row appears in
Monthly_Attestations. - Generate a test monthly invoice/offset statement.
Drive/database structure created by the script
00_Master_Database_RESTRICTEDContains the master spreadsheet and patient ↔ subject linkage. MFA/admin-only.
01_SitesContains site folders and subject folders such as 01-00001.
03_Monthly_InvoicesStores monthly Retina IQ invoice/offset statements by site.
Production notes
Google Workspace is appropriate for the pilot. For national scale, migrate imaging ZIPs and model-training data to Azure Blob/Data Lake with formal user authentication, device-side upload agents, hash-based integrity checks, and auditable de-identification workflows.
