General guidance

Introduction
- Diagram of technical layering
Security considerations
Use of codes

Introduction

This implementation guide builds on on healthdata.be CBB implementation guide and defines additional constraints and usage expectations. Especially, implementers SHALL take note of the CBB's general guidance section.

Diagram of technical layering

The below diagram offers an overview of the technical layering and dependencies related to this implementation guide. All names represent the FHIR package in which the FHIR conformance resources are released. Here follows a description of the diagram and its three used colors.

The blue boxes represent projects that form the base or provide inspiration for this implementation guide. More information is given in the general guidance page of the CBB implementation guide.
The green box represents this implementation guide that contains all the functional and techinical definitions needed to exchange LaboratorTestResults.
The grey boxes represent other projects and use cases based on the CBBs and/or the LaboratoryTestResult implementation guide.

Security considerations

This guide assumes that client and servers are able to make a secure connection. It does not provide information on finding the right server nor does it provide information about security. Moreover, each transaction is performed in the context of a specific authenticated/authorized patient, for whose context (token) has been established using authentication mechanisms described elsewhere. Each actor 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.

Use of codes

The bindings with codes SHALL be examined when implementing the LaboratoryTestResult message. Specifically, the use of codes to express LaboratoryTestResult Observations as expressed within the profiles SHALL be followed. As a general backup rule, whenever the laboratory does use a propriety code (e.g., to express a bodysite), a coding.display and .text element SHALL always be included explaining the code.