Should each mCODE data instance identify itself as conforming to a specific mCODE profile? It would be helpful to have an instance declare what it is in meta.profile, if instead of having the receiver try to guess or infer that that data represents a PrimaryCancerCondition or StagingData. The data might have clues, but this is far from a proclaming the intent to conform to a profile. My specific suggestion is that the profile URI becomes a fixed value in the meta.profile array, and therefore that array become 1..* instead of 0..*.