Stream: conformance
Topic: Forge complex extensions
Jonny Rylands (Aug 29 2016 at 09:56):
@Michel Rutten Hi Michel, I'm trying to create a complex extension in Forge with two elements, 'consentGiven' which is a boolean and 'expressedDate' which is a dateTime.
Forge allows me to add two new elements using the 'Add' button and name and type them accordingly.
However when saving and re-loading the extension, I get the following errors:
MyExtension / consentGiven / Type(s) This element has no type. Select at least one type.
MyExtension / expressedDate / Type(s) This element has no type. Select at least one type.
The consentGiven and expressedDate elements do not have a type selector pane (as the type selector is against the child valueBoolean / valueDateTime elements).
Do you know if there is something I am doing wrong?
Many thanks.
Michel Rutten (Aug 29 2016 at 10:02):
Hi @Jonny Rylands this is a bug. You can safely ignore the warning message. This issue will be solved in the next release.
Jonny Rylands (Aug 29 2016 at 13:35):
@Michel Rutten Thanks
Grahame Grieve (Aug 30 2016 at 04:14):
this page: https://simplifier.net/fhir-au/au-patient, the xml view... the xml is not properly escaped, and has no namespace
Grahame Grieve (Aug 30 2016 at 04:15):
(" are not properly escaped in attributes)
Martijn Harthoorn (Aug 31 2016 at 12:00):
The xml view was designed for 'quick' readability. That's why it's also is without the Narrative. If you want the correct 'pure' xml, you can download the resource or fetch it from the FHIR endpoint. But there is debate in our team wether we should go for 'readability' or wire-format in the view.
Last updated: Apr 12 2022 at 19:14 UTC
