Platform
Every person, payment and interaction, linked.
Cortex keeps one record for each, connected to the policies and cases that touch it.
Expense line
Dinner, Bistro Laurent
- Date
- 14-Sep-26
- Amount
- $412.00, 4 attendees
- Per person
- $103.00
- Source
- Expense report ER-58213
Linked records
Integrations
Connect the systems you already run. An expense is an expense, whether it comes from an expense tool, an ERP or a spreadsheet.
Your systems
Standard records
The graph
- Reference data from EthicsVue
- NPPES · CMS Open Payments · Exchange rates · Sanctions and exclusion lists
- Outbound
- Email · Microsoft Teams · Slack · Webhooks
Connect
A connector, a database view or a file upload brings a system's records in as they are.
Map
The assistant proposes how the system's fields map to a standard record, and a person approves the mapping.
Match
Cortex matches people and companies to records on the graph, and sends the matches it can't decide to a person to review.
Is "Dr. A. Ruiz" in the expense system the same person as Ana Ruiz, MD in NPPES?
Suggested: same person, 92% confidence
Agents
AI does the legwork. It works with the permissions of the person who runs it, and shows what it read and what it will change.
The review agent proposes. Your reviewer decides. Each answer shows its source.
Review RC-1187, flagged meal
Dinner, Bistro Laurent, Boston
14-Sep-26, Jordan Ellis, expense report ER-58213
$412.00
Dr. Maya Okafor, Dr. Samuel Reyes, Jordan Ellis and one other employee
Meal over per-person limit
$103.00 per person against a $100.00 dinner limit for the United States.
Checklist, drafted by the assistant
Who attended?
Two HCPs and two employees
Expense attendee list, matched to NPPES
Within the per-person limit?
No. $103.00 against a $100.00 dinner limit
Limit table: HCP meals, United States, dinner
Alcohol on the receipt?
Yes, $64.00 of wine
Itemized receipt, lines 4 and 5
Business purpose recorded?
Yes. Clinical discussion of TAVR outcomes
Expense report ER-58213
Proposed verdict
Genuine breach
The answers above, high confidence
What the agents do
Transaction review
Answers the review checklist from the evidence and rates each flag, with its confidence.
Receipt reading
Turns a photo of a receipt into itemized lines, so alcohol and attendee counts become checkable.
Spend check
Tells a rep which rules apply to a planned meal, gift or expense before they spend.
Field mapping
Proposes how a new system's fields map onto Cortex's standard records.
Match review
Explains why two records look like the same HCP or company, citing the fields that agree.
Policy breakdown
Splits a policy into obligations that quote the clauses they come from.
Hotline intake
Opens a case from a report and links the people and records it names.
App builder
Drafts a small application from a description, for a person to review and publish.
What you control
Permissions
An agent acts as the signed-in person and takes only the actions Cortex allows.
Approval
Your administrators set how much an agent may do without asking, and each person can narrow it further.
Preview
Before a change runs, Cortex shows the records it will touch.
People-only steps
Publishing configuration, granting access and some decisions always need a person.
Activity log
Cortex logs each task an agent does, with the records it read and the changes it made.
Your model
Agents use the AI model you choose.
A workflow can include an agent as a step, and agents your team builds can connect to Cortex through the Model Context Protocol (MCP).
Build inside Cortex
Add what your program needs next. A register, a questionnaire or a red flag, on the people and payments already there.
What your team builds
Record types
A gift, a grant or a sponsorship, with its fields, choices and evidence.
Forms
Intake forms, questionnaires and review checklists, with scoring.
Rules
Red flags, limit tables, keyword lists and obligations, written in your terms.
Workflows
Triggers, assignments, approvals, notifications and agent steps.
Applications
Dashboards, record lists, reports and workflow apps, drafted by the app builder from EthicsVue's building blocks.
Reports
Metrics, KPIs and slide decks over the same records.
Workflow: Gift approval
Versions
Version 3
Approval limit for Brazil lowered to R$250
Published by A. Patel, 12-Oct-26
14 requests in progress keep the version they started on.
EthicsVue delivers each program ready to use, and your own settings sit on top of it.
Agents save what they author as drafts, and a person publishes them.
You publish an application to a group or to named people, and each person sees only the records their access allows.
Deployment
Cortex runs in your cloud. EthicsVue reaches it only when you grant access.
Your people
Your systems
Expense and travel systems, ERP and finance, CRM and events, Employee directory, Databases and file shares
Reference data
Exchange rates, NPPES, Open Payments
Your cloud
Your account, your region
Single sign-on
Entry point
Web application firewall
Web app
API
Automation
Data imports
Database
Records, graph, audit trail
File storage
Documents and evidence
Key store
Passwords and keys
EthicsVue
Access when you grant it
Sign-in
People sign in with their company account through your identity provider. Cortex keeps no passwords of its own.
Network
A web application firewall faces the internet. Databases and file stores do not.
Separation
Each record carries the organization it belongs to, and the database keeps each organization's records apart.
Audit trail
A log of each change that nobody can edit. People and the assistant make changes the same way, so both appear in it.
Encryption
Your cloud encrypts data at rest and in transit, and passwords and keys live in your own key store.
Reference data
Exchange rates, NPPES and Open Payments arrive from EthicsVue over an encrypted connection your network opens. Your transactions stay in your cloud.