FHIR Chat · ElementDefinition.conformanceLength · conformance

Stream: conformance

Topic: ElementDefinition.conformanceLength


view this post on Zulip Frank Oemig (Feb 14 2020 at 07:49):

Would it make sense to add an attribute conformanceLength to ElementDefinition as unsignedInteger that indicates, if given, the minimum length this element should support?

view this post on Zulip Lloyd McKenzie (Feb 14 2020 at 15:04):

It's not an issue we've encountered in FHIR implementations thus far. We do have maxLength element that serves the need.

view this post on Zulip Frank Oemig (Feb 14 2020 at 16:58):

But that are different concepts. If you define a maxLen and require that all must support exactly that length, fine. ConformanLen is guidance only.

view this post on Zulip Lloyd McKenzie (Feb 14 2020 at 17:10):

So far, no one has asked for it.

view this post on Zulip Grahame Grieve (Feb 15 2020 at 04:54):

the FHIR community has generally been much less invested in length of field than the v2 community. One of the interesting questions for me is whether that will change as the slower-to-change implementers come to the party.

view this post on Zulip Grahame Grieve (Feb 15 2020 at 04:55):

if field length starts to become important, then that might change. In the meantime, @Frank Oemig , we should define a standard extension for this - can you create a task for that?


Last updated: Apr 12 2022 at 19:14 UTC