Currently, the statements are:

• Avoid constraining ‘max’
  • It’s better to slice and set constraints that let you extract the specific repetition(s) you need than to prevent others from sending the data they have
  • If you constrain max, it means you’re forcing implementations to create a custom implementation interface that just strips data out that could be ignored for free

This does not adequately reflect the severity of the issues that can occur when data is not shared accordingly. Patient harm is easy to impart when seeming unrelated information is not available to reference.

Suggest adding:

• Patient harm can occur if information is blocked at the source. For example, recent travel information may be irrelevant in many cases, until there is an outbreak of Ebola in a certain region, when it suddenly becomes a vital piece of information. Prohibiting the inclusion of recent travel information in that case will not allow a system or a person to adjust their business rules to reflect changed circumstances.