Case sensitivity in request and response validations too strict

1. CPI and HPD requests demand ou=, dn= and faile OU=, DN=
EPD largely case insensitive and accepts requests with Ou= for example. On response sends OU= and DC=
2. CPI too restrictive - insists on DC=CPI, OU=CHCommunity but DC=CPI is also acceptable because it has only one OU child
3. HPD address attribute checking assume case sensitivity - but EPD case insensitive, so status=primary is also acceptable, not just status=Primary etc.
4. HPD hcIdentifier, hcspecialisation, hcprofession also assume case sensitivity, but EPD implementation is case insensitive
e.g. acceptable values include bAg:2.16.840.1.113883.6.96:36682004,
RefData:GLN:7601000502247:inaCTive, RefData:OID:2.16.10.89.201:inActive

5. validation binary fields always seems to fail
a) genuine binary data encoded
b) text data encoded