Last modified by Robin Huisman on 2025/02/27 09:44
<
From version < 36.1 >
edited by Robin Huisman
on 2024/07/31 23:10
To version < 39.1 >
edited by Robin Huisman
on 2024/08/01 00:16
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Lab result file - SIKB version 14
1 +Lab result file - SIKB0101 v14
Content
... ... @@ -1,13 +1,14 @@
1 -= Exporting lab results to TerraIndex for a customer =
1 += Reporting lab results to TerraIndex for a customer =
2 2  
3 -The file that is used for the examples: [[Example file>>attach:LabResults.xml]]
3 +Returning the labresults to the client, that requested the analysis on samples.
4 4  
5 -{{toc/}}
5 +(% class="box infomessage" %)
6 +(((
7 +More information about SIKB0101 can be found here: [[https:~~/~~/www.sikb.nl/datastandaarden/sikb0101-bodembeheer>>url:https://www.sikb.nl/datastandaarden/sikb0101-bodembeheer]]
8 +)))
6 6  
7 -{{warning}}
8 -SIKB Version 9 is obsolete, and replaced with version 13 or version 14. Latest version can be found here: [[https:~~/~~/www.sikb.nl/datastandaarden/sikb0101-bodembeheer>>url:https://www.sikb.nl/datastandaarden/sikb0101-bodembeheer]]
9 -{{/warning}}
10 10  
11 +
11 11  == What is a Lab result file? ==
12 12  
13 13  A lab result file is an XML file contains all the lab results. The results are mapped tot their analyses samples. A lab result will be matched to the corresponding analyses sample based on the: “Labassignment Guid/SIKB-ID, projectCode, AnalysisSample Guid/SIKB-ID”
... ... @@ -17,286 +17,282 @@
17 17  
18 18  **XSD**: Ask or SIKB Members can download from: [[https:~~/~~/www.sikb.nl/datastandaarden/richtlijnen/sikb0101>>url:https://www.sikb.nl/datastandaarden/richtlijnen/sikb0101]]
19 19  
20 -**Controle XSLT**:
21 +**Controle XSLT**: [[attach:Labresult_Controle.xsl||rel="noopener noreferrer" target="_blank"]]
21 21  
22 22  **Domaintable files**: [[immetingen lookup v14.8.0.xml>>url:https://wiki.terraindex.com/bin/download/Implementation%20documentation/Setting%20up%20Lab%20communication%20by%20REST%20services%20with%20TerraIndex/Lab%20assignment%20file/WebHome/immetingen%20lookup%20v14.8.0.xml?rev=1.2]]   [[imsikb0101 lookup v14.8.0.xml>>url:https://wiki.terraindex.com/bin/download/Implementation%20documentation/Setting%20up%20Lab%20communication%20by%20REST%20services%20with%20TerraIndex/Lab%20assignment%20file/WebHome/imsikb0101%20lookup%20v14.8.0.xml?rev=1.1]]
23 23  extracted from: **[[https:~~/~~/codes.sikb.nl>>url:https://codes.sikb.nl/]] **
24 24  
25 25  
27 +{{toc/}}
26 26  
29 +
30 +== Model Structure ==
31 +
27 27  [[image:IMSIKB0101 - Labresults.png]]
28 28  
29 -== File structure ==
34 +=== Metadata ===
30 30  
31 31  
32 32  (% class="table-hover" %)
33 33  |(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**Unit**
34 -|(% colspan="1" rowspan="1" %)**Versie**|(% colspan="1" rowspan="1" %)The SIKB version of the lab assignment. This must be: **9.0.0**|(% colspan="1" rowspan="1" %)string
35 -|(% colspan="1" rowspan="1" %)**Applicatiecode**|(% colspan="1" rowspan="1" %)This is the application code of your LIMS system that you will get from TerraIndex. Be careful this is not the same code as your laboratory number|(% colspan="1" rowspan="1" %)Integer
36 -|(% colspan="1" rowspan="1" %)**Datum**|(% colspan="1" rowspan="1" %)The date on which the lab result file was made|(% colspan="1" rowspan="1" %)(((
39 +|(% colspan="1" rowspan="1" %)**version**|(% colspan="1" rowspan="1" %)The SIKB version of the lab results file. This must be: **14.8.0 or 14.9.0**|(% colspan="1" rowspan="1" %)string
40 +|(% colspan="1" rowspan="1" %)**application**|(% colspan="1" rowspan="1" %)This is the application code of your LIMS system that you will get from TerraIndex. Be careful this is not the same code as your laboratory number. Your applicationcode can be requested of found here: [[https:~~/~~/codes.sikb.nl/tablet/domain-table-details/50be26c9-5e66-46c9-9373-9d402762876f>>https://codes.sikb.nl/tablet/domain-table-details/50be26c9-5e66-46c9-9373-9d402762876f]] |(% colspan="1" rowspan="1" %)Integer
41 +|(% colspan="1" rowspan="1" %)**reportDate**|(% colspan="1" rowspan="1" %)The date on which the lab result file was made|(% colspan="1" rowspan="1" %)(((
37 37  date
38 38  
39 39  yyyy-mm-dd
40 40  )))
41 -|(% colspan="1" rowspan="1" %)**Klantcode**|(% colspan="1" rowspan="1" %)This should be the customer code in the “//klantcode//” in the lab assignment|(% colspan="1" rowspan="1" %)string
42 -|(% colspan="1" rowspan="1" %)**Laboratorium**|(% colspan="1" rowspan="1" %)The number you get from TerraIndex. This needs to be the same as the laboratorium number in the lab delivery file|(% colspan="1" rowspan="1" %)integer
43 -|(% colspan="1" rowspan="1" %)**Taal**|(% colspan="1" rowspan="1" %)(((
44 -The language of the lab results this depends on the XSD used.
46 +|(% colspan="1" rowspan="1" %)**supplier**|(% colspan="1" rowspan="1" %)The number you get from TerraIndex. This needs to be the same as the laboratorium number in the lab delivery file. Your supplier code can be requested of found here: [[https:~~/~~/codes.sikb.nl/tablet/domain-table-details/dc2ad4df-f958-4146-aee8-31f8c2f1c74b>>https://codes.sikb.nl/tablet/domain-table-details/dc2ad4df-f958-4146-aee8-31f8c2f1c74b]]|(% colspan="1" rowspan="1" %)string
47 +|(% colspan="1" rowspan="1" %)**dataflow**|(% colspan="1" rowspan="1" %)Should be '1' in this case, what stands voor 'AnalysisResults'. Other option can be found here: [[https:~~/~~/codes.sikb.nl/tablet/domain-table-details/79365ded-f56a-4f10-ba45-16bac69752d9>>https://codes.sikb.nl/tablet/domain-table-details/79365ded-f56a-4f10-ba45-16bac69752d9]]|(% colspan="1" rowspan="1" %)integer
45 45  
46 -dut = dutch
49 +===
50 +Labassignment ===
47 47  
48 -eng = English
49 -)))|(% colspan="1" rowspan="1" %)string
50 -|(% colspan="1" rowspan="1" %)**Projectgegevens**|(% colspan="1" rowspan="1" %)This section contains all the result information|(% colspan="1" rowspan="1" %)-
52 +The labassignment is the same as in the labassignment file: [[Lab assignment file - SIKB0101 v14>>https://wiki.terraindex.com/bin/view/Implementation%20documentation/Setting%20up%20Lab%20communication%20by%20REST%20services%20with%20TerraIndex/Lab%20assignment%20file/#]]
51 51  
52 -= Questions from Luca to Robin =
54 +With 3 differences/additions:
53 53  
54 -1. Do I need to add any other classes to the filestructure description apart from the ones below (those related to the IMMetingen::Result Class) ?
55 -1. uit de mail van Robin : "Je kunt de Labassignment pagina als basis gebruiken, en de extra klasses vanuit de Voorbeeld bestand LabResult aan toevoegen."
56 -11. De link naar een "LabResult" voorbeeld bestand wijst naar een directory. Daar staat wel een directory met naam "Example XML 14.8.01". maar die folder bevat niet 1 maar 4 verschillende "labresult_*" XMLs. Welke moet ik hebben? allemaal? en hoe moet ik afleiden welke klasses "extra" zijn? welke tool zou je aanbevelen om xml te lezen. ik heb er nog nooit mee gewerkt.
57 -1. Do i need to add screenshots of the xml classes as in the labassignment and labdelivery pages? if so, what software did you use?
58 -1. In Validation: ValidationScore. What are STOWA Protocols? is it Stichting Toegepast Onderzoek Waterbeheer?
59 -1. What to do with the domain tables refered to in the descriptions? Does it make sense to reference them? Should i translate the names of the domain tables or is that static? are they translated already? who manages these? is it SIKB stuff?
60 -1. in the section MeasureUncertainty > link to pdf file in description is invalid. What should it be?
61 -1. SIKB 14 Parameter result combinations> first sentence makes no sense to me. Please review so i can translate.
62 -1. What should i do with the sections from "Structure projectgegevens" to "What to exchange to store the right results?"? Is this a result of a copy paste and can they be discarded? If not, what classes do they refer to and where can i find the descriptions to be translated?
56 +* Status on the labassignment itself
57 +* Status on the labassignment.sample link
58 +* The labassignment Report number can be send in: LabAssignmentCertificate
63 63  
64 -(% class="wikigeneratedid" %)
65 -~==== Added by luca: all Classes related to "IMMetingen::Results"
66 -
67 -==== MeasureResult ====
68 -
69 -
70 -|**Attribute Name**|**Description**
60 +|**Attribute**|**Notes**
71 71  |(((
72 -**numericValue** Measure
73 -)))|Numeric Value - the numerical value of the observation. When no unit for the measurement is known, the unit 'Dimensionless' should be used.
74 -|(((
75 -**valueProcessingMethod** GenericName
62 +**identification** NEN3610ID
76 76  )))|(((
77 -Value Processing Method - a mathematical/statistical operation that is applied while the method of value determination/analysis standard remains unchanged.
78 -
79 -The operation can be applied to a series of measurement values with the same parameter (quantity/component or typing or taxon or object) or to a series of measurement values with the same analysis method that are summed up to a sum parameter.
80 -
81 -Domain table: Value Processing Method
64 +A unique code that is created when the object is created for the first time.
82 82  )))
83 83  |(((
84 -**qualityIndicatorType** GenericName
67 +**operatingLab** GenericName
68 +
69 +
85 85  )))|(((
86 -Quality Indicator/Judgement -> Detection limit, etc.
71 +Code of the laboratory to which the assignment is assigned.
87 87  
88 -Domain table: Quality Judgement
73 +Domaintable: [[Meetinstantie / Measuring Company>>url:https://codes.sikb.nl/tablet/domain-table-details/4e270f0a-cefe-446e-9d4d-6666c91180a8]]
89 89  )))
90 -
91 -==== Accuracy ====
92 -
93 -
94 -|**Attribute Name**|**Description**|**Unit**
95 95  |(((
96 -**recovery** Float
97 -)))|(((
98 -The part (percentage) of material that is recovered in an analysis.
99 -)))|Percentage [%]
76 +**startTime** DateTime
77 +)))|Dispatch date of the lab assignment
100 100  |(((
101 -**spread** Float
102 -)))|Spread = the error measured (in %) in multiple repeated measurements of the same sample/situation (and by the same laboratory technician/measuring device).|Percentage [%]
103 -|(((
104 -**measurementUncertainty** Float
105 -)))|Measurement uncertainty = the total error in the analysis (in %), considering sample collection, variation in measuring equipment/lab technician, and repeated measurements. It practically represents the value indicating the uncertainty of the measurement result.|Percentage [%]
106 -|(((
107 -**zScore** Float
108 -)))|This is an optional value that indicates how the measurement value scores in relation to other techniques or laboratories. This could be from interlaboratory comparisons or comparisons between different measuring equipment.|
109 -|(((
110 -**drift** Float
111 -)))|This is the degree of sensor drift over time (in %/year). Sensors will age over time and experience more or less drift depending on the conditions. This drift can be quantified and depends partly on age. This is especially true for online sensors.|Percentage [%]
79 +**customerCode** CharacterString
80 +)))|Client code or debtor number of the client as known by the laboratory
112 112  
113 -==== ====
114 114  
115 -==== Validation ====
116 116  
84 +=== LabAssignmentStatus ===
117 117  
118 -This DataClass contains optional attributes and indicates which validation steps the measureResult (measurement value) has undergone.
119 -
120 -
121 121  |**Attribute Name**|**Description**
122 122  |(((
123 -**automatedControl** GenericName
88 +**statusType **GenericName
124 124  )))|(((
125 -The first-line control is often an automated check of whether the measurement value is correct. It uses a domain table: ValidationSteps.
90 +The status of the lab assignment.
126 126  
127 -Various steps can be distinguished. For example, a check on hard/soft limits, ion balance, bandwidth, and dissolved not exceeding total analysis (chemistry) are part of the first-line control. The control can be approved or disapproved (see quality judgment). Different possible values are described in the domain table ValidationSteps. Example: pH of 78 and water temperature of 123 degrees Celsius are hard limits (not possible); pH=10.0 is a soft limit because the value is extremely high (but not impossible).
92 +Use the value '5' for final reported results.
93 +Use other values, or '4', for conceptual values.
128 128  
129 -Domain table: ValidationSteps
95 +Domain table: [[Labassignment Status>>https://codes.sikb.nl/tablet/domain-table-details/5c6ab373-693e-4039-af8d-93206ce4ebb4]]
130 130  )))
131 131  |(((
132 -**expertControl** GenericName
98 +**dateExpected **DateTime
133 133  )))|(((
134 -The second-line control (ExpertControl) is often a specialist check of whether the measurement value is correct. It also uses a domain table: ValidationSteps. Here, different steps can be distinguished as well. This analysis usually does not follow immediately after arrival but is performed periodically. Controls on correlation between measurement stations, history, correlations between parameters, and specialist expertise belong to the second-line control. The control can be approved or disapproved (see quality judgment). Different possible values are described in the domain table ValidationSteps.
100 +The date the results can be expected, in case of conceptual results.
135 135  
136 -Domain table: ValidationSteps
102 +If final, fill with datetime.now.
137 137  )))
104 +
105 +=== LabAssignmentCertificate ===
106 +
107 +|**Attribute Name**|**Description**
138 138  |(((
139 -**validationScore** GenericName
109 +**labCertificateNumber **CharacterString
110 +)))|The number of the certificate that will be send to the user/client, and what is used in the PDF file as order or report number of the laboratory.
111 +|(((
112 +**certification **GenericName
140 140  )))|(((
141 -Score of the validation steps followed, according to the __**STOWA protocols**__. The attribute uses the domain table ValidationScore. The score value ranges from 0 to 5
114 +Under which certificate the analyses has been done. If you do not find you code leave this field empty
142 142  
143 -Domain table: ValidationScore
116 +Domain table: [[Certification Coding>>https://codes.sikb.nl/tablet/domain-table-details/df7ffd7c-192c-44f7-ae9f-0461d9266b30]]
144 144  )))
145 145  
146 -==== ====
119 +== LabAssignmentRequest ==
147 147  
148 -==== AnalyticResult ====
121 +The connection between the labassignment and the samples with analysisrequests, as send in the labassignment.
149 149  
123 +If not retreived in a labassignment, make it yourself so we can import is as new samples.
124 +Just fill what you can fill, otherwise leave field empty, based on documentation here: [[Labassignment file - SIKB0101 v14>>https://wiki.terraindex.com/bin/view/Implementation%20documentation/Setting%20up%20Lab%20communication%20by%20REST%20services%20with%20TerraIndex/Lab%20assignment%20file/#]]
125 +
150 150  
151 -The analyzed result of an observation, typically originating from a laboratory.
127 +== Project ==
152 152  
129 +Activity that leads to the collection of soil data, as send in the labassignment.
130 +It will be used to search the correct project/investiation to bind or create the samples.
153 153  
154 -|=**Attribute Name**|=**Description**
132 +|**Attribute**|**Notes**
155 155  |(((
156 -**limitSymbol** CharacterString
157 -)))|(((
158 -LimietSymbool, allowed values: '&lt;' en '&gt;'.
134 +**identification** NEN3610ID
135 +)))|The unique identifier of the Project in TerraIndex and in the whole Exchange Chain, as send in the labassignment
136 +|(((
137 +**name** CharacterString
159 159  
160 -'&lt;' stands for 'less than the lowest threshold'
139 + [0..1]
140 +)))|The name of the project where the lab results are for, as send in the labassignment
141 +|(((
142 +**projectCode** CharacterString
143 +)))|The project code of the project where the lab results are for, as send in the labassignment
161 161  
162 -'&gt;' stands for 'greater than the highest threshold'
145 +== Sample (AnalysisSample) ==
163 163  
164 -The boundary for the limit symbol can be specified in the DeterminationLimits (LimitSymbolReferenceCode) as a reference with the actual value of the limit. The value can be included in the exchange in two ways:
147 +The analysissamples with analysisrequests, as send in the labassignment. The fieldsamples form the labassignment can be skipped in the results file.
165 165  
166 -1) as a CData block: <![CDATA[<]]> or <![CDATA[>]]>
149 +If not retreived in a labassignment, make it yourself so we can import is as new analysissamples.
150 +Just fill what you can fill, based on documentation here: [[Labassignment file - SIKB0101 v14>>https://wiki.terraindex.com/bin/view/Implementation%20documentation/Setting%20up%20Lab%20communication%20by%20REST%20services%20with%20TerraIndex/Lab%20assignment%20file/#]]
167 167  
168 -2) as HTML code: '&amp; lt;' or '&amp; gt;'
152 +(% class="box infomessage" %)
153 +(((
154 +Please keep these scenario's in mind: [[Analysissample scenario's>>https://wiki.terraindex.com/bin/view/Implementation%20documentation/Setting%20up%20Lab%20communication%20by%20REST%20services%20with%20TerraIndex/Lab%20assignment%20file/#HWhatsamplescenario27sareexchanged3F]]
169 169  )))
156 +
157 +|**Attribute**|**Notes**
170 170  |(((
171 -**alphanumericValue** CharacterString
172 -)))|Textual value associated with an analysis result
159 +**identification** NEN3610ID
160 +)))|The unique identifier of TerraIndex for the analyses sample, to keep this value unique forever in the whole exchange chain.
161 +|(((
162 +**name** CharacterString
173 173  
174 -==== ====
164 + [0..1]
165 +)))|Name given to the sample
166 +|(((
167 +**specimenType** GenericName
175 175  
176 -==== MeasureUncertainty ====
169 + [0..1]
170 +)))|(((
171 +Type of Sample- Fieldsample, Analysissample
177 177  
173 +For analysissamples fill with value '10'.
178 178  
179 -Measurement uncertainty in the result. This is the expanded measuring uncertainty as described in the document: [[http:~~/~~/www.nordicinnovation.net/nordtestfiler/tec537.pdf>>http://www.nordicinnovation.net/nordtestfiler/tec537.pdf]]
180 -
181 -
182 -|=**Attribute Name**|=**Description**
175 +Domaintable: [[MonsterType / SampleType>>url:https://codes.sikb.nl/tablet/domain-table-details/9f956093-baad-4adb-b74d-20c00cef6ab4]]
176 +)))
183 183  |(((
184 -**distributionType** GenericName
178 +**materialClass** GenericName
179 +
180 +
185 185  )))|(((
186 -The type of statistical distribution associated with the observation.
182 +An SIKB code for the matrix type. Soil, Groundwater etc..
187 187  
188 -Domain table: ProbabilityDistribution
184 +Domaintable: [[Compartiment / Matrix>>url:https://codes.sikb.nl/tablet/domain-table-details/6134f3bb-6048-431d-a130-01290d84172c]]
189 189  )))
186 +
187 +== Analysis ==
188 +
189 +The measured parameter with it's value and process.
190 +
191 +|**Attribute Name**|**Description**
190 190  |(((
191 -**statisticalParameter** Measure
193 +**identification** NEN3610ID
194 +)))|The unique identifier of the AnalysisResult, to keep this value unique forever in the whole exchange chain.
195 +If not possible to store this in the Lims, generate on the fly.
196 +(% class="info" %)|(((
197 +**physicalProperty **PhysicalProperty
192 192  )))|(((
193 -Parameters that determine the shape and size of the statistical distribution.
199 +The combination of Quantity, Parameter and Condition to provide the parameter that has been measured.
200 +**[[See this chapter for the combinations, and the CAS-NR's. >>https://wiki.terraindex.com/bin/view/Implementation%20documentation/Setting%20up%20Lab%20communication%20by%20REST%20services%20with%20TerraIndex/Lab%20result%20file/#HSIKB14Parameterresultcombinations]]**
194 194  
195 -Domain table: StatisticalParameter
202 +
196 196  )))
204 +|**result **AnalyticResult|The result of the analysis, see next chapter.
205 +|**procedure **AnalysisProcess|The process that has been used to measure/determine the result, see next chapter.
197 197  
198 -==== ====
199 199  
200 -==== DeterminationLimits ====
201 201  
209 +=== AnalyticResult (inherited from MeasureResult) ===
202 202  
203 -|=**Attribute Name**|=**Description**
211 +The actual reported value, result of detection limit.
212 +
213 +|**Attribute Name**|**Description**
204 204  |(((
205 -**detectionLimit** Measure
215 +**numericValue** Measure
206 206  )))|(((
207 -The smallest value of the measured content or the observed value of the parameter in a sample, which can still be determined with a certain reliability by the laboratory. Conventionally, this is the amount that corresponds to three times the standard deviation at that level (thus, relative standard deviation is 33%).
217 +Numeric Value - the numerical value of the observation. When no unit for the measurement is known, the unit 'Dimensionless' should be used.
208 208  
219 +Domaintable for Units: [[Eenheid>>https://codes.sikb.nl/tablet/domain-table-details/04f4f467-021b-4218-baa8-9742ed977c61]]
220 +)))
221 +|(((
222 +**valueProcessingMethod** GenericName
223 +)))|(((
224 +Value Processing Method - a mathematical/statistical operation that is applied while the method of value determination/analysis standard remains unchanged.
209 209  
210 -The standard deviation is established under (intra-lab) reproducibility. Also known in English as 'LOD' (Limit of Detection). See also: [[Wikipedia on Detection Limit>>url:https://en.wikipedia.org/wiki/Detection_limit]]
226 +The operation can be applied to a series of measurement values with the same parameter (quantity/component or typing or taxon or object) or to a series of measurement values with the same analysis method that are summed up to a sum parameter.
227 +\\Default the value '5' meaning 'Not available' can and should be used, besides leaving it empty.
228 +
229 +Domain table: [[Value Processing Method>>https://codes.sikb.nl/tablet/domain-table-details/a2310c26-065f-4aec-9440-74892ec77753]]
211 211  )))
212 212  |(((
213 -**reportingLimit** Measure
214 -)))|The smallest value of the measured content or the observed value of the parameter in a sample, agreed upon with the client by the executing laboratory, which is reported to the client. The reporting limit is at least the detection limit and is sometimes specified in an accreditation scheme like AS3000.
215 -|(((
216 -**limitSymbolReferenceCode **GenericName
232 +**qualityIndicatorType** GenericName
217 217  )))|(((
218 -The threshold value that the limitSymbol of AnalyticResult refers to.
234 +Quality Indicator/Judgement -> Detection limit, etc.
235 +\\Default the value '0' meaning 'Not available' can and should be used, besides leaving it empty.
236 +If there is a detectionlimit/reportinglimit, use: '4', meaning 'determenated with full detection limit'
219 219  
220 -Domain table: LimitSymbolReference
238 +Domain table: [[Quality Judgement>>https://codes.sikb.nl/tablet/domain-table-details/1e17d9e6-4e0e-4f88-8fe5-c71f6a7931db]]
221 221  )))
240 +
222 222  |(((
223 -**quantitationLimit** Measure
224 -)))|The smallest value of the measured content or the observed value of the parameter in a sample, which can still be determined with a certain reliability by the laboratory. Conventionally, this is the amount that corresponds to ten times the standard deviation at that level (thus, relative standard deviation is 10%). Also known in English as 'LOQ' (Limit of Quantitation). At this value, the rate of 'false negatives' is less than 1%.
242 +**limitSymbol** CharacterString
243 +)))|(((
244 +LimietSymbool, allowed values: '&lt;' en '&gt;'.
225 225  
226 -=== ===
246 +'&lt;' stands for 'less than the lowest threshold'
227 227  
228 -=== Structure projectgegevens ===
248 +'&gt;' stands for 'greater than the highest threshold'
229 229  
230 -(% style="text-align:center" %)
231 -[[image:1637656734277-997.png]]
250 +The boundary for the limit symbol can be specified in the DeterminationLimits (LimitSymbolReferenceCode) as a reference with the actual value of the limit. The value can be included in the exchange in two ways:
232 232  
252 +1) as a CData block: <![CDATA[<]]> or <![CDATA[>]]>
233 233  
234 -(% class="table-hover" %)
235 -|(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**Unit**
236 -|(% colspan="1" rowspan="1" %)**idopdracht**|(% colspan="1" rowspan="1" %)The TerraIndex id of the lab assignment the result belongs to.|(% colspan="1" rowspan="1" %)-
237 -|(% colspan="1" rowspan="1" %)**projectcode**|(% colspan="1" rowspan="1" %)The project code of the project as it was delivered in the lab assignment|(% colspan="1" rowspan="1" %)string
238 -|(% colspan="1" rowspan="1" %)**projectnaam**|(% colspan="1" rowspan="1" %)The name of the project as it was delivered in the lab assignment.|(% colspan="1" rowspan="1" %)string
239 -|(% colspan="1" rowspan="1" %)**ordernummer**|(% colspan="1" rowspan="1" %)Not relevant. The order in which the lab result could be shown|(% colspan="1" rowspan="1" %)string
240 -|(% colspan="1" rowspan="1" %)**projectleider**|(% colspan="1" rowspan="1" %)The project leader of the customer. This needs the be the “contactpersoon” from the lab assignment with the code PL|(% colspan="1" rowspan="1" %)string
241 -|(% colspan="1" rowspan="1" %)**status**|(% colspan="1" rowspan="1" %)The status of the lab assignment. See Labstatus Codegroup 76 in the attachments for all the options.|(% colspan="1" rowspan="1" %)integer
242 -|(% colspan="1" rowspan="1" %)**datumverwacht**|(% colspan="1" rowspan="1" %)The date on which the lab expects the certificate to be available|(% colspan="1" rowspan="1" %)Date
243 -yyyy-mm-dd
244 -|(% colspan="1" rowspan="1" %)**certificaatnummer**|(% colspan="1" rowspan="1" %)The number of the certificate that will be send to the user.|(% colspan="1" rowspan="1" %)string
245 -|(% colspan="1" rowspan="1" %)(((
246 -**analysemonsters**
254 +2) as HTML code: '&amp; lt;' or '&amp; gt;'
255 +\\Default the value is leaving it empty.
256 +If there is a detectionlimit/reportinglimit, use: '<'
257 +)))
258 +|(((
259 +**alphanumericValue** CharacterString
260 +)))|Textual value associated with an analysis result
247 247  
262 +==== ====
248 248  
249 -
250 -)))|(% colspan="1" rowspan="1" %)A table containing all the analysis sample with their corresponding results|(% colspan="1" rowspan="1" %)-
264 +==== ====
251 251  
252 -== Structure analysemonsters ==
253 253  
254 -(% style="text-align:center" %)
255 -[[image:1637656914799-534.png]]
256 256  
257 -(% class="table-hover" %)
258 -|(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**Unit**
259 -|(% colspan="1" rowspan="1" %)**Idanlmons**|(% colspan="1" rowspan="1" %)The unique identification code of the analyses sample as given in the lab assignment file|(% colspan="1" rowspan="1" %)string
260 -|(% colspan="1" rowspan="1" %)**Anlmons**|(% colspan="1" rowspan="1" %)The name of the analyses sample as given in the lab assignment file|(% colspan="1" rowspan="1" %)string
261 -|(% colspan="1" rowspan="1" %)**Certificaat**|(% colspan="1" rowspan="1" %)The way the name of the sample should be on the certificate. This is also given in the lab assignment|(% colspan="1" rowspan="1" %)string
262 -|(% colspan="1" rowspan="1" %)**Monstersoort**|(% colspan="1" rowspan="1" %)The code referencing the type the sample is. Check the attachment: Sample type codegroup 51 for all the options|(% colspan="1" rowspan="1" %)integer
263 -|(% colspan="1" rowspan="1" %)**Status**|(% colspan="1" rowspan="1" %)The status of the sample. See Labstatus Codegroup 76 in the attachments.|(% colspan="1" rowspan="1" %)integer
264 -|(% colspan="1" rowspan="1" %)**Datumverwacht**|(% colspan="1" rowspan="1" %)The date on which the results for the sample are expected|(% colspan="1" rowspan="1" %)(((
265 -date
268 +=== AnalysisProcess ===
266 266  
267 -yyyy-mm-dd
268 -)))
269 -|(% colspan="1" rowspan="1" %)**Volgorde**|(% colspan="1" rowspan="1" %)Is a unused field in TerraIndex|(% colspan="1" rowspan="1" %)integer
270 -|(% colspan="1" rowspan="1" %)**analyseresultaten**|(% colspan="1" rowspan="1" %)A table containing all the measurement values of the analysis samples.|(% colspan="1" rowspan="1" %)-
270 +The process that has been used to detemine the measured value or result.
271 271  
272 -== Structure analyseresultaten ==
272 +|**Attribute Name**|**Description**
273 +|(((
274 +**identification** NEN3610ID
275 +)))|The unique identifier of the AnalysisProcess, it can be bound to multiple results at once.
276 +|**analyticalTechnique **GenericName|(((
277 +The used analytical technique to detemine the result.
273 273  
274 -(% style="text-align:center" %)
275 -[[image:1637657248973-790.png]]
279 +Domain table: [[AnalyticalTechnique>>https://codes.sikb.nl/tablet/domain-table-details/04be2365-3d05-4903-a53e-edafef7111e8]]
280 +)))
281 +|**certification **GenericName|(((
282 +The used certification to detemine the result.
276 276  
277 -(% class="table-hover" %)
278 -|(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**Unit**
279 -|(% colspan="1" rowspan="1" %)**componentcode**|(% colspan="1" rowspan="1" %)The SIKB component code. See ComponentCode Codegroup 52 in the attachements for all possible options.|(% colspan="1" rowspan="1" %)integer
280 -|(% colspan="1" rowspan="1" %)**meetwaarde**|(% colspan="1" rowspan="1" %)What the measured value is for the analyses|(% colspan="1" rowspan="1" %)float
281 -|(% colspan="1" rowspan="1" %)**meetwaardeomschrijving**|(% colspan="1" rowspan="1" %)Alpha numerical description of the result|(% colspan="1" rowspan="1" %)string
282 -|(% colspan="1" rowspan="1" %)**eenheidcode**|(% colspan="1" rowspan="1" %)The unit of the measured value. See Unit CodeGroup 40 in the attachements for all possible options|(% colspan="1" rowspan="1" %)integer
283 -|(% colspan="1" rowspan="1" %)**referentiecode**|(% colspan="1" rowspan="1" %)This defines what the reference for the measurement value is. See ReferenceType CodeGroup 41 for all the possible options|(% colspan="1" rowspan="1" %)integer
284 -|(% colspan="1" rowspan="1" %)**analysenorm**|(% colspan="1" rowspan="1" %)Against which standard the analysis has been tested. See Laboratory method Codegroup 57 in the attachments for all the option. I your standard is not in the list leave this empty|(% colspan="1" rowspan="1" %)integer
285 -|(% colspan="1" rowspan="1" %)**datummonstervoorbehandeling**|(% colspan="1" rowspan="1" %)The date on which the sample was pre-treated. We don’t do anything with this value|(% colspan="1" rowspan="1" %)(((
286 -date
284 +Domain table: [[CertificationCode>>https://codes.sikb.nl/tablet/domain-table-details/04be2365-3d05-4903-a53e-edafef7111e8]]
285 +)))
286 +|**valuationMethod **GenericName|(((
287 +The used valuation method to detemine the result.
287 287  
288 -yyyy-mm-dd
289 +Domain table: [[ValuationMethod>>https://codes.sikb.nl/tablet/domain-table-details/04be2365-3d05-4903-a53e-edafef7111e8]]
289 289  )))
290 -|(% colspan="1" rowspan="1" %)**opmerking**|(% colspan="1" rowspan="1" %)A remark for this result|(% colspan="1" rowspan="1" %)string
291 -|(% colspan="1" rowspan="1" %)**certificering**|(% colspan="1" rowspan="1" %)Under which certificate the analyses has been done. See CertificateCode Codegroup 48 for all the possible options. If you do not find you code leave this field empty|(% colspan="1" rowspan="1" %)integer
292 -|(% colspan="1" rowspan="1" %)**status**|(% colspan="1" rowspan="1" %)The status of the labresult in the labassignemnt. See Labstatus Codegroep 76 in the attachments|(% colspan="1" rowspan="1" %)integer
293 -|(% colspan="1" rowspan="1" %)**datumverwacht**|(% colspan="1" rowspan="1" %)Date on which the analyses results are expected.|(% colspan="1" rowspan="1" %)date
294 294  
295 -= =
292 += What to exchange to bind the right results to the right sample? =
296 296  
297 -= What to exchange to store the right results? =
294 +The data stream ‘Lab Result’ is the feedback of analysis results on the requested lab assignment at a laboratory. At import we need to bind it onto the correct sample.
298 298  
299 -The data stream ‘Lab Result’ is the feedback of analysis results on the requested lab assignment at a laboratory.
296 +This requires importand field to match the samples in the xml to the samples in our database.
300 300  
301 301  **Important fields:**
302 302  
... ... @@ -316,7 +316,7 @@
316 316  * For Asbestos and Asphalt, new samples are also created at the Lab, which are therefore fed back with a reference to the sample from which they are derived.
317 317  * There is still a desire to feedback from a lab whether an analysis sample has been modified at the lab in terms of sub-samples. For example, if a jar has broken and been replaced with another jar. This has not yet been included in current practices.
318 318  
319 -**Importing the data can be done based on the following steps:**
316 +**Importing the data will be done based on the following steps:**
320 320  
321 321  * Search Project with Project.lokaalID (as placed in the Lab assignment XML).
322 322  * Search Project with Project.ProjectCode (as placed in the Lab assignment XML) if searching on Project.LokaalID yields no results.
... ... @@ -338,6 +338,12 @@
338 338  \\[[image:1713183008796-215.png]]
339 339  *small remark, condition will be used as: [0..1]
340 340  
338 +Domaintables bound to these fields:
339 +
340 +* Quantity -[[ Parameter, but only group/groep: Grootheid (Quantity)>>https://codes.sikb.nl/tablet/domain-table-details/0eafa483-2875-4c94-890d-66258a6b4d88]]
341 +* Parameter -[[ Parameter, but mainly group/groep: Chemische Stof (Chemical substance)>>https://codes.sikb.nl/tablet/domain-table-details/0eafa483-2875-4c94-890d-66258a6b4d88]]
342 +* Condition - Condition, but not group/groeps that refer to Chemical substance.
343 +
341 341  The combinations are defined for different compartiments like soil/ground, groundwater, wastewater.
342 342  Below are some examples, and some attachments included to support all combinations.
343 343  
... ... @@ -344,23 +344,31 @@
344 344  **2 Examples for Soil:**
345 345  
346 346  |__**Parameter Name**__|__**Parameter ID**__|__**Quantity ID**__|__**Quantity name**__|__**Condition ID**__|__**Condition Name**__
347 -|lood|1116|2725|Massafractie|1|t.o.v. drooggewicht
348 -|minerale olie|1200|2725|Massafractie|93|koolwaterstoffractie C10-C40 / drooggewicht
350 +|lood
351 +(lead)|1116|2725|Massafractie
352 +(Massfraction)|1|t.o.v. drooggewicht
353 +(relative to dry weight)
354 +|minerale olie
355 +(minerale oil)|1200|2725|Massafractie
356 +(Massfraction)|93|koolwaterstoffractie C10-C40 / drooggewicht
357 +(hydrocarbon fraction C10-C40 / dry weight)
349 349  
350 350  **2 Examples for Groundwater:**
351 351  
352 352  |__**Parameter Name**__|__**Parameter ID**__|__**Quantity ID**__|__**Quantity name**__|__**Condition ID**__|__**Condition Name**__|
353 353  |cyanide-complex|2595|2720|(massa)Concentratie|9|opgeloste fractie (bijv. na filtratie)
354 -|som 29 dioxines (Bbk, 1-10-2010, als TEQ)|2160|2720|(massa)Concentratie|10|uitgedrukt in Toxiciteit equivalenten
363 +|som 29 dioxines (TEQ)|2160|2720|(massa)Concentratie|10|uitgedrukt in Toxiciteit equivalenten
355 355  
356 356  **2 Examples for Wastewater:**
357 357  
358 358  |__**Parameter Name**__|__**Parameter ID**__|__**Quantity ID**__|__**Quantity name**__|__**Condition ID**__|__**Condition Name**__|
359 359  |cyanide-complex|2595|2720|(massa)Concentratie|8|Niet van toepassing
360 -|som 29 dioxines (Bbk, 1-10-2010, als TEQ)|2160|2720|(massa)Concentratie|10|uitgedrukt in Toxiciteit equivalenten
369 +|som 29 dioxines (TEQ)|2160|2720|(massa)Concentratie|10|uitgedrukt in Toxiciteit equivalenten
361 361  
362 362  __**Full combinations sheet:  **__[[attach:Full List of AnalysisResult combinations 04-2024.xlsx||rel="noopener noreferrer" target="_blank"]]
363 363  
373 +We can help you with the right combinations and mappings to your own codes.
364 364  
365 365  
376 +
366 366  

Navigation

TerraIndex
asd