|DotNet Class HL7Connect.Cda.ObservationMedia|
A derivative of the RIM Observation class that represents multimedia that is logically part of the current document. This class is only for multimedia that is logically part of the attested content of the document. Rendering a referenced ObservationMedia requires a software tool that recognizes the particular MIME media type.
|l version="1.0" encoding="UTF-8"?>
|l version="1.0" encoding="UTF-8"?>
|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.
|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.|
|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.|
|Represents the humans and/or machines that authored the document or section|
|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.|
|Used to represent other participants not explicitly mentioned by other classes, that were somehow involved in the documented acts.|
|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.
|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".
|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.|
|XML ID - target of an ID reference in the structured text.
Note that in XML this is the "ID" attribute, but has been renamed for the sake of some non-case sensitive implementations