FHIR Chat · Au Base Practitioner identifier slice anomaly? · australia

Stream: australia

Topic: Au Base Practitioner identifier slice anomaly?


view this post on Zulip Rob Eastwood (Sep 03 2019 at 06:07):

The HL7 AU R4 AU Base Practitioner Profile has a slice on identifier with the discriminators of pattern:type & value:system. And the slice for HPI-I mandates a system value with type as optional. This slice has 3 invariants constraining the format of the HPi-I value (ie starting with '800361' 16 digits and the Luhn check).

An example Practitioner-example0 demonstrates this slice with both type and system present (noting it includes a meta.profile value for this profile). The corresponding QA report has no corresponding errors or warnings for this example .

When the optional type node is omitted (with just a system and value), ie

<identifier>
    <system value="http://ns.electronichealth.net.au/id/hi/hpii/1.0"/>
    <value value="8003619900015717"/>
</identifier>

the locally built QA report now raises an information note of "This element does not match any known slice for the profile http://hl7.org.au/fhir/StructureDefinition/au-practitioner".

And if a clearly bogus HPI-I value is added that should fail against all 3 invariants, like "wrongHPI-I8003619900015717", then the QA report still just has the "does not match any known slice" notice. However, when the type node is re-added then the value invariants are violated.

Discussing this recently with @Grahame Grieve, it was felt that this behaviour is unexpected and that the invariants should fire in the absence of the type node.

Posting here is the hope that this can be addressed, by whatever means - one thought was to mandate typealthough Grahame indicated that this should not be needed. Please let me know if any other information is helpful.

NB: the local build was done on a cloned copy of the HL7 AU repository and built with today's IG publisher (v0.9.61)

Also note - the above 'picks on' Practitioner HPI-I slice but the same conditions exist for other identifier slices in this profile (CAE and Medicare Prescriber Number), as well as other profiles (AU Base Patient, AU Base HealthcareServiceAU Base RelatedPersonand AU Base RelatedPerson).

view this post on Zulip Rob Eastwood (Sep 03 2019 at 06:10):

Hi @Brett Esler - this is one we discussed at one of the recent PAWG meetings


Last updated: Apr 12 2022 at 19:14 UTC