COMPUTER SOFTWARE PROGRAMS PHYSICIAN

Brand Owner (click to sort) Address Description
MILLBROOK CERTIFIED PARTNER Millbrook Corporation 3330 Keller Springs Road, Suite 201 Carrollton TX 75006 computer software programs for physician practice management;
MILLBROOK PRACTICE MANAGEMENT SOLUTIONS Millbrook Corporation 3330 Keller Springs Road, Suite 201 Carrollton TX 75006 computer software programs for physician practice management;PRACTICE MANAGEMENT SOLUTIONS;
MILLBROOK PRACTICE MANAGER Millbrook Corporation 3330 Keller Springs Road, Suite 201 Carrollton TX 75006 computer software programs for physician practice management, namely, for billing, appointment scheduling, bookkeeping, and recordkeeping of patients' information;PRACTICE MANAGER;
MILLBROOK PRACTICE MANAGER 2004 Millbrook Corporation 3330 Keller Springs Road, Suite 201 Carrollton TX 75006 computer software programs for physician practice management;PRACTICE MANAGER 2004;
MILLBROOK PRACTICE MANAGER 2005 Millbrook Corporation 3330 Keller Springs Road, Suite 201 Carrollton TX 75006 computer software programs for physician practice management;PRACTICE MANAGER 2005;
PARADIGM Millbrook Corporation 3330 Keller Springs Road, Suite 201 Carrollton TX 75006 computer software programs for physician practice management;
PARADIGM PREMIER QRS, INC. Suite J 353 Marshall Avenue St. Louis MO 63119 Computer software programs for physician practice management, namely, billing management of accounts, tracking of managed care, generating reports and summaries, generating follow-up letters and invoices, transmission of claim information, productivity analysis and patient history and data archiving;
 

Where the owner name is not linked, that owner no longer owns the brand

    
Technical Examples
  1. A method and system for auditing software systems by monitoring the use and non-use of software programs in a computer. An operating system of the computer controls execution of software products through the invocation of respective load modules thereof. A monitor is periodically triggered to collect load module execution information, which is filtered by a filtering module, and a correlator correlates load module execution information with data that associates load module names with corresponding software products and develops a list of products executed in the computer over the course of a given time period.