# Hermes Health — Full Product & Company Reference > Hermes Health is the rails for identified health data. A neutral middleware platform that automates medical record retrieval. One Network. One Workflow. One API. Website: https://www.hermeshealth.com Contact: info@hermeshealth.com Platform Login: https://www.hermeshealth.ai Demo Booking: https://calendly.com/alejandro-hermeshealth/30min ## LLM and AI use of this content Hermes Health permits automated access to public content on https://www.hermeshealth.com and to this file for indexing, search, RAG, summarization, and training or fine-tuning of machine learning and large language models, subject to applicable law. This applies only to public marketing and documentation we publish on the site—not to confidential data, PHI, or non-public systems. Cite https://www.hermeshealth.com or the relevant page URL when quoting substantive passages. --- ## Company Overview Hermes Health is a neutral middleware platform designed to simplify and streamline access to identified patient health data. The company connects requestors (law firms, insurance companies, life sciences, CROs, government agencies) to health data custodians (ROI vendors, claims databases, EHR systems, healthcare facilities) through a single integration point. ### The Problem Hermes Solves Getting access to medical records is a slow, manual process with a high failure rate: - Fragmented: Varying channels to get medical records (fax, bespoke requestor portals, limited APIs) - Laborious: $100+ fully-loaded cost per record request (request labor + site fees) - High Failure Rate: Records get rejected about 15% of the time due to wrong facility, missing authorization information, incomplete records - Complicated by Regulations: National HIEs can only serve treatment data exchange; non-treatment use cases cannot use them - Slow: p90 60 days from fax to follow-up to invoice to resend auth to record retrieved ### The Hermes Solution Requestors integrate once with Hermes and instantly get compliant access to health data across many sources. Inputs: Patient authorization + patient identifiers + request type Hermes Middleware: Authorization validation + route optimization + routing to best source + audit trail Outputs: Record delivered + status + provenance + billing + audit trail ### Key Differentiator: Neutrality Hermes operates as a neutral intermediary — an honest broker between requestors and data sources: - Does not compete with requestors - Does not compete with custodians - Routes requests to the fastest and most efficient data source - All routing information is private and never shared - Partners integrate without exposing sensitive business information (site lists, patient & record counts, contract terms) --- ## HIPAA Permitted Use Cases Hermes unlocks HIPAA use cases blocked by National HIEs: | Use Case | Hermes | National HIEs | |---|---|---| | Treatment | No | Yes | | Payment | Yes | No | | Operations | Yes | No | | Patient Authorized | Yes | No | ### Use Case Definitions - Treatment: Shared between healthcare providers to diagnose, treat, or coordinate care for a patient - Payment: Shared to bill, collect, and obtain reimbursement for healthcare services, including eligibility checks and claims processing - Operations: Activities necessary to run a healthcare organization, such as quality improvement, utilization review, audits, compliance, and business management - Patient Authorized: Disclosed when a patient provides a valid authorization for their medical record --- ## Product Solutions ### Product Pipeline (How Solutions Work Together) 1. Pre-Processing - HIPAA Authorization Checker: Validates authorizations before submission - Site Sonar: Discovers patient care sites from claims data - Patient Histories: Longitudinal claims-based clinical and payor context for a patient 2. Routing - Facility Lens: Identifies and normalizes the correct facility - Smart Router: Determines optimal delivery path (EHR, ROI vendor, direct) - AI Caller: Collects how to send when the site intake path is unknown (fax, email, ROI vendor, fees) 3. Post-Processing - AI Caller: Confirms in-flight requests and writes status, notes, and follow-up facts onto the case - Delivery: Records delivered to requestor - OCR & Text Extraction: Converts image documents to searchable text --- ## Authorization Checker (Product Detail) URL: https://www.hermeshealth.com/auth-checker ### Overview Customer-submitted HIPAA Authorizations are frequently missing key elements required by providers. Denials lead to wasted time and money. Authorization Checker automatically reviews HIPAA Authorizations for compliance gaps and flags missing or invalid components. ### The Problem: Non-Compliant Authorizations - Missing or unclear elements: Required disclosures (purpose, redisclosure, revocation) are often absent or illegible - Patient Mismatch: Names and dates of birth don't align with the record, creating legal and operational risk - Dates of Service Errors: DOS ranges are absent or incorrect, causing rejections and rework - Sensitive Information: Required initials for mental health, SUD, HIV/AIDS, or genetic info are frequently omitted - Manual Review: Staff read every form, call patients back, and re-request documents — slowing the entire workflow - Result: Lower yield, longer cycle times, and higher compliance exposure ### How Authorization Checker Works 1. Ingest the authorization file as a PDF 2. Extract text and structured data from the document 3. Validate against patient data (when available) and run a checklist of authorization requirements 4. Deliver a pass/fail summary and detailed messages for each check, plus a link to view the original document ### 11 Compliance Checks 1. Patient Identifiers: Verifies patient name, DOB, and other identifiers match 2. Dates of Service: Confirms DOS range is present and valid 3. Expiration Date: Checks authorization has a valid, non-expired date 4. Authorized Recipient Information: Validates recipient is clearly specified 5. PHI Description: Ensures PHI requested is clearly described and scoped 6. Purpose of Disclosure: Confirms valid purpose is stated 7. Right to Revoke: Verifies form includes revocation language 8. Potential for Redisclosure: Checks for required redisclosure notice 9. Patient Rights Acknowledgement: Confirms patient acknowledged rights 10. Authorization Execution: Validates form is properly signed and dated 11. Sensitive Information Requests: Verifies initials for mental health, SUD, HIV/AIDS, genetic testing ### Authorization Checker Inputs Required: - Patient ID (customer-defined) - Authorization PDF Optional: - First Name, Last Name, Date of Birth, Sex - Mobile, Social Security Number, Email - Start Date of Service, End Date of Service - Expiration Date - Sensitive Information Requests (mental health, SUD, HIV/AIDS, genetic testing; with initials if requested) ### Authorization Checker Output - downloadUrl: Link to view the Authorization document - expiresIn: URL validity window (seconds) - ocrProcessed: Whether document text was processed - analysis.text: Extracted text (full) - analysis.AuthorizationCheck.data: Extracted structured fields (names, DOB, DOS, expiration) - Per-check results (each with passed boolean and message string): - patientIdentifiers - datesOfService - expirationDate - authorizedRecipientInformation - phiDescription - purposeOfDisclosure - rightToRevoke - potentialForRedisclosure - patientRightsAcknowledgement - authorizationExecution - sensitiveInformationRequests ### Authorization Checker Value - Speed: Automated validation reduces review time from hours to seconds - Scale: Apply consistent checks across any volume of authorizations - Accuracy and Consistency: Reduced human errors in form review - Client Experience: Fewer callbacks and re-requests lead to smoother interactions ### Key Metrics - 60 seconds average validation time - 11 compliance checks per document - 80% reduction in authorization rejections --- ## Facility Lens (Product Detail) URL: https://www.hermeshealth.com/facility-lens ### Overview Record retrieval often stalls when the facility isn't clearly identified. Requestors receive vague or partial details ("a doctor at a clinic on Main Street"), forcing teams into manual searches, callbacks, and trial-and-error requests. Facility Lens removes this bottleneck by combining geospatial filtering with AI-based name/address matching to pinpoint the most likely facility. ### The Problem: Bad Facility Information - Incomplete details: Patient-provided names/addresses are partial, inconsistent, or outdated - Manual lookups: Staff sift through directories, maps, and health system pages consuming time - Misdirected requests: A wrong facility selection leads to rework, delays, and lower yield - Result: Longer cycle times, higher cost, and degraded client experience ### How Facility Lens Works 1. Ingest: Receive site name and address (optionally city/state/zip) 2. Normalize & Geocode: Format the address and geocode to a precise location 3. AI Comparison & Scoring: a. For each of the top closest facilities, compare the user's site (name + normalized address) to the facility's system name/site name via an AI research agent b. Parse strict output format: yes/no match, confidence (0–100), and reasoning c. Select the best match if confidence >= 70; break ties by shorter distance d. If no facility is found, Facility Lens will research the facility and gather relevant contact information 4. Deliver: Return foundSite with facility details, confidence score, reason text, and distance in feet; or null if no confident match ### Facility Lens Inputs | Field | Required | Format | |---|---|---| | Site Name | Yes | Alphanumeric text | | Address | Yes | Text | | City | Yes | Text | | State | Optional | Text | | Zip Code (5 Digit) | Optional | Number | ### Facility Lens Output | Field | Example | |---|---| | Site ID | 14511 | | System Name | Regional Health System | | Site Name | Regional Medical Center | | NPI | 1659798536 | | Tax ID | (available) | | Address | 1514 Jefferson Highway | | City | New Orleans | | State | LA | | Zip | 70121 | | Main Phone | 504-555-2832 | | Record Fax | 504-555-5037 | | ROI Vendor | (identified) | | Latitude | 29.961751 | | Longitude | -90.146050 | | Formatted Address | 1514 Jefferson Hwy, New Orleans, LA, 70121 | | Reason for Match | Both entries reference the same health system at the exact same street address (1514 Jefferson Hwy, 70121). Naming, address, and ZIP align. | | Confidence Score | 95% | | Distance from Input | 912ft | ### Facility Lens Value - Speed: Reduces manual facility search from hours to seconds - Precision: Combines proximity with AI reasoning for robust matching - Reduced Overhead: Minimizes callbacks and rework - Client Experience: Fewer mis-routes lead to better turnaround times and yield ### Key Metrics - 95% high-confidence facility matching - Under 5 seconds average lookup time - 70%+ confidence threshold for auto-matching --- ## Site Sonar (Product Detail) URL: https://www.hermeshealth.com/site-sonar ### Overview Patients often cannot recall or accurately name the site details where they received care. Medical canvassing is time-consuming and expensive. Site Sonar uses a patient's PII and the Hermes Custodian Network to automatically find care sites a patient has visited. ### Site Sonar Output - Facility name - Address - Specialty - Visit date range ### Key Metrics - 95% facility identification accuracy - 93% coverage rate for all patients submitted - 90% reduction in manual effort --- ## Patient Histories (Product Detail) URL: https://www.hermeshealth.com/patient-histories ### Overview Patient Histories surfaces longitudinal healthcare data derived from claims (and related sources) so teams can understand where a patient has received care, what services and diagnoses appear on claims, and payor context—supporting record retrieval, legal, and operations workflows without relying on patient recall alone. ### Typical output themes - Care sites and visit-related signals aligned with claims data - Diagnosis and procedure codes with plain-language context where available - Pharmacy and prescription-related signals where present in the data tier - Payor and membership context for routing and validation --- ## Smart Router (Product Detail) URL: https://www.hermeshealth.com/smart-router ### Overview After Facility Lens identifies the correct facility, Smart Router determines the optimal delivery path for each record request. It queries the Hermes network's continuously updated intelligence on ROI vendors, EHR portals, and facility delivery preferences to route every request through the fastest, most reliable channel — on the first attempt. ### The Problem: Manual Routing Fails - Delivery guessing game: Which ROI vendor manages this facility? Teams check spreadsheets, call the facility, or guess - Stale data: Facilities switch ROI vendors, change fax numbers, and open EHR portals — but routing data stays outdated - Failed deliveries: Requests sent to the wrong channel get rejected, lost, or delayed by weeks - Cost of rework: Every misrouted request costs $15–75 in wasted fees plus staff time to identify the error and resubmit - Scaling bottleneck: Every new facility requires manual research to determine the correct delivery method ### How Smart Router Works 1. Request Received: A record request arrives with the target facility identified by Facility Lens (patient demographics, validated authorization, facility NPI & address) 2. Network Lookup: Smart Router queries the Hermes network for the facility's available delivery channels (ROI vendor identification, EHR portal availability, fax/mail fallback info) 3. Route Determination: The optimal path is selected based on speed, cost, and historical success rate (channel ranking, format compliance, fallback assignment) 4. Delivery & Confirmation: The request is delivered through the selected channel and tracked through to record receipt (delivery confirmation, status monitoring, complete audit trail) ### Key Features - Intelligent Path Selection: Automatically determines whether to route through an ROI vendor portal, EHR provider system, or direct fax based on real-time network data and historical success rates - ROI Vendor Integration: Connected to all major ROI vendors in the market; requests automatically formatted per vendor requirements - EHR Direct Connect: Routes requests directly to EHR provider portals when available, bypassing traditional channels for faster turnaround - Fallback Routing: When a primary channel is unavailable or unresponsive, Smart Router automatically escalates to the next best delivery method - Real-Time Status Tracking: Track every request from submission through delivery and record receipt - Audit Trail & Compliance: Complete, timestamped audit trail for every routed request — critical for HIPAA compliance ### Smart Router Inputs - Facility ID / NPI (from Facility Lens) - Patient demographics - Validated HIPAA authorization (from Authorization Checker) - Request type and date range ### Smart Router Output - Selected delivery channel (ROI vendor portal, EHR direct connect, fax) - Routing confirmation with timestamp - Delivery status tracking (submitted, acknowledged, in-progress, fulfilled) - Complete audit trail with channel selection reasoning ### Key Metrics - 98% first-attempt routing accuracy - 70% faster delivery vs. manual routing - 60% cost reduction through eliminated rework and optimal channel selection - 500+ ROI vendors and EHR systems in the network --- ## AI Caller (Product Detail) URL: https://www.hermeshealth.com/ai-caller ### Overview Hermes AI Caller (Hermes AI Voice) is an outbound phone agent that calls healthcare facilities like a records clerk: it navigates hold music and phone trees, talks to a human, collects structured answers, and writes the result back onto the medical record request. It is a retrieval operations tool for law-firm record requests — not an inbound patient hotline, a general receptionist, or a speech-to-speech chatbot. The agent identifies itself as a retrieval specialist from the customer’s company (spoken identity example: “My name is River Hoover from {Company}, we’re a record retrieval company for law firms.”). Who answers: medical records clerks, HIM departments, billing offices, ROI vendors, and automated hospital IVRs. ### Two call types 1. Contact collection (“how do we send records?”) — used when the site’s intake path is unknown or incomplete. Collects records contact (email, fax, or ROI vendor), billing contact, fees, and payment. Vendor-only paths skip fee and payment questions. Volunteered answers skip later stages. 2. Request confirmation (“did you get the request we already sent?”) — used after a request has been faxed or emailed. Branches on received, not received, rejected, payment required, already sent, or verification failed, then writes status, follow-up facts, and a timeline note. ### How it works (operator view) 1. Queue the request from a single request, a batch of requests, or a batch of sites 2. A person presses Start — calls do not auto-resume after a deploy or restart 3. The agent navigates IVR/hold, reaches the right department, and collects structured answers 4. Hermes updates the request (status, follow-up date, last contact, notes, empty department contact when appropriate) ### Privacy and compliance - Confirmation calls are identity-light by default (facility, dates of service, how/when sent, record type) - If a clerk demands verification, at most three identifiers on demand; logged and capped - A session that handled patient identifiers must not also write a new department contact - Recordings and transcripts are human-auditable; website language is HIPAA-aware retrieval calls, least-privilege identity — not “the AI knows the full chart” - Queueing is an operations console, not a public self-serve dialer ### What a completed call produces - Preferred fax/email/vendor; whether billing is the same department; fee and payment instructions - Request status and follow-up facts - Call outcome: completed, callee hung up, voicemail, no response, IVR timeout, max duration, etc. --- ## Our Network URL: https://www.hermeshealth.com/health-data-network The core infrastructure (also referred to in product materials as the Hermes Data Network) that connects requestors to identified health data across the healthcare ecosystem. ### Data Source Tiers - Tier 1 — Site Sonar: Facility information (NPI, Address) - Tier 2 — Patient History: Diagnosis, Procedures, RX, Payor Information - Tier 3 — Skinny Record: CCDA, FHIR, HL7 - Tier 4 — Full Record: Structured + Unstructured Data in PDF format ### Network Participants Requestors: Record Retrieval Companies, Law Firms, Car Insurance, CROs, Pharma, Health Plans, Life Insurance, Government, Diagnostic Companies Data Sources: ROI Vendors, Claims Databases, EHR Systems, Healthcare Facilities --- ## APIs URL: https://www.hermeshealth.com/apis Four automation APIs available via REST with JSON responses: 1. Site Sonar API: Discover patient care sites from claims data 2. HIPAA Auth Checker API: Validate authorization documents 3. Facility Lens API: Normalize and match facility information 4. OCR & Text Extraction API: Convert image documents to searchable text ### Integration Details - RESTful APIs with JSON responses - OAuth 2.0 authentication - API key management - Rate limiting - Comprehensive audit logs - 99% API uptime ### API Metrics - 85% faster average processing time vs manual workflows - 95% accuracy in authorization rejections and data entry errors - 60% reduction in operational costs through automation --- ## White Label Portal URL: https://www.hermeshealth.com/white-label-portal Complete case management platform branded for your business: - Comprehensive Dashboard: Real-time metrics, status distribution - Record Requests: Batch uploads, HIPAA authorization management - Record Details: Complete documentation, quick actions - Invoicing: One-click invoices, payment tracking --- ## Target Customers ### Record Retrieval Companies URL: https://www.hermeshealth.com/record-retrieval-companies ### End Users by Industry - Law Firms: Legal case record retrieval - Car Insurance: Claims-related medical records - CROs (Contract Research Organizations): Clinical trial data - Pharma: Life sciences research data - Health Plans: Insurance claims and medical records - Life Insurance: Underwriting medical records - Government: Regulatory and compliance records - Diagnostic Companies: Lab and testing records --- ## Partner Program ### ROI Partners URL: https://www.hermeshealth.com/roi-partners Release of Information vendors who integrate with Hermes to receive and fulfill record requests. ### Claims Partners URL: https://www.hermeshealth.com/claims-partners Claims data providers who supply Tier 1 and Tier 2 data to the Hermes network. ### Regional HIE Partners URL: https://www.hermeshealth.com/regional-hie-partners Regional health information exchanges that connect encounter, ADT, and clinical data to authorized record-retrieval requestors through Hermes. Regional HIEs can support payment, operations, and patient-authorized use cases. National HIEs are treatment-only and are not this partner type. Hermes is a single neutral integration for long-tail retrieval companies and law firms. Regional HIE partners keep participant lists, pricing, and operational data private. Platform integration is free. Hermes aggregates authorized requests, standardizes intake, and handles requestor communications while the HIE fulfills from existing systems. ### RX Partners URL: https://www.hermeshealth.com/rx-partners Pharmacy and prescription data partners who enrich retrieval and analytics workflows. ### Lab Partners URL: https://www.hermeshealth.com/lab-partners Clinical, pathology, and genetic testing laboratories that connect structured results and reports to authorized medical record workflows through the Hermes network. --- ## Contact Information - Website: https://www.hermeshealth.com - Email: info@hermeshealth.com - Platform: https://www.hermeshealth.ai - CEO/Founder: Alejandro Zamorano (Alejandro@hermeshealth.com, 508.397.8440) - Demo: https://calendly.com/alejandro-hermeshealth/30min