|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||
java.lang.Objectca.infoway.messagebuilder.model.MessagePartBean
public class RefusedByBean
COMT_MT300003CA.Author: *b:annotated by
Identifier of the provider who created the patient note.
Allows other providers to communicator with the author of the note for follow-up enquiries. The author of an annotation must always be known and is therefore mandatory.
POIZ_MT060150CA.Author: *administered by
Identity of the provider who performed the immunization event.
Allows for the tracking of the provider who did the immunization and therefore mandatory.
PORX_MT060160CA.Author5: *refused by
Indicates who refused to fulfill the prescription
Allows follow-up and traceability of the refusal.
Association is mandatory as the provider refusing the fill must be known.
Allows follow-up and traceability of the refusal.
Association is mandatory as the provider refusing the fill must be known.
PORX_MT060190CA.Author: *recorded by
Indicates the provider who recorded the "other active medication".
Useful for follow-up and audit purposes, and therefore mandatory.
REPC_MT000010CA.Author3: *changed by
Identity of the health service provider responsible for the change in the medical condition.
In an EHR integrated health services environment, it is important that other providers are able to query who is responsible for status changes. Also used by applications for auditing. The provider responsible for a change should always be known and is therefore mandatory.
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.
REPC_MT100002CA.Author3: *b:recorded by
Identifies the provider responsible for the recording the patient measurement.
Annotation.requestingProvider
ZPB3.18 (id.root)
ZPB3.19 (id.extension)
ZPB3.15
Annotation.requestingProvider
ZPB3.18 (id.root)
ZPB3.19 (id.extension)
ZPB3.15
Annotation.requestingProvider
ZPB3.18 (id.root)
ZPB3.19 (id.extension)
ZPB3.15
Annotation.requestingProvider
ZPB3.18 (id.root)
ZPB3.19 (id.extension)
ZPB3.15
Allows tracking of who made the patient observation. This attribute is mandatory because the provider responsible for the observation must be known.
Only needs to be specified if the author of the annotation differs from the prescriber.
REPC_MT000010CA.Author: *d:authored by
Identifies the provider who caused the condition to be recorded.
AllergyIntolerance.authorizingProvider
ZPB1.3
AllergyIntolerance.authorizingPhysician
AllergyIntolerance.authorizingProvider
ZPB1.3
AllergyIntolerance.authorizingPhysician
AllergyIntolerance.authorizingProvider
ZPB1.3
AllergyIntolerance.authorizingPhysician
Identifies responsibility for accuracy and relevance of the information. This association reflects primary responsibility, and is therefore mandatory.
QUQI_MT020000CA.Author: *b:created by
Indicates the person responsible for the event that caused this message.
Critical for auditing and for validating permissions and therefore mandatory.
PORX_MT060040CA.Author: *refused by
Indicates who refused to fulfill the prescription
Allows follow-up and traceability of the refusal.
Association is mandatory as the provider refusing the fill must be known.
Allows follow-up and traceability of the refusal.
Association is mandatory as the provider refusing the fill must be known.
REPC_MT000006CA.Author: *f:authored by
Identifies the provider who reported the reaction.
AllergyIntolerance.authorizingProvider
ZPB1.3
AllergyIntolerance.authorizingPhysician
AllergyIntolerance.authorizingProvider
ZPB1.3
AllergyIntolerance.authorizingPhysician
AllergyIntolerance.authorizingProvider
ZPB1.3
AllergyIntolerance.authorizingPhysician
Identifies responsibility for accuracy and relevance of the information. This association reflects primary responsibility, and is therefore mandatory.
PORX_MT060210CA.Author: *b:recorded by
Indicates the identity of the provider who recorded the other medication information.
Allows other providers to enquire about the authenticity of the content of the other medication record and is therefore mandatory.
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.
PORX_MT020070CA.Author: bc:prescribed by
The person who prescribed the medication.
Used to create an 'inferred' prescription if an electronic prescription does not already exist in the EHR.
MCAI_MT700223CA.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.
PORX_MT060190CA.Author3: *refused by
Indicates who refused to fulfill the prescription
Allows follow-up and traceability of the refusal and is therefore mandatory
PORX_MT030040CA.Author: *refused by
Indicates who refused to fulfill the prescription
Allows follow-up and traceability of the refusal and is therefore mandatory.
PORX_MT060090CA.Author5: *prescribed by
Indicates the prescriber of the prescription.
The prescriber is a key piece of legal information which must be conveyed and is therefore mandatory.
PORX_MT060160CA.Author: *created by
Identifies the provider responsible for capturing the Other Medication record
Provides traceability as well as contact information for follow-up and is therefore mandatory.
REPC_MT000009CA.Author: *f:authored by
Identifies the provider who reported the allergy or intolerance.
AllergyIntolerance.authorizingProvider
ZPB1.3
AllergyIntolerance.authorizingPhysician
AllergyIntolerance.authorizingProvider
ZPB1.3
AllergyIntolerance.authorizingPhysician
AllergyIntolerance.authorizingProvider
ZPB1.3
AllergyIntolerance.authorizingPhysician
Identifies responsibility for accuracy and relevance of the information. This association reflects primary responsibility, and is therefore mandatory.
COCT_MT130001CA.Author3: *changed by
Identity of the health service provider responsible for the change.
In an EHR integrated health services environment, it is important that other providers are able to query who is responsible for a given change. Also used by applications for auditing and sorting. The attribute is mandatory because the responsible provider should always be known.
PORX_MT060340CA.Author: *refused by
Indicates who refused to fulfill the prescription
Allows follow-up and traceability of the refusal.
Association is mandatory as the provider refusing the fill must be known.
Allows follow-up and traceability of the refusal.
Association is mandatory as the provider refusing the fill must be known.
REPC_MT000017CA.Author: Provider
ZPS.6
A_BillableClinicalService
ZPS.6
A_BillableClinicalService
PORX_MT060060CA.Author: *refused by
Indicates who refused to fulfill the prescription
Allows follow-up and traceability of the refusal and is therefore mandatory
REPC_MT000007CA.Author: *b:authored by
Identifies the provider who caused the condition to be recorded.
AllergyIntolerance.authorizingProvider
ZPB1.3
AllergyIntolerance.authorizingPhysician
AllergyIntolerance.authorizingProvider
ZPB1.3
AllergyIntolerance.authorizingPhysician
AllergyIntolerance.authorizingProvider
ZPB1.3
AllergyIntolerance.authorizingPhysician
Identifies responsibility for accuracy and relevance of the information. This association reflects primary responsibility, and is therefore mandatory.
REPC_MT000009CA.Author3: *changed by
Identity of the health service provider responsible for the change in the allergy/intolerance status.
In an EHR integrated health services environment, it is important that other providers are able to query who is responsible for a given change. Also used by applications for auditing and sorting. The attribute is mandatory because the responsible provider should always be known.
REPC_MT000005CA.Author: *f:authored by
... [rest of documentation truncated due to excessive length]
| Constructor Summary | |
|---|---|
RefusedByBean()
|
|
| Method Summary | |
|---|---|
ProviderBean |
getAssignedPerson()
Un-merged Business Name: AuthoredBy |
ParticipationMode |
getModeCode()
Business Name: InformationReceivedMethod |
String |
getSignatureText()
Business Name: DigitalSignature |
Date |
getTime()
Un-merged Business Name: PatientNoteDate |
void |
setAssignedPerson(ProviderBean assignedPerson)
Un-merged Business Name: AuthoredBy |
void |
setModeCode(ParticipationMode modeCode)
Business Name: InformationReceivedMethod |
void |
setSignatureText(String signatureText)
Business Name: DigitalSignature |
void |
setTime(Date time)
Un-merged Business Name: PatientNoteDate |
| 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 |
|---|
public RefusedByBean()
| Method Detail |
|---|
public Date getTime()
Un-merged Business Name: PatientNoteDate
Relationship: COMT_MT300003CA.Author.time
Conformance/Cardinality: MANDATORY (1)
The date on which the patient note was created.
Allows other provider to evaluate the currency of the information contained in the note.
The date of the note creation is always known and is therefore mandatory.
Allows other provider to evaluate the currency of the information contained in the note.
The date of the note creation is always known 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.
was constructed.
Un-merged Business Name: PrescriptionOrderDate
Relationship: PORX_MT020070CA.Author.time
Conformance/Cardinality: POPULATED (1)
The date at which the drug was prescribed. This may differ from the date on which the prescription becomes effective. E.g. A prescription created today may not be valid to be dispensed or administered for two weeks.
Indicates when the action was performed, and may influence expiry dates for the order.
The attribute is populated because the creation date of the prescription shall always be known or absent for a reason.
Indicates when the action was performed, and may influence expiry dates for the order.
The attribute is populated because the creation date of the prescription shall always be known or absent for a reason.
The date and time at which the drug was prescribed. This may differ for mthe date on which the prescription becomes effective.
Un-merged Business Name: TimeOfCreation
Relationship: MCAI_MT700223CA.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: ChangeTime
Relationship: REPC_MT000010CA.Author3.time
Conformance/Cardinality: MANDATORY (1)
The date and time on which the change was made.
Gives other providers the frame of reference in evaluating any post-change issues with the medical condition. Also used for sorting and audit purposes. Time of change is always known and thus the attribute is 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 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: PrescriptionOrderDate
Relationship: PORX_MT060090CA.Author5.time
Conformance/Cardinality: POPULATED (1)
The date at which the drug was prescribed. This may differ from the date on which the prescription becomes effective. E.g. A prescription created today may not be valid to be dispensed or administered for two weeks.
Indicates when the action was performed, and may influence expiry dates for the order.
The attribute is populated because the creation date of the prescription shall always be known or absent for a reason.
Indicates when the action was performed, and may influence expiry dates for the order.
The attribute is populated because the creation date of the prescription shall always be known or absent for a reason.
Un-merged Business Name: RecordingDatetime
Relationship: REPC_MT100002CA.Author3.time
Conformance/Cardinality: POPULATED (1)
The date and time on which the observation was recorded.
ZPB3.20
Annotation.annotationDate
ZPB3.20
Annotation.annotationDate
The date and time on which the observation was recorded. Identifies timing of observation for sorting and for audit purposes. Attribute is populated because the source of the data may not be through the 'record common observation' interaction.
If not specified, the author time of the overall order will be assumed.
Un-merged Business Name: CreateTimestamp
Relationship: REPC_MT000010CA.Author.time
Conformance/Cardinality: POPULATED (1)
The date and time on which the medical condition record was created.
Identifies timing of the medical condition for sorting and for audit purposes. Attribute is populated because the source of the data may not be through the 'record common observation' interaction.
Un-merged Business Name: CreateTimestamp
Relationship: REPC_MT000009CA.Author.time
Conformance/Cardinality: POPULATED (1)
The date and time on which the allergy/intolerance record was created.
Identifies timing of allergy/intolerance for sorting and for audit purposes. Attribute is populated because the source of the data may not be through the 'record common observation' interaction.
Un-merged Business Name: ChangeDatetime
Relationship: COCT_MT130001CA.Author3.time
Conformance/Cardinality: MANDATORY (1)
The date on which the change was made. Note that this may be earlier or occassionally later than when the change is actually effective.
Gives other providers the frame of reference in evaluating any post-change issues with the event. Also used for sorting and audit purposes. Time of change is always known and thus the attribute is mandatory.
Un-merged Business Name: TimeOfCreation
Relationship: QUQI_MT020000CA.Author.time
Conformance/Cardinality: MANDATORY (1)
The time ... [rest of documentation truncated due to excessive length]
public void setTime(Date time)
Un-merged Business Name: PatientNoteDate
Relationship: COMT_MT300003CA.Author.time
Conformance/Cardinality: MANDATORY (1)
The date on which the patient note was created.
Allows other provider to evaluate the currency of the information contained in the note.
The date of the note creation is always known and is therefore mandatory.
Allows other provider to evaluate the currency of the information contained in the note.
The date of the note creation is always known 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.
was constructed.
Un-merged Business Name: PrescriptionOrderDate
Relationship: PORX_MT020070CA.Author.time
Conformance/Cardinality: POPULATED (1)
The date at which the drug was prescribed. This may differ from the date on which the prescription becomes effective. E.g. A prescription created today may not be valid to be dispensed or administered for two weeks.
Indicates when the action was performed, and may influence expiry dates for the order.
The attribute is populated because the creation date of the prescription shall always be known or absent for a reason.
Indicates when the action was performed, and may influence expiry dates for the order.
The attribute is populated because the creation date of the prescription shall always be known or absent for a reason.
The date and time at which the drug was prescribed. This may differ for mthe date on which the prescription becomes effective.
Un-merged Business Name: TimeOfCreation
Relationship: MCAI_MT700223CA.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: ChangeTime
Relationship: REPC_MT000010CA.Author3.time
Conformance/Cardinality: MANDATORY (1)
The date and time on which the change was made.
Gives other providers the frame of reference in evaluating any post-change issues with the medical condition. Also used for sorting and audit purposes. Time of change is always known and thus the attribute is 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 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: PrescriptionOrderDate
Relationship: PORX_MT060090CA.Author5.time
Conformance/Cardinality: POPULATED (1)
The date at which the drug was prescribed. This may differ from the date on which the prescription becomes effective. E.g. A prescription created today may not be valid to be dispensed or administered for two weeks.
Indicates when the action was performed, and may influence expiry dates for the order.
The attribute is populated because the creation date of the prescription shall always be known or absent for a reason.
Indicates when the action was performed, and may influence expiry dates for the order.
The attribute is populated because the creation date of the prescription shall always be known or absent for a reason.
Un-merged Business Name: RecordingDatetime
Relationship: REPC_MT100002CA.Author3.time
Conformance/Cardinality: POPULATED (1)
The date and time on which the observation was recorded.
ZPB3.20
Annotation.annotationDate
ZPB3.20
Annotation.annotationDate
The date and time on which the observation was recorded. Identifies timing of observation for sorting and for audit purposes. Attribute is populated because the source of the data may not be through the 'record common observation' interaction.
If not specified, the author time of the overall order will be assumed.
Un-merged Business Name: CreateTimestamp
Relationship: REPC_MT000010CA.Author.time
Conformance/Cardinality: POPULATED (1)
The date and time on which the medical condition record was created.
Identifies timing of the medical condition for sorting and for audit purposes. Attribute is populated because the source of the data may not be through the 'record common observation' interaction.
Un-merged Business Name: CreateTimestamp
Relationship: REPC_MT000009CA.Author.time
Conformance/Cardinality: POPULATED (1)
The date and time on which the allergy/intolerance record was created.
Identifies timing of allergy/intolerance for sorting and for audit purposes. Attribute is populated because the source of the data may not be through the 'record common observation' interaction.
Un-merged Business Name: ChangeDatetime
Relationship: COCT_MT130001CA.Author3.time
Conformance/Cardinality: MANDATORY (1)
The date on which the change was made. Note that this may be earlier or occassionally later than when the change is actually effective.
Gives other providers the frame of reference in evaluating any post-change issues with the event. Also used for sorting and audit purposes. Time of change is always known and thus the attribute is mandatory.
Un-merged Business Name: TimeOfCreation
Relationship: QUQI_MT020000CA.Author.time
Conformance/Cardinality: MANDATORY (1)
The time ... [rest of documentation truncated due to excessive length]
public ProviderBean getAssignedPerson()
Un-merged Business Name: AuthoredBy
Relationship: COMT_MT300003CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Identifies the provider who reported the note.
Un-merged Business Name: (no business name specified)
Relationship: POIZ_MT060150CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060160CA.Author5.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060190CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT000010CA.Author3.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: MCAI_MT700221CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT100002CA.Author3.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT000010CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: CreatedBy
Relationship: QUQI_MT020000CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
are allowed to do the specified interaction.
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060040CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT000006CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060210CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: CreatedBy
Relationship: MCAI_MT700210CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
specified interaction.
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT020070CA.Author.assignedPerson
Conformance/Cardinality: POPULATED (1)
Un-merged Business Name: (no business name specified)
Relationship: MCAI_MT700223CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060190CA.Author3.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT030040CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060090CA.Author5.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060160CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: AuthoredBy
Relationship: REPC_MT000009CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: COCT_MT130001CA.Author3.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060340CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT000017CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060060CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT000007CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: AuthoredBy
Relationship: REPC_MT000005CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Identifies the provider who reported the allergy or intolerance.
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT000009CA.Author3.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060010CA.Author5.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT020060CA.Author.assignedPerson
Conformance/Cardinality: POPULATED (1)
Un-merged Business Name: (no business name specified)
Relationship: COCT_MT120600CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT100001CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
public void setAssignedPerson(ProviderBean assignedPerson)
Un-merged Business Name: AuthoredBy
Relationship: COMT_MT300003CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Identifies the provider who reported the note.
Un-merged Business Name: (no business name specified)
Relationship: POIZ_MT060150CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060160CA.Author5.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060190CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT000010CA.Author3.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: MCAI_MT700221CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT100002CA.Author3.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT000010CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: CreatedBy
Relationship: QUQI_MT020000CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
are allowed to do the specified interaction.
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060040CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT000006CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060210CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: CreatedBy
Relationship: MCAI_MT700210CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
specified interaction.
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT020070CA.Author.assignedPerson
Conformance/Cardinality: POPULATED (1)
Un-merged Business Name: (no business name specified)
Relationship: MCAI_MT700223CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060190CA.Author3.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT030040CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060090CA.Author5.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060160CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: AuthoredBy
Relationship: REPC_MT000009CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: COCT_MT130001CA.Author3.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060340CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT000017CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060060CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT000007CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: AuthoredBy
Relationship: REPC_MT000005CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Identifies the provider who reported the allergy or intolerance.
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT000009CA.Author3.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT060010CA.Author5.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT020060CA.Author.assignedPerson
Conformance/Cardinality: POPULATED (1)
Un-merged Business Name: (no business name specified)
Relationship: COCT_MT120600CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
Un-merged Business Name: (no business name specified)
Relationship: REPC_MT100001CA.Author.assignedPerson
Conformance/Cardinality: MANDATORY (1)
public ParticipationMode getModeCode()
Business Name: InformationReceivedMethod
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_MT700223CA.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.
public void setModeCode(ParticipationMode modeCode)
Business Name: InformationReceivedMethod
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_MT700223CA.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.
public String getSignatureText()
Business Name: DigitalSignature
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.
This field will be ignored if it is sent.
Un-merged Business Name: DigitalSignature
Relationship: MCAI_MT700223CA.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.
public void setSignatureText(String signatureText)
Business Name: DigitalSignature
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.
This field will be ignored if it is sent.
Un-merged Business Name: DigitalSignature
Relationship: MCAI_MT700223CA.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.
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD | |||||||||