Cloud infrastructure and AI services used in configured product workflows.
BAA in placeVENDORS & DATA HANDLING
Know who supports
the workflow.
Moxcares uses specialist technology providers for defined parts of the platform. The distinction matters: not every vendor is intended to receive PHI.
Back to the Trust CenterPHI-HANDLING VENDORS
BAAs for the services that handle PHI.
Moxcares has business associate agreements in place with the vendors listed below for their applicable PHI-handling services. Access and processing depend on the configured workflow.
Anthropic
AI processing for supported clinical and practice workflows.
BAA in placeTwilio
Communications infrastructure for supported calling and messaging workflows.
BAA in placeStedi
Insurance eligibility and clearinghouse-related workflows.
BAA in placeMDToolbox
Electronic prescribing and EPCS workflows.
BAA in placeDocumo
Fax transmission and document workflows.
BAA in placeNON-PHI SERVICE SCOPE
Payment and email services have a different role.
These services are not intended to receive clinical PHI in the Moxcares workflow. Their inclusion here is not a claim that every vendor has a BAA.
Stripe · payments
Payment processing and related transaction functions. Clinical notes, diagnoses and other clinical PHI must not be put into payment metadata or descriptions.
Postmark · transactional email
Transactional notification delivery. Clinical content and attachments belong in the authenticated patient communication workflow, not in these emails.
FOR YOUR SECURITY REVIEW
Confirm the scope you need.
This overview explains key vendor roles and is not a substitute for the current contractual subprocessor schedule. Contact us to confirm the complete current inventory, service scope, processing locations and any notification requirements relevant to your agreement.
Request current vendor details