Stream: australia
Topic: HL7 AU Terminology Server
Grahame Grieve (Jan 05 2018 at 11:21):
Today @Heath Frankel has reminded me that we have an HL7 Australian terminology service... should be at tx.hl7.org.au... but no one is using it. In fact, what would we use it for? why have it? is this a good thing?
Brian Postlethwaite (Jan 05 2018 at 21:49):
Only thing I can think of is being the definitive location for the AU terminology content, which will be in the AU Implementation Guides.
Grahame Grieve (Jan 05 2018 at 22:05):
but we could host that on tx.fhir.org.... which would be easier more generally
Brian Postlethwaite (Jan 05 2018 at 22:08):
Or the registry when that comes online?
Brian Postlethwaite (Jan 05 2018 at 22:09):
(I'm also not sure on what version that tx.hl7au is running)
Brett Esler (Jan 18 2018 at 01:01):
Think that is an older version of FHIR? I would be happy with tx.fhir.org hosting.. @Heath Frankel i can inform the HL7 AU board that the service tx.hl7.org.au... should/could be turned off
Brett Esler (Jan 18 2018 at 01:03):
gathering terminolgies from the published Base AU is on the cards - @Grahame Grieve how to go about inclusion for tx.fhir.org ? nominate content in the base AU spec download?
Grahame Grieve (Jan 18 2018 at 10:18):
I don't know what the process should be - I'll add it to my todo list
Dion McMurtrie (Jan 19 2018 at 02:52):
I'm not too sure how this fits in, or what the distinction should be, but the NCTS is attempting to be a source of terminology resource for FHIR profile binding as well, certainly from the Ageny's CI team but how much further it should or shouldn't go isn't completely clear. The vision and remit for the NCTS is to be a one stop authoritative source for the terminology resources needed for national specifications - intended to make it easier to get this content from a consistent, maintained source in a common form.
Currently the NCTS is well short of that vision in terms of scope of content, but (while it may not seem like it) there is active work going on to realise that vision. The first round of resources to support the CI team's work will be published in February, and you can expect it to continue after that. The major hurdle for this work so far seems to be getting repeatable, maintainable processes and supporting data feeds, and appropriate legal agreements to publish the content and maintain it ongoing. However we're beginning to round some of those issues. The challenges aren't really technical.
Clearly their purposes intersect, but what is the vision for the HL7 AU terminology server and how does it intersect and differ from the NCTS?
To be clear I'm not trying to kill of one in favour of the other or have the NCTS take over the world, I just want to make sure we all understand the purposes of each so we don't unnecessarily duplicate effort and can coordinate/collaborate. There's plenty of work around without duplicating it!
One suggestion (off the top of my head) is that each server could feed the other, and the owning organisations could maintain distinct sets of content. For example the NCTS may work through the Agency with other government agencies and departments to publish their canonical FHIR forms of their code systems, but get all HL7 international and AU defined code systems from the HL7 AU server and vice versa? Or is that duplicated content not worthwhile?
Brian Postlethwaite (Jan 19 2018 at 05:39):
I think the question was do we need the AU server at all, and could we just use the international server to host that content.
I personally don't have an issue with the AU content being in the NCTS, infact I would love it to be there.
(whole thread came around to see if the AU term server was still wanted, should be updated)
Grahame Grieve (Jan 19 2018 at 10:05):
I feel as though there's different sources of truth here - source of truth for forth coming ballots, and source of truth for adopted standards. Perhaps that's the difference between HL7 and NCTS?
Michael Lawley (Feb 02 2018 at 00:46):
To my mind it is a question of autonomy / control. I would expect HL7 AU to want to be in control of content, and thus operate its own server.
I would dearly like this to be an Ontoserver instance and am happy to provide resources to make this happen.
Grahame Grieve (Feb 02 2018 at 00:47):
that would work for me
Brett Esler (Feb 06 2018 at 00:10):
I am following up setup of HL7 AU Ontoserver instance to hold HL7 AU terminology content associated with all IG publications - there is also potential for NCTS to support republication and distribution channels through their network
Brian Postlethwaite (Aug 24 2021 at 03:13):
I was trying out this service and note that it's not returning json/xml ever...
https://www.healthterminologies.gov.au/integration/R4/fhir/CodeSystem/australian-indigenous-status-1
Should it?
I'm looking for a computable location to download these from via tooling.
Liam Barnes (Aug 24 2021 at 06:22):
Hi @Brian Postlethwaite I'm not certain of how that url should function but the location you're looking for may be:
https://api.healthterminologies.gov.au/integration/R4/fhir/CodeSystem/australian-indigenous-status-1
Brian Postlethwaite (Aug 24 2021 at 06:54):
Thanks, I'll give that a whirl.
Brian Postlethwaite (Feb 09 2022 at 22:08):
Has anyone done done an Australian localization of the Jurisdictions Valueset for use here?
And would that have more than just the states in it?
http://hl7.org/fhir/valueset-jurisdiction.html
Last updated: Apr 12 2022 at 19:14 UTC
