Six services. One retention outcome.
Each service targets a specific failure point in the H.R.1 renewal process — from exemption detection to contact refresh to post-renewal tracking.
01Core
Exemption Engine
The Exemption Engine continuously scans ADT feeds, EHR problem lists, behavioral health encounters, and claims to identify members who qualify for a work requirement exemption — before the county sends a renewal notice.
90 daysaverage lead time before renewal
How it works
- 01Ingests ADT admission and discharge alerts in near real-time.
- 02Parses EHR problem lists and encounter diagnoses for exemption-qualifying conditions (SUD, SMI, medically frail, pregnancy, and more).
- 03Cross-references claims history for inpatient stays, residential treatment, and chronic condition management.
- 04Scores each member with a confidence level (Confirmed / Likely / Possible) and surfaces the supporting evidence.
- 05Generates a pre-populated exemption packet ready for care manager review and county submission.
Data sources
ADT feedsEHR problem listsBehavioral health encountersClaims historyCounty renewal data
Outcome: Members with clinical exemptions are identified an average of 90 days before their renewal date — enough time to prepare documentation and prevent a gap in coverage.
Integration
Connects to your existing infrastructure.
hequity.ai is designed to layer on top of what you already have — not replace it. We connect to your ADT feeds, EHR, and county data through standard interfaces and return structured outputs your care management and eligibility teams can act on.
ADT feedsHL7 FHIR R4 and legacy HL7 v2 ADT messages
EHREpic, Cerner, and FHIR-compliant systems via CDS Hooks or bulk export
County eligibilitySAWS and CalHEERS data exchange
Claims837/835 transaction files and plan data warehouse exports
Care managementBidirectional integration with leading care management platforms