Comment:

Suggest re-reviewing whether structures with Element data types should be Resources or Data Types. Rule of thumb could be that if it is likely to be used in more than one resource, it should be a Resource. E.g., Patient.contact – why is this an Element, when Patient.address is a Data Type? Couldn't Patient.contact be generalized when used in other settings, like for a Provider (e.g., escalation needed for sending alerts, etc.)? Also, profiling such structures requires profiling the entire containing Resource, which seems suboptimal.