|
||||||||||
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.ConsistsOfBean
public class ConsistsOfBean
Business Name: ConsistsOf
PORX_MT980040CA.Component17: b:consists of
Dosage instructions may be given as textual information (as in Ad-hoc Dosage Instructions specified above) or as a structured set of dosage lines. This association allows for the specification of structured dosage lines.
Structured dosage lines facilitate the checking of dosage appropriateness. It also allows for the formal calculation of days supply based on administration instructions and supplied quantity.
COCT_MT270010CA.Component17: b:consists of
Dosage instructions may be given as textual information (as in Ad-hoc Dosage Instructions specified above) or as a structured set of dosage lines. This association allows for the specification of structured dosage lines.
Structured dosage lines facilitate the checking of dosage appropriateness. It also allows for the formal calculation of days supply based on administration instructions and supplied quantity.
Constructor Summary | |
---|---|
ConsistsOfBean()
|
Method Summary | |
---|---|
StructuredDosageLinesBean |
getDosageLine()
Un-merged Business Name: (no business name specified) |
Integer |
getSequenceNumber()
Business Name: DosageLineOrder |
void |
setDosageLine(StructuredDosageLinesBean dosageLine)
Un-merged Business Name: (no business name specified) |
void |
setSequenceNumber(Integer sequenceNumber)
Business Name: DosageLineOrder |
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 ConsistsOfBean()
Method Detail |
---|
public Integer getSequenceNumber()
Business Name: DosageLineOrder
Un-merged Business Name: DosageLineOrder
Relationship: PORX_MT980040CA.Component17.sequenceNumber
Conformance/Cardinality: MANDATORY (1)
Indicates the order in which dosage lines should be performed. Ensures that each step of multiple and complex SIGs (e.g ramp up/down) is in the desired order. Dosage lines with the same sequence number should be performed in parallel. E.g. 2 tabs tid for 3 days (sequence 1) and then 1 tab tid for 4 days (sequence 2) E.g. 1 tab in the morning (sequence 1) and 2 tabs at bedtime (sequence 1)
ZDP.13.10
Clearly expresses the order of each dosage line to ensure the correct dosage is given. Element is mandatory to ensure that dosage lines are specified and followed in the order intended.
Need examples to illustrate use of sequence lines with 'ANDs' and 'THENs'.
Un-merged Business Name: DosageLineOrder
Relationship: COCT_MT270010CA.Component17.sequenceNumber
Conformance/Cardinality: MANDATORY (1)
Indicates the order in which dosage lines should be performed. Ensures that each step of multiple and complex SIGs (e.g ramp up/down) is in the desired order. Dosage lines with the same sequence number should be performed in parallel. E.g. 2 tabs tid for 3 days (sequence 1) and then 1 tab tid for 4 days (sequence 2) E.g. 1 tab in the morning (sequence 1) and 2 tabs at bedtime (sequence 1)
ZDP.13.10
Clearly expresses the order of each dosage line to ensure the correct dosage is given. Element is mandatory to ensure that dosage lines are specified and followed in the order intended.
Need examples to illustrate use of sequence lines with 'ANDs' and 'THENs'.
public void setSequenceNumber(Integer sequenceNumber)
Business Name: DosageLineOrder
Un-merged Business Name: DosageLineOrder
Relationship: PORX_MT980040CA.Component17.sequenceNumber
Conformance/Cardinality: MANDATORY (1)
Indicates the order in which dosage lines should be performed. Ensures that each step of multiple and complex SIGs (e.g ramp up/down) is in the desired order. Dosage lines with the same sequence number should be performed in parallel. E.g. 2 tabs tid for 3 days (sequence 1) and then 1 tab tid for 4 days (sequence 2) E.g. 1 tab in the morning (sequence 1) and 2 tabs at bedtime (sequence 1)
ZDP.13.10
Clearly expresses the order of each dosage line to ensure the correct dosage is given. Element is mandatory to ensure that dosage lines are specified and followed in the order intended.
Need examples to illustrate use of sequence lines with 'ANDs' and 'THENs'.
Un-merged Business Name: DosageLineOrder
Relationship: COCT_MT270010CA.Component17.sequenceNumber
Conformance/Cardinality: MANDATORY (1)
Indicates the order in which dosage lines should be performed. Ensures that each step of multiple and complex SIGs (e.g ramp up/down) is in the desired order. Dosage lines with the same sequence number should be performed in parallel. E.g. 2 tabs tid for 3 days (sequence 1) and then 1 tab tid for 4 days (sequence 2) E.g. 1 tab in the morning (sequence 1) and 2 tabs at bedtime (sequence 1)
ZDP.13.10
Clearly expresses the order of each dosage line to ensure the correct dosage is given. Element is mandatory to ensure that dosage lines are specified and followed in the order intended.
Need examples to illustrate use of sequence lines with 'ANDs' and 'THENs'.
public StructuredDosageLinesBean getDosageLine()
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT980040CA.Component17.dosageLine
Conformance/Cardinality: POPULATED (1)
Un-merged Business Name: (no business name specified)
Relationship: COCT_MT270010CA.Component17.dosageLine
Conformance/Cardinality: POPULATED (1)
public void setDosageLine(StructuredDosageLinesBean dosageLine)
Un-merged Business Name: (no business name specified)
Relationship: PORX_MT980040CA.Component17.dosageLine
Conformance/Cardinality: POPULATED (1)
Un-merged Business Name: (no business name specified)
Relationship: COCT_MT270010CA.Component17.dosageLine
Conformance/Cardinality: POPULATED (1)
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |