Closed ziegm closed 1 year ago
Hello Michaela,
I'm really not an expert in slicing, but did you try with a different kind of discriminator like ?
<discriminator>
<type value="value"/>
<path value="system"/>
</discriminator>
<discriminator>
<type value="value"/>
<path value="code"/>
</discriminator>
Best regards, David
Dear David
Thanks for your input.
You can see from the example of the Patient.identifier that the discriminator should be pattern, because the identifier:LocalPid is built differently than the others.
Best regards, Michaela
Thanks for the explanation !
Just another supposition. LocalPid has cardinality 0..* But the pattern identifier is fix
This would mean that the system will not be able to distinguish between two LocalPid. You should somehow also include the system and the value or ?
Best regards, David
System and value are set to 1 for identifier:LocalPID, so you can distinguish between different LocalPID's according to system. The slice however identifies all localPID's together, thats intended.
The origin of this issue is that the html representation in the implementation guide is not correct, the snaphshot which is generated however is correct.
Hello,
just as information, I solved this duplicate on my side by doing as following:
For example line 199
<patternIdentifier>
<type>
<coding>
<system value="http://terminology.hl7.org/CodeSystem/v2-0203" />
<code value="MR" />
</coding>
</type>
</patternIdentifier>
And if you fix the "system" and the "code" in separated elements:
<element id="Patient.identifier:LocalPid.type.coding.system">
<path value="Patient.identifier.type.coding.system" />
<fixedUri value="http://terminology.hl7.org/CodeSystem/v2-0203"/>
</element>
<element id="Patient.identifier:LocalPid.type.coding.code">
<path value="Patient.identifier.type.coding.code" />
<fixedCode value="MR"/>
</element>
It should do the Trick, and nomore duplicate in the html the "system" part. I'm not sure that the signification is the same. But from the look and feel point of view it looks ok ;-)
Best regards, David
we need to use the patternIdentifier otherwise the slicing will not work with the different identifier usecases. can you validate with your setup all the examples?
You are right, after validating throw the examples I got some errors :-( Sorry for the disturbing.
Changes:
Telco vom 1.3: 12 - 0 - 0
In the following profiles, the sub-elements of the element identifier are displayed in duplicate in the snapshot table: https://fhir.ch/ig/ch-core/0.1.0/StructureDefinition-ch-core-organization.html https://fhir.ch/ig/ch-core/0.1.0/StructureDefinition-ch-core-patient.html https://fhir.ch/ig/ch-core/0.1.0/StructureDefinition-ch-core-composition-patient-epr.html
Applied slicing:
Applied pattern:
No duplicates are displayed without the following code element: