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): XXXX|
|Date submitted:||Committee status: Proposed to INM|
|Submitted by: Grahame Grieve|
|NAME: Change Cardinality of Relationship between SelectionExpression and QueryBySelection|
REQUIRED - This table should contain one row for each Steward Committee affected by the recommendation.
|TC||RECOMMENDATION APPROVAL STATUS||AFFECTED ENTITIES OF INTEREST TO TC |
(responsibility level: S=Steward; I=Interested)
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.
Change the cardinality to 0..1.
- 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