1health

Name: 1health
Brand: 1health
Rating: 3.2 (1 reviews)

1health is a middleware interoperability platform that assembles consolidated patient records from multiple clinical and administrative sources, enforces consent and provenance metadata, and exposes patient- and workflow-oriented functionality (patient management, provider lookup, lab ordering) via a unified API.

27 Ref Customers

Website

Published Sep 29, 2026

01Common complaints

- If procurement requires a platform with a substantial, verifiable public review footprint - The vendor has limited presence on major review platforms based on the searches conducted; buyers who require extensive Gartner/G2/TrustRadius coverage before engagement may prefer vendors with larger public review samples. - If TEFCA/QHIN participation is a strict requirement today - The vendor references TEFCA connectivity but does not clearly document whether it is a QHIN or is participating via another QHIN relationship. Buyers should confirm network status and obtain supporting documentation if TEFCA connectivity is a primary requirement. - If the primary requirement is historical HIE network data retrieval rather than cross-organization workflow - Vendors that focus primarily on record retrieval from established networks may be a closer fit for use cases centered solely on data retrieval rather than workflow orchestration. - If organizational risk tolerance is highly sensitive to prior regulatory enforcement - The FTC order related to historical consumer genetic-data activities associated with the entity is a material diligence item; some buyers may prefer vendors without such an enforcement history. - If transparent, self-serve pricing is a strict procurement requirement - Lack of a public price list increases evaluation time and may necessitate sales engagement to obtain pricing details. - Current limitations acknowledged by vendor - The vendor documentation does not present an explicit public list of limitations; buyers should request GA vs beta status for specific features and workflows during diligence. - Roadmap / not yet available - The vendor references multiple workflows beyond transitions of care; buyers should verify which capabilities are generally available (GA) versus in pilot or beta. - Scale limitations - Scalability and performance characteristics are not documented publicly; buyers should validate via reference checks, SLAs, and architecture review. - Security or compliance gaps - The vendor asserts SOC 2 Type II and HIPAA compliance, but no public audit reports were located in the sources reviewed. The historical FTC enforcement action associated with prior consumer-facing activities represents a risk signal that should be addressed in procurement and legal review. - API limitations / integration constraints - Public documentation does not provide exhaustive details on API ergonomics, rate limits, and identity-resolution edge cases; buyers should perform technical testing (POC) to validate these aspects.

Deal disqualifiers

Organizations that require extensive public third-party validation on review platforms prior to engagement
Procurement processes that require fully public security documentation and fully published pricing information without any vendor sales engagement

02Why they buy

- Consolidated patient record model assembled from multiple data sources with provenance metadata and consent governance (vendor assertion). - Multi-modal connectivity options that include standard API and messaging standards as well as document ingestion for less-technical partners (vendor assertion). - Overlay adoption approach intended to integrate without replacing existing EHRs and interoperability infrastructure (vendor assertion). - Developer-oriented platform with a shared data model and workflow primitives for functions such as patient management, provider directory, and lab ordering (vendor assertion). - Evidence from independent sources is limited; most differentiation claims are presented in vendor-authored materials and case studies.

03Field reports

- Review platforms (Gartner Peer Insights, G2, TrustRadius) - Gartner Peer Insights - No clearly discoverable product listing or reviews for the 1health interoperability product were found in the publicly accessible searches conducted for this analysis. Gartner’s platform can restrict automated access and often requires direct interaction for full results. - G2 - No clear listing for 1health as a healthcare interoperability product surfaced in the searches performed. Some search results returned unrelated similarly named products. - TrustRadius - No direct product page for the 1health interoperability platform was identified in quick results; additional interactive searching may be required. - Community/Social (Reddit) - Public forum discussions include references to a historical regulatory enforcement action and criticisms tied to the vendor’s historical consumer genetic-testing activities. Some community comments express concerns about privacy practices and customer service in that consumer context; links between that historical activity and the current enterprise product are not clearly documented in public community posts. - HackerNews - No clear Hacker News threads specifically discussing the current 1health interoperability product were identified in the searches conducted. - Why customers chose this product over alternatives (evidence quality) - Vendor case studies and product documentation cite factors such as rapid implementation for specific workflows and the ability to share records across organizations. These are vendor-provided narratives; independent validation of those claims was not available within the scope of this review. - Why some customers left for competitors (churn reasons) - No reliable, product-specific churn narratives or third-party reports about customer defections were identified in the public sources reviewed. - Vendor-published case studies (available, but not independently verified) - ### Transitions of Care - Vendor-published claims include rapid implementation for an application and a reported monthly patient volume. These claims are plausible if the platform provides high-level primitives (identity, consent, provider directory, lab ordering), but they lack independent verification and methodological detail (for example, how patient/month metrics are measured). - Critical evaluation: Buyers should request additional context on integration complexity, the number and diversity of EHR endpoints, consent models used, and metrics definitions before relying on these published performance claims. - ### Symphony case study - The vendor case study indicates an interoperability engine and a cross-organizational shared medical record layer intended to reduce manual fax-based processes. - Critical evaluation: The general objective of reducing manual handoffs aligns with common market needs, but prospective buyers should validate specifics such as endpoints integrated, data completeness and reconciliation approaches, exception handling, and measured operational outcomes.

04Best fit

Company sizes (practical estimate)

- Likely mid-market to enterprise healthcare organizations, including: - Health plans with significant transitions-of-care volume - Health systems coordinating care across multiple practices and partners - Digital health companies that require cross-organization data assembly and workflow capabilities - Indicative employee count / revenue ranges: organizations with multi-entity care networks and substantial referral/discharge volume (e.g., mid-sized to very large organizations), though exact thresholds will vary.

Industries and verticals

Health plans (care management, transitions)
Hospital systems (discharge coordination, readmission reduction)
Ambulatory practices that receive referrals/discharges
Labs and pharmacies as data sources or workflow endpoints

Roles and personas

Decision makers: CIO/CTO, VP of Interoperability, Chief Data Officer, Security/Compliance leadership, Care Management leadership
End users: care managers, transition-of-care coordinators, practice schedulers, clinical operations teams, and developers building on top of a shared record API

Pain points addressed

Manual handoffs and administrative overhead (including fax workflows), fragmented patient records across organizations, and patient identity reconciliation across heterogeneous sources

Qualification criteria

Organizations with high-volume transitions/referrals where reductions in manual work yield measurable ROI
Willingness to adopt an overlay approach rather than replacing core EHR systems
Need to connect multiple organizations with varying technical maturity

05The pitch

What the product does (core value proposition in objective terms)

- 1health describes its offering as a middleware platform for healthcare data exchange and cross-organization workflows. The vendor states the product is intended to reduce manual hand-offs (faxing, calls, chart review) that occur when patients transition between organizations by assembling a consolidated patient record from multiple sources and exposing data through an API. - The vendor states it can ingest data via multiple connection methods, including HL7, FHIR, APIs, flat files, and fax/paper, and then perform identity resolution, preserve originals with provenance metadata, and enforce consent-based access controls. - The developer documentation presents the product as a platform the vendor describes as HIPAA-compliant and that exposes functionality such as patient management, provider lookup, and lab ordering through a single API.

Target market and market positioning

- Primary market (per vendor messaging) - Payers/health plans, hospitals/health systems, ambulatory practices, and patients—specifically workflows that span organizations (transitions of care, referrals/consults, lab orders, provider directory, risk & quality). - Positioning - The vendor characterizes the product as an overlay layer intended for incremental adoption rather than wholesale replacement of existing systems; initial engagements commonly focus on a single hand-off between two organizations with the option to expand additional integrations over time. - The platform is presented as a shared data layer intended to allow multiple applications to access and update the same assembled patient record while centralizing identity resolution, consent, and compliance controls.

Get a comprehensive analysis of 1health including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →