Relationship Cardinality between SelectionExpression and QueryBySelection

Editing of harmonisation proposals prior to a harmonization meeting is restricted to the proposal submitter and the co-chairs of the steward comittee. Other changes will be undone. Please add comments to the "discussion" page associated with this proposal.

Recommendation for HL7 RIM Change	RECOMMENDATION ID:
Submitted by: INM	Revision (# and date): 20060614
Date submitted:	Committee status: under review
Submitted by: Grahame Grieve
NAME: Change Cardinality of Relationship between SelectionExpression and QueryBySelection

Stewards Position

TC	RECOMMENDATION APPROVAL STATUS	AFFECTED ENTITIES OF INTEREST TO TC (responsibility level: S=Steward; I=Interested)
INM	Slated for approval on 20060619	S

Issue

The current cardinality of the relationship between SelectionExpression and QueryBySelection is 1..1. This is a problem because SelectionExpression is the generalisation class for LogicalExpression and RelationalExpression, which form their own tree. By the existing model, each of the nodes in this tree must have a QueryBySelection relationship, and this is clearly not what is intended.

Recommendation(s)

Change the cardinality to 0..1.

Rationale

• There is no way to implement this legally as it stands
• The tooling implements the rule

Recommended Action Items

• Change the cardinality in the RIM

Resolution

20060718 Harmonization meeting: approved.