|DotNet Class HL7Connect.Cda.Entry|
In terms of the relationship between a section and its entries, CDA defines a default general case, and a more specific case that can be used when applicable.
The entry relationship is defaulted to "COMP" (component), for the general case where the only assertion is that the related entries are contained within the source section and no other semantics are implied. In this case, the narrative is the original authenticated content. The CDA entries are created by various techniques (e.g., natural language processing, a human coder, a structured data entry tool that outputs both entries and a text report). The method of entry creation may be indicated by the entry participants (e.g., by identifying the algorithm or person that generated them). Relationships between various entries (such as two Observations or an Observation and an ObservationMedia) are encoded using the relationship types defined in entryRelationship.
|A derivative of the RIM Act class, to be used when the other more specific classes aren't appropriate|
|A derivative of the RIM PatientEncounter class, used to represent related encounters, such as follow-up visits or referenced past encounters|
|A derivative of the RIM Observation class, used for representing coded and other observations.|
|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.|
|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.|
|A derivative of the RIM Procedure class, used for representing procedures.|
|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.|
|A derivative of the RIM SubstanceAdministration class, used for representing medication-related events such as medication history or planned medication administration orders.|
|A derivative of the RIM Supply class, used for representing the provision of a material by one entity to another.|
|Choice of act, encounter, observation, observationMedia, organizer, procedure_, regionOfInterest, substanceAdministration or supply|
|l version="1.0" encoding="UTF-8"?>
|l version="1.0" encoding="UTF-8"?>
|false if contextConductionInd is null, true if contextConductionInd is either true or false|