Stream: implementers
Topic: Forge 18.6 validation errors when deriving profiles
Uday Chandrupatla (May 22 2018 at 01:02):
When deriving PractitionerRole profile for HL7 AU, forge gives following errors when below changes are performed on the profile -
- identifier is made (1..*), added Must Support flag
- identifier slice (careAgencyEmployeeIdentifier) made 1..1, added Must support flag
Message : Duplicate slice name: 'careAgencyEmployeeIdentifier'. All slice names within a common slice group must be distinct.
Severity: Warning
Source : Elements
Context : PractitionerRoleCAE / identifier / careAgencyEmployeeIdentifier / Slice name
Message : Duplicate slice name: 'careAgencyEmployeeIdentifier'. All slice names within a common slice group must be distinct.
Severity: Warning
Source : Elements
Context : PractitionerRoleCAE / identifier / careAgencyEmployeeIdentifier / Slice name
Attached are the screenshot of the errors and PractitionerRoleCAE StructureDefinition. CAEI_ScreenShot.pdf practitionerrole-cae.xml
Lloyd McKenzie (May 22 2018 at 03:05):
Ok. The message seems pretty clear to me - and the screenshot clearly shows that you have duplicate slice names. If you rename the second slice, that should fix the problem...
Uday Chandrupatla (May 22 2018 at 03:41):
Thanks @Lloyd McKenzie we do not need the second slice, instead i want to edit the existing slice with below changes -
- identifier is made (1..*), added Must Support flag
- identifier slice (careAgencyEmployeeIdentifier) made 1..1, added Must support flag
The second slice appears with the same name when the first slice is edited. The PractitionedRole-au profile contains only one slice for CAEI. au-practitionerrole.xml
Uday Chandrupatla (May 24 2018 at 22:52):
@Michel Rutten, could i ask you, did you come across this error with Forge 18.6?
Michel Rutten (May 28 2018 at 11:06):
Hi @Uday Chandrupatla, thank you for reporting this issue. I've took a couple of days off after the WGM. This week I'm going to try and fix all issues reported by the community. I will also investigate this issue. I am planning to publish a hotfix by the end of the week, time permitting.
Michel Rutten (Jun 06 2018 at 14:00):
Hi @Uday Chandrupatla, this turned out to be a bug in snapshot generator from the FHIR .NET API library. We have solved the issue in the API and published a new 0.96.0 release package on NuGet. We have also updated Forge to the new library version. I'm planning to publish a Forge update this week.
Uday Chandrupatla (Jun 06 2018 at 22:21):
Thanks @Michel Rutten looking forward to test the new Forge build.
Last updated: Apr 12 2022 at 19:14 UTC
