the Contract Id in OCHP is defined with the strong recommendation to use a leading "C" in the id suffix, but in the OCHPdirect Contract Id Pattern the "C" is mandatory. On the other hand the hyphens are mandatory in OCHP, but not valid in OCHPdirect.
I think for simpliciy it would be best to drop the additional ContractIdPattern and just use the ContractId definition having the "C" as a MUST. It is up to every implementation to make sure, that a contract id of "DE-ABC-C1234567" is equals to "deABCC1234567". As the optional hypens are defined to make things more human-readable, they should be allowed everywhere.
the Contract Id in OCHP is defined with the strong recommendation to use a leading "C" in the id suffix, but in the OCHPdirect Contract Id Pattern the "C" is mandatory. On the other hand the hyphens are mandatory in OCHP, but not valid in OCHPdirect. I think for simpliciy it would be best to drop the additional ContractIdPattern and just use the ContractId definition having the "C" as a MUST. It is up to every implementation to make sure, that a contract id of "DE-ABC-C1234567" is equals to "deABCC1234567". As the optional hypens are defined to make things more human-readable, they should be allowed everywhere.