Generated Narrative: StructureDefinition ObservationRange Name Flags Card. Type Description & Constraints ObservationRange 1..1 InfrastructureRoot XML Namespace: urn:hl7-org:v3 Base for all types and resources Elements defined in Ancestors:@nullFlavor, realmCode, typeId, templateId Instance of this type are validated by templateId Logical Container: ClinicalDocument (CDA Class) #xD; @classCode 0..1 cs Binding: CDAActClassObservation (required) #xD; @moodCode 0..1 cs Binding: ActMoodPredicate (required) Fixed Value: EVN.CRT #xD; code 0..1 CD Binding: v3 Code System ActCode (example) #xD; text 0..1 ED #xD; value 0..1 #xD; value IVL_INT #xD; value IVL_PQ #xD; value IVL_TS #xD; <span title="A concept descriptor represents any kind of concept usually by giving a code defined in a code system. A concept descriptor can contain the original text or phrase that served as the basis of the coding and one or more translations into different coding systems. A concept descriptor can also contain qualifiers to describe, e.g., the concept of a "left foot" as a postcoordinated term built from the primary code "FOOT" and the qualifier "LEFT". In cases of an exceptional value, the concept descriptor need not contain a code but only the original text describing that concept.">value CD #xD; value AD #xD; value BL #xD; value CE #xD; value CO #xD; value CS #xD; value CV #xD; <span title="Data that is primarily intended for human interpretation or for further machine processing outside the scope of HL7. This includes unformatted or formatted written language, multimedia data, or structured information in as defined by a different standard (e.g., XML-signatures.) Instead of the data itself, an may contain only a reference (see [TEL](StructureDefinition-TEL.html).) Note that the data type is a specialization of the data type when the media type is text/plain.">value ED #xD; <span title="A name for a person, organization, place or thing. A sequence of name parts, such as given name or family name, prefix, suffix, etc. Examples for entity name values are "Jim Bob Walton, Jr.", "Health Level Seven, Inc.", "Lake Tahoe", etc. An entity name may be as simple as a character string or may consist of several entity name parts, such as, "Jim", "Bob", "Walton", and "Jr.", "Health Level Seven" and "Inc.", "Lake" and "Tahoe".">value EN #xD; value II #xD; value INT #xD; value INT_POS #xD; <span title="A monetary amount is a quantity expressing the amount of money in some currency. Currencies are the units in which monetary amounts are denominated in different economic regions. While the monetary amount is a single kind of quantity (money) the exchange rates between the different units are variable. This is the principle difference between physical quantity and monetary amounts, and the reason why currency units are not physical units.">value MO #xD; value ON #xD; <span title="A name for a person. A sequence of name parts, such as given name or family name, prefix, suffix, etc. Examples for person name values are "Jim Bob Walton, Jr.", "Adam Everyman", etc. A person name may be as simple as a character string or may consist of several person name parts, such as, "Jim", "Bob", "Walton", and "Jr.". PN differs from EN because the qualifier type cannot include LS (Legal Status).">value PN #xD; value PQ #xD; value REAL #xD; value SC #xD; value ST #xD; value TEL #xD; value TN #xD; value TS #xD; value PIVL_TS #xD; value EIVL_TS #xD; value SXPR_TS #xD; <span title="A quantity constructed as the quotient of a numerator quantity divided by a denominator quantity. Common factors in the numerator and denominator are not automatically cancelled out. The data type supports titers (e.g., "1:128") and other quantities produced by laboratories that truly represent ratios. Ratios are not simply "structured numerics", particularly blood pressure measurements (e.g. "120/60") are not ratios. In many cases the should be used instead of the .">value RTO_PQ_PQ #xD; interpretationCode 0..1 CE Binding: CDAObservationInterpretation (required) #xD; sdtcPrecondition1 0..* InfrastructureRoot XML Namespace: urn:hl7-org:sdtc XML: precondition1 (urn:hl7-org:sdtc) #xD; @typeCode 0..1 cs Binding: CDAActRelationshipType (required) Fixed Value: PRCN #xD; <a href="StructureDefinition-ObservationRange-definitions.html#ObservationRange.sdtcPrecondition1.conjunctionCode" title="A code specifying the logical conjunction of the criteria among all the condition-links of Acts (e.g., and, or, exclusive-or).#xA;#xA;All AND criteria must be true.#xA;#xA;If OR and AND criteria occur together, one criterion out of the OR-group must be true and all AND criteria must be true also.#xA;#xA;If XOR criteria occur together with OR and AND criteria, exactly one of the XOR criteria must be true, and at least one of the OR criteria and all AND criteria must be true.#xA;#xA;In other words, the sets of AND, OR, and XOR criteria are in turn combined by a logical AND operator (all AND criteria and at least one OR criterion and exactly one XOR criterion).">conjunctionCode 1..1 CS XML Namespace: urn:hl7-org:sdtc XML Namespace: urn:hl7-org:sdtc Binding: RelationshipConjunction (2.0.0) (required) #xD; criterion1 1..1 Criterion XML Namespace: urn:hl7-org:sdtc XML Namespace: urn:hl7-org:sdtc #xD; Documentation for this format
HL7 International - Structured Documents
Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
When valued in an instance, this attribute signals the imposition of realm-specific constraints. The value of this attribute identifies the realm in question
When valued in an instance, this attribute signals the imposition of constraints defined in an HL7-specified message type. This might be a common type (also known as CMET in the messaging communication environment), or content included within a wrapper. The value of this attribute provides a unique identifier for the type in question.
An II instance must have either a root or an nullFlavor.
A human readable name or mnemonic for the assigning authority. The Assigning Authority Name has no computational value. The purpose of a Assigning Authority Name is to assist an unaided human interpreter of an II value to interpret the authority. Note: no automated processing must depend on the assigning authority name to be present in any form.
Specifies if the identifier is intended for human display and data entry (displayable = true) as opposed to pure machine interoperation (displayable = false).
Identifies the type as an HL7 Registered model
A character string as a unique identifier within the scope of the identifier root.
When valued in an instance, this attribute signals the imposition of a set of template-defined constraints. The value of this attribute provides a unique identifier for the templates in question
The sdtc:precondition1 extension allows for the association of a criterion with a reference range (ObservationRange), which allows the expression in a lab report that a reference range is conditional on some criterion such as patient sex or age (or a combination of criterion).
A code specifying the logical conjunction of the criteria among all the condition-links of Acts (e.g., and, or, exclusive-or). All AND criteria must be true. If OR and AND criteria occur together, one criterion out of the OR-group must be true and all AND criteria must be true also. If XOR criteria occur together with OR and AND criteria, exactly one of the XOR criteria must be true, and at least one of the OR criteria and all AND criteria must be true. In other words, the sets of AND, OR, and XOR criteria are in turn combined by a logical AND operator (all AND criteria and at least one OR criterion and exactly one XOR criterion).