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

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

All Implemented Interfaces:

NullFlavorSupport, Serializable

public class SupplyEventBean
extends MessagePartBean

See Also:

Serialized Form

Constructor Summary

SupplyEventBean()

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() Business Name: DispensedDaysSupply
DrugProductBean	getProductMedication() Un-merged Business Name: (no business name specified)
PhysicalQuantity	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) Business Name: DispensedDaysSupply
void	setProductMedication(DrugProductBean productMedication) Un-merged Business Name: (no business name specified)
void	setQuantity(PhysicalQuantity 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

SupplyEventBean

public SupplyEventBean()

Method Detail

getCode

public ActPharmacySupplyType getCode()

Business Name: DispenseType

Un-merged Business Name: DispenseType

Relationship: PORX_MT060090CA.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_MT060090CA.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_MT060090CA.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_MT060100CA.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.

setEffectiveTime

public void setEffectiveTime(Interval<Date> effectiveTime)

Business Name: DispenseProcessingAndPickupDate

Un-merged Business Name: DispenseProcessingAndPickupDate

Relationship: PORX_MT060090CA.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_MT060100CA.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.

getQuantity

public PhysicalQuantity getQuantity()

Business Name: DispensedQuantity

Un-merged Business Name: DispensedQuantity

Relationship: PORX_MT060090CA.SupplyEvent.quantity

Conformance/Cardinality: MANDATORY (1)

The amount of medication that has been dispensed. Includes unit of measure.

Critical in understanding the patient's medication 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_MT060100CA.SupplyEvent.quantity

Conformance/Cardinality: MANDATORY (1)

The amount of medication that has been dispensed. Includes unit of measure.

Critical in understanding the patient's medication 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(PhysicalQuantity quantity)

Business Name: DispensedQuantity

Un-merged Business Name: DispensedQuantity

Relationship: PORX_MT060090CA.SupplyEvent.quantity

Conformance/Cardinality: MANDATORY (1)

The amount of medication that has been dispensed. Includes unit of measure.

Critical in understanding the patient's medication 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_MT060100CA.SupplyEvent.quantity

Conformance/Cardinality: MANDATORY (1)

The amount of medication that has been dispensed. Includes unit of measure.

Critical in understanding the patient's medication 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()

Business Name: DispensedDaysSupply

Un-merged Business Name: DispensedDaysSupply

Relationship: PORX_MT060090CA.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: DispensedDaysSupply

Relationship: PORX_MT060100CA.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.

setExpectedUseTime

public void setExpectedUseTime(Interval<Date> expectedUseTime)

Business Name: DispensedDaysSupply

Un-merged Business Name: DispensedDaysSupply

Relationship: PORX_MT060090CA.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: DispensedDaysSupply

Relationship: PORX_MT060100CA.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.

getProductMedication

public DrugProductBean getProductMedication()

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

Relationship: PORX_MT060090CA.Product2.medication

Conformance/Cardinality: MANDATORY (1)

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

Relationship: PORX_MT060100CA.Product2.medication

Conformance/Cardinality: MANDATORY (1)

setProductMedication

public void setProductMedication(DrugProductBean productMedication)

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

Relationship: PORX_MT060090CA.Product2.medication

Conformance/Cardinality: MANDATORY (1)

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

Relationship: PORX_MT060100CA.Product2.medication

Conformance/Cardinality: MANDATORY (1)

getReceiverPersonalRelationship

public RelatedPersonBean getReceiverPersonalRelationship()

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

Relationship: PORX_MT060090CA.Receiver2.personalRelationship

Conformance/Cardinality: POPULATED (1)

setReceiverPersonalRelationship

public void setReceiverPersonalRelationship(RelatedPersonBean receiverPersonalRelationship)

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

Relationship: PORX_MT060090CA.Receiver2.personalRelationship

Conformance/Cardinality: POPULATED (1)

getDestinationServiceDeliveryLocation

public DispenseShipToLocationBean getDestinationServiceDeliveryLocation()

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

Relationship: PORX_MT060090CA.Destination2.serviceDeliveryLocation

Conformance/Cardinality: POPULATED (1)

setDestinationServiceDeliveryLocation

public void setDestinationServiceDeliveryLocation(DispenseShipToLocationBean destinationServiceDeliveryLocation)

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

Relationship: PORX_MT060090CA.Destination2.serviceDeliveryLocation

Conformance/Cardinality: POPULATED (1)