FHIR Chat · Constraining path defined in another type · implementers

Stream: implementers

Topic: Constraining path defined in another type


view this post on Zulip Ivan Dubrov (Mar 13 2018 at 21:39):

Specification says that

StructureDefinitions with derivation = constraint (i.e. Resource and Data Type profiles) are not allowed to define or include ElementDefinitions with a path not defined within the base resource definition from which they derive (e.g. in the FHIR specification).

However, it is not clear, if StructureDefinition with derivation = constraint can place restrictions on elements defined in another type. For example, http://hl7.org/fhir/us/core/stu1/StructureDefinition-us-core-patient.json.html profile places restriction on "Patient.name.family" which is defined for "HumanName.family".

So, I assume the answer is "yes", it is allowed, but want to make sure.

view this post on Zulip Grahame Grieve (Mar 13 2018 at 21:42):

yes


Last updated: Apr 12 2022 at 19:14 UTC