FHIR Chat · ElementDefinition.type.targetProfile Uniqueness · conformance

Stream: conformance

Topic: ElementDefinition.type.targetProfile Uniqueness


view this post on Zulip Gino Canessa (Mar 04 2020 at 21:47):

Spelunking through resources as I'm processing, I ran across Media, which has Media.device as a Reference to a Device, DeviceMetric, or Device.

Is it valid to have the same profile listed twice? If so, why? If not, I'll file a Jira issue for media (and any others I run into), and should the build process check for this?

view this post on Zulip Grahame Grieve (Mar 04 2020 at 22:53):

it's not valid.

view this post on Zulip Lloyd McKenzie (Mar 04 2020 at 23:08):

So yes, please submit an issue for the tooling to check

view this post on Zulip Gino Canessa (Mar 05 2020 at 15:44):

Thanks, created FHIR#26454 .

view this post on Zulip Eric Haas (Mar 05 2020 at 17:00):

Media gone R5+

view this post on Zulip Gino Canessa (Mar 05 2020 at 17:04):

Yep, issue is that the uniqueness should be validated generally to prevent downstream issues (e.g., adding duplicate keys, etc.).

view this post on Zulip Eric Haas (Mar 05 2020 at 17:07):

Yeah ....DeviceComponent was Merged into Device and somehow 'DeviceComponent' got changed to 'Device' instead of being removed.


Last updated: Apr 12 2022 at 19:14 UTC