Stream: conformance
Topic: Multiple Slice Groups?
Brian Postlethwaite (Mar 21 2018 at 09:33):
I've been re-reading the profiling page, and specifically
https://www.hl7.org/fhir/profiling.html#discriminator
In this section it talks about a "slice group" which has the initiator, and slices.
Does this mean that we can put in multiple slice groups, just by adding in another initiator and slices for it.
(Is that what the "open" part is in the discriminator)
I know you definitely cant do this with Forge.
Brian Postlethwaite (Mar 21 2018 at 09:45):
What I'm looking to do is describe a profile that can accurately describe this sequence of identifiers as valid:
<!-- National Identifier, has a strictly defined identifier.system value -->
<!-- (This is essentially a complete instance, only the value can change) -->
<identifier>
<type>
<coding>
<system value="http://hl7.org/fhir/v2/0203" />
<code value="NPI" />
</coding>
</type>
<system value="http://ns.electronichealth.net.au/id/hi/hpii/1.0" />
<value value="8003610833334086" />
</identifier>
<!-- Vendor Identifier, Identified by the identifier.type (system is required, but will be different for each vendor) -->
<!-- These are only required for Secure Messaging Vendors in directories, so in a different profile to the above identifier -->
<identifier>
<type>
<coding>
<system value="http://hl7.org.au/fhir/v2/0203" />
<code value="VDI" />
<display value="Vendor Directory Identifier" />
</coding>
</type>
<system value="http://telstrahealth.com/fhir/NameSystem/Argus" />
<value value="123456AB" />
<assigner> <!-- The assigner is required for the Vendor identifiers -->
<display value="Telstra Health"/>
</assigner>
</identifier>
<!-- This is some other identifier that won't match either of the above identifiers -->
<identifier>
<system value="http://example.org/meaning-of-life" />
<value value="42" />
</identifier>
Brian Postlethwaite (Mar 21 2018 at 09:45):
@Brett Esler
Grahame Grieve (Mar 21 2018 at 11:16):
no you can't have multiple kinds of slicing for a path
Grahame Grieve (Mar 21 2018 at 11:17):
aren't you just slicing by system there?
Brian Postlethwaite (Mar 21 2018 at 11:20):
The vendor identifier system can be anything, it is identified by the type.
Don't want to define those, as prevents new additions
Grahame Grieve (Mar 21 2018 at 11:34):
so combo of type and system is unique then?
Brian Postlethwaite (Mar 21 2018 at 19:10):
yes, but does that work for the one that has no value for the type?
and which order would it be in? (or doesn't that matter)
Grahame Grieve (Mar 21 2018 at 19:46):
there could only be one without either - they have to be distinct.
Brian Postlethwaite (Mar 21 2018 at 19:57):
My issue here is that the HPI only needs the system to be identified, and the vendor identifier needs the type
And no way to represent this.
At the AU Base level, really just want to slice by system (as doens't have the vendor identifiers)
and then at the AU PD level slice by type
To do this will mean that can't derive the profile, but state that needs to conform to both
Brian Postlethwaite (Mar 21 2018 at 19:59):
(I guess this is re-slicing, but don't have a named slice to put it on, and the open slice applies to all if i'm reading it right)
Brian Postlethwaite (Mar 22 2018 at 05:22):
May have found a bug in the .net Validator
If the identifier slice is by value:system and value:type and I have an identifier that doesn't have a type value, then it shouldn't match a the slice right? It shouldn't mean that all identifiers have to have a type value?
Brian Postlethwaite (Mar 22 2018 at 05:37):
I've come to the conclusion after trawling over this for too long, that you can't define a single profile that can define the above requirements.
Grahame Grieve (Mar 22 2018 at 05:55):
it should match the slice if the slice specifies no identifier type
Last updated: Apr 12 2022 at 19:14 UTC
