Friendly

The about page states the platform digitizes any document from any source, and the features page says Friendly imports and processes the customer's medical data and lets a team share a case as a customizable summary report to feed their own system or print out. Ingestion of case files and export of a report is the whole documented integration surface: no connector, catalog, custom tool route or authenticated action in an outside system is named. No agent action in an outside system is documented, and the published surface is thin, file based ingestion and export with no system named.

SourceFriendly, friendlycares.com/features and friendlycares.com/aboutread 2026-09-07

The about page states the platform digitizes documents, produces summary reports, auto adjudicates claims and enables new business straight through processing, with people called on to review a case or approve a payment when needed; the underwriting page shows the processing pipeline as classify, group, cleanup and structured report. That is a fixed multi step pipeline the vendor runs end to end on a case, not orchestration the customer composes: no workflow builder, no multi agent execution, no named runtime and no multi participant workflow is documented.

SourceFriendly, friendlycares.com/about and friendlycares.com/underwritingread 2026-09-07

The features page documents that imported case documents are OCR extracted, structured into cards grouped by diagnosis, abnormal labs, vitals over time and physical exams, connected to SNOMED, ICD-10 and LOINC codes, and presented in a case dashboard where every item links to its source; an AI chat assistant then answers questions by searching across all documents in a case, and a treaties advanced query searches and filters across a collection of reinsurance treaties. The structured, coded extraction persists as the case record and stays queryable by the assistant, which is a maintained retrieval structure over the customer's documents rather than context assembled per run.

SourceFriendly, friendlycares.com/featuresread 2026-09-07

Claims are auto adjudicated, and the about page says people are called on when needed to review a case or approve a payment; the underwriting and features pages present recommendations on next best actions for a human decision. That is a one sentence claim that an approval step exists for payments and exceptions. No review surface, approval queue, configuration of what routes to a human, or the conditions that trigger review is documented.

SourceFriendly, friendlycares.com/about and friendlycares.com/underwritingread 2026-09-07

The features page says the platform adheres to HIPAA, GDPR and SOC 2 guidelines, and the underwriting page says deployment ensures HIPAA, GDPR and SOC 2 compliance; neither asserts an audit or certification, so the posture is alignment rather than attestation.

The features page also names advanced encryption, multi layered access controls, continuous threat monitoring and a PII anonymizer, but no identity integration (SSO, SAML, SCIM) and no named access model (roles, RBAC, permissions) is published.

There is no trust or security subdomain and no product documentation, and the site is a Wix marketing site with a privacy statement.

SourceFriendly, friendlycares.com/features and friendlycares.com/underwritingread 2026-09-07

Every piece of information in the case dashboard links to its original source, so a reviewer can click through to where it came from, and a case timeline follows each medical event. That is provenance for extracted outputs, showing what the extraction says and where it came from, not a runtime record of what the agent did: no log of agent actions, decisions, model calls or adjudication steps, no reconstruction of why an auto adjudication landed where it did, and no audit export is documented.

SourceFriendly, friendlycares.com/featuresread 2026-09-07

The persistent case history and timeline belong to the case itself. The case dashboard, timeline and structured extraction are the customer's case record, the application's data model, and deleting them would delete the case. No memory layer with a stated scope and lifetime, per user, per team or per workflow, is documented, and no session state for the chat assistant is published.

SourceFriendly, friendlycares.com/featuresread 2026-09-07

The features page states the platform runs whether hosted in Friendly's secure infrastructure or within the customer's own private cloud, and the underwriting page says it easily deploys on private cloud infrastructure. Customers can deploy into their own private cloud or use vendor hosting, so a buyer with a different requirement gets a different answer. No hosting region for the vendor hosted option, no deployment documentation and no selection surface is published, and the option rests on a marketing sentence.

SourceFriendly, friendlycares.com/features and friendlycares.com/underwritingread 2026-09-07

The site presents three solution lines, underwriting, claims and treaties, and a set of named features on one platform: HealthGrid and Focus Grid, case dashboard, chat assistant, medical summary, narrative summary, case timeline, pattern recognition and PII anonymizer. These are modules and views of one product rather than separate agents a buyer selects and adopts as they stand, and no template library or catalog of prebuilt agents is published. The Omniscient treaty assistant is a named product on the press page, but it is one product, not a pack.

SourceFriendly, friendlycares.com/features and friendlycares.com/newsread 2026-09-07

Processing starts when a case file is imported: the features page says work begins once Friendly imports the customer's medical data, and the about page says documents are digitized from any source. Case arrival is the only documented trigger; no event, schedule, webhook or inbound queue is documented, and the chat assistant is invoked by a user.

SourceFriendly, friendlycares.com/features and friendlycares.com/aboutread 2026-09-07

The features page says Friendly's model is trained to recognize medical data and can be trained on additional languages, describing the vendor's own models. No model provider is named, and no customer or admin choice of model or routing is documented.

SourceFriendly, friendlycares.com/featuresread 2026-09-07

No API, SDK, MCP server or other interface for calling the platform from outside is documented, and there is no developer documentation. The only outbound surface is a summary report a team can export to feed its own system, which is a file handed back, not an interface for driving Friendly. The vendor calls the product a software only infrastructure layer, which suggests embeddability, but nothing documents it.

SourceFriendly, friendlycares.com/featuresread 2026-09-07

The features and underwriting pages document pattern recognition that uncovers mismatches between medical data and disclosures, discrepancy highlighting and fraud signals. The artifact under test there is the customer's case, data quality on the applicant's file, not the agent, and no evaluation harness, scored test cases, release gate, controlled loop or debugging trace for the platform's own outputs is published.

SourceFriendly, friendlycares.com/features and friendlycares.com/underwritingread 2026-09-07

The platform OCR extracts and structures uploaded documents, handwritten notes, lab results, X-rays and EHR exports, at up to 7,000 pages an hour, and presents them in its own dashboard; that is ingestion into the case record, not computer control. No browser, desktop or computer control driven by the agent at run time is documented.

SourceFriendly, friendlycares.com/features and friendlycares.com/underwritingread 2026-09-07