Objective
Explore the ExactaCare portal/access situation and how Sam can leverage it for Trent's Treatment-stage case workflow, using read-only Drive, Litify, and local artifact evidence.
Evidence Used
Findings
- The supplied Drive root is an Aguiar Law Offices case-folder tree with client/case folders and some loose PDFs.
- ExactaCare evidence appeared as provider-named subfolders and PDFs: registration, release, records, bills, notes, HCFAs/charge reports.
- Aptiva evidence appeared as provider PDFs plus saved ShareFile-style HTML snapshots and email PDFs with integratedmedicalsolutions.sharefile.com links; some reports also referenced RamSoft/PACS.
- No verified shared ExactaCare/Aptiva portal-login instruction artifact was found in this pass. The access pattern looks case/provider-scoped rather than a single reusable shared login.
- Current local queue artifacts already classify 37 ExactaCare/Aptiva provider rows across 28 Trent Treatment-stage matters, with 22 active unreceived provider requests, 89 draft-only Litify updates, and 37 no-send adjuster drafts.
Recommended Workflow
- Use the current queue read-only first, then work smallest-first: linked Matter folders and file candidates before missing-link matters.
- Treat Drive connector evidence as primary until local gws OAuth is repaired; the current gws client is broken/deleted-client.
- Keep automation Matter-scoped. Parse provider PDFs, saved ShareFile HTML, and email-link evidence into candidate records/bills summaries, then require human approval before Litify writes or adjuster sends.
- Prioritize populating verified Matter Drive links because missing Drive links are the biggest blocker for safe automation.
Pickup Prompt