Scheduling changes are automatically sent to all other scheduling screens--without
polling or manual refresh.

We centrally scrub—and enable users to scrub—claims using custom and standard criteria.

Fifteen settings control statement-generation behavior; statements reveal all insurance
and adjustmet activity with a clarity that curtails phone calls from patients.

Encounter forms are user-configurable. You can have a whole library of encounter
form types for different uses.

Seventeen active to-do lists itemize such things as denied claims, claims that failed
our own scrub, and all other details that must be dealt with to maintain cash flow.
List items items contain data links.

You can track managed care contract fees and reimbursement compliance.

You can track production by any combination of practice, provider, procedure code,
and accounting period.

All entities, such as patients, providers,
service lines and payments, display as nodes on a tree control on your main application
window, the best way visually to map and represent your data.

A single search screen gets you directly
to any entity type, even with nested criteria logic, and without having first to
drill (and later back out) through layers of conventional windows and grids.

Navigation from one entity to neighboring
entities is standardized, simple and consistent across all entity types and perfectly
depicted by the tree.

The creation, display, and updating of
entities is done with a single standardized window, regardless of entity type.

Ad hoc and programmatic queries are configured,
not written, simply by clicking on metadata grids along the path of the query. The
actual run-time SQL is generated automatically.

To summarize,
the Veriquant Framework standardizes and simplifies
how you retrieve, view, modify, and secure all entities—and standardizes and simplifies
how we as programmers enable you to do so. The need for numerous specialized screens
and the knowledge required to use them is sharply reduced.
When all entity types, however diverse, are abstracted to a common structure, the
node, only one tool is required to perform a given action across all of them. This
is as true under the hood as it is with the user interface itself. No other practice
management system known to us has this capability.