: Public Class
Created: 1/16/2007 4:53:18 PM
Modified: 2/23/2012 3:58:14 PM
Project:
Advanced:
DEFINITION:<br /></p><p>Specifies the meaning (or semantics) of the relationship between one document version and another.<br /></p><p><br /></p><p>EXAMPLE(S):<br /></p><p>decomposition (component), pre-condition, post-condition, sequel (replaces, modifies), attribution (cause and effect)<br /></p><p><br /></p><p>In a Regulated Product Submission (RPS), support of versioning can be accomplished by having two different revisions of a document related to each other through a "replaces" relationship.  Another example is version 3 of a breast cancer protocol "uses" version 2 of a consent form.<br /></p><p><br /></p><p>NOTE(S):<br /></p><p>The DocumentVersions on either side of the DocumentVersionRelationship do not necessarily have to be related to the same Document, or even have the same Document.typeCode.<br /></p>
Attribute
Public CD
  typeCode
Details:
Map:AE=SafetyReport.amendmentReportInd
Map:CTRPv3.8=StudyRelationship.typeCode
Map:CTRv1.0=DocumentVersionRelationship.typeCode
Map:FDA HL7 SD SD DSTU2012=outboundRelationship.typeCode
Map:ICSRr2=SourceOf1.typeCode (in IndividualCaseSafetyReport)
Map:ICSRr2=SourceOf2.typeCode (in IndividualCaseSafetyReport)
Map:LSDAM=DocumentVersionRelationship.typeCode
Map:RPS1=RelatedDocumentation.relationship
Notes: DEFINITION:#lt;br /#gt;#lt;/p#gt;#lt;p#gt;A coded value specifying the kind of document version relationship. Each value implies specific constraints to what kinds of objects can be related and in which way.#lt;br /#gt;#lt;/p#gt;#lt;p#gt;#lt;br /#gt;#lt;/p#gt;#lt;p#gt;EXAMPLE(S):#lt;br /#gt;#lt;/p#gt;#lt;p#gt;decomposition (component), pre-condition, post-condition, sequel (replaces, modifies), attribution (cause and effect)#lt;br /#gt;#lt;/p#gt;#lt;p#gt;#lt;br /#gt;#lt;/p#gt;#lt;p#gt;OTHER NAME(S):#lt;br /#gt;#lt;/p#gt;#lt;p#gt;#lt;br /#gt;#lt;/p#gt;#lt;p#gt;NOTE(S):#lt;br /#gt;#lt;/p#gt;#lt;p#gt;This is HL7 structured vocabulary and is part of a controlled vocabulary set.#lt;br /#gt;#lt;/p#gt;
Public REAL
  priorityNumber
Details:
Map:CTRPv3.8=StudyRelationship.sequenceNumber
Map:CTRv1.0=DocumentVersionRelationship.priorityNumber
Map:ICSRr2=SourceOf1.priorityNumber (in IndividualCaseSafetyReport)
Notes: DEFINITION:#lt;br /#gt;#lt;/p#gt;#lt;p#gt;A number specifying the relative rank for one document version before other similar documents having the same type of association to the same source document version.#lt;br /#gt;#lt;/p#gt;#lt;p#gt;#lt;br /#gt;#lt;/p#gt;#lt;p#gt;EXAMPLE(S):#lt;br /#gt;#lt;/p#gt;#lt;p#gt;A report initiated by the primary physician may be ranked higher than reports initiated by specialty consultants or support staff.#lt;br /#gt;#lt;/p#gt;#lt;p#gt;#lt;br /#gt;#lt;/p#gt;#lt;p#gt;OTHER NAME(S):#lt;br /#gt;#lt;/p#gt;#lt;p#gt;#lt;br /#gt;#lt;/p#gt;#lt;p#gt;NOTE(S):#lt;br /#gt;#lt;/p#gt;#lt;p#gt;Relationships with lower priorityNumber values are considered before and above those with higher values.#lt;br /#gt;#lt;/p#gt;#lt;p#gt;#lt;br /#gt;#lt;/p#gt;#lt;p#gt;There may be multiple investigations (and therefore reports) into the same event, each initiated by a different party. The priorityNumber may be used to rank these investigations. #lt;br /#gt;#lt;/p#gt;#lt;p#gt;#lt;br /#gt;#lt;/p#gt;#lt;p#gt;The ordering may be a total ordering, in which all priority numbers are unique, or a partial ordering, in which the same priority may be assigned to more than one relationship. Decimal numbers may be used to insert values between existing priority numbers.#lt;br /#gt;#lt;/p#gt;
Element Source Role Target Role
DocumentVersion
Class   		Name: sourceDocumentVersionRelationship
  		Name: targetDocumentVersion
 
Details:
DESCRIPTION:<br /></p><p>Each DocumentVersionRelationship always has as target one DocumentVersion.  Each DocumentVersion might be the target for one or more DocumentVersionRelationship.<br /></p><p><br /></p><p>DEFINITION:<br /></p><p><br /></p><p>EXAMPLE(S):<br /></p><p><br /></p><p>OTHER NAME(S):<br /></p><p><br /></p><p>NOTE(S):<br /></p>
DocumentVersion
Class   		Name: targetDocumentVersionRelationship
  		Name: sourceDocumentVersion
 
Details:
DESCRIPTION:<br /></p><p>Each DocumentVersionRelationship always has as source one DocumentVersion.  Each DocumentVersion might be the source for one or more DocumentVersionRelationship.<br /></p><p><br /></p><p>DEFINITION:<br /></p><p><br /></p><p>EXAMPLE(S):<br /></p><p><br /></p><p>OTHER NAME(S):<br /></p><p><br /></p><p>NOTE(S):<br /></p>
Tag Value
Map:CTRPv3.8 StudyProtocol.(StudyRelationship)
Details:
 
Map:CTRPv3.8 StudyRelationship
Details:
 
Map:CTRv1.0 DocumentVersionRelationship
Details:
 
Map:HL7SD ReplacementOf1
Details:
 
Map:ICSRr2 SourceOf2 (in IndividualCaseSafetyReport)
Details:
 
Map:ICSRr2 SourceOf1 (in IndividualCaseSafetyReport)
Details:
 
Map:ICSRr2 reference (in IndividualCaseSafetyReport)
Details:
 
Map:LSDAM DocumentVersionRelationship
Details:
 
Map:LSDAMv2.2.3Plus DocumentVersionRelationship
Details:
 
Map:RPS1 RelatedDocumentation
Details: