HdBe-LaboratoryTestResult
| CBB | Status | URL |
|---|---|---|
| HdBe-LaboratoryTestResult | draft | https://fhir.healthdata.be/StructureDefinition/LogicalModel/HdBe-LaboratoryTestResult |
| LaboratoryTestResult | LaboratoryTestResult | ||
| LaboratoryTest | 0..* | BackboneElement | |
| TestCode | 1..1 | CodeableConcept | |
| TestResult[x] | 0..1 | ||
| TestResultString | string | ||
| TestResultQuantity | Quantity | ||
| TestResultCodeableConcept | CodeableConcept | ||
| TestResultBoolean | boolean | ||
| TestResultInteger | integer | ||
| TestResultRange | Range | ||
| TestResultRatio | Ratio | ||
| TestResultSampledData | SampledData | ||
| TestResultTime | time | ||
| TestResultDateTime | dateTime | ||
| TestResultPeriod | Period | ||
| TestMethod | 0..1 | CodeableConceptBinding | |
| TestDateTime | 0..1 | dateTime | |
| TestResultStatus | 0..1 | CodeableConceptBinding | |
| ReferenceRangeUpperLimit[x] | 0..1 | ||
| ReferenceRangeUpperLimitString | string | ||
| ReferenceRangeUpperLimitQuantity | SimpleQuantity | ||
| ReferenceRangeLowerLimit[x] | 0..1 | ||
| ReferenceRangeLowerLimitString | string | ||
| ReferenceRangeLowerLimitQuantity | SimpleQuantity | ||
| InterpretationMethod | 0..1 | CodeableConcept | |
| ResultFlags | 0..* | CodeableConceptBinding | |
| ResultInterpretation | 0..1 | string | |
| Specimen | 0..1 | BackboneElement | |
| SpecimenId | 0..1 | Identifier | |
| SpecimenNumberExtension | 0..1 | Count | |
| ContainerType | 0..1 | CodeableConceptBinding | |
| SpecimenMaterial | 0..1 | CodeableConceptBinding | |
| AnatomicalLocation | 0..1 | HdBe AnatomicalLocation | |
| Microorganism | 0..1 | CodeableConceptBinding | |
| CollectedVolume | 0..1 | Quantity | |
| CollectionPeriod | 0..1 | HdBe TimeInterval | |
| CollectionDateTime | 0..1 | dateTime | |
| ReceivedDateTime | 0..1 | dateTime | |
| CollectionMethod | 0..1 | CodeableConceptBinding | |
| Morphology | 0..1 | CodeableConceptBinding | |
| SpecimenSource | 0..1 | string | |
| Comment | 0..1 | string | |
| PanelOrBattery | 0..1 | CodeableConceptBinding | |
| ResultStatus | 0..1 | CodeableConceptBinding | |
| Comment | 0..1 | string | |
| ResultType | 0..1 | CodeableConceptBinding | |
| RelatedResult | 0..* | Reference(HdBe LaboratoryTestResult) | |
| Requester | 0..1 | Reference(HdBe HealthProfessional) | |
| Performer | 0..1 | Reference(HdBe HealthcareOrganization) |
| LaboratoryTestResult | 0..* | |
| LaboratoryTestResult.LaboratoryTest | BackboneElement | 0..* |
| LaboratoryTestResult.LaboratoryTest.TestCode | CodeableConcept | 1..1 |
| LaboratoryTestResult.LaboratoryTest.TestResult[x] | string, Quantity, CodeableConcept, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | 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 | Count | 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 | string | 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 HealthcareOrganization) | 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 |
|
| Mappings |
|
| 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 | System.String |
| Mappings |
|
| 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 |
|
| Mappings |
|
| LaboratoryTestResult.LaboratoryTest | |
| Definition | Container of the LaboratoryTest concept. This container contains all data elements of the LaboratoryTest concept. |
| Cardinality | 0...* |
| Type | BackboneElement |
| Invariants |
|
| Mappings |
|
| 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 | System.String |
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| LaboratoryTestResult.LaboratoryTest.TestMethod | |
| Definition | The test method used to obtain the result. |
| Cardinality | 0...1 |
| Type | CodeableConcept |
| Binding | TestMethod codes TestMethod (required) |
| Comments |
|
| Invariants |
|
| Mappings |
|
| LaboratoryTestResult.LaboratoryTest.TestDateTime | |
| Definition | The date and if possible the time at which the test was carried out. |
| Cardinality | 0...1 |
| Type | dateTime |
| Invariants |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 |
|
| Invariants |
|
| Mappings |
|
| 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 |
|
| Invariants |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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. |
| 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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| LaboratoryTestResult.Specimen | |
| Definition | Container of the Specimen concept. This container contains all data elements of the Specimen concept. |
| Cardinality | 0...1 |
| Type | BackboneElement |
| Invariants |
|
| Mappings |
|
| 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 | System.String |
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 | Count |
| 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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 (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 |
|
| Mappings |
|
| LaboratoryTestResult.Specimen.AnatomicalLocation | |
| Definition | Anatomical location where the material is collected, *e.g. *elbow. |
| Cardinality | 0...1 |
| Type | HdBe AnatomicalLocation |
| Invariants |
|
| Mappings |
|
| 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 (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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 |
| Invariants |
|
| Mappings |
|
| LaboratoryTestResult.Specimen.CollectionDateTime | |
| Definition | Date and time at which the material was collected. |
| Cardinality | 0...1 |
| Type | dateTime |
| Invariants |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 | string |
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
| Invariants |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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. |
| Cardinality | 0...1 |
| Type | CodeableConcept |
| Binding | ReTaM lab codes https://fhir.healthdata.be/ValueSet/ReTaM (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 |
|
| Mappings |
|
| LaboratoryTestResult.ResultStatus | |
| Definition | The status of the laboratory test result .If the laboratory test is an 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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| 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 |
|
| Mappings |
|
| LaboratoryTestResult.Requester | |
| Definition | The healthcare provider 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 |
|
| Mappings |
|
| LaboratoryTestResult.Performer | |
| Definition | The healthcare provider and/or organization where or by whom the LaboratoryTestResult was performed. |
| Cardinality | 0...1 |
| Type | Reference(HdBe HealthcareOrganization) |
| 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 |
|
| Mappings |
|
Example instances
| LaboratoryTestResult | |
|---|---|
| LaboratoryTest | |
| 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 | |
| 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 |
|---|---|---|
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) |
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). |
Specimen.ReceivedDateTime |
textual | Removed sentence 'This is the issue...' (zib ticket #1551) |
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.InterpretationMethod |
terminology | Removed bound ValuSet because it is invalid. (zib ticket #1292) and (zib ticket #677) |
LaboratoryTest.ResultFlags |
terminology | Removed concepts 'Resistant', 'Intermediate' and 'Susceptible' from the ValueSet. These codes are seen as a quantitative result. (zib ticket #1555) |
LaboratoryTest.ResultFlags |
textual | Removed notion of 'Resistent', 'Intermediate' and 'Susceptible' codes in definition. |
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). |
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. |