Site search

This white paper discusses the alignment of health information management business practices with capabilities of standards-based health IT products to support information governance, patient safety and quality of care.

The FAQs are guidance material for implementation. They should be used for clarification purposes and to support existing documentation. This FAQ answers the question: What is the proper representation of pathology test result date/time

This document sets out the standards for general practices, developed by the Royal Australian College of General Practitioners (RACGP).

This FAQ answers the question: When retrieving Medicare documents from the My Health Record system why does the hash value in the metadata differ from the hash value of the CDA Relates to FAQ Hash value verification v1.0  

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. Previous file name: Vic IHI Integration Best Practice Guide v1.1.pdf

This standard defines universal and specialised characteristics of health terminological resources that make them fit for the purposes required of various applications.

This User Guide for Practice Managers is designed to assist practice managers to implement the Healthcare Identifiers (HI) Service.

The FAQs are guidance material for implementation. They are to be used for clarification purposes and to support existing documentation. This FAQ answers the question: How should the speciality field be used in an eDischarge Summary

The FAQs are guidance material for implementation. They should be used for clarification purposes and to support existing documentation. This FAQ answers the question: What are the nullable fields in clinical documents conformant to the CDA implementation guides

The FAQs are guidance material for implementation. They are to be used for clarification purposes and to support existing documentation. This FAQ answers the question: How to represent patient identifiers (other than IHIs) in CDA documents

This document specifies several metadata elements that describe resources containing medical knowledge.

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

This document describes the openEHR Resource Model, including identification, metadata, annotations and translations.

The FAQs are guidance material for implementation. They are to be used for clarification purposes and to support existing documentation.

The content covered in this FAQ has been clarified in the Document Exchange Technical Services Specification, section 4.1 as well as through the introduction of Conformance Point DEXS-T 124.

This FAQ is out of date and no longer accurate.

NOTE: The document presentation has been enhanced to align with current branding guidelines however the content has not been changed. The CDA implementation guides that include diagnostic service reports (eReferral, Specialist Letter, Event Summary, and Discharge Summary) divide the reports into pathology and radiology. This FAQ answers the question: What…

The content in this FAQ is now covered in the Document Exchange Technical Service Specification. Table 2 and Table 3 have been updated to ensure the correct typeCodeDisplayName fields are correct and consistent.

The FAQs are guidance material for implementation. They should be used for clarification purposes and to support existing documentation.

This FAQ describes an extension to these eDischarge Summary, eReferral and Specialist Letter that involves encapsulating the CDA package within an HL7 v2 MDM^T02 message (which covers the delivery of a document). Using this technique, the message payload can be transported through SMD messaging systems and other messaging networks designed to transport…

The content in this FAQ is now covered in the Document Exchange Service Technical Service Specification. Section 4.2.5 contains extra information specifying ClassCodes may be included in the query.

NOTE: The document presentation has been enhanced to align with current branding guidelines, however the content has not been changed. A global exclusion statement is common in CDA clinical documents and has three possible values: None known Not asked None supplied This FAQ answers the question: What is the proper use of none known in global exclusion…