Changes for page Lab delivery file - SIKB version 14
Last modified by Robin Huisman on 2024/12/18 14:57
From version 54.1
edited by Robin Huisman
on 2024/12/18 14:57
on 2024/12/18 14:57
Change comment:
There is no comment for this version
To version 42.1
edited by Robin Huisman
on 2024/04/05 15:41
on 2024/04/05 15:41
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Lab delivery file - SIKB version 14 1 +Lab delivery file - SIKB version 14.8.0 - Content
-
... ... @@ -1,14 +1,14 @@ 1 1 = Creating a Delivery file and binding them to a customer = 2 2 3 -This chapter contains the information needed to understand the lab delivery file. A Lab delivery file only has to be updated when there are changes. Otherwise ,TerraIndex will always show the last imported file.3 +This chapter contains the information needed to understand the lab delivery file. A Lab delivery file only has to be updated when there are changes. Otherwise TerraIndex will always show the last imported file. 4 4 5 5 {{warning}} 6 6 Latest version can be found here: [[https:~~/~~/www.sikb.nl/datastandaarden/sikb0101-bodembeheer>>url:https://www.sikb.nl/datastandaarden/sikb0101-bodembeheer]] 7 7 {{/warning}} 8 8 9 -== What is a lab delivery file ?==9 +== What is a lab delivery file == 10 10 11 -A lab delivery file contains the Customer code of the customer that will be sending the lab assignment. It also contains the analyses that can be requested from the lab by the customer. A Lab delivery file needs to be custom for every user and needs to be a nXML file. This file will be available for the customer to choose their options for requesting and ordering an analysis at the lab. It's the Menu-card of the Lab, the user can choose from.11 +A lab delivery file contains the Customer code of the customer that will be sending the lab assignment. It also contains the analyses that can be requested from the a lab by the customer. A Lab delivery file needs to be custom for every user and needs to be a XML file 12 12 13 13 **Example files**: [[attach:Labdeliveryfile.xml||rel="noopener noreferrer" target="_blank"]] 14 14 ... ... @@ -15,18 +15,15 @@ 15 15 **XSD**: [[attach:LabDelivery_v14.8.0.xsd||rel="noopener noreferrer" target="_blank"]] 16 16 17 17 **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]] 18 -extracted from: **[[https:~~/~~/codes.sikb.nl>>url:https://codes.sikb.nl/]] 19 -\\Translations English to Dutch: **[[attach:LabdeliveryFile_14.8.0_ENG_NL.xslt||rel="noopener noreferrer" target="_blank"]] 18 +extracted from: **[[https:~~/~~/codes.sikb.nl>>url:https://codes.sikb.nl/]] ** 20 20 21 - 22 22 {{toc/}} 23 23 24 24 25 -[[image:1722464591905-118.png]] 26 - 27 27 == File structure == 28 28 29 -In the image below, the main structure of the XML file is shown. Every table is described in more detail later on in this chapter. 25 +In the image below the main structure of the XML file is shown. Every table is described in more detail later on in this chapter. 26 +[[image:1712158795900-531.png||height="604" width="391"]] 30 30 31 31 (% class="table-hover" %) 32 32 |(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**Unit** ... ... @@ -76,7 +76,7 @@ 76 76 77 77 “Category” does not need a lot of explanation. A category is a group defined by the lab where certain values in the “koppeltabel” can be grouped under. A category is determined by the lab and can be used in the “Links”. 78 78 79 -In TerraIndex ,it will be shownas Header/Group:76 +In TerraIndex it will be showed as Header/Group: 80 80 [[image:1712162927138-349.png]] 81 81 82 82 ... ... @@ -86,19 +86,19 @@ 86 86 (% class="table-hover" %) 87 87 |(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**Unit** 88 88 |(% colspan="1" rowspan="1" %)**CategorieId**|(% colspan="1" rowspan="1" %)The code/Id of the category or group given by the lab|(% colspan="1" rowspan="1" %)string 89 -|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)The name/description of the category (This will also be shown in the user interface , in alphabtical order)|(% colspan="1" rowspan="1" %)string90 -|(% colspan="1" rowspan="1" %)**Sequence**|(% colspan="1" rowspan="1" %) The fieldto assignan order/serquence for the presentation ofthecategoryin the interface of TerraIndex|(% colspan="1" rowspan="1" %)integer86 +|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)The name/description of the category (This will also be shown in the user interface)|(% colspan="1" rowspan="1" %)string 87 +|(% colspan="1" rowspan="1" %)**Sequence**|(% colspan="1" rowspan="1" %)Field is redundant and does not have to be filled|(% colspan="1" rowspan="1" %)integer 91 91 92 92 == Structure explanation AnalysisLink and Analysis == 93 93 94 -This table contains all the analyses that a nanalysis package can contain. Be sure the “analysepakketcode” corresponds to a code in the table: “analysepakketten”. The analysecode is your own identification code for the analyses.91 +This table contains all the analyses that a analyses package can contain. Be sure the “analysepakketcode” corresponds to a code in the table: “analysepakketten”. The analysecode is your own identification code for the analyses. 95 95 \\[[image:1712163145392-331.png]] 96 96 \\[[image:1712163459761-326.png||height="488" width="799"]] 97 97 98 98 (% class="table-hover" %) 99 99 |(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**Unit** 100 -|(% colspan="1" rowspan="1" %)**AnalysisSetId**|(% colspan="1" rowspan="1" %)The analys isset code that corresponds to a code in the “//AnalysisSets//”|(% colspan="1" rowspan="1" %)string101 -|(% colspan="1" rowspan="1" %)**Analysis**|(% colspan="1" rowspan="1" %)A table containing al lthe analyses that should be in this analysis set or package|(% colspan="1" rowspan="1" %)-97 +|(% colspan="1" rowspan="1" %)**AnalysisSetId**|(% colspan="1" rowspan="1" %)The analyse set code that corresponds to a code in the “//AnalysisSets//”|(% colspan="1" rowspan="1" %)string 98 +|(% colspan="1" rowspan="1" %)**Analysis**|(% colspan="1" rowspan="1" %)A table containing ale the analyses that should be in this analysis set or package|(% colspan="1" rowspan="1" %)- 102 102 103 103 === __Analysis__ === 104 104 ... ... @@ -111,7 +111,7 @@ 111 111 112 112 == Structure explanation Clients == 113 113 114 -A customer can have multiple “clients”. There always needs to be one “client” so that a lab assignment can be sen t. But for example,when there is a price agreement for a certain project,a new “Client” can be added. Or when a company has multiple offices,every office can have its own “Client”.111 +A customer can have multiple “clients”. There always needs to be one “client” so that a lab assignment can be send. But for example when there is a price agreement for a certain project a new “Client” can be added. Or when a company has multiple offices every office can have its own “Client”. 115 115 \\It will be shown in the interface of TerraIndex, and needs to be chosen before selecting analysis sets: 116 116 [[image:1712163957735-690.png]] 117 117 \\[[image:1712163986350-364.png||height="409" width="544"]] ... ... @@ -118,11 +118,11 @@ 118 118 119 119 |(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**Unit** 120 120 |(% colspan="1" rowspan="1" %)**ClientId**|(% colspan="1" rowspan="1" %)The customer identification code(s) for the company or office|(% colspan="1" rowspan="1" %)string 121 -|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)The name\description of the customer code, as shown in the interface ,and will be invoiced.|(% colspan="1" rowspan="1" %)string118 +|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)The name\description of the customer code, as shown in the interface and will be invoiced.|(% colspan="1" rowspan="1" %)string 122 122 123 123 == Structure explanation LabSampleMatrices == 124 124 125 -The “LabSampleMatrices” is an important section of the XML. The “matrix” defines the main type of sample for the lab, and can contain multiple or pre defined additional pretreatments of preservatives. Without a sample type in this table,a customer will not be able to send in lab assignments to the laboratory.122 +The “LabSampleMatrices” is an important sections of the XML. The “matrix” defines the main type of sample for the lab, and can contain multiple or prefined additional pretreatments of preservations. Without a sample type in this table a customer will not be able to send in lab assignments to the laboratory. 126 126 127 127 It needs to be chosen in the interface of TerraIndex, before any analysis set can be chosen: 128 128 \\[[image:1712164314258-543.png]] ... ... @@ -132,15 +132,15 @@ 132 132 133 133 (% class="table-hover" %) 134 134 |(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**unit** 135 -|(% colspan="1" rowspan="1" %)**CompartimentId**|(% colspan="1" rowspan="1" %)An SIKB ID that determin es to which matrix the analyses belongs.132 +|(% colspan="1" rowspan="1" %)**CompartimentId**|(% colspan="1" rowspan="1" %)An SIKB ID that determins to which matrix the analyses belongs. 136 136 Domaintable: [[Compartment/Matrix>>https://codes.sikb.nl/tablet/domain-table-details/6134f3bb-6048-431d-a130-01290d84172c]]|(% colspan="1" rowspan="1" %)int 137 137 |(% colspan="1" rowspan="1" %)//CompartimentCode//|(% colspan="1" rowspan="1" %)-not in use-|(% colspan="1" rowspan="1" %) 138 -|(% colspan="1" rowspan="1" %)**LabSampleMatrixCode**|(% colspan="1" rowspan="1" %)The laboratory matrix- or compartment-code of the lab, that will be also be sen tin the Labassignment to the lab|(% colspan="1" %)string135 +|(% colspan="1" rowspan="1" %)**LabSampleMatrixCode**|(% colspan="1" rowspan="1" %)The laboratory matrix- or compartment-code of the lab, that will be also be send in the Labassignment to the lab|(% colspan="1" %)string 139 139 |(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)The name\description of the matrix or compartment of the lab, as shown in the interface.|(% colspan="1" rowspan="1" %)string 140 140 141 141 == Structure explanation SpecialAppointment == 142 142 143 -The “SpecialAppointment" contains the names of the price catalogs, the default quote or the special project quote. This way ,extra discount options are possible. It will be sentin the labassignment to the lab.140 +The “SpecialAppointment" contains the names of the price catalogus, the default quote or the special project quote. This way extra discount options are possible. It will be send in the labassignment to the lab. 144 144 145 145 It needs to be chosen in the interface of TerraIndex, before any analysis set can be chosen, and empty means 'default quote': 146 146 ... ... @@ -151,16 +151,16 @@ 151 151 152 152 (% class="table-hover" %) 153 153 |(% colspan="1" rowspan="1" %)**Attribute name**|(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)**unit** 154 -|(% colspan="1" rowspan="1" %)**SpecialAppointmentId**|(% colspan="1" rowspan="1" %)An identif ication code from the lab that will be sentin the Labassignment to the lab.|(% colspan="1" rowspan="1" %)string151 +|(% colspan="1" rowspan="1" %)**SpecialAppointmentId**|(% colspan="1" rowspan="1" %)An identifcation code from the lab that will be send in the Labassignment to the lab.|(% colspan="1" rowspan="1" %)string 155 155 |(% colspan="1" rowspan="1" %)**Description**|(% colspan="1" rowspan="1" %)The name\description of the matrix or compartment of the lab, as shown in the interface.|(% colspan="1" rowspan="1" %)string 156 156 |(% colspan="1" rowspan="1" %)//startdate//|(% colspan="1" rowspan="1" %)-not in use-|(% colspan="1" rowspan="1" %) 157 157 |(% colspan="1" rowspan="1" %)//finaldate//|(% colspan="1" rowspan="1" %)-not in use-|(% colspan="1" rowspan="1" %) 158 -|(% colspan="1" rowspan="1" %)**AppointmentTypeCode**|(% colspan="1" rowspan="1" %)The type of appointment, like: total pricelist, default quotation or special project agreement. 155 +|(% colspan="1" rowspan="1" %)**AppointmentTypeCode**|(% colspan="1" rowspan="1" %)The type of appointment, like: total pricelist, default quotation or special project agreement. 159 159 Domaintable: [[PriceAgreement Type>>https://codes.sikb.nl/tablet/domain-table-details/60028a8a-f386-47bf-bf2e-f46af49b7b56]]|(% colspan="1" rowspan="1" %)int 160 160 161 161 == Structure explanation Links == 162 162 163 -The “Links” is one of the most important sections of the XML. The “Link” defines the combination of Analysespackages, cust omer/clientcode, categories and sampletype. Without a combination in this table,a customer will not be able to send in lab assignments to the laboratory.160 +The “Links” is one of the most important sections of the XML. The “Link” defines the combination of Analysespackages, custerom/clientcode, categories and sampletype. Without a combination in this table a customer will not be able to send in lab assignments to the laboratory. 164 164 [[image:1712158823685-514.png||height="563" width="531"]] 165 165 166 166 ... ... @@ -176,7 +176,7 @@ 176 176 ))) 177 177 |(% colspan="1" %)Price|(% colspan="1" %)The optional Price indication for this combination of the Analysis|(% colspan="1" %)decimal 178 178 |(% colspan="1" %)CertificationId|(% colspan="1" %)The optional code that corresponds to the way of Sample and analysis handling as described in a certification. 179 -Some other labs have this arra nged by the LabSampleMatrix types.176 +Some other labs have this arragened by the LabSampleMatrix types. 180 180 Domaintable: [[CertificeringsCode >>https://codes.sikb.nl/tablet/domain-table-details/df7ffd7c-192c-44f7-ae9f-0461d9266b30]]|(% colspan="1" %)int 181 181 |(% colspan="1" rowspan="1" %)**CategoryId**|(% colspan="1" rowspan="1" %)The code that corresponds to a category code in Categories table|(% colspan="1" rowspan="1" %)string 182 182 |(% colspan="1" rowspan="1" %)//Accredited//|(% colspan="1" rowspan="1" %)-not in use-|(% colspan="1" rowspan="1" %)bool ... ... @@ -183,7 +183,7 @@ 183 183 184 184 == Structure explanation Urgencies == 185 185 186 -This table contains a list with different delivery times for analyses results. For example ,5 work days, overnight, within 48 hours and so on. The “UrgencyId” is a code given by the lab.183 +This table contains a list with different delivery times for analyses results. For example 5 work days, overnight, within 48 hours and so on. The “UrgencyId” is a code given by the lab. 187 187 188 188 [[image:1712324236054-772.png||height="372" width="511"]] 189 189 ... ... @@ -194,7 +194,7 @@ 194 194 195 195 == Structure explanation StoragePeriods == 196 196 197 -This table contains a list with different storage periods for the storage of the delivered Samples and its containers. For example ,'1 month', '5 weeks', 'customer agreement' and so on. The “StoragePeriodId” is a code given by the lab.194 +This table contains a list with different storage periods for the storage of the delivered Samples and it's containers. For example '1 month', '5 weeks', 'customer agreement' and so on. The “StroragePeriodId” is a code given by the lab. 198 198 199 199 [[image:1712324393233-546.png||height="359" width="519"]] 200 200
- 1722464591905-118.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.RobinHuisman - Size
-
... ... @@ -1,1 +1,0 @@ 1 -165.1 KB - Content
- LabdeliveryFile_14.8.0_ENG_NL.xslt
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.RobinHuisman - Size
-
... ... @@ -1,1 +1,0 @@ 1 -9.0 KB - Content
-
... ... @@ -1,356 +1,0 @@ 1 -<?xml version="1.0" encoding="UTF-8"?> 2 -<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xpath-default-namespace="http://www.element-examples.org" xmlns="http://www.element-examples.org" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 3 - 4 -<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/> 5 - 6 - <!-- Kopier alle nodes --> 7 - <xsl:template match="node()"> 8 - <xsl:copy> 9 - <xsl:apply-templates select="@*|node()"/> 10 - </xsl:copy> 11 - </xsl:template> 12 - 13 - <!-- Kopier de text van de nodes en de attributen--> 14 - <xsl:template match="text()"> 15 - <xsl:value-of select="."/> 16 -</xsl:template> 17 - 18 - 19 -<!-- Vervang de attributen--> 20 -<xsl:template match="LabDelivery/@version"> 21 - <xsl:attribute namespace="{namespace-uri()}" name="versie" ><xsl:value-of select="."/></xsl:attribute> 22 - </xsl:template> 23 - 24 -<xsl:template match="LabDelivery/@versionDeliveryData"> 25 - <xsl:attribute namespace="{namespace-uri()}" name="kenmerk" ><xsl:value-of select="."/></xsl:attribute> 26 - </xsl:template> 27 - 28 -<xsl:template match="LabDelivery/@laboratory"> 29 - <xsl:attribute namespace="{namespace-uri()}" name="laboratorium" ><xsl:value-of select="."/></xsl:attribute> 30 - </xsl:template> 31 - 32 -<xsl:template match="LabDelivery/@language"> 33 - <xsl:attribute namespace="{namespace-uri()}" name="taal" ><xsl:value-of select="."/></xsl:attribute> 34 - </xsl:template> 35 - 36 - 37 - <!-- vervang LabDelivery --> 38 -<xsl:template match="LabDelivery"> 39 - <labaanlevering> 40 - <xsl:apply-templates select="@*|node()"/> 41 - </labaanlevering> 42 - </xsl:template> 43 - 44 -<xsl:template match="Links"> 45 - <koppeltabel> 46 - <xsl:apply-templates select="@*|node()"/> 47 - </koppeltabel> 48 - </xsl:template> 49 - 50 - <xsl:template match="AnalysisSets"> 51 - <analysepakketten> 52 - <xsl:apply-templates select="@*|node()"/> 53 - </analysepakketten> 54 - </xsl:template> 55 - 56 - <xsl:template match="Categories"> 57 - <categorieen> 58 - <xsl:apply-templates select="@*|node()"/> 59 - </categorieen> 60 - </xsl:template> 61 - 62 - <xsl:template match="AnalysisLinks"> 63 - <analysetabel> 64 - <xsl:apply-templates select="@*|node()"/> 65 - </analysetabel> 66 - </xsl:template> 67 - 68 - <xsl:template match="Clients"> 69 - <debiteurtabel> 70 - <xsl:apply-templates select="@*|node()"/> 71 - </debiteurtabel> 72 - </xsl:template> 73 - 74 - <xsl:template match="LabSampleMatrices"> 75 - <labmonstersoorttabel> 76 - <xsl:apply-templates select="@*|node()"/> 77 - </labmonstersoorttabel> 78 - </xsl:template> 79 - 80 - <xsl:template match="SpecialAppointments"> 81 - <afspraaktabel> 82 - <xsl:apply-templates select="@*|node()"/> 83 - </afspraaktabel> 84 - </xsl:template> 85 - 86 - <xsl:template match="Urgencies"> 87 - <urgentietabel> 88 - <xsl:apply-templates select="@*|node()"/> 89 - </urgentietabel> 90 - </xsl:template> 91 - 92 - <xsl:template match="StorePeriods"> 93 - <bewaarduurtabel> 94 - <xsl:apply-templates select="@*|node()"/> 95 - </bewaarduurtabel> 96 - </xsl:template> 97 - 98 - <xsl:template match="Reports"> 99 - <rapportagetabel> 100 - <xsl:apply-templates select="@*|node()"/> 101 - </rapportagetabel> 102 - </xsl:template> 103 - 104 - <xsl:template match="FractionLinks"> 105 - <fractietabel> 106 - <xsl:apply-templates select="@*|node()"/> 107 - </fractietabel> 108 - </xsl:template> 109 - 110 - <xsl:template match="Link"> 111 - <koppeling> 112 - <xsl:apply-templates select="@*|node()"/> 113 - </koppeling> 114 - </xsl:template> 115 - 116 - <xsl:template match="AnalysisSetId"> 117 - <analysepakketcode> 118 - <xsl:apply-templates select="@*|node()"/> 119 - </analysepakketcode> 120 - </xsl:template> 121 - 122 - <xsl:template match="ClientId"> 123 - <klantcode> 124 - <xsl:apply-templates select="@*|node()"/> 125 - </klantcode> 126 - </xsl:template> 127 - 128 - <xsl:template match="LabSampleMatrix"> 129 - <labmonstersoort> 130 - <xsl:apply-templates select="@*|node()"/> 131 - </labmonstersoort> 132 - </xsl:template> 133 - 134 - <xsl:template match="CompartimentId"> 135 - <compartimentid> 136 - <xsl:apply-templates select="@*|node()"/> 137 - </compartimentid> 138 - </xsl:template> 139 - <xsl:template match="CompartimentCode"> 140 - <compartimentcode> 141 - <xsl:apply-templates select="@*|node()"/> 142 - </compartimentcode> 143 - </xsl:template> 144 - <xsl:template match="LabSampleMatrixCode"> 145 - <labmonstersoortcode> 146 - <xsl:apply-templates select="@*|node()"/> 147 - </labmonstersoortcode> 148 - </xsl:template> 149 - <!--Omschrijving wordt al gedaan --> 150 - 151 - <xsl:template match="AppointmentTypeCode"> 152 - <afspraakCode> 153 - <xsl:apply-templates select="@*|node()"/> 154 - </afspraakCode> 155 - </xsl:template> 156 - 157 - <xsl:template match="SpecialAppointmentId"> 158 - <afspraaknummer> 159 - <xsl:apply-templates select="@*|node()"/> 160 - </afspraaknummer> 161 - </xsl:template> 162 - 163 - <xsl:template match="SampleKind"> 164 - <monstersoort> 165 - <xsl:apply-templates select="@*|node()"/> 166 - </monstersoort> 167 - </xsl:template> 168 - 169 - <xsl:template match="Price"> 170 - <prijs> 171 - <xsl:apply-templates select="@*|node()"/> 172 - </prijs> 173 - </xsl:template> 174 - 175 - <xsl:template match="CertificationId"> 176 - <certificering> 177 - <xsl:apply-templates select="@*|node()"/> 178 - </certificering> 179 - </xsl:template> 180 - 181 - <xsl:template match="AnalysisSet"> 182 - <analysepakket> 183 - <xsl:apply-templates select="@*|node()"/> 184 - </analysepakket> 185 - </xsl:template> 186 - 187 - <!-- AnalysisSetId Deze kunnen we overslaan, wordt al gedaan als goed is --> 188 - 189 - <xsl:template match="Description"> 190 - <omschrijving> 191 - <xsl:apply-templates select="@*|node()"/> 192 - </omschrijving> 193 - </xsl:template> 194 - 195 - <xsl:template match="CategoryId"> 196 - <categoriecode> 197 - <xsl:apply-templates select="@*|node()"/> 198 - </categoriecode> 199 - </xsl:template> 200 - 201 - <xsl:template match="Sequence"> 202 - <volgorde> 203 - <xsl:apply-templates select="@*|node()"/> 204 - </volgorde> 205 - </xsl:template> 206 - 207 - <xsl:template match="MinimalDeliveryTime"> 208 - <minlevertermijn> 209 - <xsl:apply-templates select="@*|node()"/> 210 - </minlevertermijn> 211 - </xsl:template> 212 - 213 - <xsl:template match="Category"> 214 - <categorie> 215 - <xsl:apply-templates select="@*|node()"/> 216 - </categorie> 217 - </xsl:template> 218 - 219 -<!-- CategoryId kunnen we overslaan, is al gedaan--> 220 - 221 -<!-- Description kunnen we overslaan, is al gedaan--> 222 - 223 -<!-- Sequence kunnen we overslaan, is al gedaan--> 224 - 225 - <xsl:template match="AnalysisLink"> 226 - <pakket> 227 - <xsl:apply-templates select="@*|node()"/> 228 - </pakket> 229 - </xsl:template> 230 - 231 - <!-- AnalysisSetId kunnen we overslaan, is al gedaan --> 232 - 233 - <xsl:template match="Analysis"> 234 - <analyse> 235 - <xsl:apply-templates select="@*|node()"/> 236 - </analyse> 237 - </xsl:template> 238 - 239 - <xsl:template match="AnalysisId"> 240 - <analysecode> 241 - <xsl:apply-templates select="@*|node()"/> 242 - </analysecode> 243 - </xsl:template> 244 - 245 -<!--Desciption kunnen we overslaan, wordt al gedaan --> 246 - 247 -<!--MinimalDeliveryTime kunnen we overslaan, wordt al gedaan --> 248 - 249 - <xsl:template match="Client"> 250 - <debiteur> 251 - <xsl:apply-templates select="@*|node()"/> 252 - </debiteur> 253 - </xsl:template> 254 - 255 - <!--ClientId kunnen we overslaan --> 256 - 257 - <!-- Description kunnen we overslaan --> 258 - 259 - <xsl:template match="SpecialAppointment"> 260 - <afspraak> 261 - <xsl:apply-templates select="@*|node()"/> 262 - </afspraak> 263 - </xsl:template> 264 - 265 - <!-- SpecialAppointmentId kunnen we overslaan --> 266 - 267 - <!-- Description kunnen we overslaan --> 268 - 269 - <xsl:template match="startdate"> 270 - <begindatum> 271 - <xsl:apply-templates select="@*|node()"/> 272 - </begindatum> 273 - </xsl:template> 274 - 275 - <xsl:template match="finaldate"> 276 - <einddatum> 277 - <xsl:apply-templates select="@*|node()"/> 278 - </einddatum> 279 - </xsl:template> 280 - 281 - <xsl:template match="Startdate"> 282 - <begindatum> 283 - <xsl:apply-templates select="@*|node()"/> 284 - </begindatum> 285 - </xsl:template> 286 - 287 - <xsl:template match="Finaldate"> 288 - <einddatum> 289 - <xsl:apply-templates select="@*|node()"/> 290 - </einddatum> 291 - </xsl:template> 292 - 293 - <xsl:template match="Urgency"> 294 - <urgentie> 295 - <xsl:apply-templates select="@*|node()"/> 296 - </urgentie> 297 - </xsl:template> 298 - 299 - <xsl:template match="UrgencyId"> 300 - <urgentiecode> 301 - <xsl:apply-templates select="@*|node()"/> 302 - </urgentiecode> 303 - </xsl:template> 304 - 305 - <!-- Description wordt al gedaan--> 306 - 307 - <xsl:template match="StorePeriod"> 308 - <bewaarduur> 309 - <xsl:apply-templates select="@*|node()"/> 310 - </bewaarduur> 311 - </xsl:template> 312 - 313 - <!--StorePeriodId kunnen we overslaan --> 314 - 315 - <!--Description kunnen we overslaan --> 316 - 317 - <xsl:template match="Report"> 318 - <rapportage> 319 - <xsl:apply-templates select="@*|node()"/> 320 - </rapportage> 321 - </xsl:template> 322 - 323 - <xsl:template match="ReportId"> 324 - <rapportcode> 325 - <xsl:apply-templates select="@*|node()"/> 326 - </rapportcode> 327 - </xsl:template> 328 - 329 -<!--Description kunnen we overslaan --> 330 - 331 - <xsl:template match="FractionLink"> 332 - <fracties> 333 - <xsl:apply-templates select="@*|node()"/> 334 - </fracties> 335 - </xsl:template> 336 - 337 - <!--AnalysisSetId kunnen we overslaan --> 338 - 339 - <xsl:template match="Fraction"> 340 - <fractie> 341 - <xsl:apply-templates select="@*|node()"/> 342 - </fractie> 343 - </xsl:template> 344 - 345 - <xsl:template match="FractionId"> 346 - <fractiecode> 347 - <xsl:apply-templates select="@*|node()"/> 348 - </fractiecode> 349 - </xsl:template> 350 - 351 - <!-- SampleKind is al vertaald --> 352 - 353 - <!--Description is al vertaald --> 354 - 355 -</xsl:stylesheet> 356 -