Site search

This document provides guidance for facilities, hospitals, software developers and label vendors on the design of ISBT 128 labels for reproductive tissue and cell products.

This standard defines the data elements and structural relationships required for the unique identification and detailed description of medicinal products.

This standard defines the data elements, structures and relationships required for the exchange of regulated information to uniquely identify pharmaceutical products.

This document adds an additional annex to ISO 11615:2017. The annex specifies class name and attribute translations and synonyms for the identification of medicinal products.

This document provides detailed information about ISBT 128 product coding for tissue products (Product Description Codes that begin with the letter “T”).

This document provides guidance for cellular therapy facilities in the use of the Product Code [Data Structure 003], Product Divisions [Data Structure 032], and the supporting database in the coding of cellular therapy products.

The HIPS product enables the seamless integration of digital health systems with national digital health infrastructure services, such as the Healthcare Identifiers Service, the My Health Record system. The product data sheet provides information for implementers about the capabilities of the HIPS end product and its product components.

This reference set contains terminology to describe, in a health record, the product (medication) brand name or the grouping of products into a "family", for either single component products or components of multicomponent products.

This document provides guidance to users and software developers on the use of the Product Divisions [Data Structure 032] for cellular therapy and regenerated tissue products, when used with the Product Code [Data Structure 003].

This document provides detailed guidance for eye banks about ISBT 128 product coding for ocular tissue using the Product Code [Data Structure 003].

This document provides a standard terminology for describing transfusion and transplantation products. It helps users distinguish between products when required for safety, clinical practice, or inventory management.

SNOMED CT is a standard for data elements used in the electronic exchange of clinical information. This document specifies the concept model for representation of pharmaceutical and biological products in the international edition of SNOMED CT.

HIPS Mobile is a mobile web application that may be added to an existing HIPS v7.1 or higher instance operated by a HIPS site, enabling users to list, download and display CDA™ documents and views from a patient’s My Health Record on their mobile or tablet device. The product data sheet provides information for implementers about the…

The Health Viewer product enables the viewing of the My Health Record on various devices, including desktop, tablet and phone form-factors. Health Viewer is an optional add-on to HIPS and will be the eventual replacement for HIPS UI. HIPS is a middleware product offering standards-based interfaces for seamless integration with systems like patient…

This specification defines the components (benchmarks) of capability of terminological resources implementation in healthcare software products, including electronic health record systems.

A guide for vendors already in production. It covers topics such as incident management and software changes and upgrades. This document outlines the process for liaising with the My Health Record System Operator (SO) about production incidents and events requiring notification to the SO, such as changes and upgrades to software that connects to the My…

This document provides guidance for blood facilities in the use of the Product Code [Data Structure 003] and its supporting database in the coding of blood components.

The Clinical Document Packaging Library provides a sample implementation of how to package CDA documents (and any attachments) following the Agency specifications. This product component was previously called CDA Packaging Library - Product Data Sheet.

This FAQ answers: What identity information contained in a production or test NASH certificate should I use when validating a signature And What will be the impact on the CCA status of any SMD product that was tested with code that used the URI in the test NASH certificates issued before June 2012

The HIPS Core APIs provide a set of APIs that are dependencies for various HIPS products. As of this release, the following HIPS products are compatible with HIPS Core APIs v2.0: Document Authoring Adapter v1.0 Health Viewer v1.0 Structured Pathology Adapter v1.0

The Clinical Document Data Extractor Library simplifies the development process by providing vendors with a simple interface for extracting data from a range of CDA documents. The library uses the information from Agency-developed CDA implementation guides. This product component was previously called CDA Data Extractor Library - Product Data…

A guide for vendors already in production. It covers topics such as incident management and software changes and upgrades. This document outlines the process for liaising with the My Health Record System Operator (SO) about production incidents and events requiring notification to the SO, such as changes and upgrades to software that connects to the My…