CDA-20031 us realm date fields

[benjaminflessner]

This started from https://jira.hl7.org/browse/CDA-20031, but I quickly discovered that almost every use of "US Realm Date and Time (either flavor) had invalid schematron. It either:

• Didn't test anything (so the required existence of the field was not tested)
• Incorrectly required @value to be longer than 8 (this is unnecessary, since every US Realm Date and Time already has its own check.

Part of the problem is that when you apply a US Realm Date and Time template onto an effectiveTime element, the auto-generated Trifolia export tries to require effectiveTime/templateId which doesn't exist; so each of these places needs custom schematron... and it was often done incorrectly.

Now this is caught in the following places:

• US Realm Header:
  • effectiveTime (yes, this was never validated)
  • author/time (never validated for existence)
  • legalAuthenticator/time (never validated for existence)
• Progress Note / Op Note:
  • documentationOf/serviceEvent/effectiveTime (removed @value requirement)
• Progress Note / Consult Note / H&P Note:
  • componentOf/encompassingEncounter (removed @value requirement)

[mjszczep]

Looks good to me!