Healthcare Administrative Automation
A

ArisGlobal

ArisGlobal sells LifeSphere, a cloud suite for pharmacovigilance, regulatory affairs, medical information and quality management, to more than 220 drug makers, contract research organizations and health authorities. NavaX, the AI engine it launched in late 2023, reads adverse event reports, extracts fields into safety case forms and drafts case narratives, and runs agents for MedDRA coding, case distribution and signal detection. Advanced Intake can sit over an existing safety database, while MultiVigilance brings intake, case management and regulatory submissions into one system. Literature Intelligence finds material to review for safety cases, Medical Information routes inquiries and drafts responses from approved content, and Regulatory Intelligence tracks changes in requirements and their effect on a sponsor's registrations. Users review and approve NavaX output before relying on it, and customer data is not used to train or fine tune the models.

Boehringer Ingelheim deployed Advanced Intake for individual case safety reports and reached up to 90% average extraction accuracy on case forms within weeks, with its quality control steps still in place. Maruho, a Japanese dermatology company, selected MultiVigilance and NavaX for its global safety operations, CHEPLAPHARM chose LifeSphere Safety and Medical Information, and YURiA-PHARM went live with LifeSphere Regulatory in February 2026.

Deepak Abbhi founded ArisGlobal in 1987, and the company is based in Waltham, Massachusetts. Dassault Systèmes acquired it in 2026 and sells LifeSphere under the ArisGlobal name.

AI Health Index verifiedNovember 20, 2026
Compare ArisGlobal with other vendors
Founded
1987
Headquarters
Waltham, Massachusetts, United States
Categories
healthcare-admin-automation
Indexed Products
LifeSphere Unify, NavaX, Advanced Intake, MultiVigilance, Literature Intelligence, Medical Information, Regulatory Intelligence, Advanced Compliance Docs
Buyer Segments
Pharmaceutical and biotechnology safety teams, Contract research organizations, Medical affairs and regulatory teams, Government health authorities
Assessment

Capability Axes

An AI Health Index grade measures what a buyer can verify from public sources on the date shown. It is not a rating of how good the product is. A vendor can build an excellent system and grade low on an axis because it publishes nothing an outsider can check. How grades read

AI Capability
BB on AI CentralityThe model is the engine of a core module. The platform carries other value, but this capability does not exist without it.
Vendor Published

NavaX extracts fields from adverse event reports and writes case narratives for pharmacovigilance teams, and its agents code events to MedDRA, distribute cases and surface safety signals. Advanced Intake takes documents in several formats and sends the extracted information into a safety database, and MultiVigilance connects intake to the case record and the submission workflow.

Medical Information uses the same engine to route inquiries and draft responses from approved material, and Regulatory Intelligence applies it to tracking regulatory change. The safety database, reporting formats, submission tools and document management all run without NavaX, which is sold as the intake, coding and drafting layer on top of them.

BB on Autonomy and Oversight ModelThe oversight structure is described and one part is missing, commonly the threshold at which the system stops or what happens after it is wrong.
Vendor Published

Users review and approve NavaX output before relying on it, and the AI Trust Center FAQ names human review thresholds and confidence scoring as the controls that send work to a person. At Boehringer Ingelheim, a safety reviewer checks fields extracted by NavaX before a case moves on, and quality control stayed in place after Advanced Intake went live. NavaX constrains output to typed fields and checks them against the source document.

MultiVigilance can also run qualifying cases from intake through submission with no manual step. The confidence level that routes an extraction to review, and the rule for which cases may skip a person, are left to each workflow with no values given.

BB on Model and Technology TransparencyThe approach or the suppliers are named without the version and update discipline behind them. Naming a supplier is the entry to this band both here and on Model Supply Chain Disclosure, which ask different questions of the same disclosure: who receives the data, and what produces the output.
Vendor Published

In a technical account coauthored by ArisGlobal engineers, Claude Sonnet 4.5 serves adverse event extraction through Amazon Bedrock, and the AI Trust Center FAQ describes NavaX as built on commercially available foundation models.

NavaX splits a case into sections and sends a series of model requests whose instructions carry a schema of around 130 fields, examples, customer rules and formatting constraints for different reporting regimes; a validation step ties each field back to the source PDF. Customer data does not train or fine tune the models. Training data, version pinning and the schedule for model changes in production are not given, nor is the model behind the other NavaX modules.

BB on Model Supply Chain DisclosureSubstantial partial disclosure, or a chain that is structurally short: an in house build, a cleared model that cannot be quietly swapped, or a deployment where the transfer does not occur at all. Naming the model provider exits the band below into this one; the axis rises from here on the completeness of the party list and on the terms that govern data once it arrives.
Vendor Published

Amazon Web Services hosts LifeSphere and runs Amazon Bedrock, which supplies the Anthropic model behind NavaX's adverse event extraction. ArisGlobal sets the case schema, customer mappings and instructions, which are reused through Bedrock prompt caching, and the production design processes each individual case document after the cache checkpoint so the PDF stays out of the shared cached portion. NavaX Translation is offered with TransPerfect Life Sciences. Customer data does not train or fine tune the models, but the retention terms that apply to patient material at Bedrock, and a full list of the parties that process safety case data, are not given.

CC on Clinical and Operational EvidenceNamed customers, or vendor reported percentages with no method, denominator or reference standard. Scale of use is recorded here and is not treated as evidence of benefit.
Vendor Published

Boehringer Ingelheim's Advanced Intake rollout reached up to 90% average extraction accuracy on adverse event case forms within weeks, with the customer's quality controls still running; no form count or rule for scoring a field as correct comes with the figure. An unnamed pharmaceutical customer using Dynamic Data Extraction and Narrative Generation reported a 17% gain in intake efficiency in its first three weeks.

Maruho and CHEPLAPHARM have selected the safety suite and YURiA-PHARM is live on the regulatory suite, with no results yet from those deployments. LifeSphere counts more than 220 organizations as users across the suite.

BB on AI Safety and PHI StewardshipCategorical commitments are published, such as no training on customer data, without the retention schedule behind them.
Vendor Published

A NavaX extraction request carries an adverse event report that can hold patient details. ArisGlobal states that customer data is not used to train, retrain or fine tune AI models. In the Bedrock deployment, filtering can detect or mask sensitive information, extracted fields are checked against the source, and the shared prompt cache excludes the individual case document.

The privacy policy treats services data as confidential under the customer contract, limits subcontractors to the contracted purpose and provides for return or destruction at contract end, while retention follows each customer agreement with no number of days stated. Retention of raw reports, outputs and model logs, and the handling of an AI safety incident, are not described.

Regulatory and Compliance
CC on HIPAA and BAA PostureA status is stated but not supported: compliance is claimed, or business associate status stated, without the underlying document, including where the only privacy notice published covers the website rather than the service that handles patients. The mirror case grades here as well: a substantive privacy document that reaches the service, with no statement of business associate status anywhere and no scope position taken. One of the two elements the band above asks for is present, which is a grade below it and not a grade at the floor.
Vendor Published

LifeSphere handles adverse event reports that can include protected patient data. ArisGlobal's privacy policy has a services data section covering information on its hosted systems and on customer or third party systems it accesses to perform services, keeps that data confidential under each customer contract and restricts what subcontractors may do with it.

The same policy says ArisGlobal has no access to personal data customers store in its products, while the Bedrock workflow sends case fields through a cloud model, and the two statements are not reconciled. A 2019 company post called its security compliant with HIPAA among other standards, before NavaX existed. No business associate agreement or terms for HIPAA covered customers are offered.

DD on Security Certifications and Trust CenterControls are asserted with nothing independent behind them, or nothing is published. Read the note before concluding anything: this is the grade most often corrected on a second pass, because assurance material frequently sits on a parent domain or inside an old announcement rather than on the product pages.
Vendor Published

MultiVigilance runs as a multitenant service on AWS, and ArisGlobal keeps a status page for it and other LifeSphere tools. Its service privacy provisions refer to access controls and limits on subcontractors, and the July 2026 AI Trust Center FAQ places data access and storage under the company's information security policies without naming a certification.

Older material carries the only named frameworks: a 2018 presentation on the earlier Safety estate cited SOC 2 compliance and ISO 27001 certification for development, and an April 2019 post called LifeSphere's security compliant with ISO 27001, SOC 2, GDPR and HIPAA. Both predate NavaX, and no current report, certificate or audit period is tied to the AI workloads.

CC on FDA and Regulatory StatusNo device claim is made and the product is scoped accordingly. Most administrative and operational products sit here and are not penalized for it, because this axis grades the appropriateness of the positioning rather than possession of a clearance. A stated limit on use, such as research use only or a clause that the product gives no medical advice, beside marketing that sells the product for clinical decisions also sits here, with both quoted, because the buyer has to ask which one governs.
Vendor Published

LifeSphere is marketed for pharmacovigilance and regulatory operations and makes no device claim. MultiVigilance prepares individual case safety reports in the formats regulators accept, including E2B(R3), and NavaX extracts case details and drafts the narrative inside that sponsor workflow. At Boehringer Ingelheim, quality control stays on the extracted fields, and the resulting forms feed medical review and benefit risk analysis by the sponsor's own staff.

ArisGlobal counts FDA, Health Canada and NMPA among the regulators it works with, and health authorities use the broader suite. The product supports a sponsor's reporting duties rather than any clinical decision about a patient.

CC on AI Governance and Bias DisclosureResponsible artificial intelligence is committed to in policy language with no evaluation behind it. Most of the index sits here.
Vendor Published

NavaX runs case extraction under Bedrock controls and checks each field against a schema and the source report, and sponsors set how fields map and how the workflow handles reporting rules that differ by jurisdiction. ArisGlobal's AI Trust Center FAQ, dated July 2026, lists bias among the risks that validation, monitoring, confidence scoring, human review and governance processes are meant to address, without describing a bias test or its results.

LifeSphere's quality and safety workflows add controlled documents and review. Intake and translation span many source languages, yet no results compare accuracy across languages, case types or reporting populations, and no outside evaluation of NavaX's behavior is available.

CC on AI Liability and RecourseMechanisms exist that let someone challenge an output, such as audit trails, source traceability or review before commit, with nothing standing behind the output and no route for the harmed party.
Vendor Published

Each extracted case field can be checked against the source report and the requested output schema, and Boehringer Ingelheim's safety teams kept quality control over forms processed by Advanced Intake, so sponsor staff can challenge a value during case handling. ArisGlobal's AI Trust Center FAQ states that it does not guarantee AI generated outputs will be error free and that users remain responsible for reviewing and approving outputs before relying on them.

The Boehringer accuracy figure comes with no form count, scoring method or contractual commitment, and service obligations sit in each customer agreement. A patient whose details appear in a submitted case has no correction route against ArisGlobal, and an incorrect narrative carries no stated remedy.

Integration and Deployment
CC on EHR and Interoperability DepthIntegration is claimed through standards or a middleware layer with no system named and nothing to verify.
Vendor Published

No clinical record integration is offered for LifeSphere; its connections run to safety databases and regulatory gateways. Advanced Intake receives reports in several formats and can run above a sponsor's existing safety database, and MultiVigilance carries case data into submission preparation in E2B(R3), the standard exchange format for individual case safety reports.

Maruho's implementation migrates its historical safety records to the new platform, a one time load rather than a live connection. No outside safety database is named as a connector, and how the connectors read or write individual case fields is not described.

CC on Deployment Model and Data ResidencyA single hosted option with location implied rather than committed.
Vendor Published

LifeSphere runs on AWS as a multitenant cloud, and MultiVigilance uses a shared cloud architecture. NavaX extraction uses European cross region inference through Amazon Bedrock, with customer specific mappings applied during processing.

The privacy policy places service providers in the United States and Europe and governs transfers out of the European Economic Area with standard contractual clauses, and the AI Trust Center FAQ says data is stored in the customer's contracted environment, with processing locations set by the agreement. Where case records and backups rest, which path serves customers outside Europe, and whether NavaX can run in a dedicated tenant or on premises are not stated.

Commercial
CC on Commercial TransparencyNo price is published and the posture is discoverable: a buyer can establish how the product is sold and what drives the cost before contacting the vendor. Most of the index sits here.
Vendor Published

LifeSphere Safety is sold as a cloud suite, and Advanced Intake can be installed above an existing safety database without a full move to MultiVigilance. A sponsor can instead buy a package that migrates its records, as Maruho plans to do, and add literature review and other modules. Migration and implementation support are offered on the same order. LifeSphere is listed on the SoftwareOne marketplace, and ArisGlobal offers a demonstration. No entry price, subscription rate or unit of charge appears for NavaX, and charges vary with the modules selected, with no word on how report volume or user counts move them.

BB on Setting and Specialty CoverageCoverage is named with validation behind part of it.
Vendor Published

Boehringer Ingelheim runs individual case safety reports through Advanced Intake and has reported extraction results since rollout. Maruho chose the safety suite for global pharmacovigilance in a dermatology business, moving to one safety database with its existing records migrated, and CHEPLAPHARM selected LifeSphere Safety with Medical Information. YURiA-PHARM went live on the regulatory suite in February 2026.

LifeSphere sells to drug makers, contract research organizations and public health authorities, and covers medical inquiry handling and regulatory intelligence beside safety reporting. Measured results exist only for case intake, with nothing by therapeutic area and nothing yet for the medical inquiry or regulatory AI tools.

Alternatives

Alternatives to ArisGlobal

Other products that do the same kind of work as ArisGlobal, and what each one does.

Authenticx, founded in Indianapolis in 2018 by former healthcare executive Amy Brown, analyses the conversations healthcare organizations have with patients, members and professionals across telephony, chat, messaging, email and CRM notes, and reports what they reveal at a system level.

Courier Health gives biopharma teams a shared system for managing patient access to specialty therapies. It connects information from hubs, specialty pharmacies, payers and internal teams so staff can see enrollment progress, authorization barriers, therapy starts and ongoing adherence.

Sample Healthcare, founded in San Francisco in 2023 and backed by Y Combinator, builds AI copilots that read medical records and clinical documents and carry out the administrative work around them.

ReferralMD runs referral management for practices, health systems and provider networks, bringing faxed referrals, online submissions and record feeds into one work queue.

Flexbone, based in Atlanta, builds AI agents for administrative operations, primarily in healthcare; its privacy policy describes it as a healthcare automation company working with providers and payors.

Honey Health sells AI agents that do back office work inside a practice's EHR and the other systems its staff use, logging in and working the screens the way a trained employee would, so no API project is needed.

Commercial

Pricing

Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.

Entry Price Pricing Basis BAA Tier Implementation Source
Quote based
LifeSphere Safety is sold as a SaaS platform with separately selectable capabilities. Advanced Intake can be installed above an existing safety database. A MultiVigilance implementation can include migration of historical records. No business associate agreement is offered. Migration and implementation support are offered on the order, with no fee shown. Vendor Published

ArisGlobal offers a demonstration, and LifeSphere Safety is listed through SoftwareOne. No entry rate, price per case or subscription tier is shown for NavaX, and no fee is shown for translation, additional usage or migration.