Generated Narrative: StructureDefinition ResultObservation Name Flags Card. Type Description & Constraints Observation <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( should-text-ref-value, should-interpretationCode, should-author, should-referenceRange )">C 1..1 Observation XML Namespace: urn:hl7-org:v3 Base for all types and resources Instance of this type are validated by templateId Logical Container: ClinicalDocument (CDA Class) Constraints: should-text-ref-value, should-interpretationCode, should-author, should-referenceRange #xD; Slices for templateId 1..* II Slice: Unordered, Open by value:root, value:extension #xD; templateId:result-obs 1..1 II #xD; @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.4.2 #xD; @extension 1..1 st Required Pattern: 2023-05-01 #xD; @classCode 1..1 cs Fixed Value: OBS #xD; @moodCode 1..1 cs Fixed Value: EVN #xD; id 1..* II #xD; sdtcCategory 0..* CD Binding: US Core Clinical Result Observation Category (preferred) #xD; code <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( shall-code-or-nullflavor, 4537-19212 )">C 1..1 CD 헨?헦?헖?헗?헜?: Tests Binding: ObservationType (example) Additional Bindings Purpose Documentation Common LOINC Lab Codes Preferred Common Lab Tests Radiology Procedures (LOINC) Preferred Radiology Clinical Tests Preferred Clinical Test Constraints: shall-code-or-nullflavor, 4537-19212 #xD; (Choice of one) 1..1 #xD; @nullFlavor 0..1 cs #xD; @code 0..1 cs #xD; text 0..1 ED SHOULD reference the portion of section narrative text corresponding to this entry #xD; reference <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( value-starts-octothorpe )">C 0..1 TEL Constraints: value-starts-octothorpe #xD; statusCode 1..1 CS 헨?헦?헖?헗?헜?: Result Status #xD; @nullFlavor 0..0 #xD; @code 1..1 cs Binding: Result Status (required) #xD; effectiveTime 1..1 IVL_TS Represents the clinically relevant time of the measurement (e.g., the time a blood pressure reading is obtained, the time the blood sample was obtained for a chemistry test). #xD; Slices for value 1..1 ANY, BL, ED, ST, CD, CV, CE, CO, SC, II, TEL, AD, EN, INT, REAL, PQ, MO, TS, IVL_PQ, IVL_TS, PIVL_TS, EIVL_TS, SXPR_TS, RTO_PQ_PQ 헨?헦?헖?헗?헜?: Values/Results - Value can be any type, but certain types have additional rules. Slice: Unordered, Open by type:$this #xD; value:physical-quantity 0..1 PQ #xD; @unit 1..1 cs 헨?헦?헖?헗?헜?: Result Unit of Measure Binding: UnitsOfMeasureCaseSensitive (preferred) #xD; translation 0..1 PQR Can be used to represent the original results as output by the lab #xD; value:coded C 0..1 CD Constraints: 4537-32610 #xD; translation 0..1 CD Can be used to represent the original results as output by the lab #xD; interpretationCode 0..* CE 헨?헦?헖?헗?헜?: Result Interpretation #xD; methodCode 0..1 CE #xD; targetSiteCode 0..1 CD #xD; author 0..* AuthorParticipation #xD; referenceRange 0..* InfrastructureRoot 헨?헦?헖?헗?헜?: Result Reference Range #xD; observationRange 1..1 ObservationRange #xD; value 1..1 BL, ED, ST, CD, CV, CE, CO, SC, II, TEL, AD, EN, INT, REAL, PQ, MO, TS, IVL_PQ, IVL_TS, PIVL_TS, EIVL_TS, SXPR_TS When the value is a quantity, then the unit SHOULD be selected from ValueSet UnitsOfMeasureCaseSensitive. #xD; Documentation for this format
HL7 International - Structured Documents
This template represents the results of a laboratory, radiology, or other study performed on a patient. The result observation includes a statusCode to allow recording the status of an observation. Pending results (e.g., a test has been run but results have not been reported yet) should be represented as active ActStatus. If code contains a valid non-null LOINC then the xsi:type value SHOULD match the LOINC Scale Part based on the table below: | LOINC Scale Part | Value xsi:type | | -------- | ------- | | Qn - Quantitative | INT, IVL_INT, MO, IVL_MO, REAL, IVL_REAL, PQ, IVL_PQ, RTO, TS, IVL_TS | | Ord - Ordinal | CD | | Nom - Nominal | CD | | Nar - Narrative | ED, ST | | OrdQn - Quantitative or Ordinal | CD, INT, IVL_INT, MO, IVL_MO, REAL, IVL_REAL, PQ, IVL_PQ, RTO, TS, IVL_TS | | Multi - Multi | ED | | Doc - Document | ED | The Result Observation template is a versatile template designed to represent any type of finding resulting from various types of tests. Value set bindings for Observation.code have been created to support implementers, covering three categories: 1) Common Laboratory Tests, 2) Radiology Tests, and 3) Clinical Tests. If a suitable code is not available within these value sets, first use another LOINC code. If no LOINC code is appropriate, a local code may be used.
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
A unique identifier that guarantees the global uniqueness of the instance identifier. The root alone may be the entire instance identifier.
SHALL contain exactly one [1..1] @classCode="OBS" Observation (CodeSystem: HL7ActClass urn:oid:2.16.840.1.113883.5.6 STATIC) (CONF:4537-7130).
SHALL contain exactly one [1..1] @moodCode="EVN" Event (CodeSystem: HL7ActMood urn:oid:2.16.840.1.113883.5.1001 STATIC) (CONF:4537-7131).
SHALL contain at least one [1..*] id (CONF:4537-7137).
SHALL contain exactly one [1..1] code, which SHOULD be selected from CodeSystem LOINC (urn:oid:2.16.840.1.113883.6.1) (CONF:4537-7133).
SHALL contain either a @code attribute or a @nullFlavor attribute, but not both.
This code **SHOULD** be a code from the LOINC that identifies the result observation. If an appropriate LOINC code does not exist, then the local code for this result **SHALL** be sent (CONF:4537-19212).
Either code or nullFlavor MUST be present
The plain code symbol defined by the code system. For example, "784.0" is the code symbol of the ICD-9 code "784.0" for headache.
Specifies the code system that defines the code.
If applicable, a version descriptor defined specifically for the given code system.
A name or title for the code, under which the sending system shows the code value to its users.
The valueSet extension adds an attribute for elements with a CD dataType which indicates the particular value set constraining the coded concept.
The valueSetVersion extension adds an attribute for elements with a CD dataType which indicates the version of the particular value set constraining the coded concept.
The text or phrase used as the basis for the coding.
Specifies additional codes that increase the specificity of the the primary code.
A set of other concept descriptors that translate this concept descriptor into other code systems.
SHOULD reference the portion of section narrative text corresponding to this entry
Indicates whether the raw byte data is compressed, and what compression algorithm was used.
The integrity check is a short binary value representing a cryptographically strong checksum that is calculated over the binary data. The purpose of this property, when communicated with a reference is for anyone to validate later whether the reference still resolved to the same data that the reference resolved to when the encapsulated data value with reference was created.
Specifies the algorithm used to compute the integrityCheck value. The cryptographically strong checksum algorithm Secure Hash Algorithm-1 (SHA-1) is currently the industry standard. It has superseded the MD5 algorithm only a couple of years ago, when certain flaws in the security of MD5 were discovered. Currently the SHA-1 hash algorithm is the default choice for the integrity check algorithm. Note that SHA-256 is also entering widespread usage.
For character based information the language property specifies the human language of the text.
Identifies the type of the encapsulated data and identifies a method to interpret or render the data.
Allows for mixed text content. If @representation='B64', this SHALL be a base64binary string.
Data that is primarily intended for human interpretation or for further machine processing is outside the scope of HL7. This includes unformatted or formatted written language, multimedia data, or structured information as defined by a different standard (e.g., XML-signatures.)
This element is represented in XML as textual content. The actual name "xmlText" will not appear in a CDA instance.
A telecommunication address (TEL), such as a URL for HTTP or FTP, which will resolve to precisely the same binary data that could as well have been provided as inline data.
If reference/@value is present, it SHALL begin with a '#' and SHALL point to its corresponding narrative
value.exists() implies value.startsWith('#')
An abbreviated rendition of the full data. A thumbnail requires significantly fewer resources than the full data, while still maintaining some distinctive similarity with the full data. A thumbnail is typically used with by-reference encapsulated data. It allows a user to select data more efficiently before actually downloading through the reference.
SHALL contain exactly one [1..1] statusCode (CONF:4537-7134).
Represents the clinically relevant time of the measurement (e.g., the time a blood pressure reading is obtained, the time the blood sample was obtained for a chemistry test).
SHALL contain exactly one [1..1] effectiveTime (CONF:4537-7140).
𝗨𝗦𝗖𝗗𝗜: Values/Results - Value can be any type, but certain types have additional rules.
The unit of measure specified in the Unified Code for Units of Measure (UCUM) [].
The magnitude of the quantity measured in terms of the unit.
Can be used to represent the original results as output by the lab
An alternative representation of the same physical quantity expressed in a different unit, of a different unit code system and possibly with a different value.
If Observation/value is a CD (**xsi:type="CD"**) the value **SHOULD** be SNOMED-CT or LOINC (CONF:4537-32610).
SHOULD contain zero or more [0..*] interpretationCode, which SHALL be selected from ValueSet Observation Interpretation (HL7) urn:oid:2.16.840.1.113883.1.11.78 DYNAMIC (CONF:4537-7147).
MAY contain zero or one [0..1] methodCode (CONF:4537-7148).
MAY contain zero or one [0..1] targetSiteCode (CONF:4537-7153).
SHOULD contain zero or more [0..*] Author Participation (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.119) (CONF:4537-7149).
Relates an Observation to the ObservationRange class, where the expected range of values for a particular observation can be specified.
SHOULD contain zero or more [0..*] referenceRange (CONF:4537-7150).
The referenceRange, if present, SHALL contain exactly one [1..1] observationRange (CONF:4537-7151).
When the value is a quantity, then the unit SHOULD be selected from ValueSet UnitsOfMeasureCaseSensitive.
This observationRange SHALL contain exactly one [1..1] value (CONF:4537-32175).
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).