ca.infoway.messagebuilder.model.ab_mr2007_v02_r02.merged
Class CreatedByBean

java.lang.Object
  ca.infoway.messagebuilder.model.MessagePartBean
      ca.infoway.messagebuilder.model.ab_mr2007_v02_r02.merged.CreatedByBean

All Implemented Interfaces:

NullFlavorSupport, Serializable

public class CreatedByBean
extends MessagePartBean

Business Name: CreatedBy

MCAI_MT700211CA.Author: a:*created by

Indicates the person responsible for the event that caused this message.

Critical for auditing and for validating permissions and therefore mandatory.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

QUQI_MT020002CA.Author: a:*created by

If AuthorizationToken is specified and communicates author, the bare AuthorRole class must be specified, otherwise the R_ActingPerson CMET must be specified.

Indicates the person responsible for the event that caused this message.

Critical for auditing and for validating permissions and therefore mandatory.

MCAI_MT700212CA.Author: a:*created by

If AuthorizationToken is specified and communicates author, the bare AuthorRole class must be specified, otherwise the R_ActingPerson CMET must be specified.

Indicates the person responsible for the event that caused this message.

Critical for auditing and for validating permissions and therefore mandatory.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

QUQI_MT020000CA.Author: a:*created by

Indicates the person responsible for the event that caused this message.

Critical for auditing and for validating permissions and therefore mandatory.

MCAI_MT700232CA.Author: a:*created by

If AuthorizationToken is specified and communicates author, the bare AuthorRole class must be specified, otherwise the R_ActingPerson CMET must be specified.

Indicates the person responsible for the event that caused this message.

Critical for auditing and for validating permissions and therefore mandatory.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

MCAI_MT700230CA.Author: a:*created by

If AuthorizationToken is specified and communicates author, the bare AuthorRole class must be specified, otherwise the R_ActingPerson CMET must be specified.

Indicates the person responsible for the event that caused this message.

Critical for auditing and for validating permissions and therefore mandatory.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

MCAI_MT700210CA.Author: a:*created by

Indicates the person responsible for the event that caused this message.

Critical for auditing and for validating permissions and therefore mandatory.

MCAI_MT700231CA.Author: a:*created by

If AuthorizationToken is specified and communicates author, the bare AuthorRole class must be specified, otherwise the R_ActingPerson CMET must be specified.

Indicates the person responsible for the event that caused this message.

Critical for auditing and for validating permissions and therefore mandatory.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

MCAI_MT700221CA.Author: a:*created by

Indicates the person responsible for the event that caused this message.

Critical for auditing and for validating permissions and therefore mandatory.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or similar processing.

3. 'identified-confirmable' otherwise.

Choice of Patient CMET is as follows:

1. 'identified' when supporting Patient Session Tokens.

2. 'informational' when passing through non Client- Registry patient for PHS or sim ... [rest of documentation truncated due to excessive length]

See Also:

Serialized Form

Constructor Summary

CreatedByBean()

Method Summary

ProviderBean	getAssignedPerson() Un-merged Business Name: (no business name specified)
AuthorPerson	getAuthorPerson() Un-merged Business Name: (no business name specified)
ParticipationMode	getModeCode() Business Name: InformationReceivedMethod
String	getSignatureText() Business Name: DigitalSignature
Date	getTime() Business Name: TimeOfCreation
void	setAssignedPerson(ProviderBean assignedPerson) Un-merged Business Name: (no business name specified)
void	setAuthorPerson(AuthorPerson authorPerson) Un-merged Business Name: (no business name specified)
void	setModeCode(ParticipationMode modeCode) Business Name: InformationReceivedMethod
void	setSignatureText(String signatureText) Business Name: DigitalSignature
void	setTime(Date time) Business Name: TimeOfCreation

Methods inherited from class ca.infoway.messagebuilder.model.MessagePartBean

getField, getNullFlavor, getNullFlavor, getSpecializationType, hasNullFlavor, hasNullFlavor, setNullFlavor, setNullFlavor, setSpecializationType

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

CreatedByBean

public CreatedByBean()

Method Detail

getTime

public Date getTime()

Business Name: TimeOfCreation

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700211CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: QUQI_MT020002CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700212CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700232CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: QUQI_MT020000CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700210CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700230CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700231CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700221CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effec ... [rest of documentation truncated due to excessive length]

setTime

public void setTime(Date time)

Business Name: TimeOfCreation

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700211CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: QUQI_MT020002CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700212CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700232CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: QUQI_MT020000CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700210CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700230CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700231CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effective. (E.g. If a provider decides today to put a prescription on hold starting next Tuesday, the time of creation would be today and the change effective period would be next Tuesday.)

This date can be back-dated.

The time a change is made is a critical piece of audit information and is therefore mandatory.

Un-merged Business Name: TimeOfCreation

Relationship: MCAI_MT700221CA.Author.time

Conformance/Cardinality: MANDATORY (1)

The time the person responsible for the event made the decision for it to occur. This may be different than the time the change became effec ... [rest of documentation truncated due to excessive length]

getModeCode

public ParticipationMode getModeCode()

Business Name: InformationReceivedMethod

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700211CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: QUQI_MT020002CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700212CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700232CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: QUQI_MT020000CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700210CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700230CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700231CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700221CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

setModeCode

public void setModeCode(ParticipationMode modeCode)

Business Name: InformationReceivedMethod

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700211CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: QUQI_MT020002CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700212CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700232CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: QUQI_MT020000CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700210CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700230CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700231CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

Un-merged Business Name: InformationReceivedMethod

Relationship: MCAI_MT700221CA.Author.modeCode

Conformance/Cardinality: REQUIRED (0-1)

Indicates how the person who recorded the event became aware of it.. E.g. Verbal, written, fax, etc.

May have ramifications for the audit trail and reliability of the information.

getSignatureText

public String getSignatureText()

Business Name: DigitalSignature

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700211CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: QUQI_MT020002CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700212CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700232CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: QUQI_MT020000CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700210CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700230CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700231CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700221CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

setSignatureText

public void setSignatureText(String signatureText)

Business Name: DigitalSignature

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700211CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: QUQI_MT020002CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700212CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700232CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: QUQI_MT020000CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700210CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700230CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700231CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

Un-merged Business Name: DigitalSignature

Relationship: MCAI_MT700221CA.Author.signatureText

Conformance/Cardinality: OPTIONAL (0-1)

Indicates the formal digital signature of the message content.

Digital signatures may be needed for authentication of message content. The attribute is marked as optional because it is not yet clear whether there is a use-case for this, or where it will be used.

getAuthorPerson

public AuthorPerson getAuthorPerson()

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700211CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: QUQI_MT020002CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700212CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700232CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: QUQI_MT020000CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700230CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700231CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700221CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

setAuthorPerson

public void setAuthorPerson(AuthorPerson authorPerson)

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700211CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: QUQI_MT020002CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700212CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700232CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: QUQI_MT020000CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700230CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700231CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700221CA.Author.authorPerson

Conformance/Cardinality: POPULATED (1)

getAssignedPerson

public ProviderBean getAssignedPerson()

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700210CA.Author.assignedPerson

Conformance/Cardinality: MANDATORY (1)

setAssignedPerson

public void setAssignedPerson(ProviderBean assignedPerson)

Un-merged Business Name: (no business name specified)

Relationship: MCAI_MT700210CA.Author.assignedPerson

Conformance/Cardinality: MANDATORY (1)