Harmonization: enable Batch.profileId attribute

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): 20060305
Date submitted:	Committee status: Approved
Submitted by: Rene Spronk
NAME: Enable Batch.profileId attribute

Stewards Position

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)
INM	Approved	S
Conformance SIG	No objections	I

Issue

The Message class contains a profileId attribute which can be used to identify the conformamce profiles a Message (i.e. an interaction with a Message-class entry point) conforms to. New interactions with a Batch-class entry point have been added to the ballot material. It is however not possible at this point in time to use the Batch.profileId attribute since it doesn't exist in the RIM. This proposal seeks to add the attribute.

Recommendation(s)

1. (preferential) Add a new Transmission.profileId LIST<II> [0..*] attribute to the RIM, and deprecate the Message.profileId attribute.
2. (alternative, in case #1 has backwards compatibility issues associated with it) Add a new Batch.profileId LIST<II> [0..*] attribute to the RIM.

Rationale

1. Conformance profiles exist for Batches as well as for Messages
2. Recommendation #1 is preferential because it defines the attribute only once, leading to a high degree of consistency.

Recommended Action Items

• Implement the proposed solution

Resolution

20060718 Harmonization.

Lloyd no back w compatib issues here, sort order doesn't change. Instance backw compat is not part of nackw comp, only semabtic backw comp is of importance. versionCode identifies RIM version. Rules have been clarified. Happy with "preferred" option. Message.profileId wont be deprecated (wrong terminology) but it will be promoted.

Reword recommendation: Promote Message.profileId to be Transmission.profileId. (Alternate recommendation can be removed).

Motion approved: 9-0-1