Home
Administration
Set up Clinical, manage configuration, user records, updates, back ups and other maintenance.
Upgrading SQL Server
Both Clinical and Pracsoft use Microsoft SQL databases. Clinical and Pracsoft require two SQL Server instances.

Administration
Set up Clinical, manage configuration, user records, updates, back ups and other maintenance.
- Installing, Modifying, or Uninstalling Clinical/
  Install Clinical/ and its related components with the Installation Wizard.
- Installing Clinical, Pracsoft, and MDref Updates Automatically
  Update Clinical, Pracsoft, or MDref without monitoring the Installation Wizard or intervening directly.
- Upgrading Clinical
  Upgrade the server and workstations that run Clinical.
- Installing or Upgrading SQL Server
  Install SQL Server or upgrade your existing SQL Server installation.
- Adding your Licence Details
  After installing Clinical, or if you renew your Service-Level Agreement (SLA) with MedicalDirector, enter your licence details.
- Maintenance
  Use update, backup and restore and other maintenance utilities to manage MedicalDirector Clinical .
- Managing Practitioner and User Records
  Each user must be defined in MedicalDirector Clinical's user database.
- Custom Options
  Clinical provides numerous user-definable options for tailoring the program to your requirements.
- MyMedicare Import Wizard
  Update the MyMedicare status of your Clinical and Pracsoft patients.
- Telehealth Widget
  Use the Telehealth widget for Telehealth consults with patients.
- Adding New Widgets
  Add new widgets from the widget store.
- eHealth
  Summarises Clinical's support for eHealth.
- Healthcare Identifier Service
  The Healthcare Identifier Service (HI Service) issues unique IDs to healthcare providers and individuals who seek healthcare.
- Technical Reference
  Technical reference information for Clinical.
- Clinical System Requirements
  Minimum requirements for computers on which Clinical is installed.
- Moving Data to a New Server
  Move your MedicalDirector Clinical data to a new server and configure the workstations.
- Auditing User Access with MDTrace Log
  Log information about the way people at your practice use Clinical.
- Patient Database Clean-up Tips
  If your practice has just migrated to MedicalDirector Clinical or you have merged patient databases you should clean up your patient database.
- Upgrading SQL Server
  Both Clinical and Pracsoft use Microsoft SQL databases. Clinical and Pracsoft require two SQL Server instances.
- Business Transition Guide
  Relocating your Practice or making significant changes to your Business practices can be challenging enough without adding complications from the software your business uses.
- FTP and MedicalDirector
  Set up an FTP client application for downloading data.
- IP and Host Name Resolution Requirements for MedicalDirector Communication Services
  Set up MedicalDirector Communication Services so multiple users can record progress notes simultaneously.
- Setting Folder Permissions

Upgrading SQL Server

Both Clinical and Pracsoft use Microsoft SQL databases. Clinical and Pracsoft require two SQL Server instances.

Upgrade the server first, then upgrade the workstations.

HCNSQL07 - Required. Hosts the clinical and financial data.
ESP - Required. Used by functionality such as Insights, and if your practice uses a Tyro device.

The MedicalDirector ISO includes Microsoft SQL 2019 Express Edition. A new server role installation will create the SQL Server instances for you automatically but will not upgrade existing installations.

If you have a full SQL Server licence and are currently running Clinical and/or Pracsoft within SQL Express, you can upgrade to full SQL Server either before or after upgrading to Clinical / Pracsoft. In either case:

Perform a Backup with the Backup Utilities.
Follow the instructions supplied by Microsoft to upgrade both SQL Express Instances HCNSQL07 and ESP to your version of full SQL Server. This requires running the SQL installer twice.

17 August 2026