|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Objectca.infoway.messagebuilder.model.MessagePartBean
ca.infoway.messagebuilder.model.ab_mr2007_v02_r02.merged.AdministrationInstructionsBean
public class AdministrationInstructionsBean
Business Name: AdministrationInstructions
PORX_MT980040CA.DosageInstruction: Administration Instructions
routeCode is mandatory and apporachSiteCode is required if not using SNOMED
- moodCode must be DEFN for drug definitions (such as monographs) - moodCode must be RQO for orders; - moodCode must be EVN for dispenses and recording of other medications
routeCode is mandatory and apporachSiteCode is required if not using SNOMED
- moodCode must be DEFN for drug definitions (such as monographs) - moodCode must be RQO for orders; - moodCode must be EVN for dispenses and recording of other medications
This comprises all specifications necessary for the dispensed product to be administered to/by the patient in a manner as intended by the prescriber.
Allows providers to communicate intentions and to cross-check intended and actual methods of administration.
COCT_MT270010CA.DosageInstruction: Administration Instructions
routeCode is mandatory and apporachSiteCode is required if not using SNOMED
- moodCode must be DEFN for drug definitions (such as monographs) - moodCode must be RQO for orders; - moodCode must be EVN for dispenses and recording of other medications
routeCode is mandatory and apporachSiteCode is required if not using SNOMED
- moodCode must be DEFN for drug definitions (such as monographs) - moodCode must be RQO for orders; - moodCode must be EVN for dispenses and recording of other medications
This comprises all specifications necessary for the dispensed product to be administered to/by the patient in a manner as intended by the prescriber.
Allows providers to communicate intentions and to cross-check intended and actual methods of administration.
Constructor Summary | |
---|---|
AdministrationInstructionsBean()
|
Method Summary | |
---|---|
AdministrableDrugForm |
getAdministrationUnitCode()
Business Name: DosageUnit |
Set<HumanSubstanceAdministrationSite> |
getApproachSiteCode()
Business Name: AdministrationSites |
ActCode |
getCode()
Business Name: DosageType |
AdditionalSIGInstructionBean |
getComponent1SupplementalInstruction()
Un-merged Business Name: (no business name specified) |
List<ConsistsOfBean> |
getComponent2()
Un-merged Business Name: (no business name specified) |
Medication |
getConsumableMedication1()
Un-merged Business Name: (no business name specified) |
Interval<Date> |
getEffectiveTime()
Business Name: AdministrationPeriod |
Set<Ratio<PhysicalQuantity,PhysicalQuantity>> |
getMaxDoseQuantity()
Un-merged Business Name: MaximumDosesPerPeriod |
x_ActMoodDefEvnRqo |
getMoodCode()
Business Name: DosageUsageContext |
RouteOfAdministration |
getRouteCode()
Business Name: RouteCode |
String |
getText()
Business Name: RenderedDosageInstruction |
void |
setAdministrationUnitCode(AdministrableDrugForm administrationUnitCode)
Business Name: DosageUnit |
void |
setCode(ActCode code)
Business Name: DosageType |
void |
setComponent1SupplementalInstruction(AdditionalSIGInstructionBean component1SupplementalInstruction)
Un-merged Business Name: (no business name specified) |
void |
setConsumableMedication1(Medication consumableMedication1)
Un-merged Business Name: (no business name specified) |
void |
setEffectiveTime(Interval<Date> effectiveTime)
Business Name: AdministrationPeriod |
void |
setMoodCode(x_ActMoodDefEvnRqo moodCode)
Business Name: DosageUsageContext |
void |
setRouteCode(RouteOfAdministration routeCode)
Business Name: RouteCode |
void |
setText(String text)
Business Name: RenderedDosageInstruction |
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 AdministrationInstructionsBean()
Method Detail |
---|
public x_ActMoodDefEvnRqo getMoodCode()
Business Name: DosageUsageContext
Un-merged Business Name: DosageUsageContext
Relationship: PORX_MT980040CA.DosageInstruction.moodCode
Conformance/Cardinality: MANDATORY (1)
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Puts the class in context, and is therefore mandatory.
Un-merged Business Name: DosageUsageContext
Relationship: COCT_MT270010CA.DosageInstruction.moodCode
Conformance/Cardinality: MANDATORY (1)
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Puts the class in context, and is therefore mandatory.
public void setMoodCode(x_ActMoodDefEvnRqo moodCode)
Business Name: DosageUsageContext
Un-merged Business Name: DosageUsageContext
Relationship: PORX_MT980040CA.DosageInstruction.moodCode
Conformance/Cardinality: MANDATORY (1)
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Puts the class in context, and is therefore mandatory.
Un-merged Business Name: DosageUsageContext
Relationship: COCT_MT270010CA.DosageInstruction.moodCode
Conformance/Cardinality: MANDATORY (1)
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Indicates the context of the administration.
moodCode = RQO, for administration instruction on orders
moodCode = EVN, for administration instruction on dispenses
moodCode = DEF, for administration instruction on medication definition documents/references (typically, monographs).
Puts the class in context, and is therefore mandatory.
public ActCode getCode()
Business Name: DosageType
Un-merged Business Name: DosageType
Relationship: PORX_MT980040CA.DosageInstruction.code
Conformance/Cardinality: MANDATORY (1)
Distinguishes types of dosage.
Distinguishes between types of dosage administration and is therefore mandatory. Datatype is CD to allow for SNOMED codes.
For SNOMED this will pre-coordinate route, body site and potentially drug. For non-SNOMED, this will be a fixed value of DRUG.
Un-merged Business Name: DosageType
Relationship: COCT_MT270010CA.DosageInstruction.code
Conformance/Cardinality: MANDATORY (1)
Distinguishes types of dosage.
Distinguishes between types of dosage administration and is therefore mandatory. Datatype is CD to allow for SNOMED codes.
For SNOMED this will pre-coordinate route, body site and potentially drug. For non-SNOMED, this will be a fixed value of DRUG.
public void setCode(ActCode code)
Business Name: DosageType
Un-merged Business Name: DosageType
Relationship: PORX_MT980040CA.DosageInstruction.code
Conformance/Cardinality: MANDATORY (1)
Distinguishes types of dosage.
Distinguishes between types of dosage administration and is therefore mandatory. Datatype is CD to allow for SNOMED codes.
For SNOMED this will pre-coordinate route, body site and potentially drug. For non-SNOMED, this will be a fixed value of DRUG.
Un-merged Business Name: DosageType
Relationship: COCT_MT270010CA.DosageInstruction.code
Conformance/Cardinality: MANDATORY (1)
Distinguishes types of dosage.
Distinguishes between types of dosage administration and is therefore mandatory. Datatype is CD to allow for SNOMED codes.
For SNOMED this will pre-coordinate route, body site and potentially drug. For non-SNOMED, this will be a fixed value of DRUG.
public String getText()
Business Name: RenderedDosageInstruction
Un-merged Business Name: RenderedDosageInstruction
Relationship: PORX_MT980040CA.DosageInstruction.text
Conformance/Cardinality: MANDATORY (1)
A free form textual specification generated from the input specifications as created by the provider.
This is made up of either an 'Ad-hoc dosage instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider.
A free form textual specification generated from the input specifications as created by the provider.
This is made up of either an 'Ad-hoc dosage instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider.
Allows the provider to verify the codified structured dosage information entered and ensure that the exploded instruction is consistent with the intended instructions.
Also useful in bringing back administration instructions on query responses.
This is mandatory as dosage instructions must always be available in rendered form.
Allows the provider to verify the codified structured dosage information entered and ensure that the exploded instruction is consistent with the intended instructions.
Also useful in bringing back administration instructions on query responses.
This is mandatory as dosage instructions must always be available in rendered form.
Allows the provider to verify the codified structured dosage information entered and ensure that the exploded instruction is consistent with the intended instructions.
Also useful in bringing back administration instructions on query responses.
This is mandatory as dosage instructions must always be available in rendered form.
Un-merged Business Name: RenderedDosageInstruction
Relationship: COCT_MT270010CA.DosageInstruction.text
Conformance/Cardinality: MANDATORY (1)
A free form textual specification generated from the input specifications as created by the provider.
This is made up of either an 'Ad-hoc dosage instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider.
A free form textual specification generated from the input specifications as created by the provider.
This is made up of either an 'Ad-hoc dosage instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider.
Allows the provider to verify the codified structured dosage information entered and ensure that the exploded instruction is consistent with the intended instructions.
Also useful in bringing back administration instructions on query responses.
This is mandatory as dosage instructions must always be available in rendered form.
Allows the provider to verify the codified structured dosage information entered and ensure that the exploded instruction is consistent with the intended instructions.
Also useful in bringing back administration instructions on query responses.
This is mandatory as dosage instructions must always be available in rendered form.
Allows the provider to verify the codified structured dosage information entered and ensure that the exploded instruction is consistent with the intended instructions.
Also useful in bringing back administration instructions on query responses.
This is mandatory as dosage instructions must always be available in rendered form.
public void setText(String text)
Business Name: RenderedDosageInstruction
Un-merged Business Name: RenderedDosageInstruction
Relationship: PORX_MT980040CA.DosageInstruction.text
Conformance/Cardinality: MANDATORY (1)
A free form textual specification generated from the input specifications as created by the provider.
This is made up of either an 'Ad-hoc dosage instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider.
A free form textual specification generated from the input specifications as created by the provider.
This is made up of either an 'Ad-hoc dosage instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider.
Allows the provider to verify the codified structured dosage information entered and ensure that the exploded instruction is consistent with the intended instructions.
Also useful in bringing back administration instructions on query responses.
This is mandatory as dosage instructions must always be available in rendered form.
Allows the provider to verify the codified structured dosage information entered and ensure that the exploded instruction is consistent with the intended instructions.
Also useful in bringing back administration instructions on query responses.
This is mandatory as dosage instructions must always be available in rendered form.
Allows the provider to verify the codified structured dosage information entered and ensure that the exploded instruction is consistent with the intended instructions.
Also useful in bringing back administration instructions on query responses.
This is mandatory as dosage instructions must always be available in rendered form.
Un-merged Business Name: RenderedDosageInstruction
Relationship: COCT_MT270010CA.DosageInstruction.text
Conformance/Cardinality: MANDATORY (1)
A free form textual specification generated from the input specifications as created by the provider.
This is made up of either an 'Ad-hoc dosage instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider.
A free form textual specification generated from the input specifications as created by the provider.
This is made up of either an 'Ad-hoc dosage instruction' or 'Textual rendition of the structured dosage lines', plus route, dosage unit, and other pertinent administration information specified by the provider.
Allows the provider to verify the codified structured dosage information entered and ensure that the exploded instruction is consistent with the intended instructions.
Also useful in bringing back administration instructions on query responses.
This is mandatory as dosage instructions must always be available in rendered form.
Allows the provider to verify the codified structured dosage information entered and ensure that the exploded instruction is consistent with the intended instructions.
Also useful in bringing back administration instructions on query responses.
This is mandatory as dosage instructions must always be available in rendered form.
Allows the provider to verify the codified structured dosage information entered and ensure that the exploded instruction is consistent with the intended instructions.
Also useful in bringing back administration instructions on query responses.
This is mandatory as dosage instructions must always be available in rendered form.
public Interval<Date> getEffectiveTime()
Business Name: AdministrationPeriod
Un-merged Business Name: AdministrationPeriod
Relationship: PORX_MT980040CA.DosageInstruction.effectiveTime
Conformance/Cardinality: REQUIRED (0-1)
The time period (begin and end dates) within which the dispensed medication is to be completely administered to/by the patient. May differ from date prescription was issued.
Prescription.Admin istrationStartDate (Low)
Prescription.Admin istrationStopDate (High)
DispensedItem.expectedStartDate
Prescription.Admin istrationStartDate (Low)
Prescription.Admin istrationStopDate (High)
DispensedItem.expectedStartDate
Prescription.Admin istrationStartDate (Low)
Prescription.Admin istrationStopDate (High)
DispensedItem.expectedStartDate
Indicates the overall time boundaries in which the person is expected to take the drug. Denotes the reference point for calculating expected exhaustion date and quantity on hand.
Facilitates compliance checking.
Note: TID may be interpreted differently based on situation (e.g. based on schedules of a facility).
Indicates the overall time boundaries in which the person is expected to take the drug. Denotes the reference point for calculating expected exhaustion date and quantity on hand.
Facilitates compliance checking.
Note: TID may be interpreted differently based on situation (e.g. based on schedules of a facility).
Indicates the overall time boundaries in which the person is expected to take the drug. Denotes the reference point for calculating expected exhaustion date and quantity on hand.
Facilitates compliance checking.
Note: TID may be interpreted differently based on situation (e.g. based on schedules of a facility).
Frequently only the duration (width) component is specified. E.g. 100mg tid for 10 days. In that case, the start date is presumed to be the date the prescription was written
Un-merged Business Name: AdministrationPeriod
Relationship: COCT_MT270010CA.DosageInstruction.effectiveTime
Conformance/Cardinality: REQUIRED (0-1)
The time period (begin and end dates) within which the dispensed medication is to be completely administered to/by the patient. May differ from date prescription was issued.
Prescription.Admin istrationStartDate (Low)
Prescription.Admin istrationStopDate (High)
DispensedItem.expectedStartDate
Prescription.Admin istrationStartDate (Low)
Prescription.Admin istrationStopDate (High)
DispensedItem.expectedStartDate
Prescription.Admin istrationStartDate (Low)
Prescription.Admin istrationStopDate (High)
DispensedItem.expectedStartDate
Indicates the overall time boundaries in which the person is expected to take the drug. Denotes the reference point for calculating expected exhaustion date and quantity on hand.
Facilitates compliance checking.
Note: TID may be interpreted differently based on situation (e.g. based on schedules of a facility).
Indicates the overall time boundaries in which the person is expected to take the drug. Denotes the reference point for calculating expected exhaustion date and quantity on hand.
Facilitates compliance checking.
Note: TID may be interpreted differently based on situation (e.g. based on schedules of a facility).
Indicates the overall time boundaries in which the person is expected to take the drug. Denotes the reference point for calculating expected exhaustion date and quantity on hand.
Facilitates compliance checking.
Note: TID may be interpreted differently based on situation (e.g. based on schedules of a facility).
Frequently only the duration (width) component is specified. E.g. 100mg tid for 10 days. In that case, the start date is presumed to be the date the prescription was written
public void setEffectiveTime(Interval<Date> effectiveTime)
Business Name: AdministrationPeriod
Un-merged Business Name: AdministrationPeriod
Relationship: PORX_MT980040CA.DosageInstruction.effectiveTime
Conformance/Cardinality: REQUIRED (0-1)
The time period (begin and end dates) within which the dispensed medication is to be completely administered to/by the patient. May differ from date prescription was issued.
Prescription.Admin istrationStartDate (Low)
Prescription.Admin istrationStopDate (High)
DispensedItem.expectedStartDate
Prescription.Admin istrationStartDate (Low)
Prescription.Admin istrationStopDate (High)
DispensedItem.expectedStartDate
Prescription.Admin istrationStartDate (Low)
Prescription.Admin istrationStopDate (High)
DispensedItem.expectedStartDate
Indicates the overall time boundaries in which the person is expected to take the drug. Denotes the reference point for calculating expected exhaustion date and quantity on hand.
Facilitates compliance checking.
Note: TID may be interpreted differently based on situation (e.g. based on schedules of a facility).
Indicates the overall time boundaries in which the person is expected to take the drug. Denotes the reference point for calculating expected exhaustion date and quantity on hand.
Facilitates compliance checking.
Note: TID may be interpreted differently based on situation (e.g. based on schedules of a facility).
Indicates the overall time boundaries in which the person is expected to take the drug. Denotes the reference point for calculating expected exhaustion date and quantity on hand.
Facilitates compliance checking.
Note: TID may be interpreted differently based on situation (e.g. based on schedules of a facility).
Frequently only the duration (width) component is specified. E.g. 100mg tid for 10 days. In that case, the start date is presumed to be the date the prescription was written
Un-merged Business Name: AdministrationPeriod
Relationship: COCT_MT270010CA.DosageInstruction.effectiveTime
Conformance/Cardinality: REQUIRED (0-1)
The time period (begin and end dates) within which the dispensed medication is to be completely administered to/by the patient. May differ from date prescription was issued.
Prescription.Admin istrationStartDate (Low)
Prescription.Admin istrationStopDate (High)
DispensedItem.expectedStartDate
Prescription.Admin istrationStartDate (Low)
Prescription.Admin istrationStopDate (High)
DispensedItem.expectedStartDate
Prescription.Admin istrationStartDate (Low)
Prescription.Admin istrationStopDate (High)
DispensedItem.expectedStartDate
Indicates the overall time boundaries in which the person is expected to take the drug. Denotes the reference point for calculating expected exhaustion date and quantity on hand.
Facilitates compliance checking.
Note: TID may be interpreted differently based on situation (e.g. based on schedules of a facility).
Indicates the overall time boundaries in which the person is expected to take the drug. Denotes the reference point for calculating expected exhaustion date and quantity on hand.
Facilitates compliance checking.
Note: TID may be interpreted differently based on situation (e.g. based on schedules of a facility).
Indicates the overall time boundaries in which the person is expected to take the drug. Denotes the reference point for calculating expected exhaustion date and quantity on hand.
Facilitates compliance checking.
Note: TID may be interpreted differently based on situation (e.g. based on schedules of a facility).
Frequently only the duration (width) component is specified. E.g. 100mg tid for 10 days. In that case, the start date is presumed to be the date the prescription was written
public RouteOfAdministration getRouteCode()
Business Name: RouteCode
Un-merged Business Name: RouteCode
Relationship: PORX_MT980040CA.DosageInstruction.routeCode
Conformance/Cardinality: OPTIONAL (0-1)
This is the means by which the dispensed drug is to be administered to the patient.
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Ensures consistency in description of routes. Provides potential for cross-checking dosage form and route. Route is an optional because it is pre-coordinated with SubstanceAdministration.code when using SNOMED.
Un-merged Business Name: RouteCode
Relationship: COCT_MT270010CA.DosageInstruction.routeCode
Conformance/Cardinality: OPTIONAL (0-1)
This is the means by which the dispensed drug is to be administered to the patient.
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Ensures consistency in description of routes. Provides potential for cross-checking dosage form and route. Route is an optional because it is pre-coordinated with SubstanceAdministration.code when using SNOMED.
public void setRouteCode(RouteOfAdministration routeCode)
Business Name: RouteCode
Un-merged Business Name: RouteCode
Relationship: PORX_MT980040CA.DosageInstruction.routeCode
Conformance/Cardinality: OPTIONAL (0-1)
This is the means by which the dispensed drug is to be administered to the patient.
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Ensures consistency in description of routes. Provides potential for cross-checking dosage form and route. Route is an optional because it is pre-coordinated with SubstanceAdministration.code when using SNOMED.
Un-merged Business Name: RouteCode
Relationship: COCT_MT270010CA.DosageInstruction.routeCode
Conformance/Cardinality: OPTIONAL (0-1)
This is the means by which the dispensed drug is to be administered to the patient.
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Prescription.route
ZDP.14.2
Compound.452-E8
RXR.1
Ensures consistency in description of routes. Provides potential for cross-checking dosage form and route. Route is an optional because it is pre-coordinated with SubstanceAdministration.code when using SNOMED.
public Set<HumanSubstanceAdministrationSite> getApproachSiteCode()
Business Name: AdministrationSites
Un-merged Business Name: AdministrationSites
Relationship: PORX_MT980040CA.DosageInstruction.approachSiteCode
Conformance/Cardinality: OPTIONAL (0-5)
A value denoting the body area where the medicine should be administered. E.g. 'Right Elbow', 'Left Ear'. When multiples sites are specified they should be treated as 'AND'.
Allows specificity when a drug can potentially be applied to different parts of the patien's body. Multiple repetitions are used when the product should be administered to multiple parts of the body. CWE is used because using a code system is not essential for understanding or analyzing the prescription. The attribute is optional because it can be pre-coordinated with SubstanceAdministration.code when using SNOMED.
Un-merged Business Name: AdministrationSites
Relationship: COCT_MT270010CA.DosageInstruction.approachSiteCode
Conformance/Cardinality: OPTIONAL (0-5)
A value denoting the body area where the medicine should be administered. E.g. 'Right Elbow', 'Left Ear'. When multiples sites are specified they should be treated as 'AND'.
Allows specificity when a drug can potentially be applied to different parts of the patien's body. Multiple repetitions are used when the product should be administered to multiple parts of the body. CWE is used because using a code system is not essential for understanding or analyzing the prescription. The attribute is optional because it can be pre-coordinated with SubstanceAdministration.code when using SNOMED.
public Set<Ratio<PhysicalQuantity,PhysicalQuantity>> getMaxDoseQuantity()
Un-merged Business Name: MaximumDosesPerPeriod
Relationship: PORX_MT980040CA.DosageInstruction.maxDoseQuantity
Conformance/Cardinality: REQUIRED (0-2)
The maximum amount of the dispensed medication to be administered to the patient in a specified period of time. Examples include: per hour, 24-hr period (doses per day), 7 day period (doses per week), yearly.
ZPB3.5(denominator=1D)
Sets an upper boundary for the quantity of the drug to be administered over a specified period of time. Particularly useful for PRN medications.
This field can only capture maximum doses based on explicit time periods. Dosage maximums based on other constraints such as patient lifetime, menstrual cycles must be recorded using additional dosage instruction comments.
Un-merged Business Name: MaximumDailyWeeklyDoses
Relationship: COCT_MT270010CA.DosageInstruction.maxDoseQuantity
Conformance/Cardinality: REQUIRED (0-2)
The maximum amount of the dispensed medication to be administered to the patient in a 24-hr period (doses per day) or in a 7 day period (doses per week).
ZPB3.5(denominator=1D)
Sets an upper boundary for the quantity of the drug to be administered over a specified period of time. Particularly useful for PRN medications.
This field can only capture maximum doses based on explicit time periods. Dosage maximums based on other constraints such as patient lifetime, menstrual cycles must be recorded using additional dosage instruction comments.
public AdministrableDrugForm getAdministrationUnitCode()
Business Name: DosageUnit
Un-merged Business Name: DosageUnit
Relationship: PORX_MT980040CA.DosageInstruction.administrationUnitCode
Conformance/Cardinality: REQUIRED (0-1)
Identifies how the drug is measured for administration.
Specified when not implicit from the drug form (e.g. puff, inhalation, drops, etc.).
Identifies how the drug is measured for administration.
Specified when not implicit from the drug form (e.g. puff, inhalation, drops, etc.).
Needed when the dosage unit is not expressed as part of the dose quantity (mg, mL) or implicit as part of the drug form (capsules, tablets). Examples are Puffs, Actuations, etc.
Un-merged Business Name: DosageUnit
Relationship: COCT_MT270010CA.DosageInstruction.administrationUnitCode
Conformance/Cardinality: REQUIRED (0-1)
Identifies how the drug is measured for administration.
Specified when not implicit from the drug form (e.g. puff, inhalation, drops, etc.).
Identifies how the drug is measured for administration.
Specified when not implicit from the drug form (e.g. puff, inhalation, drops, etc.).
Needed when the dosage unit is not expressed as part of the dose quantity (mg, mL) or implicit as part of the drug form (capsules, tablets). Examples are Puffs, Actuations, etc.
public void setAdministrationUnitCode(AdministrableDrugForm administrationUnitCode)
Business Name: DosageUnit
Un-merged Business Name: DosageUnit
Relationship: PORX_MT980040CA.DosageInstruction.administrationUnitCode
Conformance/Cardinality: REQUIRED (0-1)
Identifies how the drug is measured for administration.
Specified when not implicit from the drug form (e.g. puff, inhalation, drops, etc.).
Identifies how the drug is measured for administration.
Specified when not implicit from the drug form (e.g. puff, inhalation, drops, etc.).
Needed when the dosage unit is not expressed as part of the dose quantity (mg, mL) or implicit as part of the drug form (capsules, tablets). Examples are Puffs, Actuations, etc.
Un-merged Business Name: DosageUnit
Relationship: COCT_MT270010CA.DosageInstruction.administrationUnitCode
Conformance/Cardinality: REQUIRED (0-1)
Identifies how the drug is measured for administration.
Specified when not implicit from the drug form (e.g. puff, inhalation, drops, etc.).
Identifies how the drug is measured for administration.
Specified when not implicit from the drug form (e.g. puff, inhalation, drops, etc.).
Needed when the dosage unit is not expressed as part of the dose quantity (mg, mL) or implicit as part of the drug form (capsules, tablets). Examples are Puffs, Actuations, etc.
public Medication getConsumableMedication1()
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT980040CA.Consumable1.medication1
Conformance/Cardinality: POPULATED (1)
Un-merged Business Name: (no business name specified)
Relationship: COCT_MT270010CA.Consumable1.medication1
Conformance/Cardinality: POPULATED (1)
public void setConsumableMedication1(Medication consumableMedication1)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT980040CA.Consumable1.medication1
Conformance/Cardinality: POPULATED (1)
Un-merged Business Name: (no business name specified)
Relationship: COCT_MT270010CA.Consumable1.medication1
Conformance/Cardinality: POPULATED (1)
public AdditionalSIGInstructionBean getComponent1SupplementalInstruction()
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT980040CA.Component.supplementalInstruction
Conformance/Cardinality: POPULATED (1)
Un-merged Business Name: (no business name specified)
Relationship: COCT_MT270010CA.Component.supplementalInstruction
Conformance/Cardinality: POPULATED (1)
public void setComponent1SupplementalInstruction(AdditionalSIGInstructionBean component1SupplementalInstruction)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT980040CA.Component.supplementalInstruction
Conformance/Cardinality: POPULATED (1)
Un-merged Business Name: (no business name specified)
Relationship: COCT_MT270010CA.Component.supplementalInstruction
Conformance/Cardinality: POPULATED (1)
public List<ConsistsOfBean> getComponent2()
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT980040CA.DosageInstruction.component2
Conformance/Cardinality: REQUIRED (0-20)
Un-merged Business Name: (no business name specified)
Relationship: COCT_MT270010CA.DosageInstruction.component2
Conformance/Cardinality: REQUIRED (0-20)
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |