Stream: conformance
Topic: Using a profiled data type in a profile of resource
François Macary (Aug 31 2017 at 09:42):
Continuation of discussion initiated by Isabelle Gibaud on the implementers stream.
@Michel Rutten
@Stefan Lang We have looked at address-de-basis and how this profile of data-type is used by the profile patient-de-basis on Simplifier.net :
https://simplifier.net/BasisprofilDE/patient-de-basis
https://simplifier.net/BasisprofilDE/address-de-basis
What we don't understand is that in the profile of Patient Patient.address references address-de-basis as profiled datatype, however the content of this address element does not show the changes brought by this profile (extensions on Address.line, and removal of Address.district).
And we have currently the same issue when trying to use a profiled datatype in a profile of resource , with Forge latest release. This seemed to work in July.
Is it an issue of Forge last release?
Stefan Lang (Aug 31 2017 at 10:38):
This is an issue of Simplifier. It always shows the elements of the base data type in a profile's tree view and you have to click on the custom data type to see the actual elements.
The profile itself is correct, so no Forge issue here. It's a display problem I too would like to see fixed in Simplifier.
Stefan Lang (Aug 31 2017 at 10:40):
At least definitely not an issue of Forge latest release; the profile and the data type have been last edited with Forge 16.4 iirc
François Macary (Aug 31 2017 at 11:41):
Thank you Stefan,
However, I also do not see the constraints of address-de-basis when opening patient-de-basis in Forge (see attached screenshot)patient-de-basis_screenshot_Forge.jpg
Mirjam Baltus (Aug 31 2017 at 11:46):
For Forge to show the constraints, the address-de-basis profile should be present in the same folder that contains the patient-de-basis profile, or in a subfolder if you have the "Resolve resources from subdirectories" option selected.
Michel Rutten (Aug 31 2017 at 11:50):
Hi @François Macary, as Mirjam explains, you should make sure that the profile parent folder also contains all the referenced external profiles (such as type profiles and extension definitions). I've checked and the latest release correctly expands the address datatype.
It seems that the uploaded profile version on Simplifier has an invalid snapshot. I suggest that you try to re-generate the full snapshot locally and then re-upload the corrected version to Simplifier.
François Macary (Aug 31 2017 at 12:01):
Thanks @Mirjam Baltus jam and @Michel Rutten ,
All my resource profiles are in the same folder. The erroneous snapshot seems a good clue. I have this error on snapshot generation:
patient-de-basis_snaphot_generation_error.jpg .
Michel Rutten (Aug 31 2017 at 12:40):
Apparently the snapshot generator cannot resolve the external profiles from the containing parent folder.
You need to include the profiles humanname-de-basis and address-de-basis.
François Macary (Aug 31 2017 at 13:33):
Thanks Michel, I had not downloaded all of them.
Michel Rutten (Aug 31 2017 at 13:37):
OK, that explains. Glad that the issue has been solved.
Last updated: Apr 12 2022 at 19:14 UTC
