Stream: implementers
Topic: Forge Extension Resolve Error
Joel Francis (Mar 21 2018 at 12:26):
Hi,
I created an extension for the Patient.address.line elelment as follows and added 6 extensions from the Extension Registry (https://www.hl7.org/fhir/extensibility-registry.html)
After saving my work, when I re-open up the Forge editor, I get a resolution error. I noticed that the status of these extensions is “Draft”. Could this be a reason why this is happening?
Any advice on how to resolve this is appreciated. Note: All work done using Forge 18.2.1
Thanks,
Joel
Resolve_error.png Extension_Forge.png
Lloyd McKenzie (Mar 21 2018 at 14:33):
It's not a status issue. Looks like Forge is having trouble finding extensions from the international spec. @Michel Rutten ?
Lilian Minne (Mar 22 2018 at 08:15):
Forge is indeed having trouble finding the extensions. Forge is looking for them in your working directory. The only way to get rid of these errors at the moment is placing everything you need in your working directory, but this is of course not an ideal solution. Michel is planning to work on a solution in the future, but for now it is safe to ignore these errors. You can still edit your profiles without breaking anything.
Joel Francis (Mar 22 2018 at 14:01):
Forge is indeed having trouble finding the extensions. Forge is looking for them in your working directory. The only way to get rid of these errors at the moment is placing everything you need in your working directory, but this is of course not an ideal solution. Michel is planning to work on a solution in the future, but for now it is safe to ignore these errors. You can still edit your profiles without breaking anything.
Thanks @Lilian Minne and @Lloyd McKenzie
Michel Rutten (Mar 26 2018 at 11:52):
Hi @Joel Francis, indeed as my colleague @Lilian Minne explains, Forge needs access to all the referenced (external) profiles in order to fully expand the snapshot. Specifically, Forge tries to resolve all dependencies from the same folder structure as the referencing profile. I suggest that you download all the referenced extension definitions and save them to the same target folder as the referencing profile. Now, if you load your profile, Forge should automatically resolve all extensions.
Joel Francis (Mar 26 2018 at 17:30):
Hi @Joel Francis, indeed as my colleague @Lilian Minne explains, Forge needs access to all the referenced (external) profiles in order to fully expand the snapshot. Specifically, Forge tries to resolve all dependencies from the same folder structure as the referencing profile. I suggest that you download all the referenced extension definitions and save them to the same target folder as the referencing profile. Now, if you load your profile, Forge should automatically resolve all extensions.
Thanks @Michel Rutten
Last updated: Apr 12 2022 at 19:14 UTC
