Comment:

Related to above issue not being documented, FHIR publishing tools are not checking for cases where the cardinality in derived profiles are not allowed. This results in publishing invalid profiles where snapshot view has the invalid cardinality values.

If only 1 is specified (max=1), then derived profiles can't make it many. If this is the rule then it should be clearly documented and be enforced in the publish tools.

Examples:

profile: diagnosticorder-daf

DiagnosticOrder.encounter

base card: 0..1 => 0..*

profile: medicationadministration-daf

MedicationAdministration.dosage

base card: 0..1 => 0..*

The snapshot in diagnosticorder-daf shows the publisher tools allowing an invalid override to the base resource.

<snapshot>

<element>

<path value="DiagnosticOrder.encounter"/>

<min value="0"/>

<max value="*"/>

...

FHIR publishing tools are not validating profiles that break conformance to the base resources and are publishing artifacts that are not valid with respect to the spec.

Additional URLs: http://hl7.org/fhir/2015May/diagnosticorder-daf-dafdiagnosticorder.html http://hl7.org/fhir/2015Ma