ca.infoway.messagebuilder.model.ab_mr2007_v02_r02.pharmacy.merged
Class DispenseStatusChangesBean

Package class diagram package DispenseStatusChangesBean
java.lang.Object
  extended by ca.infoway.messagebuilder.model.MessagePartBean
      extended by ca.infoway.messagebuilder.model.ab_mr2007_v02_r02.pharmacy.merged.DispenseStatusChangesBean
All Implemented Interfaces:
NullFlavorSupport, Serializable

public class DispenseStatusChangesBean
extends MessagePartBean

PORX_MT060210CA.ControlActEvent: Other Medication Status Changes

This records the history of changes that have been made to the other medication record, including why the changes were made, who made them and when.

Provides an audit trail of a patient's use of other medications.

PORX_MT060040CA.ControlActEvent: Status Changes

This records the history of changes that have been made to the prescription, including why the changes were made, who made them and when.

Provides an audit trail of a patient's therapy adjustments. Status changes may affect evaluations of compliance.

PORX_MT060090CA.ControlActEvent: Dispense Status Changes

This records the history of changes that have been made to the prescription dispense, including why the changes were made, who made them and when.

Provides an audit trail of a patient's therapy adjustments. Status changes may affect evaluations of compliance.

PORX_MT060010CA.ControlActEvent: Dispense Status Changes

This records the history of changes that have been made to the prescription dispense, including why the changes were made, who made them and when.

Provides an audit trail of a patient's therapy adjustments. Status changes may affect evaluations of compliance.

See Also:
Serialized Form

Constructor Summary
DispenseStatusChangesBean()
           
 
Method Summary
 Author1Bean getAuthor()
          Un-merged Business Name: (no business name specified)
 HL7TriggerEventCode getCode()
          Un-merged Business Name: ChangeType
 Interval<Date> getEffectiveTime()
          Un-merged Business Name: ChangeEffectivePeriod
 ControlActReason getReasonCode()
          Un-merged Business Name: ChangeReason
 HealthcareWorkerBean getResponsiblePartyAssignedEntity()
          Un-merged Business Name: (no business name specified)
 void setAuthor(Author1Bean author)
          Un-merged Business Name: (no business name specified)
 void setCode(HL7TriggerEventCode code)
          Un-merged Business Name: ChangeType
 void setEffectiveTime(Interval<Date> effectiveTime)
          Un-merged Business Name: ChangeEffectivePeriod
 void setReasonCode(ControlActReason reasonCode)
          Un-merged Business Name: ChangeReason
 void setResponsiblePartyAssignedEntity(HealthcareWorkerBean responsiblePartyAssignedEntity)
          Un-merged Business Name: (no business name specified)
 
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

DispenseStatusChangesBean

public DispenseStatusChangesBean()
Method Detail

getCode

public HL7TriggerEventCode getCode()

Un-merged Business Name: ChangeType

Relationship: PORX_MT060040CA.ControlActEvent.code

Conformance/Cardinality: MANDATORY (1)

Identifies what kind of change occurred. Examples include Suspended, Superseded, Released, Aborted (stopped), etc.

This attribute is mandatory to ensure that change types are distinguishable.

Un-merged Business Name: OtherMedicationStatusChangeType

Relationship: PORX_MT060210CA.ControlActEvent.code

Conformance/Cardinality: MANDATORY (1)

Identifies what kind of change occurred. Examples include Completed, Aborted, etc.

This attribute is mandatory to ensure that change types are distinguishable

Un-merged Business Name: DispenseStatusChangeType

Relationship: PORX_MT060010CA.ControlActEvent.code

Conformance/Cardinality: MANDATORY (1)

Identifies what kind of change occurred. Examples include Suspended, Aborted, etc.

This attribute is mandatory to ensure that change types are distinguishable.

Un-merged Business Name: DispenseStatusChangeType

Relationship: PORX_MT060090CA.ControlActEvent.code

Conformance/Cardinality: MANDATORY (1)

Identifies what kind of change occurred. Examples include Suspended, Aborted, etc.

This attribute is mandatory to ensure that change types are distinguishable.


setCode

public void setCode(HL7TriggerEventCode code)

Un-merged Business Name: ChangeType

Relationship: PORX_MT060040CA.ControlActEvent.code

Conformance/Cardinality: MANDATORY (1)

Identifies what kind of change occurred. Examples include Suspended, Superseded, Released, Aborted (stopped), etc.

This attribute is mandatory to ensure that change types are distinguishable.

Un-merged Business Name: OtherMedicationStatusChangeType

Relationship: PORX_MT060210CA.ControlActEvent.code

Conformance/Cardinality: MANDATORY (1)

Identifies what kind of change occurred. Examples include Completed, Aborted, etc.

This attribute is mandatory to ensure that change types are distinguishable

Un-merged Business Name: DispenseStatusChangeType

Relationship: PORX_MT060010CA.ControlActEvent.code

Conformance/Cardinality: MANDATORY (1)

Identifies what kind of change occurred. Examples include Suspended, Aborted, etc.

This attribute is mandatory to ensure that change types are distinguishable.

Un-merged Business Name: DispenseStatusChangeType

Relationship: PORX_MT060090CA.ControlActEvent.code

Conformance/Cardinality: MANDATORY (1)

Identifies what kind of change occurred. Examples include Suspended, Aborted, etc.

This attribute is mandatory to ensure that change types are distinguishable.


getEffectiveTime

public Interval<Date> getEffectiveTime()

Un-merged Business Name: ChangeEffectivePeriod

Relationship: PORX_MT060040CA.ControlActEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

The date on which the various status changes of a prescription become valid and applicable. In the case of a suspend, may also indicate the scheduled time at which the status change will end.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Un-merged Business Name: OtherMedicationStatusChangeEffectivePeriod

Relationship: PORX_MT060210CA.ControlActEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

The date on which the various status changes of an other medication record become valid and applicable. In the case of a suspend, may also indicate the scheduled time at which the status change will end.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Un-merged Business Name: DispenseStatusChangeEffectiveDate

Relationship: PORX_MT060010CA.ControlActEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

The date on which the various status changes of a prescription dispense become valid and applicable. In the case of a suspend, may also indicate the scheduled time at which the status change will end.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Un-merged Business Name: DispenseStatusChangeEffectiveDate

Relationship: PORX_MT060090CA.ControlActEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

The date on which the various status changes of a prescription dispense become valid and applicable. In the case of a suspend, may also indicate the scheduled time at which the status change will end.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.


setEffectiveTime

public void setEffectiveTime(Interval<Date> effectiveTime)

Un-merged Business Name: ChangeEffectivePeriod

Relationship: PORX_MT060040CA.ControlActEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

The date on which the various status changes of a prescription become valid and applicable. In the case of a suspend, may also indicate the scheduled time at which the status change will end.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Un-merged Business Name: OtherMedicationStatusChangeEffectivePeriod

Relationship: PORX_MT060210CA.ControlActEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

The date on which the various status changes of an other medication record become valid and applicable. In the case of a suspend, may also indicate the scheduled time at which the status change will end.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Un-merged Business Name: DispenseStatusChangeEffectiveDate

Relationship: PORX_MT060010CA.ControlActEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

The date on which the various status changes of a prescription dispense become valid and applicable. In the case of a suspend, may also indicate the scheduled time at which the status change will end.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Un-merged Business Name: DispenseStatusChangeEffectiveDate

Relationship: PORX_MT060090CA.ControlActEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

The date on which the various status changes of a prescription dispense become valid and applicable. In the case of a suspend, may also indicate the scheduled time at which the status change will end.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.

Allows applications to sort and filter by time.

The effective date can be defaulted to change date, and thus is mandatory.


getReasonCode

public ControlActReason getReasonCode()

Un-merged Business Name: ChangeReason

Relationship: PORX_MT060040CA.ControlActEvent.reasonCode

Conformance/Cardinality: REQUIRED (0-1)

Denotes the reason the status of the prescription was changed.

Ensures consistent terminology in capturing and interpreting reasons for change. Allows CWE because not all reasons will correspond to a pre-defined code.

Un-merged Business Name: OtherMedicationStatusChangeReason

Relationship: PORX_MT060210CA.ControlActEvent.reasonCode

Conformance/Cardinality: REQUIRED (0-1)

Denotes the reason the status of the other medication was changed.

Ensures consistent terminology in capturing and interpreting reasons for change. Allows CWE because not all reasons will correspond to a pre-defined code.

Un-merged Business Name: DispenseStatusChangeReason

Relationship: PORX_MT060010CA.ControlActEvent.reasonCode

Conformance/Cardinality: REQUIRED (0-1)

Denotes the reason the status of the prescription dispense was changed.

Ensures consistent terminology in capturing and interpreting reasons for change. Allows CWE because not all reasons will correspond to a pre-defined code.

Un-merged Business Name: DispenseStatusChangeReason

Relationship: PORX_MT060090CA.ControlActEvent.reasonCode

Conformance/Cardinality: REQUIRED (0-1)

Denotes the reason the status of the prescription dispense was changed.

Ensures consistent terminology in capturing and interpreting reasons for change. Allows CWE because not all reasons will correspond to a pre-defined code.


setReasonCode

public void setReasonCode(ControlActReason reasonCode)

Un-merged Business Name: ChangeReason

Relationship: PORX_MT060040CA.ControlActEvent.reasonCode

Conformance/Cardinality: REQUIRED (0-1)

Denotes the reason the status of the prescription was changed.

Ensures consistent terminology in capturing and interpreting reasons for change. Allows CWE because not all reasons will correspond to a pre-defined code.

Un-merged Business Name: OtherMedicationStatusChangeReason

Relationship: PORX_MT060210CA.ControlActEvent.reasonCode

Conformance/Cardinality: REQUIRED (0-1)

Denotes the reason the status of the other medication was changed.

Ensures consistent terminology in capturing and interpreting reasons for change. Allows CWE because not all reasons will correspond to a pre-defined code.

Un-merged Business Name: DispenseStatusChangeReason

Relationship: PORX_MT060010CA.ControlActEvent.reasonCode

Conformance/Cardinality: REQUIRED (0-1)

Denotes the reason the status of the prescription dispense was changed.

Ensures consistent terminology in capturing and interpreting reasons for change. Allows CWE because not all reasons will correspond to a pre-defined code.

Un-merged Business Name: DispenseStatusChangeReason

Relationship: PORX_MT060090CA.ControlActEvent.reasonCode

Conformance/Cardinality: REQUIRED (0-1)

Denotes the reason the status of the prescription dispense was changed.

Ensures consistent terminology in capturing and interpreting reasons for change. Allows CWE because not all reasons will correspond to a pre-defined code.


getResponsiblePartyAssignedEntity

public HealthcareWorkerBean getResponsiblePartyAssignedEntity()

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

Relationship: PORX_MT060040CA.ResponsibleParty4.assignedEntity

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060210CA.ResponsibleParty2.assignedEntity

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060010CA.ResponsibleParty2.assignedEntity

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060090CA.ResponsibleParty4.assignedEntity

Conformance/Cardinality: POPULATED (1)


setResponsiblePartyAssignedEntity

public void setResponsiblePartyAssignedEntity(HealthcareWorkerBean responsiblePartyAssignedEntity)

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

Relationship: PORX_MT060040CA.ResponsibleParty4.assignedEntity

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060210CA.ResponsibleParty2.assignedEntity

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060010CA.ResponsibleParty2.assignedEntity

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060090CA.ResponsibleParty4.assignedEntity

Conformance/Cardinality: POPULATED (1)


getAuthor

public Author1Bean getAuthor()

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

Relationship: PORX_MT060040CA.ControlActEvent.author

Conformance/Cardinality: MANDATORY (1)

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

Relationship: PORX_MT060210CA.ControlActEvent.author

Conformance/Cardinality: MANDATORY (1)

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

Relationship: PORX_MT060010CA.ControlActEvent.author

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060090CA.ControlActEvent.author

Conformance/Cardinality: MANDATORY (1)


setAuthor

public void setAuthor(Author1Bean author)

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

Relationship: PORX_MT060040CA.ControlActEvent.author

Conformance/Cardinality: MANDATORY (1)

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

Relationship: PORX_MT060210CA.ControlActEvent.author

Conformance/Cardinality: MANDATORY (1)

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

Relationship: PORX_MT060010CA.ControlActEvent.author

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060090CA.ControlActEvent.author

Conformance/Cardinality: MANDATORY (1)



Copyright © 2013. All Rights Reserved.