Ancestor: HL7Connect.Cda.CDABase

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.

Properties

HL7Connect.Cda.INT sequenceNumber;
   l version="1.0" encoding="UTF-8"?>

HL7Connect.Cda.BL seperatableInd;
   l version="1.0" encoding="UTF-8"?>

HL7Connect.Cda.Act act;
   A derivative of the RIM Act class, to be used when the other more specific classes aren't appropriate

HL7Connect.Cda.Encounter encounter;
   A derivative of the RIM PatientEncounter class, used to represent related encounters, such as follow-up visits or referenced past encounters

HL7Connect.Cda.Observation observation;
   A derivative of the RIM Observation class, used for representing coded and other observations.

HL7Connect.Cda.ObservationMedia 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.

HL7Connect.Cda.Organizer organizer;
   A derivative of the RIM Act class, which can be used to create arbitrary groupings of other CDA entries that share a common context. An Organizer can contain other Organizers and/or other CDA entries, by traversing the component relationship. An Organizer can refer to external acts by traversing the reference relationship. An Organizer cannot be the source of an entryRelationship relationship.

HL7Connect.Cda.Procedure procedure;
   A derivative of the RIM Procedure class, used for representing procedures.

HL7Connect.Cda.RegionOfInterest regionOfInterest;
   A derivative of the RIM Observation class that represents a region of interest on an image, using an overlay shape. RegionOfInterest is used to make reference to specific regions in images, e.g., to specify the site of a physical finding by "circling" a region in a schematic picture of a human body. The units of the coordinate values in RegionOfInterest.value are in pixels, expressed as a list of integers. The origin is in the upper left hand corner, with positive X values going to the right and positive Y values going down. The relationship between a RegionOfInterest and its referenced ObservationMedia or ExternalObservation is specified by traversing the entryRelationship or reference class, respectively, where typeCode equals "SUBJ". A RegionOfInterest must reference exactly one ObservationMedia or one ExternalObservation. If the RegionOfInterest is the target of a <renderMultimedia> reference, then it shall only reference a ObservationMedia and not an ExternalObservation.

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

HL7Connect.Cda.Supply supply;
   A derivative of the RIM Supply class, used for representing the provision of a material by one entity to another.

HL7Connect.Cda.ClinicalStatement clinicalStatement;
   Choice of act, encounter, observation, observationMedia, organizer, procedure_, regionOfInterest, substanceAdministration or supply

string typeCode;
   l version="1.0" encoding="UTF-8"?>

bool inversionInd;
   The entryRelationship.inversionInd can be set to "true" to indicate that the relationship should be interpreted as if the roles of the source and target entries were reversed. In the example in the table above, "treadmill test" RSON (has reason) "chest pain". Inverted, this would have "chest pain" as the source and "treadmill test" as the target: "chest pain" RSON (inverted) "treadmill test". Inversion can be useful when the current context is describing the target of an act relationship that needs to be related back to the source.

bool HasInversionInd;
   false if inversionInd is null, true if inversionInd is either true or false

bool contextConductionInd;
   The entryRelationship.contextConductionInd differs from the otherwise common use of this attribute (see CDA Context ( 4.4 )) in that in all other cases where this attribute is used, the value is fixed at "true", whereas here the value is defaulted to "true", and can be changed to "false" when referencing an entry in the same document. Setting the context conduction to false when referencing an entry in the same document keeps clear the fact that the referenced object retains its original context.

bool HasContextConductionInd;
   false if contextConductionInd is null, true if contextConductionInd is either true or false

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: entryRelationship, HasNegationInd, negationInd, typeCode, contextConductionInd, HasContextConductionInd, act, clinicalStatement, encounter, observation, observationMedia, organizer, regionOfInterest, seperatableInd, sequenceNumber, substanceAdministration, supply, HasInversionInd, inversionInd, Procedure, HL7Connect.Cda.EntryRelationship