Administration
Set up Clinical, manage configuration, user records, updates, back ups and other maintenance.
- Installing MedicalDirector Clinical/Pracsoft for the First Time
- Adding your Licence Details
  After installing Clinical, or if you renew your Service-Level Agreement (SLA) with MedicalDirector, you will be required to 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
  Use the MyMedicare Import Wizard to update the MyMedicare status of all your Clinical and Pracsoft patients simultaneously.
- Telehealth Widget
- Adding New Widgets
  Add new widgets from the widget store.
- eHealth
- Medicare Healthcare Identifier Service
  The Healthcare Identifier Service (HI Service) uniquely identifies healthcare providers and individuals who seek healthcare.
- HESA PKI Certificates
- Technical Reference
- Clinical System Requirements
  This information applies to MedicalDirector Clinical 4.3.
- 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
- Modifying Current Installations
- Merge Duplicate Doctor Records
- 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 MedicalDirector Clinical
- 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
- IP and Host Name Resolution Requirements for MedicalDirector Communication Services
- Setting Folder Permissions

Process for Removing a Mobility Instance

Before you begin

Procedure

Uninstall the existing SQL Instance, from within windows select Start > Control Panel > Programs & Features (or Add/Remove Programs).
- Highlight Microsoft SQL 2005, 2008 or 2012(3.15+) click Remove or Uninstall.
- Select Instance HCNMOB07, click Next.
- Click the Finish button when presented with the completion window.
Rename the following folders, by adding a suffix consisting of the current date. For example, the 'Health Communication Network' folder becomes 'Health Communication Network 25-03-11'.
For 32-bit Operating Systems
- SQL 2005: C:\Program Files\Microsoft SQL Server\MSSQL.*
- SQL 2008: C:\Program Files\Microsoft SQL Server\MSSQL10.HCNSQL07
- SQL 2008r2: C:\Program Files\Microsoft SQL Server\MSSQL10_50.HCNMOB07
- SQL 2012: C:\Program Files\Microsoft SQL Server\MSSQL11.HCNMOB07
  For 32-bit Operating Systems
- SQL 2005: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.*
- SQL 2008: C:\Program Files (x86)\Microsoft SQL Server\MSSQL10.HCNSQL07
- SQL 2008r2: C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.HCNMOB07
- SQL 2012: C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.HCNMOB07
  For 64-bit Operating Systems with 64-bit SQL (3.12+)
- SQL 2008: C:\Program Files\Microsoft SQL Server\MSSQL10.HCNSQL07
- SQL 2008 R2: C:\Program Files\Microsoft SQL Server\MSSQL10_50.HCNSQL07
- SQL 2012: C:\Program Files\Microsoft SQL Server\MSSQL11.HCNSQL07
Return to Full 'Cleanout' Process for Mobility step 5.

Results