Diagnostic Imaging Resources

Diagnostic Imaging is a key diagnostic information source used by health applications. To find out more about Diagnostic Imaging click here.

The Australian Digital Health Agency provides sample code to assist software development and integration with the Healthcare Identifiers Service and the My Health Record system. Most sample code is available in .NET and Java. To see the full list, please visit the eHealth Reference Platform section on the Australian Digital Health Agency website or GitHub. Read more....

This guide explains how a requesting clinician can communicate to a pathology or diagnostic imaging provider that they should not upload a report to the patient’s My Health Record.

OIDs assigned by the Australian Digital Health Agency (ADHA) for external use under the arc of 1.2.36.1.2001.1005.

OID
Display
Definition

1.2.36.1.2001.1005.11
MIMS
This is the official OID for MIMS external products, principally the MIMS coding system for medications as widely used by vendors. This OID is reserved for MIMS, who will issue sub-OIDs from this OID for general use in CDA documents.

1.2.36.1.2001.1005.11.1
MIMS Standard Code set
The OID used for all MIMS codes as defined by the MIMS Integrated Data Solution (IDS). Usage notes for MIMS Codes -------------------------- The intended use of MIMS Data is to fully specify the product as a combination of Product Code, Form Code, and Pack Code. For example, when providing a MIMS Code within a CDA Document, the MIMS Code will be a minimum of 5 digits (in most cases will be 8 digits). Product Code: is 1 or more digits (usually a MIMS Product Code is 4 digits. Leading zeros are not required) Form Code: is always 2 digits (padded with leading zero) Pack Code: is always 2 digits (padded with leading zero) Example: 12340102 When decoded is interpreted as follows Product Code = 1234 Form Code = 1 Pack Code = 2 In some cases you may wish to only specify the product code. Whilst this is not the preferred use of MIMS data you may do so by ensuring the Form and Pack Codes are specific as zeros and must appended to the end of the Product Code. e.g. 12340000

1.2.36.1.2001.1005.12
NATA Lab Accreditation Number
NATA issues unique identifiers to laboratories when they are accredited. These numbers are used in v2 messages and CDA documents in order to identify the lab that is the source of a pathology report and the detailed items in it. This OID identifies that NATA lab accreditation number

1.2.36.1.2001.1005.13
Docle
DOCLE medical coding system – the OID used when representing DOCLE codes in CDA documents.

1.2.36.1.2001.1005.14
ISAAC
Root OID for identifying Integrated South Australian Activity Collection (ISAAC) lists maintained by South Australian government.

1.2.36.1.2001.1005.15
State Authority Number
State Authority Numbers issued to cover prescription payments. This is a reserved root OID which contains sub-OIDs for each State. This OID should never be used.

1.2.36.1.2001.1005.15.1
State Authority Number, NSW
State Authority Numbers issued to cover prescription payments by the Australian State of NSW.

1.2.36.1.2001.1005.15.2
State Authority Number, VIC
State Authority Numbers issued to cover prescription payments by the Australian State of VIC.

1.2.36.1.2001.1005.15.3
State Authority Number, QLD
State Authority Numbers issued to cover prescription payments by the Australian State of QLD.

1.2.36.1.2001.1005.15.4
State Authority Number, SA
State Authority Numbers issued to cover prescription payments by the Australian State of SA.

1.2.36.1.2001.1005.15.5
State Authority Number, WA
State Authority Numbers issued to cover prescription payments by the Australian State of WA.

1.2.36.1.2001.1005.15.6
State Authority Number, TAS
State Authority Numbers issued to cover prescription payments by the Australian State of TAS.

1.2.36.1.2001.1005.15.7
State Authority Number, NT
State Authority Numbers issued to cover prescription payments by the Australian State of NT.

1.2.36.1.2001.1005.16
NSW Health Domain
This OID Arc will be used to register NSW Health Domain specific concepts. Initially this will be NSW Health identifiers for patients (MRNs, AUIDs) and NSWH Data Dictionary schemes (such as Facility Code) but may be expanded to other NSW Health specific concepts.

1.2.36.1.2001.1005.17
Australian Vaccine Code
OID that identifies item codes defined in the Australian Childhood Immunisation Register Vaccine, as managed and published by the Australian Department of Health and Ageing. The version of the code system should be conveyed along with the code, and the version should be in the form YYYYMM which corresponds  to the official month of the medicare schedule that the code is taken fromNote: The OID is a leaf node - it is used in a coded data element to indicate that the accompanying code in the coded data element identifies an Australian Childhood Immunisation Register Vaccine. The OID is not an arc that can be extended by adding OIDs below it

1.2.36.1.2001.1005.18
Unit Record Number
This is the Healthcare Client identifier and is unique within a Queensland Health facility. Synonym: Medical Record (MR) Number

1.2.36.1.2001.1005.19
NT Department Of Health
This OID Arc will be used to register NT Department Of Health specific concepts. Initially this will be NT Department Of Health patient identifiers(HCID, HRN) but may be expanded to other NT Department Of Health specific concepts.

1.2.36.1.2001.1005.19.1
Health Connect Identifier for NT Department of Health
This OID will be used for identifying NT Department Of Health 'Health Connect Identifiers'.

1.2.36.1.2001.1005.19.10
Clinical Workstation IDs for NT Department of Health
NT Clinical Information System Identifiers for use with a unique user identifier when HPI-I is not available. This OID will be used for identifying the Clinical Workstation (Acute Care System).

1.2.36.1.2001.1005.19.11
NT Clinical Information System Identifiers
NT Clinical Information System Identifiers for use with a unique user identifier when HPI-I is not available. One additional OID is required required for the use of an ePass based unique identifier. NT DoH has a root OID, which is 1.2.36.1.2001.1005.19

1.2.36.1.2001.1005.19.2
Hospital Record Number for NT Department of Health
This OID will be used for identifiying NT Department Of Health 'Hosptial Record Numbers'.

1.2.36.1.2001.1005.19.3
SEHR Facility Codes for NT Department of Health
This OID will be used for identifying NT Location/Site Identifier for our Electronic Health Record.

1.2.36.1.2001.1005.19.4
Clinical System IDs for NT Department of Health
This OID will be used for identifying NT Clinical Information System Identifiers for our Electronic Health Record.

1.2.36.1.2001.1005.19.5
SEHR User IDs for NT Department of Health
This OID will be used for identifying NT User Identifiers for our Electronic Health Record.

1.2.36.1.2001.1005.19.6
PICS Central IDs for NT Department of Health
NT Clinical Information System Identifiers for use with a unique user identifier when HPI-I is not available. This OID will be used for identifying the PICS Central (NT Primary Care System, central server).

1.2.36.1.2001.1005.19.7
PICS Bagot IDs for NT Department of Health
NT Clinical Information System Identifiers for use with a unique user identifier when HPI-I is not available. This OID will be used for identifying the PCIS Bagot (NT Primary Care System, Bagot server)

1.2.36.1.2001.1005.19.8
PICS Binjari IDs for NT Department of Health
NT Clinical Information System Identifiers for use with a unique user identifier when HPI-I is not available. This OID will be used for identifying the PCIS Binjari (NT Primary Care System, Binjari server).

1.2.36.1.2001.1005.19.9
Caresys l IDs for NT Department of Health
NT Clinical Information System Identifiers for use with a unique user identifier when HPI-I is not available. This OID will be used for identifying the CareSys (Acute Care System).

1.2.36.1.2001.1005.20
Medications at Admission
This is the descriptor for information about medications recorded (usually, by a Ward Pharmacist) as being taken by the patient at time of admission to hospital for the current encounter. Each medication is described by the following data elements; 1) Generic or Brand Name/Strength/Form 2) Directions 3) Status 4) Reason

1.2.36.1.2001.1005.21
Australian Department of Human Services Modifications of MBS Item and DVA Fee Schedule Item
OID that identifies the code system of combined Medicare Benefits Schedule items and Department of Veterans' Affairs fee schedule items as modified and maintained by the Australian Government Department of Human Services. This code system has historically identified MBS and DVA items as belonging to the same code system. One of the modifications included padding MBS codes with leading zeros so they are all of a consistent character length. Note: The OID is a leaf node - it is used in a coded data element to identify the code system of which a code belongs. The OID is not an arc that can be extended by adding OIDs below it.

1.2.36.1.2001.1005.22
Australian Department of Human Services Modified PBS Schedule Item
OID that identifies Pharmaceutical Benefits Scheme schedule item codes as modified by the Australian Government Department of Human Services. The modifications are typically padding codes with leading zeros so they are all of a consistent character length. The canonical PBS schedule item code system is published by the Australian Department of Health and is uniquely identified. Note: The OID is a leaf node - it is used in a coded data element to identify the code system of which a code belongs. The OID is not an arc that can be extended by adding OIDs below it.

1.2.36.1.2001.1005.23
Australian PBS Manufacturer Code
OID that identifies the two letter manufacturer codes used in the Australian Pharmaceutical Benefit Schedule as managed and published by the Australian Department of Health and Ageing. The Australian Pharmaceutical Benefits schedule is released regularly. The version of the code system should be conveyed along with the code, and the version should be in the form YYYYMMDD which corresponds to the official date of release of the schedule that the code is taken from. Note: The OID is a leaf node - it is used in a coded data element to indicate that the accompanying code in the coded data element identifies an PBS Item. The OID is not an arc that can be extended by adding OIDs below it.

1.2.36.1.2001.1005.24
Australian Streamlined Authority Approval Number
OID that identifies streamlined authority code defined by the Australian Pharmaceutical Benefit Schedule as managed and published by the Australian Department of Health and Ageing. The Australian Pharmaceutical Benefits schedule is released regularly. The version of the code system should be conveyed along with the code, and the version should be in the form YYYYMMDD which corresponds to the official date of release of the schedule that the code is taken from. Note: The OID is a leaf node - it is used in a coded data element to indicate that the accompanying code in the coded data element identifies an MBS Item. The OID is not an arc that can be extended by adding OIDs below it.

1.2.36.1.2001.1005.26
SA Health eHealth Systems
Root OID for identifying code systems and identifier namespaces maintained by eHealth Systems division of South Australian Department of Health and Ageing.

1.2.36.1.2001.1005.26.1
SA Health Clinical Document ID
Assignment ontology node for SA Health Clinical Document instance identifier. This OID is not used directly, but groups the OIDs for each application that creates clinical documents. Number for application (Oacis, PUMA or EPAS) must be appended to identify the namespace of a clinical document instance identifier.

1.2.36.1.2001.1005.26.1.1
SA Health Oacis Document ID
Namespace for identifier of an instance of a clinical document from Oacis. The PCEHR system requires that the root OID is globally unique, and not just the combination of root OID and extension text, therefore this OID will always be suffixed with the actual document ID, which is repeated in the extension, for example:

1.2.36.1.2001.1005.26.1.2
SA Health PUMA Document ID
Namespace for identifier of an instance of a clinical document from PUMA. The PCEHR system requires that the root OID is globally unique, and not just the combination of root OID and extension text, therefore this OID will always be suffixed with the actual document ID, which is repeated in the extension, for example:

1.2.36.1.2001.1005.26.1.3
SA Health EPAS Document ID
Namespace for identifier of an instance of a clinical document from EPAS. The PCEHR system requires that the root OID is globally unique, and not just the combination of root OID and extension text, therefore this OID will always be suffixed with the actual document ID, which is repeated in the extension, for example:

1.2.36.1.2001.1005.26.2
SA Health Clinical Document Set ID
Assignment ontology node for SA Health Clinical Document set identifier. Code for application (Oacis, PUMA or EPAS) must be appended to identify the namespace of a clinical document set identifier.

1.2.36.1.2001.1005.26.2.1
SA Health Oacis Document Set ID
Namespace for set identifier of a clinical document from Oacis. In the setId element of the CDA document, this OID goes in the root attribute, and the actual set ID goes in the extension attribute. For example:

1.2.36.1.2001.1005.26.2.2
SA Health PUMA Document Set ID
Namespace for set identifier of a clinical document from PUMA. In the setId element of the CDA document, this OID goes in the root attribute, and the actual set ID goes in the extension attribute. For example:

1.2.36.1.2001.1005.26.2.3
SA Health EPAS Document Set ID
Namespace for set identifier of a clinical document from EPAS. In the setId element of the CDA document, this OID goes in the root attribute, and the actual set ID goes in the extension attribute. For example:

1.2.36.1.2001.1005.26.3
SA Health Clinical Document Code Sets
Branch node that groups together various small code sets used within SA Health clinical documents.

1.2.36.1.2001.1005.26.3.1
SA Health Clinical Document Section
Small code set for extensions in SA Health clinical documents. This code set is used in the discharge summary in CDA schema path "ClinicalDocument/component/structuredBody/component/section/code". The full set of defined values is as follows: 1) 2) 3)

1.2.36.1.2001.1005.26.3.2
SA Health Separation Summary Medication Status
Small code set for SA Health Separation Summary Medication Status. This code set is used in the discharge summary at NEHTA SDT Data Component "Therapeutic Good > Medication History > Item Status" which is mapped to CDA schema paths
 
"ClinicalDocument/component/structuredBody/component[meds]/
section/component[current|ceased]/section/entry[sbadm]/
substanceAdministration/entryRelationship[item_status]/observation/code"

(current or ceased medication item status). The full set of defined values is as follows: 1) 2) 3) 4)

1.2.36.1.2001.1005.26.5
SA Health Recipient Organisation
Assignment ontology node for SA Health identifiers of document recipient organisations. Code for assigning system must be appended to identify the namespace of an organisation identifier.

1.2.36.1.2001.1005.26.5.1
SA Health Oacis Practice Location
Namespace for identifier (practice location ID) of an organisation that the OACIS user selected as the recipient of a clinical document. This is a numeric value allocated by the Health Provider Registry or its replacement. This OID goes in the root attribute, and the numeric location ID goes in the extension attribute at CDA schema path "informationRecipient/intendedRecipient/receivedOrganization/ext:asEntityIdentifier/ext:id".

1.2.36.1.2001.1005.26.6
SA Health Recipient Individual
Assignment ontology node for SA Health identifiers of document recipient individuals. Code for assigning system must be appended to identify the namespace of an individual identifier.

1.2.36.1.2001.1005.26.6.1
SA Health Oacis Provider Number
Namespace for identifier (e.g. provider number) of an individual that the Oacis user selected as the recipient of a clinical document. This is an alphanumeric value, often but not always the Medicare Provider Number. Other known formats are "SADInnnnn", originally allocated by SA Divisions of General Practice Inc (SADI) for providers who do not have a Medicare Provider Number, and "RMnnnn", allocated by Oacis for a Records Manager (RM) at each practice location. This OID goes in the root attribute, and the provider number goes in the extension attribute at CDA schema path "informationRecipient/intendedRecipient/informationRecipient/ext:asEntityIdentifier/ext:id".

1.2.36.1.2001.1005.26.7
SA Health Local System User
Assignment ontology node for SA Health identifiers of local system users. Code for assigning system must be appended to identify the namespace of an individual identifier.

1.2.36.1.2001.1005.26.7.1
SA Health Active Directory Account
Namespace for identifier of a local system user from the SA Health Active Directory (HAD). This OID goes in the root attribute, and the alphanumeric user logon name goes in the extension attribute at CDA schema path "author/assignedAuthor/assignedPerson/ext:asEntityIdentifier/ext:id". For example:

1.2.36.1.2001.1005.26.7.2
SA Health Oacis User ID
Namespace for identifier of a local system user of the Oacis application, which is used to identify the author of an Oacis discharge summary, in lieu of an HPI-I. This OID goes in the root attribute, and the numeric Oacis User ID goes in the extension attribute at CDA schema path "author/assignedAuthor/assignedPerson/ext:asEntityIdentifier/ext:id". For example:

1.2.36.1.2001.1005.27
eRx root OID
Root OID for identifying code systems and identifier namespaces maintained by eRX Systems.

1.2.36.1.2001.1005.27.1
eRx Identifiers
Root OID for identifying identifiers maintained by eRX Systems.

1.2.36.1.2001.1005.27.1.1
eRX Prescription Item Identifier
An identifier used by eRx to identify prescription items.

1.2.36.1.2001.1005.27.1.2
eRx Dispense Item Identifier
An identifier used by eRx to identify dispense items.

1.2.36.1.2001.1005.28
Barwon root OID
Root OID for identifying code systems and identifier namespaces maintained by Barwon Systems.

1.2.36.1.2001.1005.28.1
Barwon Identifiers
Root OID for identifying identifiers maintained by Barwon Systems.

1.2.36.1.2001.1005.28.1.1
Barwon Prescription Item Identifier
An identifier used by Barwon to identify Prescription items.

1.2.36.1.2001.1005.28.1.2
Barwon Dispense Item Identifier
An identifier used by Barwon to identify Dispense items.

1.2.36.1.2001.1005.28.1.3
Barwon Prescribe Transaction Identifier
An identifier used by Barwon to identify Prescribe Transactions.

1.2.36.1.2001.1005.28.1.4
Barwon Dispense Transaction Identifier
An identifier used by Barwon to identify Dispense Transactions.

1.2.36.1.2001.1005.29
HPI-O based Organisation Medical Record Identifier
An identifier used to identify a patient, scoped by an HPI-O. This OID is never used in CDA documents directly; instead, a sub-oid is used: root="1.2.36.1.2001.1005.29.[HPI-O]" extension="[MRN]". Note that this OID is provided as a default option; if the organisation has some other OID to use to identify the MRN, then that OID should be used instead.

1.2.36.1.2001.1005.30
ACT Government Health Directorate
Root OID for identifying code systems and identifier namespaces maintained by ACT Government Health Directorate.

1.2.36.1.2001.1005.30.1
ACT Government Health Directorate Hospital Entity Identifier
This is the OID of Local Hosp Medical Spectrum space. This will identify the locally defined codes for the Medical staff for both their role as author of the document and encounter participant.

1.2.36.1.2001.1005.30.2
ACT Government Health Directorate MRN
This is the OID of ACT Government Health Directorate MRN space. This OID is used to identify an MRN that has been issues to a patient/client of a Health Directorate hospital or service.

1.2.36.1.2001.1005.30.3
ACT Government Health Directorate Healthcare Institution
This OID represents the custodian organisation for the CDA document; in this case the assigned custodian will be the Canberra Hospital.

1.2.36.1.2001.1005.30.4
TCH Drug Administration System
This is the OID of the Canberra Hospital Drugs administration system space. It will be used to identify the Code System used to code the drugs listed in the medication section of the discharge summary.

1.2.36.1.2001.1005.30.5
TCH Portal Identifier
This OID represents the identifier to be used as a temporary alternative option when the HPI-I is unavailable. Example:

1.2.36.1.2001.1005.31
MedView patient identifier
These identifiers appear to identify the patient to whom medications have been prescribed or dispensed.

1.2.36.1.2001.1005.32
MedView individual customer identifier
These identifiers uniquely identify healthcare individuals (e.g. Prescribing GPs). The identifier appears frequently as the Prescriber individual is used in a number of structures in the e-Prescription Record CDA Documents (i.e. Author, Custodian, Legal Authenticator, etc.)

1.2.36.1.2001.1005.33
MedView individual customer identifier dispense
These identifiers uniquely identify healthcare individuals (e.g. Pharmacies). The identifier appears frequently as the Dispensing individual is used in a number of structures in the Dispense Record CDA Documents (i.e. Author, Custodian, Legal Authenticator, etc.)

1.2.36.1.2001.1005.34
MedView dispensed item identifier
This identifier is for items dispensed in the dispense record.

1.2.36.1.2001.1005.35
MedView transaction identifier
An identifier used by eRx to identify transactions uniquely.

1.2.36.1.2001.1005.36
MedView prescription item identifier
This identifier is for items in the prescription and the dispense record.

1.2.36.1.2001.1005.37
MedView organisation customer identifier - Prescribe
These identifiers uniquely identify prescribing healthcare organizations.

1.2.36.1.2001.1005.38
MedView organisation customer identifier - Dispense
These identifiers uniquely identify Dispensing healthcare organizations.

1.2.36.1.2001.1005.39
MedView message identifier
These identifiers identify the message Id of the messages which are transformed into CDA Documents by the MedView Collector Adapter.

1.2.36.1.2001.1005.40
Calvary Healthcare ACT - Public - Root OID
Root OID for identifying code systems and identifier namespaces maintained by Calvary Healthcare ACT - Public.

1.2.36.1.2001.1005.40.1
Calvary Healthcare ACT - Public - Custodian Organisation ID
This OID represents the custodian organisation for the CDA document; in this case the assigned custodian will be Calvary Healthcare ACT - Public.

1.2.36.1.2001.1005.40.2
Calvary Healthcare ACT - Public - Entity Identifier
This is the OID of Local Hosp Medical Spectrum space. This will identify the locally defined codes for the Medical staff for both their role as author of the document and encounter participant.

1.2.36.1.2001.1005.40.3
Calvary Healthcare ACT - Public - Drug Administration System
This is the OID of Calvary Healthcare ACT – Public, Drugs administration system space. It will be used to identify the Code System used to code the drugs listed in the medication section of the discharge summary.

1.2.36.1.2001.1005.40.4
Calvary Portal Identifier
This OID represents the identifier to be used as a temporary alternative option when the HPI-I is unavailable for Calvary. Example:

1.2.36.1.2001.1005.41
HPI-O based Local System Identifier
An identifier used to identify a Provider when an HPI-I isn't available, scoped by an HPI-O. This OID is never used in CDA documents directly; instead, a sub-oid is used: root="1.2.36.1.2001.1005.41.[HPI-O]" extension="[LocalSystemIdentifier]". Example: Note that this OID is provided as a default option; if the organisation has some other OID to use to identify the Local System Identifier, then that OID should be used instead.

1.2.36.1.2001.1005.42
PCEHR Child Development Information Data Root OID
Root OID for identifying the PCEHR Child Development Information Data and Questionnaire content for inclusion in the PCEHR. Child Arcs are used to identify State/Territory and the specific questions, answers and schedules for Child Developmental Information Questionnaire content. (.1) ACT (.2) NSW (.3) VIC (.4) QLD (.5) SA (.6) WA (.7) TAS (.8) NT

1.2.36.1.2001.1005.42.1
PCEHR Child Development Information Data - Jurisdiction - ACT
This OID is for identifying ACT's Child Developmental Information Questionnaires. Child Arcs are used to identify: (.1) Questions (.2) Answers (.3) Health Check Types (.4) Schedules (.5) Section

1.2.36.1.2001.1005.42.2
PCEHR Child Development Information Data - Jurisdiction - NSW
This OID is for identifying NSW's Child Developmental Information Questionnaires. Child Arcs are used to identify: (.1) Questions (.2) Answers (.3) Health Check Types (.4) Schedules (.5) Section

1.2.36.1.2001.1005.42.3
PCEHR Child Development Information Data - Jurisdiction - VIC
This OID is for identifying VIC's Child Developmental Information Questionnaires. Child Arcs are used to identify: (.1) Questions (.2) Answers (.3) Health Check Types (.4) Schedules (.5) Section

1.2.36.1.2001.1005.42.4
PCEHR Child Development Information Data - Jurisdiction - QLD
This OID is for identifying QLD's Child Developmental Information Questionnaires. Child Arcs are used to identify: (.1) Questions (.2) Answers (.3) Health Check Types (.4) Schedules (.5) Section

1.2.36.1.2001.1005.42.5
PCEHR Child Development Information Data - Jurisdiction - SA
This OID is for identifying SA's Child Developmental Information Questionnaires. Child Arcs are used to identify: (.1) Questions (.2) Answers (.3) Health Check Types (.4) Schedules (.5) Section

1.2.36.1.2001.1005.42.6
PCEHR Child Development Information Data - Jurisdiction - WA
This OID is for identifying WA's Child Developmental Information Questionnaires. Child Arcs are used to identify: (.1) Questions (.2) Answers (.3) Health Check Types (.4) Schedules (.5) Section

1.2.36.1.2001.1005.42.7
PCEHR Child Development Information Data - Jurisdiction - TAS
This OID is for identifying TAS's Child Developmental Information Questionnaires. Child Arcs are used to identify: (.1) Questions (.2) Answers (.3) Health Check Types (.4) Schedules (.5) Section

1.2.36.1.2001.1005.42.8
PCEHR Child Development Information Data - Jurisdiction - NT
This OID is for identifying NT's Child Developmental Information Questionnaires. Child Arcs are used to identify: (.1) Questions (.2) Answers (.3) Health Check Types (.4) Schedules (.5) Section

1.2.36.1.2001.1005.43
PBS Closing the Gap Benefit
Identifies the Closing the Gap PBS Co-payment Measure.

1.2.36.1.2001.1005.44
RACF Id
A RACF Id is a string issued by the Australian government which is used to identify residential aged care facilities.

1.2.36.1.2001.1005.45
PCEHR Custom Data Component
For identification of custom data components which is used within PCEHR Documents.

1.2.36.1.2001.1005.46
TAS Department of Health and Human Services
This OID Arc will be used to register TAS Department Of Health and Human Services specific concepts. Initially this will be TAS Department Of Health and Human Services patient identifiers(THCI) but may be expanded to other TAS Department Of Health and Human Services specific concepts.

1.2.36.1.2001.1005.46.2
TAS Department of Health and Human Services Patient ID Branch
TAS Health Identifier eHealth systems under root OID for the OID arc - Patient identifier.

1.2.36.1.2001.1005.46.2.1
TAS Department of Health and Human Services Client Identifier (THCI)
TAS Clinical Information System Identifiers for our Electronic Health Record under Patient's(.2) for the instance identifier (II) Tasmanian Health Client Identifier [THCI].

1.2.36.1.2001.1005.46.3
TAS Department of Health and Human Services DHHS Drug File Identifier
DHHS Drug File identifier

1.2.36.1.2001.1005.47
ANZSIC
Australian and New Zealand Standard Industrial Classification. See: http://www.abs.gov.au/ausstats/abs@.nsf/mf/1292.0

1.2.36.1.2001.1005.48
Diagnostic Imaging Provider location specific practice number
The Department of health issues location specific practice numbers (LSPN's) to Diagnostic Imaging providers in the accreditation program. A unique LSPN's is issued to diagnostic providers when they are accredited. These numbers are used in v2 messages and CDA documents in order to identify the diagnostic imaging provider that is the source of a diagnostic imaging report and the detailed items in it. This OID identifies that LSPN number.

1.2.36.1.2001.1005.49
HIPS (Healthcare Identifier and PCEHR System)
Root OID for identifying code systems and identifier namespaces for use with in the Healthcare Identifier and PCEHR System (HIPS) product.

1.2.36.1.2001.1005.49.1
HIPS Document Id
Namespace for identifier of an instance of a clinical document from HIPS. The PCEHR system requires that the root OID is globally unique, and not just the combination of root OID and extension text, therefore this OID will always be suffixed with the HPIO of the organisation creating the document and the local document id, which is repeated in the extension, for example:

1.2.36.1.2001.1005.49.2
HIPS Set Id
Namespace for set identifier of an instance of a clinical document set from HIPS. The PCEHR system requires that the combination of the root OID and extension text for a setId must be unique, therefore this OID will always be suffixed with the HPIO of the organisation creating the document set, and in the extension is a unique document setId for that HPIO, for example:

1.2.36.1.2001.1005.49.3
HIPS Medical Record Id
Namespace for Medical Record identifier of a patient from HIPS. The CDA Document requires that the second Entity Identifier of the patient relates to the local Medical Record of the patient. The root is a combination of this OID, the HPI-O number and the HospitalId (from within HIPS) to create a sub-oid, and the extension text will be the actual MR. For example:

1.2.36.1.2001.1005.49.4
HIPS Entity Id
Entity idenfier for HIPS to record when no HPI-I is available

1.2.36.1.2001.1005.50
Prescription Identifier scoped by an HPI-O
This OID is used as the root of an arc that organisations can use for their own internal prescription IDs. This OID is never used directly – instead, the 16 digit HPIO is appended to the OID, like so: 1.2.36.1.2001.1005.50.[HPIO], where it goes in the CDA id root to identify that organization's internal prescription identifier (which goes in the id extension). If an organization has more than one prescription identifier, it should use a finer grained HPI-O.

1.2.36.1.2001.1005.51
Dispense Record Identifier scoped by an HPI-O
This OID is used as the root of an arc that organisations can use for their own internal dispense record IDs. This OID is never used directly – instead, the 16 digit HPIO is appended to the OID, like so: 1.2.36.1.2001.1005.51.[HPIO], where it goes in the CDA id root to identify that organization's internal dispense record identifier (which goes in the id extension). If an organization has more than one dispense record identifier, it should use a finer grained HPI-O

1.2.36.1.2001.1005.52
HPI-O based Local Order Identifier
This OID is used as the root of an arc that organisations can use for their own local order IDs. This OID is never used directly – instead, the 16 digit HPIO is appended to the OID, like so: 1.2.36.1.2001.1005.52.[HPIO], where it goes in the CDA id root to identify that organization's local order identifier (which goes in the id extension). Example:

1.2.36.1.2001.1005.53
HPI-O based Accession Number
This OID is used as the root of an arc that organisations can use to issue accession numbers in accordance with the DICOM standard. The OID is never used directly – instead, the 16 digit HPIO is appended to the OID, like so: 1.2.36.1.2001.1005.53.[HPIO], where it goes in the CDA id root to identify accession numbers issued by that organization (which goes in the id extension). Example:

1.2.36.1.2001.1005.54
HPI-O based Report Identifier
This OID is used as the root of an arc that organisations can use for their local report identifiers. This OID is never used directly – instead, the 16 digit HPIO is appended to the OID, like so: 1.2.36.1.2001.1005.54.[HPIO], where it goes in the CDA id root to identify that organization's local report identifier (which goes in the id extension). Example:

1.2.36.1.2001.1005.55
Pharmhos Medication Code
Namespace to represent Pharmhos medication codes

1.2.36.1.2001.1005.56
AHPRA Registration number
The AHPRA registration number for practitioners can be used to search the HI Service to retrieve the HPI-I. It is a unique identifier provided by AHPHA to manage and maintain their registers

1.2.36.1.2001.1005.57
i.Pharmacy Medicinal Product Code
Namespace to represent CSC i.Pharmacy medicinal product code

1.2.36.1.2001.1005.58
i.Pharmacy Dispense Identifier
Namespace to represent CSC i.Pharmacy dispense identifier

1.2.36.1.2001.1005.59
R8 WP09 - Medicines View, Detailed Design - Back-End
Document which defines content of the Medications View CDA to be used as the template ID in the XML.

1.2.36.1.2001.1005.60
Uniting Care Health Identifiers
Namespace to represent Uniting Care Health identifiers for facility, patients, encounters, orders and documents

1.2.36.1.2001.1005.61
Sonic Healthcare Australia Identifiers
Namespace to represent Sonic Healthcare Australia identifiers for facility, patients, providers, requests, orders and documents.

1.2.36.1.2001.1005.62
Kestral Computing Identifiers
Namespace to represent Kestral computing identifiers for facility, patients, providers, requests, orders and documents.

1.2.36.1.2001.1005.63
Mater Group Identifiers
Root OID identifying all local Mater Misericordiae Limited Clinical Document codes and identifiers for facility, patients, providers, requests, orders and documents

1.2.36.1.2001.1005.64
Minfos System Identifiers
Namespace to represent “Minfos” identifiers for representing concepts such as medicines, packages, facilities, patients, providers, requests, prescriptions, dispenses and documents.

1.2.36.1.2001.1005.65
Phillips & Phillips Pharmacy Computers Identifiers
Namespace to represent “Phillips and Phillips” identifiers for representing concepts such as medicines, packages, facilities, patients, providers, requests, prescriptions, dispenses and documents.

1.2.36.1.2001.1005.66
Peninsula Health
Root OID to represent Peninsula Health identifiers for representing concepts such as medicines, packages, facilities, patients, providers, requests, prescriptions, dispenses and documents which will be identified as sub-arcs.

1.2.36.1.2001.1005.66.1
Peninsula Health MR Id
Namespace to represent Peninsula Health Medical Record Identifier

1.2.36.1.2001.1005.67
MyScript
Namespace to represent “Myscript” identifiers for representing concepts such as medicines, packages, facilities, patients, providers, requests, prescriptions, dispenses and documents

1.2.36.1.2001.1005.68
For identifier dispense and prescription record
Namespace to represent “Corum Health” identifiers for representing concepts such as medicines, packages, facilities, patients, providers, requests, prescriptions, dispenses and documents

1.2.36.1.2001.1005.69
Z Software Pty Ltd
Namespace to represent “Z Software Pty Ltd” identifiers for representing concepts such as medicines, dispenses and documents.

1.2.36.1.2001.1005.70
ABN or ACN based Local Individual Service Provider Identifier
An identifier used to identify an individual service provider, scoped by an ABN or ACN. This OID is never used in CDA documents directly; instead, a sub-oid is used: root="1.2.36.1.2001.1005.70.[ABN or ACN]" extension="[identifier]". Note that this OID is provided as a default option; if the organisation has some other OID to use to identify individual service providers, then that OID should be used instead.

1.2.36.1.2001.1005.71
ABN or ACN based Local Medical Record Identifier
An identifier used to identify a patient, scoped by an ABN or ACN. This OID is never used in CDA documents directly; instead, a sub-oid is used: root="1.2.36.1.2001.1005.71.[ABN or ACN]" extension="[MRN]". Note that this OID is provided as a default option; if the organisation has some other OID to use to identify MRNs, then that OID should be used instead.

1.2.36.1.2001.1005.72
Western Health
Namespace to represent “Western Health” identifiers for representing concepts such as medicines, packages, facilities, patients, providers, requests, prescriptions, dispenses and documents

1.2.36.1.2001.1005.73
HealthSoft Australia Ltd
Namespace to represent “RxOne” identifiers for representing concepts such as medicines, packages, facilities, patients, providers, requests, prescriptions, dispenses and documents

1.2.36.1.2001.1005.74
NATA Site Number
National Association of Testing Authorities (NATA) Site Number - a specific location reference identifier for a NATA accredited facillity. See National Association of Testing Authorities (NATA) / for more information.

1.2.36.1.2001.1005.75
Queensland Health
The OID will identify the originating jurisdiction as Queensland Health. This OID will be used for operational and audit purposes.

1.2.36.1.2001.1005.76
R10.2 WP01 – Pathology and DI CDA-based Views – Detailed Design
Document which defines content of the Pathology and DI View CDA to be used as the template ID in the XML.

The Agency now provides sample code libraries directly from GitHub and NuGet enabling developers to: 

  • access both released and interim versions of the sample code;
  • interact and collaborate directly with the Agency's development team; and
  • submit feedback and their own code changes for inclusion in the libraries.
Wednesday, 31 July 2019

The Australian Digital Health Agency is pleased to announce version 1.0 of its Java-based CDA™ Document Library.

For GP desktop software, please also read about the Practice Incentives Program (PIP).

To enable the uploading of clinical documents and the viewing of a patient's My Health Record, the following functionality and supporting material is recommended.

We have created the following templates to assist you in achieving a successful project outcome. While they are based on our experience in project of this type, we can't guarantee their completeness or relevance to your organisation.

The following Diagnostic Imaging Process Flows were updated in March 2018.

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