FHIR Chat · Adding profile restrictions to DomainResource or Resource · implementers

Stream: implementers

Topic: Adding profile restrictions to DomainResource or Resource


view this post on Zulip Jonny Rylands (Mar 09 2016 at 12:16):

When profiling a resource (e.g. Patient), is it possible to restrict elements in the resources parents (e.g. DomainResource or Resource)?

Example, if creating a NhsPatient profile based on the Patient resource, could you add a slice to meta.profile and constrain the slice to be the URI of NhsPatient?

I note that Forge doesn't allow you to "see" the parent resource elements, but I don't know if this is just something not supported in it yet.

Many thanks.

view this post on Zulip Michel Rutten (Mar 09 2016 at 12:17):

Hi Jonny, yes FHIR allows constraints on elements inherited from Resource or DomainResource. However Forge currently does not yet display these elements. We are planning to implement support in a future release.

view this post on Zulip Jonny Rylands (Mar 09 2016 at 12:18):

Great, thanks.

view this post on Zulip Michel Rutten (Mar 09 2016 at 12:20):

BTW I am aware that the NHS needs this functionality. We'll try and prioritize this change.

view this post on Zulip David Hay (Mar 09 2016 at 17:21):

why is this useful? sounds like a recursive profile :) Is this for profiles on other profiles? (ie where there is a subset of UK patient??)

view this post on Zulip Richard Kavanagh (Mar 09 2016 at 17:50):

I'm not sure of Jonny's use case but we definitely have requirements in this area. In some places for example we may want to say "always state a profile"

view this post on Zulip Lloyd McKenzie (Mar 09 2016 at 18:45):

You want to be able to say "instances of this profile must explicitly declare conformance with this profile" or possibly "must declare conformance with one of the following other profiles" - it's a shortcut to "including" other profiles.

view this post on Zulip Michel Rutten (Mar 10 2016 at 13:29):

@Jonny, coincidentally I managed to implement support in Forge for editing profile restrictions on common resource elements inherited from DomainResource and/or Resource (id, meta, implicitRules, language, text). This behavior is disabled by default and controlled by a new configuration setting in the Options menu ("Expand Common Elements"). If you toggle this setting the application requires a restart. You can download the new release from http://fhir.furore.com/forge. Please let me know if you have any questions or comments.

view this post on Zulip Jonny Rylands (Mar 10 2016 at 14:06):

Superb! I will check it out now.


Last updated: Apr 12 2022 at 19:14 UTC