Difference between revisions of "Harmonization: add priorTransmission to support Transmission Sequencing"
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
Line 1: | Line 1: | ||
− | |||
{|width=100% cellspacing=0 cellpadding=2 border=1 | {|width=100% cellspacing=0 cellpadding=2 border=1 | ||
|- | |- | ||
Line 41: | Line 40: | ||
[[Image:Transmission_rel.bmp|250px|right|thumb|Proposed new RIM class]] | [[Image:Transmission_rel.bmp|250px|right|thumb|Proposed new RIM class]] | ||
+ | See image on right: | ||
+ | *Add a new TransmissionRelationship class to the RIM, with 2 relationships with the Transmission RIM class. A Transmission (entry point) has 0..n TransmissionRelationships, each of those transmissionRelationships is related to 1..n Transmissions. | ||
+ | **Effectively what this tries to accomplish is shown in the top half of the image, if Transmission were an Act. | ||
+ | *The TransmissionRelationship class has 1 attribute: typeCode (description: xxxx), with values taken from the TransmissionRelationshipTypeCode vocabulary (description: xxx). The initial value for the vocabulary is SEQL (description: xxxx). | ||
=== RIM Recommendation(s) === | === RIM Recommendation(s) === | ||
− | + | *Add a new TransmissionRelationship class with a typeCode attribute as described above. | |
=== Vocabulary Recommendation(s) === | === Vocabulary Recommendation(s) === | ||
− | + | *Add a new TransmissionRelationshipTypeCode vocabulary with 1 value: SEQL and descriptions as shown above. | |
== Rationale == | == Rationale == |
Revision as of 09:03, 10 October 2006
Recommendation for HL7 RIM Change | RECOMMENDATION ID: |
Sponsored by: INM | Approval date by committee: see Sequence Number Protocol. |
Revision (# and date): 20061010 | Date submitted: |
Editor/Author: Rene Spronk | |
PROPOSALNAME: add priorTransmission to support Transmission Sequencing |
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 | Reviewed | S |
Issue
Use of the Sequence Number Protocol requires that all interactions have an immediate response interaction. The Sequence Number Protocol therefore forces the sender to request accept acknowledgements for some interactions, but not in others. In order to separate the use of accept Acks from the use of a sequencing mechanism INM has decided to drop the sequence number protocol from the v3 standard.
In order to provide a sequencing mechanism, this proposal seeks to add a new "blue class" to the RIM that allows the identification of the "prior transmission". If one has the ability to identify a Transmission and its preceding Transmission, then we have a new sequencing mechanism that doesn't rely on accept acknowledgements.
Recommendation(s)
See image on right:
- Add a new TransmissionRelationship class to the RIM, with 2 relationships with the Transmission RIM class. A Transmission (entry point) has 0..n TransmissionRelationships, each of those transmissionRelationships is related to 1..n Transmissions.
- Effectively what this tries to accomplish is shown in the top half of the image, if Transmission were an Act.
- The TransmissionRelationship class has 1 attribute: typeCode (description: xxxx), with values taken from the TransmissionRelationshipTypeCode vocabulary (description: xxx). The initial value for the vocabulary is SEQL (description: xxxx).
RIM Recommendation(s)
- Add a new TransmissionRelationship class with a typeCode attribute as described above.
Vocabulary Recommendation(s)
- Add a new TransmissionRelationshipTypeCode vocabulary with 1 value: SEQL and descriptions as shown above.
Rationale
Recommended Action Items
- Implement the proposed solution