Versie van 29 okt 2025 om 16:32

This IG is currently under development and can not be considered stable and ready for use.

For an overview of all current documentation see information standard lab exchange main page

1 Introduction

This is the technical design (TO) for the information standard (IS) Lab2patient. This TO must be used together with the IS functional design, see functional design Lab2patient 1.0.0-beta.1. The data exchange format used in this version is: FHIR R4.

1.1 Support

For questions, feedback, or change requests, please contact our support team at Nictiz Servicemanagement.

1.2 Boundaries

This information standard may overlap with other standards related to identification, roles, and geographic classifications, requiring careful alignment to ensure consistency and avoid duplication. For more information, see functional design Lab2patient 1.0.0-beta.1.

1.3 Prerequisite knowledge

The following background information is required for understanding this TO:

The functional design Lab2patient 1.0.0-beta.1 accompanying this TO.
The data exchange format FHIR R4, which you can find here:

2 Relationships

Example: Geboortezorg Relationships chapter

3 Components

HL7 FHIR is used to accommodate the Dutch Clinical Information Models (zibs) used in the IS.

3.1 HL7 FHIR R4

Nictiz uses the FHIR Packaging mechanism. This conveniently bundles all profiles, terminology, example material and other conformance resources you need into a single archive, which can be downloaded or installed using the appropriate FHIR tooling. This version of the information standard uses the following packages:

nictiz.fhir.nl.r4.labexchange version 3.0.0-beta.4 or compatible
nictiz.fhir.nl.r4.nl-core version 0.12.0-beta.1 or compatible
nictiz.fhir.nl.r4.zib2020 version 0.12.0-beta.1 or compatible

Note: packages use Semantic Versioning. Other versions can be used at will as long as they have the same major.minor number or a minor number higher than the stated version.

3.1.1 Artifacts

The artifacts of the information standard are presented in the following table:

zib	FHIR resource	FHIR profile
HealthcareProvider	Organization	nl-core-HealthcareProvider-Organization
HealthProfessional	Practitioner	nl-core-HealthProfessional-Practitioner
HealthProfessional	PractitionerRole	nl-core-HealthProfessional-PractitionerRole
LaboratoryTestResult	Device	nl-core-LaboratoryTestResult.Specimen.Source
	Observation	nl-core-LaboratoryTestResult
	Specimen	nl-core-LaboratoryTestResult.Specimen
Patient	Patient	nl-core-Patient
	DiagnosticReport	lu-LaboratoryTestResult-DiagnosticReport
	ServiceRequest	lu-OrderData

3.1.2 Examples of FHIR instances

You can find examples of FHIR-instances (filled-in FHIR profiles) in the Nictiz GitHub repository: Lab exchange Testscripts repository.

4 Transactions

4.1 <Use case 1>

4.1.1 Involved actors

*Abbreviations: SRC = system role code, FCSN = FHIR CapabilityStatement Name.*
Transaction group	Transaction	Actor	System role code	FHIR CapabilityStatement
<Transaction group name>	<Transaction 1>	<Actor 1>	<SRC 1>	<FCSN link 1>
<Transaction group name>	<Transaction 2>	<Actor 2>	<SRC 2>	<FCSN link 2>

4.1.2 Search parameters

*Use this caption for extra notes, abbreviations, etc.*
FHIR Search Parameter	Description	FHIR Resource	Example
<Functional building block 1>
<FHIR Search Parameter 1>	<Description of FHIR Search Parameter 1>	<FHIR Resource 1>	<HTTP Method> [base]/<FHIR resource>?_include=<FHIR resource>:<Search parameters>
<Functional building block 2>
<FHIR Search Parameter 2>	<Description of FHIR Search Parameter 2>	<FHIR Resource 2>	<HTTP Method> [base]/<FHIR resource>?_include=<FHIR resource>:<Search parameters>
<Functional building block 3>
<FHIR Search Parameter 3>	<Description of FHIR Search Parameter 3>	<FHIR Resource 3>	<HTTP Method> [base]/<FHIR resource>?_include=<FHIR resource>:<Search parameters>

5 Actors involved

Actors		Systems		FHIR CapabilityStatements
Name	Description	Name	Description	Name	Description
Patient	The user of a personal healthcare environment.	PHR	Personal health record	CapabilityStatement: Lab2Healthcare-Results-RetrieveServe	Retrieve [LAB-LRR-PGO]/serve [LAB-LRB-PGO] lab results requirements.
Lab Professional	The user of a LIS	LIS	Laboratory information system	CapabilityStatement: Lab2Healthcare-Results-RetrieveServe

6 Use cases

6.1 Patient retrieves laboratory results in their PGO

6.1.1 Introduction

This FHIR Implementation Guide assumes that the PHR system is able to make a connection to the right LIS that contains the patient's information. It does not provide information on finding the right LIS nor does it provide information about security. Moreover, each transaction is performed in the context of a specific authenticated patient, for whose context (token) has been established using the authentication mechanisms described in the 'Afsprakenstelsel'. Each XIS Gateway is required to perform filtering based on the patient associated with the context for the request, so only the records associated with the authenticated patient are returned. For this reason, search parameters should not be included for patient identification.

6.1.2 Actors

Transaction group	Transaction	Actor	Role
Retrieve laboratory results (PULL)	Retrieve laboratory results request	LaboratoriumresultaatResultaatRaadplegend Systeem [LAB-LRR-PGO]	Send a query to the LAB-LRB-PGO to retrieve lab results
Retrieve laboratory results (PULL)	Retrieve laboratory results response	LaboratoriumresultaatResultaatBeschikbaarstellend Systeem [LAB-LRB-PGO]	Respond to a query from the LAB-LRR-PGO to retrieve lab results

6.1.3 Invocations

6.1.3.1 LAB-LRR-PGO: request message

The request message represents an HTTP GET parameterized query from the PHR (LAB-LRR-PGO) to the LIS (LAB-LRB-PGO).

6.1.3.1.1 Trigger events

When the PHR wants to obtain laboratory results, it issues a retrieve laboratory results request message.

6.1.3.1.2 Message semantics

The PHR (LAB-LRR-PGO) executes an HTTP GET conforming to the FHIR RESTful and search specification against the LIS's Observation endpoint. Laboratory results are all under the .category observation, using query parameter category as token.

Basic query syntax

GET [base]/Observation?category=http://terminology.hl7.org/CodeSystem/observation-category|laboratory

Examples

Parameter values have not been uri escaped in these examples for readability. This is likely necessary in practice.

Get all lab results of type 14683-7 (LOINC)
GET [base]/Observation?category=http://terminology.hl7.org/CodeSystem/observation-category\|laboratory&code=http://loinc.org\|14683-7

Get all lab results of type 14683-7 (LOINC) since March 12, 2022
GET [base]/Observation?category=http://terminology.hl7.org/CodeSystem/observation-category\|laboratory&code=http://loinc.org\|14683-7&date=gt2022-03-12

Get all lab results of type 14683-7 (LOINC) since March 12, 2022 but before June 7, 2022
GET [base]/Observation?category=http://terminology.hl7.org/CodeSystem/observation-category\|laboratory&code=http://loinc.org\|14683-7&date=gt2022-03-12&date=lt2022-06-07

Get all lab results of type 14683-7 (LOINC) and/or 3583 (NHG)

GET [base]/Observation?category=http://terminology.hl7.org/CodeSystem/observation-category|laboratory&code=http://loinc.org|14683-7,https://referentiemodel.nhg.org/tabellen/nhg-tabel-45-diagnostische-bepalingen|3583

Get latest lab result of type 14683-7 (LOINC)
GET [base]/Observation/$lastn?category=http://terminology.hl7.org/CodeSystem/observation-category\|laboratory&code=http://loinc.org\|14683-7

Get latest 5 lab results of type 14683-7 (LOINC)
GET [base]/Observation/$lastn?max=5&category=http://terminology.hl7.org/CodeSystem/observation-category\|laboratory&code=http://loinc.org\|14683-7

Get latest lab result of any type
GET [base]/Observation/$lastn?category=http://terminology.hl7.org/CodeSystem/observation-category\|laboratory

6.1.3.1.2.1 Expected actions

The LIS (LAB-LRB-PGO) SHALL process the query to retrieve laboratory results.

6.1.3.2 LAB-LRB-PGO: response message

The LIS (LAB-LRB-PGO) returns an HTTP Status code appropriate to the processing as well as a FHIR Bundle including the matching information. Refer to the generic FHIR IG for more information on handling errors and status codes. Not finding a match based on stated parameters does not constitute an error.

6.1.3.2.1 Trigger events

The LIS (LAB-LRB-PGO) completed the processing of the retrieve laboratory results request message.

6.1.3.2.2 Message semantics

The LIS (LAB-LRB-PGO) SHALL process the request and, unless an error is found, respond with a Bundle resource of type searchset. Each Observation matching the request SHALL be marked with .entry.search.mode=match. Each otherwise included resource SHALL be marked with .entry.search.mode=include. If the searchset bundle contains less matching resources than the actual total set, then:

the Bundle.link that holds the self link, SHOULD include the _count parameter to inform the client of what max was applied
an OperationOutcome SHOULD be included marked with .entry.search.mode=outcome.

The resources in the response Bundle SHALL be a valid instance of their stated profile. All resources SHALL include their related profile canonical URL in the .meta.profile element in order to show compliance. The exception is the OperationOutcome resource for which there is no profile in this specification.

Example searchset Bundle

XML contents for searchset Bundle

<Bundle xmlns="http://hl7.org/fhir">
    <id value="1"/>
    <type value="searchset"/>
    <total value="3"/>
    <link>
        <relation value="self"/>
        <url value="http://example.org/fhir?category=http://terminology.hl7.org/CodeSystem/observation-category|laboratory&amp;patient:identifier=http://fhir.nl/fhir/NamingSystem/bsn|111222333&amp;code=http://loinc.org|14683-7"/>
    </link>
    <entry>
        <fullUrl value="https://example.org/fhir/Observation/1"/>
        <resource>
            <Observation>
                <!--  -->
            </Observation>
        </resource>
        <search>
            <mode value="match"/>
        </search>
    </entry>
    <entry>
        <fullUrl value="https://example.org/fhir/Observation/2"/>
        <resource>
            <Observation>
                <!--  -->
            </Observation>
        </resource>
        <search>
            <mode value="match"/>
        </search>
    </entry>
    <entry>
        <fullUrl value="https://example.org/fhir/Observation/3"/>
        <resource>
            <resource>
                <Observation>
                    <!--  -->
                </Observation>
            </resource>
        </resource>
        <search>
            <mode value="match"/>
        </search>
    </entry>
    <entry>
        <fullUrl value="https://example.org/fhir/Specimen/1"/>
        <resource>
            <Specimen>
                <!--  -->
            </Specimen>
        </resource>
        <search>
            <mode value="include"/>
        </search>
    </entry>
    <entry>
        <fullUrl value="https://example.org/fhir/Patient/1"/>
        <resource>
            <Patient>
                <!--  -->
            </Patient>
        </resource>
        <search>
            <mode value="include"/>
        </search>
    </entry>
    <entry>
        <fullUrl value="https://example.org/fhir/Organization/1"/>
        <resource>
            <Organization>
                <!--  -->
            </Organization>
        </resource>
        <search>
            <mode value="include"/>
        </search>
    </entry>
</Bundle>

Example OperationOutcome

XML contents for OperationOutcome

<OperationOutcome xmlns="http://hl7.org/fhir">
    <id value="size-exceeded-1"/>
    <issue>
        <severity value="warning"/>
        <code value="too-costly"/>
        <details>
            <text value="Resultaat was 3000, wat meer is dan het maximum van 1000"/>
        </details>
    </issue>
</OperationOutcome>

6.1.3.2.3 LAB-LRB-PGO: Expected actions

The LIS (LAB-LRB-PGO) SHALL process the response Bundle in accordance with the intentions of the trigger event that caused the retrieve. Actions may include discrete rendering on screen or in context with other information, triggering alerts on trends, ordering of (other) tests and more.

@@ Regel 1: / Regel 1: @@
 {{Vdraft/InformationBox|This IG is currently under development and can not be considered stable and ready for use.}}
-{{DISPLAYTITLE:FHIR Implementation Guide Lab2patient V1.0.0 - beta}}
+{{DISPLAYTITLE:Technical Design Lab2patient V1.0.0-beta.1}}
 <!--{{underconstruction}}-->
@@ Regel 10: / Regel 10: @@
 desc none
 </imagemap>
+<big>For an overview of all current documentation [[Lab:V3.0.0_Ontwerp_Laboverdacht| see information standard lab exchange main page]]</big>
 __NUMBEREDHEADINGS__
-=Introduction=
+==Introduction==
 [[Bestand:Functioneel-02.png|link=Lab:V1.0_Ontwerp_Lab2Patient|100px|rechts|Functional design|Go to functional design]]
-This page describes the technical design of Lab2patient (L2P) as a subset of the '''[[Lab:V3.0.0 Ontwerp Laboverdacht|Information standard lab exchange]]''' (Dutch: Labuitwisseling or abbreviated to LU). This technical specification is implementer centric and complements the '''[[Lab:V1.0_Ontwerp_Lab2Patient|functional design]]'''. This page uses various terms as defined in the [[Lab:V3.0.0 Ontwerp Laboverdacht#Begrippenlijst|glossary]].
+This is the technical design (TO) for the information standard (IS) Lab2patient. This TO must be used together with the IS functional design, see [[Lab:V1.0_Ontwerp_Lab2Patient| functional design Lab2patient 1.0.0-beta.1]]. The data exchange format used in this version is: FHIR R4.
+=== Support ===
+For questions, feedback, or change requests, please contact our support team at [https://nictiz.atlassian.net/servicedesk/customer/portal/4 Nictiz Servicemanagement].
-==Disclaimers==
+=== Boundaries ===
-This page implements general principles applicable to FHIR as outlined by a central [[FHIR:V1.0_FHIR_IG_R4|FHIR IG for R4]]. Please make sure you familiarize yourself with both the functional design and the FHIR IG for full appreciation of the context of this page.
+This information standard may overlap with other standards related to identification, roles, and geographic classifications, requiring careful alignment to ensure consistency and avoid duplication. For more information, see [[Lab:V1.0_Ontwerp_Lab2Patient| functional design Lab2patient 1.0.0-beta.1]].
-This FHIR Implementation Guide assumes that systems (XIS) are able to make a connection to the right systems. It does not provide information on finding the right XIS nor does it provide information about security including authentication and authorization. Finding the right system, and security aspects of the connection, are dealt with by the infrastructure. Any relevant infrastructure is expected to have a framework in place to deal with this. The only assumption/requirement for an infrastructure is that this allows RESTful FHIR-based exchange as specified here.
+=== Prerequisite knowledge ===
+The following background information is required for understanding this TO:
+* The [[Lab:V1.0_Ontwerp_Lab2Patient| functional design Lab2patient 1.0.0-beta.1]] accompanying this TO.
+* The data exchange format FHIR R4, which you can find here:
+** [[FHIR:V1.0 FHIR IG R4|general FHIR R4 Implementation Guide]],
+** [[FHIR:V1.0_FHIR_IG_R4#FHIR_Packages|FHIR packages]],
+** [[FHIR:V1.0_FHIR_IG_R4#Usage_of_the_.id.2C_.identifier_and_.fullUrl_elements_in_FHIR_instances|usage of the .id, .identifier and .fullUrl]].
-=Boundaries and relationships=
+== Relationships ==
-==Overview of relationships between FHIR resources==
-[[Bestand:LaboratoryInFHIRR4Overview.png||Laboratory results in FHIR R4 overview]]
-==Mappings between profiles and data set==
-Each transaction starts with links to the [https://decor.nictiz.nl/ad/#/lu-/scenarios/scenarios/2.16.840.1.113883.2.4.3.11.60.25.3.5/2024-09-16T00:00:00 functional definition in an ART-DECOR publication] and references one or several FHIR profiles. Where the functional definition contains all specific data elements for the transaction (prefixed with ‘lu-concept-v2’), the FHIR profiles only contain a mapping to these data elements that do not have a dependency on a zib counterpart. For example: ‘lu-concept-v2-4266’ (Specimen) has a relation with the zib element with id ‘NL-CM-13.1.2’, therefore no mapping with ‘lu-concept-v2-4266’ can be found in the profiles. On the other hand, ‘lu-concept-v2-4296’ (LaboratoryResultIdentification) has no relation with a zib element, therefore a mapping can be found in the relevant FHIR profile.
-Cardinalities in FHIR profiles may be less strict than the ART-DECOR definitions. In this IG, transaction-level cardinalities take precedence. For example: in the nl-core-LaboratoryTestResult profile, {{fhir|.performer}} has a core cardinality of 0..*, while in both the 'Send laboratory results' and ‘Serve laboratory results’ ART-DECOR transactions, the Performer element has a cardinality of 1..1 M. Therefore, {{fhir|.performer}} is expected to be filled with a reference to an nl-core-HealthcareProvider-Organization resource.
+<div style="background-color:aliceblue;padding:5px;">
+'''Example:''' [https://informatiestandaarden.nictiz.nl/wiki/Gebz:V1.3_FHIR_IG#A_high_level_overview Geboortezorg Relationships chapter]
+</div>
-Each transaction contains a Patient building block with cardinality 1..1 M. This patient is the subject of all other building blocks in the transaction, although no explicit relation exists in the data set. Therefore, a reference to a Patient resource conforming to the nl-core-Patient profile is expected in {{fhir|.subject}} of each FHIR instance of each building block.
+==Components==
-The single zib LaboratoryTestResult consists of objects that in FHIR are represented using different (instances of) resources:
+HL7 FHIR is used to accommodate the Dutch Clinical Information Models (zibs) used in the IS.
-* ''NL-CM:13.1.1 LaboratoryTestResult'' maps into profile {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-LaboratoryTestResult|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.6.0-beta.2|title=nl-core-LaboratoryTestResult}} {{fhir|Observation}} and has {{fhir|.hasMember}} relationships with individual ''NL-CM:13.1.3 LaboratoryTests''.
-** Note that this level only exists when LaboratoryTestResult contains ''NL-CM:13.1.4 PanelOrBattery''. The concepts ''NL-CM:13.1.7 ResultType'', ''NL-CM:13.1.5 Comment'', and ''NL-CM:13.1.6 ResultStatus'' are not mapped in the absence of ''NL-CM:13.1.4 PanelOrBattery''.
-* ''NL-CM:13.1.3 LaboratoryTest'' also maps into profile {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-LaboratoryTestResult|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.6.0-beta.2|title=nl-core-LaboratoryTestResult}} {{fhir|Observation}} and MAY be referenced by a different {{fhir|Observation.hasMember}} containing ''NL-CM:13.1.1 LaboratoryTestResult''.
-* ''NL-CM:13.1.2 Specimen'' maps into profile {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-LaboratoryTestResult.Specimen|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.6.0-beta.2|title=nl-core-LaboratoryTestResult.Specimen}} {{fhir|Specimen}}.
-** Note that there could be multiple instances of Specimen: one for the main ''NL-CM:13.1.16 SpecimenMaterial'', and one per isolated ''NL-CM:13.1.22 Microorganism'' with a {{fhir|.parent}} relationship to the main specimen.
-* ''NL-CM:13.1.29 SpecimenSource'' maps into profile {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-LaboratoryTestResult.Specimen.Source|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.6.0-beta.2|title=nl-core-LaboratoryTestResult.Specimen.Source}} {{fhir|Device}}. This is a special case where the specimen did not come from the Patient directly.
-==FHIR relationship structures==
+=== HL7 FHIR R4 ===
-Many laboratory results have important relationships to other observations and need to be grouped together. [http://hl7.org/fhir/r4/observation.html#10.1.4.1 The FHIR specification] defines several structures to do this:
+{{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.labexchange|v1=3.0.0-beta.4|p2=nictiz.fhir.nl.r4.nl-core|v2=0.12.0-beta.1|p3=nictiz.fhir.nl.r4.zib2020|v3=0.12.0-beta.1}}
-* {{fhir|Observation.hasMember}}
+==== Artifacts ====
-** Each {{fhir|.hasMember}} element references another Observation and the Observation with {{fhir|.hasMember}} elements thus serves as grouper for all Observations it references. Each Observation can be accessed individually. This is useful for panels and/or batteries of tests.
-** Note that while FHIR Observation also allows references to resource types MolecularSequence and QuestionnaireResponse, there is no identified use case for that at the time of writing.
-** An Observation without {{fhir|.hasMember}} elements is expected to be an individual result and has a value when one can be/is determined.
-* {{fhir|Observation.derivedFrom}}
-** Each {{fhir|.derivedFrom}} element references another Observation references related measurements the observation is made from.
-** Note that while FHIR Observation also allows references to resource types DocumentReference, ImagingStudy, Media, QuestionnaireResponse and MolecularSequence, there is no identified use case for those at the time of writing.
-* {{fhir|Observation.component}}
-** {{fhir|.component}} elements of an Observation are not accessible individually. Whenever you access the Observation, you also access all its components. This is mostly useful when certain context is provided around the result. For lab observations this is expected to be less common. An example outside of the lab realm could be BloodPressure where systolic, diastolic, and cuff size are all in one Observation with 3 components.
-==Resource identification==
+The artifacts of the information standard are presented in the following table:
-ART-DECOR transactions define a stricter cardinality of 1..1 R for resource identifiers. Therefore:
+{| style="text-align: left; background-color: white;" cellpadding=5px;
-* A stable identifier SHOULD be provided for each resource.
-* If no identifier value is available, [[FHIR:V0.9_FHIR_IG_R4#Missing_information|the DataAbsentReason extension]] SHOULD be used.
-* Identifiers SHALL contain both a {{fhir|.system}} and a {{fhir|.value}}.
-For compatibility with HL7v3 (CDA), where identifiers can only be represented as [[Hoofdpagina#Object_IDentifiers_.28OIDs.29|OIDs]]:
+|- style="color: white; background-color: #e7844b;"
-* The {{fhir|.system}} SHALL be an OID to ensure compatibility in transformations to and from FHIR.
+! zib
-* The {{fhir|.system}} SHALL have a maximum of 128 characters.
+! FHIR resource
-* The {{fhir|.value}} SHALL have a maximum of 64 characters.
+! FHIR profile
-Regarding reference handling:
+|- style="background-color: #fcf0e9;"
-* Systems that encounter or resolve references, either logical or literal, in resources they receive, SHALL NOT rewrite these references to a copy of these resources (with {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/ext-CopyIndicator|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.6.0-beta.2}} present) they may store.
+| HealthcareProvider
-* This means that [https://hl7.org/fhir/r4/references.html relative literal references] MAY need to be rewritten to absolute ones.
+| Organization
-* The same applies to [[FHIR:V1.0_FHIR_IG_R4#Including_.22secondary.22_resources_when_sending_information|included secondary resources in transactions]].
+| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.12.0-beta.1|title=nl-core-HealthcareProvider-Organization}}
-==FHIR Profile Package==
+|- style="background-color: #fcf0e9;"
-<!-- If you change this section title, also change the links to it on the pages ... -->
+| rowspan="2" | HealthProfessional
-All use cases in this specification depend on the same set of FHIR profiles. FHIR profile package for Lab2Patient is currently in development. The table below lists profiles used within the framework of Lab2Zorg (Lab2Healthcare) that represent applicable zibs for laboratory result information exchange.
+| Practitioner
+| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-Practitioner|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.12.0-beta.1|title=nl-core-HealthProfessional-Practitioner}}
-{{NoteBoxNictizR4Package|p1=nictiz.fhir.nl.r4.labexchange|v1=3.0.0-beta.2|p2=nictiz.fhir.nl.r4.nl-core|v2=0.8.0-beta.1|p3=nictiz.fhir.nl.r4.zib2020|v3=0.6.0-beta.2}}
+|- style="background-color: #fcf0e9;"
+| PractitionerRole
+| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-HealthProfessional-PractitionerRole|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.12.0-beta.1|title=nl-core-HealthProfessional-PractitionerRole}}
-{| class="wikitable"
+|- style="background-color: #fcf0e9;"
-! style="text-align:left;" | FHIR Profile
+| rowspan="3" | LaboratoryTestResult
-! style="text-align:left;" | FHIR Resource
+| Device
-! style="text-align:left;" | Based on zib
+| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-LaboratoryTestResult.Specimen.Source|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.7.0-beta.1|title=nl-core-LaboratoryTestResult.Specimen.Source}}
-|-
-| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-LaboratoryTestResult|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.6.0-beta.2|title=nl-core-LaboratoryTestResult}}
+|- style="background-color: #fcf0e9;"
 | Observation
-| rowspan="3" | [https://zibs.nl/wiki/LaboratoryTestResult-v4.6(2020EN) LaboratoryTestResult]
+| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-LaboratoryTestResult|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.12.0-beta.1|title=nl-core-LaboratoryTestResult}}
-|-
-| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-LaboratoryTestResult.Specimen|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.6.0-beta.2|title=nl-core-LaboratoryTestResult.Specimen}}
+|- style="background-color: #fcf0e9;"
 | Specimen
-|-
+| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-LaboratoryTestResult.Specimen|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.12.0-beta.1|title=nl-core-LaboratoryTestResult.Specimen}}
-| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-LaboratoryTestResult.Specimen.Source|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.6.0-beta.2|title=nl-core-LaboratoryTestResult.Specimen.Source}}
-| Device
+|- style="background-color: #fcf0e9;"
-|-
+| Patient
-| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-patient|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.6.0-beta.2|title=nl-core-Patient}}
 | Patient
-| [https://zibs.nl/wiki/Patient-v3.2(2020EN) Patient]
+| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/nl-core-Patient|nictiz.fhir.nl.r4.nl-core|pkgVersion=0.12.0-beta.1|title=nl-core-Patient}}
-|-
-| {{Simplifier|http://fhir.nl/fhir/StructureDefinition/nl-core-HealthcareProvider-Organization|nictiz.fhir.nl.r4.nl-core|title=nl-core-HealthcareProvider-Organization}}
+|- style="background-color: #fcf0e9;"
-| Organization
+|
-| [https://zibs.nl/wiki/HealthcareProvider-v3.4(2020EN) HealthcareProvider]
+| DiagnosticReport
+| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/lu-LaboratoryTestResult-DiagnosticReport|nictiz.fhir.nl.r4.labexchange|pkgVersion=3.0.0-beta.4|title=lu-LaboratoryTestResult-DiagnosticReport}}
+|- style="background-color: #fcf0e9;"
+|
+| ServiceRequest
+| {{Simplifier|http://nictiz.nl/fhir/StructureDefinition/lu-OrderData|nictiz.fhir.nl.r4.labexchange|pkgVersion=3.0.0-beta.4|title=lu-OrderData}}
+|}
+==== Examples of FHIR instances ====
+You can find examples of FHIR-instances (filled-in FHIR profiles) in the Nictiz GitHub repository: [https://github.com/Nictiz/Nictiz-testscripts/blob/main/src/LaboratoryResults-3-0 <nowiki>Lab exchange Testscripts repository</nowiki>].
+== Transactions ==
+=== <Use case 1> ===
+==== Involved actors ====
+{| style="text-align: left;" cellpadding=5px;
+|- style="color: white; background-color: #e7844b;"
+! Transaction group || Transaction || Actor || System role code || FHIR CapabilityStatement
+|- style="background-color: #fcf0e9;"
+| rowspan="2" | <Transaction group name>
+| <Transaction 1> || <Actor 1> || <SRC 1> || <FCSN link 1>
+|- style="background-color: #fcf0e9;"
+| <Transaction 2> || <Actor 2> || <SRC 2> || <FCSN link 2>
+|+ style="align: bottom; caption-side: bottom; text-align: left;" | ''Abbreviations: SRC = system role code, FCSN = FHIR CapabilityStatement Name.''
+|}
+==== Search parameters ====
+{| style="text-align: left;" cellpadding=5px;
+|- style="color: white; background-color: #e7844b;"
+! FHIR Search Parameter || Description || FHIR Resource || Example
+|- style="color: white; background-color: #eda778;"
+! colspan="4"  | <Functional building block 1>
+|- style="background-color: #fcf0e9;"
+| <FHIR Search Parameter 1> || <Description of FHIR Search Parameter 1> || <FHIR Resource 1> || <pre> <HTTP Method> [base]/<FHIR resource>?_include=<FHIR resource>:<Search parameters> </pre>
+|- style="color: white; background-color: #eda778;"
+! colspan="4" | <Functional building block 2>
+|- style="background-color: #fcf0e9;"
+| <FHIR Search Parameter 2> || <Description of FHIR Search Parameter 2> || <FHIR Resource 2> || <pre> <HTTP Method> [base]/<FHIR resource>?_include=<FHIR resource>:<Search parameters> </pre>
+|- style="color: white; background-color: #eda778;"
+! colspan="4" | <Functional building block 3>
+|- style="background-color: #fcf0e9;"
+| <FHIR Search Parameter 3> || <Description of FHIR Search Parameter 3> || <FHIR Resource 3> || <pre> <HTTP Method> [base]/<FHIR resource>?_include=<FHIR resource>:<Search parameters> </pre>
+|+ style="align: bottom; caption-side: bottom; text-align: left;" | ''Use this caption for extra notes, abbreviations, etc.''
 |}

Lab:V1.0 FHIR Lab2Patient: verschil tussen versies