Administration
Set up Clinical, manage configuration, user records, updates, back ups and other maintenance.
- MedicalDirector Automatic Updates
- System Configurations
  Manage database configurations.
- Managing Practitioner and User Records
- Merge Clinical Lists
- 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
  - ePrescribing and eRx Script Exchange
  - My Health Record Audit and Medications
  - My Health Record Assisted Registration for Child Patients
  - Practice Incentives Program (PIP) eHealth Incentive
  - eHealth Troubleshooting Guide
  - Creating CDA e-Health Documents
    CDA documents can be shared between registered practitioners via systems such as MDExchange and My Health Record.
- Managing Communications
  Use the Manage Communications utility to configure how Investigation Results are imported to Clinical.
- Medicare Healthcare Identifiers Service
- Medicare's Health Identifier Service and Clinical
- HESA PKI Certificates
- Backup and Restore
  The MedicalDirector Backup and Restore utilities backup and restore Clinical and Pracsoft.
- MedicalDirector Mobility
  MedicalDirector Mobility is a utility for downloading patient records to a mobile computer, allowing you to work with them off-site.
- Technical Reference
- Language Codes Reference
  Instances of 'nec' found following refer to "Not Elsewhere Classified".
- Clinical System Requirements
  This information applies to MedicalDirector Clinical 4.3.

Checklist for Requirement 2

To ensure that your practice complies with Requirement 2 the following information must be ticked:


	Practice must complete Requirement 1 - Integrating Healthcare Identifiers into Electronic Practice Records.
	Practice has applied for the National Authentication Service for Health (NASH) PKI certificate for eHealth and secure messaging within two weeks of receiving its HPI-O (Requirement 1) or by 1 February 2013, whichever is later.
	Practice has imported the NASH PKI Certificate.
	By 1 February 2013, or within four weeks of having received your NASH PKI certificate, whichever is later: Practices must have a standards-compliant product with secure messaging capability that is listed on the PIP eHealth Product Register for Secure Messaging (https://epipregister.NEHTA.gov.au/registers/ securemessage delivery), or Have written advice from a vendor listed on the PIP eHealth Product Register for Secure Messaging that their listed product will be available to the practice in order to meet the time frame outlined in the last check box below.
	A written policy must be in place to encourage the use of standards-compliant secure messaging.
	Practice can provide verification that the compliant product has been installed (e.g. HealthLink) and configured or has written advice that their product will be compliant within the time line for Secure Messaging Delivery (SMD) compliance. This step must be completed by 1st August 2013.