Page tree
Skip to end of metadata
Go to start of metadata

Approach to Coding/Profiling URL allocation

PBS Item Code yes

PBS Item Code - correspondence received re acceptance of this form

confirmed: MEDS WG; PBS


use Coding.version to identify specific verision eg.


Australian Medicines Terminology (same as it is part of SNOMED-CT AU)

use Coding.version to identify specific verision eg.

confirmed: MEDS WG

ANZSCO of Occupations; Confirmed NCTS + PA WG; NCTS publishing pending
ANZSIC Classification: Confirmed NCTS + PA WG; published by HL7 AU
ARTG? ??

discussion required to decide on this


Indigenous Status


Confirmed NCTS + PA WG; NCTS publishing pending

Individual Healthcare Identifier Status

yesConfirmed NCTS + PA WG; NCTS publishing pending
Individual Healthcare Identifier Record Status NCTS + PA WG; NCTS publishing pending
Date Accuracy Indicator

yesConfirmed NCTS + PA WG; NCTS publishing pending
Australian States and Territories

yesConfirmed NCTS + PA WG; NCTS publishing pending
Concurrent Supply Grounds NCTS + MEDS WG; NCTS publishing pending


IHI agency; PA WG
HPI-I agency; PA WG 
HPI-O agency; PA WG 
Medicare Number agency; PA WG 
DVA Number agency; PA WG 
Medicare Provider Number agency; PA WG 
Prescriber Number agency; PA WG
Centerlink Customer Reference Number

confirmed: agency; PA WG



  1. I know this is a work in progress, but I saw the notification so while I think of it, AMT is part of SNOMED CT-AU now so just a single URI -{version}

  2. Note that there is no SNOMED CT-AU or AMT FHIR CodeSystem URI other than

    The uri listed above ( is a (partial) version URI that identifies the SNOMED CT-AU "Edition", which represents a family of versions.


    1. thanks Michael - so for AU use just go for for all SNOMED coding including AMT concepts  - right?

      or do we need to be version specific?

  3. I think Michael is saying that in the FHIR world the URI for the code system is always for all SNOMED CT editions. The version URI is where the distinction of the particular edition and version exists.


        "system": "",
        "code": "372567009",
        "version": "",
        "display": "Metformin"

    The version part is optional, but when specified it includes the edition it is from (in this case SNOMED CT-AU) and the version of that edition (the January 2017 release)

  4. thanks all - very helpful... 

  5. I'd suggest as the URI for the ARTG. I've contacted the TGA to try and agree with them the appropriate URI and am awaiting a response.

    I've also contacted Steve Ball from the PBS who has confirmed for PBS item codes. There are a number of other PBS code systems used in the PBS data and the PBS page provides good candidate URIs for code systems used in the data. Those URIs starting with are the clear candidate URIs for referencing the code systems PBS has. Steve has extracted these into a file that will be included in future PBS releases.

     In my work I've referenced a few of these, but there are rather a lot of them. I'd suggest we add them to the table above as they get used rather than adding a large number. The ones I've used are

    Should I add them above?

    1. Thanks Dion - very helpful. Could you help define where these would get used i.e. against which resources for which elements?

      For manufacturer currently was thinking this is actually an identifier .e.g. especially as there is name and contact details associated with the manufacturing org.  

      it would be great to discuss at next Medications working group meeting.

  6. Hi Brett Esler, I'm drafting some of these national Code Systems and have been questioning the correct identification of them. Dion referred me here. 2 sources of current interest to me are METeOR and ABS. Can you provide any information on how you came to the URIs you've allocated. Did this involve any discussion with them? Thanks

    1. Thanks for asking Liam, I am also interested in the answer to your question.


      1. These (METeOR, and ABS) are under review and likely to change