Summer Summer connects clinical and pharmacy evidence to the customer's support case. Your MCP client can configure the company connection and read Summer's findings within its permissions. Summer's operational agent uses the authorized provider API or supported portal workflow to investigate the case.
MD Integrations, Beluga Health and GEN Health have built-in credential setups. Bask Health, OpenLoop, the health-record platforms and pharmacy services below need an agreed connection for the access your company has. Use the service directory for MCP setup and the provider reference for exact built-in credential fields.
Clinical platforms
MD Integrations
Save the matching client ID and client secret through the MD Integrations setup. Verify a known patient and encounter in the selected environment. Connect the encounter to the customer's actual purchase before interpreting its status.
A useful first case is a paid purchase with an unfinished administrative step. Read the relevant original conversation to establish why it is waiting and who needs to act. See MD Integrations MCP and automating MD Integrations support for the complete workflow.
Beluga Health
Use the Beluga Health setup for the API key and optional separate dashboard login key. Verify the intended visit and pharmacy record against the original source. API access and trusted browser sign-in are configured separately.
Start with an order-status case where your team knows the current care and fulfillment state. Preserve the difference between a care milestone, a pharmacy update and carrier tracking. Read Beluga Health MCP and Beluga customer-support workflows.
GEN Health
The GEN Health setup uses the account's API key. Optional portal credentials support a separately configured trusted browser connection. Verify a known record and the patient or care episode it belongs to.
For an appointment-access question, check the current booking and the patient's required next step. Use the exact visit record rather than an old reminder. The initial check should establish which API and portal reads your company's workflow can use.
Bask Health
Arrange a custom connection using the access available to your Bask account. Identify the work Bask already handles and the remaining task Summer should own across your help desk, payments or pharmacy records.
Test a case that needs information from both Bask and another service. Verify the same purchase across both sources and define who follows up. Summer MCP supplies the agent's Summer connection; this setup does not require an official Bask MCP server. Read Bask Health MCP and Bask support automation.
OpenLoop
Agree the records and partner access available to your OpenLoop program, then configure the custom workflow with Summer. Confirm which support tasks your existing program handles and which tasks Summer will handle.
Use a case that crosses a clear responsibility boundary, such as a customer conversation that needs a provider update. Preserve the original response and the next owner. Read the OpenLoop and Summer comparison and the clinical-platform comparison.
Health records
Healthie
Healthie's API guide requires an account with API access. Confirm that access with your Healthie administrator, then arrange a custom connection for the administrative records the support workflow needs.
Verify a known patient and relevant appointment or administrative record. Match it to the support case without copying unnecessary clinical content into customer communications.
Practice Better
Review the integrations available in Practice Better with your practice administrator. Agree which permitted connection or browser workflow supplies the records needed by Summer. The logo on the homepage does not establish a public API or an already-enabled connector for your practice.
Test one administrative support task using an original record your team can inspect. Record the supported read and any access gap before using it in live cases.
SimplePractice
Arrange the permitted account access and supported workflow with your practice administrator and Summer. Use the custom-integration process to describe required credentials when needed. Confirm the actual access method before making an API part of the workflow.
A useful initial check is whether Summer can inspect the specific appointment or account record behind a support question. Keep clinical decisions and treatment explanations with the care team.
Pharmacy connections
Strive Pharmacy
Strive's telehealth partner page describes API and portal options. Confirm the reads available under your partner agreement and configure the relevant workflow with Summer.
For support inquiries, Summer uses the configured Strive partner portal workflow. Check the exact pharmacy order, prior inquiries and original responses before proposing another contact. Keep a new inquiry open until its result and any remaining customer obligation are known. Read Strive Pharmacy MCP and Strive follow-up workflows.
Empower Pharmacy
Use Empower's API introduction as the provider starting point, then confirm the current account-specific documentation and access with your partner team. Arrange a custom connection for the reads and follow-up process your support cases need.
Verify one known order and its latest original update. When a shipment reference is available, use carrier evidence to answer delivery questions. An order event alone does not establish delivery. Read Empower Pharmacy MCP and Empower follow-up workflows.
The Pharmacy Hub
The Pharmacy Hub's developer page describes API and webhook access. Confirm the account's current reference and the exact operations your workflow needs, then configure the connection with Summer.
Check that an update belongs to the correct purchase and that a missed or repeated event does not create another order or inquiry. Compare Summer's finding with the live original record. Read The Pharmacy Hub MCP and Pharmacy Hub support workflows.
Can one case use several clinical and pharmacy services?
Yes, when the company's verified connections cover the needed records. Match the purchase to its provider visit, pharmacy order and shipment. Keep each source's meaning and timestamp with the finding. The multi-pharmacy workflow guide explains how to preserve ownership when several vendors are involved.
Does Summer provide medication instructions?
Only a clinician provides or clarifies medication directions. Summer can investigate administrative records and logistics, and link the patient to the authenticated clinician conversation. Summer must not write, relay, quote or summarize medication directions, including text from an existing prescription or clinician message.
What should I verify before using a connection?
Verify the company, environment and exact record behind one representative case. Compare the original evidence with Summer's result. Record any missing access and who will resolve it. Use capability checks to make the setup visible to your team.
For a case that needs several sources, read Connecting AI to your EHR, help desk and pharmacy. Use API, MCP or browser automation to choose the access method for a particular missing fact.