Clinical Core
1.2.0 - STU1 BE

Clinical Core, published by eHealth Platform. This guide is not an authorized publication; it is the continuous build for version 1.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-be/core-clinical/ and changes regularly. See the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

BeClinicalObservation Model

Clinical Observation logical model
BeProcedure Model

Procedure logical model
BodySite Model

Body site model
Device Logical Model

Logical model for a medical device
DeviceUseStatement Logical Model

Logical model for recording the use of a medical device by a patient
Problem Logical Model

Logical model for Problem

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

BeClinicalObservation

Belgian federal profile for a clinical observation.
BeDevice

A medical device used in the context of Belgian healthcare.
BeDeviceUseStatement

A record of a device being used by a patient in the context of Belgian healthcare.
BeObservation

Belgian federal profile for an observation. Initially based on the functional description of the NIHDI. As Observation is used in many instances in FHIR, please refer to the HL7 specs of the base resource for guidance around expression of actual values using UCUM, methods, location on body etc.

Special remarks for KMEHR users: The FHIR Observation resource captures many things that are in a KMEHR message structured as an ‘item’. This includes things like ‘vital signs such as body weight, blood pressure, and temperature […], personal characteristics such as eye-color […] social history like tobacco use, family support, or cognitive status […]’ ( https://www.hl7.org/fhir/R4/observation.html ) For some of these things, HL7 already has worked out profiles and they SHALL be used when such a use case is needed. Specifically, projects SHALL take note of the existing profiles described on https://www.hl7.org/fhir/R4/observation-vitalsigns.html
BeProblem

A condition, diagnosis or situation that is the focus of care.
BeProcedure

Placeholder profile for contextualising the FHIR resource
BeScoreResult

To support the standard exchange of scores such as pain assessment scores, or risk score, etc

Structures: Data Type Profiles

These define constraints on FHIR data types for systems conforming to this implementation guide.

BeObservationCodeableConcept

This is a supporting profile, only to give guidelines how to express a few of the typical coding systems. In general, it shall be noted SNOMED-CT is the preferred national terminology. Other coding systems remain allowed or MAY be preferred in specific flows (e.g. the use of LOINC codes to express a laboratory test.)

Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

BeExtBodyTopography

Describes the location or relative position on the body, such as superior/inferior, medial/lateral or internal/external.
BeExtLaterality

An explicit statement of laterality of a lesion, or a treatment, etc.
BeExtProblemOriginType

The type of event that triggers the problem to be evaluated - whether the problem was reported from a referring GP, etc…
Surgical Approach

The surgical approach used for the procedure.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

BeVSBodyTopography

Body topography value set - describes the location or relative position on the body (e.g., superior/inferior, medial/lateral, internal/external). Placeholder valueset - the normative definition will be published in the Belgian terminology IG.
Body Site

Body Site - placeholder valueset - the normative definition will be published in the Belgian terminology IG.
Condition Disease Course Value Set

Condition Disease Course
Device Status Reason Value Set

Device Status Reason - placeholder valueset - the normative definition will be published in the Belgian terminology IG.
Device Status Value Set

Device Status - placeholder valueset - the normative definition will be published in the Belgian terminology IG.
Device Type Value Set

Device Type - placeholder valueset - the normative definition will be published in the Belgian terminology IG.
Laterality

Laterality - placeholder valueset - the normative definition will be published in the Belgian terminology IG.
Problem Category Value Set

Problem Category - placeholder valueset - the normative definition will be published in the Belgian terminology IG.
Problem Code

Problem Code - placeholder valueset - the normative definition will be published in the Belgian terminology IG.
Problem Code Value Set

Code of the problem (this is a demonstrative valueset)
Problem Origin Type Value Set

Problem Origin Type
Reaction Manifestation Code

Reaction Manifestation Code (Allergy - Immunization)
Score Category Value Set

Score Category Value Set
Score Value Set

Codes as defined by the NIHDI. Dutch translations are expected for a next release.
Severity

Severity - placeholder valueset - the normative definition will be published in the Belgian terminology IG.

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

Body Site CodeSystem

Body Site CodeSystem
Problem Category Code System

Problem Category
Problem Origin Type

Problem Origin Type
Score Category

Score Category
Score Code System

Codes as defined initially by the NIHDI. Dutch translations were not yet defined but are planned for a next release.