Stream: implementers
Topic: Create profile of DomainResource
John Grimes (Jan 24 2019 at 00:08):
Is it possible to create a profile of DomainResource using Forge, i.e. a custom FHIR resource that does not inherit from any existing resource definitions?
DomainResource is not present on the Create new Resource profile screen. I tried to use Derived profile option, using the DomainResource StructureDefinition within the "definitions.json" pack, but it doesn't seem to load the base profile. No error message is displayed.
Lloyd McKenzie (Jan 24 2019 at 01:52):
No, that's not possible. However, you can profile Basic.
Lloyd McKenzie (Jan 24 2019 at 01:53):
(Basic is the intended resource to use when creating 'custom' resources.)
John Grimes (Jan 24 2019 at 04:26):
Ok, thanks, I didn't know about Basic.
Michel Rutten (Jan 24 2019 at 09:37):
Forge explicitly prohibits you from creating profiles on core types Resource, DomainResource, Extension, ElementDefinition and BackboneElement. In theory, the application could allow and support this scenario. However FHIR explicitly disallows this and most systems (including our own Firely tools) will not be capable of handling them.
Lloyd McKenzie (Jan 24 2019 at 15:43):
Technically, Forge does allow creating profiles on Extension - it just uses a different interface for doing so to make sure the rules are followed. (A profile on Extension is just an extension definition)
Michel Rutten (Jan 24 2019 at 15:48):
Of course - thanks for clarification Lloyd
Last updated: Apr 12 2022 at 19:14 UTC
