Important: This is a draft IG for trial use. Click here to give feedback.

HdBe-LaboratoryTestResult

CBB	Description	Status
HdBe-LaboratoryTestResult	A laboratory result describes the result of a laboratory analysis. These are specimen-oriented tests as performed in laboratories such as Clinical Chemistry, Serology, Microbiology, etc. In addition to the results of tests with a singular result, this concept can also contain the results of more complex tests with multiple results or a ‘panel’. Purpose Laboratory tests are done for the purpose of diagnosing and preventing disease and follow-up on the effects of treatment. Evidence Base There are two information models for recording laboratory test results: TextResult and LaboratoryTestResult. In the case of laboratory test results, it is difficult to clearly indicate exactly when to use this information model and when to use the TextResult information model. In general, laboratory tests resulting in a value (7.1 mmol/L), ordinal number (++ from series to ++++) or a quantitative result (Low) are recorded using this information model. The TextResult information model is better suited for textual results that are more descriptive in nature and which are longer than just a few words. Both types of tests occur in almost all laboratories. The applicability of the aforementioned information models is not determined by the kind of lab but by the kind of result.	active

CBB

Description

Status

A laboratory result describes the result of a laboratory analysis. These are specimen-oriented tests as performed in laboratories such as Clinical Chemistry, Serology, Microbiology, etc. In addition to the results of tests with a singular result, this concept can also contain the results of more complex tests with multiple results or a ‘panel’.

Purpose

Laboratory tests are done for the purpose of diagnosing and preventing disease and follow-up on the effects of treatment.

Evidence Base

There are two information models for recording laboratory test results: TextResult and LaboratoryTestResult.

In the case of laboratory test results, it is difficult to clearly indicate exactly when to use this information model and when to use the TextResult information model. In general, laboratory tests resulting in a value (7.1 mmol/L), ordinal number (++ from series to ++++) or a quantitative result (Low) are recorded using this information model. The TextResult information model is better suited for textual results that are more descriptive in nature and which are longer than just a few words. Both types of tests occur in almost all laboratories. The applicability of the aforementioned information models is not determined by the kind of lab but by the kind of result.

active

LaboratoryTestResult			LaboratoryTestResult	Element id LaboratoryTestResult Short description LaboratoryTestResult Definition Root concept of the LaboratoryTestResult information model. This root concept contains all data elements of the LaboratoryTestResult information model. Data type LaboratoryTestResult Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id LaboratoryTestResult.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id LaboratoryTestResult.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
LaboratoryTest		0..*	BackboneElement	Element id LaboratoryTestResult.LaboratoryTest Short description LaboratoryTest Definition Container of the LaboratoryTest concept. This container contains all data elements of the LaboratoryTest concept. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id LaboratoryTestResult.LaboratoryTest.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id LaboratoryTestResult.LaboratoryTest.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id LaboratoryTestResult.LaboratoryTest.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
TestResultId		0..1	string	Element id LaboratoryTestResult.LaboratoryTest.TestResultId Short description TestResultId Definition A unique identifier assigned to this LaboratoryTest. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
TestCode		1..1	CodeableConcept	Element id LaboratoryTestResult.LaboratoryTest.TestCode Short description TestCode Definition The name and code of the executed test. The codification to be used SHOULD be LOINC as per the subset defined by the FPS Health, for the majority of commonly used lab measurements and demands. This subset is available on the website of the FPS Health. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
TestResult[x]		0..1		Element id LaboratoryTestResult.LaboratoryTest.TestResult[x] Short description TestResult Definition The test result. Depending on the type of test, the result will consist of a value with a unit or a coded value (ordinal or nominal). Comments For quantitative results, it is mandatory to provide an unit. Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
TestResultString			string	Data type string
TestResultQuantity			Quantity	Data type Quantity
TestResultCodeableConcept			CodeableConcept	Data type CodeableConcept
TestMethod		0..1	CodeableConceptBinding	Element id LaboratoryTestResult.LaboratoryTest.TestMethod Short description TestMethod Definition The test method used to obtain the result. Comments 0..1 If the LOINC test code (in ‘TestCode’) already contains a method, the ‘TestMethod’ value may not conflict with that method. ‘TestMethod’ will then contain the same method, or a specification. Data type CodeableConcept Binding TestMethod codes TestMethod (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
TestDateTime		0..1	dateTime	Element id LaboratoryTestResult.LaboratoryTest.TestDateTime Short description TestDateTime Definition The date and if possible the time at which the test was carried out. Data type dateTime Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
TestResultStatus		0..1	CodeableConceptBinding	Element id LaboratoryTestResult.LaboratoryTest.TestResultStatus Short description TestResultStatus Definition The status of the test result of this test. If the laboratory test is a panel/cluster, the overall status is given in the status of the panel/cluster. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding TestResultStatus codes TestResultStatus (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
ReferenceRangeUpperLimit[x]		0..1		Element id LaboratoryTestResult.LaboratoryTest.ReferenceRangeUpperLimit[x] Short description ReferenceRangeUpperLimit Definition The upper reference limit for the patient of the value measured in the test. Comments If the result has data type PQ and there are reference values, then the unit of the result and reference value must be the same. If the result has reference values, then the data type of the result and reference values must be the same. A string datatype may only be used if the reference range cannot be expressed as PQ. Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
ReferenceRangeUpperLimitString			string	Data type string
ReferenceRangeUpperLimitQuantity			SimpleQuantity	Data type SimpleQuantity
ReferenceRangeLowerLimit[x]		0..1		Element id LaboratoryTestResult.LaboratoryTest.ReferenceRangeLowerLimit[x] Short description ReferenceRangeLowerLimit Definition The lower reference limit for the patient of the value measured with the test. Comments If the result has data type PQ and there are reference values, then the unit of the result and reference value must be the same. If the result has reference values, then the data type of the result and reference values must be the same. A string datatype may only be used if the reference range cannot be expressed as PQ. Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
ReferenceRangeLowerLimitString			string	Data type string
ReferenceRangeLowerLimitQuantity			SimpleQuantity	Data type SimpleQuantity
InterpretationMethod		0..1	CodeableConcept	Element id LaboratoryTestResult.LaboratoryTest.InterpretationMethod Short description InterpretationMethod Definition The method used to determine interpretation flags. An example of this is EUCAST, for determining clinical breakpoints in microbiological susceptibility tests. Comments A ValueSet is not yet available for this concept. Data type CodeableConcept Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
ResultFlags		0..*	CodeableConceptBinding	Element id LaboratoryTestResult.LaboratoryTest.ResultFlags Short description ResultFlags Definition Attention codes indicating whether the result of a quantitative test is above or below certain reference values or interpreting the result otherwise. (Resistent). The values Resistant, Intermediate en Susceptible are used with microbiological test results. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding ResultFlags codes ResultFlags (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
ResultInterpretation		0..1	string	Element id LaboratoryTestResult.LaboratoryTest.ResultInterpretation Short description ResultInterpretation Definition Comment of the laboratory specialist regarding the interpretation of the results Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
Specimen		0..1	BackboneElement	Element id LaboratoryTestResult.Specimen Short description Specimen Definition Container of the Specimen concept. This container contains all data elements of the Specimen concept. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id LaboratoryTestResult.Specimen.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id LaboratoryTestResult.Specimen.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id LaboratoryTestResult.Specimen.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). Requirements Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
SpecimenId		0..1	Identifier	Element id LaboratoryTestResult.Specimen.SpecimenId Short description SpecimenId Definition Identification number of the material obtained, as a reference for inquiries to the source organization. In a transmural setting, this number will consist of a specimen number including the identification of the issuing organization, to be unique outside of the borders of an organization. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier
SpecimenNumberExtension		0..1	string	Element id LaboratoryTestResult.Specimen.SpecimenNumberExtension Short description SpecimenNumberExtension Definition The specimen number extension is used when the collected material is distributed from the original tube or container across multiple tubes. In combination with the specimen Id the extension yield a unique identification of the tube or container Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
ContainerType		0..1	CodeableConceptBinding	Element id LaboratoryTestResult.Specimen.ContainerType Short description ContainerType Definition Container type describes the envelope in which the material is collected or sent. Examples include blood tubes, transport container, possibly including culture medium. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding ContainerType codes ContainerType (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
SpecimenMaterial		0..1	CodeableConceptBinding	Element id LaboratoryTestResult.Specimen.SpecimenMaterial Short description SpecimenMaterial Definition SpecimenMaterial describes the material obtained. If the LOINC test code also implicitly describes a material, this element may not conflict with the description. If desired, this component can provide a more detailed description of the material: LOINC codes only contain the materials at a main level. This is in line with the agreements made in the IHE/Nictiz program e-Lab. If the test is carried out on derived material (such as plasma), this element will still contain the material drawn (in this case, blood). In this case, the LOINC code will generally refer to plasma. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding SpecimenMaterial codes SpecimenMaterial (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
AnatomicalLocation		0..1	HdBe-AnatomicalLocation	Element id LaboratoryTestResult.Specimen.AnatomicalLocation Short description AnatomicalLocation Definition Anatomical location where the material is collected, e.g. elbow. Data type HdBe-AnatomicalLocation Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
Microorganism		0..1	CodeableConceptBinding	Element id LaboratoryTestResult.Specimen.Microorganism Short description Microorganism Definition In particular in microbiological determinations the subject of the test is an isolate of a certain microorganism rather then a material. This concept provides the ability to capture information about this microorganism. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding Microorganism codes Microorganism (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
CollectedVolume	I	0..1	QuantityPattern	Element id LaboratoryTestResult.Specimen.CollectedVolume Short description CollectedVolume Definition Total volume of the collected material. If it is necessary to determine the absolute amount of a particular substance in the collected material, the volume thereof must be given. Comments The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator. Data type Quantity Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` qty-3: If a code for the unit is present, the system SHALL also be present `code.empty() or system.exists()` Pattern { "unit": "mL", "system": "http://unitsofmeasure.org", "code": "mL" } Mappings rim: n/a v2: SN (see also Range) or CQ rim: PQ, IVL<PQ>, MO, CO, depending on the values
CollectionPeriod		0..1	HdBe-TimeInterval	Element id LaboratoryTestResult.Specimen.CollectionPeriod Short description CollectionPeriod Definition If the material has not been collected at a single point in time but over a certain period, this period can be captured in this concept. An example is 24 hour urine. Comments TimeInterval.Duration is expressed in minutes (min). Data type HdBe-TimeInterval Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
CollectionDateTime		0..1	dateTime	Element id LaboratoryTestResult.Specimen.CollectionDateTime Short description CollectionDateTime Definition Date and time at which the material was collected. Data type dateTime Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
ReceivedDateTime		0..1	dateTime	Element id LaboratoryTestResult.Specimen.ReceivedDateTime Short description ReceivedDateTime Definition Date and time that the material is handed over at the laboratory or specimen collection center. Data type dateTime Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
CollectionMethod		0..1	CodeableConceptBinding	Element id LaboratoryTestResult.Specimen.CollectionMethod Short description CollectionMethod Definition If relevant for the results, the method of obtaining the specimen can be entered as well. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding CollectionMethod codes CollectionMethod (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
Morphology		0..1	CodeableConceptBinding	Element id LaboratoryTestResult.Specimen.Morphology Short description Morphology Definition Morphology describes morphological abnormalities of the anatomical location where the material is taken, for example wound, ulcer. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding Morphology codes Morphology (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
SpecimenSource		0..1	CodeableConceptBinding	Element id LaboratoryTestResult.Specimen.SpecimenSource Short description SpecimenSource Definition If the material is not collected directly from the patient but comes from a patient-related object, e.g. a cathetertip, this source of material can be recorded here. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding The source of the specimen SpecimenSource (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
Comment		0..1	string	Element id LaboratoryTestResult.Specimen.Comment Short description Comment Definition Comments on the specimen , such as drawing material after a (glucose) stimulus or taking medicine. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
PanelOrBattery		0..1	CodeableConcept	Element id LaboratoryTestResult.PanelOrBattery Short description PanelOrBattery Definition For laboratory tests comprising multiple subtests and often requested together as a whole, this concept contains the name of the compound request (often indicated as a ‘panel’, ‘battery’ or ‘cluster’). Examples include: blood gases and EBV serology. The codification to be used SHOULD be LOINC as per the subset defined by the FPS Health, for the majority of commonly used lab measurements and demands. This subset is available on the website of the FPS Health. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
ResultStatus		0..1	CodeableConceptBinding	Element id LaboratoryTestResult.ResultStatus Short description ResultStatus Definition The status of the laboratory test result. If the laboratory test is a panel/cluster, this status reflects the status of the whole panel/cluster. If the status item per subtest is used too, this status must be in accordance with these status values. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding TestResultStatus codes TestResultStatus (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
Comment		0..1	string	Element id LaboratoryTestResult.Comment Short description Comment Definition Comments, such as a textual interpretation or advice accompanying the result, for example. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
ResultType		0..1	CodeableConceptBinding	Element id LaboratoryTestResult.ResultType Short description ResultType Definition The type of result defines the laboratory specialty under which the test is categorized. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding ResultType codes ResultType (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
RelatedResult	I	0..*	Reference(HdBe-LaboratoryTestResult)	Element id LaboratoryTestResult.RelatedResult Short description RelatedResult Definition Reference to related tests, e.g. paired tests or sequential tests like gram staining and microbiological cultures Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(HdBe-LaboratoryTestResult) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
Requester	I	0..1	Reference(HdBe-HealthProfessional)	Element id LaboratoryTestResult.Requester Short description Requester Definition The healthcare professional and/or organization where or by whom the LaboratoryTestResult was requested. Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(HdBe-HealthProfessional) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
Performer	I	0..1	Reference(HdBe-HealthProfessional)	Element id LaboratoryTestResult.Performer Short description Performer Definition The HealthProfessional responsible for the LaboratoryTestResult. The performing laboratory (HealthcareOrganization) is referenced through the HealthProfessional. Comments References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Data type Reference(HdBe-HealthProfessional) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)

LaboratoryTestResult		0..*
LaboratoryTestResult.LaboratoryTest	BackboneElement	0..*
LaboratoryTestResult.LaboratoryTest.TestResultId	string	0..1
LaboratoryTestResult.LaboratoryTest.TestCode	CodeableConcept	1..1
LaboratoryTestResult.LaboratoryTest.TestResult[x]	string, Quantity, CodeableConcept	0..1
LaboratoryTestResult.LaboratoryTest.TestMethod	CodeableConcept	0..1
LaboratoryTestResult.LaboratoryTest.TestDateTime	dateTime	0..1
LaboratoryTestResult.LaboratoryTest.TestResultStatus	CodeableConcept	0..1
LaboratoryTestResult.LaboratoryTest.ReferenceRangeUpperLimit[x]	string, SimpleQuantity	0..1
LaboratoryTestResult.LaboratoryTest.ReferenceRangeLowerLimit[x]	string, SimpleQuantity	0..1
LaboratoryTestResult.LaboratoryTest.InterpretationMethod	CodeableConcept	0..1
LaboratoryTestResult.LaboratoryTest.ResultFlags	CodeableConcept	0..*
LaboratoryTestResult.LaboratoryTest.ResultInterpretation	string	0..1
LaboratoryTestResult.Specimen	BackboneElement	0..1
LaboratoryTestResult.Specimen.SpecimenId	Identifier	0..1
LaboratoryTestResult.Specimen.SpecimenNumberExtension	string	0..1
LaboratoryTestResult.Specimen.ContainerType	CodeableConcept	0..1
LaboratoryTestResult.Specimen.SpecimenMaterial	CodeableConcept	0..1
LaboratoryTestResult.Specimen.AnatomicalLocation	HdBe-AnatomicalLocation	0..1
LaboratoryTestResult.Specimen.Microorganism	CodeableConcept	0..1
LaboratoryTestResult.Specimen.CollectedVolume	Quantity	0..1
LaboratoryTestResult.Specimen.CollectionPeriod	HdBe-TimeInterval	0..1
LaboratoryTestResult.Specimen.CollectionDateTime	dateTime	0..1
LaboratoryTestResult.Specimen.ReceivedDateTime	dateTime	0..1
LaboratoryTestResult.Specimen.CollectionMethod	CodeableConcept	0..1
LaboratoryTestResult.Specimen.Morphology	CodeableConcept	0..1
LaboratoryTestResult.Specimen.SpecimenSource	CodeableConcept	0..1
LaboratoryTestResult.Specimen.Comment	string	0..1
LaboratoryTestResult.PanelOrBattery	CodeableConcept	0..1
LaboratoryTestResult.ResultStatus	CodeableConcept	0..1
LaboratoryTestResult.Comment	string	0..1
LaboratoryTestResult.ResultType	CodeableConcept	0..1
LaboratoryTestResult.RelatedResult	Reference(HdBe-LaboratoryTestResult)	0..*
LaboratoryTestResult.Requester	Reference(HdBe-HealthProfessional)	0..1
LaboratoryTestResult.Performer	Reference(HdBe-HealthProfessional)	0..1

LaboratoryTestResult
Definition	Root concept of the LaboratoryTestResult information model. This root concept contains all data elements of the LaboratoryTestResult information model.
Cardinality	0...*
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.id
Definition	Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality	0...1
Type	string
Mappings	rim: n/a
LaboratoryTestResult.extension
Definition	May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Cardinality	0...*
Type	Extension
Alias	extensions, user content
Comments	There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Slicing	Unordered, Open, by url(Value)
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: n/a rim: N/A
LaboratoryTestResult.LaboratoryTest
Definition	Container of the LaboratoryTest concept. This container contains all data elements of the LaboratoryTest concept.
Cardinality	0...*
Type	BackboneElement
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.LaboratoryTest.id
Definition	Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality	0...1
Type	string
Mappings	rim: n/a
LaboratoryTestResult.LaboratoryTest.extension
Definition	May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Cardinality	0...*
Type	Extension
Alias	extensions, user content
Comments	There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Slicing	Unordered, Open, by url(Value)
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: n/a rim: N/A
LaboratoryTestResult.LaboratoryTest.modifierExtension
Definition	May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Cardinality	0...*
Type	Extension
Modifier	True
Summary	True
Alias	extensions, user content, modifiers
Requirements	Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.
Comments	There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: n/a rim: N/A
LaboratoryTestResult.LaboratoryTest.TestResultId
Definition	A unique identifier assigned to this LaboratoryTest.
Cardinality	0...1
Type	string
Comments	Note that FHIR strings SHALL NOT exceed 1MB in size
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.LaboratoryTest.TestCode
Definition	The name and code of the executed test. The codification to be used SHOULD be LOINC as per the subset defined by the FPS Health, for the majority of commonly used lab measurements and demands. This subset is available on the [website of the FPS Health](https://www.vas.ehealth.fgov.be/webretam/retam/home.htm).
Cardinality	1...1
Type	CodeableConcept
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.LaboratoryTest.TestResult[x]
Definition	The test result. Depending on the type of test, the result will consist of a value with a unit or a coded value (ordinal or nominal).
Cardinality	0...1
Type	string
Comments	For quantitative results, it is mandatory to provide an unit.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.LaboratoryTest.TestMethod
Definition	The test method used to obtain the result.
Cardinality	0...1
Type	CodeableConcept
Binding	TestMethod codes TestMethod (required)
Comments	0..1 If the LOINC test code (in ‘TestCode’) already contains a method, the ‘TestMethod’ value may not conflict with that method. ‘TestMethod’ will then contain the same method, or a specification.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.LaboratoryTest.TestDateTime
Definition	The date and if possible the time at which the test was carried out.
Cardinality	0...1
Type	dateTime
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.LaboratoryTest.TestResultStatus
Definition	The status of the test result of this test. If the laboratory test is a panel/cluster, the overall status is given in the status of the panel/cluster.
Cardinality	0...1
Type	CodeableConcept
Binding	TestResultStatus codes TestResultStatus (extensible)
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.LaboratoryTest.ReferenceRangeUpperLimit[x]
Definition	The upper reference limit for the patient of the value measured in the test.
Cardinality	0...1
Type	string
Comments	If the result has data type PQ and there are reference values, then the unit of the result and reference value must be the same. If the result has reference values, then the data type of the result and reference values must be the same. A string datatype may only be used if the reference range cannot be expressed as PQ.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.LaboratoryTest.ReferenceRangeLowerLimit[x]
Definition	The lower reference limit for the patient of the value measured with the test.
Cardinality	0...1
Type	string
Comments	If the result has data type PQ and there are reference values, then the unit of the result and reference value must be the same. If the result has reference values, then the data type of the result and reference values must be the same. A string datatype may only be used if the reference range cannot be expressed as PQ.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.LaboratoryTest.InterpretationMethod
Definition	The method used to determine interpretation flags. An example of this is EUCAST, for determining clinical breakpoints in microbiological susceptibility tests.
Cardinality	0...1
Type	CodeableConcept
Comments	A ValueSet is not yet available for this concept.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.LaboratoryTest.ResultFlags
Definition	Attention codes indicating whether the result of a quantitative test is above or below certain reference values or interpreting the result otherwise. (Resistent). The values Resistant, Intermediate en Susceptible are used with microbiological test results.
Cardinality	0...*
Type	CodeableConcept
Binding	ResultFlags codes ResultFlags (extensible)
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.LaboratoryTest.ResultInterpretation
Definition	Comment of the laboratory specialist regarding the interpretation of the results
Cardinality	0...1
Type	string
Comments	Note that FHIR strings SHALL NOT exceed 1MB in size
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.Specimen
Definition	Container of the Specimen concept. This container contains all data elements of the Specimen concept.
Cardinality	0...1
Type	BackboneElement
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.Specimen.id
Definition	Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality	0...1
Type	string
Mappings	rim: n/a
LaboratoryTestResult.Specimen.extension
Definition	May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Cardinality	0...*
Type	Extension
Alias	extensions, user content
Comments	There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Slicing	Unordered, Open, by url(Value)
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: n/a rim: N/A
LaboratoryTestResult.Specimen.modifierExtension
Definition	May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Cardinality	0...*
Type	Extension
Modifier	True
Summary	True
Alias	extensions, user content, modifiers
Requirements	Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.
Comments	There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()`
Mappings	rim: n/a rim: N/A
LaboratoryTestResult.Specimen.SpecimenId
Definition	Identification number of the material obtained, as a reference for inquiries to the source organization. In a transmural setting, this number will consist of a specimen number including the identification of the issuing organization, to be unique outside of the borders of an organization.
Cardinality	0...1
Type	Identifier
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier
LaboratoryTestResult.Specimen.SpecimenNumberExtension
Definition	The specimen number extension is used when the collected material is distributed from the original tube or container across multiple tubes. In combination with the specimen Id the extension yield a unique identification of the tube or container
Cardinality	0...1
Type	string
Comments	Note that FHIR strings SHALL NOT exceed 1MB in size
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.Specimen.ContainerType
Definition	Container type describes the envelope in which the material is collected or sent. Examples include blood tubes, transport container, possibly including culture medium.
Cardinality	0...1
Type	CodeableConcept
Binding	ContainerType codes ContainerType (preferred)
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.Specimen.SpecimenMaterial
Definition	SpecimenMaterial describes the material obtained. If the LOINC test code also implicitly describes a material, this element may not conflict with the description. If desired, this component can provide a more detailed description of the material: LOINC codes only contain the materials at a main level. This is in line with the agreements made in the IHE/Nictiz program e-Lab. If the test is carried out on derived material (such as plasma), this element will still contain the material drawn (in this case, blood). In this case, the LOINC code will generally refer to plasma.
Cardinality	0...1
Type	CodeableConcept
Binding	SpecimenMaterial codes SpecimenMaterial (extensible)
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.Specimen.AnatomicalLocation
Definition	Anatomical location where the material is collected, e.g. elbow.
Cardinality	0...1
Type	HdBe-AnatomicalLocation
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.Specimen.Microorganism
Definition	In particular in microbiological determinations the subject of the test is an isolate of a certain microorganism rather then a material. This concept provides the ability to capture information about this microorganism.
Cardinality	0...1
Type	CodeableConcept
Binding	Microorganism codes Microorganism (extensible)
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.Specimen.CollectedVolume
Definition	Total volume of the collected material. If it is necessary to determine the absolute amount of a particular substance in the collected material, the volume thereof must be given.
Cardinality	0...1
Type	Quantity
Comments	The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` qty-3: If a code for the unit is present, the system SHALL also be present `code.empty() or system.exists()`
Pattern	{ "unit": "mL", "system": "http://unitsofmeasure.org", "code": "mL" }
Mappings	rim: n/a v2: SN (see also Range) or CQ rim: PQ, IVL<PQ>, MO, CO, depending on the values
LaboratoryTestResult.Specimen.CollectionPeriod
Definition	If the material has not been collected at a single point in time but over a certain period, this period can be captured in this concept. An example is 24 hour urine.
Cardinality	0...1
Type	HdBe-TimeInterval
Comments	TimeInterval.Duration is expressed in minutes (min).
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.Specimen.CollectionDateTime
Definition	Date and time at which the material was collected.
Cardinality	0...1
Type	dateTime
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.Specimen.ReceivedDateTime
Definition	Date and time that the material is handed over at the laboratory or specimen collection center.
Cardinality	0...1
Type	dateTime
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.Specimen.CollectionMethod
Definition	If relevant for the results, the method of obtaining the specimen can be entered as well.
Cardinality	0...1
Type	CodeableConcept
Binding	CollectionMethod codes CollectionMethod (required)
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.Specimen.Morphology
Definition	Morphology describes morphological abnormalities of the anatomical location where the material is taken, for example wound, ulcer.
Cardinality	0...1
Type	CodeableConcept
Binding	Morphology codes Morphology (required)
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.Specimen.SpecimenSource
Definition	If the material is not collected directly from the patient but comes from a patient-related object, e.g. a cathetertip, this source of material can be recorded here.
Cardinality	0...1
Type	CodeableConcept
Binding	The source of the specimen SpecimenSource (extensible)
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.Specimen.Comment
Definition	Comments on the specimen , such as drawing material after a (glucose) stimulus or taking medicine.
Cardinality	0...1
Type	string
Comments	Note that FHIR strings SHALL NOT exceed 1MB in size
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.PanelOrBattery
Definition	For laboratory tests comprising multiple subtests and often requested together as a whole, this concept contains the name of the compound request (often indicated as a ‘panel’, ‘battery’ or ‘cluster’). Examples include: blood gases and EBV serology. The codification to be used SHOULD be LOINC as per the subset defined by the FPS Health, for the majority of commonly used lab measurements and demands. This subset is available on the [website of the FPS Health](https://www.vas.ehealth.fgov.be/webretam/retam/home.htm).
Cardinality	0...1
Type	CodeableConcept
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.ResultStatus
Definition	The status of the laboratory test result. If the laboratory test is a panel/cluster, this status reflects the status of the whole panel/cluster. If the status item per subtest is used too, this status must be in accordance with these status values.
Cardinality	0...1
Type	CodeableConcept
Binding	TestResultStatus codes TestResultStatus (extensible)
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.Comment
Definition	Comments, such as a textual interpretation or advice accompanying the result, for example.
Cardinality	0...1
Type	string
Comments	Note that FHIR strings SHALL NOT exceed 1MB in size
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
LaboratoryTestResult.ResultType
Definition	The type of result defines the laboratory specialty under which the test is categorized.
Cardinality	0...1
Type	CodeableConcept
Binding	ResultType codes ResultType (extensible)
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
LaboratoryTestResult.RelatedResult
Definition	Reference to related tests, e.g. paired tests or sequential tests like gram staining and microbiological cultures
Cardinality	0...*
Type	Reference(HdBe-LaboratoryTestResult)
Comments	References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))`
Mappings	rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
LaboratoryTestResult.Requester
Definition	The healthcare professional and/or organization where or by whom the LaboratoryTestResult was requested.
Cardinality	0...1
Type	Reference(HdBe-HealthProfessional)
Comments	References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))`
Mappings	rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
LaboratoryTestResult.Performer
Definition	The HealthProfessional responsible for the LaboratoryTestResult. The performing laboratory (HealthcareOrganization) is referenced through the HealthProfessional.
Cardinality	0...1
Type	Reference(HdBe-HealthProfessional)
Comments	References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))`
Mappings	rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)

Example instances

LaboratoryTestResult
LaboratoryTest
LaboratoryTest.TestResultId	6458f56c-2183-4f01-8eb0-c286d3703362
LaboratoryTest.TestCode	Chloride [Moles/volume] in Blood
LaboratoryTest.TestMethod	275711006 - Serum chemistry test (code by SNOMED CT)
LaboratoryTest.TestDateTime	2022-01-13 12:00:00
LaboratoryTest.TestResult	109 mmol/L
LaboratoryTest.TestResultStatus	final - Final (code by urn:oid:2.16.840.1.113883.2.4.3.11.60.40.4.16.1)
LaboratoryTest.ReferenceRangeUpperLimit	108 mmol/L
LaboratoryTest.ReferenceRangeLowerLimit	99 mmol/L
LaboratoryTest.InterpretationMethod
LaboratoryTest.ResultFlags	281302008 - Above reference range (code by SNOMED CT)
LaboratoryTest.ResultInterpretation	High
Specimen
Specimen.SpecimenId	123456
Specimen.SpecimenNumberExtension	A
Specimen.ContainerType
Specimen.SpecimenMaterial	119297000 - Blood specimen (code by SNOMED CT)
Specimen.AnatomicalLocation	368208006 - Left upper arm (code by SNOMED CT)
Specimen.Microorganism	409795000 - Antimicrobial resistant virus (code by SNOMED CT)
Specimen.CollectedVolume
Specimen.CollectionPeriod
Specimen.CollectionPeriod.StartDateTime
Specimen.CollectionPeriod.EndDateTime
Specimen.CollectionPeriod.Duration
Specimen.CollectionDateTime	2022-01-12 08:08:00
Specimen.ReceivedDateTime
Specimen.CollectionMethod	82078001 - Collection of blood specimen for laboratory (code by SNOMED CT)
Specimen.Morphology
Specimen.SpecimenSource
Specimen.Comment
PanelOrBattery
ResultStatus
Comment
ResultType
RelatedResult
Requester
Performer	Enrico Penninx

zib LaboratoryTestResult-v4.6 difference

Concept	Category	Description
`LaboratoryTest.TestResultId`	element	The TestResultId element is added due to its frequent usage within the Data Collection Definitions of Healthdata.be, despite its somewhat technical nature for a informational model.
`LaboratoryTest.TestCode`	terminology	Removed ValueSet binding and described in the comment the use of Loinc and Albert codes as per the subset defined by the FPS Health (ReTaM). Added a reference to the subset on the website of the FPS Health. The ReTaM codes are not duplicated in a FHIR ValueSet because this would require extensive maintenance in keeping the ValueSet up-to-date.
`LaboratoryTest.TestResult`	type	The zib datatype 'ANY' was incorrectly exported as only a 'string', likely because Forge was giving an (incorrect) warning. The element has been made polymorphic by allowing all the `Observation.Value[x]` datatype options.
`LaboratoryTest.TestResult`	textual	Added textual guidance to include the unit for quantitative results.
`LaboratoryTest.TestResultStatus`	terminology	Replaced the values of the ValueSet TestResultStatus with corresponding values from the Observation-status valueset from FHIR.
`LaboratoryTest.TestResultStatus`	textual	Changed 'an panel/cluster' to 'a panel/cluster'. (zib ticket #1551)
`LaboratoryTest.ReferenceRangeUpperLimit`	type	The concepts ReferenceRangeUpperLimit and ReferenceRangeLowerLimit are defined as datatype ANY, but it is unclear how these concepts should work for anything that is not a Quantity or string. In addition, there's no obvious way in FHIR to support reference values other than type Quantity or string. Therefore, support for reference ranges has been restricted to Quantity and String. (zib ticket #1703)
`LaboratoryTest.ReferenceRangeLowerLimit`	type	The concepts ReferenceRangeUpperLimit and ReferenceRangeLowerLimit are defined as datatype ANY, but it is unclear how these concepts should work for anything that is not a Quantity or string. In addition, there's no obvious way in FHIR to support reference values other than type Quantity or string. Therefore, support for reference ranges has been restricted to Quantity and String. (zib ticket #1703).
`LaboratoryTest.ResultFlags`	terminology	Added concepts 260405006 (Trace) and 260408008 (Weakly positive) from SNOMED and included CodeSystem-ResultFlags to the ValueSet ResultFlags.
`LaboratoryTest.InterpretationMethod`	terminology	Removed bound ValuSet because it is invalid. (zib ticket #1292) and (zib ticket #677)
`Specimen.ContainerType`	terminology	Relaxed binding from required to preferred. (zib ticket #1552)
`Specimen.SpecimenMaterial`	terminology	Replaced SpecimenMaterial valueset values from a SNOMED descendent-of 105590001 (Substance) to a descendent-of 123038009 (Specimen) because this makes it simpler, it is already in use in the DCD's like this and the container element can be used when additional information is required. (zib ticket #1554) Also included CodeSystem-SpecimenMaterial into the valueset, and loosened the binding from required to extensible.
`Specimen.AnatomicalLocation`	textual	Changed anatomic to anatomical in the definition. (zib ticket #1551)
`Specimen.Microorganism`	terminology	Replaced Dutch reference set for Microorganism by changing the SNOMED hierarchy 2581000146104 (Dutch microorganism simple reference set) to 410607006 (Organism). Also loosened the binding from required to extensible.
`Specimen.ReceivedDateTime`	textual	Removed sentence 'This is the issue...' (zib ticket #1551)
`Specimen.SpecimenSource`	type	Changed datatype from string to CodeableConcept. (zib ticket #1845).
`Specimen.SpecimenSource`	terminology	Constructed ValueSet SpecimenSource as a SNOMED descendent-of 898201001 (Specimen from device) and added it with an extensible binding to the concept (zib ticket #1845).
`Specimen.CollectionPeriod`	textual	Added the expected unit (minutes) in a comment for the TimeInterval.Duration concept. It cannot be added as a pattern because the model uses the custom datatype TimeInterval here. (zib ticket #1915)
`Specimen.CollectedVolume`	cardinality	Added the expected unit (mL) in a pattern. (zib ticket #1915)
`Specimen.SpecimenNumberExtension`	type	Change datatype from int to string to accommodate using letters for identification of the specimen.
`PanelOrBattery`	terminology	Removed ValueSet binding and described in the comment the use of Loinc and Albert codes as per the subset defined by the FPS Health (ReTaM). Added a reference to the subset on the website of the FPS Health. The ReTaM codes are not duplicated in a FHIR ValueSet because this would require extensive maintenance in keeping the ValueSet up-to-date.
`ResultStatus`	terminology	Replaced zib CodeSystem values to corresponding values from the FHIR ObservationStatus CodeSystem because these are more widely adopted and can be mapped to zib status terminology. The new ValueSet contains a subset of the ObservationStatus CodeSystem to maintain compatibility with the zib. Also merged duplicated status ValueSets into one 'TestResultStatus' ValueSet because a ValueSet with similar codes was bound to `.TestResultStatus`.
`Performer`	reference	Changed reference from HealthcareOrganization to a reference to HealthProfessional to assign a person responsible for the LaboratoryTestResult instead of the Laboratory (the HealthcareOrganization can be obtained through the HealthProfessional).
`ResultStatus`	textual	Replaced 'result .If' and 'an panel'.

Terminology Bindings

Path	Name	Strength	URL
LaboratoryTest.TestMethod	TestMethod	required	https://fhir.healthdata.be/ValueSet/TestMethod
LaboratoryTest.TestResultStatus	TestResultStatus	extensible	https://fhir.healthdata.be/ValueSet/TestResultStatus
LaboratoryTest.ResultFlags	ResultFlags	extensible	https://fhir.healthdata.be/ValueSet/ResultFlags
Specimen.ContainerType	ContainerType	preferred	https://fhir.healthdata.be/ValueSet/ContainerType
Specimen.SpecimenMaterial	SpecimenMaterial	extensible	https://fhir.healthdata.be/ValueSet/SpecimenMaterial
Specimen.Microorganism	Microorganism	extensible	https://fhir.healthdata.be/ValueSet/Microorganism
Specimen.CollectionMethod	CollectionMethod	required	https://fhir.healthdata.be/ValueSet/CollectionMethod
Specimen.Morphology	Morphology	required	https://fhir.healthdata.be/ValueSet/Morphology
Specimen.SpecimenSource	SpecimenSource	extensible	https://fhir.healthdata.be/ValueSet/SpecimenSource
ResultStatus	TestResultStatus	extensible	https://fhir.healthdata.be/ValueSet/TestResultStatus
ResultType	ResultType	extensible	https://fhir.healthdata.be/ValueSet/ResultType