Anne is dual-eligible, enrolled in a D-SNP, and lives alone. At enrollment she has the plan's supplemental benefits, including an SSBCI grocery allowance that required a chronic condition determination. Then a fall is reported at a routine touchpoint, with no hospital stay. Her needs change, and so does the funding source that covers each one first.
The fall is noted, and the follow-up depends on who picks it up. Doctor and pharmacy trips, help at home, and grab bars each sit with a different program, and none of them shows where the others stand.
Anchor surfaces the needs-based benefits that match the new need and which funding source covers each one first. The care manager refers: Medicaid transportation for doctor and pharmacy trips, a waiver referral for help at home, and a community program for grab bars and a ramp. Her grocery allowance continues.
Calls member services, a vendor, and the Medicaid case manager to learn what was ordered for her mother. Each call reaches someone different, and each has part of the answer.
Whichever care manager takes her call sees the same record: each referral made for her mother, its status, and how long it has been open, with each vendor's record accepted and graded.
Referrals go out by phone, fax, and email. No single place shows which funding source covers the need, whether a referral was received, or the latest cap balance.
Sends referrals and confirms services from one screen, within the existing care management workflow. The latest available cap balance shows at referral, and each vendor's record comes back accepted and graded.
Each need, the funding source that covers it first, each referral, and each vendor's record, tied to the member with the criteria and PBP on record. Across a plan's dual-eligible members, that record is how the plan substantiates its non-medical benefit spend at the member level.
Anchor builds that record as the work happens.
As Anne's needs change, the care manager sees the needs-based benefits available to her on one screen. Whichever care manager takes the next call sees the same record, with the criteria and PBP that applied at each determination.
Illustrative example. Covered services, waiver programs, and referral processes vary by state and plan. This example follows Illinois, where a waiver request is a referral to a state-contracted Care Coordination Unit that decides within 30 days, and where the waiver does not cover home modification, so grab bars and a ramp route to a community program.
Our team walks you through how Anchor would fit your state, member mix, and care management workflow, from a member’s need to a documented service.
Anchor orchestrates non-medical benefits for dual-eligible members within existing care management workflows. Every service is substantiated at the member level.
Request a DemoEffective date: January 1, 2026
Anchor Care, Inc. ("Anchor," "we," "us," or "our") operates anchorcare.ai and related services. This Privacy Policy explains how we collect, use, disclose, and safeguard information when you visit our website or engage with our platform.
We may collect information you provide directly, such as your name, email address, organization, and the content of messages submitted through contact forms. We also collect certain usage data automatically, including IP addresses, browser type, pages visited, and time spent on the site, through standard web analytics tools.
We use the information we collect to respond to inquiries, operate and improve our services, communicate about pilot programs and product updates, and comply with applicable legal obligations. We do not sell your personal information to third parties.
Our platform is designed for use by health plans and their authorized personnel. To the extent any protected health information (PHI) is processed through our platform, it is handled in accordance with applicable HIPAA requirements and the terms of executed Business Associate Agreements.
We retain personal information for as long as necessary to fulfill the purposes outlined in this policy, unless a longer retention period is required by law or contract.
Depending on your jurisdiction, you may have rights to access, correct, or request deletion of your personal information. To exercise these rights, contact us through our website.
Anchor Care, Inc. · 5227 N 7th Street, Phoenix, AZ 85014
Last updated: April 2026
Anchor is built for health plans operating in a regulated, high-stakes environment. Our security and compliance posture reflects that responsibility.
Anchor operates as a Business Associate under HIPAA when processing protected health information on behalf of covered entities. We execute Business Associate Agreements (BAAs) with all health plan partners prior to any data exchange. Our systems are designed to support the administrative, physical, and technical safeguards required under the HIPAA Security Rule.
All data transmitted to and from Anchor's systems is encrypted in transit using TLS 1.2 or higher. Data at rest is encrypted using AES-256. Access to production systems is restricted by role-based access controls and multi-factor authentication.
Anchor's infrastructure is hosted on HIPAA-eligible cloud services. We maintain audit logs of system access and regularly review access permissions. Penetration testing and vulnerability assessments are conducted on a scheduled basis.
We maintain a list of subprocessors used in the delivery of our services and update it as our vendor relationships change. Health plan partners may request the current subprocessor list by contacting us directly.
Anchor maintains a documented incident response plan. In the event of a security incident affecting health plan data, we will notify affected partners in accordance with HIPAA Breach Notification Rule requirements and any applicable contractual obligations.
SOC 2 Type I targeted Q2 2026. SOC 2 Type II targeted Q4 2026. HITRUST r2 certification is on our 2027 roadmap. Anchor operates under HIPAA-compliant data handling practices with encryption in transit and at rest, role-based access controls, and annual third-party security review.
For security inquiries or to request a BAA, reach us at security@anchorcare.ai or submit a security or compliance inquiry through our contact form. · Anchor Care, Inc. · 5227 N 7th Street, Phoenix, AZ 85014