Archived

This document lists the specific conformance requirements for Medicare Overview documents that are in addition to the Common Conformance Profile for Clinical Documents.

This minor release provides updated versions of the PCEHR Conformance Profile and Template Package Library product components. The updates are aimed at supporting improvements introduced with PCEHR Release 5.

This template package library provides validation rules for Medicare Overview documents to identify points of non-conformance to the relevant specifications. The template packages contained in this library can be used by the My Health Record system, other clinical information systems and the Agency's Clinical Package Validator tool. Clarification: PCEHR…

Medicare Overview v1.2 Medicare Overview documents provide an overview of Medicare-sourced information stored in an individual’s My Health Record. An individual’s My Health Record can be used to collect administrative information from Medicare records. Such records relate to the following data sets of claims and registries managed by…

Addendum to the E-Procurement Technical Architecture Version 1.0 – Mapping Web Services requirements to AS2

GST and rounding errors can be the source of legitimate variances in Purchase Orders and Invoices which may require manual intervention. Since one of the benefits of e-Procurement is to minimise the amount of manual intervention required, this document describes procedures that will allow these variances to be processed as automatically as possible. These…

This paper discusses the options for different document formats for Electronic Procurement for Health. Its purpose is to arrive at a shortlist or choice of suitable standards to represent the five document types nominated in the E-Procurement Business Architecture. This document replaces the Preliminary Evaluation (Version 1.6) paper,…

This business architecture provides the high level solution for the implementation of e-procurement in the Health supply chain. It explains the roles in the e-procurement community, and the shared processes that they use to achieve procurement using electronic document exchange. The purpose of the architecture is to define an Agency…

This document is part of the technical perspective of the E-Procurement Architecture and it describes the operational guidelines for E-Procurement Hub Services. This document is intended to form a checklist of capabilities that Hub Services should provide, and may be used as a foundation for the terms and conditions presented in Service…

This implementation architecture explains the paradigm of interactions between the three roles in E-Procurement: Buyers, Hubs and Suppliers. Some example interactions are shown using UML Interaction Diagrams. It then goes on to document the XML types and Web Services interfaces that are used to facilitate the exchange of business…

WSDL for E-Procurement