Ancestor: HL7Connect.Cda.ClinicalStatement

A derivative of the RIM SubstanceAdministration class, used for representing medication-related events such as medication history or planned medication administration orders.

Properties

HL7Connect.Cda.CD code;
   l version="1.0" encoding="UTF-8"?>

HL7Connect.Cda.ED text;
   l version="1.0" encoding="UTF-8"?>

HL7Connect.Cda.CS statusCode;
   l version="1.0" encoding="UTF-8"?>

HL7Connect.Cda.QSET effectiveTime;
   is used to describe the timing of administration. It is modeled using the GTS data type to accommodate various dosing scenarios

HL7Connect.Cda.CD priorityCode;
   categorizes the priority of a substance administration

HL7Connect.Cda.IVL repeatNumber;
   l version="1.0" encoding="UTF-8"?>

HL7Connect.Cda.CD routeCode;
   l version="1.0" encoding="UTF-8"?>

IList<HL7Connect.Cda.CD> approachSiteCode;
   l version="1.0" encoding="UTF-8"?>

HL7Connect.Cda.IVL doseQuantity;
   indicates how much medication is given per dose

HL7Connect.Cda.IVL rateQuantity;
   can be used to indicate the rate at which the dose is to be administered (e.g., the flow rate for intravenous infusions)

HL7Connect.Cda.RTO maxDoseQuantity;
   is used to capture the maximum dose of the medication that can be given over a stated time interval (e.g., maximum daily dose of morphine, maximum lifetime dose of doxorubicin)

HL7Connect.Cda.CD administrationUnitCode;
   l version="1.0" encoding="UTF-8"?>

HL7Connect.Cda.Subject subject;
   The subject participant represents the primary target of the entries recorded in the document or section. Most of the time the subject is the same as the recordTarget, but need not be, for instance when the subject is a fetus observed in an obstetrical ultrasound.

The subject participant can be ascribed to a CDA section or a CDA entry. It propagates to nested components, unless overridden. The subject of a document is presumed to be the patient.

IList<HL7Connect.Cda.Specimen> specimen;
   A specimen is a part of some entity, typically the subject, that is the target of focused laboratory, radiology or other observations. In many clinical observations, such as physical examination of a patient, the patient is the subject of the observation, and there is no specimen. The specimen participant is only used when observations are made against some substance or object that is taken or derived from the subject.

HL7Connect.Cda.Consumable consumable;
   used to bring in the LabeledDrug or Material entity that describes the administered substance

IList<HL7Connect.Cda.Performer2> performer;
   The performer is a person who carries out or will carry out a particular act. The performer need not be the principal responsible participant, e.g. a surgery resident operating under supervision of attending surgeon is a performer.

IList<HL7Connect.Cda.Author> author;
   Represents the humans and/or machines that authored the document or section

IList<HL7Connect.Cda.Informant12> informant;
   An informant (or source of information) is a person that provides relevant information, such as the parent of a comatose patient who describes the patient's behavior prior to the onset of coma.

IList<HL7Connect.Cda.Participant2> participant;
   Used to represent other participants not explicitly mentioned by other classes, that were somehow involved in the documented acts.

IList<HL7Connect.Cda.EntryRelationship> entryRelationship;
   CDA has identified and modeled various link and reference scenarios. These scenarios enable CDA entries to be semantically linked to entries that exist within the same document (by traversing the entryRelationship class) or to objects external to it (by traversing the reference class).

NOTE: The CDA specification permits any CDA entry to relate to any CDA entry using any of the following relationship types. In many cases, this would result in nonsensical relationships. The following table is a guideline for reasonable relationships between CDA entries, and is not a conformance constraint.

IList<HL7Connect.Cda.Reference> reference;
   CDA entries can reference external objects such as external images and prior reports. These external objects are not part of the authenticated document content. They contain sufficient attributes to enable an explicit reference rather than duplicating the entire referenced object. The CDA entry that wraps the external reference can be used to encode the specific portions of the external reference that are addressed in the narrative block.

Each object allows for an identifier and a code, and contains the RIM Act.text attribute, which can be used to store the URL and MIME type of the object. External objects always have a fixed moodCode of "EVN".

IList<HL7Connect.Cda.Precondition> precondition;
   The precondition class, derived from the ActRelationship class, is used along with the Criterion class to express a condition that must hold true before some over activity occurs.

bool negationInd;
   l version="1.0" encoding="UTF-8"?>

bool HasNegationInd;
   false if negationInd is null, true if negationInd is either true or false


Methods


© Kestral Computing P/L 2000 - 2003. HL7Connect v2.00-063 generated on 30-Nov 2015.
Keywords: Code, Text, reference, author, effectiveTime, entryRelationship, HasNegationInd, informant, negationInd, participant, performer, precondition, priorityCode, specimen, statusCode, subject, substanceAdministration, repeatNumber, approachSiteCode, administrationUnitCode, consumable, doseQuantity, maxDoseQuantity, rateQuantity, routeCode, HL7Connect.Cda.SubstanceAdministration