Stream: australia
Topic: AU Base IG
Brett Esler (Apr 10 2017 at 07:50):
AU base IG is now in a basically navigable form with examples. http://build.fhir.org/ig/hl7au/au-fhir-base/index.html
I am compiling a list of review items for the PA WG teleconference on Wednesday http://confluence.hl7australia.com/display/PA/2017-04-12+Agenda -please feel free to point out any issues with the content.
The plan is - anything not reviewable on Wednesday won't go to the connectathon - some of the planned scope has already been cut back a bit. Will spend the week 14th to 21st Apr on QA fixes to the existing content (no more added scope, hopefully some of the profiling tooling is also available for this period). Final review on 26th April for static publication on 28th April. Implement up to Connectathon 26th May Sydney.
Brett Esler (Apr 18 2017 at 22:13):
Hi all please feel free to review and comment on the base IG material - comments here in Zulip and also on the HL7 AU confluence site will be addressed for next week's final review meeting on the 26th April. Release of Forge is a little later than expected, will be doing a technical clean-up of the profiles when that is available.
Brett Esler (Apr 18 2017 at 22:23):
I should also mention one can add issues directly into HL7 AU Jira http://jira.hl7australia.com/projects/PA and hit the 'Create' button
Grahame Grieve (Apr 18 2017 at 22:38):
btw: http://fhir.hl7.org.au/fhir/base/index.html
Grahame Grieve (Apr 18 2017 at 22:40):
why do we rule out animal? Do we assert that there is no vet care here in Australia?
Grahame Grieve (Apr 18 2017 at 22:42):
and I thought you said ANZSCO and ANZSIC where added?
Brett Esler (Apr 18 2017 at 22:44):
that is an old static build look at http://build.fhir.org/ig/hl7au/au-fhir-base/index.html
have not considered vet care patient; this profile is human as they have medicare number and IHI etc.. left the pets to core FHIR until we consider...
Grahame Grieve (Apr 18 2017 at 22:45):
might add a note about the vet care thing then
Grahame Grieve (Apr 18 2017 at 22:46):
ahh much better
Brett Esler (Apr 18 2017 at 22:46):
cool will do - will put some words on front page re this stuff - there are a lot of cases not consided
Brett Esler (Apr 18 2017 at 22:48):
btw IG builder rocks - considering the pain of getting a nice presentation of material together - can just concentrate on the real content...
Brett Esler (Apr 18 2017 at 22:51):
I am expecting there are some techmical profiling issue - e.g. missing elements etc; hand rolled sorts of issues; the plan is to clean this up when I have Forge to hold my hand...
Brett Esler (Apr 19 2017 at 03:07):
@Grahame Grieve some advice on slicing; expect DVA number identifier is broken as Identifier.type is not repeating and I have attempted to slice - the reason was to have a choice of specifc CodeableConcept with specific Identifier.type.text as a fixed value for codes. Is there a neat way to do this? A terminology binding will only constrain the Identifier.type.coding as far as I can tell (not the Identifier.type.text) so do I need to have invariants instead for this?
Grahame Grieve (Apr 19 2017 at 03:14):
not following. why do you need to slice the type?
Brett Esler (Apr 19 2017 at 03:18):
was looking for a way to set the entire CodeableConcept (including text) as options- think instead will bind the colour coding ValueSet to Identifer.type.coding then use invariants to verify specifc colour code + Identfier.type.text match (i.e. make sense)
Grahame Grieve (Apr 19 2017 at 03:56):
why don't you just fix the value of type complete?
Grahame Grieve (Apr 19 2017 at 03:56):
...completely?
Brett Esler (Apr 19 2017 at 03:57):
I have the option of 3 colours or unspecified colour for DVA
Brett Esler (Apr 19 2017 at 03:59):
i.e one of 3 codes + associated Identifier.type.text
Brett Esler (Apr 19 2017 at 03:59):
or no code + specific Identfier.type.text
Brett Esler (Apr 19 2017 at 04:01):
e.g type = { coding = [ code="DVG", system="... ], text ="DVA Number (Gold)” }
Brett Esler (Apr 19 2017 at 04:02):
unspecified
type = { text = "DVA Number” }
Grahame Grieve (Apr 19 2017 at 04:14):
isn't the colour part of the system?
Brett Esler (Apr 19 2017 at 04:17):
have not done that way... as the number is same format etc. could have the same number unspecified colour and then later a known colour - it is the same identifier...
Grahame Grieve (Apr 19 2017 at 04:21):
they're not going to clash? then it's not really the 'type' of the identifier; it's more like the IHI status
Brett Esler (Apr 19 2017 at 04:39):
ok doing my reading believe can change status (colour) base on changes in disability conditions
Grahame Grieve (Apr 19 2017 at 04:50):
supports my argument, I think
Brett Esler (Apr 19 2017 at 04:56):
same number could be unspecified (no one recorded colour); then gold (someone recorded it); then orange (disability status changed) - better to have separate Identifier.system for each of these (even though the same allocated number?)
Grahame Grieve (Apr 19 2017 at 05:00):
I think it's a status code personally
Brett Esler (Apr 30 2017 at 03:25):
Hi all the static publication of AU base profiles has been made in preperation for the 26th May connectathon
Brett Esler (Apr 30 2017 at 03:25):
The static publication may experience technical corrections as needed and can be found at http://fhir.hl7.org.au/fhir/base2017Apr/
Brett Esler (Apr 30 2017 at 03:29):
Registration for the event is now open on http://www.hl7.org.au/events/2017-may-hl7-education-and-connectathon-event/ it is free for HL7 Australia members - and you can become a member until 30th June 2018 and attend the event as part of registering if you are not a member so far.
Brett Esler (Apr 30 2017 at 03:30):
As well as the AU Base IG track at the conectathon there will be an 'Introduction to FHIR' track also running - a great chance for anyone looking to get started with FHIR.
Brett Esler (Apr 30 2017 at 03:33):
Please do promote the event with your organisations, partners and suppliers to expand the community!
Brian Postlethwaite (May 01 2017 at 05:23):
I'll be there and will likely give an update on the activities that occurred at the HL7 International WGM that is occuring in Madrid next week. And hope to have some great new things to share!
David Cai (May 18 2017 at 07:23):
@Brett Esler in http://fhir.hl7.org.au/fhir/base2017Apr/StructureDefinition-indigenous-status.html is it an error in Extension.url? It seems the same as the URL for the profile.
Brett Esler (May 21 2017 at 03:56):
@David Cai what was expected for this url for indigenous status extension?
David Cai (May 21 2017 at 23:32):
@Brett Esler I was confused because in both Extension: Australian IHI Status and Extension: Australian IHI Record Status, the URL for the profile is different from Extension.url. Can you or someone please explain the difference between these two URLs?
Brett Esler (May 21 2017 at 23:49):
got it - you are seeing some of the publishing issues we have at the moment; the URL in the definition of IHI status/record status extension is the 'official' ns.electronic.net.au url and the hl7.org.au url is the location it is currently published - this is a work in progress re sorting out where definitions are held and published; I would like to discuss this at the connectathon with participants there, at the PA working group and here on zulip...
Brett Esler (May 21 2017 at 23:50):
note also the urls in the definitions at http://fhir.hl7.org.au/fhir/base2017Apr/StructureDefinition-extension-au-ihi-status.html and http://fhir.hl7.org.au/fhir/base2017Apr/StructureDefinition-extension-au-ihi-record-status.html have be 'fixed' in the CI build at they were not as desired.....
David Cai (May 22 2017 at 00:07):
@Brett Esler Thanks that was much clear.
Grahame Grieve (May 25 2017 at 00:59):
@Brett Esler have we got an extension for CTG status? any discussion about that?
Grahame Grieve (May 25 2017 at 03:46):
Also, ABN
Grahame Grieve (May 25 2017 at 03:48):
how about a system value of http://business.gov.au
Brett Esler (May 25 2017 at 15:48):
@Grahame Grieve is that CTG code on a prescription? Or property of a patient?
Brett Esler (May 25 2017 at 15:52):
ABN suggestion looks good to me - anyone else with comments? Only as an extension of Organization?
Grahame Grieve (May 26 2017 at 05:48):
I think it's an identifier not an extension
Grahame Grieve (May 26 2017 at 05:48):
and yes, CTG is for the flag on patient
Brett Esler (May 31 2017 at 01:48):
For ABN - do we want to do ACN and ARBN also? these are all ASIC numbers so think we should use the same Identifier.system?
Brett Esler (May 31 2017 at 01:49):
add an Identifier type?
Grahame Grieve (May 31 2017 at 01:49):
yes
Grahame Grieve (May 31 2017 at 01:50):
not fussed about identifier type.
Brett Esler (May 31 2017 at 01:50):
cool - will draft up something into base IG for next PA meeting next week to look at
Brett Esler (May 31 2017 at 01:52):
For CTG status - Patient extension boolean - should it always be = true (i.e not there or true)?
Brett Esler (May 31 2017 at 01:53):
and and should we have invariant - Indigenous Status extension code must be Aboriginal, TSI or Aboriginal & TSI for CTG status=true
Grahame Grieve (May 31 2017 at 01:55):
I don't think that we should fix extensions to true, unless we are completely sure that there's no difference between false and unknown
Grahame Grieve (May 31 2017 at 01:55):
and I don't know that there's any clerical rule that you must document indigenous status code if you claim CTG?
Brett Esler (May 31 2017 at 02:01):
Agree CTG - optional extension boolean sound good
Brett Esler (May 31 2017 at 02:08):
GP systems apply business logic - must have an ATSI status to allow CTG registered status - basically affects prescribing behaviour (i.e. add a code on script printed) - it doesn't say you need to record the indigenous status anywhere on the claiming side as afar as i can tell- so will drop the invariant - i.e. could just have the CTG status
Brett Esler (Jun 02 2017 at 00:29):
@Grahame Grieve I have switched ig.json content for AU Base IG to 3.1.0 (which is not the desired 3.0.1) due to build issues - will this have any major detrimental effects for now? 3.0.1 ig build should be fixed sometime correct?
Grahame Grieve (Jun 02 2017 at 02:59):
fixed now
Grahame Grieve (Jun 02 2017 at 02:59):
well, once 12071 builds
Brett Esler (Jun 25 2019 at 09:27):
@Grahame Grieve would you have any advice for AU Base publishing - we are looking at two CI builds one for STU3 and one for R4 both of which would like to have available to build against. Currently have a branch aubase2 where STU3 build lives and plan to port master to R4 but can not work out how to reference the aubase2 branch from other IGs
Brett Esler (Jun 25 2019 at 09:27):
do I need a whole new IG - is that easier?
Grahame Grieve (Jun 25 2019 at 10:57):
hmm. later this year I'll be upgrading the IGPublisher to handle this directly, but for now your options are two separate IGs or one single combined one a la davinca-crd. @Lloyd McKenzie can explain how that works
Brett Esler (Jun 25 2019 at 12:32):
Thanks @Grahame Grieve think i'll go for a separate IG as expect STU3 work will slow down when R4 version in place so not planning STU3 to be active forevermore
Last updated: Apr 12 2022 at 19:14 UTC
