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

java.lang.Object
  ca.infoway.messagebuilder.model.MessagePartBean
      ca.infoway.messagebuilder.model.ab_mr2007_v02_r02.pharmacy.merged.DispenseDetailsBean

All Implemented Interfaces:

NullFlavorSupport, Serializable

public class DispenseDetailsBean
extends MessagePartBean

See Also:

Serialized Form

Constructor Summary

DispenseDetailsBean()

Method Summary

ActPharmacySupplyType	getCode() Business Name: DispenseType
DispenseShipToLocationBean	getDestinationServiceDeliveryLocation() Un-merged Business Name: (no business name specified)
Interval<Date>	getEffectiveTime() Business Name: DispenseProcessingAndPickupDate
Interval<Date>	getExpectedUseTime() Un-merged Business Name: DispensedDaysSupply
DeviceProductBean	getProductManufacturedProduct() Un-merged Business Name: (no business name specified)
Integer	getQuantity() Business Name: DispensedQuantity
RelatedPersonBean	getReceiverPersonalRelationship() Un-merged Business Name: (no business name specified)
void	setCode(ActPharmacySupplyType code) Business Name: DispenseType
void	setDestinationServiceDeliveryLocation(DispenseShipToLocationBean destinationServiceDeliveryLocation) Un-merged Business Name: (no business name specified)
void	setEffectiveTime(Interval<Date> effectiveTime) Business Name: DispenseProcessingAndPickupDate
void	setExpectedUseTime(Interval<Date> expectedUseTime) Un-merged Business Name: DispensedDaysSupply
void	setProductManufacturedProduct(DeviceProductBean productManufacturedProduct) Un-merged Business Name: (no business name specified)
void	setQuantity(Integer quantity) Business Name: DispensedQuantity
void	setReceiverPersonalRelationship(RelatedPersonBean receiverPersonalRelationship) 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

DispenseDetailsBean

public DispenseDetailsBean()

Method Detail

getCode

public ActPharmacySupplyType getCode()

Business Name: DispenseType

Un-merged Business Name: DispenseType

Relationship: PORX_MT020060CA.SupplyEvent.code

Conformance/Cardinality: MANDATORY (1)

Indicates the type of dispensing event that is performed. Examples include: Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc.

Indicates reason for the size of dispense. Because it defines what type of dispense is occurring, the attribute is mandatory.

Un-merged Business Name: DispenseType

Relationship: PORX_MT060010CA.SupplyEvent.code

Conformance/Cardinality: MANDATORY (1)

Indicates the type of dispensing event that is performed. Examples include: Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc.

Indicates reason for the size of dispense. Because it defines what type of dispense is occurring, the attribute is mandatory.

Un-merged Business Name: DispenseType

Relationship: PORX_MT060040CA.SupplyEvent.code

Conformance/Cardinality: MANDATORY (1)

Indicates the type of dispensing event that is performed. Examples include: Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc.

Indicates reason for the size of dispense. Because it defines what type of dispense is occurring, the attribute is mandatory.

setCode

public void setCode(ActPharmacySupplyType code)

Business Name: DispenseType

Un-merged Business Name: DispenseType

Relationship: PORX_MT020060CA.SupplyEvent.code

Conformance/Cardinality: MANDATORY (1)

Indicates the type of dispensing event that is performed. Examples include: Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc.

Indicates reason for the size of dispense. Because it defines what type of dispense is occurring, the attribute is mandatory.

Un-merged Business Name: DispenseType

Relationship: PORX_MT060010CA.SupplyEvent.code

Conformance/Cardinality: MANDATORY (1)

Indicates the type of dispensing event that is performed. Examples include: Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc.

Indicates reason for the size of dispense. Because it defines what type of dispense is occurring, the attribute is mandatory.

Un-merged Business Name: DispenseType

Relationship: PORX_MT060040CA.SupplyEvent.code

Conformance/Cardinality: MANDATORY (1)

Indicates the type of dispensing event that is performed. Examples include: Trial Fill, Completion of Trial, Partial Fill, Emergency Fill, Samples, etc.

Indicates reason for the size of dispense. Because it defines what type of dispense is occurring, the attribute is mandatory.

getEffectiveTime

public Interval<Date> getEffectiveTime()

Business Name: DispenseProcessingAndPickupDate

Un-merged Business Name: DispenseProcessingAndPickupDate

Relationship: PORX_MT020060CA.SupplyEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

Represents the date the dispense product was prepared and when the product was picked up by or delivered to the patient. The dispense processing date and pickup date can be back dated to reflect when the actual processing and pickup occurred. The lower-bound of the period signifies the dispense-processing date whereas the upper-bound signifies the dispense-pickup date.

Used by the system in calculating expected exhaustion time. Valuable in compliance checking. This attribute is mandatory because an existing dispense record must at least indicate the date it was processed.

Must be able to post-date a dispense (enter retroactively) e.g. system failure.

Un-merged Business Name: DispenseProcessingAndPickupDate

Relationship: PORX_MT060010CA.SupplyEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

Represents the date the dispense product was prepared and when the product was picked up by or delivered to the patient. The dispense processing date and pickup date can be back dated to reflect when the actual processing and pickup occurred. The lower-bound of the period signifies the dispense-processing date whereas the upper-bound signifies the dispense-pickup date.

Used by the system in calculating expected exhaustion time. Valuable in compliance checking. This attribute is mandatory because an existing dispense record must at least indicate the date it was processed.

Un-merged Business Name: DispenseProcessingAndPickupDate

Relationship: PORX_MT060020CA.SupplyEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

Represents the date the dispense product was prepared and when the product was picked up by or delivered to the patient. The dispense processing date and pickup date can be back dated to reflect when the actual processing and pickup occurred. The lower-bound of the period signifies the dispense-processing date whereas the upper-bound signifies the dispense-pickup date.

Used by the system in calculating expected exhaustion time. Valuable in compliance checking.

This attribute is mandatory because an existing dispense record must at least indicate the date it was processed.

Used by the system in calculating expected exhaustion time. Valuable in compliance checking.

This attribute is mandatory because an existing dispense record must at least indicate the date it was processed.

Un-merged Business Name: DispenseProcessingAndPickupDate

Relationship: PORX_MT060040CA.SupplyEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

Represents the date the dispense product was prepared and when the product was picked up by or delivered to the patient. The dispense processing date and pickup date can be back dated to reflect when the actual processing and pickup occurred. The lower-bound of the period signifies the dispense-processing date whereas the upper-bound signifies the dispense-pickup date.

Used by the system in calculating expected exhaustion time. Valuable in compliance checking. This attribute is mandatory because an existing dispense record must at least indicate the date it was processed.

setEffectiveTime

public void setEffectiveTime(Interval<Date> effectiveTime)

Business Name: DispenseProcessingAndPickupDate

Un-merged Business Name: DispenseProcessingAndPickupDate

Relationship: PORX_MT020060CA.SupplyEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

Represents the date the dispense product was prepared and when the product was picked up by or delivered to the patient. The dispense processing date and pickup date can be back dated to reflect when the actual processing and pickup occurred. The lower-bound of the period signifies the dispense-processing date whereas the upper-bound signifies the dispense-pickup date.

Used by the system in calculating expected exhaustion time. Valuable in compliance checking. This attribute is mandatory because an existing dispense record must at least indicate the date it was processed.

Must be able to post-date a dispense (enter retroactively) e.g. system failure.

Un-merged Business Name: DispenseProcessingAndPickupDate

Relationship: PORX_MT060010CA.SupplyEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

Represents the date the dispense product was prepared and when the product was picked up by or delivered to the patient. The dispense processing date and pickup date can be back dated to reflect when the actual processing and pickup occurred. The lower-bound of the period signifies the dispense-processing date whereas the upper-bound signifies the dispense-pickup date.

Used by the system in calculating expected exhaustion time. Valuable in compliance checking. This attribute is mandatory because an existing dispense record must at least indicate the date it was processed.

Un-merged Business Name: DispenseProcessingAndPickupDate

Relationship: PORX_MT060020CA.SupplyEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

Represents the date the dispense product was prepared and when the product was picked up by or delivered to the patient. The dispense processing date and pickup date can be back dated to reflect when the actual processing and pickup occurred. The lower-bound of the period signifies the dispense-processing date whereas the upper-bound signifies the dispense-pickup date.

Used by the system in calculating expected exhaustion time. Valuable in compliance checking.

This attribute is mandatory because an existing dispense record must at least indicate the date it was processed.

Used by the system in calculating expected exhaustion time. Valuable in compliance checking.

This attribute is mandatory because an existing dispense record must at least indicate the date it was processed.

Un-merged Business Name: DispenseProcessingAndPickupDate

Relationship: PORX_MT060040CA.SupplyEvent.effectiveTime

Conformance/Cardinality: MANDATORY (1)

Represents the date the dispense product was prepared and when the product was picked up by or delivered to the patient. The dispense processing date and pickup date can be back dated to reflect when the actual processing and pickup occurred. The lower-bound of the period signifies the dispense-processing date whereas the upper-bound signifies the dispense-pickup date.

Used by the system in calculating expected exhaustion time. Valuable in compliance checking. This attribute is mandatory because an existing dispense record must at least indicate the date it was processed.

getQuantity

public Integer getQuantity()

Business Name: DispensedQuantity

Un-merged Business Name: DispensedQuantity

Relationship: PORX_MT020060CA.SupplyEvent.quantity

Conformance/Cardinality: MANDATORY (1)

The number of devices that have been dispensed.

Critical in understanding the patient's profile, both past and current, This is also mandatory to allow determination of the amount that remains to be dispensed against the prescription.

Un-merged Business Name: DispensedQuantity

Relationship: PORX_MT060010CA.SupplyEvent.quantity

Conformance/Cardinality: MANDATORY (1)

The number of devices that have been dispensed.

Critical in understanding the patient's profile, both past and current, This is also mandatory to allow determination of the amount that remains to be dispensed against the prescription.

Un-merged Business Name: DispensedQuantity

Relationship: PORX_MT060020CA.SupplyEvent.quantity

Conformance/Cardinality: MANDATORY (1)

The number of devices that have been dispensed.

D58

ZPB3.4

D58

ZPB3.4

Critical in understanding the patient's profile, both past and current, This is also mandatory to allow determination of the amount that remains to be dispensed against the prescription.

Un-merged Business Name: DispensedQuantity

Relationship: PORX_MT060040CA.SupplyEvent.quantity

Conformance/Cardinality: MANDATORY (1)

The number of devices that have been dispensed.

Critical in understanding the patient's profile, both past and current, This is also mandatory to allow determination of the amount that remains to be dispensed against the prescription.

setQuantity

public void setQuantity(Integer quantity)

Business Name: DispensedQuantity

Un-merged Business Name: DispensedQuantity

Relationship: PORX_MT020060CA.SupplyEvent.quantity

Conformance/Cardinality: MANDATORY (1)

The number of devices that have been dispensed.

Critical in understanding the patient's profile, both past and current, This is also mandatory to allow determination of the amount that remains to be dispensed against the prescription.

Un-merged Business Name: DispensedQuantity

Relationship: PORX_MT060010CA.SupplyEvent.quantity

Conformance/Cardinality: MANDATORY (1)

The number of devices that have been dispensed.

Critical in understanding the patient's profile, both past and current, This is also mandatory to allow determination of the amount that remains to be dispensed against the prescription.

Un-merged Business Name: DispensedQuantity

Relationship: PORX_MT060020CA.SupplyEvent.quantity

Conformance/Cardinality: MANDATORY (1)

The number of devices that have been dispensed.

D58

ZPB3.4

D58

ZPB3.4

Critical in understanding the patient's profile, both past and current, This is also mandatory to allow determination of the amount that remains to be dispensed against the prescription.

Un-merged Business Name: DispensedQuantity

Relationship: PORX_MT060040CA.SupplyEvent.quantity

Conformance/Cardinality: MANDATORY (1)

The number of devices that have been dispensed.

Critical in understanding the patient's profile, both past and current, This is also mandatory to allow determination of the amount that remains to be dispensed against the prescription.

getExpectedUseTime

public Interval<Date> getExpectedUseTime()

Un-merged Business Name: DispensedDaysSupply

Relationship: PORX_MT020060CA.SupplyEvent.expectedUseTime

Conformance/Cardinality: POPULATED (1)

The number of days that the dispensed quantity is expected to last.

Useful in monitoring patient compliance. May also be useful in determining and managing certain contraindications ('Fill-Too-Soon', 'Fill-Too-Late', and 'Duration of Therapy'). Because 'Days Supply' may be necessary to compute total dispensed quantity, it is made a 'populated' field.

Un-merged Business Name: DispensedDaysSupply

Relationship: PORX_MT060010CA.SupplyEvent.expectedUseTime

Conformance/Cardinality: POPULATED (1)

The number of days that the dispensed quantity is expected to last. Cannot be mandatory as there are some situations where 'as needed' cannot be used to determine days supply.

.daysSupply

Useful in monitoring patient compliance. May also be useful in determining and managing certain contraindications ('Fill-Too-Soon', 'Fill-Too-Late', and 'Duration of Therapy'). Because 'Days Supply' may be necessary to compute total dispensed quantity, it is made a 'populated' field.

Un-merged Business Name: DispensedDaysSupply

Relationship: PORX_MT060020CA.SupplyEvent.expectedUseTime

Conformance/Cardinality: POPULATED (1)

The number of days that the dispensed quantity is expected to last. Cannot be mandatory as there are some situations where 'as needed' cannot be used to determine days supply.

Useful in monitoring patient compliance. May also be useful in determining and managing certain contraindications ('Fill-Too-Soon', 'Fill-Too-Late', and 'Duration of Therapy'). Because 'Days Supply' may be necessary to compute total dispensed quantity, it is made a 'populated' field.

Un-merged Business Name: DispenseDaysSupply

Relationship: PORX_MT060040CA.SupplyEvent.expectedUseTime

Conformance/Cardinality: POPULATED (1)

The number of days that the dispensed quantity is expected to last.

Cannot be mandatory as there are some situations where 'as needed' cannot be used to determine days supply.

The number of days that the dispensed quantity is expected to last.

Cannot be mandatory as there are some situations where 'as needed' cannot be used to determine days supply.

Useful in monitoring patient compliance. May also be useful in determining and managing certain contraindications ('Fill-Too-Soon', 'Fill-Too-Late', and 'Duration of Therapy'). Because 'Days Supply' may be necessary to compute total dispensed quantity, it is made a 'populated' field.

setExpectedUseTime

public void setExpectedUseTime(Interval<Date> expectedUseTime)

Un-merged Business Name: DispensedDaysSupply

Relationship: PORX_MT020060CA.SupplyEvent.expectedUseTime

Conformance/Cardinality: POPULATED (1)

The number of days that the dispensed quantity is expected to last.

Useful in monitoring patient compliance. May also be useful in determining and managing certain contraindications ('Fill-Too-Soon', 'Fill-Too-Late', and 'Duration of Therapy'). Because 'Days Supply' may be necessary to compute total dispensed quantity, it is made a 'populated' field.

Un-merged Business Name: DispensedDaysSupply

Relationship: PORX_MT060010CA.SupplyEvent.expectedUseTime

Conformance/Cardinality: POPULATED (1)

The number of days that the dispensed quantity is expected to last. Cannot be mandatory as there are some situations where 'as needed' cannot be used to determine days supply.

.daysSupply

Useful in monitoring patient compliance. May also be useful in determining and managing certain contraindications ('Fill-Too-Soon', 'Fill-Too-Late', and 'Duration of Therapy'). Because 'Days Supply' may be necessary to compute total dispensed quantity, it is made a 'populated' field.

Un-merged Business Name: DispensedDaysSupply

Relationship: PORX_MT060020CA.SupplyEvent.expectedUseTime

Conformance/Cardinality: POPULATED (1)

The number of days that the dispensed quantity is expected to last. Cannot be mandatory as there are some situations where 'as needed' cannot be used to determine days supply.

Useful in monitoring patient compliance. May also be useful in determining and managing certain contraindications ('Fill-Too-Soon', 'Fill-Too-Late', and 'Duration of Therapy'). Because 'Days Supply' may be necessary to compute total dispensed quantity, it is made a 'populated' field.

Un-merged Business Name: DispenseDaysSupply

Relationship: PORX_MT060040CA.SupplyEvent.expectedUseTime

Conformance/Cardinality: POPULATED (1)

The number of days that the dispensed quantity is expected to last.

Cannot be mandatory as there are some situations where 'as needed' cannot be used to determine days supply.

The number of days that the dispensed quantity is expected to last.

Cannot be mandatory as there are some situations where 'as needed' cannot be used to determine days supply.

Useful in monitoring patient compliance. May also be useful in determining and managing certain contraindications ('Fill-Too-Soon', 'Fill-Too-Late', and 'Duration of Therapy'). Because 'Days Supply' may be necessary to compute total dispensed quantity, it is made a 'populated' field.

getProductManufacturedProduct

public DeviceProductBean getProductManufacturedProduct()

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

Relationship: PORX_MT020060CA.Product2.manufacturedProduct

Conformance/Cardinality: MANDATORY (1)

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

Relationship: PORX_MT060010CA.Product2.manufacturedProduct

Conformance/Cardinality: MANDATORY (1)

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

Relationship: PORX_MT060020CA.Product2.manufacturedProduct

Conformance/Cardinality: MANDATORY (1)

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

Relationship: PORX_MT060040CA.Product2.manufacturedProduct

Conformance/Cardinality: MANDATORY (1)

setProductManufacturedProduct

public void setProductManufacturedProduct(DeviceProductBean productManufacturedProduct)

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

Relationship: PORX_MT020060CA.Product2.manufacturedProduct

Conformance/Cardinality: MANDATORY (1)

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

Relationship: PORX_MT060010CA.Product2.manufacturedProduct

Conformance/Cardinality: MANDATORY (1)

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

Relationship: PORX_MT060020CA.Product2.manufacturedProduct

Conformance/Cardinality: MANDATORY (1)

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

Relationship: PORX_MT060040CA.Product2.manufacturedProduct

Conformance/Cardinality: MANDATORY (1)

getDestinationServiceDeliveryLocation

public DispenseShipToLocationBean getDestinationServiceDeliveryLocation()

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

Relationship: PORX_MT020060CA.Destination2.serviceDeliveryLocation

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060010CA.Destination2.serviceDeliveryLocation

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060040CA.Destination2.serviceDeliveryLocation

Conformance/Cardinality: POPULATED (1)

setDestinationServiceDeliveryLocation

public void setDestinationServiceDeliveryLocation(DispenseShipToLocationBean destinationServiceDeliveryLocation)

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

Relationship: PORX_MT020060CA.Destination2.serviceDeliveryLocation

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060010CA.Destination2.serviceDeliveryLocation

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060040CA.Destination2.serviceDeliveryLocation

Conformance/Cardinality: POPULATED (1)

getReceiverPersonalRelationship

public RelatedPersonBean getReceiverPersonalRelationship()

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

Relationship: PORX_MT060010CA.Receiver2.personalRelationship

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060040CA.Receiver2.personalRelationship

Conformance/Cardinality: POPULATED (1)

setReceiverPersonalRelationship

public void setReceiverPersonalRelationship(RelatedPersonBean receiverPersonalRelationship)

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

Relationship: PORX_MT060010CA.Receiver2.personalRelationship

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060040CA.Receiver2.personalRelationship

Conformance/Cardinality: POPULATED (1)