Stream: tooling
Topic: Forge - can't profile careplan?
Jose Costa Teixeira (Sep 23 2019 at 15:31):
Hi. Is it only me that cannot create a profile from CarePlan?
Ward Weistra (Sep 24 2019 at 07:54):
Hi Jose! In Forge STU3 22.0 I indeed get:
[Severity: Error] [Code: Invalid] http://hl7.org/fhir/StructureDefinition/SimpleQuantity (Element Quantity has an invalid non-empty sliceName 'SimpleQuantity'. Root element definitions cannot introduce slice names.)
In Forge R4 22.1 I can create the profile without problems. Is this the same you're seeing?
Jose Costa Teixeira (Sep 24 2019 at 11:46):
No, I'm seeing something different.
Jose Costa Teixeira (Sep 24 2019 at 11:46):
Actually my issue is cool: I can create a profile of careplan without issues, UNLESS i have in my resource folder a logical model for care plan.
Jose Costa Teixeira (Sep 24 2019 at 11:47):
so, the moment I delete my careplan logical model from the folder and clicked Refresh on Forge, it works again.
Jose Costa Teixeira (Sep 24 2019 at 11:47):
That is strange, but I guess it is due to some lookup behaviour....
Ward Weistra (Sep 24 2019 at 16:04):
Interesting, which version of Forge is this (eg. in title bar)?
Michel Rutten (Sep 25 2019 at 13:43):
logical model for care plan.
Could you share this model?
Jose Costa Teixeira (Sep 25 2019 at 20:56):
I have R22.1 Atlanta
Jose Costa Teixeira (Sep 25 2019 at 20:56):
and I found out the cause for the issue.
Jose Costa Teixeira (Sep 25 2019 at 20:57):
Since my logical model was made from changing the CarePlan structureDefinition.kind to "logical", i only changed the elements and forgot to change the url
Jose Costa Teixeira (Sep 25 2019 at 20:58):
so i had a logical model whose url was still
<url value="http://hl7.org/fhir/StructureDefinition/CarePlan" />
Jose Costa Teixeira (Sep 25 2019 at 20:58):
when this is there, i can not create a profile on care plan.
Jose Costa Teixeira (Sep 25 2019 at 21:00):
Not sure if this is something you prefer to change, or if I should have just informed myself better.
In my opinion, it is not a straight reasoning to figure out what happened, and the error message does not lead me to the right action.
Michel Rutten (Sep 26 2019 at 09:20):
Ah, that explains! Profiles are resolved via the canonical url. So invalid match usually indicates an url conflict. Maybe we could add some additional validation logic to the SnapshotGenerator to verify the actually resolved profiles and e.g. generate a warning if the resolver returns a logical model when that isn't expected/valid.
Last updated: Apr 12 2022 at 19:14 UTC
