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 |
Contents
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 | Under review | 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)
- (preferential) Add a new Transmission.profileId LIST<II> [0..*] attribute to the RIM, and deprecate the Message.profileId attribute.
- (alternative, in case #1 has backwards compatibility issues associated with it) Add a new Batch.profileId LIST<II> [0..*] attribute to the RIM.
Rationale
- Conformance profiles exist for Batches as well as for Messages
- 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
