Home
Administration
Set up Clinical, manage configuration, user records, updates, back ups and other maintenance.
eHealth
Practice Incentives Program (PIP) eHealth Incentive
Requirement 2 - Secure Messaging Capability

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.

Requirement 2 - Secure Messaging Capability

The intent of this requirement is to begin the process that will drive towards achieving a standards based and interoperable secure messaging environment within the health sector.

The practice must have a standards-compliant secure messaging capability to electronically transmit and receive clinical messages to and from other healthcare providers, use it where feasible, and have a written policy to encourage its use in place.

Source: http://www.medicareaustralia.gov.au/provider/incentives/pip/files/9977.pdf

The Secure Message Delivery (SMD) Australian Technical Specification published by Standards Australia defines a set of interfaces and associated applications ensuring that health information exchanged by healthcare providers is protected against malicious interference. Source: NEHTA website