BATech View is OCR for sensitive data, designed as a platform for pharma copay and patient-support programs. Each faxed benefits page is looked at before it is read, goes to the readers built for it, and is checked by rules that can only flag.
Available for pilots. View runs today as a local build on synthetic data.
Each fax is encrypted under its own key on arrival, before it is read. By default, every reader runs where View runs: no page is sent out to be read.
Each value arrives with its page and the words it was read from, boxed where it can be placed. A doubtful value carries a warning in plain words.
Today a named reviewer files every value, with the page beside it. View is designed so that, once measured, what passes every check files itself, and exceptions go to a person.
Filed values join the patient's record. A new value supersedes the old, the old is kept with its page, and an older document never silently replaces a newer one.
Your system reads each record over an API: every value with its source and who filed it, checked against View's versioned schema before it leaves. Every read is logged.
Your claim gates screen the claim. View checks the paper. It reads the benefits documents your program already holds and shows the page behind every value and every flag. We do not publish a time saving or a catch rate we have not measured. A pilot measures these four on your own faxes.
Checking View's proposed values against the page, timed against typing the same faxes in by hand.
Measured in the pilotThe share of each fax's values a reviewer confirms or corrects instead of keying from scratch.
Measured in the pilotEvery misread a reviewer corrected, counted against answers checked by hand. Accumulator and maximizer programs are read like any other value.
Measured in the pilotThe faxes where View found signs of government coverage on the page, counted against what your own records showed for the same patients.
Measured in the pilotRouted reading. Every page is looked at before it is read. View is designed so that each part then goes to the reader built for it, and so that no route can skip the checks, which can only flag.
Each original fax is encrypted under its own key on arrival, before it is read. Each client sets its own lines, allowed senders and quarantine.
Before a page is read, View checks whether it carries real digital text, and cleans up a faxed page. A page that arrived sideways or upside down is turned and read again.
Each page's document type is then recognised, and the page goes to the readers built for that type. Each part of a page is designed to reach its own reader; today digital text, fax pages and tick boxes each have one.
What the readers read becomes values in one versioned vocabulary, each with its page. One extractor per document type is on the roadmap.
A check can send a value to a person. It never changes a value and never lets one file.
Today a named person files every value, traced to its page. View is designed so that, once measured, what passes every check files itself, and exceptions go to a person.
One record per patient, never overwritten, read by your systems by token.
Designed to run analysis modules over filed records, never changing them.
Under every route
A reader can be wrong without knowing it. So View is designed so that no route or module can loosen these rules. Each says what holds today and what the design adds.
No figure read by OCR files by itself on one reading, and View never matches a fax to a patient on a near match.
A check can send a value to a person. It never changes a value and never lets one file, so adding a check can send more to a person, never less.
View looks for signs of government coverage on every page about the patient, and sends any fax where it finds one to a person. So does a fax whose patient is uncertain, in conflict or ambiguous.
View cannot decide eligibility by itself: the database refuses it.
That rule is enforced in the code and tested, and View has never trained a model on patient data.
Each patient's record gives every value with its source page, the words it was read from, and who filed it and when.
is designed to grow by adding modules.One platform, many parts. Some of View's reading steps are already built as plug-in modules. Each kind shows what is available now and what is on the roadmap.
Documents arrive from the fax lines a program already runs. Each client sets its own lines, allowed senders and quarantine.
5 available now1 on the roadmap
5 available now1 on the roadmap
Documents arrive from the fax lines a program already runs. Each client sets its own lines, allowed senders and quarantine.
Faxes arrive from a webhook your online fax service posts to, a folder your fax server writes to, or a portal upload.
Available nowEach client sets up its own fax and eFax lines, each as an ingestion module with its own settings.
Each line keeps its own list of allowed sending numbers, chosen by the client.
Available nowA fax from a number a line does not allow is held in quarantine, sealed and unread, until an administrator lets it in or turns it away.
Each file is typed from its contents, never its name. A file sent twice is kept once, and one that cannot be opened is refused before anything is stored.
Available nowThe platform is designed to take documents in from more places, each as an ingestion module.
On the roadmapEvery page is looked at before it is read.
4 available now1 on the roadmap
4 available now1 on the roadmap
Every page is looked at before it is read.
Every page is looked at before it is read. Real digital text is read exactly; a picture of a page goes to OCR prepared for fax.
Available nowText that another OCR added to a PDF is treated as a reading to check, not as the document's own words.
Available nowFax artefacts are handled before a page is read. A page that arrived sideways or upside down is turned and read again.
Available nowEach page's document type is recognised, and the document goes to the readers built for that type.
Available nowThe pre-screen is designed to grow with the platform. Routing is designed to be measured and versioned, so every route can be audited.
On the roadmapEach part of a page is designed to reach its own reader.
3 available now4 on the roadmap
3 available now4 on the roadmap
Each part of a page is designed to reach its own reader.
A born-digital PDF is read from its own text, with no OCR.
Available nowOCR prepared for fax, running where View runs.
Available nowTick boxes have a reader of their own, and a mark it cannot call is never taken as an answer.
Available nowA second, independent reader is built and being measured before it becomes the default.
On the roadmapShort exact fields such as IDs and dates are designed to get a reader of their own. Coming: a reader for tables.
On the roadmapHandwriting is not read yet: a person types what the reader missed.
On the roadmapDesigned as a route a client can choose per document type, running in its own cloud. An AI reading is designed never to file on its own.
On the roadmapWhat the readers read becomes values in one versioned vocabulary, each with its page.
4 available now1 on the roadmap
4 available now1 on the roadmap
What the readers read becomes values in one versioned vocabulary, each with its page.
Plan summaries and federal employee plan brochures are read by readers built for them, and a brochure's plan options are kept apart.
Available nowView reads insurance cards, benefits-verification and enrollment forms, test-claim and eligibility printouts, prior authorisation letters and cover sheets.
Available nowCoverage type, relationship, authorisation status and claim result are read from the boxes. Two marks where one answer is allowed are flagged, never picked.
Available nowEvery value lands in one fixed, versioned vocabulary: 114 fields in 11 groups, including the patient's identity, as of 9 Oct 2026.
Available nowEach document type is designed to get its own extractor module, so a new type can join without changing the others.
On the roadmapA check can send a value to a person. It never changes one.
7 available now1 on the roadmap
7 available now1 on the roadmap
A check can send a value to a person. It never changes one.
A doubtful reading carries a warning under the value it belongs to, saying what to check.
Available nowIdentifiers are checked against their expected shape, and an NPI against its check digit.
Available nowValues on the same fax are checked against each other.
Available nowView looks for signs of government coverage on every page about the patient, and sends any fax where it finds one to a person. It never reads silence as "no government coverage".
Available nowIf the identity printed on a fax does not match the chosen patient, View says so before anything is filed.
Available nowAn older document never silently replaces a newer value.
Available nowA check can send a value to a person. It never changes a value and never lets one file.
Available nowThe platform is designed to grow by adding checks, including flag rules a client writes itself. Because checks never fix, adding one can send more to a person, never less.
On the roadmapNo figure read by OCR files by itself on one reading. Today a named person files every value.
6 available now2 on the roadmap
6 available now2 on the roadmap
No figure read by OCR files by itself on one reading. Today a named person files every value.
Today a named reviewer files every value, with the page beside it. Nothing that needs a person starts ticked.
Available nowEvery fax that needs a person says why, in one plain sentence.
Available nowNo figure read by OCR files by itself on one reading, and View never matches a fax to a patient on a near match.
Available nowA fax where View finds signs of government coverage, or whose patient is uncertain, in conflict or ambiguous, always goes to a person. By default, so does a fax for a patient not yet on file. Eligibility is always a person's decision.
Available nowView cannot decide eligibility by itself: the database refuses it. By default, an eligible decision must cite the page that answers the government-coverage question. A program's administrator can choose to allow one without it.
Available nowWith the default reader, an ID number or code read by OCR must be partly retyped by a person before it files, not just ticked.
Available nowDesigned so that independent readers must agree on every figure before anything files by itself.
On the roadmapDesigned to file what passes every check by itself, with daily spot checks, an automatic pause and undo. It is designed to switch on after a measurement on documents it was never tuned on; today every fax goes to a person.
On the roadmapOne record per patient, never overwritten.
4 available now
4 available now
One record per patient, never overwritten.
One record per patient, never overwritten. See what was on file on any date, which page it came from and who filed it.
Available nowA work list of the faxes that need a person, which today is every fax. It has holds, follow-ups and reminders before a plan year restarts or an authorisation or coverage ends. Once automatic filing files, the list is designed to hold exceptions and spot checks, not every fax.
Available nowSearch the text of every fax. The log records that a search happened, never what was searched.
Available nowRole-based access for intake, supervisors, program managers and auditors.
Available nowAnalysis is designed to read filed records, never to change them.
2 on the roadmap
2 on the roadmap
Analysis is designed to read filed records, never to change them.
Coming: analytics and a program report. Shareable views are designed to withhold small groups.
On the roadmapThe platform is designed to add analysis as modules a client can turn on, each reading filed records and never changing a value.
On the roadmapYour systems read each record, with its source, by token.
4 available now1 on the roadmap
4 available now1 on the roadmap
Your systems read each record, with its source, by token.
Each patient's record gives every value with its typed form, source page, the words it was read from, and who filed it and when.
Available nowEvery record is checked against View's versioned schema before it leaves. A record that fails is not sent.
Available nowThe CSV is sent whole or not at all, with spreadsheet formulas neutralised.
Available nowYour systems read records by token. A portal session alone cannot download a record or the CSV.
Available nowComing: endpoints for a record's status and its changes. The platform is designed to deliver results through output modules.
On the roadmapSealed on arrival. By default, no page is sent anywhere to be read.
8 available now1 on the roadmap
8 available now1 on the roadmap
Sealed on arrival. By default, no page is sent anywhere to be read.
Each original fax is encrypted under its own key on arrival, before it is read. Read text and filed values are kept in View's database, not sealed per document.
Available nowPage images are drawn in memory and never written to disk.
Available nowBy default, no page is sent anywhere to be read.
Available nowBy default, no AI model reads a patient document. That rule is enforced in the code and tested, and View has never trained a model on patient data.
Available nowThe database itself keeps the audit log from being edited or deleted. It records ids, never patient names or values.
Available nowEach client's records are kept apart by the database itself, as well as by the application.
Available nowPages and records reach the browser through short-lived tokens, and sessions lock when idle.
Available nowNo real patient data has been used to build or test View.
Available nowDesigned to run in your own cloud account, with sign-in from your single sign-on with MFA.
On the roadmapEach client has its own settings, and the platform is designed to grow by adding modules.
2 available now1 on the roadmap
2 available now1 on the roadmap
Each client has its own settings, and the platform is designed to grow by adding modules.
Each client has its own review targets, reminder windows and idle lock, set when its account is configured. Its settings can make the government-coverage rule for automatic filing stricter, never looser.
Available nowSome of View's reading steps, such as tick-box answers and the government-coverage check, are already built as plug-in modules.
Available nowEach module is designed to declare what it may touch (patient data, the network, AI), and the platform enforces it.
On the roadmapEach client arranges its own flow on a board, around safety steps that stay locked.
5 available now1 on the roadmap
5 available now1 on the roadmap
See the flow builderEach client arranges its own flow on a board, around safety steps that stay locked.
A client's administrator proposes changes to its flow on a board, dragging modules into place around safety steps no flow can remove. For now, changes to readers and checks run in the sandbox and cannot go live.
Available nowA proposed change runs on practice faxes in a sandbox, and its results show next to the current flow, step by step, before the change can go live.
Available nowEach change to a flow is versioned with who made it and when. A second administrator approves it before it goes live, and any version can be put back in one step.
Available nowSafety steps are locked into every flow. No flow can remove them, switch them off or route around them.
Available nowA change that could let more file by itself is designed to be measured again on practice faxes before it goes live.
On the roadmapA flow view shows how a client's documents move through View's steps, from the fax line they arrive on.
Available now12kinds
68capabilities
52available now
16on the roadmap
Statuses checked against the code on 10 Oct 2026. View runs today as a local build on synthetic data.
Arranged by you, around locked steps. A client's administrator proposes changes to its flow on a board and can try each one on practice faxes in a sandbox, with the results next to the current flow. A change goes live when a second administrator approves it. For now, a live change sets which fax lines a flow takes; changes to readers and checks run in the sandbox and cannot go live yet.
Flow builder5 available now1 on the roadmap
View's own screens, redrawn here around one synthetic fax and View's own reading of it: every value read from that fax is what the reader proposed, copied exactly, and its warnings are shown in plain words with reading scores left out. The reviewer's one correction and the earlier history are scripted, and every person, plan and number is invented.
The fax as it arrived, and beside it all 21 values the reader proposed, nothing ticked, from the member ID to the copay accumulator program. Point at a value and its box lights up on the page; warnings sit under the value they belong to.
Synthetic data: invented people, plans and numbers.
Benefits documents often arrive by fax. Until someone reads the page, nothing on it can be searched, checked or filed. And a figure typed in by hand does not point back to where it was printed.
Readers propose. Checks flag. People decide.
We ran two public Summaries of Benefits and Coverage through a fax simulator, 28 runs at two fax resolutions, and checked 392 benefit values against answers checked by hand.
| Input | Correct | Missing, typed in by the reviewer | Wrong, with a warning | Wrong, with no warning |
|---|---|---|---|---|
| Digital PDFthe plan's own file, not a faxed PDF · 28 values | 100% | 0% | 0% | 0% |
| Fine fax204 × 196 · 196 values | 48.5% | 33.2% | 17.9% | 0.5%1 of 196 |
| Standard fax204 × 98 · 196 values | 56.1% | 27.0% | 16.8% | 0.0% |
A plan's own digital PDF is read from its text layer, with no OCR. On the two plan documents we tested, every value was right. A fax, even one delivered as a PDF, is read by OCR: about half the values came out right, nearly a third had to be typed in, and nearly all the rest were proposed with a warning.
1 value in 392 was wrong with no warning. That is why no value files on one reader's word: today a named reviewer files every value, with the page beside it.
Warnings lean toward caution. About 60% of the correct fax readings also carried a warning or note. They stay, because a missed warning costs more than a second look.
On faxes held out from tuning. On 40 synthetic benefits faxes kept out of tuning, 12 of 2,242 checked values (0.5%) were wrong with no warning, and 7 values were proposed where the document stated nothing. They share their layouts with the faxes View was tuned on, and the set was scored more than once during development. Measured on 9 Oct 2026 with View's default reader. View's reading code has changed since, so this figure is also due to be measured again.
Simulated faxes of two documents from one carrier, each run seven times at each of two fax resolutions. Both were also used to develop View's plan-summary reading, so this is not a held-out result. Measured on 8 Oct 2026 and reproduced on 9 Oct 2026, with View's default reader on those dates. View's reading code has changed since, so these figures are due to be measured again. Real faxes will differ, so a pilot starts by measuring View the same way on your de-identified sample faxes, against answers checked by hand.
See it read. Each value comes with the words it was read from and its box on the page, wherever View can place it. On a fax it also says, in plain words, what to check.
Intake teams read the faxes. Compliance answers for them. IT runs the system. Other systems need the result.
The page and the proposed values side by side. Confirm, correct, or add what the reader missed.
Intake and benefits teamsEvery filed value records its source document, its reviewer and the time. The audit log keeps ids and reviewer names, never patient names or benefit values. In the local build the reviewer types their name; in the production design it comes from your single sign-on with MFA, so every filing is tied to a signed-in person.
Compliance and privacyBy default, every reader runs where View runs, with no outside calls. A service-by-service plan for AWS, with the agreements and eligible services a deployment needs.
IT and securityEach patient's current benefits as JSON, or every patient as CSV, behind a token. Every read is written to the audit log.
Your systemsMedicare or Medicaid coverage usually decides whether a patient can use a manufacturer's copay program. View looks for signs of government coverage on every page about the patient, and sends any fax where it finds one to a person. It never reads silence as “no government coverage”, and it never decides eligibility: a person does. The record keeps a place for it: government or state-funded coverage, a Medicare ID (MBI), a Medicaid ID and a pending Medicaid application.
OCR for sensitive data. Every reading, back to the page it came from.
Built to run inside your HIPAA program. Each fax is encrypted on arrival, every filed value carries the name of the person who filed it, and every fax opened, value filed and record exported is written to an append-only audit log.
Before any real patient data touches it, a production deployment needs a signed AWS Business Associate Agreement, HIPAA-eligible services only, a BAA with your fax service, single sign-on with MFA, and your own HIPAA program: risk analysis, access reviews, retention and incident response.
Today View runs as a local build on synthetic data, with a service-by-service plan for running it in your own AWS account. That is what a pilot starts from.
Every screen on this page uses synthetic data: every person, plan and number on them is invented. The accuracy figures are real measurements, made on two public plan documents run through a fax simulator.
for yourself.Walk through it with us on synthetic faxes, or talk to us about your own documents.
Demos, pilots and deployments of View.
View is a BATech product. BATech also designs and builds systems like it for other companies. See what BATech builds
Benefits intake
