The must support description for implantable devices states:

 'Each Device must support ... A Unique Device Identifier (UDI) numeric or alphanumeric code ...either as the Human Readable Form (HRF) string representation of the barcode ...or the Automatic Identification and Data Capture (AIDC) representation.'

 If it is ok for a US Core responder to only support one representation (and never support sending the other), as this seems to state, then the must-support flags need to be updated to reflect this intent.  Right now, both udiCarrier.carrierAIDC and udiCarrier.carrierHRF have must-support flags on them.  Which formally means that the US Core responder must support sending both (though only one representation needs to be sent in any given resource).

Assuming that the requirement is support for at least one of the two representations system-wide, consider removing the must-support flags on both udiCarrier.carrierAIDC and udiCarrier.carrierHRF.  There is already a must-support flag on udiCarrier, and an invariant that states that either carrierAIDC or carrierHRF must be present when udiCarrier is present (us-core-12), which combined is sufficient to ensure that a system supports udiCarrier and at least one of the two representations.

Alternatively, if the requirement is really for US Core responders to support both representations, then the must support narrative should be updated to be more clear that the system must support both, but a given resource with UDI information only needs one or the other.