Difference between revisions of "Harmonization: add QuerySpec.responseTemplateId attribute"
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 35: | Line 35: | ||
== Issue == | == Issue == | ||
| − | + | INM has accepted a motion to state that "The ParameterItem class cannot be used to constrain scope by columns". This proposal seeks to introduce a new query class to convey information related to the selection of columns. | |
| + | |||
| + | To use an analogy: if a v3 query by parameter query is expressed as a "SELECT x,y FROM <server database> WHERE a=1 AND b=2", then the use of ParamaterItem is limited to a and b. We need to introduce a new class for x and y ("the columns"). | ||
== Recommendation(s) == | == Recommendation(s) == | ||
| − | |||
| Line 45: | Line 46: | ||
=== Vocabulary Recommendation(s) === | === Vocabulary Recommendation(s) === | ||
| − | |||
== Rationale == | == Rationale == | ||
''Any additional information needed to understand, evaluate or implement the recommendation, such as model fragments or other context that demonstrates use of the requested change. Include implications.'' | ''Any additional information needed to understand, evaluate or implement the recommendation, such as model fragments or other context that demonstrates use of the requested change. Include implications.'' | ||
| − | *See the "[[Nature of ParameterItem]]" HL7 Wiki page for details of the discussion. | + | *See the "[[Nature of ParameterItem]]" HL7 Wiki page for details of the discussion around the use of ParameterItem. |
== Recommended Action Items == | == Recommended Action Items == | ||
Revision as of 14:52, 10 October 2006
This page documents an INM Workitem, i.e. an issue within scope of the INM Committee that either is still being discussed, or the resolution of which has not yet been included in an INM ballot.
Editing of harmonization 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: |
| Sponsored by: INM | Approval date by committee: See Nature of ParameterItem . |
| Revision (# and date): 20061010 | Date submitted: |
| Editor/Author: Rene Spronk | |
| PROPOSALNAME: create new Scope related parameter class |
Contents
Stewards Position
| TC | RECOMMENDATION APPROVAL STATUS | AFFECTED ENTITIES OF INTEREST TO TC (responsibility level: S=Steward; I=Interested) |
| INM | Reviewed | S |
Issue
INM has accepted a motion to state that "The ParameterItem class cannot be used to constrain scope by columns". This proposal seeks to introduce a new query class to convey information related to the selection of columns.
To use an analogy: if a v3 query by parameter query is expressed as a "SELECT x,y FROM <server database> WHERE a=1 AND b=2", then the use of ParamaterItem is limited to a and b. We need to introduce a new class for x and y ("the columns").
Recommendation(s)
RIM Recommendation(s)
Vocabulary Recommendation(s)
Rationale
Any additional information needed to understand, evaluate or implement the recommendation, such as model fragments or other context that demonstrates use of the requested change. Include implications.
- See the "Nature of ParameterItem" HL7 Wiki page for details of the discussion around the use of ParameterItem.
Recommended Action Items
- Implement the proposed solution
Discussion
Resolution
NOTE: This template puts this proposal in the "Harmonization Proposal" Wiki Category. Once the proposal has been discussed and the resolution has been aded, please update the Category statement to put the proposal in the "Discussed Harmonization Proposal". The "Harmonization Proposal" Wiki Category is for OPEN non-discussed proposals only.
