D

DigitalOwl

The models are the whole product, with nothing beneath them. DigitalOwl does one thing, turning unstructured medical records into structured data, and every part of it is model work: extraction from conventional and electronic health records, building chronologies, classifying by impairment and body part, spotting soft medical terms, detecting changes in condition status, and a chat interface over the records. The vendor says its AI is proprietary, built by in house experts and trained for these uses rather than adapted from a general tool.

Connect exposes the model output as an API for other systems, which shows plainly that the extraction is the asset. Remove the models and there is no product, only a file upload. The product is owned by Datavant and still sold under its own name.

An accuracy figure is published, short of the evidence that would make it checkable. The vendor says the platform is third party tested at over 98 percent accuracy, attributing the number to independent testing. What is missing is everything that would let a reader test it: no evaluator, method, sample size, test set or date, and above all no definition of accuracy for this task. Extraction accuracy could mean correctly transcribed values, correctly classified pages, correctly ordered events or correctly identified providers, which are very different measures giving very different numbers. A figure without a definition or an evaluator cannot be verified or compared.

A clear positioning statement exists and no operational boundary does. The vendor says plainly that the platform is a tool to support legal professionals, not replace them, and that it cannot substitute for their judgment, decision making or expertise. That is a statement about role, not a description of the oversight model. Nothing published says whether any extraction or classification is applied without human review, whether a low confidence result is shown differently, what happens when the chat interface answers a question the records do not support, or what review the Self-Serve output gets before delivery inside 24 hours.

Independent recognition and a corporate outcome are both dated and checkable, and no customer is named. The Self-Serve legal platform was named an Innovative Product Winner in the 2026 BIG Innovation Awards, a named program with a dated announcement. Datavant, a major health data company, acquired the company in 2025 in an arm's length deal. Published operational figures are specific: up to 72 percent of medical record review time saved, review time cut by up to 50 percent, page count cut by 90 percent, and a thousand page record reviewed in minutes.

But no law firm, carrier or customer is named in any material located, no case study with a method exists, and every efficiency figure carries an up to qualifier with no baseline, sample or period.

A strong set of instruments, and an unaddressed conflict question. Published: SOC 2 Type II, HIPAA and GDPR compliance, a business associate agreement offered to customers and covered entities, secure storage of uploaded records, and manual deletion by the customer at any time. That is a real set of protections for the claimant health information at stake. The open question is that this vendor sells to both sides. Its legal offering serves plaintiff personal injury, medical malpractice and mass tort firms, and its insurance offering explicitly includes streamlining review of inbound settlement demand packages and bodily injury claims for carriers.

Those are the same disputes seen from opposite ends, and nothing published describes what separates a plaintiff firm's uploaded records and case insights from the carrier side of the business. No treatment of attorney client privilege or work product is published either.

The claim is made and no framework sits behind it. The vendor says the platform is a tool to support legal professionals, not replace them, and that it cannot substitute for their judgment, decision making or expertise, in a post addressing attorney resistance to adoption. That is a direct and relevant position. What is missing: no statement that output is not legal advice, nothing on the supervising attorney's duty over machine extracted medical facts that will support a demand, no guidance on checking before reliance, and no engagement with bar guidance. A sentence in a blog post about adoption worries is a claim, not a professional responsibility framework.

The vendor tells buyers to demand the disclosure it does not make. Its own buyer guidance advises firms choosing medical chronology software to ask whether the platform has had independent bias and accuracy testing. It says reputable providers will be open about their validation and able to show their AI gives reliable, unbiased results across case types and medical conditions. DigitalOwl publishes an accuracy figure and nothing on bias.

No bias or fairness testing, validation method, AI policy, model card, evaluation output, accuracy monitoring, named governance body or ISO 42001 is published. The untested risk is concrete for a product extracting clinical facts. Documentation quality and diagnostic language vary systematically across providers and patient groups, and differences in how the model performs across those groups would shape which injuries appear in a demand.

Data control is disclosed specifically, and the training question is unanswered. Records uploaded to the Self-Serve portal are stored securely and the customer can delete them manually at any time, a control the user can exercise rather than a policy assurance. Alongside it sit a business associate agreement, SOC 2 Type II, HIPAA and GDPR compliance, and a published trust page. GDPR compliance brings data subject rights, which matter here because the person whose records these are is a third party to the customer relationship.

Nothing says whether uploaded medical records, generated chronologies or extracted data are used to train or improve the proprietary models. No retention period is published for data the customer does not delete, and nothing says what happens to derived structured output when the source records are deleted. A deletion control answers how long, not what for.

No published position located beyond the BAA, which allocates HIPAA obligations between the parties rather than product liability. Nothing was found on liability for AI output, warranty, service levels or remedy. The exposure is asymmetric in a way particular to this product: a missed diagnosis, an omitted provider or a misdated treatment in an extracted chronology understates an injury, and on the plaintiff side that flows into a demand that settles low while on the carrier side it supports a denial, so the same extraction error harms a claimant in both directions.

The published 98 percent accuracy figure implies a residual error rate by its own arithmetic and no published position addresses who bears it.

A real integration product exists and it is aimed at the other half of the customer base. Connect is a medical data API allowing clients to retrieve and integrate structured output into rules engines, workbenches and custom workflows, and it is sold as a named product rather than mentioned as a capability, which is genuine integration substance. The language and the named destinations are insurance systems: rules engines and workbenches are carrier claims and underwriting infrastructure, not law firm systems.

No legal case management system is named anywhere in located material, no document management connector, and no integration with the platforms a personal injury firm runs on. A plaintiff firm gets a self serve upload portal and an API it would need to build against itself.

Nothing located. No hosting provider is named, no region or data residency commitment is published, and no single tenant or dedicated instance option is described. Stated GDPR compliance implies the vendor handles European personal data and says nothing about where it is processed or stored, and a company holding United States claimant medical records under HIPAA alongside European obligations is exactly the case where residency would be stated if it were designed for.

Three regimes and a trust page are published, without dates. The vendor states SOC 2 Type II, HIPAA and GDPR compliance, offers a business associate agreement to customers and covered entities, and publishes a dedicated trust page, Trust at DigitalOwl, linked from product pages. A business associate agreement is the instrument HIPAA actually requires, not a claim about compliance. No auditing firm is named, and no examination period, scope or certificate date is published for the SOC 2, so its currency cannot be established. The trust page itself was not read and is the page most likely to carry dates and scope.

Nothing located. The AI is described as proprietary and built by in house experts, which is an ownership statement rather than a supply chain disclosure, and no foundation model provider, model family or version is named. No subprocessor list was found. The acquisition adds an unaddressed dimension rather than resolving one: Datavant is a health data platform company and nothing published describes what data or processing relationship now exists between the two, which for a business associate handling protected health information is a question a covered entity is entitled to have answered.

No pricing is published at any level. There is no price, range or unit of charge, and no sign of whether the Self-Serve portal charges per case, per page, per record set or by subscription. That matters because a self serve product is exactly where a firm expects to see a price before engaging. An independent review site reports a starting figure of $7,500 a month; that is a third party estimate, not disclosure, and if roughly right it puts the product beyond small firm reach.

Case costs in contingency work are advanced against a claimant's recovery, so undisclosed cost is undisclosed cost to an injured person.

Coverage is broad and spans both sides of the market. Legal coverage names personal injury, medical malpractice and mass tort. Insurance coverage names underwriting, claims review, post issue audits, long term care application review for material misrepresentation, workers compensation, property and casualty claims, bodily injury, and review of inbound settlement demand packages. Records covered include both conventional and electronic health records, a real technical distinction since EHR exports and scanned paper files pose different extraction problems.

But breadth is asserted rather than characterized. Nothing says which record formats, provider systems or document types the extraction handles reliably, no jurisdictional scope is given, and nothing shows whether the 98 percent accuracy figure holds evenly across record types or was measured on a favorable subset.