This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Harmonization: Description of AttentionLine

From HL7Wiki
Revision as of 14:53, 19 February 2006 by Rene spronk (talk | contribs) (new harmonization page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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): 20060219
Date submitted: Committee status: Discussed, not Approved yet
Submitted by: Rene Spronk  
NAME: description of AttentionLine  

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

Issue

The RIM Transmission::AttentionLine class has the following description (ballot Jan 2006): This class allows parameters for a technology specific transport to be represented in the V3 message outer wrapper. - This doesn't cover the way it is currently used, nor does it allow for a set of use-cases INM plans to support using this class.

Recommendation(s)

Change description of AttentionLine to: This class allows parameters related to the transmission to be represented in the V3 message outer wrapper. The contents of the class shall be solely used for transmission related purposes and not have any impact on the semantic interpretation of the contents of the transmission.

Rationale

  • The change is in line with current usage, which is to use the AttentionLine for "routing" purposes by e.g. including (duplicating from payload) the pateint.id in it.
  • The change is requested so the class can be used to convey (realm specific) meta-information related to the batch (a transmission) as a whole, as long as such content has no impact on the semantic interpretation of the contents of the Batch.
  • The INM TC is examining various use-cases related to batch transmissions. Some of the "universal" use-cases may result in new attributes in either the Transmission or the Batch class. For non-universal use-cases or for use-cases not yet covered by the MCCI domain the suggested recommendation offers a solution.

Recommended Action Items

  • Implement the proposed solution

Resolution