At the moment, all the attributes of DV_IDENTIFIER are mandatory. In health care none of the features other thant the ID are used at present - at least in HL7 v2. Although we could use empty strings, the problem is that people doing transforms feel they have to debate what to put into each. Making them optional is a much more suitable response and would provide backward compatibility. It will mean we need to have a way of saying that a feature is mandatory in the archetype.
I find these mandatory fields unneeded - and filling with empty strings not nice at all - doesn't quite satisfy 'mandatory' in my opinion.
So +1 for making them non-mandatory.
+1 one for making them non-mandatory
Any particular reason we cannot adopt URI? Probably will make it easy to interoperate with modern web apps etc.
Whenever you specify a URI, you are just specifying a parseable String. Then you have to specify the parse rules and implied structure, so we are back to the same place. With the structured representation, no parsing is required. But the main point is that DV_IDENTIFIER is commonly used, and it would be a breaking change to start using DV_URI (+ parse / format rules) instead.
It's not that such a thing could never be done in the future, but I think this PR is just about making DV_IDENTIFIER work properly.