ca.infoway.messagebuilder.model.pcs_mr2009_r02_04_02.merged
Class BecauseOfBean

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

public class BecauseOfBean
extends MessagePartBean

REPC_MT230003CA.Reason: *m:because of Indications

Essential for understanding the context in which the action was performed. Also frequently used in searching and filtering and can impact whether the record will be automatically masked. Multiple indications are supported for circumstances where the Clinical Observation Document is being done for multiple reasons.

Identifies the clinical reason(s) for performing the action described by the record.

REPC_MT410001CA.Reason: *j:because of

Essential for understanding the context in which the action was performed. Also frequently used in searching and filtering and can impact whether the record will be automatically masked. Multiple indications are supported for circumstances where the Measured Observation is being done for multiple reasons.

Identifies the clinical reason(s) for performing the action described by the record.

POME_MT010040CA.Reason: recommended for

Useful in prescribing by narrowing selectable drugs based on specified indication.

Recommends which drugs are to be used for which indications.

PORX_MT060190CA.Reason: d:prescribed because of

Helps providers evaluate the appropriateness of the dosage instructions for the medication, and may influence education or literature provided to the patient on the use of the medication.

Provided at the discretion of the prescriber to enhance patient care. E.g., take 1 tab bid for migraine. Also needed for drug-disease interaction checking software to work properly.

This field is marked as populated because of its high clinical importance, however 'Nulls' are allowed because the individual recording the prescription (e.g. pharmacist) may not be aware of the indication or the prescriber may choose to withhold (mask) the information due to patient sensitivity.

Denotes the reason(s) for this specific prescription; it must not be interpreted as a permanent diagnosis.

REPC_MT230001CA.Reason: *m:because of Indications

Essential for understanding the context in which the action was performed. Also frequently used in searching and filtering and can impact whether the record will be automatically masked. Multiple indications are supported for circumstances where the Clinical Observation Document is being done for multiple reasons.

Identifies the clinical reason(s) for performing the action described by the record.

REPC_MT220003CA.Reason: *m:because of Indications

Essential for understanding the context in which the action was performed. Also frequently used in searching and filtering and can impact whether the record will be automatically masked. Multiple indications are supported for circumstances where the Discharge-Care Summary is being done for multiple reasons.

Identifies the clinical reason(s) for performing the action described by the record.

REPC_MT220002CA.Reason: *m:because of Indications

Essential for understanding the context in which the action was performed. Also frequently used in searching and filtering and can impact whether the record will be automatically masked. Multiple indications are supported for circumstances where the Discharge-Care Summary is being done for multiple reasons.

Identifies the clinical reason(s) for performing the action described by the record.

REPC_MT230002CA.Reason: *m:because of Indications

Essential for understanding the context in which the action was performed. Also frequently used in searching and filtering and can impact whether the record will be automatically masked. Multiple indications are supported for circumstances where the Clinical Observation Document is being done for multiple reasons.

Identifies the clinical reason(s) for performing the action described by the record.

PORX_MT060040CA.Reason2: d:prescribed because of

Helps providers evaluate the appropriateness of the instructions for the device, and may influence education or literature provided to the patient on the use of the device.

Provided at the discretion of the prescriber to enhance patient care. E.g., take 1 tab bid for migraine. Also needed for drug-disease interaction checking software to work properly.

This field is marked as populated because of its high clinical importance, however 'Nulls' are allowed because the individual recording the prescription (e.g. pharmacist) may not be aware of the indication or the prescriber may choose to withhold (mask) the information due to patient sensitivity.

Denotes the reason(s) for this specific prescription; it must not be interpreted as a permanent diagnosis.

REPC_MT210002CA.Reason: *m:because of Indications

Essential for understanding the context in which the action was performed. Also frequently used in searching and filtering and can impact whether the record will be automatically masked. Multiple indications are supported for circumstances where the Referral is being done for multiple reasons.

Identifies the clinical reason(s) for performing the action described by the record.

REPC_MT420003CA.Reason: *j:because of

Essential for understanding the context in which the action was performed. Also frequently used in searching and filtering and can impact whether the record will be automatically masked. Multiple indications are supported for circumstances where the Coded Observation is being done for multiple reasons.

Identifies the clinical reason(s) for performing the action described by the record.

PORX_MT060340CA.Reason2: d:prescribed because of

Helps providers evaluate the appropriateness of the dosage instructions for the medication, and may influence education or literature provided to the patient on the use of the medication.

Provided at the discretion of the prescriber to enhance patient care. E.g., take 1 tab bid for migraine. Also needed for drug-disease interaction checking software to work properly.

This field is marked as populated because of its high clinical importance, however 'Nulls' are allowed because the individual recording the prescription (e.g. pharmacist) may not be aware of the indication or the prescriber may choose to withhold (mask) the information due to patient sensitivity.

Denotes the reason(s) for this specific prescription; it must not be interpreted as a permanent diagnosis.

PORX_MT030040CA.Reason: d:prescribed because of

Helps providers evaluate the appropriateness of the dosage instructions for the medication, and may influence education or literature provided to the patient on the use of the medication.

Provided at the discretion of the prescriber to enhance patient care. E.g., take 1 tab bid for migraine. Also needed for drug-disease interaction checking software to work properly.

This field is marked as populated because of its high clinical importance, however 'Nulls' are allowed because the individual recording the prescription (e.g. pharmacist) may not be aware of the indication or the prescriber may choose to withhold (mask) the information due to patient sensitivity.

Denotes the reason(s) for this specific prescription; it must not be interpreted as a permanent diagnosis.

REPC_MT500001CA.Reason: k:because of

Association is mandatory, 1..1 when Care Composition Type is Episode (Health Condition-based) or a specialization there-of

Essential for understanding the context in which the action was performed. Also frequently used in searching and filtering and can impact whether the record will be automatically masked. Multiple indications are supported for circumstances where the Care Composition is being done for multiple reasons.

For health condition-based (episode) collections, there must be exactly one indication (the 'definitional' problem for the episode). For care-based collections, there should not be any indications. (Problems are captured as part of the overall care, not as the reason for care.)

Identifies the clinical reason(s) for performing the action described by the record.

REPC_MT420001CA.Reason: *j:because of

Essential for understanding the context in which the action was performed. Also frequently used in searching and filtering and can impact whether the record will be automatically masked. Multiple indications are supported for circumstances where the Coded Observation is being done for multiple reasons.

Identifies the clinical reason(s) for performing the action described by the record.

PORX_MT060060CA.Reason: d:prescribed because of

Helps providers evaluate the appropriateness of the usage instructions for the device, and may influence education ... [rest of documentation truncated due to excessive length]

See Also:
Serialized Form

Constructor Summary
BecauseOfBean()
           
 
Method Summary
 Indications getIndications()
          Un-merged Business Name: (no business name specified)
 Integer getPriorityNumber()
          Business Name: IndicationPriority
 void setIndications(Indications indications)
          Un-merged Business Name: (no business name specified)
 void setPriorityNumber(Integer priorityNumber)
          Business Name: IndicationPriority
 
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

BecauseOfBean

public BecauseOfBean()
Method Detail

getIndications

public Indications getIndications()

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

Relationship: REPC_MT410003CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT230003CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT410001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: POME_MT010040CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT230001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060190CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT220003CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT210001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT220002CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT230002CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060040CA.Reason2.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT210002CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT420003CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060340CA.Reason2.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT030040CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT500001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT420001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060060CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT500004CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT220001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT010120CA.Reason2.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT500003CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT210003CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060160CA.Reason2.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT500002CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT010110CA.Reason2.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT610002CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT610001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)


setIndications

public void setIndications(Indications indications)

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

Relationship: REPC_MT410003CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT230003CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT410001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: POME_MT010040CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT230001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060190CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT220003CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT210001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT220002CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT230002CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060040CA.Reason2.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT210002CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT420003CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060340CA.Reason2.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT030040CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT500001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT420001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060060CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT500004CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT220001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT010120CA.Reason2.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT500003CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT210003CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT060160CA.Reason2.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT500002CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: PORX_MT010110CA.Reason2.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT610002CA.Reason.indications

Conformance/Cardinality: POPULATED (1)

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

Relationship: REPC_MT610001CA.Reason.indications

Conformance/Cardinality: POPULATED (1)


getPriorityNumber

public Integer getPriorityNumber()

Business Name: IndicationPriority

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT060060CA.Reason.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT010120CA.Reason2.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT030040CA.Reason.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT060340CA.Reason2.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT060040CA.Reason2.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT060160CA.Reason2.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT060190CA.Reason.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT010110CA.Reason2.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.


setPriorityNumber

public void setPriorityNumber(Integer priorityNumber)

Business Name: IndicationPriority

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT060060CA.Reason.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT010120CA.Reason2.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT030040CA.Reason.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT060340CA.Reason2.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT060040CA.Reason2.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT060160CA.Reason2.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT060190CA.Reason.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.

Un-merged Business Name: IndicationPriority

Relationship: PORX_MT010110CA.Reason2.priorityNumber

Conformance/Cardinality: REQUIRED (0-1)

Allows providers to indicate whether indication is the primary or secondary target of the therapy. E.g., Terazosin for Benign Prostatic Hypertrophy as primary and Hypertension as secondary or vice-versa.

Ordering of prescribing indications from primary indication (low number) to minor indication (higher number). Multiple indications are permitted to have the same priority if they're considered of equivalent importance.



Copyright © 2013. All Rights Reserved.