Step 5 -- Personally Controlled Electronic Health (eHealth) Record System

Requirement 5: Personally Controlled Electronic Health (eHealth) Record System

The practice must:

  1. Use compliant software for accessing the personally controlled electronic health (eHealth) record system, and creating and posting Shared Health Summaries and when available, Event Summaries; and
  2. Apply to participate in the eHealth record system upon obtaining a HPI-O.
  3. Your organisation has a written policy to progress the use of Personally Controlled Electronic Health Records
back

Step 4 -- Electronic Transfer of Prescriptions

Requirement 4: Electronic Transfer of Prescriptions The practice must:

  1. Use a software system that is able to send an electronic prescription to a Prescription Exchange Service (PES) operator for later retrieval by a dispenser at the time of dispensing.
  2. Your organisation has a written policy to progress the use of Electronic Transfer of Prescriptions
back banner new gps

Step 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:

  1. Apply for a NASH PKI Certificate for eHealth and Secure Messaging (not required until the practice has obtained a HPI-O)
  2. Have a standards-compliant secure messaging capability to electronically transmit and receive clinical messages to and from other healthcare providers, use it where feasible,
  3. Work with your secure messaging vendor to ensure your messaging solution is installed and configured correctly (not required until 1 August 2013), and
  4. Have a written policy to encourage its use in place.
back banner new gps

 

Step 3 -- Data Records and Clinical Coding

There are no software conformance requirements for this Requirement. This requirement is a work process change associated with whichever medical vocabulary used by the vendor (such as SNOMED-CT, DOCLE, PYEFINCH and ICPC2+).

  • Medical Director: DOCLE
  • Best Practice: PYEFINCH
  • Zedmed: ICPC2+
  • MedTech 32: ICPC2+
  • Genie: ICPC2+ (subscription fee applies)

The practice must:

  1. Ensure that where clinically relevant, they are working towards recording the majority of diagnoses for active patients electronically using a medical vocabulary that will eventually be mapped against a nationally recognised disease classification or terminology system.
  2. Provide a written policy to this effect to all GPs within the practice.
back banner new gps

 

Step 1 -- Integrating Healthcare Identifiers

The intent of this Requirement is to make Healthcare Identifiers available for Secure Message Delivery and for use in the personally controlled electronic health (eHealth) record. The practice must:

1) Apply for a Healthcare Provider Identifier-Organisation (HPI-O) for the practice, and store the HPI-O in your compliant clinical software system.

HPI-O: A 16 digit number allocated to an organisation, it identifies where the health service was provided. To obtain a HPI-O, apply to Department of Human Services (DHS).

2) Ensure that each general practitioner within the practice has a Healthcare Provider Identifier-Individual (HPI-I), stored in a compliant clinical software system; and

HPI-I: A number allocated to all healthcare providers, it identifies who provided the health service. All healthcare professionals registered with the Australian Health Professional Regulation Agency (AHPRA) have already been given an HPI-I. Log in to AHPRA or call Medicare Australia to obtain your HPI-I number. Note: This number is different from the national registration number issued by AHPRA in July 2010.

3) Use a compliant clinical software system to access, retrieve and store verified Individual Healthcare Identifiers (IHI) for presenting patients.

IHI: A number that Medicare has allocated to all consumers, it identifies who received a health service.

 

back banner new gps