Use case 1: send LaboratoryTestResults

Purpose and relevance

This page describes the electronic and structured exchange of LaboratoryTestResults from a laboratory or healthcare provider to a consumer. The functional design is defined infrastructure-agnostic and independent of any technical implementation.

It standardizes a common information need and provides an information architecture that can be technically implemented in the various applications used in the Belgian healthcare landscape.

Information

The focal body of information is the CBB LaboratoryTestResult, which covers the result of a laboratory analysis by a laboratory. These are specimen-oriented tests as performed in laboratories such as Clinical Chemistry, Serology, Microbiology, etc. In addition to the results of tests with a singular result, this can also contain the results of more complex tests with multiple results or a ‘panel’. Besides the CBB LaboratoryTestResult, the following supportive CBBs compose the LaboratoryTestResult message:

LaboratoryTestResults message

LaboratoryTestResults are sent per patient in a structured manner using CBBs, as shown in the below-rendered model of a LaboratoryTestResult message. Although not directly shown, the CBBs referenced from the LaboratoryTestResult, such as the requester and performer of a LaboratoryTestResult, are also included.


Patient1..1HdBe Patient
LaboratoryTestResult1..*HdBe LaboratoryTestResult
HealthcareOrganization0..*HdBe HealthcareOrganization
HealthProfessional0..*HdBe HealthProfessional


Response message

The receiving system sends a confirmation response message. When LaboratoryTestResults cannot be processed due to errors or business logic, the response message contains the details of the error. Technical specifications will elaborate on the appropriate response and error messages.

Actors

The following actors are defined:

Actor System Definition
LaboratoryTestResult Provider LIMS A system maintaining LaboratoryTestResults over time, such as a LIMS (Laboratory information management system).
LaboratoryTestResult Consumer HD4DP A system acquiring LaboratoryTestResults, such as the HD4DP (healthdata.be for data providers) application.

Process

This section explains the process for sending LaboratoryTestResults from the LaboratoryTestResult Provider to the LaboratoryTestResults Consumer. It consists of four parts: pre-conditions, triggers, process steps, and post-conditions.

Pre condition

  • The Provider and Consumer have agreed on when and which information needs to be exchanged.
  • The Provider is authorized to send the requested patient data to the Consumer.
  • The Provider is able to make a secure connection with the Consumer.
  • The LaboratotyTestResult has a 'final' status.

Trigger events

  • No specific trigger events for sending LaboratoryTestResults here.
    • Agreements made by the Provider and Consumer can involve triggers such as: 'for every positive Hepatitis A virus infection, the Provider sends a LaboratoryTestResults message.'

Process steps

  • The Provider sends a LaboratoryTestResults message, per patient, to the Consumer.
  • The Consumer receives the LaboratoryTestResults message and processes it.
  • The Consumer responds indicating it successfully received the message or detailing why it cannot process the message.
  • In case of a failed message, the Provider may try again (with an updated message) or use another method not described here to provide the information to the consumer.

Post condition

  • The Consumer has received the LaboratoryTestResults message.

Transactions

Transactiongroup Transaction System Role
LaboratoryTestResults (PUSH) Send LaboratoryTestResults LIMS Provider
Receive LaboratoryTestResults HD4DP Consumer

Sequence diagram