Victoria IHI Pre-Implementation Project v1.0

Victoria IHI Pre-Implementation Project v1.0

The primary objective of the Victorian IHI Pre-Implementation project is to develop a suite of system design artefacts to support integration of the national Individual Healthcare Identifier into health services’ patient administration systems.
The project was conducted by the Department of Health, Victoria, under the HealthSMART program, and NEHTA. Subject matters experts in health information management, primarily from HealthSMART health services in Victoria, provided their expertise in the development of requirements and the functional design. They also provided valuable reviews of the project deliverables.
In keeping with the original Victorian IHI Pre-Implementation Project brief, the IHI integration design is aligned with the requirements and capabilities of HealthSMART and major Victorian public health services. The design may be scaled down as required to suit smaller health services.

Identifier: 
EP-1344:2011
Date: 
11-02-2011
Type: 
application/zip
SHA256 Checksum: 
6894e12add472587e7301b35a2005428983d3cbfef3bf2bca40466da7160dbcd
Size: 
12.24 MB

Product Components

Product component
Identifier: 
NEHTA-1346:2011

The Best Practice Guide provides guidance to all those wishing to adopt individual healthcare Identifiers (IHIs) into their systems and business processes. This document is user focused, though it should also be read by designers and architects of health IT systems.

Product component
Identifier: 
NEHTA-1352:2011

This group of use cases focuses on functions usually performed by Health Information Managers in larger health services. This includes patient merges, patient duplicate and other reporting, and a number of use cases to help them to resolve IHI related exceptions.

Product component
Identifier: 
NEHTA-1345:2011

The purpose of this document is to provide information regarding the release of deliverables from the Victorian IHI Pre-Implementation Project, jointly conducted by the Department of Health, Victoria and the Agency.

Product component
Identifier: 
NEHTA-1354:2011

These use cases focus on patient record centred use cases, such as searching for a patient record in the PAS, creating a patient record and updating a patient record.

Product component
Identifier: 
NEHTA-1347:2011

The reader should begin with this document.

Product component
Identifier: 
NEHTA-1353:2011

These use cases effectively form the intermediary layer between business processes and user initiated functions, and the HI Service. This includes the functions to search for an IHI, to check the IHI, and to perform batch processing of the IHI.

Product component
Identifier: 
NEHTA-1355:2011

This is the introduction to the functional design, and the document includes all business processes developed during the project.
Of the detailed design documents, this one should be read first.

Product component
Identifier: 
NEHTA-1350:2011

This use case grouping focuses on functions that support coordination of care for a patient, such as referrals, orders and discharge summary.

Product component
Identifier: 
NEHTA-1349:2011

This document list the exceptions raised within the Victorian IHI integration design, and the available resolutions. The exception handling is a major part of the design, with some IHI related functions only available through the IHI exception resolution process.

Product component
Identifier: 
NEHTA-1348:2011

This document provided an important input to the Vic IHI Integration Design, and much of the design exists to address the risk areas identified. It was prepared by the project team with input from health service and other staff well-versed in evaluating and mitigating clinical risks.

Product component
Identifier: 
NEHTA-1356:2011

The IHI Technical Design uses a use case approach to identifying some of the technical processes required to support the IHI Integration Functional Design. The document is more aligned with the HealthSMART architecture and services than the other documents in this release.

Product component
Identifier: 
NEHTA-1357:2011

The reader should progress to this document after having read the business requirements.

Product component
Identifier: 
NEHTA-1351:2011

This functional grouping focuses on functions available in the HI Service, with the design providing the local processing components needed to make optimum use of the HI Service.

By operation of the Public Governance, Performance and Accountability (Establishing the Australian Digital Health Agency) Rule 2016, on 1 July 2016, all the assets and liabilities of NEHTA will vest in the Australian Digital Health Agency. In this website, on and from 1 July 2016, all references to "National E-Health Transition Authority" or "NEHTA" will be deemed to be references to the Australian Digital Health Agency. PCEHR means the My Health Record, formerly the "Personally Controlled Electronic Health Record", within the meaning of the My Health Records Act 2012 (Cth), formerly called the Personally Controlled Electronic Health Records Act 2012 (Cth).

Back to Top