CARELOGIX · ASSISTANT
For everyone who runs field operations, in the portal and in your enterprise AI assistant. It answers from your own data and checks every figure before anyone sees it.
Live questions answer in seconds. Questions about any period come back from DataLogiX, the EVAS analytics engine, as verified reports.
1 · TOOLS COMPUTE FACTS
f7 · 3,380 m · road routef8 · 361 s · drive timef9 · 11:30 · schedules3 · staff2 · THE MODEL WRITES, WITH BINDINGS
{{e:s3}} is closest: {{v:f7}}, about {{v:f8}} by road, free until {{v:f9}}.
claims: closest(s3, L-17) · busy_until(s3, f9)3 · THE VERIFIER CHECKS
4 · YOU SEE
R. Okafor, RN is closest: 2.1 mi, about 6 min by road, free until 11:30 AM.
FOUR RULES
Enforced in code, not asked of the model.
RULE 1
Code computes, the model talks
Every distance, drive time, count, cost, date and time comes from CareLogiX’s own code. Common report questions need no model at all.
RULE 2
Nothing unchecked reaches you
The model cites facts; a verifier fills each value, re-checks every claim and reconciles totals. If a check fails, you see the data.
RULE 3
The model gets the least data possible
Patients become location tokens and visits become jobs. No patient ID, address, coordinate or care word is sent.
RULE 4
A person confirms every change
The assistant proposes. The server checks again and acts only when a person confirms, under their name.
WHO IT SERVES
Each role gets its own scope, saved questions and rights.
Dispatcher
LIVEWho is where, who can take a job now, the late-risk list, a morning brief and proposals to dispatch or reassign.
“Nearest RN to Patient ID ••••18 who is free now?”
Dispatcher, planning
LIVESpread a sick call’s day, order a day’s visits, plan multi-stop runs.
“Spread today’s visits for the RN who called in sick.”
Division manager
REPORTWeekly reviews, coverage gaps and caseload balance.
“Weekly review for Hospice, against last week.”
HR and payroll
REPORTMileage files per pay period, field time against shifts, overtime risk, phones of leavers still reporting.
“Mileage for pay period Oct 12 to 25, as a CSV.”
Executive
REPORTKPIs by division and month and what moved them, as a page or deck.
“October against September, all divisions, as a deck.”
Fleet
LIVE + REPORTLocation and driver, utilization, fuel, faults and service due.
“Which vans have a fault code or service due this week?”
Compliance and QA
REPORTVisits with no measured stay or a silent phone, location access, data quality.
“Confirmed visits last week with no measured stay.”
IT and support
LIVEOld builds, missing permissions, flat batteries, silent trackers, late feeds.
“Which phones need the latest app update?”
Out of scope by design: anything clinical, any change without a person’s confirmation, and any change to settings.
CHECKED NUMBERS
It binds to facts code registered for this answer, and a verifier refuses any answer it can’t trace. DataLogiX uses the same rules for its reports.
Every value traces to a fact
A binding with no fact computed in this answer fails.
No number typed by the model
No digits outside a binding, and no number words in any spelling or script.
Strong words need evidence
“Closest”, “only”, “late” and “on time” need a recomputed claim; “trend” needs a statistical signal.
Totals add up
A total equals its rows, to the cent, the minute and the tenth of a mile.
One source per comparison
A tracker’s odometer and a phone’s GPS miles are never compared silently.
Fresh live facts
Positions older than five minutes and drive times older than ten are fetched again.
Only what you may see
A fact from outside your divisions or role fails the answer.
Arithmetic and time are tools
Sums, business days and “Friday 2 PM” are computed in your division’s time zone.
When a check fails
The model gets one retry. If that fails too, you see the facts as a table.
Questions with no model at all
Common questions such as “miles by staff last week” are answered from the metric catalog directly.
Hover any value
Each value shows where it came from and when.
WHAT A MODEL SEES
All geometry runs on our side, so a model never needs a position. A guard checks every request before it leaves, and fails closed.
Send Rosa Okafor, RN to Patient ID 4471-0018 at 1204 Bayshore Ave: 2.1 mi by road, free until 11:30 AM. The visit is a hospice nursing visit.
Names, IDs and addresses are shown only in the portal, after you sign in.
Send s3 to L-17: {{v:f7}} by road, free until {{v:f9}}. The job is J-204, scheduled.
The model gets tokens and the facts code computed. Tokens map back on the server and expire within a day.
| DATA | SENT AS | RULE |
|---|---|---|
| Patient | A location token such as L-17 | Mapped back on the server, gone within a day |
| Visit | A job such as J-204: window, duration, status | Never “visit”, “patient” or “care”; no diagnosis |
| Staff | Name, role, discipline, load, phone status | A division can mask names |
| Vehicle | Its name, type and operating facts | Its driver follows the staff rules |
| A place | “0.4 mi from L-17”, “at the office”, “driving” | Never a coordinate |
| Address, patient ID, record numbers | Not sent | Shown in the portal after sign-in |
| Notes and free text | Not sent | Mapped into codes where needed |
| Your typed question | Scrubbed first | Names, IDs and addresses in it become tokens |
The same guard runs on replies to outside assistants. Instructions inside record text are treated as data, never followed.
ANY MODEL, ONE POLICY
The tools, the verifier and the privacy guard are the same whichever model you use.
Any model, by alias
Code names a role, never a model. Each division maps roles to the providers you approve, including a model you host.
Health data stays with eligible endpoints
Health data goes only to endpoints approved for it. Unknown means no.
Budgets and an emergency stop
A daily budget per division, caps on each answer, and one Pause that stops every model.
Fallback without surprises
If a provider is down, the next one that meets policy takes over. Live views work with no model.
ACTING SAFELY
It never changes a record on its own. You control it with a pause, per-division capabilities and access by role.
STEP 1
Proposed
With its exact parameters, facts and warnings. It expires in 15 minutes.
STEP 2
Shown
One card per change, with Confirm, Edit and Dismiss.
STEP 3
Checked again
Drive time and conflicts are re-checked. If either moved, you see it first.
STEP 4
Done as you
Made through the same endpoint you would use, under your name.
Every turn is audited. The board, the ranking and reports keep working when the assistant is off.
ENTERPRISE AI ASSISTANTS
One connector, served by DataLogiX’s MCP server with a CareLogiX tool pack. People reach reports and live operations from the assistant they already use, with their portal rights.
Sign in as yourself
Each person connects with their own account. A shared key gets nothing.
Your division, your rights
Each call gets a short-lived token for one division, so CareLogiX’s rights checks apply.
Location tokens only
No patient IDs, addresses or care words. Figures from health data are read in the portal.
Audited on both sides
Both CareLogiX and DataLogiX record each call.
CARELOGIX TOOL PACK
carelogix_askThe full live pipeline: the checked answer, its table and a portal linkcarelogix_statusA person’s or phone’s current state, with its source and timecarelogix_nearestThe nearest staff for a location token, by roadcarelogix_jobsToday’s jobs, as codescarelogix_itemsNeeds action items, with their agecarelogix_vehicleA vehicle’s state, driver, fuel and faultscarelogix_check_claimsChecks text the assistant wrote against the facts it citesAlongside DataLogiX’s own report tools. Every reply carries its verified sentence, sources and a portal link. A missing division or time comes back as a question.
CARELOGIX AND DATALOGIX
CareLogiX dispatches in seconds; DataLogiX reports on any period, verified and signed. They connect through DataLogiX’s standard sources, packs, API and webhooks.
Live dispatch never calls DataLogiX
Positions, drive times and proposals run only in CareLogiX. With DataLogiX down, only reports pause.
DataLogiX never writes CareLogiX records
Visits from a new record system reach CareLogiX through its own import.
Standard surfaces only
To DataLogiX, CareLogiX is one more source and a set of packs. Each product runs and is sold on its own.
ELEVEN CONNECTIONS
Agency-wide figures are only for people with agency-wide rights.
WHAT IT READS
Any record system
One source-neutral model, the one DataLogiX uses. A new system is a new adapter.
Vehicle trackers
A profile per vehicle for its tracker, tank and service intervals.
Two years of history
Longer periods, and the system as it was at a past moment.
A company car is not paid as mileage. A phone trip matching a company-vehicle trip bills zero miles, with the vehicle named.
TESTED LIKE THE REST OF EVAS
A set of golden questions
Across the seven audiences, run for every model and prompt version.
A change ships only if it holds up
Fact correctness must not drop, and answers must pass the verifier.
An adversarial set
Attempts at an address, planted instructions, another division’s data or an unconfirmed action must end in a refusal, a token or a proposal.
Leak tests on every reply
Every tool result and connector reply is searched for coordinates, addresses, names, record IDs and care words.
BEYOND HEALTHCARE
The assistant speaks in jobs, places, staff and vehicles, so it fits field service, home services, deliveries, security patrols or utilities unchanged.
Each division has its own vocabulary, so a patient can be a client, a site or a unit and a visit a job or a stop. The operations metrics carry no healthcare term; a healthcare overlay adds visit reconciliation for agencies that need it.