FHIR Chat · Change to List.identifier cardinality with IG 1.0.1 fsh · Da Vinci PDex Drug Formulary

Stream: Da Vinci PDex Drug Formulary

Topic: Change to List.identifier cardinality with IG 1.0.1 fsh


view this post on Zulip Kate Dech (Mar 17 2021 at 15:57):

@Saul Kravitz

https://build.fhir.org/ig/HL7/davinci-pdex-formulary/branches/fsh-convert2/StructureDefinition-usdf-CoveragePlan.html

In the versions of the IG before this (https://build.fhir.org/ig/HL7/davinci-pdex-formulary/branches/STU1/), the List.identifier had a cardinality constraint of 1..1 (that is still reflected in the logical model diagrams on the home page of the IG). But in versions after this (including the current build - https://build.fhir.org/ig/HL7/davinci-pdex-formulary/StructureDefinition-usdf-CoveragePlan.html), within the actual structure definition, the cardinality follows the base resource - 0..*.

Was this an intentional change to allow more than one identifier on List?

If so, we may need to update the model diagrams included in the IG.
If not, is this something that can be considered to keep? (Given the different discussion threads about the plan ID to use, we actually prefer having the ability to include multiple business identifiers for a plan -- HIOS plus an internal pbm plan code, for example.)

The issue then comes down to how plan ID is referenced within FormularyDrug/MedicationKnowledge. That extension type is currently only a string so there can only be one value. (Has there been any consideration to changing the type to be identifier vs string?)
cc: @Bapi Behera

view this post on Zulip Lloyd McKenzie (Mar 17 2021 at 16:19):

In general, constraining max cardinality to be tighter than it is on the resource is something to avoid - you never want to prohibit systems from sending data that they have. Such constraints also make it difficult/impossible for implementations to comply with multiple IGs simultaneously. So, whether intentional or not, relaxing the constraint is a good thing.

view this post on Zulip Saul Kravitz (Mar 18 2021 at 13:58):

@Kate Dech -- the branch you are referring to, fsh-convert, is from 10/2020, and is not relevant.

The relevant branches are:

  • master (the CI build), and
  • v1.01 (the build for STU1.0.1)

In both of these, List.identifier is 0..*. In the STU1 the cardinality was 1..1, but that has apparently been relaxed.
We did lose the MS flag on identifier, which should be fixed. I'll add a tracker for that, and for updating the drawing. Thx.
@Dave Hill @Corey Spears

view this post on Zulip Saul Kravitz (Mar 18 2021 at 14:04):

https://jira.hl7.org/browse/FHIR-31572

view this post on Zulip Kate Dech (Mar 18 2021 at 18:32):

Thanks Saul!


Last updated: Apr 12 2022 at 19:14 UTC