CareClinic Health Tracker + connected AI assistant CAIHL draft report

CareClinic Health Tracker + connected AI assistant: CAIHL review

Reviewed September 28, 2026. AI-assisted draft. Potentially agency-expanding; unscored.

Executive summary

CareClinic can supply authorized records to a separately governed AI assistant. Scoped access, confirmation before supported writes and revocation may expand agency; host interpretation and retained copies remain outside those controls. Unscored.

CAIHL question: who does this AI serve?

Patient-authorized record access with interpretation by a separately governed AI host. Primary user: Individuals using their CareClinic records through an AI assistant they connect. CareClinic hosts records and connector; the selected AI host processes returned context under its own terms. Consumer choice supports a patient-directed pathway, but does not by itself establish patient alignment. Vendor interests in subscriptions and continued use coexist with the patient's purposes.

What the service does and the scope of this review

Consumer CareClinic MCP connection plus the chosen AI host. The deterministic tracker alone and built-in image AI are not the evaluated AI deployment.

Patient-impact pathway

An AI assistant interprets authorized health records and can prepare supported check-ins, affecting understanding and the patient-held narrative.

Mixed HugoScore profile

Who sets and changes the goal?

Partial. Users authorize a host connection and choose questions; authority over the host interpretation was not tested. S1 S2

Can patients tell AI is involved?

Yes. The connector workflow explicitly involves an AI assistant chosen by the user. S1

Can patients meaningfully choose?

Partial. Scoped authorization and revocation are described. Revocation stops future access, not host-held copies. S1 S3

Can patients correct or challenge the output?

Partial. Supported symptom/mood check-ins use preview and confirmation; medication writes are disabled. These controls do not verify correction of AI conclusions. S2

Does it help patients understand or act?

Potentially. Authorized record context may support chosen questions and patterns; causal or treatment conclusions are not established. S1 S2

Can patients evaluate the conditions of use?

Partial. Documentation distinguishes connector and host responsibilities; users must assess both policies and actual granted scope. S1 S3

What happens to patient data?

Two governance layers. CareClinic describes minimized connector returns and separate host terms. Account-linked MCP usage events have no automatic expiry; deletion reconciliation is distinct from revocation. Built-in AI training commitments do not govern an independent host. [S3]

Who is left out or burdened?

Host-dependent. A CareClinic account is required; Premium is not required to connect. Premium adds deterministic trend detail. Host costs and accessible connector support vary. [S2]

Are the clinical boundaries clear?

Documented; behavior untested. MCP help describes consumer informational use, excluding diagnosis and HIPAA covered-entity/clinical use. Broad security language does not override this scope. [S2, S4, S5]

Who defined what good looks like?

Tracker evidence is not AI validation. The cited Skeens study evaluates marketplace apps using MARS. It does not establish clinical benefit or validate MCP-mediated AI interpretation. Patient influence on AI outcome selection is not established. [S6, S7]

Evidence boundaries

CareClinic’s clinical-evidence page frames tracker research as evidence for its app. The Skeens paper is a systematic marketplace search and app-quality assessment, not a trial of this connector or its AI host. Its ratings cannot establish patient health outcomes or AI accuracy. The review does not equate tracker engagement ratings with patient agency. The paper’s publisher page was inaccessible to this pass; the indexed abstract and PubMed record support the methodological distinction. Vendor evidence page · Study record

Key unknowns

• Which host/model and privacy configuration each person uses
• Actual permission and preview-confirmation enforcement across supported hosts
• Correction and deletion of host-derived summaries or inferences
• Independent evaluation of the combined AI workflow
• Accessible use, costs and subgroup outcomes

Risks to investigate

These are plausible failure modes, not observed harms.

• Treating connection revocation as erasure from every recipient
• Mistaking descriptive record patterns for causes or treatment guidance
• Extending tracker quality evidence or built-in AI privacy claims to the connected host
• Unsupported generalization of vendor security claims to clinical deployment

Patient agency interpretation

Could support patient-selected questions about records and deliberate authorship of supported check-ins. Revocation cannot retract information already copied by the host; host behavior and downstream correction are untested. Critical reflection requires inspectable evidence; strategic action requires the ability to use the result for the patient's own purposes; neither is proved by engagement or vendor assurances alone. Documented access and write controls support patient choice. Agency still depends on the host, actual enforcement and whether interpretations can be challenged.

Publication recommendation

Publish as a source-backed AI-assisted draft. Retain a null numerical axis position: documented architecture is insufficient for a calibrated comparative number. Confidence: Medium for connector documentation, low for host behavior and outcomes (AI-assisted draft).

Evidence ledger

All sources accessed September 28, 2026. Vendor disclosures establish what is promised, not that controls work.

• S1: CareClinic MCP — CareClinic. User-authorized records and assistant workflow.

• S2: MCP help — CareClinic. September 3, 2026; previews, limits and consumer scope.

• S3: Privacy policy — CareClinic Software Inc.. September 5, 2026; built-in AI versus MCP hosts, event retention and deletion.

• S4: Terms of use — CareClinic Software Inc.. Consumer self-management, unverified records and account/subscription distinctions.

• S5: Data security — CareClinic. February 12, 2026; controls and audits in progress.

• S6: Clinical evidence — CareClinic. Claims based on tracker literature.

• S7: mHealth Apps in the Digital Marketplace for Pediatric Patients With Cancer: Systematic Search and Analysis — JMIR Pediatrics and Parenting / PubMed. Skeens et al., 2024; abstract methods: app-store search and Mobile App Rating Scale.

Review provenance

criteriaSource: CAIHL-derived HugoScore framework and current qualitative review method

reviewer: AI-assisted public-source review prepared in OpenAI Codex

model: OpenAI Codex / GPT-6 (exact variant not recorded)

humanReview: Hugo Campos authorized review and publication. No comprehensive human verification is claimed.

reviewDate: 2026-09-28

limitations: Public-source documentary review only. No account creation, health-data upload, interaction tests, security audit, clinical evaluation or vendor interview. Host-specific and provider-specific behavior is unverified.