: Public Class
Created: 3/12/2008 3:08:49 PM
Modified: 8/26/2017 2:00:46 AM
Project:
Advanced:
DEFINITION:<br/>A document version characterized by information or other content which is tailored to the context of a given situation and audience.<br/><br/>EXAMPLE(S):<br/>Safety Report, Study Report<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>
Attribute
Public CD
  communicationModeCode
Details:
Map:AE=ReportReceipt.modeCode
Map:CTRv1.0=ReportVersion.communicationModeCode
Map:ICSRr2=PrimaryInformationRecipient.modeCode (in IndividualCaseSafetyReport)
Notes: DEFINITION:<br/>A coded value specifying the form in which the report version is transmitted.<br/><br/>EXAMPLE(S):<br/>physically present, over the telephone, written communication, electronic<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>
Public BL
  physicianSignOffIndicator
Details:
Map:APSRv2.1=Hdr: Legal Authenticator - hl7:ClinicalDocument > hl7:legalAuthenticator > hl7:signatureCode
Map:caAERSv2.2=ReportVersion.physicianSignOff
Map:CTRv1.0=ReportVersion.physicianSignOffIndicator
Notes: DEFINITION:<br/>Specifies whether the physician has reviewed and signed off on a version of a report.<br/><br/>EXAMPLE(S):<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>Theoretically speaking, the physicianSignoffIndicator could be derived from the existence of an authenticating person for the report.  However, authenticating person is not represented in the BRIDG model because this use case has not yet been formally presented to BRIDG.  If and when this use case is presented to BRIDG the physicianSignoffIndicator will be marked as derived, but for now this attribute will remain as not derivable.<br/>
Public TS.DATETIME
  dueDate
Details:
Map:caAERSv2.2=Report.dueDate
Map:caAERSv2.2=ReportVersion.dueOn
Map:CTRv1.0=ReportVersion.dueDate
Notes: DEFINITION:<br/>The date (and time) on which the report version is expected or scheduled to be submitted.<br/><br/>EXAMPLE(S):<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>
Element Source Role Target Role
PerformedObservationResult
Class   		Name: describingReportVersion
  		Name: describedPerformedObservationResult
 
Details:
DESCRIPTION:<br/>Each ReportVersion might describe one or more PerformedObservationResult.  Each PerformedObservationResult might be described by one or more ReportVersion.<br/><br/>DEFINITION:<br/><br/>EXAMPLE(S):<br/>surgical pathology report describes observations about a specimen collection group<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/>
Element Source Role Target Role
ReportReceiver
Class   		Name: receivingReportReceiver
  		Name: receivedReportVersion
 
Details:
DESCRIPTION:<br/>Each ReportReceiver always receives one ReportVersion. Each ReportVersion might be received by one or more ReportReceiver.<br/><br/>DEFINITION:<br/><br/>EXAMPLE(S):<br/><br/>OTHER NAME(S):<br/><br/>NOTE(S):<br/><br/>
Tag Value
Map:AE ReportReceipt
Details:
 
Map:C3PRv2.9 ReportVersion
Details:
 
Map:caAERSv2.2 Report
Details:
 
Map:CTRRr3 Report
Details:
 
Map:CTRv1.0 ReportVersion
Details:
 
Object Type Connection Direction Notes
DocumentVersion Class Generalization To DESCRIPTION: Each ReportVersion always specializes one DocumentVersion. Each DocumentVersion might be specialized by one ReportVersion. DEFINITION: EXAMPLE(S): OTHER NAME(S): NOTE(S):
SafetyReportVersion Class Generalization From DESCRIPTION: Each SafetyReportVersion always specializes one ReportVersion. Each ReportVersion might be specialized by one SafetyReportVersion. DEFINITION: EXAMPLE(S): OTHER NAME(S): NOTE(S):
AnatomicPathologyReportVersion Class Generalization From DESCRIPTION: Each AnatomicPathologyReportVersion always specializes one ReportVersion. Each ReportVersion might be specialized by one AnatomicPathologyReportVersion. DEFINITION: EXAMPLE(S): OTHER NAME(S): NOTE(S):
AnatomicPathologySectionVersion Class Generalization From DESCRIPTION: Each AnatomicPathologySectionVersion always specializes one ReportVersion. Each ReportVersion might be specialized by one AnatomicPathologySectionVersion. DEFINITION: EXAMPLE(S): OTHER NAME(S): NOTE(S):